ipmitool recipe update needed?

Vernon Mauery vernon.mauery at linux.intel.com
Fri Apr 12 05:49:29 AEST 2019


On 11-Apr-2019 02:08 PM, Alexander Amelkin 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.

Would it be better to just point at the upstream release tag instead of 
the release tarball?

Along these lines, if we can get my pending dbus interface pull-request 
merged, openbmc can use the upstream ipmitool with only one patch to 
change the default interface (which is on my list to make a --configure 
option at some point).

--Vernon

>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