Public bug reported: 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 ** Affects: nut (Ubuntu) Importance: Undecided Status: New -- FFE: Network UPS Tools 2.4.1-2 https://bugs.launchpad.net/bugs/334470 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
