[Piuparts-devel] Bug#856846: piuparts.debian.org: jessie-security has >1700 packages in dependency-failed-testing status

Andreas Beckmann anbe at debian.org
Wed Mar 8 11:50:36 UTC 2017

On 2017-03-08 12:41, Holger Levsen wrote:
> Hi Andreas,
> On Wed, Mar 08, 2017 at 08:21:07AM +0100, Andreas Beckmann wrote:
>> On 2017-03-05 14:07, Andreas Beckmann wrote:
>>>> see https://piuparts.debian.org/jessie-security
>>> These are mostly packages where jessie has a newer version than
>>> jessie-updates ... I have a local hack that adds a new state "outdated"
>>> and ignores these packages 
> why are those packages ignored and not used? In the real world they are used
> too, so shouldn't we test using them?

    1814 - fail/libc6_2.19-18+deb8u3.log (PTS) (BTS) #710521
    1488 - fail/multiarch-support_2.19-18+deb8u3.log (PTS) (BTS)

libc6      | 2.19-18+deb8u7  | stable     | amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x

So we are trying to test downgrades ... stable/updates does not get pruned.
In the real world these packages will only be used on misconfigured systems
(no deb source for stable itself or only cds or ..)

>> (but I reuse one of the old states, since
>>> adding a new state will require adding another column of zeroes to all
>>> counts.txt files ...)
> been there done that. (modifying columns in counts.txt…)

Not any more :-)


More information about the Piuparts-devel mailing list