[Bug 1732795] [NEW] Sync rfkill 0.5-2 (main) from Debian unstable (main)
Launchpad Bug Tracker
1732795 at bugs.launchpad.net
Thu Nov 16 22:10:04 UTC 2017
You have been subscribed to a public bug by Bryan Quigley (bryanquigley):
Please sync rfkill 0.5-2 (main) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* Resynchronise with Debian. Remaining changes:
- Add upstart jobs rfkill-store and rfkill-restore to save soft RF kill
state across reboots.
Per the changelog the only remaining changes is to create the upstart jobs in /etc/init.
That's no longer needed and no longer has any effect with upstart no longer used - in fact
some of upstart has already been removed from this package, see:
* Drop obsolete and no-op dh_installinit --upstart-only option.
(LP: #1519228)
Changelog entries since current bionic version 0.5-1ubuntu4:
rfkill (0.5-2) unstable; urgency=medium
* QA upload.
* Set Debian QA Group as maintainer. (see #881513)
* Migrations:
- debian/control to format 1.0.
- debian/rules to simplified format.
- DH level to 10.
* debian/control:
- Bumped Standards-Version to 4.1.1.
- Removed no longer needed build dependency dpkg-dev.
- Updated VCS fields.
* debian/patches/:
- debian-changes:
~ Renamed to 10_fix-manpage.patch.
~ Added a specific header.
- 20_add-GCC-hardening.patch: created to use GCC hardening.
* debian/rules:
- Do not use Debian revision as version for final binary.
- Use build architecture compiler to avoid a FTCBFS. Thanks to
Helmut Grohne <helmut at subdivi.de>. (Closes: #839798)
* debian/source/:
- options: removed. This file was pushing all patches to a single file.
- patch-header: removed. It was creating a "default" header.
* debian/watch:
- Bumped to version 4.
- Updated.
-- Joao Eriberto Mota Filho <eriberto at debian.org> Mon, 13 Nov 2017
18:17:03 -0200
** Affects: rfkill (Ubuntu)
Importance: Wishlist
Status: New
--
Sync rfkill 0.5-2 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1732795
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.
More information about the Ubuntu-sponsors
mailing list