On Sat, Jul 12, 2014 at 06:55:09PM +0100, Adam D. Barratt wrote:
> tl;dr: do stable and stable-security chroots apply P-a-s correctly?
>
> DSA 2952-1 updated kfreebsd-9 in wheezy-security. As it was built on all
> architectures for which kfreebsd-9 was available in wheezy, it was then
> also accepted in to proposed-updates. It appears that packages for some
> other architectures - arm{el,hf}, ia64, mips, powerpc, s390{,x} and
> sparc - were subsequently built by the buildds in wheezy chroots.
>
> The kfreebsd-9 source package in wheezy has "Architecture: any all".
> That changed in unstable at some point last year, and the package was
> subsequently removed from the "sid" branch of P-a-s in May.
>
> However, the wheezy branch of P-a-s still contains:
>
> %kfreebsd-9: kfreebsd-i386 kfreebsd-amd64 i386 amd64 mipsel hurd-i386 # freebsd kernel 8.x
>
> This raises a couple of questions:
>
> - are the wheezy w-b databases filtered using the wheezy branch of
> P-a-s?
>
> - are the wheezy and wheezy-security w-b databases filtered using the
> _same_ branch of P-a-s?
Oh well, you just uncovered a bug that was not exposed widely because there's
a fallback P-a-s in the toplevel directory:
* All the triggers source triggers/common.
* common says at the top:
PAS_BASE="/srv/buildd.debian.org/web/quinn-diff"
PAS_FILE="$PAS_BASE/$SUITE/Packages-arch-specific"
* $SUITE is set subsequently but the file has already been source and hence
we get "/srv/buildd.debian.org/web/quinn-diff//Packages-arch-specific" for
all suites.
* This file exists and points to the sid checkout.
/srv/buildd.debian.org/web/quinn-diff/Packages-arch-specific -> sid/Packages-arch-specific
I'll fix that. Thanks.
Kind regards
Philipp Kern
Attachment:
signature.asc
Description: Digital signature