Hello Markus, or anyone else affected, Accepted cracklib2 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cracklib2/2.9.2-1ubuntu1 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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! -- 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/1681231 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Confirmed Status in cracklib2 package in Ubuntu: Fix Released Status in cracklib2 source package in Trusty: Incomplete Status in cracklib2 source package in Xenial: Fix Committed Status in cracklib2 source package in Yakkety: Won't Fix Status in cracklib2 source package in Zesty: Fix Committed Status in cracklib2 package in Debian: Fix Released Bug description: [Impact] Upgrading cracklib-runtime is not working for some systems due to trigger cycles. This is making distribution upgrades challenging. [Test Case] While we haven't been able to replicate this directly the following tests will confirm that there are no regressions. Test A ------ 1) Install cracklib-runtime from -proposed. 2) Reinstall dictionaries-common and verify that the trigger is called Test B ------ 1) With the version of cracklib-runtime from -proposed installed, confirm that a distribution upgrade to next supported release succeeds. Test C ------ 1) Test a release upgrade from an affected release (Trusty, Xenial) to the next supported release (Xenial, Zesty) with -proposed enabled. To do this upgrade you'll need to edit /etc/apt/sources.list to the target release and run 'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed. [Regression Potential] It's possible that upgrades will break hence all the regression tests in the Test Case. Original Description -------------------- This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp