FFE: Network UPS Tools 2.4.1-2

[Arnaud Quette]

FeatureFreeze Exception for Network UPS Tools

* A description of the proposed changes, with sufficient detail to estimate their potential impact on the distribution
--
Update the nut package in Jaunty from 2.2.2-10ubuntu3 to 2.4.1-2 through a Debian sync (see LP: #332030)
This has a minimal impact in terms of risks, but a maximal impact in terms of new features, Ubuntu differentiation, user benefits and diff with Debian (see below)

* A rationale for the exception, explaining the benefit of the change
--
- this represents the final step of the "Improved Power Management" blueprint:
https://blueprints.edge.launchpad.net/ubuntu/+spec/improved-power-management

The other milestones have been reached in time, but sadly not for NUT (too much upstream and Debian work)!

- this version adds many new features (needed for Ubuntu Server)
see the attached upstream-new-features.txt attached

- this version address a lot of bugs (see below) and has seen a lot of Debian work (see LP: #332030)

- LP bugs closed:
- 1568: nut takes too long to start
- 221737: upsd doesn't start on system startup
- 239025: usbhid-ups not behaving with Tripplite UPS
- 278495: megatec_usb does'nt detect ups
- 332030: [sync request] Please sync nut 2.4.1 from Debian unstable (main)
- 332032: nut wrongly install nut-cgi's config files

- remaining diffs with Debian
  * debian/control:
    - Update maintainer field as per spec.
  (The below ones only need to be uncommented in the matching file...)
    - Add Breaks to ensure we have correct udev version.
  * debian/{nut-cgi,nut}.postinst: add nut to the dialout
    and nut groups unconditionally, to handle the upgrade from the hardy
    release.
  * debian/rules: pre merge the changes for Ubuntu (udev path and version),

* Any additional information which would be helpful in considering the decision
--
- ChangeLog can be found here: http://svn.debian.org/wsvn/nut/tags/v2.4.1/ChangeLog?op=file&rev=0&sc=0

- jaunty pbuilder log is attached in the archive (nut_2.4.1-2_i386.build)

- install log (clean test in pbuilder chroot) are also attached with the following tests:
 - jaunty: fresh install and update from 2.2.2-10ubuntu3 to 2.4.1-2 of a running configuration (jaunty-{fresh,upgrade}.install)
 - intrepid: update from 2.2.2-6ubuntu1 to 2.4.1-2 (intrepid-update.install)
 - hardy: not considered since jaunty is not an LTS (?) so there is no interest in testing 2.2.1-2.1ubuntu7.2 upgrade

The validation were:
- check that the install or update goes smoothly, without warning or errors,
- check that the previous configuration has been migrated from /etc/default/nut to /etc/nut/nut.conf in case of upgrade
- check that the resulting configuration runs the same way and is still working in case of upgrade (ie the same daemons restarted successfully)
- check that the user is warned that nut has to be configured in case of fresh install (#221737)
All this has been done with a bare config (see the attached nut-config.txt), using the dummy-ups driver

[Scott Kitterman (kitterman)]

Approved. I see you are subscribed to bugs for the package and are from upstream. Please keep an eye on the package and send patches if needed ....

You may seek sponsorship through the normal process now.

[Scott Kitterman (kitterman)]

Nevermind. I'm sorry. I just noticed this is in Main, so not mine to approve.

[Arnaud Quette (aquette)]

2009/2/25 Scott Kitterman <email address hidden>

> Nevermind. I'm sorry. I just noticed this is in Main, so not mine to
> approve.
>

nevermind, thanks for your action ;-)

and yes, I'm leading the upstream devs, doing the debs, cleaning the
kitchen... ^_^

Arnaud
--
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/

[Martin Pitt (pitti)]

Approved based on the fact that it's an approved blueprint and has no reverse dependencies.

[Dustin Kirkland  (kirkland)]

Arnaud-

Can you attach a debdiff to this bug, applying the remaining Ubuntu changes to http://ftp.debian.org/debian/pool/main/n/nut/nut_2.4.1-2.dsc ?

I'll upload as soon as I have that.

Thanks,
:-Dustin

[Arnaud Quette (aquette)]

here it is!

please double check it, along with it's install / upgrade (my tests were done on the pristine Debian version, though none of the Ubuntu diff should make troubles here) and closed LPs

cheers,
Arnaud

[Dustin Kirkland  (kirkland)]

Hmm, there is a slight wrinkle here...

This version of nut build-depends on libpowerman0-dev, which is in universe. nut is in main, and should only depend, recommend, and build-depend on other packages in main.

We probably need to file an MIR for libpowerman0-dev...

:-Dustin

[Dustin Kirkland  (kirkland)]

Arnaud-

It's kind of late in Jaunty to start the Main Inclusion process for powerman, as a brand new package.

What do you think about building nut without libpowerman0-dev for now? And starting the MIR process for powerman. If it makes it in, we can turn it on in the build...

:-Dustin

[Dustin Kirkland  (kirkland)]

I just tested the build, and it succeeds. So I'm uploading Nut 2.4.1-2 right now, without the build-depends on libpowerman0-dev to ensure that this version gets into Jaunty, and so that people can start testing it.

If you want to get it building against that library, please:
 1) open a new bug (with simple debdiff) asking for this build-depend to be added
 2) file an MIR for powerman, see: https://wiki.ubuntu.com/MainInclusionReportTemplate
 3) file an MIR bug for powerman
 4) subscribe me to all of the above and I'll help out :-)

:-Dustin

[Arnaud Quette (aquette)]

hey Dustin,

I'll reply directly to that one.

2009/3/3 Dustin Kirkland

> I just tested the build, and it succeeds. So I'm uploading Nut 2.4.1-2
> right now, without the build-depends on libpowerman0-dev to ensure that
> this version gets into Jaunty, and so that people can start testing it.
>

ok, so let's go that way. *but* you (the server team) will have less PDUs to
announce (only the SNMP ones present in NUT).
the thing I'm not sure about: removing only the Build-dep should not be
sufficient since the debhelper files for powerman are still there! or did I
got you wrong?

If you want to get it building against that library, please:
> 1) open a new bug (with simple debdiff) asking for this build-depend to be
> added

I will need the 2.4.1-2 source pkg you've uploaded (which removes the
build-dep *and* the debhelper files) before I can do the debdiff...

> 2) file an MIR for powerman, see:
> https://wiki.ubuntu.com/MainInclusionReportTemplate

done: https://wiki.ubuntu.com/MainInclusionReportPowerman

 3) file an MIR bug for powerman

done: https://launchpad.net/bugs/337226

> 4) subscribe me to all of the above and I'll help out :-)
>

done

Arnaud

[Dustin Kirkland  (kirkland)]

On Tue, Mar 3, 2009 at 8:39 AM, Arnaud Quette <email address hidden> wrote:
> ok, so let's go that way. *but* you (the server team) will have less PDUs to
> announce (only the SNMP ones present in NUT).
> the thing I'm not sure about: removing only the Build-dep should not be
> sufficient since the debhelper files for powerman are still there! or did I
> got you wrong?

You're absolutely right.... The build did *not* succeed. Sorry.

> I will need the 2.4.1-2 source pkg you've uploaded (which removes the
> build-dep *and* the debhelper files) before I can do the debdiff...

Forget the package I uploaded... It's bust. Just hit me with a
debdiff against Debian (like your other one), but drop the build-dep
(and whatever else that entails) against powerman. This will allow
for some testing of nut, while the MIR gets processed.

> done: https://wiki.ubuntu.com/MainInclusionReportPowerman
> done: https://launchpad.net/bugs/337226

Great! I'll try to nurse those along.

:-Dustin

[Arnaud Quette (aquette)]

here it is (2.4.1-2ubuntu1)

-- Arno

[Dustin Kirkland  (kirkland)]

Awesome, thanks! Uploaded!

Okay, now, let's see if we can get that FFE pushed through...

:-Dustin

[Steve Langasek (vorlon)]

nut 2.4.1-2ubuntu2 is in jaunty now - is there something else requiring a freeze exception that we should keep this bug open for?

[Arnaud Quette (aquette)]

yep, possibly for reverting my above patch if/when the above mentioned
powerman's MIR is accepted...

-- Arnaud

[Dustin Kirkland  (kirkland)]

On Fri, Mar 6, 2009 at 3:53 PM, Arnaud Quette <email address hidden> wrote:
> yep, possibly for reverting my above patch if/when the above mentioned
> powerman's MIR is accepted...

Steve, we would need an MIR for powerman, such that nut could compile
against it.

I'm afraid that it's probably too late in Jaunty to do that, but I'll
leave that for the MIR-team.

:-Dustin

[Martin Pitt (pitti)]

Dustin Kirkland [2009-03-07 14:57 -0000]:
> I'm afraid that it's probably too late in Jaunty to do that, but I'll
> leave that for the MIR-team.

It's not a MIR process question, we have traditionally moved packages
between components until the bitter end of a release (not that I
*like* that, but it was just necessary). It's rather a question of who
will maintain the package and whether we have the resources in the
server team to support it. If the server team wants it, please go
ahead with the SRU.

[Arnaud Quette (aquette)]

2009/3/8 Martin Pitt

> Dustin Kirkland [2009-03-07 14:57 -0000]:
> > I'm afraid that it's probably too late in Jaunty to do that, but I'll
> > leave that for the MIR-team.
>
> It's not a MIR process question, we have traditionally moved packages
> between components until the bitter end of a release (not that I
> *like* that, but it was just necessary). It's rather a question of who
> will maintain the package and whether we have the resources in the
> server team to support it. If the server team wants it, please go
> ahead with the SRU.
>

well, the server team has /me behind, at both upstream and Debian levels.
that should help a bit ;-)

-- Arnaud

[Daniel Holbach (dholbach)]

I unsubscribe the sponsors team for now, nothing to sponsor.

[Chuck Short (zulcss)]

Can this bug be actually closed since you know jaunty is closed?

Regards
chuck

[Arnaud Quette (aquette)]

Hey Chuck,

I guess you can close it since:
- 2.4.1-2 has made its way into Jaunty (2.4.1-2ubuntu4 to be exact),
- jaunty is closed (as you've mentioned),
- this one was left open for a newer version, including the Powerman (PDU)
support, which in turn would need to have powerman in main...

For that last, another bug is needed against karmic, but I'm checking with
the Powerman maintainer to create a common core that could be included in
both NUT and Powerman. So, up to you the Server Team ;-)

cheers,
Arnaud