[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

detecting uninstallable packages in sid/experimental (was: Re: Bug#793405: nmu: caja-actions_1.8.0+dfsg1-1)

On 2015-07-23 22:07, Jonathan Wiltshire wrote:
> On Thu, Jul 23, 2015 at 07:44:53PM +0200, Andreas Beckmann wrote:
>> nmu caja-actions_1.8.0+dfsg1-1 . amd64 . -m "Rebuild in an up-to-date environment."
>> was quarantined in NEW since February ...
>> ==> caja-actions/amd64 unsatisfiable Depends: libgtop2-7 (>= 2.22.3)
> Scheduled. (As usual, thanks for noticing such things - it's a great help.)

Since a recent update to piuparts it is possible to detect some
uninstallable packages in sid and experimental in a more timely fashion
(which resulted in /me filing more binNMU bugs):

piuparts.debian.org has them for amd64:


My local piuparts instance supplies me with results for i386 as well.

This catches only "trivial" uninstallabilities, i.e. completely
unavailable packages, but no version incompatibilities.

A much better analysis of uninstallability is performed by the DOSE
tools: https://qa.debian.org/dose/debcheck.html
but output is not friendly enough for regular checking.
Also it lacks support for experimental - Ralf, can you add this?

I don't know what output format of the DOSE uninstallability webpages
could be better for a quick glance over the changes to possibly file
bugs for binNMUs.

Maybe a list of all uninstallable packages (or just the newest 1000),
ordered by duration (newest uninstallabilities first), merging all (or a
subset of architectures) together. Switchable between being based on
binary or source packages. This should be correlated to ongoing
transitions. Maybe with a udd-like query interface ...

Results should be updated frequently - correlated to the mirror pushes.

Some way to propagate this uninstallability information into piuparts
would be nice, too. A package becoming (un)installable should trigger a
recheck in piuparts.


Reply to: