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

[Holger Levsen]

On Wed, Mar 08, 2017 at 12:50:36PM +0100, Andreas Beckmann wrote:
> >>> 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.

yes, we are and that's wrong.

However, your "outdated" state doesnt *really* help with this, or? AIUI it
will make us stop testing (or rather, stop trying to test) outdated packages,
but it's still not testing *dependend* packages correctly, or?

eg libc6 will be tested in jessie, instead of jessie-security, thats fine. But
wont packages depend on libc in jessie-security not be tested, as libc is in
state "outdated" there?


(also I'd like to show that there are outdated packages in some suites and
that these can be removed…)

-- 
cheers,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 811 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20170308/1d0be66a/attachment.sig>