'matches no packages' should appear for every argument

[Rehan Khan]

Imported: http://tracker.labix.org/issue360

Reason: Review issue. I have checked this behaviour. Smart stops at the first error.

further details: https://blueprints.launchpad.net/smart/+spec/bug-reporting-migration

msg1303 (view) Author: ed Date: 2008-02-05.12:24:16

When you ask to install lots of packages in a single command, for example

smart install a b c

then if one of them doesn't match any packages, smart prints a message

error: 'a' matches no packages. Suggestions:
   [...]

and then stops. It prints this message only for the first argument that matches
no packages.

It would be better to continue and print the same message, if applicable, for
each other argument too.

[Rehan Khan (rasker)]

behaviour confirmed, importance undecided

[Rehan Khan (rasker)]

This is also in the same ball park.

http://tracker.labix.org/issue331

msg1199 (view) Author: rolfn Date: 2007-10-04.12:23:46

The smart call "install" should have a parameter "--ignore-errors". Then
packages which can't be installed should trigger a warning instead of an error
with a program break.