Re: Gathering debug data from buildd's?
Am 31.07.2019 um 09:46 teilte Frédéric Bonnard mit: Hi Frédéric, >> I sent a request 3 days ago, still no response. Do I have to sign my >> E-Mail to get the request processed? > > No. It just takes a bit of time sometimes for people of the team that > do this manually but they usually answer, so you'll be informed when > it's done. > Hmm, due to the fact, that the wanna-build request needs to have a defined format I rather expected that they are processed automatically. Anyway there is a new asymptote package on its way through the NEW queue (due to package split). Let's see, what happening earlier. ;-) Hilmar -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Re: Gathering debug data from buildd's?
Hi Hilmar, > I sent a request 3 days ago, still no response. Do I have to sign my > E-Mail to get the request processed? No. It just takes a bit of time sometimes for people of the team that do this manually but they usually answer, so you'll be informed when it's done. F. pgp5yTbAlpDJ2.pgp Description: PGP signature
Re: Gathering debug data from buildd's?
Am 25.07.2019 um 16:39 teilte Frédéric Bonnard mit: > On Thu, 25 Jul 2019 15:35:31 +0200, Hilmar Preuße wrote: Hi, >> Is it possible to force a rebuild after updating build tools on the >> builders? > > yes, see last paragraph here : > https://release.debian.org/wanna-build.txt > I sent a request 3 days ago, still no response. Do I have to sign my E-Mail to get the request processed? Hilmar -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Re: Gathering debug data from buildd's?
On Thu, 25 Jul 2019 15:35:31 +0200, Hilmar Preuße wrote: > Am 25.07.2019 um 13:15 teilte Frédéric Bonnard mit: > > Hi *, > > > no I didn't reproduce the issue in a ppc64 vm even after 3 tries. > > > Maybe it was an gcc bug, which has been solved in the meantime? The > builder used gcc-8.3.0-7, meanwhile I (and probably you too) used > gcc-8.3.0-19. That's what I personally thought, a difference in the toolchain or some dep. > Is it possible to force a rebuild after updating build tools on the > builders? yes, see last paragraph here : https://release.debian.org/wanna-build.txt > > Hilmar > -- > #206401 http://counter.li.org > pgpngx1tvOh2Q.pgp Description: PGP signature
Re: Gathering debug data from buildd's?
Am 25.07.2019 um 13:15 teilte Frédéric Bonnard mit: Hi *, no I didn't reproduce the issue in a ppc64 vm even after 3 tries. Maybe it was an gcc bug, which has been solved in the meantime? The builder used gcc-8.3.0-7, meanwhile I (and probably you too) used gcc-8.3.0-19. Is it possible to force a rebuild after updating build tools on the builders? Hilmar -- #206401 http://counter.li.org
Re: Gathering debug data from buildd's?
Hi Hilmar, no I didn't reproduce the issue in a ppc64 vm even after 3 tries. F. On Wed, 24 Jul 2019 19:55:57 +0200, Hilmar Preuße wrote: > On 24.07.19 11:05, Frédéric Bonnard wrote: > > Hi Frédéric, > > > potentially recreate the issue in a ppc64 vm ? > > I may also try to reproduce in a vm I already have. > > > Were you successful in problem reproduction? > > Hilmar > -- > sigfault > #206401 http://counter.li.org > pgpE0iUk0wR90.pgp Description: PGP signature
Re: Gathering debug data from buildd's?
On 24.07.19 11:05, Frédéric Bonnard wrote: Hi Frédéric, > potentially recreate the issue in a ppc64 vm ? > I may also try to reproduce in a vm I already have. > Were you successful in problem reproduction? Hilmar -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Re: Gathering debug data from buildd's?
On 24.07.19 11:21, Andrey Rahmatullin wrote: > On Wed, Jul 24, 2019 at 11:13:59AM +0200, Hilmar Preuße wrote: Hi, >> Well, I don't have an ppc64 at hand and I'm not really willing to run >> every possible arch on my own hardware. If it would be quite easy to >> emulate an ppc64 on amd64, drop me a note. > > You can do that with with qemu-user-static, you can even make a > schroot and use sbuild. > So, I now have an ppc64 chroot, installed the BD's of asymptote and guess: (ppc64-sid)root@haka:~# ls -l *deb -rw-r--r-- 1 root root 13846732 Jul 24 17:09 asymptote-dbgsym_2.49-2_ppc64.deb -rw-r--r-- 1 root root 2984904 Jul 24 17:09 asymptote-doc_2.49-2_all.deb -rw-r--r-- 1 root root 1776592 Jul 24 17:08 asymptote_2.49-2_ppc64.deb ..I'm failing to reproduce the problem. As the build fails on the buildd always at the point I don't think we look at an random error. How to proceed? Hilmar -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Re: Gathering debug data from buildd's?
On 24.07.19 14:36, Andrey Rahmatullin wrote: Hi, > This exact command mostly worked for me. It failed later, with > "powerpc-utils depends on pmac-utils; however: Package pmac-utils is not > installed." > Correct: #927255 H. -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Re: Gathering debug data from buildd's?
On 24.07.19 14:36, Andrey Rahmatullin wrote: > On Wed, Jul 24, 2019 at 02:04:29PM +0200, Hilmar Preuße wrote: Hi, >> qemu-debootstrap --verbose --arch=ppc64 >> --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg sid ppc64>> >> http://ftp.de.debian.org/debian-ports/ > > This exact command mostly worked for me. It failed later, with > "powerpc-utils depends on pmac-utils; however: Package pmac-utils is > not installed." but the chroot is usable, I can chroot into it, after > which /usr/bin/qemu-ppc64-static is launched. > OK, one step further. Running that command inside an VirtualBox VM caused the error. Doing the same on the host (running still Debian oldstable) failed b/c package debian-ports-archive-keyring contains just expired keys and the signing key is not contained. I had to upgrade to the version from unstable. Now we are at I: Configuring libc-bin... I: Unpacking the base system... , which takes ages to execute. H. -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Re: Gathering debug data from buildd's?
On Wed, Jul 24, 2019 at 02:04:29PM +0200, Hilmar Preuße wrote: > qemu-debootstrap --verbose --arch=ppc64 > --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg sid ppc64 > http://ftp.de.debian.org/debian-ports/ This exact command mostly worked for me. It failed later, with "powerpc-utils depends on pmac-utils; however: Package pmac-utils is not installed." but the chroot is usable, I can chroot into it, after which /usr/bin/qemu-ppc64-static is launched. -- WBR, wRAR signature.asc Description: PGP signature
Re: Gathering debug data from buildd's?
On 24.07.19 13:06, Hilmar Preuße wrote: Hi, > I'll try further. > Next try: qemu-debootstrap --verbose --arch=ppc64 --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg sid ppc64 http://ftp.de.debian.org/debian-ports/ I: Running command: debootstrap --arch ppc64 --foreign --verbose --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg sid ppc64 http://ftp.de.debian.org/debian-ports/ I: Retrieving InRelease I: Checking Release signature I: Valid Release signature (key id 66571731B5A71F91C501F3FDDA1B2CEA81DCBC61) I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Extracting zlib1g... I: Running command: chroot ppc64 /debootstrap/debootstrap --second-stage chroot: failed to run command ‘/debootstrap/debootstrap’: Exec format error ?? Is qemu unable to execute the binaries? Hilmar -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Re: Gathering debug data from buildd's?
On 24.07.19 11:21, Andrey Rahmatullin wrote: > On Wed, Jul 24, 2019 at 11:13:59AM +0200, Hilmar Preuße wrote: Hi, >> Well, I don't have an ppc64 at hand and I'm not really willing to run >> every possible arch on my own hardware. If it would be quite easy to >> emulate an ppc64 on amd64, drop me a note. > > You can do that with with qemu-user-static, you can even make a > schroot and use sbuild. > OK, I found [1] (do you have a better introduction?). I fails at creating the new env, as ppc64 is not an release arch root@haka:/home/hille# qemu-debootstrap --arch=ppc64 sid ppc64 I: Running command: debootstrap --arch ppc64 --foreign sid ppc64 I: Retrieving InRelease I: Checking Release signature I: Valid Release signature (key id 0146DC6D4A0B2914BDED34DB648ACFD622F3D138) E: Invalid Release file, no entry for main/binary-ppc64/Packages Next try: root@haka:~# qemu-debootstrap --verbose --arch=ppc64 sid ppc64 http://ftp.de.debian.org/debian-ports/ I: Running command: debootstrap --arch ppc64 --foreign --verbose sid ppc64 http://ftp.de.debian.org/debian-ports/ I: Retrieving InRelease I: Checking Release signature E: Release signed by unknown key (key id DA1B2CEA81DCBC61) I'll try further. H. [1] http://logan.tw/posts/2017/01/21/introduction-to-qemu-debootstrap/ -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Re: Gathering debug data from buildd's?
Hi Hilmar, potentially recreate the issue in a ppc64 vm ? I may also try to reproduce in a vm I already have. Regards, F. On Wed, 24 Jul 2019 10:32:59 +0200, Hilmar Preuße wrote: > Hi, > > dumb question: since a few releases we have problems to build a package > on ppc64 [1]. The resulting binary segfaults when generating files. I > reported the problem upstream: they asked me for core dumps/gdb output. > > How to proceed: I could try to get access to a porter box through an RT > request (took last time 2 month to be processed). Are there other/faster > methods, e.g. gathering the data from the buildd itself? > > Thanks! > > Hilmar > > [1] https://buildd.debian.org/status/logs.php?pkg=asymptote=ppc64 > -- > sigfault > #206401 http://counter.li.org > pgp2fgkKeXIG5.pgp Description: PGP signature
Re: Gathering debug data from buildd's?
On Wed, Jul 24, 2019 at 11:13:59AM +0200, Hilmar Preuße wrote: > Well, I don't have an ppc64 at hand and I'm not really willing to run > every possible arch on my own hardware. If it would be quite easy to > emulate an ppc64 on amd64, drop me a note. You can do that with with qemu-user-static, you can even make a schroot and use sbuild. -- WBR, wRAR signature.asc Description: PGP signature
Re: Gathering debug data from buildd's?
On 24.07.19 11:05, Frédéric Bonnard wrote: Hi Frédéric, > potentially recreate the issue in a ppc64 vm ? > I may also try to reproduce in a vm I already have. > Well, I don't have an ppc64 at hand and I'm not really willing to run every possible arch on my own hardware. If it would be quite easy to emulate an ppc64 on amd64, drop me a note. Thanks! Hilmar -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Gathering debug data from buildd's?
Hi, dumb question: since a few releases we have problems to build a package on ppc64 [1]. The resulting binary segfaults when generating files. I reported the problem upstream: they asked me for core dumps/gdb output. How to proceed: I could try to get access to a porter box through an RT request (took last time 2 month to be processed). Are there other/faster methods, e.g. gathering the data from the buildd itself? Thanks! Hilmar [1] https://buildd.debian.org/status/logs.php?pkg=asymptote=ppc64 -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
