bugreporting for ubuntu-release-upgrader is struggling on naming issue

This does not work because ubuntu-release-upgrader is a source package. However, the error messages in ubuntu-release-upgrader itself indicate that one should use a binary package with ubuntu-bug, e.g. ubuntu-bug ubuntu-release-upgrader core as you've mentioned. See:

#: ../DistUpgrade/DistUpgradeCache.py:706
msgid ""
"If none of this applies, then please report this bug using the command "
"'ubuntu-bug ubuntu-release-upgrader-core' in a terminal."

Having said that it'd still be good if people could use "ubuntu-bug ubuntu-release-upgrader". This was previously mentioned in a different bug report and I'm copying the comment here.

"On IRC you also asked about "apport-bug ubuntu-release-upgrader". As this is not a (binary) package name, this won't work. If this is desired, apport-symptoms should get a new symptom with that name (and perhaps a few aliases like "release-upgrade" and "upgrade" while we are at it) which simply redirects the report to "ubuntu-release-upgrader-core"; see /usr/share/doc/apport/symptoms.txt ." - Martin Pitt

Writing this symptom makes sense and it had just slipped off my to do list.

This bug was fixed in the package apport-symptoms - 0.20

---------------
apport-symptoms (0.20) saucy; urgency=low

  * Add in an symptom for ubuntu-release-upgrader, and aliases for it that just
    return the binary package. (LP: #1173913)
 -- Brian Murray <email address hidden> Wed, 22 May 2013 15:03:40 -0700

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!

Hello Sasa, or anyone else affected,

Accepted apport-symptoms into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/apport-symptoms/0.16.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!

Testing done for Ubuntu13.04 raring.

A run of

ubuntu-bug ubuntu-release-upgrader

is now working.

A test for Ubuntu12.04 precise is still pending.

This bug was fixed in the package apport-symptoms - 0.19.1

---------------
apport-symptoms (0.19.1) raring-proposed; urgency=low

  * Add in an symptom for ubuntu-release-upgrader, and aliases for it that just
    return the binary package. (LP: #1173913)
 -- Brian Murray <email address hidden> Wed, 22 May 2013 15:36:40 -0700