Re: Please give back pandas, dep-wait on numexpr #1049326
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)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: buildd.debian.org log summary page - add tar of all logs
Hi, Marc Haber (2023-07-03): > please consider adding an option that will create and download a tarball > of all logs listed on a certain page like > https://buildd.debian.org/status/package.php?p=gensio=sid > > That would make it vastly easier to grep the logs of all architectures > to find out whether an issue applies identically to many architectures. Have you tried this? getbuildlog gensio 2.6.6-4 Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: Bug#1023811: golang-github-grpc-ecosystem-go-grpc-middleware_1.3.0-1 sources changed in the archive?
Adrian Bunk (2022-11-10): > Package: ftp.debian.org > Severity: grave > X-Debbugs-Cc: debian-wb-team@lists.debian.org, Thomas Goirand > Yeah, the dsc seems to have changed, deb.debian.org returns the old version (due to corporate-grade caching or whatever), while my local mirror (standard apache2 serving files synced by ftpsync via syncproxy2.eu.debian.org and debian.ethz.ch) shows the new version (which matches the Sources file and downloads fine accordingly). > Get:1 https://deb.debian.org/debian experimental/main > golang-github-grpc-ecosystem-go-grpc-middleware 1.3.0-1 (dsc) [2857 B] > Err:1 https://deb.debian.org/debian experimental/main > golang-github-grpc-ecosystem-go-grpc-middleware 1.3.0-1 (dsc) > Hash Sum mismatch > Hashes of expected file: >- SHA256:8e86e0a9cc31461c0f564e8feefb2e1e9ec05c265ab06e96fd32b7de787bc504 >- Filesize:2857 [weak] >- MD5Sum:c4d33ab09e4f4a95c819dd1de88d0876 [weak] > Hashes of received file: >- SHA256:8bbee530bbdb11a58a275c34878c372558223c294384897822eba1338b84db82 >- MD5Sum:8d6eee1b2b773c9be12536396ba949a6 [weak] >- Filesize:2857 [weak] > Last modification reported: Wed, 26 Oct 2022 14:32:16 + An extra check can be done by querying snapshot.debian.org, and `debsnap golang-github-grpc-ecosystem-go-grpc-middleware 1.3.0-1` downloads the old version as well. An extra hint is obtained by clicking the 1.3.0-1 link on <http://snapshot.debian.org/package/golang-github-grpc-ecosystem-go-grpc-middleware/> and getting an error page, I suppose because of a different lookup implementation. Adding `-v` to the debsnap line above, I'm getting this URL: https://snapshot.debian.org/mr/package/golang-github-grpc-ecosystem-go-grpc-middleware/1.3.0-1/srcfiles?fileinfo=1 which indeed has two `fileinfo` entries for the .dsc: "0feb631739624059c1db234338e87a57d33f4d5f": [ { "archive_name": "debian", "first_seen": "20221027T213940Z", "name": "golang-github-grpc-ecosystem-go-grpc-middleware_1.3.0-1.dsc", "path": "/pool/main/g/golang-github-grpc-ecosystem-go-grpc-middleware", "size": 2857 } ], "48d5553979d3de93b05587668ce30305d3ad9141": [ { "archive_name": "debian", "first_seen": "20221103T151306Z", "name": "golang-github-grpc-ecosystem-go-grpc-middleware_1.3.0-1.dsc", "path": "/pool/main/g/golang-github-grpc-ecosystem-go-grpc-middleware", "size": 2857 } ], Maybe that'll help pinpoint what happened and/or when. Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: Builds stalled on mipsel workers?
Nilesh Patra (2021-10-02): > I have noticed that a few packages still have a "Build-Needed" stage > on mipsel and mips64el even after completing 2 days of migration > delay, and this is stalling testing migration for them. > > For instance, these[1,2,3] -- is this some extra load on mips buildd > machines, or is this just stuck behind a long queue instead? We have stats, like: https://buildd.debian.org/status/architecture.php?a=mips64el=all https://buildd.debian.org/status/architecture.php?a=mipsel=all There are ongoing or just-finished linux builds, and those take a *very* long time on those archs. Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: clear extra-depends for pocl/mips64el
Emilio Pozuelo Monfort (2020-04-27): > On 25/04/2020 18:28, Philipp Kern wrote: > > So I *think* that worked, because it calls update_source_info, setting the > > extra_depends field. The database query confirms that the field was > > cleared. I'm > > not sure if --extra-depends= was actually needed as --override is supposed > > to > > put the package back into Needs-Build anyway, from BD-Uninstallable. > > It is needed, otherwise it will go into needs-build with the same > extra-depends field I think that's what I noticed with a bare gb -o, yes. :) > and the next build or dose run (whichever happens first) will put it > back into bd-uninst. The same can be achieved with wb btw, from my > bash history: > > wb gb gnome-software . x32 . --extra-depends '' -o Thanks! Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: clear extra-depends for pocl/mips64el
Andreas Beckmann (2020-04-24): > please clear the obsolete (and nowadays unsatisfiable) > Extra-Depends: gcc-7 (>= 7.2.0-3) > for pocl om mips64el. Hm, I had “gb -o” in mind, but that's only to clear the “failed” status; I'd be happy to learn how to get rid of extra-depends (https://release.debian.org/wanna-build.txt doesn't seem to list anything relevant). Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: Please give back rear on i386
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)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: package "micro-httpd" stuck as "Uploaded"
Feb 11 10:31:40 micro-httpd_20140814-2_amd64.changes moved to /srv/upload.debian.org/DEFERRED/1-day Feb 11 10:31:40 micro-httpd_20140814-2.dsc moved to /srv/upload.debian.org/DEFERRED/1-day Feb 11 10:31:40 micro-httpd_20140814-2.debian.tar.xz moved to /srv/upload.debian.org/DEFERRED/1-day Feb 11 10:31:40 micro-httpd-dbgsym_20140814-2_amd64.deb moved to /srv/upload.debian.org/DEFERRED/1-day Feb 11 10:31:40 micro-httpd_20140814-2_amd64.buildinfo moved to /srv/upload.debian.org/DEFERRED/1-day Feb 11 10:31:40 micro-httpd_20140814-2_amd64.deb moved to /srv/upload.debian.org/DEFERRED/1-day Feb 11 23:20:27 > cancel micro-httpd_20140814-2_amd64.changes Feb 11 23:20:27 Files removed from 1-day: micro-httpd_20140814-2_amd64.changes micro-httpd_20140814-2.dsc micro-httpd_20140814-2.debian.tar.xz micro-httpd-dbgsym_20140814-2_amd64.deb micro-httpd_20140814-2_amd64.buildinfo micro-httpd_20140814-2_amd64.deb Giving it back. Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: node-yarnpkg is stuck in Uploaded state for 50+ days
Hi, Andreas Beckmann (2020-02-06): > please do the right thing to help node-yarnpkg out of the Uploaded state > in sid where it is for 50+ days already. > > Should there be some process that automatically reports stale Uploaded > packages after x days? It seems to have reached dak just fine, but: kibi@coccia:~$ xzgrep node-yarnpkg /srv/ftp-master.debian.org/log/2019-12.xz 20191217121905|process-upload|dak|Processing changes file|node-yarnpkg_1.21.1-1_source.changes 20191217121933|process-upload|dak|REJECT|node-yarnpkg_1.21.1-1_source.changes 20191217144608|process-upload|dak|Processing changes file|node-yarnpkg_1.21.1-1_source.changes 20191217144659|process-upload|dak|ACCEPT|node-yarnpkg_1.21.1-1_source.changes 20191217144704|process-upload|dak|Archiving|node-yarnpkg_1.21.1-1_source.buildinfo 20191217151914|process-upload|dak|Processing changes file|node-yarnpkg_1.21.1-1_all.changes 20191217151914|process-upload|dak|REJECT|node-yarnpkg_1.21.1-1_all.changes 20191219145045|manage-build-queues|dak|removed source from build queue|buildd-unstable|node-yarnpkg|1.21.1-1 Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: Please give back comskip on ppc64el
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)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: mecab-0.996-7 build failure on mipsel
Hi, NOKUBI Takatsugu (2020-01-21): > I uploaded mecab-0.996-7 as a sponsor. > > I built from salsa repository https://salsa.debian.org/nlp-ja-team/mecab, > with -uc -us options then signed with debsign, it is debian wiki's > procedure. > > https://wiki.debian.org/DebianMentorsFaq#What_is_the_process_for_sponsoring_a_package.3F > > My built package(amd64) was accepted, but buildd said failing on mipsel: > https://buildd.debian.org/status/fetch.php?pkg=mecab=mipsel=0.996-7=1579538988=log > > It seems that causes by gpg verifing process. How do I fix the problem? I'd suggest you try building with the -b flag (arch:any + arch:all packages), that should work. Then try building with the -B flag (arch:any packages only), as done on the build daemons. This will likely fail on your machine too, and you'll be able to debug what's going on. Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: vacation 3.3.2 MIGRATED to testing
Ian Jackson (2019-08-25): > Niels Thykier writes ("Re: vacation 3.3.2 MIGRATED to testing"): > > There was a binNMU of vacation/3.3.2 yesterday[1]. I have not looked > > into the precise timing but I assume that is the reason why 3.3.2 migrated. > ... > > [1] > > https://buildd.debian.org/status/logs.php?pkg=vacation=3.3.2%2Bb1=amd64=sid > > Ah. Thanks for the clarification. > > Forgive my ignorance (and adding the WB team), but: > > Do you happen to know what the most sensible way is for me to check > for a binNMU in future ? Starting from tracker and its links to > buildd logs, I can't seem to find any trace of 3.3.2+b1. It's not on > p.d.o either (https://packages.debian.org/unstable/vacation). Always a good idea to check what your source and binaries look like? kibi@armor:~$ rmadison -S vacation -s testing vacation | 3.3.2 | testing| source, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x vacation | 3.3.2+b1 | testing| amd64 > And I didn't get any email about this binNMU despite being listed in > Uploaders. There are no binNMU notifications that I'm aware of. > And, DYK if there is a way for me to know who scheduled this binNMU > and why ? From your link I found a log which contains this > information: > > Binary-Only-Changes: >vacation (3.3.2+b1) sid; urgency=low, binary-only=yes >. > * Binary-only non-maintainer upload for amd64; no source changes. > * rebuild on buildd >. > -- amd64 Build Daemon (x86-grnet-01) > Sat, 24 Aug 2019 04:47:34 + The why is in the changelog you quoted… The who, probably somewhere in the wanna-build DB, but that's not my forte. Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: Please give back abyss on all archs
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)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: Please give back abyss on all archs
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)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: Do we upload buildd arch:all pkgs? (ie, where is python-mplexporter/0.0.1+20140921-4 ?)
Hello, Sandro Tosi (2019-08-14): > i hope this is the right address to send my question. > > As part of the effort to remove Python 2, i was looking at the > reverse-dependencies of matplotlib. I noticed pyhton-mplexporter was > uploaded recently > (https://packages.qa.debian.org/p/python-mplexporter.html) to its -4 > revision, but only -3 is available in sid/testing > (https://packages.debian.org/sid/python-mplexporter). > > It looks like the package was built > (https://buildd.debian.org/status/package.php?p=python-mplexporter=unstable) > but somehow it never reached the archive? check for example madison: > > $ rmadison python-mplexporter > python-mplexporter | 0.0.1+20140921-1 | oldoldstable | source, all > python-mplexporter | 0.0.1+20140921-2 | oldstable| source, all > python-mplexporter | 0.0.1+20140921-3 | stable | source, all > python-mplexporter | 0.0.1+20140921-3 | unstable | source, all > python-mplexporter | 0.0.1+20140921-4 | testing | source > python-mplexporter | 0.0.1+20140921-4 | unstable | source > > what can we do? Nothing? kibi@armor:~$ rmadison -s unstable -S python-mplexporter python-mplexporter | 0.0.1+20140921-3 | unstable | source, all python-mplexporter | 0.0.1+20140921-4 | unstable | source python3-mplexporter | 0.0.1+20140921-4 | unstable | all Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: Please give back erlang-p1-mqtree 1.0.3-3 on mips
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)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: Please give back passwordsafe on arm64
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)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: Please give back nftables on i386
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)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: plexus-utils2 give back
Hi Emmanuel, Emmanuel Bourg (2019-07-19): > plexus-utils2/3.2.1-1 failed to build due to a regression in a build > dependency that is not resolved. Could you please reset its build state? Assuming s/not/now/ here… > gb plexus-utils2_3.2.1-1 . all … done, thanks. Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: please give back exadrums in experimental on armel mips mipsel m68k powerpc powerpcspe sh4
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)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: Please giveback libosinfo
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)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: Bug#919341: libtool-bin: amd64 /usr/bin/libtool is a zero byte file
Control: severity -1 grave Control: tag -1 patch Cyril Brulebois (2019-01-15): > For some reasons, libtool and its manpage (from the libtool-bin binary) > are “sanitized” in binary-indep, which might explain why it's only > showing up on the maintainer build which was likely using “-b”. > > > $ dpkg-deb -c libtool-bin_2.4.6-7_amd64.deb > > -rwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/bin/libtool > > -rw-r--r-- root/root20 2019-01-12 09:10 > > ./usr/share/man/man1/libtool.1.gz > > The manpage is a gzipped empty file. I'm afraid the situation is pretty bad, as an empty executable doesn't do anything but also produces no errors; so I fear any packages having been built using this version of libtool-bin on amd64 has likely missed a step or two without that getting noticed… Cc-ing debian-release@ & debian-wb-team@ for information. > At least those points need addressing: > 1. some sed lines have an extra slash before the repetition specifier. > 2. the for loop isn't set up to bail out on errors > 3. libtoolize from bin:libtool which is arch:all is “sanitized” > in binary-arch; looks like a mixup between both targets given > the already mentioned libtool (binary and manpage)… > 4. hardcoding the upstream version in debian/rules looks like a recipe > for a later regression I'm attaching individual patches addressing these, along with a ready to use (except for “dch -r”) source debdiff. A quick upload and further assessment would likely be a good idea. Setting up something with autopkgtest might be worth it, if only just to check a few trivial commands (--help comes to mind). Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant From e3c73f4532de8f8f83b242011f536729f4db7b05 Mon Sep 17 00:00:00 2001 From: Cyril Brulebois Date: Tue, 15 Jan 2019 03:41:39 + Subject: [PATCH 1/7] Fix Vcs-* URLs. --- debian/changelog | 6 ++ debian/control | 4 ++-- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/debian/changelog b/debian/changelog index ace7740..4266654 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +libtool (2.4.6-8) UNRELEASED; urgency=medium + + * Fix Vcs-* URLs. + + -- Cyril Brulebois Tue, 15 Jan 2019 03:41:15 + + libtool (2.4.6-7) unstable; urgency=medium * Standards-Version: 4.3.0 diff --git a/debian/control b/debian/control index c2cfefc..0d92424 100644 --- a/debian/control +++ b/debian/control @@ -17,8 +17,8 @@ Maintainer: Alastair McKinstry Standards-Version: 4.3.0 Rules-Requires-Root: no Homepage: https://www.gnu.org/software/libtool/ -Vcs-Browser: https://salsa.debian.org:/mckinstry/libtool.git -Vcs-Git: https://salsa.debian.org:/mckinstry/libtool.git +Vcs-Browser: https://salsa.debian.org/mckinstry/libtool.git +Vcs-Git: https://salsa.debian.org/mckinstry/libtool.git Package: libtool Architecture: all -- 2.11.0 From 3849d58d6013a1ae557647335b215a6cfe62d725 Mon Sep 17 00:00:00 2001 From: Cyril Brulebois Date: Tue, 15 Jan 2019 03:42:58 + Subject: [PATCH 2/7] Fix sed syntax errors. Closes: #919341 These errors lead to empty libtool executable and manpage. With thanks to James McCoy for reporting. --- debian/changelog | 2 ++ debian/rules | 8 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/debian/changelog b/debian/changelog index 4266654..da983ae 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,6 +1,8 @@ libtool (2.4.6-8) UNRELEASED; urgency=medium * Fix Vcs-* URLs. + * Fix sed syntax errors leading to empty libtool executable and + manpage, with thanks to James McCoy for reporting. Closes: #919341 -- Cyril Brulebois Tue, 15 Jan 2019 03:41:15 + diff --git a/debian/rules b/debian/rules index 004285f..e502a2b 100755 --- a/debian/rules +++ b/debian/rules @@ -163,8 +163,8 @@ binary-indep: build-indep install for f in \ debian/libtool-bin/usr/share/man/man1/libtool.1 \ debian/libtool-bin/usr/bin/libtool ; do cat $$f | \ - sed -e 's%/usr/bin/grep%/bin/grep%/g' | \ - sed -e 's%/usr/bin/sed%/bin/sed%/g' | \ + sed -e 's%/usr/bin/grep%/bin/grep%g' | \ + sed -e 's%/usr/bin/sed%/bin/sed%g' | \ sed -e 's%/usr/bin/dd%/bin/dd%g' | \ sed -e 's%${CURDIR}%/build/libtool-2.4.6%g' | \ > debian/tmpff ; \ @@ -193,8 +193,8 @@ binary-arch: build-arch install for f in \ debian/libtool/usr/bin/libtoolize ; do \ cat $$f | \ - sed -e 's%/usr/bin/grep%/bin/grep%/g' | \ - sed -e 's%/usr/bin/sed%/bin/sed%/g' | \ + sed -e 's%/usr/bin/grep%/bin/grep%g' | \ + sed -e 's%/usr/bin/sed%/bin/sed%g' | \ sed -e 's%/usr/bin/dd%/bin/dd%g' | \ sed -e 's%${CURDIR}%/build/libtool-2.4.6%g' | \ > debian/tmpff ; \ -- 2.11.0 From 669ed2faf2510b3931cf4a37ca53ba15a8c0598f Mon Sep 17 00:00:00 2001 From: Cyril Brulebois Date: Tue, 15 Jan 2019 03:46:3
Re: Please give back golang-1.12 on mipsel
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)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: Please give back rivet on collectd
Hi, Frédéric Bonnard <fre...@debian.org> (2018-05-17): > collectd's last build failed on ppc64el. > https://buildd.debian.org/status/fetch.php?pkg=collectd=ppc64el=5.8.0-5=1525460552=0 > > --- > /usr/bin/protoc -I./proto \ > --grpc_out=. --plugin=protoc-gen-grpc=/usr/bin/grpc_cpp_plugin > proto/collectd.proto > /usr/bin/grpc_cpp_plugin: error while loading shared libraries: > libprofiler.so.0: cannot open shared object file: No such file or directory > --grpc_out: protoc-gen-grpc: Plugin failed with status code 127. > --- > > I didn't manage to make it fail on my side on both vm and read hardware. > > Please give back collectd on ppc64el. > > gb collectd_5.8.0-5 . ppc64el This was also requested by Sebastian on IRC; given back and successful build. Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant signature.asc Description: PGP signature
Re: misleading timestamps in binnmus
Ian Jackson(2016-11-09): > What version of sbuild do buildds run ? Ie, supposing that this is > fixed in sbuild in stretch, will this be fixed on the buildds ? Or do > we need to update jessie, or what ? sbuild on buildds uses a specific version of sbuild, for reasons I'm not going to summarize. The base version is close to what's in jessie (see the first lines of any build log which has “sbuild (Debian sbuild) 0.65.2”). dsa-puppet.git has: ,---[ modules/debian-org/files/apt.preferences ]--- | … | Package: sbuild | Pin: release o=buildd.debian.org | Pin-Priority: 500 | | Package: buildd | Pin: release o=buildd.debian.org | Pin-Priority: 500 | | Package: libsbuild-perl | Pin: release o=buildd.debian.org | Pin-Priority: 500 `--- Repository seems to live under: https://apt.buildd.debian.org/ KiBi. signature.asc Description: Digital signature
Re: Please give back xiphos on ppc64el
Fernando Seiti Furusato(2016-10-10): > The package xiphos was failing to build from source, due to a bug > introduced by sword on type definitions. > > That is now fixed, so xiphos can be built on ppc64el. > > Please, give back xiphos on ppc64el with sword_1.7.3+dfsg-9 > > gb xiphos_4.0.4+dfsg1-1 . ppc64el Done, thanks. KiBi. signature.asc Description: Digital signature
Re: Please give back jacktrip
Cyril Brulebois <k...@debian.org> (2016-08-02): > IOhannes m zmölnig (Debian/GNU) <umlae...@debian.org> (2016-08-02): > > There was a bug in librtaudio-dev that caused jacktrip to FTBFS on all > > architectures. This has just been fixed with the upload of > > rtaudio-4.1.2~ds0-4. > > Please give back jacktrip on all archs once the new rtaudio package has > > hit the archives. > > > > dw jacktrip_1.1~repack-4 . ANY . -m 'librtaudio-dev (>=4.1.2~ds0-4)' > > Done, thanks. > > (I'll try to keep an eye until the first builds go through; it's been a > while since my last dw.) It doesn't seem to go too well, even with librtaudio-dev picked from incoming (with the right version): | Get:13 http://incoming.debian.org/debian-buildd buildd-unstable/main amd64 librtaudio-dev amd64 4.1.2~ds0-4 [18.5 kB] […] | g++ -c -m64 -pipe -D__LINUX_ALSA__ -g -O2 -fPIC -D__LINUX_ALSA__ -g -std=gnu++0x -D_REENTRANT -Wall -W -fPIC -D__RT_AUDIO__ -D__LINUX__ -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -isystem /usr/local/include -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -Idebug -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o debug/JackTrip.o JackTrip.cpp | In file included from JackTrip.cpp:44:0: | RtAudioInterface.h:41:21: fatal error: RtAudio.h: No such file or directory | compilation terminated. | Makefile.Debug:356: recipe for target 'debug/JackTrip.o' failed | make[2]: *** [debug/JackTrip.o] Error 1 Full build log for amd64: https://buildd.debian.org/status/fetch.php?pkg=jacktrip=amd64=1.1~repack-4%2Bb1=1470144208 KiBi. signature.asc Description: Digital signature
Re: Please give back jacktrip
IOhannes m zmölnig (Debian/GNU)(2016-08-02): > There was a bug in librtaudio-dev that caused jacktrip to FTBFS on all > architectures. This has just been fixed with the upload of > rtaudio-4.1.2~ds0-4. > Please give back jacktrip on all archs once the new rtaudio package has > hit the archives. > > dw jacktrip_1.1~repack-4 . ANY . -m 'librtaudio-dev (>=4.1.2~ds0-4)' Done, thanks. (I'll try to keep an eye until the first builds go through; it's been a while since my last dw.) KiBi. signature.asc Description: Digital signature
Re: please give back libdisorder on ppc64el
Fernando Seiti Furusato(2016-07-26): > The package libdisorder failed to build from source due to a bug on d-shlibs > on > version prior d-shlibs_0.75. > > I have tested it on a schroot. > > Could you please give back libdisorder with d-shlibs_0.75? > > gb libdisorder_0.0.2-1 . ppc64el Done on ppc64el, and also s390x which by the looks of it had the same issue and is also concerned by the d-shlibs fix. KiBi. signature.asc Description: Digital signature
Re: give back openexr on ppc64el
Mathieu Malaterre(2016-07-19): > Something looks rather odd on ppc64el for openexr. The build time is > very close to 2h. Sorry, I forgot to follow up on this part: its build time was about 6 minutes[1]. The “very close to 2h” part was likely the time it had spent in the “Maybe-Failed” state instead. 1. https://buildd.debian.org/status/logs.php?pkg=openexr=ppc64el > Since I cannot reproduce the issue on the sole ppc64el we have […] It's built now (after 16 minutes). Maybe some glitch in the test suite? KiBi. signature.asc Description: Digital signature
Re: gb: dolfin: fix bogus "BD-Uninstallable" state
Drew Parsons(2016-07-16): > Thanks Emilio. dolfin is now built on armel. armhf is the last arch > that's needed. > > Can dolfin be given back manually on armhf? I've forced a give-back to get it out of the BD-Uninstallable status, and it seems to have been picked up for building already. KiBi. signature.asc Description: Digital signature
Re: Please give back afnix
Hi, Fernando Seiti Furusato(2016-06-14): > The package afnix was failing to build some days ago due to probably a > compiler problem. > I have just tested on a ppc64el chroot and it built successfully. > Since it fails on more archs I am requesting a give-back on all of them, but > I only know that it builds on ppc64el. > Could you please process the following? > >gb afnix_2.6.2-1 . ppc64el powerpc mipsel mips i386 armhf armel arm64 It's marked on [1] as Failed with this bug report reference [2]. How about checking this patch? 1. https://buildd.debian.org/status/package.php?p=afnix=sid 2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815436 KiBi. signature.asc Description: Digital signature
Re: reniced [all] is stuck in Uploaded state
Andreas Beckmann(2016-05-26): > the reniced arch:all build for sid is stuck in "Uploaded" state for more > than a week now, please push it forward or give it back or do whatever > is appropriate to unblock it :-) > > https://buildd.debian.org/status/package.php?p=reniced=unstable May 16 14:45:13 processing /reniced_1.21-1_i386.changes May 16 14:45:13 GnuPG signature check failed on reniced_1.21-1_i386.changes May 16 14:45:13 /reniced_1.21-1_i386.changes has bad PGP/GnuPG signature! May 16 14:45:13 Removing /reniced_1.21-1_i386.changes, but keeping its associated files for now. May 19 11:18:57 processing /reniced_1.21-1_all.changes May 19 11:18:58 reniced_1.21-1_all.deb doesn't exist (ignored for now) May 19 11:18:58 /reniced_1.21-1_all.changes couldn't be processed for 48 hours and is now deleted May 19 11:18:58 reniced_1.21-1_all.deb Given back. KiBi. signature.asc Description: Digital signature
Re: Please give back phpunit on all
David Prévot(2016-03-06): > Hi, > > Please, retry building phpunit now that a recent php-codecoverage is > in (I uploaded it a bit too quickly, sorry). > > gb phpunit_5.2.10-1 . all Done, thanks. KiBi. signature.asc Description: Digital signature
Re: src:docker-registry
Tianon Gravi(2016-03-02): > On 2 March 2016 at 14:24, Aurelien Jarno wrote: > > Looking at the reason why dak rejected those packages gives the > > following error: > > > > APT could not parse Built-Using field > > > > Looking at the build log, one can see the following wrong entry: > > > > golang-go.crypto-dev (= ) > > Oh, that's bizarre -- I'll take a look to figure out how that's > happening; thanks for your help! > > Is that dak rejection posted somewhere public (or on a machine I can > access) so I can look it up myself if the problem happens again? I'm > not having any luck trying to find it. :( Yes. ssh mirror.ftp-master.debian.org kibi@coccia:~$ xzgrep docker-registry /srv/ftp-master.debian.org/log/2016-02.xz|grep REJECT 20160219180553|process-upload|dak|REJECT|docker-registry_2.2.0~ds1-1_all.changes 20160219180553|process-upload|dak|REJECT|docker-registry_2.2.0~ds1-1_amd64.changes 20160219180553|process-upload|dak|REJECT|docker-registry_2.2.0~ds1-1_arm64.changes 20160219180553|process-upload|dak|REJECT|docker-registry_2.2.0~ds1-1_i386.changes 20160219183417|process-upload|dak|REJECT|docker-registry_2.2.0~ds1-1_ppc64el.changes 20160219191921|process-upload|dak|REJECT|docker-registry_2.2.0~ds1-1_armel.changes 20160219191921|process-upload|dak|REJECT|docker-registry_2.2.0~ds1-1_armhf.changes kibi@coccia:~$ ls /srv/ftp-master.debian.org/queue/reject/docker-registry_2.2.0~ds1-1_*.changes.reason /srv/ftp-master.debian.org/queue/reject/docker-registry_2.2.0~ds1-1_all.changes.reason /srv/ftp-master.debian.org/queue/reject/docker-registry_2.2.0~ds1-1_amd64.changes.reason /srv/ftp-master.debian.org/queue/reject/docker-registry_2.2.0~ds1-1_arm64.changes.reason /srv/ftp-master.debian.org/queue/reject/docker-registry_2.2.0~ds1-1_armel.changes.reason /srv/ftp-master.debian.org/queue/reject/docker-registry_2.2.0~ds1-1_armhf.changes.reason /srv/ftp-master.debian.org/queue/reject/docker-registry_2.2.0~ds1-1_i386.changes.reason /srv/ftp-master.debian.org/queue/reject/docker-registry_2.2.0~ds1-1_ppc64el.changes.reason KiBi. signature.asc Description: Digital signature
Re: Please give back some packages on kfreebsd, hurd
Steven Chamberlain(2016-02-29): > Dear wanna-build team, > > Please could someone give back cmake for build on kfreebsd and hurd, > because the (same) test failures seen on those arches' build logs, > I don't see now in an up-to-date sid chroot on kfreebsd-amd64: > > gb cmake_3.4.1-2 . kfreebsd-amd64 > gb cmake_3.4.1-2 . kfreebsd-i386 Done. > gb cmake_3.4.1-2 . hurd-i386 This one was marked as Failed, not touching but copying hurd-i386@. KiBi. signature.asc Description: Digital signature
Re: Please give back elk 3.99.8-4 on i386
Ben Hutchings(2016-02-21): > elk version 3.99.8-4 failed to build on i386 due to a test failure. I > can't reproduce the test failure, and all other architectures passed, > so I think it's worth retrying. > > gb elk_3.99.8-4 . i386 I've just reproduced the FTBFS in a sid-i386 chroot on amd64: | (sid-i386-devel)kibi@wodi:~/hack/bsp/elk-3.99.8$ cat test/test-suite.log | === |: test/test-suite.log | === | | # TOTAL: 4 | # PASS: 3 | # SKIP: 0 | # XFAIL: 0 | # FAIL: 1 | # XPASS: 0 | # ERROR: 0 | | .. contents:: :depth: 2 | | FAIL: check-gc | == | | testing garbage collector integrity (1 loops) | | Panic: Visit: object not in prev space at 0xf7428e54 ('pair') 195 197 (dumping core). | Aborted | FAIL check-gc (exit status: 134) I have no idea whether the list of installed packages is relevant, but I've attached it. KiBi. adduser adwaita-icon-theme apt apt-utils autoconf automake autopoint autotools-dev base-files base-passwd bash bash-completion bc bf-utf-source binfmt-support binutils bsd-mailx bsdmainutils bsdutils build-essential bzip2 ca-certificates clang-3.5 coreutils cpio cpp cpp-4.8 cpp-4.9 cpp-5 cron dash dbus dconf-gsettings-backend:i386 dconf-service dctrl-tools debconf debconf-i18n debfoster debhelper debian-archive-keyring debiandoc-sgml debianutils devscripts dh-autoreconf dh-python dh-strip-nondeterminism diffstat diffutils dirmngr dmsetup docbook-xml docbook-xsl dosfstools dpkg dpkg-dev e2fslibs:i386 e2fsprogs eatmydata efibootmgr exim4-base exim4-config exim4-daemon-light fakeroot file findutils fontconfig fontconfig-config fonts-dejavu-core g++ g++-4.8 g++-5 gcc gcc-4.7-base:i386 gcc-4.8 gcc-4.8-base:i386 gcc-4.9 gcc-4.9-base:i386 gcc-5 gcc-5-base:i386 gdb gdbserver genext2fs genisoimage gettext gettext-base git git-man glib-networking:i386 glib-networking-common glib-networking-services gnupg gnupg-agent gnupg2 gpgv grep groff groff-base grub-common grub-efi-ia32-bin gsettings-desktop-schemas gzip hicolor-icon-theme hostname htop icu-devtools ifupdown init init-system-helpers initscripts insserv install-info intltool-debian iproute2 isc-dhcp-client isc-dhcp-common isolinux kernel-wedge krb5-locales less libacl1:i386 libapparmor1:i386 libapr1:i386 libaprutil1:i386 libapt-inst2.0:i386 libapt-pkg4.12:i386 libapt-pkg5.0:i386 libarchive-zip-perl libasan0:i386 libasan1:i386 libasan2:i386 libassuan0:i386 libatk-bridge2.0-0:i386 libatk1.0-0:i386 libatk1.0-data libatm1:i386 libatomic1:i386 libatspi2.0-0:i386 libattr1:i386 libaudit-common libaudit1:i386 libauthen-sasl-perl libavahi-client3:i386 libavahi-common-data:i386 libavahi-common3:i386 libbabeltrace-ctf1:i386 libbabeltrace1:i386 libblkid-dev:i386 libblkid1:i386 libbogl-dev libbogl0:i386 libbsd0:i386 libburn4:i386 libbz2-1.0:i386 libc-bin libc-dev-bin libc-l10n libc6:i386 libc6-dbg:i386 libc6-dev:i386 libc6-pic:i386 libcairo-gobject2:i386 libcairo2:i386 libcap-ng0:i386 libcap2:i386 libcc1-0:i386 libcilkrts5:i386 libclang-common-3.5-dev libclang1-3.5:i386 libcloog-isl4:i386 libcolord2:i386 libcomerr2:i386 libconfig-inifiles-perl libcroco3:i386 libcups2:i386 libcurl3-gnutls:i386 libdatrie1:i386 libdb5.3:i386 libdbus-1-3:i386 libdconf1:i386 libdebconfclient0:i386 libdevmapper-dev:i386 libdevmapper-event1.02.1:i386 libdevmapper1.02.1:i386 libdns-export100 libdpkg-perl libdrm2:i386 libeatmydata1:i386 libedit2:i386 libefivar0:i386 libegl1-mesa:i386 libelf-dev:i386 libelf1:i386 libencode-locale-perl libepoxy0:i386 liberror-perl libexpat1:i386 libexpat1-dev:i386 libfakeroot:i386 libfdisk1:i386 libffi-dev:i386 libffi6:i386 libfile-listing-perl libfile-stripnondeterminism-perl libfont-afm-perl libfontconfig1:i386 libfontconfig1-dev:i386 libfreetype6:i386 libfreetype6-dev libfuse2:i386 libgbm1:i386 libgc1c2:i386 libgcc-4.8-dev:i386 libgcc-4.9-dev:i386 libgcc-5-dev:i386 libgcc1:i386 libgcrypt11-dev libgcrypt20:i386 libgcrypt20-dev libgd3:i386 libgdbm-dev libgdbm3:i386 libgdk-pixbuf2.0-0:i386 libgdk-pixbuf2.0-common libglib2.0-0:i386 libgmp10:i386 libgnutls30:i386 libgomp1:i386 libgpg-error-dev libgpg-error0:i386 libgpgme11:i386 libgpm2:i386 libgraphite2-3:i386 libgssapi-krb5-2:i386 libgtk-3-0:i386 libgtk-3-bin libgtk-3-common libgtk2.0-0:i386 libgtk2.0-bin libgtk2.0-common libharfbuzz0b:i386 libhogweed4:i386 libhtml-form-perl libhtml-format-perl libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-daemon-perl libhttp-date-perl libhttp-message-perl libhttp-negotiate-perl libice-dev:i386 libice6:i386 libicu-dev:i386 libicu55:i386 libidn11:i386 libio-html-perl libio-pty-easy-perl libio-pty-perl libio-socket-ip-perl libio-socket-ssl-perl libisc-export95 libisl10:i386 libisl15:i386 libisoburn1:i386 libisofs6:i386 libitm1:i386 libjbig0:i386 libjpeg62-turbo:i386 libjson-glib-1.0-0:i386 libjson-glib-1.0-common libjte1 libk5crypto3:i386 libkeyutils1:i386 libkrb5-3:i386 libkrb5support0:i386 libksba8:i386 liblcms2-2:i386
Re: gb r-bioc-biostrings on mips
Andreas Beckmann(2016-02-21): > gb r-bioc-biostrings_2.38.0-1 . mips mips64el > > the package has an insufficiently versioned B-D on r-bioc-xvector > (#815429), but now a sufficient version is available on all platforms, > so a mips rebuild should succeed in sid. This seems to have happened: mips is built, mips64el is now BD-Uninstallable. KiBi. signature.asc Description: Digital signature
Re: gb mercurial-buildpackage on i386, kfreebsd-i386
Andreas Beckmann(2016-02-21): > gb mercurial-buildpackage_0.10.1 . i386 kfreebsd-i386 > > That build failed more than a year ago with > > [ "0.10.1" = ] > /bin/sh: 1: [: =: argument expected > > I cannot reproduce that in a current sid i386 pbuilder environment. Done, thanks. KiBi. signature.asc Description: Digital signature
Re: Please give back openimageio on amd64
Matteo F. Vescovi(2016-02-22): > Hi team! > > While it was tested to build fine on amd64 debomatic[1], buildd's is > failing badly, and weirdly. > > So it would be great if you could give it a new try to see if the > problem persists. > > > gb openimageio_1.6.10~dfsg0-2 . amd64 Done, thanks. KiBi. signature.asc Description: Digital signature
Re: Please give back babl on mips
Matteo F. Vescovi(2016-02-22): > Build history on mips shows a long list of success[1]. > But not this time, and nothing explain clearly what happened there. > > Could you then give back babl on mips, please? > > gb babl_0.1.16-1 . mips Done, thanks. KiBi. signature.asc Description: Digital signature
Re: Please give back turbojson on arch:all
Hi, Graham Inggs(2016-02-23): > Turbojson builds again since python-peak.rules 0.5a1+r2713-1 was uploaded. > Please give back turbojson on arch:all. > > gb turbojson_1.3.2-2.1 . all Why should it be given back? python-turbojson | 1.3.2-2.1 | unstable | all turbojson| 1.3.2-2.1 | unstable | source KiBi. signature.asc Description: Digital signature
Re: Give back several R packages on mips
Sébastien Villemot(2016-01-15): > Dear Wanna-build team, > > A bug in r-base (#810357) has caused quite a few R packages to FTBFS on > mips. The bug is now fixed, so a give back should now be enough: > > gb r-cran-mime_0.4-2 r-cran-ape_3.4-1 r-cran-scales_0.3.0-1 > r-cran-maps_3.0.2-1 r-cran-timeseries_3022.101.2-1 > r-cran-dosefinding_0.9-13-1 r-cran-statmod_1.4.23-1 r-cran-rms_4.4-1-1 > rjava_0.9-8-1 r-cran-coin_1.1-2-1 r-cran-digest_0.6.9-1 r-cran-afex_0.15-2-1 > r-cran-ncdf4_1.15-1 rcpp_0.12.3-1 r-cran-rjags_1:4-5-1 urca_1.2-9-1 . mips Done, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please give back on kfreebsd-amd64
Steven Chamberlain(2015-12-25): > Dear wanna-build maintainers, > > Please also would you give back: > > gb cmake_3.4.1-2 . kfreebsd-amd64 > gb cmake_3.4.1-2 . kfreebsd-i386 > > since I can't reproduce the FTBFS seen there, but it may FTFBS for a new > reason now. Many of its build-deps were updated on kfreebsd the past > few days. Also: > > gb gmsh_2.10.1+dfsg1-1 . kfreebsd-amd64 > gb gmsh_2.10.1+dfsg1-1 . kfreebsd-i386 > > since we now have OpenJDK as default Java. And: > > gb python-scipy_0.16.1-1 . kfreebsd-i386 > > since that was a transient buildd problem. All those, along with healpy + qtbase-opensource-src, given back. Mraw, KiBi.
Re: Please give back docker.io on arm64
Potter, Tim (Converged Cloud)(2015-11-20): > Hi there. I’m trying to get docker.io built for arm64 and the last build > failed. However a new > version of the golang-github-boltdb-bolt package was uploaded to unstable on > the 11th of > November. I’m hoping this fixes the build, but it hasn’t been run since the > 4th of November. > > Could someone please give back docker.io on arm64 to kick things off again? > > gb docker.io_1.8.3~ds1-2 . arm64 Done, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please giveback elk on i386
Laurent Bigonville(2015-11-14): > Hello, > > Could you please giveback src:elk on i386, I tried to rebuild the pkg in a > i386 chroot and it built successfully. > > gb elk_3.99.8-4 . i386 Done; might be useful to cat the test suite log when a failure happens though? Mraw, KiBi. signature.asc Description: Digital signature
Re: [PATCH:di-autobuild] buildscript: Adjust sed call for dpkg 1.18.3
Hi, Cyril Brulebois <k...@debian.org> (2015-09-28): > This commit in dpkg led to a slightly variation in dpkg-checkbuilddeps's > output: > | commit d287060bb1a45f5de33eb27034a7d8b27b039dbb > | Author: Guillem Jover <guil...@debian.org> > | Date: Thu Sep 17 18:14:00 2015 +0200 > | > | scripts: Use error() and errormsg() instead of printing on STDERR > directly > | > | This way any transformation done for error messages gets applied > | consistently to all error output. > > The new pattern should support both variants. > > Signed-off-by: Cyril Brulebois <k...@debian.org> > --- > buildscript | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > Hi, > > I'm not sure who exactly can pull this, so trying my luck with > debian-wb-team@ for now. > > (No need to tell me how ugly this is.) > > Confirmed to work fine on barriere (except for libpango's udeb being > uninstallable). > > Thanks for your time. > > Mraw, > KiBi. > > > diff --git a/buildscript b/buildscript > index fb35920..f787db4 100755 > --- a/buildscript > +++ b/buildscript > @@ -60,7 +60,7 @@ install_build_deps() { >dd-schroot-cmd -c "$SID" apt-get update >( > LANG=C schroot -q -c "$SID" -d "$HOME/di/build/$(basename > "$INSTALLER_DIR")/checkout/build" -p -r -- dpkg-checkbuilddeps -B > ../debian/control 2>&1 || true > - ) | sed -e 's%dpkg-checkbuilddeps: Unmet build dependencies: %%' -e 's, > *([^)]*),,g' \ > + ) | sed -e 's%dpkg-checkbuilddeps: \(error: \)*Unmet build dependencies: > %%' -e 's, *([^)]*),,g' \ > | DEBIAN_PRIORITY=critical DEBIAN_FRONTEND=noninteractive xargs > dd-schroot-cmd -c "$SID" -y apt-get install > } It's been a few days without any daily builds so I've decided to apply my patch on all linux and kfreebsd porterboxes, after adjusting some bits: - missing http.sslCAinfo parameter on one; - missing merge from origin/porterbox for some. I'll take care of git rebasing (or resetting) all of them once a patch lands into origin. Since I've applied this a few hours after the usual “0 0” crontab entry, I've manually started builds as well. Stuff should show up on the d-i daily build overview page soon: http://d-i.debian.org/daily-images/daily-build-overview.html Mraw, KiBi. signature.asc Description: Digital signature
Re: I screwed up, how do I recover?
Hi, Andrew Pollock(2015-09-24): > I accidentally built grpc 0.11.0.0-1~bpo8+1 against unstable. So I built > grpc 0.11.0.0-1~bpo8+2 against stable and uploaded it. > > Rereading http://backports.debian.org/Contribute/ it looks like that's not > what I should have done, and it may explain why a day later > 0.11.0.0-1~bpo8+2 hasn't hit the buildds or anything. > > How should I fix this? The .changes looks correct to me, and your package got accepted: | kibi@franck:~$ grep grpc_0.11.0.0-1~bpo8+2_amd64.changes /srv/ftp-master.debian.org/log/current | 20150922213919|process-upload|dak|Processing changes file|grpc_0.11.0.0-1~bpo8+2_amd64.changes | 20150922213922|process-upload|dak|ACCEPT|grpc_0.11.0.0-1~bpo8+2_amd64.changes | | kibi@franck:~$ dak ls grpc|grep jessie | grpc | 0.11.0.0-1~bpo8+1 | jessie-backports| source | grpc | 0.11.0.0-1~bpo8+2 | buildd-jessie-backports | source | grpc | 0.11.0.0-1~bpo8+2 | jessie-backports| source I'm not sure why it's not seen by buildds/wanna-build according to [1] so I'm cc-ing debian-wb-team@ to get their input. 1. https://buildd.debian.org/status/package.php?p=grpc=jessie-backports Mraw, KiBi. signature.asc Description: Digital signature
Re: Please give back gcc-python-plugin on ppc64el
Erwan Prioul er...@linux.vnet.ibm.com (2015-08-10): Hello, There was a file missing in gcc-5-plugin-dev that caused gcc-python-plugin to FTBFS on ppc64el architecture. This has been fixed in gcc-5-plugin-dev 5.2.1-15. Please give back gcc-python-plugin on ppc64el. gb gcc-python-plugin_0.14-4 . ppc64el Done, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: please give back krb5 on arm64
Benjamin Kaduk ka...@mit.edu (2015-08-10): https://buildd.debian.org/status/package.php?p=krb5 says it's been instate 'building' for 45 days, on arm-arm-03, which seems implausible. Probably it just needs another go at it. Done, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: globus-gridftp-server stuck in Built on ppc64el fir 7 days
Mattias Ellert mattias.ell...@fysast.uu.se (2015-06-28): It is not progressing to Uploaded an Installed. Can someone give it a push? Mattias Giving it back resulted in a successful build but no-reupload AFAICT by looking at queued's log. The .upload file might need removal. Some other packages have been stuck in Uploaded state for several days. Cc-ing ppc64el@buildd.d.o to get some action on this side. Mraw, KiBi. signature.asc Description: Digital signature
Re: please give back libuv (0.10.28-6) on i386
Luca Bruno lu...@debian.org (2015-02-27): Please give back libuv 0.10.28-6 on i386. It is a minimal security fix upload intended for jessie, already unblocked by the release team. Its test-suite failed yesterday for the first time on babin, while building everywhere else. The failure seems to be somehow time sensitive. I suspect that it will just build if retried. Done, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: [patch] remove .upload files on re-build of a package
Andreas Barth a...@ayous.org (2014-10-15): diff --git a/lib/Buildd/Mail.pm b/lib/Buildd/Mail.pm index cff1880..9741955 100644 --- a/lib/Buildd/Mail.pm +++ b/lib/Buildd/Mail.pm @@ -576,6 +576,7 @@ sub prepare_for_upload ($$) { my $pkg_noep = $pkg; $pkg_noep =~ s/_\d*:/_/; my $changes_name = $pkg_noep . _ . $changes_filename_arch . .changes; +my $upload_name = $pkg_noep . _ . $changes_filename_arch . .upload; for my $upload_dir (@upload_dirs) { if (! -d $upload_dir !mkdir( $upload_dir, 0750 )) { @@ -597,6 +598,7 @@ sub prepare_for_upload ($$) { } } + system(rm -f -- $upload_dir/$upload_name); perldoc -f unlink open( F, $upload_dir/$changes_name ); print F $changes; close( F ); Mraw, KiBi. signature.asc Description: Digital signature
Re: Please give back billiard on kfreebsd-i386
Sebastian Ramacher sramac...@debian.org (2014-10-14): Please give back billiard on kfreebsd-i386. I did a test build on fischer and it succeeded. It seems like the Python build stack picks the right compiler again. gb billiard_3.3.0.18-2 . kfreebsd-i386 Done, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: give-back git-annex on amd64
Joey Hess jo...@debian.org (2014-09-28): This is blocking a security fix from reaching testing. Build log shows that the linker was killed with signal 9, which seems most likely to be an OOM kill or some other system event. gb git-annex_5.20140927 . amd64 Done. There's also a missing mips build, but it's in the building state right now. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please give-back libpipeline/hurd-i386
Colin Watson cjwat...@debian.org (2014-09-28): Hi, libpipeline failed on hurd-i386 with a test timeout. It builds fine on exodar.debian.net and that test takes under a second to run (info check says that the default test timeout is four seconds), so I wonder if the buildd was just under unusual load at the time? Please give it back. gb libpipeline_1.3.1-1 . hurd-i386 Since it was in the 'Failed' state, an override is needed: kibi@wuiet:~$ wb gb libpipeline . hurd-i386 . -o * libpipeline/hurd-i386 | libpipeline: not taken for building (state is Failed). | libpipeline: Forcing give-back (TL;DR: done.) Mraw, KiBi. signature.asc Description: Digital signature
Re: Please give back efl on kfreebsd-amd64
Steven Chamberlain ste...@pyro.eu.org (2014-09-28): Hi, Please give back efl for another build on kfreebsd-amd64 It apparently timed out during a 'DNS resolution' test, which I tried but couldn't reproduce locally. Done. Mraw, KiBi. signature.asc Description: Digital signature
Re: kfreebsd-kernel-headers_10.1~1_source.changes ACCEPTED into experimental
Steven Chamberlain ste...@pyro.eu.org (2014-09-01): On 31/08/14 20:18, Debian FTP Masters wrote: kfreebsd-kernel-headers (10.1~1) experimental; urgency=medium . * Update for 10.1 * Add myself to uploaders This package seems to have disappeared from wanna-build? It was in Needs-Build state for several hours, the build depends should be satisfiable, but it just disappeared from the queue and there is no log? It was a source-only upload to experimental, was never held in the NEW queue, and does not build any arch-indep packages. Could anyone explain where it went? /srv/upload.debian.org/queued/log.2014-08.xz says: Aug 31 19:14:16 processing /kfreebsd-kernel-headers_10.1~1_source.changes Aug 31 19:14:17 kfreebsd-kernel-headers_10.1~1_source.changes processed successfully (uploader debian-...@lists.debian.org) /srv/ftp-master.debian.org/log/2014-08.xz says: 20140831191852|process-upload|dak|Processing changes file|kfreebsd-kernel-headers_10.1~1_source.changes 20140831191857|process-upload|dak|ACCEPT|kfreebsd-kernel-headers_10.1~1_source.changes /srv/ftp-master.debian.org/log/2014-09 says: 2014090815|clean-suites|dak|set lastused|ftp-master|k/kfreebsd-kernel-headers/kfreebsd-kernel-headers_10.1~1.tar.xz 2014090815|clean-suites|dak|set lastused|ftp-master|k/kfreebsd-kernel-headers/kfreebsd-kernel-headers_10.1~1.dsc 2014090926|manage-build-queues|dak|removed source from build queue|accepted|kfreebsd-kernel-headers|10.1~1 2014090930|manage-build-queues|dak|removed source from build queue|buildd-experimental|kfreebsd-kernel-headers|10.1~1 20140901113319|clean-suites|dak|set lastused|build-queues|k/kfreebsd-kernel-headers/kfreebsd-kernel-headers_10.1~1.dsc 20140901113319|clean-suites|dak|set lastused|build-queues|k/kfreebsd-kernel-headers/kfreebsd-kernel-headers_10.1~1.tar.xz 20140901144930|clean-suites|dak|delete archive file|/srv/ftp-master.debian.org/public/incoming.debian.org/web/debian-buildd/pool/main/k/kfreebsd-kernel-headers/kfreebsd-kernel-headers_10.1~1.dsc 20140901144930|clean-suites|dak|removed file|/srv/ftp-master.debian.org/public/incoming.debian.org/web/debian-buildd/pool/main/k/kfreebsd-kernel-headers/kfreebsd-kernel-headers_10.1~1.dsc 20140901144930|clean-suites|dak|delete archive file|/srv/ftp-master.debian.org/public/incoming.debian.org/web/debian-buildd/pool/main/k/kfreebsd-kernel-headers/kfreebsd-kernel-headers_10.1~1.tar.xz 20140901144930|clean-suites|dak|removed file|/srv/ftp-master.debian.org/public/incoming.debian.org/web/debian-buildd/pool/main/k/kfreebsd-kernel-headers/kfreebsd-kernel-headers_10.1~1.tar.xz 20140901144948|clean-suites|dak|removing directory|/srv/ftp-master.debian.org/public/incoming.debian.org/web/debian-buildd/pool/main/k/kfreebsd-kernel-headers Adding ftpmaster to the loop. Mraw, KiBi. signature.asc Description: Digital signature
Re: agda dep-waits
Colin Watson cjwat...@debian.org (2014-08-10): agda is failing on hurd-i386 and powerpc because haskell-quickcheck uses an overly-restrictive test to decide whether it needs to build the Test.QuickCheck.All module. I've just uploaded 2.7.6-3 to fix this; could you please set the following dep-wait so that agda will be retried at the appropriate time? dw agda_2.4.0.2-1 . hurd-i386 powerpc . -m 'libghc-quickcheck2-dev (= 2.7.6-3)' Done, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: [p-a-s/sid] remove many packages with explicit architecture list
Andreas Barth a...@ayous.org (2014-05-01): --- Packages-arch-specific | 182 +--- 1 file changed, 1 insertion(+), 181 deletions(-) Did you check the P-a-s entry and the arch list for each package matched? raw, KiBi. signature.asc Description: Digital signature
Re: dose-debcheck on wuiet
Joachim Breitner nome...@debian.org (2014-02-10): Dear Wanna-Build team, TL;DR: apt-get install dose-debcheck on wuiet, please given that edos-debcheck is broken with stuff like Depends: python:any (http://bugs.debian.org/727550#15), can we have dose-debcheck installed on wuiet? My haskell-binNMU-script constantly tries to rebuild haskell-glade despite it being installable – it’s just that edos-debcheck doesn’t see that. You probably want to send a patch against debian/control (“Package: debian.org-buildd.debian.org”) to debian-admin@: https://db.debian.org/git/debian.org.git Mraw, KiBi. signature.asc Description: Digital signature
grieg back up, please sync your data *now*
Hi people, as you probably all know, grieg went shopping, and got replaced by wuiet some time ago. Somebody managed to get grieg up again, so if there's anything you want to sync from it, I suspect *NOW* is the time. I can't speak for DSA, but I think the plan is to zero it and kill it off. Mraw, KiBi. @Mehdi: Explicitly sending to you since you wondered about home dirs not so long ago. signature.asc Description: Digital signature
Re: Please give-back python-apt 0.8.9.1 on armel
Julian Andres Klode j...@debian.org (2013-10-08): It seems there was some temporary issue; namely a .list file in the /tmp directory, which python-apt unfortunately uses as a sources.list.d directory during testing; and thus an unexpected source ended up in the test, causing it to FTBFS. I suspect you want to get that fixed at some point, though, using a temp directory below $(CURDIR) would be better than relying on what (not) to find under /tmp? Mraw, KiBi. signature.asc Description: Digital signature
Re: Please give-back audacity on armel
Sebastian Ramacher sramac...@debian.org (2013-09-23): Hi wb-team, audacity failed to build on armel because soundtouch silently changed some typedefs on armel which broke libsoundtouch0's ABI and audacity's hardcoded assumptions on the involved types. This has now been fixed in libsoundtouch0, so please give-back audacity on armel: gb audacity_2.0.4-1 . armel Thanks for the bugfix, and for the notice. Given back. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-wb-team-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130923010357.ga26...@mraw.org
Re: build logs of cluster3
Thorsten Alteholz deb...@alteholz.de (2013-09-17): Hi, on 2013-09-16 I uploaded a new version of the cluster3 package and now I am missing build logs for that package. Not only those from the last upload but all from the first upload as well. Is this related to the outage of grieg or do I have a different problem? The same problem seems to appear with package abyss. I think it's totally unrelated. That's a non-free package, it isn't autobuilt, so no logs from the buildds. See main page: https://buildd.debian.org/ As for the upload you performed, no logs are attached, so they don't show up either. Those packages don't appear to be known from the wanna-build DB at all: | kibi@wuiet:~$ wb info abyss . ALL | W: can't get version info for abyss/amd64 | W: can't get version info for abyss/armel | W: can't get version info for abyss/armhf | W: can't get version info for abyss/hurd-i386 | W: can't get version info for abyss/i386 | W: can't get version info for abyss/ia64 | W: can't get version info for abyss/kfreebsd-amd64 | W: can't get version info for abyss/kfreebsd-i386 | W: can't get version info for abyss/mips | W: can't get version info for abyss/mipsel | W: can't get version info for abyss/powerpc | W: can't get version info for abyss/s390 | W: can't get version info for abyss/s390x | W: can't get version info for abyss/sparc | kibi@wuiet:~$ wb info cluster3 . ALL | W: can't get version info for cluster3/amd64 | W: can't get version info for cluster3/armel | W: can't get version info for cluster3/armhf | W: can't get version info for cluster3/hurd-i386 | W: can't get version info for cluster3/i386 | W: can't get version info for cluster3/ia64 | W: can't get version info for cluster3/kfreebsd-amd64 | W: can't get version info for cluster3/kfreebsd-i386 | W: can't get version info for cluster3/mips | W: can't get version info for cluster3/mipsel | W: can't get version info for cluster3/powerpc | W: can't get version info for cluster3/s390 | W: can't get version info for cluster3/s390x | W: can't get version info for cluster3/sparc But someone else will certainly expand on that. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please give back libgtk2-perl on kfreebsd-i386
intrigeri intrig...@debian.org (2013-08-08): libgtk2-perl failed to build on kfreebsd-i386 a while ago. I suspect the test suite was terminated because it took too long. Today, I've successfully built the package in a sid chroot on fischer.d.o, so I'd like to see if the build error was temporary, due to performance issue on the buildd at that time, or anything else. So, please give-back libgtk2-perl on kfreebsd-i386. If it happens to be scheduled on the same buildd and fail, I suggest we give-back it again on a faster buildd, if available. We can't select the buildd it's getting tried on. gb libgtk2-perl_2:1.247-2 . kfreebsd-i386 Done. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-wb-team-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130809141901.gb27...@mraw.org
Re: Request to give back globus-xio 3.3-2 on armel
Mattias Ellert mattias.ell...@fysast.uu.se (05/06/2013): I would like to ask for a giveback of globus-xio 3.3-2 on armel According to the log the build failed due to a glitch in a call to doxygen: /bin/bash: line 10: 26994 Illegal instruction /usr/bin/doxygen Doxyfile Done. Mraw, KiBi. signature.asc Description: Digital signature
Re: building libcoro-perl with a fixed libanyevent-perl
Niko Tyni nt...@debian.org (19/05/2013): libcoro-perl_6.310-1 failed to build on several architectures due to #708730 in libanyevent-perl. That's now fixed, so please gb libcoro-perl_6.310-1 . kfreebsd-amd64 kfreebsd-i386 mips mipsel sparc dw libcoro-perl_6.310-1 . kfreebsd-amd64 kfreebsd-i386 mips mipsel sparc . -m 'libanyevent-perl (= 7.040-3) Hope I got that right. Yep; the former isn't needed though, since 'dw' implies 'gb'. ;) Done. Mraw, KiBi. signature.asc Description: Digital signature
Re: give back gdcm on ia64
Mathieu Malaterre ma...@debian.org (06/05/2013): wheezy is out, please move gdcm from unstable to testing ! gb gdcm_2.2.3-1 . ia64 I'd rather see an ia64 buildd admin look into this part: | /build/buildd-gdcm_2.2.3-1-ia64-HV0wLK/gdcm-2.2.3/obj-ia64-linux-gnu/Wrapping/Python/gdcmswigPYTHON_wrap.cxx:100622:1: fatal error: error writing to /tmp/ccXjZpVV.s: No space left on device Not sure whether your package is too space-hungry and/or the buildd needs a clean-up. Mraw, KiBi. signature.asc Description: Digital signature
Re: please give-back atlas until it is successfully built everywhere #4
Andreas Beckmann a...@debian.org (02/05/2013): gb atlas_3.8.4-9.1 . armel armhf Sigh, done. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please, give back freecad on amd64, experimental
Anton Gladky gladky.an...@gmail.com (12/01/2013): I have just successfully rebuilt the package on amd64-box in clean environment. Please, try to restart the build again. I'd rather see the box admin check the chroot first. Might be due to some package version skew. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please, give back freecad on amd64, experimental
Anton Gladky gladky.an...@gmail.com (11/01/2013): freecad failed to build on amd64 in experimental branch. On other (even slow) platforms it is built fine. Please, try to rebuild. gb freecad_0.13~20130106.gitafb3355-exp1 . amd64 What about that? /usr/bin/ld: cannot find -lgfortran Mraw, KiBi. signature.asc Description: Digital signature
Re: Please give back gcc-mingw-w64 (so it rebuilds using gcc-4.6 4.6.3-12)
Hi, Stephen Kitt st...@sk2.org (14/10/2012): Now that gcc-4.6 4.6.3-12 is installed in unstable on all architectures, would it be possible to give gcc-mingw-w64 back on all buildds? This will cause it to be rebuilt using gcc-4.6 4.6.3-12; since the latter's version ends up in the resulting binary packages' versions, a binNMU shouldn't be necessary... gb gcc-mingw-w64_7 . ALL a package which failed to build can be given back. That's really an alias for “please give it another chance to build (successfully)”. If you want to get a(n already successfully built) package rebuilt against a new set of packages, that's where binNMUs come into play. Mraw, KiBi. signature.asc Description: Digital signature
Re: Requesting give-back for alpine
Asheesh Laroia ashe...@asheesh.org (06/07/2012): gb alpine_2.02+dfsg-1 . mips Done, thanks. Let me know if that is the right syntax, and if this is the right contact address. (I'm attempting to follow the instructions here: http://release.debian.org/wanna-build.txt ). That's all right. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please give back firebird2.5 on ia64
Hello Damyan, redirecting to ia64@buildd.d.o + wb team: Damyan Ivanov d...@debian.org (03/07/2012): Due to #679680 in libatomic-ops-dev, firebird2.5 failed to build on ia64. The bug is fixed in version 7.3~alpha1+git20120701-1, but I am not sure what would be the best way to ensure that it is present on the buildd. Adding a versioned build-dependency would mean firebird2.5 won't be buildable in wheezy (and it built before with the wheezy version if libatomic-ops-dev), and I can't figure out the --dep-wait wb usage. In any case, the give-back command would be: wb gb firebird2.5_2.5.2~svn+54698.ds4-1 . ia64 Mraw, KiBi. signature.asc Description: Digital signature
Re: Please gb openturns on mips
D. Barbier bou...@gmail.com (18/06/2012): I modified debian/rules to not build python libraries in parallel on mipsel, in order to reduce memory constraints. It built fine on mipsel (but it may be also that swarm has more RAM than other mipsel buildds), but failed on mips for the same reason. I will also disable parallel building of python libraries on mips by the next upload, but all other architectures are now built, can you please give back openturns on mips? gb openturns_1.0-4 . mips Done. Mraw, KiBi. signature.asc Description: Digital signature
Re: gnucash 'BD-Uninstallable' on hurd-i386
Micha Lenk mi...@debian.org (13/06/2012): But the package libgoffice-0.8-dev (= 0.8.17-1.1+b1) seems to be available in the archive since almost two months now, as could be seen here: https://buildd.debian.org/status/package.php?p=goffice So I would expect that gnucash should be in state 'Needs-Build' instead. Is there anything that I am missing? Available doesn't mean installable: http://edos.debian.net/edos-debcheck/results/unstable/1339560240/hurd-i386/list.php#libgoffice-0.8-dev This package isn't binNMU-safe: Package: libgoffice-0.8-8 Depends: […] libgoffice-0.8-8-common (= ${binary:Version}) […] Package: libgoffice-0.8-8-common Architecture: all → kaboom. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please give back parrot on ia64
Alessandro Ghedini al3x...@gmail.com (10/06/2012): parrot 4.3.0-1 build failed on ia64, but I couldn't reproduce the failure on merulo.d.o. Could you please give it back? gb parrot_4.3.0-1 . ia64 Sure, done. -- perl -E '$_=q;$/= @{[@_]};and s;\S+;inidehG ordnasselA;eg;say~~reverse' -- perl -e 'print Mraw,\nKiBi\n' signature.asc Description: Digital signature
Re: Please give back gdcm on armel/mipsel
Mathieu Malaterre ma...@debian.org (30/05/2012): vtk has been recently fixed to not store full path to lib […] Finally! gb gdcm_2.2.0-12 . armel mipsel Done, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please gb presage 0.8.7-2 on armel and kfreebsd-i386
Aron Xu happyaron...@gmail.com (29/05/2012): It still FTBFS, should it be gb again or what to do? Given back one more time. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please give back evtest 1:1.30-1 on ia64, mips and mipsel
Stephen Kitt st...@sk2.org (29/05/2012): evtest was bitten by the old zlib1g packages on some ia64, mips and mipsel buildds (#673297). Since the chroots have been upgraded, it should be safe to gb evtest_1:1.30-1 . ia64 mips mipsel Done, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please gb openturns on mipsel
D. Barbier bou...@gmail.com (28/05/2012): Unfortunately rem picked it up again and failed, can you please requeue it? gb openturns_1.0-3 . mipsel I'll leave that up to the buildd maintainers. ISTR they can --take it, which {c,sh}ould help pick the “right” buildd. Mraw, KiBi. signature.asc Description: Digital signature
Re: please retry db5.3 on kfreebsd-amd64
Petr Salinger petr.salin...@seznam.cz (27/05/2012): it builds fine for me. Given back, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: please retry smartmontools on kfreebsd-*
Petr Salinger petr.salin...@seznam.cz (27/05/2012): It builds fine for me in current sid. Done too, but please don't reuse threads; it makes tracking requests harder. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please gb openturns on mipsel
D. Barbier bou...@gmail.com (27/05/2012): Please give back openturns on mipsel, rem tried to build it but this package needs more RAM. gb openturns_1.0-3 . mipsel Given back again. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please give back openturns on s390
D. Barbier bou...@gmail.com (25/05/2012): Swig 2.0.6 had been quickly released to fix it, and is now available on s390, please give back openturns 1.0.3 on s390: gb openturns_1.0-3 . s390 Done. I am not involved at maintaining the packages below, but I guess that gdcm could be rebuilt too gb gdcm_2.2.0-12 . s390 Done. and hugin (from experimental) also failed: gb hugin_2011.4.0+dfsg-1 . s390 Done earlier after a mail to -release@. Thanks for the heads-up. I meant to check what happened on the swig side, then got stuck doing other things and forgot until now. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please give back mysql-connector-c++
Rene Engelhard rene.engelh...@gmx.de (26/05/2012): mysql-connector-c++ git csught by the mysql_config ssl bug so please dw mysql-connector-c++_1.1.0-4 . armel armhf hurd-i386 i386 ia64 powerpc sparc . - m libmysqlclient-dev (= 5.5.23+dfsg-1) With s/- m/-m/, done. Thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please retry xapian-core on sparc
Olly Betts o...@survex.com (24/05/2012): gb xapian-core_1.2.10-2 . sparc Done. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please restart build of unar 1.1-1 on amd64
Julián Moreno Patiño darkju...@gmail.com (24/05/2012): I saw a amd64 FTBFS in unar some days ago: https://buildd.debian.org/status/fetch.php?pkg=unararch=amd64ver=1.1-1stamp=1336880985 You shouldn't be linking with gcc -lstdc++, but with g++ directly. I suggest you perform a maintainer upload fixing that. Mraw, KiBi. signature.asc Description: Digital signature
Re: Re-try sparc build of boost1.49
Steve M. Robbins st...@sumost.ca (22/05/2012): So I'd like to re-try the build on a machine *other than* stadler.debian.org. This needs manual intervention. gb boost1.49_1.49.0-3 . sparc That I can do. Done. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please gb shelxle 1.0.551-1 on mipsel
Aron Xu happyaron...@gmail.com (19/05/2012): On Sat, May 19, 2012 at 8:18 PM, Aron Xu happyaron...@gmail.com wrote: shelxle 1.0.551-1 failed on mipsel with an error saying undefined reference to gzopen64 in libxml2.so, but I cannot reproduce the problem on eder.d.o, so I'd like to ask you to give it back and try again. gb shelxle_1.0.551-1 . mipsel Done. The chroots might need an upgrade or something. Buildd maintainers didn't bother replying to me on that topic past times, let's see how it goes… Mraw, KiBi. signature.asc Description: Digital signature
Re: Please gb presage 0.8.7-2 on armel and kfreebsd-i386
Aron Xu happyaron...@gmail.com (19/05/2012): Package presage failed to build on armel and kfreebsd-i386, the problems seem to be a glitch of doxygen on armel, and insufficiency of memory on kfreebsd-i386, so I'd like to ask you give back it on the two architectures. gb presage_0.8.7-2 . armel kfreebsd-i386 doxygen is a big, fat PITA, at least on armel… Done, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: Give back kdenlive on ia64 and mipsel
Patrick Matthäi pmatth...@debian.org (19/05/2012): on ia64 and mipsel kdenlive 0.9-1 FTBFSed because of: /usr/lib/ia64-linux-gnu/libxml2.so.2: undefined reference to `gzopen64@ZLIB_1.2.3.3' Giving it back on both architectures should be enough to let them build. Done, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please restart build of s3d 0.2.2-8 on mipsel
Sven Eckelmann s...@narfation.org (15/05/2012): it seems that there was a temporary problem with cmake 2.8.8-1. This problem should be fixed now with 2.8.8-2 (2.8.8-3 is in testing) gb s3d_0.2.2-8 . mipsel Done, thanks. Mraw, KiBi. signature.asc Description: Digital signature
Re: [ftpmas...@ftp-master.debian.org: ffmpeg_0.5.8-1_mipsel.changes REJECTED]
Moritz Mühlenhoff j...@inutil.org (13/05/2012): Please give-back ffmpeg_0.5.8-1 on mipsel for stable-security. I think that's the issue Andreas has fixed/is fixing. Packages should be reuploaded. Mraw, KiBi. signature.asc Description: Digital signature
Re: Please give back cxxtools on sparc
Kari Pahula k...@debian.org (11/05/2012): gb cxxtools_2.1-1 . sparc Done. Mraw, KiBi. signature.asc Description: Digital signature
Re: Give back rakudo 0.1~2012.01-1 on armel
Alessandro Ghedini al3x...@gmail.com (06/05/2012): the rakudo 0.1~2012.01-1 build on armel was terminated after a few hours of apparent inactivity. Since I see no problem when building it on QEMU, could you please give it back? gb nqp_0.1~2012.01-1 . armel I'm giving back rakudo instead. ;-) Also, I'm not sure if you can do anything about it, but the nqp 0.1~2012.01-5 package has been Needs-Build on mipsel for a few days, then it built successfully [0], but now it is Needs-Build again. Is there anything wrong with it? Note that it is preventing rakudo from building on mipsel too. Wild guess, it was built on the machine which died, so he has to be built again. Mraw, KiBi. signature.asc Description: Digital signature
Re: Slightly outdated 'armel' build machine
Hi Dmitry, Dmitry Smirnov dmitry.smir...@member.fsf.org (07/05/2012): I've noticed that 'armel' build environment is slightly outdated. Recent upload of 'mc' package FTBFS on armel [1] due to outdated libslang2/libslang2-dev packages which were fixed recently but somehow two slang2 uploads did not make it to 'armel' build machine. According to 'libslang2' package page [2], version 2.2.4-10 should be available on armel but build server still have broken libslang2-dev 2.2.4-8 (already installed). adding ar...@buildd.debian.org to Cc, which point at people responsible for those chroots; should be debian-wb-team@ readers, but let's make sure. ;-) Mraw, KiBi. signature.asc Description: Digital signature
Re: Give back freemat_4.0-5 on sparc
Anton Gladky gladky.an...@gmail.com (02/05/2012): gb freemat_4.0-5 . sparc There is a strange internal compiler error: Segmentation fault only on this platform. Done. Mraw, KiBi. signature.asc Description: Digital signature
Re: give back gdcm on sparc
Mathieu Malaterre ma...@debian.org (16/04/2012): gb gdcm_2.2.0-10 . sparc Done. Mraw, KiBi. signature.asc Description: Digital signature