Re: buildds screwed?
Christian T. Steigies dixit:
>Thorsten mentioned something about a new toolchain which causes problems
>with the buildds. I think I got that... kullervo could not install debhelper
>because of libffi5, where it really wanted libffi6. After installing about
Should be done now, as I’m uploading glib2.0 right now.
>20 packages in the host system, I have the new debhelper, but in the buildd
>chroot, this should work automatically as the packages are available? How
>did you fix that for the other buildds?
Waiting for a bit, until the relevant packages are available.
>Maybe related to that, I was trying to build gcc-4.6, but I have unmet build
>dependencies (how can this ever be built from scratch with such a large list
>of build-depends?)
Please do not build gcc-4.6 manually, it wants patches.
I marked it specifically as Not-For-Us in wanna-build.
I’m working on gcc-4.{6,7,8} right now, additionally.
>According to debian-ports 0.16.1-2 is installed (but there is no log):
>http://buildd.debian-ports.org/status/package.php?p=cloog-ppl&suite=sid
That’s because I built it manually.
>Where can I get this package? Yes, I have unstable and unreleased on my
>sources.list.
I uploaded it to unstable late yesternight, so it will probably
show up now or later this day. Just like the glib2.0 I’m uploading
right now will end up being pooled by mini-dak in the run at 12:02 UTC
(14:02 CEST), which will then take a few hours to process the archive
to generate new Packages and Release{,.gpg} files, which means that,
at something like 18:00-20:00 CEST, it should be available.
I’ll be dayjobbing now.
HTH & HAND,
//mirabilos
--
Sorry, I’m annoyed today and you came by as an Arch user. These are the
perfect victims for any crime against humanity, like systemd, feminism
or social democracy.
-- Christoph Lohmann on dev@suckless.org
Reply to: