touch-packages team mailing list archive

[Chris J Arges <1479207@xxxxxxxxxxxxxxxxxx>]

Hello Adam, or anyone else affected,

Accepted apt into vivid-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.0.9.7ubuntu4.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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

** Changed in: apt (Ubuntu Vivid)
       Status: New => Fix Committed

** Tags added: verification-needed

** Changed in: apt (Ubuntu Precise)
       Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1479207

Title:
  Never-MarkAuto-Sections not working correctly

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Precise:
  Fix Committed
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Vivid:
  Fix Committed
Status in apt package in Debian:
  Fix Released

Bug description:
  [ SRU Justification ]
  Not only is this behaviour broken for every day use, but it also completely breaks livefs generation for ubuntukylin, and causes most of $flavour-desktop to be on the autoremove list in any point release livefs, making this bug point-release critical.

  [ Test Case ]
  Install a metapackage (say, ubuntu-standard), and then "apt-get --purge autoremove ubuntu-standard" and check that only that package is removed, rather than large chunks of its dependencies.

  Further, also run the test case from comment 2 of bug #1429041 and
  make sure the previous fix didn't regress.

  [ Regression Potential ]
  My fix was tested locally against both test cases and passes with flying colours, so I don't see how this can make things any worse than they already are.

  [ Original Report ]
  In current trusty, vivid, and wily, when you install ubuntu-minimal (from the "metapackages" section) in a clean chroot, some 75ish packages are installed.  If you then "apt-get --purge autoremove ubuntu-minimal", some large portion (between 20 and 40, depending on the target release) of those dependencies are removed again.

  If this test is repeated putting the release pocket version of
  apt/libapt on hold, the purge/autoremove only removes the metapackage,
  but none of its dependencies, so this is likely a regression brought
  on from the previous autoremoval fix.

  This bug is release-critical for the 14.04.3 point release, as we
  install using metapackages instead of tasks in point releases, thus
  meaning that anyone removing ubuntu-desktop for any reason will end up
  with dozens (potentially hundreds) of packages on the autoremoval
  list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1479207/+subscriptions