[Qa-jenkins-dev] chroot upgrade for armhf machines

[Mattia Rizzolo]

On Fri, Oct 02, 2015 at 12:01:43AM +0200, Santiago Vila wrote:
> Hello.
> 
> [ I'm not sure if this is a jenkins issue. Feel free to forward this to
> whoever may do something or just tell me the right address ].
> 
> Anyway: I see packages which fail to build reproducibly in armhf but
> not in amd64. An example is "boa-constructor", for which I did a QA
> upload some time ago.
> 
> https://reproducible.debian.net/rb-pkg/unstable/amd64/boa-constructor.html
> https://reproducible.debian.net/rb-pkg/unstable/armhf/boa-constructor.html
> 
> The source package is the same, the "torture" tests I think they are
> the same, but a diff between the buildinfo files show some differences:
> 
> ("before" file is amd64, "after" file is armhf)
> 
> [...]
> <  tar (= 1.28-2),
> ---
> >  tar (= 1.28-1),
> 
> Would be possible to update the chroots in the armhf machines?

all the chroots get updated every 3 hours '5 0,3,6,9,12,15,18,21 * * *'
in the maintenance jobs.

The reason of that difference is just that tar currently FTBFS:
https://buildd.debian.org/status/package.php?p=tar so the -2 can't be
installed on armhf :)


/me and Holger (with Holger being the main jenkins person) are here so
here it's fine for jenkins related issues ^^
But I believe that's "just" a reproducibly issue, an annoying one, if
it's there only on armhf...

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  http://mapreri.org                              : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/qa-jenkins-dev/attachments/20151001/06da1a69/attachment.sig>