Re: Please give back pandas on i386

[Philipp Kern]

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 updates/patches need to be possible without a lot of give-backs.


Does the test generate random inputs? Can you reproduce these random 
build failures locally by running the build for i386 a couple of times? 
(At least this isn't some fringe architecture.)


Kind regards
Philipp Kern

[*] I could not easily see if there were almost always follow-up fixes. 
I went off https://buildd.debian.org/status/logs.php?pkg=pandas=i386.

Re: Please give back pandas, dep-wait on numexpr #1049326

[Cyril Brulebois]

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 (>= 2.8.5-3)'

Done.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Please create chroots for bookworm-backports

[Aurelien Jarno]

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 done on the wb-team side.
Sorry for not seeing the mail earlier.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net


signature.asc
Description: PGP signature

Re: please give back sollya on amd64

[Mattia Rizzolo]

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, that's only used for failed builds.  You'd
need a full binNMU instead.

Either way, that would be useless, because then you'd still be stuck
with the maintainer uploaded arc:all binary.

So you need to do a full sourceful upload instead, just upload a -2.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Re: Please give back acl2 on armhf

[Camm Maguire]

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 hitting the giveback button for me again
>> once gcl-2.6.12-104 is installed?
>>
>> Take care,
>>
>> Mattia Rizzolo  writes:
>>
>> > 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 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 username and email address, and am awaiting administrator
>> >> >> confirmation.  Am I overlooking anything?
>> >> >
>> >> > AFAIK it would anyway require to be a DD, so it wouldn't work.
>> >>
>> >> I am a DD, but it does not appear I have a working salsa login.  I would
>> >> like to get that working so I could give back packages without bothering
>> >> anyone.  Might you be able to advise me on that?
>> >
>> > Oh, sorry.  I did a lookup on your email address, but didn't yield any
>> > result because that address is not in a uid of your gpg key, nor was it
>> > used "recently" in any upload.
>> >
>> > Anyway, salsa accounts of DDs have been disabled for all those DDs that
>> > didn't activate theirs within 2 years after salsa was created.
>> > Only the salsa admins can re-enable those accounts, and ttbomk, the way
>> > is to mail salsa-ad...@debian.org like you said you already did.
>> > Registering a new account won't probably help anyway, since your @d.o
>> > address is tied to the deactivated one, and moving the address still
>> > require admin intervention which then leads to the same situation of
>> > waiting on them (furthermore the "DD status" of a salsa account actually
>> > comes from nm.debian.org and their linking.  re-linking your nm.d.o
>> > account to a new salsa account has some rought edges that can also
>> > require a nm.d.o admin ("Front Desk") to manually set it up; so you'll
>> > then still have to nudge plenty of people to get it done).
>> >
>> >
>> > 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?
>>
>> --
>> Camm Maguirec...@maguirefamily.org
>> ==
>> "The earth is but one country, and mankind its citizens."  --  Baha'u'llah

-- 
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

Re: Please give back acl2 on armhf

[Mattia Rizzolo]

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 gcl-2.6.12-104 is installed?
>
> Take care,
>
> Mattia Rizzolo  writes:
>
> > 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 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 username and email address, and am awaiting administrator
> >> >> confirmation.  Am I overlooking anything?
> >> >
> >> > AFAIK it would anyway require to be a DD, so it wouldn't work.
> >>
> >> I am a DD, but it does not appear I have a working salsa login.  I would
> >> like to get that working so I could give back packages without bothering
> >> anyone.  Might you be able to advise me on that?
> >
> > Oh, sorry.  I did a lookup on your email address, but didn't yield any
> > result because that address is not in a uid of your gpg key, nor was it
> > used "recently" in any upload.
> >
> > Anyway, salsa accounts of DDs have been disabled for all those DDs that
> > didn't activate theirs within 2 years after salsa was created.
> > Only the salsa admins can re-enable those accounts, and ttbomk, the way
> > is to mail salsa-ad...@debian.org like you said you already did.
> > Registering a new account won't probably help anyway, since your @d.o
> > address is tied to the deactivated one, and moving the address still
> > require admin intervention which then leads to the same situation of
> > waiting on them (furthermore the "DD status" of a salsa account actually
> > comes from nm.debian.org and their linking.  re-linking your nm.d.o
> > account to a new salsa account has some rought edges that can also
> > require a nm.d.o admin ("Front Desk") to manually set it up; so you'll
> > then still have to nudge plenty of people to get it done).
> >
> >
> > 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?
>
> --
> Camm Maguirec...@maguirefamily.org
> ==
> "The earth is but one country, and mankind its citizens."  --  Baha'u'llah



-- 
regards,
Mattia Rizzolo

GPG Key: 4096R/B9444540 http://goo.gl/I8TMB
more about me: http://mapreri.org
Launchpad User: https://launchpad.net/~mapreri
Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo

Re: Please give back acl2 on armhf

[Camm Maguire]

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, 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 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 username and email address, and am awaiting administrator
>> >> confirmation.  Am I overlooking anything?
>> >
>> > AFAIK it would anyway require to be a DD, so it wouldn't work.
>> 
>> I am a DD, but it does not appear I have a working salsa login.  I would
>> like to get that working so I could give back packages without bothering
>> anyone.  Might you be able to advise me on that?
>
> Oh, sorry.  I did a lookup on your email address, but didn't yield any
> result because that address is not in a uid of your gpg key, nor was it
> used "recently" in any upload.
>
> Anyway, salsa accounts of DDs have been disabled for all those DDs that
> didn't activate theirs within 2 years after salsa was created.
> Only the salsa admins can re-enable those accounts, and ttbomk, the way
> is to mail salsa-ad...@debian.org like you said you already did.
> Registering a new account won't probably help anyway, since your @d.o
> address is tied to the deactivated one, and moving the address still
> require admin intervention which then leads to the same situation of
> waiting on them (furthermore the "DD status" of a salsa account actually
> comes from nm.debian.org and their linking.  re-linking your nm.d.o
> account to a new salsa account has some rought edges that can also
> require a nm.d.o admin ("Front Desk") to manually set it up; so you'll
> then still have to nudge plenty of people to get it done).
>
>
> 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?

-- 
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

Re: Please give back acl2 on armhf

[Camm Maguire]

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 was just unsure if the protocol
specified was still live.

Take care, and thanks so much!
-- 
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

Re: Please give back acl2 on armhf

[Mattia Rizzolo]

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 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 username and email address, and am awaiting administrator
> >> confirmation.  Am I overlooking anything?
> >
> > AFAIK it would anyway require to be a DD, so it wouldn't work.
> 
> I am a DD, but it does not appear I have a working salsa login.  I would
> like to get that working so I could give back packages without bothering
> anyone.  Might you be able to advise me on that?

Oh, sorry.  I did a lookup on your email address, but didn't yield any
result because that address is not in a uid of your gpg key, nor was it
used "recently" in any upload.

Anyway, salsa accounts of DDs have been disabled for all those DDs that
didn't activate theirs within 2 years after salsa was created.
Only the salsa admins can re-enable those accounts, and ttbomk, the way
is to mail salsa-ad...@debian.org like you said you already did.
Registering a new account won't probably help anyway, since your @d.o
address is tied to the deactivated one, and moving the address still
require admin intervention which then leads to the same situation of
waiting on them (furthermore the "DD status" of a salsa account actually
comes from nm.debian.org and their linking.  re-linking your nm.d.o
account to a new salsa account has some rought edges that can also
require a nm.d.o admin ("Front Desk") to manually set it up; so you'll
then still have to nudge plenty of people to get it done).


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?


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Re: Please give back acl2 on armhf

[Mattia Rizzolo]

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 salsa-ad...@debian.org to no effect.  Just tried registering fresh
> with a new username and email address, and am awaiting administrator
> confirmation.  Am I overlooking anything?

AFAIK it would anyway require to be a DD, so it wouldn't work.

At any rate, I gave it back 4 hours ago, and the second build already
completed and failed, is that enough for you?

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Re: Please give back acl2 on armhf

[Camm Maguire]

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 username and email address, and am awaiting administrator
confirmation.  Am I overlooking anything?

Take care,

Philipp Kern  writes:

> Hi,
>
> On 03.10.21 15:20, Camm Maguire wrote:
>> Greetings!  I need another log to triangulate a rare unreproducible
>> build failure.
>
> Have you tried the link on
> https://buildd.debian.org/status/package.php?p=acl2 already?
>
> Kind regards
> Philipp Kern
>
>
>

-- 
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

Re: Please give back gphoto2 on hurd-i386

[Samuel Thibault]

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

Re: Please give back s6 on hurd-i386

[Samuel Thibault]

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

Re: Please give back r-cran-roxygen2

[Emilio Pozuelo Monfort]

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 amd64. As the error was the same on all the failing
> architectures, I guess the issue has been fixed on all of these.
> 
> Please give back r-cran-roxygen2
> 
> r-cran-roxygen2 7.1.0-1 . amd64 armhf i386 ppc64el ppc64 . unstable

This got fixed through a sourceful upload.

For the future, note that you can now give back packages yourself, see:

https://debblog.philkern.de/2019/08/alpha-self-service-buildd-givebacks.html

Cheers,
Emilio

Re: Please give back rear on i386

[Cyril Brulebois]

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 i386 .
> 
> gb rear_2.5+dfsg-1 . i386 . unstable -m 'Rebuild against unknown fixed issue'

Built fine locally as well, given back (without any message).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Please give back ncbi-blast+ on mipsel and ppc64

[Aaron M. Ucko]

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 option
nowadays, and then proceeding to overlook the brief directions on using
it.  Sorry for the noise.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Re: Please give back ncbi-blast+ on mipsel and ppc64

[Philipp Kern]

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

Re: Please gb kdevelop/mipsel

[Héctor Orón Martínez]

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:

https://debblog.philkern.de/2019/08/alpha-self-service-buildd-givebacks.html?m=1

Regards


> Thanks,
> --
> Pino Toscano

Re: Please give back comskip on ppc64el

[Frédéric Bonnard]

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"
> > 
> > And checking the buildd logs :
> > https://buildd.debian.org/status/package.php?p=comskip
> > comskip on ppc64el is marked "Installed" but there is no log.
> > I thought the "testing migrations" wants some logs there and forcing
> > rebuilding may help. Let me know if I'm wrong.
> > 
> > Please give back comskip on ppc64el .
> > 
> > gb 0.82.009+ds.1-1 . ppc64el . unstable -m 'Rebuild to pass testing 
> > migrations checks'
> > 
> > Thanks.
> 
> A give back means retrying a failed build, which isn't the case here;
> you want a binNMU instead, which is usually handled by the release team
> instead.

:) thanks for explaining

> Hopefully this will do the trick:
> 
> kibi@wuiet:~$ wb nmu comskip . ppc64el . unstable . -m "Rebuild on 
> buildd."
> 
> (But it's been a while since I last did that, so please monitor and poke
> me back if needed.)

excellent, that did the trick : comskip built and migrated to testing.
Thanks again for taking care of this !

F.


pgpZ5zn7vUMXa.pgp
Description: PGP signature

Re: Please give back comskip on ppc64el

[Cyril Brulebois]

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 :
> https://buildd.debian.org/status/package.php?p=comskip
> comskip on ppc64el is marked "Installed" but there is no log.
> I thought the "testing migrations" wants some logs there and forcing
> rebuilding may help. Let me know if I'm wrong.
> 
> Please give back comskip on ppc64el .
> 
> gb 0.82.009+ds.1-1 . ppc64el . unstable -m 'Rebuild to pass testing 
> migrations checks'
> 
> Thanks.

A give back means retrying a failed build, which isn't the case here;
you want a binNMU instead, which is usually handled by the release team
instead.

Hopefully this will do the trick:

kibi@wuiet:~$ wb nmu comskip . ppc64el . unstable . -m "Rebuild on buildd."

(But it's been a while since I last did that, so please monitor and poke
me back if needed.)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Please remove extra Dep-Wait on mipsel

[Adam D. Barratt]

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 with the Dep-Wait. Can you please remove
> it for the following packages:
> - trace-cmd
> - gmic
> - kate
> - sigil
> - vtk-dicom
> - seafile-client

Done.

Regards,

Adam

Re: Please remove extra Dep-Wait on mipsel

[Mattia Rizzolo]

> 
> 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 the following packages:
> - trace-cmd
> - gmic
> - kate
> - sigil
> - vtk-dicom
> - seafile-client

FWIW, this is because the dep-wait was added against the source package
(qtbase-opensource-src) instead of a binary package (such as
qtbase5-dev)


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Re: Please binNMU libphonenumber on x32 and sh4

[Philipp Kern]

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 against libicu63'

Done, thanks.

Kind regards
Philipp Kern




signature.asc
Description: OpenPGP digital signature

Re: Please remove

[Emilio Pozuelo Monfort]

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.

Emilio

Re: please give back nqp on mipsel

[Robert Lemmen]

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:
> https://buildd.debian.org/status/logs.php?pkg=nqp=2019.07.1%2Bdfsg-2=mipsel
> 
> I've now given back the version in experimental as well, though it
> doesn't make sense since it's older than the one in unstable???

thanks amd sorry for the confusion, I had indeed mixed up the
experimental and sid builds (I wasn't aware of the experimental version
at all). In any case this shows that the build failure is quite
reproducible, which makes my successes on the porterboxes suspicious...

regards  robert

-- 
Robert Lemmen   http://www.semistable.com 


signature.asc
Description: PGP signature

Re: please give back nqp on mipsel

[Mattia Rizzolo]

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 e.g.
> https://buildd.debian.org/status/architecture.php?a=mipsel=experimental.
> I was expecting it to go back to "needs build", am I mistaken there?

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:
https://buildd.debian.org/status/logs.php?pkg=nqp=2019.07.1%2Bdfsg-2=mipsel

I've now given back the version in experimental as well, though it
doesn't make sense since it's older than the one in unstable…

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Re: please give back nqp on mipsel

[Robert Lemmen]

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 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 e.g.
https://buildd.debian.org/status/architecture.php?a=mipsel=experimental.
I was expecting it to go back to "needs build", am I mistaken there?

thanks  robert

-- 
Robert Lemmen   http://www.semistable.com 


signature.asc
Description: PGP signature

Re: please give back nqp on mipsel

[Mattia Rizzolo]

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 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Re: Please give back rlottie on mipsel and powerpc

[Коля Гурьев]

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 bug 24228 [1] in glibc-2.28. It appeared
because I applied a version script to all binaries including test
runners. Now a correct export map[2] is already accepted by upstream.
The map is used only for shared library and it does not cause segfaults
in auto-tests.

 [1]: https://sourceware.org/bugzilla/show_bug.cgi?id=24228
 [2]: 
https://github.com/Samsung/rlottie/commit/ad100040301b7df6e71ed8f9cecb12517a88ef4e

Re: Please give back rlottie on mipsel and powerpc

[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.

> Please rebuild rlottie on mipsel and powerpc again.
> 
>   gb rlottie_0~git20190721.24346d0+dfsg-2 . mipsel powerpc

✓

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Re: Please give back gnome-games-app

[Philipp Kern]

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
---
https://buildd.debian.org/status/package.php?p=gnome-games-app
https://buildd.debian.org/status/package.php?p=vala


Done, thanks!

Kind regards
Philipp Kern

Re: Please give back abyss on all archs

[Michael Crusoe]

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 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
> chroot, even if there's some more fun (that doesn't trigger an FTBFS):
>
> ./configure: line 5896: : command not found
>
> I'll give it back on amd64 first, and see how that goes.
>
>
> Cheers,
> --
> Cyril Brulebois (k...@debian.org)
> D-I release manager -- Release team member -- Freelance Consultant
>


-- 
Michael R. Crusoe
Co-founder & Lead, Common Workflow Language project

https://orcid.org/-0002-2961-9670

m...@commonwl.org
+1 480 627 9108

Re: Please give back abyss on all archs

[Cyril Brulebois]

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
  | abyss: not taken for building (state is Auto-Not-For-Us). Skipping.

* abyss/hurd-i386
  | abyss: not taken for building (state is Failed). Skipping.

* abyss/mips
  | abyss: not taken for building (state is Auto-Not-For-Us). Skipping.

* abyss/powerpc
  | abyss: not taken for building (state is Auto-Not-For-Us). Skipping.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Please give back abyss on all archs

[Cyril Brulebois]

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
chroot, even if there's some more fun (that doesn't trigger an FTBFS):

./configure: line 5896: : command not found

I'll give it back on amd64 first, and see how that goes.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Please give back a number of ros- packages

[Wookey]

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 . amd64 arm64 armel armhf i386 mips mips64el mipsel 
> ppc64el s390x
> gb ros-nodelet-core_1.9.16-1+b2 . amd64 arm64 armel armhf i386 mips mips64el 
> mipsel ppc64el s390x
> gb ros-robot-model_1.12.6-5+b2 . amd64 arm64 armel armhf i386 mips mips64el 
> mipsel ppc64el s390x
> gb ros-rviz_1.13.1+dfsg-2+b1 . amd64 arm64 armel armhf i386 mips mips64el 
> mipsel ppc64el s390x
> gb ros-opencv-apps_1.12.0-2+b1 . amd64 arm64 armel armhf i386 mips mips64el 
> mipsel ppc64el s390x

done

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Re: Please give back golang-golang-x-tools (1:0.0~git20190809.6d4652c+ds-1) on mipsel

[Aurelien Jarno]

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 golang-golang-x-tools_1:0.0~git20190809.6d4652c+ds-1 . mipsel

Done.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Re: Please give back ros-ros-comm

[Aurelien Jarno]

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 armhf i386 mips mips64el 
> mipsel ppc64el s390x hppa sh4

Done.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Re: Please retry gnutls28 3.6.9-3 on i386

[Stéphane Glondu]

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

Re: Please give back erlang-p1-mqtree 1.0.3-3 on mips

[Cyril Brulebois]

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 present, the syntax is
“package_version” rather than “package version”. The latter would
try to operate on “version” as if it were a package name).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Please give back golang-1.12 on mipsel

[Dr. Tobias Quathamer]

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 five times, unfortunately.
> 
> Kind regards Philipp Kern

Hi,

yes, I've seen that as well. The failure happens at different stages of
the build, so the problem is not easy to identify. I'll take this to
debian-go@l.d.o for more eyes.

Thank you nonetheless for the several build attempts.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Re: Please give back golang-1.12 on mipsel

[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 five times, unfortunately.

Kind regards
Philipp Kern

Re: Please give back znc on arm64

[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

Re: Please give back passwordsafe on arm64

[Cyril Brulebois]

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 passwordsafe_1.06+dfsg-2 . arm64

Done, thanks.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Please give back nftables on i386

[Cyril Brulebois]

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 nftables_0.9.1-2 . i386

Done (without the typo).

Please consider increasing the level of verbosity/logging if that
continues, so that one has a chance of understanding what's going on.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Please give back zeromq3 on mipsel

[GCS]

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 pass.
 I second this. Just built zeromq3/4.3.1-5 on eller.d.o several times
without a failure.

Thanks,
Laszlo/GCS

Re: Please give back firefox/unstable on arch: all

[Emilio Pozuelo Monfort]

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

Re: Please retry gnutls28 3.6.7-3 on armel

[Philipp Kern]

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

Re: Please g-b slepc/experimental on m68k and sh4

[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 as a proof will also help me push an important fix
> to Buster, see #926976
> 
> gb slepc_3.11.0+dfsg1-1exp2 . m68k sh4 . experimental

Done now. (Whyever this was still pending. *sigh*)

Kind regards
Philipp Kern

Re: please give back exadrums in experimental on armel mips mipsel m68k powerpc powerpcspe sh4

[Cyril Brulebois]

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 during the freeze.
> 
> There was a bug in libexadrums_0.3.0-1
> (#927229 requires libatomic on some architectures)
> that caused exadrums to FTBFS
> on armel mips mipsel m68k powerpc powerpcspe sh4.
> 
> This has been fixed in libexadrums 0.3.0-2.
> 
> Please give back exadrums in experimental once the fixed libexadrums
> is available on armel mips mipsel m68k powerpc powerpcspe sh4.
> 
> As far as I understand, there is no need for a Non-Maintainer Upload,
> and a give-back is implied by the dep-wait.
> 
>   dw exadrums_0.3.0-1 . armel mips mipsel m68k powerpc powerpcspe sh4 . 
> experimental . -m 'libexadrums (>= 0.3.0-2)'

The dep-wait syntax expects binary packages. ;) Replacing libexadrums
with libexadrums-dev: done.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Please give back openjdk-12 on ppc64el

[Frédéric Bonnard]

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
> > 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 side. There were some changes
> > since then on the toolchain package list, so maybe this is the reason.
> > 
> > Please give back openjdk on ppc64el .
> > 
> > gb openjdk-12_12~33-1 . ppc64el . unstable -m 'Rebuild against unknown 
> > fixed build dependency'
> 
> There's been a newer version uploaded in the meantime, and fwiw that one 
> built fine.
> 
> Emilio
> 


pgpEC0dUETXom.pgp
Description: PGP signature

Re: Please give back openjdk-12 on ppc64el

[Emilio Pozuelo Monfort]

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 side. There were some changes
> since then on the toolchain package list, so maybe this is the reason.
> 
> Please give back openjdk on ppc64el .
> 
> gb openjdk-12_12~33-1 . ppc64el . unstable -m 'Rebuild against unknown fixed 
> build dependency'

There's been a newer version uploaded in the meantime, and fwiw that one built 
fine.

Emilio

Re: Please give back mtail on armel

[Philipp Kern]

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

Re: Please give back prometheus-alertmanager on ppc64el

[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

Re: Please give-back pypy on ppc64el

[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 issue.
> 
>  gb pypy_7.0.0+dfsg-2 . ppc64el

done. I guess I don't want to know why it paints ASCII art into its
build log...

Kind regards
Philipp Kern

Re: Please give back kf5-messagelib 4:18.08.3-1 on mipsel

[Philipp Kern]

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. Please give it another try.
> 
>   gb kf5-messagelib_18.08.3-1 . mipsel . -m 'rerun to work with flaky tests.'

Done, although at some point it'd be useful to know why they're flaky.

Kind regards
Philipp Kern

Re: Please give back shelxle on kfreebsd-i386

[Daniel Leidert]

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




signature.asc
Description: This is a digitally signed message part

Re: Please give back libkgapi 18.08.3-1 on mipsel

[Philipp Kern]

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

Re: Please give back gnome-builder on mips

[Emilio Pozuelo Monfort]

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 enough for us (usually).
> 
> gb gnome-builder_3.30.3-1 . mips

Given back. Since that seems not to be enough, maybe that should be raised 
again?

Emilio

Re: Please giveback libosinfo

[Cyril Brulebois]

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.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Please give back golang-1.12 on mipsel

[Cyril Brulebois]

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)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Please give back meep on mipsel

[Kurt Roeckx]

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 give meep back:
> > 
> >gb meep_1.7.0-2 . mipsel
> 
> Build-Depends are checked automatically. mpb-dev is still not
> available on mipsel. On mipsel, the meep source pacakge did not

I of course meant the mpb source package

> generate the mpb-dev binary package like it does on some of the
> other arches.
> 
> 
> Kurt
> 

Re: Please give back meep on mipsel

[Kurt Roeckx]

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 automatically. mpb-dev is still not
available on mipsel. On mipsel, the meep source pacakge did not
generate the mpb-dev binary package like it does on some of the
other arches.


Kurt

Re: Please give back golang-1.11 on mips and mipsel

[Philipp Kern]

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.

   gb golang-1.11_1.11.4-1 . mips mipsel


These seem to be consistent/persistent, unfortunately, as they also 
happened (in one case even multiple times) with the newly uploaded 
golang-1.11.


Kind regards and thanks
Philipp Kern

Re: Please give back opencv 3.4.4 on armel

[Philipp Kern]

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

Re: Please give back opencv 3.4.4 on armel

[Mo Zhou]

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 opencv_3.4.4+dfsg-1~exp1 . armel
> 
> That command lacks a distribution argument at the end (the default one is 
> unstable):
> 
> gb opencv_3.4.4+dfsg-1~exp1 . armel . experimental
> 
> Given back.

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


dpkg-deb: building package 'libopencv-calib3d3.4' in 
'../libopencv-calib3d3.4_3.4.4+dfsg-1~exp1_mips.deb'.
dpkg-deb: building package 'libopencv-calib3d3.4-dbgsym' in 
'../libopencv-calib3d3.4-dbgsym_3.4.4+dfsg-1~exp1_mips.deb'.
dpkg-deb: building package 'libopencv-flann-dev' in 
'../libopencv-flann-dev_3.4.4+dfsg-1~exp1_mips.deb'.
dpkg-deb: building package 'libopencv-flann3.4' in 
'../libopencv-flann3.4_3.4.4+dfsg-1~exp1_mips.deb'.
dpkg-deb: building package 'libopencv-flann3.4-dbgsym' in 
'../libopencv-flann3.4-dbgsym_3.4.4+dfsg-1~exp1_mips.deb'.
dpkg-deb: building package 'libopencv-dnn-dev' in 
'../libopencv-dnn-dev_3.4.4+dfsg-1~exp1_mips.deb'.
 dpkg-genbuildinfo
 dpkg-genchanges  >../opencv_3.4.4+dfsg-1~exp1_mips.changes
dpkg-genchanges: info: including full source code in upload
 dpkg-source --after-build .
dpkg-buildpackage: info: full upload (original source is included)
[...]
(experimental_mips-dchroot)lumin@minkus:~/opencv-3.4.4+dfsg$

Re: Please give back opencv 3.4.4 on armel

[Emilio Pozuelo Monfort]

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 is 
unstable):

gb opencv_3.4.4+dfsg-1~exp1 . armel . experimental

Given back.

Cheers,
Emilio

Re: please give back pyside.

[Emilio Pozuelo Monfort]

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:
>>
>> 
>> /usr/lib/x86_64-linux-gnu/cmake/Shiboken-1.2.2/ShibokenConfig.cpython-37m-x86_64-linux-gnu.cmake
>>
>> Call Stack (most recent call first):
>>    CMakeLists.txt:8 (find_package)
> The build attempt was against an older version of libshiboken-dev which as far
> as I can tell was not built against python 3.7, the shiboken 1.2.2-5.1 seems 
> to
> have been built against python3.7 and hence has the file in question.

Given back.

Emilio

Re: Please give back prometheus-node-exporter on s390x

[Emilio Pozuelo Monfort]

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

Re: Please give back golang-1.11 on mipsel

[Emilio Pozuelo Monfort]

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?
>>>
>>> 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
>> somewhat large.
> 
> Hi,
> 
> thanks for trying again, the build now succeeded. However, there's a
> similar strange build failure on mips64el. Could you please give the
> package back on mips64el?
> 
>   gb golang-1.11_1.11.2-2 . mips64el

You may want to do a test build on a porterbox and investigate those failures,
and possibly disable the flaky tests if it's a problem in the tests and not in
the code.

> Also, rclone failed on mipsel. That also seems to need a give back.
> 
>   gb rclone_1.45-1 . mipsel

There was a new upload and it has built this time.

> Are you aware of any issues with the mipsel and mips64el buildds? It
> seems odd that those buildds randomly fail at different tests. Or is
> this a problem with golang on those arches?

AFAIR some buildds lack an FPU, but that should only slow down the builds, but
not fail them due to different FP precision. So I guess you will have to
reproduce them in a porterbox and investigate.

Cheers,
Emilio

Re: Please give back golang-1.11 on mipsel

[Dr. Tobias Quathamer]

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 may take a while for the build to be tried as the mipsel queue 
> is
> somewhat large.

Hi,

thanks for trying again, the build now succeeded. However, there's a
similar strange build failure on mips64el. Could you please give the
package back on mips64el?

  gb golang-1.11_1.11.2-2 . mips64el

Also, rclone failed on mipsel. That also seems to need a give back.

  gb rclone_1.45-1 . mipsel

Are you aware of any issues with the mipsel and mips64el buildds? It
seems odd that those buildds randomly fail at different tests. Or is
this a problem with golang on those arches?

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Re: Please give back golang-1.11 on mipsel

[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 may take a while for the build to be tried as the mipsel queue is
somewhat large.

Cheers,
Emilio

Re: Please give back blender on mips64el

[Emilio Pozuelo Monfort]

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 . mips64el

Done.

Emilio

Re: Please give back xmltooling on arm64 and armel

[Emilio Pozuelo Monfort]

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

Done.

Emilio

Re: Please give back brainparty on mips64el

[Philipp Kern]

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 regards and thanks
Philipp Kern

Re: Please gb krunner/mipsel

[Philipp Kern]

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

Re: please give-back botch

[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:
>>
>>gb botch_0.21-8 . ANY
>>
>> Thanks!
> 
> Because python-pygraphviz did not yet build on mips64el and mipsel, a dw would
> be appropriate:
> 
> dw botch_0.21-8 . mips64el mipsel . -m 'python-pygraphviz (>= 1.5-1)'

Done (except setting the dw everywhere, including ports - which will
take a little bit to clear).

Kind regards and thanks
Philipp Kern

Re: please give-back botch

[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:
> 
>gb botch_0.21-8 . ANY
> 
> Thanks!

Because python-pygraphviz did not yet build on mips64el and mipsel, a dw would
be appropriate:

dw botch_0.21-8 . mips64el mipsel . -m 'python-pygraphviz (>= 1.5-1)'


signature.asc
Description: signature

Re: Please give back appstream-generator

[Matthias Klumpp]

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 done yet, so I did that now. My apologies for the
> delay.

Thank you! :-)

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

Re: Please give back libguess 1.2-2

[Philipp Kern]

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 that it failed four times on ppc and
ppcspe. Consistently, with the last failure 14d ago.

Anyway I'm fine retrying mips{,el} as that was 199d ago and never
retried and those are actually release architectures. Done. I will note
that for these architectures specifically
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897086 is marked as
affecting libguess.

Kind regards
Philipp Kern

Re: Please give back appstream-generator

[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 done yet, so I did that now. My apologies for the
delay.

Kind regards
Philipp Kern

Re: Please give back kido on armhf

[Wookey]

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.
> 
>  dw kido_0.1.0+dfsg-6 . armhf . -m 'libassimp4 (>= 4.1.0~dfsg-5)'

done (and built)


Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Re: Please give back file-roller

[Ivo De Decker]

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

Re: Please give back sunpy on 32 bit

[Ivo De Decker]

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.

Ivo

Re: Please give back file-roller

[Jeremy Bicha]

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

Re: Please give back python-pcl on armhf

[Ivo De Decker]

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

Re: Please give back file-roller

[Wookey]

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 done.
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?

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Re: Please give-back hiredis 0.14.0-1 on mips64el

[Emilio Pozuelo Monfort]

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

It has already been attempted three times:

https://buildd.debian.org/status/logs.php?pkg=hiredis=mips64el

Emilio

Re: Please give back nomad on ppc64el

[Breno Leitao]

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.
> 
> gb nomad_0.8.6+dfsg1-1 . ppc64el

Done. Let me know if it does not work.

Thanks,
Breno

Re: Please give back glib2.0 on armel

[Jeremy Bicha]

This was done. smcv also did some diagnosis of the issue in
https://bugs.debian.org/909150

Thanks,
Jeremy Bicha

Re: Please give back cogl on armel

[Wookey]

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 anyway (test failures
> are ignored).
> 
> gb cogl_1.22.2-4 . armel
> 
> References
> ---
> https://buildd.debian.org/status/package.php?p=cogl

given back

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Re: Please gb ktexteditor/armhf

[John Paul Adrian Glaubitz]

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 fine. (While on harris GCC ICEd really a lot, and I gave up
>> after the 4 ICE in a row...).
>> 
>> So please giveback ktexteditor_5.49.0-2/armhf, hoping it was some kind
>> of transient failure...
>> 
> I doubt it's transient failure (it failed again), more likely to be the
> fact that arm-arm-01 is arm64 hardware.  You may want to try amdahl's
> armhf chroot rather than abel.  The arm porters may be able to help too.

It fails on sparc64 as well which is a good indicator that it’s an alignment 
issue although the crash on sparc64 looks differently.

Generally, code that uses pointer type casts is usually the cause for unaligned 
access and SIGBUS. Pointer type casts should always be avoided since they can 
always lead to undefined behavior.

On x86, unaligned access is usually less a problem but it can trigger crashes 
when using extensions like SSE which has stricter alignment requirements.

I suggest debugging the crash on a porterbox. Unaligned accesses can be 
normally easily tracked down with gdb.

Adrian

Re: Please gb ktexteditor/armhf

[Julien Cristau]

[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 ICE in a row...).
> 
> So please giveback ktexteditor_5.49.0-2/armhf, hoping it was some kind
> of transient failure...
> 
I doubt it's transient failure (it failed again), more likely to be the
fact that arm-arm-01 is arm64 hardware.  You may want to try amdahl's
armhf chroot rather than abel.  The arm porters may be able to help too.

Cheers,
Julien

Re: Please give back geary on failed architectures

[Julien Cristau]

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 again on alpha since the previous version built.
>>>
>>> dw geary_0.12.4-1 . alpha . -m 'libsoup2.4 (>= 2.64.0-2)'
>>> gb geary_0.12.4-1 . mips64el hppa powerpcspe sh4
>>> gb libsoup2.4_2.64.0-2 . alpha
>>
>> Done.
>>
>> Kind regards
>> Philipp Kern
> 
> Please clear the depwait for alpha. I didn't realize that it needed to
> be a binary package (instead of a source package). libsoup2.4 has
> built and been installed on alpha now.
> 
Done.

Cheers,
Julien

Re: Please give back geary on failed architectures

[Jeremy Bicha]

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.
> >
> > dw geary_0.12.4-1 . alpha . -m 'libsoup2.4 (>= 2.64.0-2)'
> > gb geary_0.12.4-1 . mips64el hppa powerpcspe sh4
> > gb libsoup2.4_2.64.0-2 . alpha
>
> Done.
>
> Kind regards
> Philipp Kern

Please clear the depwait for alpha. I didn't realize that it needed to
be a binary package (instead of a source package). libsoup2.4 has
built and been installed on alpha now.

Thanks,
Jeremy Bicha

Re: Please give back geary on failed architectures

[Philipp Kern]

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)'
> gb geary_0.12.4-1 . mips64el hppa powerpcspe sh4
> gb libsoup2.4_2.64.0-2 . alpha

Done.

Kind regards
Philipp Kern

Re: Please increase the no-activity time limit on slow build servers

[Bastian Blank]

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 Dove", stardate unknown

Re: Please give back blender on mips64el

[James Cowgill]

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 . mips64el

Done.

James



signature.asc
Description: OpenPGP digital signature

Re: Please give pack wxpython4.0 on *

[Emilio Pozuelo Monfort]

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 called ANY.

Scheduled.

Cheers,
Emilio

Re: Please give back ros-common-msgs on amd64

[Emilio Pozuelo Monfort]

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 back ros-common-msgs on amd64:
> 
>  gb ros-common-msgs_1.12.6-3 . amd64

FTR: this needs a binNMU, give backs are for packages that failed to build. I
have scheduled it, but for future reference binNMUs are handled in
release.debian.org bugs.

Thanks,
Emilio

Re: please dep-wait adacontrol on most architectures in experimental

[Philipp Kern]

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 failed with 2017-3 on
  amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el
  alpha hppa hurd-i386 ia64 powerpc sparc64

* is waiting for dependencies on
  kfreebsd-amd64 kfreebsd-i386 m64k powerpcspe riscv64 sh4 x32
  On such architectures, an attempt may fail or not depending on the
  available version of libasis2018-dev.

I believe that a dep-wait fixes both problems.
Please trigger a rebuild once the updated asis is available.

dw adacontrol_1.19r10-3 . ANY -s390x -ppc64 . experimental . -m
'libasis2018-dev (>= 2018-1)'


done.

Kind regards and thanks
Philipp Kern