New upstream version 1.4.1

I found some work on this done in Debian
(http://anonscm.debian.org/gitweb/?p=pkg-freeipmi/pkg-freeipmi.git) and
by a third party contributor
(https://github.com/yanovich/freeipmi-debian).

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.logrotate has been dropped upstream. Does this now need
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://github.com/yanovich/freeipmi-debian/commit/860834b837cf067171d480a59dc73ec3c5f18f2d
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 libipmimonitoring5). Thus we
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_when_opening_tmp.patch: applied upstream (checked
manually).

b) fix-Wunused-result.patch: doesn't apply (no sign of read and write
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.

> I tried to upload a (hacked) version to my PPA for others to test, but this FTBFS (see issue 0).

Now fixed, and built in ppa:racb/experimental (freeipmi 1.4.1-1~test2). There are still many packaging issues that need to be resolved, as described in my previous comment. But this should at least make it possible to begin testing changes made upstream for the pieces that were already functional.

Unassigned myself, since the conclusion seems to be that this won't make Trusty.

This landed in xenial.