© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
I found some work on this done in Debian
(http://
by a third party contributor
(https:/
After some investigation, here's a summary of what is required to be
done. Some of these items pose regression risk. In highest to lowest
order of impact (IMHO): 7, 3, 4, 2, 5, 8b.
I tried to upload a (hacked) version to my PPA for others to test, but this
FTBFS (see issue 0).
0) My test package FTBFS on the buildds, but does build locally using
sbuild. Need to investigate.
1) ipmiseld and ipmi-config are new and need putting into a package.
2) bmc-watchdog.
to be carried in packaging, or will logs now grow forever, or does the
log no longer exist?
3) Upstream libfreeipmi12 soname bump to 16. This needs an update in
debian/control and in symbols file.
4)
https:/
suggests to me that libipmimonitoring needed a soname bump, but didn't
receive one upstream. This needs investigation.
5) Due to this, libipmidetect0 and libipmiconsole2 should also be
checked for backwards compatibility.
6) debian/*.symbols need updating (see yanovich's work on Github for an
example).
7) nut-ipmi depends on libfreeipmi12 (and libipmimonitori
cannot update a newer freeipmi without a mini-transition (rebuilding
nut-ipmi against a new libfreeipmi15). This extends regression risk to
nut. nut-ipmi is in main (src:nut). nut-ipmi first appeared in Trusty.
8) Some distribution patches need checking:
Ubuntu delta status:
a) 0002_excel_
manually).
b) fix-Wunused-
calls).
c) dso-linking.patch: probably needs updating, though a build without it
seemed OK.
Debian delta status:
d) d/p/up_typos.patch doesn't apply.
9) If the target is Trusty, then a feature freeze exception needs to be
requested from the release team. Will the binNEWs need an archive admin
on hand to deal them also? At this stage of the cycle, we'll also need a
specific QA plan on this update to mitigate regression risk.