I'm just trying to wrap my head around the update output
results on the 'testing' page for devlopers,
http://www.debian.org/devel/testing
(This is more an example than a request... it just makes
a good illustration)
Basically, smstools depends on libmm11, which has been
superseeded with libmm12 (and the smstools in unstable
depends on this new library version)...
So the update output for the two is:
trying: mm
skipped: mm (1230+5)
got: 6+0: a-6
* alpha: smstools
~~
trying: smstools
skipped: smstools (1219+2)
got: 6+0: a-6
* alpha: smstools
~~
skipped: mm (454+753)
got: 6+0: a-6
* alpha: smstools
~~
trying: smstools
skipped: smstools (142+1065)
got: 6+0: a-6
* alpha: smstools
Is manual intervention required to make mm and smstools
go into testing together, or is there some automated
process I'm not aware of. The page makes an oblique
reference to a possible automated system, but...
This is prolly a bad case, since lots of other stuff in
testing depends on libmm11, but doesn't get listed in the
output... Is the output a complete list of packages that
get broken, or just the first 'n'... (In this case, php4
depends on libmmnn, and it's held back in the excuses file
for other reasons.)
--
-----------------------------------------------------------
Paul "TBBle" Hampson, MCSE
6th year CompSci/Asian Studies student, ANU
The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361)
Paul.Hampson@Anu.edu.au
Of course Pacman didn't influence us as kids. If it did,
we'd be running around in darkened rooms, popping pills and
listening to repetitive music.
-- Kristian Wilson, Nintendo, Inc, 1989
This email is licensed to the recipient for non-commercial
use, duplication and distribution.
-----------------------------------------------------------
Attachment:
pgpuMysW7VJNI.pgp
Description: PGP signature