[Bug 1850851] Re: [SRU] ubuntu-release-upgrader no longer produces tarballs

Brian Murray brian at ubuntu.com
Thu Oct 31 21:46:50 UTC 2019


Hello Adam, or anyone else affected,

Accepted ubuntu-release-upgrader into eoan-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:19.10.15.2 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-release-upgrader (Ubuntu Eoan)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1850851

Title:
  [SRU] ubuntu-release-upgrader no longer produces tarballs

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Committed
Status in ubuntu-release-upgrader source package in Eoan:
  Fix Committed

Bug description:
  [ SRU Justification ]
  ubuntu-release-upgrades was unintentionally relying on a debhelper bug/misfeature where mixing and matching dh(1) and explicit make targets would lead "dh binary" to call a binary-indep target in debian/rules, despite no dependency being declared.  This dh(1) misfeature went away when arch/indep handling was reworked in debhelper 12.5, and ubuntu-release-upgrader's binary-indep target (which generated the release-upgrader tarball) hasn't been called since.

  [ Test Case ]
  1) Make sure the release-upgrader tarball is built, included in .changes, and published to the archive.
  2) debdiff .deb binaries from this upload and the last to ensure nothing else has gone amiss.

  [ Regression Potential ]
  Fairly low.  This is just fixing some broken assumptions about makefiles and debhelper to deterministically return us to the situation we were arriving at by accident before.

  [ Other Info ]
  In doing this, and testing interaction between arch and indep targets and dh(1) itself, I noted that there were a few more small fixes to be made which are no-ops in the current package, but are ticking time-bombs if the package ever grows a non-arch-all package, so I'm including those fixes too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1850851/+subscriptions



More information about the foundations-bugs mailing list