ipmitool recipe update needed?

William Kennington wak at google.com
Fri Apr 12 05:07:52 AEST 2019


The problem with the archive tarballs is that their contents are not
stable (they are autogenerated when needed from git), and they aren't
dist tarballs so they haven't been run over `./bootstrap.sh;
./configure; make dist` yet.

On Thu, Apr 11, 2019 at 4:08 AM Alexander Amelkin <a.amelkin at yadro.com> wrote:
>
> Hi, Andrew!
>
> Yes, I've seen that recipe and planned to update it, just didn't have time to. You may do so yourself if you want.
>
> Releases are automatically packaged by GitHub according to tags and the tags in the project are like IPMITOOL_1_8_18, so the packaged release is https://github.com/ipmitool/ipmitool/archive/IPMITOOL_1_8_18.tar.gz
>
> For future releases I planned to continue using the same tagging scheme.
>
> Alexander.
>
> 09.04.2019 19:02, Andrew Geissler wrote:
> > Hi Alexander,
> >
> > A while back we had some intermittent CI failures when
> > trying to retrieve the ipmitool package from sourceforge.
> >
> > The link for ipmitool on sourceforge shows it's been moved
> > to github. Are there plans to update the recipe upstream to
> > use github? William noted in the infrastructure workgroup that
> > you'll probably have to provide the package in the expected
> > format on github for it to work.
> >
> > The recipe is:
> > meta-openembedded/meta-oe/recipes-kernel/ipmitool/ipmitool_1.8.18.bb
> >
> > Andrew
>


More information about the openbmc mailing list