[backportpackage] package failure warning should warn properly if the package argument is not a source package

[Karl Thorén]

I did used backportpackage to build and upload Gnupg2 version 2.0.19 to my personal PPA.

The I started to build all reverse depends but backportpackage started to fail
with the message "backportpackage: Error: The package 'kleopatra' does not exist in the Ubuntu primary archive in quantal, quantal-security, quantal-updates or quantal-proposed"

Command used: "backportpackage --no-conf --dont-sign -b -w kleopatra -s quantal kleopatra"
I did also use "backportpackage --dont-sign -b -w kleopatra -s quantal kleopatra"
and "backportpackage --no-conf --dont-sign -b -w kleopatra kleopatra"

All test failed with "The package 'kleopatra' does not exist in the Ubuntu primary archive"

I also tested to build the packages gpa and dirmngr and they build without errors.

apt-get install kleopatra does install kleopatra without any problems on my computer.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubuntu-dev-tools 0.143ubuntu0.2
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
Date: Fri Dec 21 23:56:18 2012
InstallationDate: Installed on 2012-12-02 (19 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: ubuntu-dev-tools
UpgradeStatus: No upgrade log present (probably fresh install)

[Benjamin Drung (bdrung)]

You have to specify a _source_ package name. In case of kleopatra, the source package is kdepim.

Therefore this bug report is about improving the error message. Maybe we should add "Have you specified a valid source package name?" or "Please specify a existing source package name."

[Stefano Rivera (stefanor)]

The error in the description doesn't seem accurate, the current error generated is:

backportpackage: Error: The source package 'kleopatra' does not exist in the Ubuntu primary archive in quantal, quantal-security, quantal-updates or quantal-proposed

That clearly says "source package", as Benjamin suggested it should. So, I'm going to mark this bug as invalid.