Hello Thomas, or anyone else affected, Accepted gnome-keyring into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- keyring/3.8.2-0ubuntu3.1 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: gnome-keyring (Ubuntu Saucy) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1241881 Title: gnome-keyring depends on transitional package libgcr-3-1 Status in “gnome-keyring” package in Ubuntu: Fix Committed Status in “gnome-keyring” source package in Saucy: Fix Committed Bug description: According its package description, libgcr-3-1 version 3.8.2-4 in Saucy Salamander is a transitional package that should be safe to remove. However, an attempt to remove the package reveals that gnome-keyring (version 3.8.2-0ubuntu3) depends on it. I cannot tell if removing the dependency from gnome-keyring was forgotten or libgcr-3-1 has been wrongfully marked as transitional, but the latter seems highly unlikely. Either way this is a problem that should be fixed. [Rationale] People should be able to remove transitional packages without removing the packages that depend on their replacements. This is forbidding people from removing libgcr-3-1 without removing gnome-keyring as well. [Test Case] Install the gnome-keyring package, and then try removing the transitional libgcr-3-1 package. It forces the removal of gnome-keyring, even though gnome-keyring should depend on libgcr-base-3-1 instead. [Regression Potential] None. This is just a simple dependency change. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sat Oct 19 01:43:15 2013 InstallationDate: Installed on 2010-09-07 (1137 days ago) InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: Upgraded to saucy on 2013-10-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1241881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
