Hello Sasa, or anyone else affected, Accepted apport-symptoms into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/apport- symptoms/0.19.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! ** Description changed: [ Impact ] It can be challenging to report distribution upgrade bugs about ubuntu- release-upgrader because it is a source package and the binary package is called ubuntu-release-upgrader-core. - [ Test Case ] 1) run ubuntu-bug ubuntu-release-upgrader - 2) observer a dialog saying that the package does not exist + 2) observe a dialog saying that the package does not exist After installing the version from -proposed you'll see an apport dialog with information about ubuntu-release-upgrader-core e.g. Package: ubuntu-release-upgrader-core. [ Regression Potential ] None, as it did not work before. Original Description -------------------- I was wondering why so many people report about ubuntu-release-upgrader without using apport for this. I think I know it now. If you give to command line: ubuntu-bug ubuntu-release-upgrader upgrader" you will see a popup that informs you that such a package do not exist. The correct command would be ubuntu-bug ubuntu-release-upgrader-core , but I think this is not known to much reporter, also because launchpad itself list all only as "ubuntu-release-upgrader" The people just not see how to name correctly for apport. This should be treat with,...well is a redirect possible?! ProblemType: BugDistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.10 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CrashDB: ubuntu Date: Sun Apr 28 12:35:04 2013 InstallationDate: Installed on 2013-01-13 (104 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: allSourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to raring on 2013-04-18 (9 days ago) VarLogDistupgradeTermlog: ** Changed in: apport-symptoms (Ubuntu Raring) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173913 Title: bugreporting for ubuntu-release-upgrader is struggling on naming issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport-symptoms/+bug/1173913/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
