Public bug reported:
I presume that check-mir is expected to be run on a system with
appropriate apt sources enabled. But having the proposed pocket of the
development release enabled is not appropriate even on a development
system. This means that when a package is blocked from proposed
migration, and another package needs to be uploaded to fix it, that
second package cannot have "check-mir" run on its source with accurate
results, as check-mir is blind to the proposed pocket.
For example: right now, apache2-dev is in saucy-proposed, but there is
no such thing in saucy, since it is introduced by apache2 2.4 whose
migration is in progress. When I run check-mir on php5 from Debian, I
see "apache2-dev does not exist (pure virtual?)" when it does exist in
saucy-proposed.
The only way I can think of to fix this is to switch to querying
Launchpad directly. Is there any other way?
** Affects: ubuntu-dev-tools (Ubuntu)
Importance: Undecided
Status: New
** Package changed: python-apt (Ubuntu) => ubuntu-dev-tools (Ubuntu)
--
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1199751
Title:
[check-mir] does not use -proposed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1199751/+subscriptions
--
universe-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
