sparc64 buildd state wrt. Perl transition (was: Re: Results of the porter roll call)
Hi,
Michael Cree wrote:
> On Thu, Oct 03, 2013 at 01:06:01AM +0200, Axel Beckert wrote:
> > Julien Cristau wrote:
> > > On Wed, Oct 2, 2013 at 11:44:44 +0200, Axel Beckert wrote:
> > > > Yesterday I tried to setup a sparc64 chroot on a second disc in one of
> > > > my Sparcs, but the currently documented way[1] to do so failed[2] due
> > > > to outdated packages. On a first glance it looks like missing BinNMUs
> > > > for the Perl 5.14 to Perl 5.18 transition.
> > >
> > > Part of the porter's job is to take care of that kind of things.
> >
> > Definitely.
> >
> > > If that's not happening for sparc64 because nobody's actually taking
> > > care of the port, I don't see it as a viable candidate for the
> > > archive...
> >
> > *nod* One of the reasons why I'm trying to improve that...
>
> Looking at a recent build log on sparc64 it is obvious the chroots on at
> least one of the sparc64 buildds have not even been upgraded to have perl
> 5.18. So that one (and presumably the rest) is building packages against
> the old (no longer available) perl!
That explains a lot. Thanks for checking.
I'd also volunteer as sparc64 buildd admin as there seems to be some
need for it. Cc'ing admin@debian-ports.org for that.
I though have no experience as buildd admin so far and hence are not
sure how the actual duties of a buildd admin look like.
> It might be possible to set up a sparc64 chroot by bootstrapping from
> snapshot.d.o at a date a bit before the upload of perl 5.18, and then
> upgrading as much of the chroot as possible to as recently as possible
> from debian-ports
I actually was able to rebuild all Perl modules I needed in my (in the
meanwhile working) sparc64 chroot.
> but even if that is done on a local machine and one rebuilds the
> relevant perl packages to get a fully upgradeable chroot one is
> still faced with buildds at debian-ports that will build packages
> against an obsolete perl.
Correct. I'll try to take care of that issue.
> So I would suggest locating the buildd admins. The following lists a
> useful email address for that purpose:
> http://www.debian-ports.org/contacts
Thanks for that pointer! I was already looking for such contacts, but
apparently at the wrong place, namely at
http://wiki.debian.org/Sparc64 -- I've added this information to the
wiki now.
Cc'ing sparc64@debian-ports.org and therewith contacting the sparc64
buildd maintainers, too.
I'm also dropping debian-devel@lists.debian.org and setting Reply-To
to debian-sparc@lists.debian.org to not clutter the other lists while
working on these sparc-specific issues.
Regards, Axel
--
,''`. | Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
Reply to: