Discussion:
[Ipmitool-devel] ipmitool - Get another ipmitool version (1.8.14?)
Thomas Renninger
2014-03-06 12:03:56 UTC
Permalink
Hi,

not sure what the plans are for another version update.
Because of git commit:

--------------------
commit c18ec02f3304ce2a889a50e378f07a4168af3884
Author: Petter Reinholdtsen <***@hungry.com>
Date: Wed Feb 5 17:30:32 2014 +0100

Move all files one level up in the file hierarcy, to avoid the useless
ipmitool directory.
--------------------

An ipmitool-1.8.13.tar.bz2 tarball including plain version 1.8.13
will never patch with new mainline commits.

Typically packagers use latest version tarballs and cherry pick
additional critical patches on top.
Or add a "patch to latest git head" on top:
git diff IPMITOOL_1_8_13 HEAD

This does not work now anymore or would need adjusting of every
single patch.

A new version release/tag would solve this issue.

Thanks,

Thomas
Petter Reinholdtsen
2014-03-06 13:28:32 UTC
Permalink
[Thomas Renninger]
Post by Thomas Renninger
Hi,
not sure what the plans are for another version update.
I do not know either. I guess it depend on someone doing the work to
wrap up a release. Any volunteers? :)
Post by Thomas Renninger
--------------------
commit c18ec02f3304ce2a889a50e378f07a4168af3884
Date: Wed Feb 5 17:30:32 2014 +0100
Move all files one level up in the file hierarcy, to avoid the useless
ipmitool directory.
--------------------
An ipmitool-1.8.13.tar.bz2 tarball including plain version 1.8.13
will never patch with new mainline commits.
Typically packagers use latest version tarballs and cherry pick
additional critical patches on top.
git diff IPMITOOL_1_8_13 HEAD
This does not work now anymore or would need adjusting of every
single patch.
A new version release/tag would solve this issue.
I do not understand what you mean here. What is it that 'patch -p1'
can't solve?
--
Happy hacking
Petter Reinholdtsen
Jim Mankovich
2014-03-06 16:28:55 UTC
Permalink
I can cut the release, we just need to decide when and what goes in it.
I have one change I need to get submitted yet, probably get to it next
week sometime.
Post by Petter Reinholdtsen
[Thomas Renninger]
Post by Thomas Renninger
Hi,
not sure what the plans are for another version update.
I do not know either. I guess it depend on someone doing the work to
wrap up a release. Any volunteers? :)
Post by Thomas Renninger
--------------------
commit c18ec02f3304ce2a889a50e378f07a4168af3884
Date: Wed Feb 5 17:30:32 2014 +0100
Move all files one level up in the file hierarcy, to avoid the useless
ipmitool directory.
--------------------
An ipmitool-1.8.13.tar.bz2 tarball including plain version 1.8.13
will never patch with new mainline commits.
Typically packagers use latest version tarballs and cherry pick
additional critical patches on top.
git diff IPMITOOL_1_8_13 HEAD
This does not work now anymore or would need adjusting of every
single patch.
A new version release/tag would solve this issue.
I do not understand what you mean here. What is it that 'patch -p1'
can't solve?
--
Loading...