autopkgtest should provide apt debug log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
autopkgtest (Ubuntu) |
Fix Released
|
Medium
|
Ian Jackson |
Bug Description
Binary package hint: autopkgtest
14:28 <seb128> iwj: bug #135519, do you think those bugs could have an apt
14:28 <ubotu> Launchpad bug 135519 in compiz "autopkgtest gutsy compiz amd64:
14:28 <seb128> iwj: the bug has been opened on compiz but the issue is
14:28 <iwj> seb128: I could probably organise that. How would I acquire one ?
14:29 <seb128> iwj: probably by setting Debug::
the apt configuration
14:29 <iwj> seb128: Right, if it's just a transitional problem feel free to
close the bug with `this is fixed now we think'.
14:30 <seb128> iwj: is there a way to determine that the bug is a "package not
14:30 <iwj> The tester can't really tell if uninstallability is just transient
or not.
14:30 <iwj> I think it would be better just to turn on the debugging in general.
14:30 <seb128> mvo: ^ what do you think?
14:30 <iwj> Or to capture it and suck it out.
14:30 <iwj> I mean, suck it out if the installation fails.
14:31 <seb128> right, that would be nice
14:34 <seb128> mvo: would it be possible to make apt smarter about displaying
14:34 <seb128> it display package is not installable because <list of depends
not installable>
14:34 <seb128> but doesn't mention where is the issue in the list of depends
14:34 <seb128> and what prevents it to be installed
14:34 <mvo> seb128: probably
Changed in autopkgtest: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
assignee: | nobody → ijackson |
Following discussion on irc, and tests, this can be achived by setting :pkgProblemReso lver=true
Debug:
and this should be done globally for all of autopkgtest's apt invocations.