Hi,
On 21.01.24 22:48, Rebecca N. Palmer wrote:
Please give back pandas_1.5.3+dfsg-11 (unstable) on i386: that looks
like a rare random failure.
Does it? It looks like pandas is failing pretty often "randomly" on
i386. In that case[*] it'd be worth investigating. The main reason being
that
Hi Rebecca,
Rebecca N. Palmer (2023-08-18):
> numexpr 2.8.5-2 didn't actually fix enough of #1049326 to let pandas build.
> numexpr 2.8.5-3 should do so, but hasn't been built yet.
>
> (DMs can't use the self-service method.)
>
> dw pandas_1.5.3+dfsg-5 . ANY all . -m 'python3-numexpr (>=
Hi,
On 2023-06-21 21:06, Alexander Wirt wrote:
> Hi,
>
> to support bookworm backports we need the correspondending chroots. Could
> someone please take
> care about it?
wanna-build and the buildds already support bookworm-backports since the
release of bullseye. So there is nothing to be
Hi Jerome,
On Sat, Apr 23, 2022 at 11:45:00AM +0200, Jerome BENOIT wrote:
> Sollya 8.0+ds-1 is actually prevented from migration because
> it was not built on buildd for arch 64. I have to submit first
> this package to the NEW queue.
>
> gb sollya_8.0+ds-1 . amd64
"gb" is the wrong command,
Thanks so much!
Mattia Rizzolo writes:
> Done!
>
> On Sun, Oct 10, 2021 at 4:37 PM Camm Maguire wrote:
>>
>> Greetings, and thank you so much for your reply! Most happy to wait on
>> salsa-admin. In the meantime, I have committed a fix in gcl for this
>> issue -- would you please mind
Done!
On Sun, Oct 10, 2021 at 4:37 PM Camm Maguire wrote:
>
> Greetings, and thank you so much for your reply! Most happy to wait on
> salsa-admin. In the meantime, I have committed a fix in gcl for this
> issue -- would you please mind hitting the giveback button for me again
> once
Greetings, and thank you so much for your reply! Most happy to wait on
salsa-admin. In the meantime, I have committed a fix in gcl for this
issue -- would you please mind hitting the giveback button for me again
once gcl-2.6.12-104 is installed?
Take care,
Mattia Rizzolo writes:
> On Sun,
Mattia Rizzolo writes:
> I see you asked in #salsa on IRC 3 days ago, and I have to suppose you
> mailed them around the same time. Since you have been without salsa for
> more than 3 years already perhaps you can give the salsa admins more
> time to react?
Of course -- most happy to wait. I
On Sun, Oct 03, 2021 at 07:12:19PM -0400, Camm Maguire wrote:
> Mattia Rizzolo writes:
> > On Sun, Oct 03, 2021 at 01:49:04PM -0400, Camm Maguire wrote:
> >> Greetings, and thanks for your reply! When I do, I am asked for salsa
> >> login credentials. Apparently my automatically created account
On Sun, Oct 03, 2021 at 01:49:04PM -0400, Camm Maguire wrote:
> Greetings, and thanks for your reply! When I do, I am asked for salsa
> login credentials. Apparently my automatically created account was
> disabled due to non-use a year ago. I've requested activation on #salsa
> and
Greetings, and thanks for your reply! When I do, I am asked for salsa
login credentials. Apparently my automatically created account was
disabled due to non-use a year ago. I've requested activation on #salsa
and salsa-ad...@debian.org to no effect. Just tried registering fresh
with a new
Hello,
wf...@debian.org, le sam. 24 oct. 2020 17:36:05 +0200, a ecrit:
> The latest upload of libgphoto2 (2.5.26-2) should fix the unit test
> failure of gphoto2 on hurd-i386, please give back the failed build.
>
> gb gphoto2_2.5.26-1 . hurd-i386
Done so, thanks!
Samuel
Hello,
Shengjing Zhu, le dim. 22 mars 2020 02:22:31 +0800, a ecrit:
> It's been fixed in skalibs_2.9.2.0-3.
> Since it's in Failed state, I can't gb myself with the self-service.
>
> gb s6_2.9.1.0-1 . hurd-i386
Done so, thanks!
Samuel
On 16/03/2020 14:43, Frédéric Bonnard wrote:
> Hello,
>
> r-cran-roxygen2 failed to build recently on amd64, armhf, i386, ppc64el,
> ppc64 :
> https://buildd.debian.org/status/package.php?p=r-cran-roxygen2
> It didn't failed for me when I tried to reproduce the build today on
> ppc64el and
Hello,
Frédéric Bonnard (2020-03-06):
> rear's last build failed on i386 :
> https://buildd.debian.org/status/package.php?p=rear
> https://buildd.debian.org/status/fetch.php?pkg=rear=i386=2.5%2Bdfsg-1=1565612410=0
>
> I didn't manage to make it fail on my side.
>
> Please give back rear on
Philipp Kern writes:
> Looks like this already happened. FWIW with self-service giveback you
> need to URL encode the plus but I confirmed that this works.
Yes, looks all good now, thanks! As for not using self-service, it was
more a matter of having more or less forgotten that it was an
On 2/19/2020 8:40 PM, Aaron M. Ucko wrote:
> As such, could we please try for another automated build?
>
> gb ncbi-blast+_2.9.0-4 . mipsel
Looks like this already happened. FWIW with self-service giveback you
need to URL encode the plus but I confirmed that this works.
Kind regards
Philipp Kern
Hello Pino
El ds., 15 de febr. 2020, 10:35, Pino Toscano va escriure:
> Hi,
>
> please giveback kdevelop_4:5.5.0-2/mipsel: ld exited with a bizzarre
> issue, so maybe trying it again will work.
>
Please check whether this instructions work for you:
Hi Cyril,
On Wed, 29 Jan 2020 18:00:00 +0100, Cyril Brulebois wrote:
> Frédéric Bonnard (2020-01-29):
> > "testing migrations" on tracker (https://tracker.debian.org/pkg/comskip)
> > complains about :
> > "Not built on buildd: arch ppc64el binaries uploaded by
> > fre...@linux.vnet.ibm.com"
>
Hi,
Frédéric Bonnard (2020-01-29):
> "testing migrations" on tracker (https://tracker.debian.org/pkg/comskip)
> complains about :
> "Not built on buildd: arch ppc64el binaries uploaded by
> fre...@linux.vnet.ibm.com"
>
> And checking the buildd logs :
>
On Fri, 2019-12-27 at 11:54 +0100, Pino Toscano wrote:
> because of the update of libglvnd/mesa/qt5, some packages failed to
> build, and were given a Dep-Wait on the newer qtbase-opensource-src.
> The fixed version was already built and installed yesterday, however
> the packages are still stuck
>
> because of the update of libglvnd/mesa/qt5, some packages failed to
> build, and were given a Dep-Wait on the newer qtbase-opensource-src.
> The fixed version was already built and installed yesterday, however
> the packages are still stuck with the Dep-Wait. Can you please remove
> it for
On 12/4/2019 6:23 PM, Laurent Bigonville wrote:
> Apparently libphonenumber on x32 and sh4 is still depending on an old
> version of src:icu library (bin:libicu60) that doesn't exist in the
> archive anymore.
>
> Could you please binnmu it?
>
> nmu libphonenumber 7.1.0-5 . sh4 x32 . -m 'Rebuild
On 04/12/2019 14:41, Laurent Bigonville wrote:
> Hello,
>
> Could someone remove the extra-depends against libgnome-desktop-3-12 for
> gnome-software?
>
> bin:libgnome-desktop-3-12 doesn't exists in unstable anymore
>
> https://buildd.debian.org/status/package.php?p=gnome-software
Done.
On Sun, Oct 20, 2019 at 06:56:30PM +0200, Mattia Rizzolo wrote:
> So are you looking to give-back the experimental build? You never said
> so, and even the version you specified in the first email is the one in
> sid.
>
> Indeed the version in unstable has been retried 7 times now:
>
On Sun, Oct 20, 2019 at 02:19:07PM +0200, Robert Lemmen wrote:
> thanks for the give-back, but I didn't see any change. I also tried the
> self-service interface you helpfully pointed out, which seems to have
> worked (it says "Successfully given back the package"), yet I don't see
> any change on
hey folks,
On Fri, Oct 18, 2019 at 11:45:38PM +0200, Mattia Rizzolo wrote:
> On Fri, Oct 18, 2019 at 07:54:29PM +0200, Robert Lemmen wrote:
> > Could you please
> >
> > gb nqp_2019.07.1+dfsg-1 . mipsel
>
> done
> (https://lists.debian.org/debian-devel-announce/2019/08/msg3.html)
thanks
On Fri, Oct 18, 2019 at 07:54:29PM +0200, Robert Lemmen wrote:
> Could you please
>
> gb nqp_2019.07.1+dfsg-1 . mipsel
done
(https://lists.debian.org/debian-devel-announce/2019/08/msg3.html)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04
25.09.2019 17:58, Mattia Rizzolo пишет:
> On Wed, Sep 25, 2019 at 05:36:25PM +0300, Коля Гурьев wrote:
>> I discovered that if rlottie in the current state is build against
>> recent glibc (= 2.29-2), the rlottie package passes all its auto-tests.
>
> Interesting.
The build failure was caused by
On Wed, Sep 25, 2019 at 05:36:25PM +0300, Коля Гурьев wrote:
> I discovered that if rlottie in the current state is build against
> recent glibc (= 2.29-2), the rlottie package passes all its auto-tests.
Interesting.
> Please rebuild rlottie on mipsel and powerpc again.
>
> gb
On 2019-09-15 18:08, Jeremy Bicha wrote:
The latest gnome-games-app fails to build with vala 0.42 but vala 0.46
has now been uploaded to unstable, so gnome-games-app should build
fine now.
gb gnome-games-app 3.34.0-1 . ANY
References
---
Hey Cyril,
Thanks for the give back of amd64; it built just fine:
https://buildd.debian.org/status/package.php?p=abyss
Can we get the give backs for the rest of the archs?
Cheers,
On Mon, Aug 19, 2019 at 10:28 AM Cyril Brulebois wrote:
> Hi,
>
> Michael Crusoe (2019-08-19):
> > No one can
Hi,
Michael Crusoe (2019-08-19):
> Hey Cyril,
>
> Thanks for the give back of amd64; it built just fine:
> https://buildd.debian.org/status/package.php?p=abyss
>
> Can we get the give backs for the rest of the archs?
Thanks, done:
kibi@wuiet:~$ wb gb abyss . ANY -amd64
* abyss/hppa
Hi,
Michael Crusoe (2019-08-19):
> No one can replicate the build failure for abyss, not even Ubuntu, so
> hopefully it was just a transient error. Please give back abyss on all
> architectures
>
> gb abyss_2.2.2-1 . ANY
Seems to go further than the initial breakage in a local sid sbuild
On 2019-08-13 23:10 +0200, Jochen Sprickerhof wrote:
> Hello,
>
> There was a change in libclass-loader-dev that caused a number of ros- to
> FTBFS.
> Please give back:
>
> gb ros-image-common_1.11.13-3+b2 . amd64 arm64 armel armhf i386 mips mips64el
> mipsel ppc64el
> gb ros-urdf_1.13.1-1+b2
On 2019-08-12 12:28, Anthony Fok wrote:
> Hello,
>
> Please give back the latest golang-golang-x-tools
> (1:0.0~git20190809.6d4652c+ds-1) on mipsel which ended up building fine
> on mipsel porterbox eller.debian.org, so hopefully the build failure on buildd
> was a temporary glitch.
>
> gb
On 2019-08-12 17:59, Jochen Sprickerhof wrote:
> Hello,
>
> There was a change in libclass-loader-dev that caused ros-ros-comm to FTBFS on
> amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x hppa sh4.
> Please give it back:
>
> gb ros-ros-comm_1.14.3+ds1-5+b1 . amd64 arm64 armel
Le 06/08/2019 à 19:17, Andreas Metzler a écrit :
> please retry gnutls28 3.6.9-3 (sid) on i386. The error is not
> reproducible, a manual build in a local chroot succeeded.
>
> gb gnutls28_3.6.9-3 . i386
Done. It is getting in the way of some OCaml packages.
Cheers,
--
Stéphane
Hi Philipp,
Philipp Hübner (2019-08-06):
> please give back erlang-p1-mqtree 1.0.3-3 on mips,
> the previous upload (1.0.3-2) did build just fine,
> 1.0.3-3 was a no-change source-only upload.
>
> gb erlang-p1-mqtree 1.0.3-3 . mips
Done, thanks.
(Please note the version isn't needed; if
Am 03.08.19 um 22:19 schrieb Philipp Kern:
> Hey,
>
> On 7/25/2019 5:12 PM, Dr. Tobias Quathamer wrote:
>> the build of golang-1.12 has failed on mipsel with a segmentation
>> violation. Could this package be retried, please?
>>
>> gb golang-1.12_1.12.7-2 . mipsel
>
> by now it already fixed
Hey,
On 7/25/2019 5:12 PM, Dr. Tobias Quathamer wrote:
> the build of golang-1.12 has failed on mipsel with a segmentation violation.
> Could this package be retried, please?
>
> gb golang-1.12_1.12.7-2 . mipsel
by now it already fixed five times, unfortunately.
Kind regards
Philipp Kern
On 7/29/2019 11:24 AM, Patrick Matthäi wrote:
> please give back znc 1.7.4-4 on arm64. It looks like a temporary failure:
> https://buildd.debian.org/status/fetch.php?pkg=znc=arm64=1.7.4-4=1563879024=0
Looks like if anything it was cmake's fault. Done, thanks!
Kind regards
Philipp Kern
Hi Bill,
Bill Blough (2019-07-26):
> There was a change in file 5.37-1 that broke functionality in
> passwordsafe on arm64 arch. This change has been reverted as of file
> 5.37-5.
>
> Please give back passwordsafe on arm64 once file 5.37-1 is available on
> the buildd servers.
>
> gb
Hi,
Arturo Borrero Gonzalez (2019-07-23):
> nftables FTBFS on i386 because some weird issue in xsltproc:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932043
>
> However, I just tried locally the i386 build again and it was fine.
> I therefore ask for a rebuild on buildd.
>
> gb
Hi,
On Mon, Jul 8, 2019 at 8:25 PM Luca Boccassi wrote:
> A unit test is a bit flacky on very slow machines, it very rarely fails
> so it's hard to reproduce locally, haven't been able to so far on my
> machines nor on a mips porterbox.
> Please give it a good kicking on mipsel, it should then
On 19/06/2019 08:35, Mike Hommey wrote:
> Somehow failed with a weird GNU make error.
>
> gb firefox_67.0.3-1 . all
Given back.
Emilio
Hi,
On 5/31/2019 7:30 AM, Andreas Metzler wrote:
> please retry gnutls28 3.6.7-3 (sid) on armel. The error is not
> reproducible, a manual build on abel succeeded.
>
> gb gnutls28_3.6.7-3 . armel
done.
Kind regards and thanks
Philipp Kern
On 4/24/2019 1:48 PM, Mo Zhou wrote:
> Please rebuild slepc/experimental on m68k and sh4.
> The two architectures failed the build due to a bug in the blis
> package. Now I have fixed the blis package in experimental and
> I'd like to see whether the problem is really fixed.
>
> The build result
Hi,
Nicolas Boulenguez (2019-04-27):
> Exadrums and libexadrums are two distinct source packages (despite
> similar version numbers for now). As the names suggest, the former
> links with the latter. It is the only consumer for now.
> Both are in experimental because they have been introduced
Ok, thanks Emilio for letting know !
F.
On Fri, 22 Mar 2019 13:18:12 +0100, Emilio Pozuelo Monfort
wrote:
> On 20/03/2019 15:52, Frédéric Bonnard wrote:
> > Hello,
> >
> > openjdk-12's last build failed on ppc64el :
> > https://buildd.debian.org/status/package.php?p=openjdk-12
> >
On 20/03/2019 15:52, Frédéric Bonnard wrote:
> Hello,
>
> openjdk-12's last build failed on ppc64el :
> https://buildd.debian.org/status/package.php?p=openjdk-12
> https://buildd.debian.org/status/fetch.php?pkg=openjdk-12=ppc64el=12%7E33-1=1551181149=0
>
> I didn't manage to make it fail on my
On 3/12/2019 11:29 AM, Martín Ferrari wrote:
> Mtail failed to build on armel a few days ago, but it seems a transient
> failure (builds fine on abel). Sadly I only realised this today, could
> you give it back please?
Done.
Kind regards
Philipp Kern
On 3/1/2019 5:55 PM, Martín Ferrari wrote:
> THe build for prometheus-alertmanager failed on ppc64el, but I can build
> it fine on plummer, so I think it was a transient failure. Could you
> give it back please?
Done.
Kind regards
Philipp Kern
Hey,
On 2/21/2019 2:23 AM, Stefano Rivera wrote:
> I think I've got on top of pypy's build timeout issues, but we recently
> got a stuck build on ppc64el (usually one of the fastest architectures,
> rarely timing out). So probably a bug that caused something to lock-up
> rather than a timeout
On 2/14/2019 6:30 PM, Sandro Knauß wrote:
> thanks for the gb for libkgapi. Now it failed at kf5-messagelib 4:18.08.3-1
> because of failing tests, again. I rebuild the same package on
> eller.d.o(porterbox) and the build was successfully. That
> means that the test are a little bit flaky.
Am Mittwoch, den 13.02.2019, 15:27 +0100 schrieb Daniel Leidert:
> gb shelxle_1.0.949-1 . kfreebsd-i386
Please defer this request. I just saw, that the fixed version of QT5 is
currently building on mipsel too and I'll probably have to do a -2
upload of shelxle anyway.
Thanks and regards, Daniel
On 2/6/2019 3:36 PM, Sandro Knauß wrote:
> gb libkgapi_18.08.3-1 . mipsel . -m 'rerun to work with flaky tests.'
Done.
Kind regards and thanks
Philipp Kern
On 23/01/2019 18:56, Jeremy Bicha wrote:
> One of gnome-builder's build tests too long on mips. I increased the
> timeout for that test to 650 seconds and generally that test has only
> been taking about 50 seconds since then. I could ask upstream to bump
> the timeout more but I think 650 is
Hi Laurent,
Laurent Bigonville (2019-01-16):
> I just tried to rebuild libosinfo on mips64el and the test is
> succeeding on the porter box.
>
> Could you please try to give it back on mips64el but also on armhf and
> mipsel?
>
> gb libosinfo_1.2.0-1 . mips64el armhf mipsel
Done, thank you.
Hi,
Dr. Tobias Quathamer (2019-01-12):
> golang-1.12 has FTBFS on mipsel. It seems to have been caught by a
> brittle test, so a retry of the build will hopefully succeed.
>
> gb golang-1.12_1.12~beta2-1 . mipsel
Done, thanks.
Cheers,
--
Cyril Brulebois (k...@debian.org)
On Tue, Jan 01, 2019 at 08:35:40PM +0100, Kurt Roeckx wrote:
> On Tue, Jan 01, 2019 at 04:59:17PM +0100, Thorsten Alteholz wrote:
> > Hi,
> >
> > the mipsel buildd marked meep as "unsatisfiable Build-Depends(-Arch) on
> > mipsel: mpb-dev".
> > As mpb-dev is finally available on mipsel, please
On Tue, Jan 01, 2019 at 04:59:17PM +0100, Thorsten Alteholz wrote:
> Hi,
>
> the mipsel buildd marked meep as "unsatisfiable Build-Depends(-Arch) on
> mipsel: mpb-dev".
> As mpb-dev is finally available on mipsel, please give meep back:
>
>gb meep_1.7.0-2 . mipsel
Build-Depends are checked
Hi,
very belated reply, I know. Sorry about that.
On 16/12/2018 21:41, Dr. Tobias Quathamer wrote:
the builds of golang-1.11 have failed on mips and mipsel. Could you
please give those packages back? The previous version built fine, and
the code changed does not explain the build failure.
On 24/12/2018 02:54, Mo Zhou wrote:
Thanks for the hint. BTW the mips failure looks temporary and similar to
the armel one, could you please also give-back it on mips?
gb opencv_3.4.4+dfsg-1~exp1 . mips . experimental
Done.
Kind regards and thanks
Philipp Kern
Hi,
On Fri, Dec 21, 2018 at 09:31:08AM +0100, Emilio Pozuelo Monfort wrote:
> On 21/12/2018 04:23, Mo Zhou wrote:
> > Hello,
> >
> > Please rebuild opencv 3.4.4 on armel since I cannot reproduce the
> > problem that buildd encountered and the problem is still unknown.
> >
> > gb
On 21/12/2018 04:23, Mo Zhou wrote:
> Hello,
>
> Please rebuild opencv 3.4.4 on armel since I cannot reproduce the
> problem that buildd encountered and the problem is still unknown.
>
> gb opencv_3.4.4+dfsg-1~exp1 . armel
That command lacks a distribution argument at the end (the default one
On 20/12/2018 14:12, peter green wrote:
> please give back pyside, it failed to build due to a missing file,
>
>> CMake Error at
>> /usr/lib/x86_64-linux-gnu/cmake/Shiboken-1.2.2/ShibokenConfig.cmake:5
>> (include):
>> include could not find load file:
>>
>>
>>
On 19/12/2018 16:34, Martín Ferrari wrote:
> Hi,
>
> prometheus-node-exporter 0.17.0 failed on s390x due to a bug in a
> dependency, which I have fixed and uploaded (#916236). Can you
> please give it back?
Given back.
Emilio
On 07/12/2018 20:45, Dr. Tobias Quathamer wrote:
> Am 04.12.2018 um 12:28 schrieb Emilio Pozuelo Monfort:
>> On 03/12/2018 23:10, Dr. Tobias Quathamer wrote:
>>> Hi,
>>>
>>> the build of golang-1.11 has failed on mipsel, most likely due to a
>>> flaky test. Could you please retry the package?
>>>
Am 04.12.2018 um 12:28 schrieb Emilio Pozuelo Monfort:
> On 03/12/2018 23:10, Dr. Tobias Quathamer wrote:
>> Hi,
>>
>> the build of golang-1.11 has failed on mipsel, most likely due to a
>> flaky test. Could you please retry the package?
>>
>> gb golang-1.11_1.11.2-2 . mipsel
>
> Given back. It
On 03/12/2018 23:10, Dr. Tobias Quathamer wrote:
> Hi,
>
> the build of golang-1.11 has failed on mipsel, most likely due to a
> flaky test. Could you please retry the package?
>
> gb golang-1.11_1.11.2-2 . mipsel
Given back. It may take a while for the build to be tried as the mipsel queue is
On 03/12/2018 09:26, Matteo F. Vescovi wrote:
> Hi!
>
> Failure on mips64el for blender seems to be due to some issues on the
> buildd machine on the compilation. A test made on a qemu VM succeeded.
>
> So, please give back on that only failing architecture:
>
> gb blender_2.79.b+dfsg0-5 .
On 28/11/2018 10:57, wf...@niif.hu wrote:
> Hello,
>
> There was a bug in libxml-security-c20 that case xmltooling to FTBFS on
> arm64 and maybel armel. This has been fixed in libxml-security-c20
> 2.0.2-3. Please give back xmltooling on arm64 and armel.
>
> gb xmltooling_3.0.2-2 . arm64 armel
Am 24.11.2018 um 15:04 schrieb Markus Koschany:
> There was a bug in mesa that caused brainparty to FTBFS on mips64el.
>
> https://bugs.debian.org/914167
>
> This has been fixed in mesa 18.2.5-2. Please give
> back brainparty on mips64el.
>
> gb brainparty_0.61+dfsg-4 . mips64el
Done.
Kind
Am 24.11.2018 um 13:20 schrieb Pino Toscano:
> please giveback krunner_5.51.0-2/mipsel, as qtbase-opensource-src
> 5.11.2+dfsg-7 (which fixes a build regression in other packages) was
> just built, and installed on mipsel too.
Done.
Kind regards and thanks
Philipp Kern
Am 23.11.2018 um 21:27 schrieb Johannes Schauer:
> Quoting Johannes Schauer (2018-11-23 21:05:52)
>> after the upload of Python 3.7, python-pygraphviz experienced bug #914378
>> which
>> made botch FTBFS. The bug is now fixed by a new upstream release of
>> python-pygraphviz. Thus, please:
>>
>>
Quoting Johannes Schauer (2018-11-23 21:05:52)
> after the upload of Python 3.7, python-pygraphviz experienced bug #914378
> which
> made botch FTBFS. The bug is now fixed by a new upstream release of
> python-pygraphviz. Thus, please:
>
>gb botch_0.21-8 . ANY
>
> Thanks!
Because
Am Sa., 10. Nov. 2018 um 12:01 Uhr schrieb Philipp Kern :
>
> On 24.10.2018 15:44, Jeremy Bicha wrote:
> > Please give back appstream-generator. The meson bug has been fixed for
> > a while now.
> >
> > https://buildd.debian.org/status/package.php?p=appstream-generator
>
> Apparently this wasn't
On 04.11.2018 13:52, Andrej Shadura wrote:
> Hello,
>
> libguess failed to build on a few architectures due to what appears to
> have been an issue with the build environment. Please give it back.
> Thanks.
>
> gbp libguess_1.2-2 . mips mipsel powerpc powerpcse
I don't think that's true given
On 24.10.2018 15:44, Jeremy Bicha wrote:
> Please give back appstream-generator. The meson bug has been fixed for
> a while now.
>
> https://buildd.debian.org/status/package.php?p=appstream-generator
Apparently this wasn't done yet, so I did that now. My apologies for the
delay.
Kind regards
On 2018-10-23 23:06 +0200, Jochen Sprickerhof wrote:
> Hello,
>
> There was a bug in libassimp4 that caused kido to FTBFS on armhf (#911484).
> This has been fixed in libassimp4 4.1.0~dfsg-5. Please give back kido on
> armhf. Note that libassimp4 4.1.0~dfsg-5 not build yet, so add a dep-wait.
>
Hi,
On 10/21/18 8:30 PM, Jeremy Bicha wrote:
On Sun, Oct 21, 2018 at 1:36 PM Wookey wrote:
It's been marked 'failed' on hurd-i386, but seems to have the same
fault as all the other arches. Should that be given-back too?
Yes please. Thanks!
Done.
Ivo
Hi,
On 10/21/18 10:26 PM, Ole Streicher wrote:
There was a bug in skimage that caused sunpy to FTBFS on all 32 bit
architectures. This has been fixed in 0.14.1-2. Please give
back sunpy on armel, armhf, i386, mips, and mipsel.
gb sunpy_0.9.3-1 . armel armhf i386 mips mipsel
Given back.
On Sun, Oct 21, 2018 at 1:36 PM Wookey wrote:
> It's been marked 'failed' on hurd-i386, but seems to have the same
> fault as all the other arches. Should that be given-back too?
Yes please. Thanks!
Jeremy
Hi,
On 10/21/18 12:44 AM, Jochen Sprickerhof wrote:
There was a bug in libopenni0 that caused python-pcl to FTBFS on all
armhf architectures. This has been fixed in libopenni0 1.5.4.0+dfsg-2.
Please give back libopenni0 on armhf.
gb python-pcl_0.3.0~rc1+dfsg-4 . armhf
Given back.
Ivo
On 2018-10-20 09:58 -0400, Jeremy Bicha wrote:
> meson has fixed its regression with its 0.48.1-1 relase (in Testing as
> of today).
>
> Therefore, please give back file-roller on all architectures where it
> failed to build:
>
> https://buildd.debian.org/status/package.php?p=file-roller
OK
On 06/10/2018 15:39, Tom Lee wrote:
> Hello,
>
> Requesting a giveback of a failed mips64el build of hiredis 0.14.0-1. I
> suspect a possible flakey test, but looking for another data point before I
> go through the hassle of porterbox access requests etc.
>
> gb hiredis_0.14.0-1 . mips64el
Hi Frédéric,
On 10/03/2018 08:44 AM, Frédéric Bonnard wrote:
> Hello,
>
> nomad's last build failed on ppc64el.
> https://buildd.debian.org/status/fetch.php?pkg=nomad=ppc64el=0.8.6%2Bdfsg1-1=1538008929=0
>
> I didn't manage to make it fail on my side.
>
> Please give back nomad on ppc64el.
>
This was done. smcv also did some diagnosis of the issue in
https://bugs.debian.org/909150
Thanks,
Jeremy Bicha
On 2018-09-16 17:16 -0400, Jeremy Bicha wrote:
> Today's cogl update fixed a logic error in dh_auto_test. So the tests
> are being run now but weren't being run before.
>
> Please retry armel. If it fails again, I'm considering disabling the
> tests on that architecture. The tests don't pass
Hi!
> On Sep 12, 2018, at 2:31 PM, Julien Cristau wrote:
>
> [cc += debian-arm]
>
>> On 09/09/2018 11:15 PM, Pino Toscano wrote:
>> Hi,
>>
>> the 5.49.0-2build of ktexteditor failed because two unit tests
>> SIGBUS'ed. OTOH, armel worked, and my tests on the abel armhf porterbox
>> worked
[cc += debian-arm]
On 09/09/2018 11:15 PM, Pino Toscano wrote:
> Hi,
>
> the 5.49.0-2 build of ktexteditor failed because two unit tests
> SIGBUS'ed. OTOH, armel worked, and my tests on the abel armhf porterbox
> worked fine. (While on harris GCC ICEd really a lot, and I gave up
> after the 4
On 09/12/2018 03:05 AM, Jeremy Bicha wrote:
> On Tue, Sep 11, 2018 at 6:36 PM Philipp Kern wrote:
>> On 10.09.2018 12:27, Jeremy Bicha wrote:
>>> There was a bug in libsoup2.4 that caused geary to FTBFS on several
>>> architectures. Please give it back there.
>>>
>>> And let's try libsoup2.4
On Tue, Sep 11, 2018 at 6:36 PM Philipp Kern wrote:
> On 10.09.2018 12:27, Jeremy Bicha wrote:
> > There was a bug in libsoup2.4 that caused geary to FTBFS on several
> > architectures. Please give it back there.
> >
> > And let's try libsoup2.4 again on alpha since the previous version built.
>
On 10.09.2018 12:27, Jeremy Bicha wrote:
> There was a bug in libsoup2.4 that caused geary to FTBFS on several
> architectures. Please give it back there.
>
> And let's try libsoup2.4 again on alpha since the previous version built.
>
> dw geary_0.12.4-1 . alpha . -m 'libsoup2.4 (>= 2.64.0-2)'
>
On Tue, Aug 28, 2018 at 09:26:33AM +0200, Mattias Ellert wrote:
> The fix was a simple one-line patch changing the size of the key
> generated for the test.
Why don't you pre-generate the key?
Bastian
--
Only a fool fights in a burning house.
-- Kank the Klingon, "Day of the
Hi,
On 18/07/18 13:26, Matteo F. Vescovi wrote:
> Hi!
>
> Failure on mips64el for blender seems to be due to some issues on the
> buildd machine on the compilation. A test made on a qemu VM succeeded.
>
> So, please give back on that only failing architecture:
>
> gb blender_2.79.b+dfsg0-2 .
On 09/07/18 03:02, Scott Talbert wrote:
> Hello,
>
> There was a bug in sip4 that caused wxpython4.0 to FTBFS on all
> architectures.
> This has been fixed in sip4 4.19.12+dfsg-1. Please give back wxpython4.0 on
> all
> architectures.
>
> gb wxpython4.0_4.0.1+dfsg-5 . *
That wildcard is
On 28/06/18 23:04, Jochen Sprickerhof wrote:
> Dear release team,
>
> there was an update in catkin that caused ros-common-msgs to generate
> different
> cmake macros. This has not been picked up on amd64 due to transitioning
> through
> new and being build before that change.
> Please give
Hi,
On 2018-06-24 17:05, Nicolas Boulenguez wrote:
libasis2018-dev/2017-3 is buggy because it depends on gnat/gcc-8 but
relies on headers describing gnat/gcc-7 internal structures.
This is fixed in libasis2018-dev/2018-1.
adacontrol/1.19r10-3
* is built with 2018-1 on ppc64 and s390x.
* has
1 - 100 of 726 matches
Mail list logo
