Hi,
while reporting #1070498 I noticed that the build succeeded on some
buildds (x86-grnet-02, arm-conova-04, zandonai) that have
HOME=/var/lib/sbuild
instead of
HOME=/sbuild-nonexistent
cu
Adrian
On Sat, Jan 06, 2024 at 10:02:18AM +0100, Paul Gevers wrote:
> Hi,
Hi Paul,
> On 05-01-2024 18:08, Aurelien Jarno wrote:
> > I have just given it back, let's see what happens.
>
> Didn't help.
it did.
> I asked rmadison:
> paul@mulciber ~ $ rmadison gcc-mingw-w64-i686-posix --suite=unstable
>
On Sat, Oct 21, 2023 at 07:08:34PM +0200, Sebastian Ramacher wrote:
> Hi Adrian
Hi Sebastian,
> On 2023-10-20 08:30:21 +0200, Sebastian Ramacher wrote:
> > On 2023-10-19 18:00:29 +0300, Ilias Tsitsimpis wrote:
> > > > Do you need help from us?
> > >
> > > Can you please schedule the necessary
https://buildd.debian.org/status/logs.php?pkg=gcc-mingw-w64=26.1=s390x=sid
The way the logs are cut might indicate that zani has 37 GB diskspace
that are exhausted?
I've failed the package for now, please verify whether this is really a
diskspace issue and then either fix it on the buildd or
On Fri, Sep 08, 2023 at 04:26:26PM +0200, Philipp Kern wrote:
> On 07.09.23 11:00, Adrian Bunk wrote:
> > Examples:
> > https://buildd.debian.org/status/package.php?p=guile-3.0
> > https://buildd.debian.org/status/package.php?p=libpsl
> >No entry in loong64 da
Examples:
https://buildd.debian.org/status/package.php?p=guile-3.0
https://buildd.debian.org/status/package.php?p=libpsl
No entry in loong64 database, check Packages-arch-specific
These packages are "Architecture: any" not in Packages-arch-specific,
with no obvious reason why they aren't being
On Fri, Aug 18, 2023 at 11:28:07AM +0200, Stéphane Glondu wrote:
> Hi,
>
> ocaml-fdkaac has stayed in state BD-Uninstallable since its upload two days
> ago. buildd.debian.org says it build-depends on missing libfdk-aac-dev
> (which is in non-free but available).
>
> Is there some subtlety I'm
On Sun, Aug 13, 2023 at 04:22:50PM +0200, Aurelien Jarno wrote:
> Hi,
Hi Aurelien,
> incoming.d.o is not really the area of the wb-team, but let me answer
> you with my DSA hat.
thanks.
>...
> > A side-effect of this issue is that dep-wait might not ensure a recent
> > enough version is
Hi,
a problem that has already happend in recent days but is exceptionally
frequent today are buildd timeouts from incoming.d.o, e.g.[1]
Could not connect to incoming.debian.org:443 (2603:400a::bb8::801f:3e),
connection timed out Could not connect to incoming.debian.org:443
On Fri, Jul 14, 2023 at 11:03:39AM +0100, Adam D. Barratt wrote:
> Hi Adrian,
Hi Adam,
> While checking the status of the linux upload to proposed-updates this
> morning, I noticed that the packages for mipsel and mips64el were still
> in the BD-Uninstallable state, whereas those for some other
https://buildd.debian.org/status/package.php?p=r-cran-sf=trixie
https://buildd.debian.org/status/package.php?p=r-cran-terra=trixie
https://buildd.debian.org/status/package.php?p=r-cran-rgdal=trixie
These are the first binNMUs in trixie, but some configuration for that
seems to be missing.
cu
On Mon, Jun 26, 2023 at 04:35:50AM -0400, Jeffrey Walton wrote:
> Hi Everyone,
Hi Jeffrey,
> I'm a fan of PPC and PPC64. I'm interested in helping get some of the
> packages to build from
> https://buildd.debian.org/status/architecture.php?a=ppc64=sid.
>
> My area of expertise is C and C++.
>
On Fri, Feb 24, 2023 at 12:27:35PM +0100, Emilio Pozuelo Monfort wrote:
> On 24/02/2023 09:48, Adrian Bunk wrote:
> > On Fri, Feb 24, 2023 at 09:19:40AM +0100, Emilio Pozuelo Monfort wrote:
> > > ...
> > > Also note that one of the concerns was for armhf, which is now b
On Fri, Feb 24, 2023 at 09:19:40AM +0100, Emilio Pozuelo Monfort wrote:
>...
> Also note that one of the concerns was for armhf, which is now being built
> from arm64 buildds.
>...
On armhf there is a 4 GB FTBFS for the future (like on i386),
and a 3 GB FTBFS today that still seems to be present
On Tue, Nov 22, 2022 at 02:08:25PM +, Graham Inggs wrote:
> > 3 days ago mipsel-osuosl-04 started building pyfftw/mips64el.
> > The build never finished, and mipsel-osuosl-04 is down since then.
> >
> > 11 hours ago mipsel-manda-05 started building pyfftw/mips64el.
> > The build never
3 days ago mipsel-osuosl-04 started building pyfftw/mips64el.
The build never finished, and mipsel-osuosl-04 is down since then.
11 hours ago mipsel-manda-05 started building pyfftw/mips64el.
The build never finished, and mipsel-manda-05 is down since then.
cu
Adrian
On Sat, Nov 12, 2022 at 11:42:20PM +0100, Aurelien Jarno wrote:
>...
> On 2022-11-12 23:04, Adrian Bunk wrote:
>...
> > Sebastian, was there any real-world problem motivating your commit,
> > or did it just sound more correct?
> >
> > With default settings there
On Fri, Nov 11, 2022 at 07:15:59PM +0100, Manuel A. Fernandez Montecelo wrote:
>...
> The origins of this bug report are because there are sometimes problems
> building
> packages in buildds, the compression phase is very slow and sometimes the
> build
> is aborted due to inactivity:
>
> E:
Package: ftp.debian.org
Severity: grave
X-Debbugs-Cc: debian-wb-team@lists.debian.org, Thomas Goirand
https://buildd.debian.org/status/logs.php?pkg=golang-github-grpc-ecosystem-go-grpc-middleware=1.3.0-1=all=experimental
The three Maybe-Failed until November 3rd at the bottom are normal FTBFS.
On Thu, Oct 27, 2022 at 07:50:17PM +0800, YunQiang Su wrote:
> YunQiang Su 于2022年10月26日周三 01:56写道：
> >
> > Adrian Bunk 于2022年10月25日周二 21:50写道：
> > >
> > > https://buildd.debian.org/status/logs.php?pkg=gcc-12=mips64el
> > >
> > > ...
> > &g
https://buildd.debian.org/status/logs.php?pkg=gcc-12=mips64el
...
Finished
I: Built successfully
chmod: cannot access
'/<>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal3/filesystem-test.FSLTZS-last_write_time':
Value too large for defined data type
chmod: cannot access
On Mon, Oct 10, 2022 at 09:20:52PM +0200, Samuel Thibault wrote:
> Adrian Bunk, le lun. 10 oct. 2022 21:51:25 +0300, a ecrit:
> > Control: severity -1 serious
> >
> > [ adding debian-wb-team to Cc ]
> >
> > On Fri, Oct 07, 2022 at 01:55:41PM +0200, Samuel Thibau
Control: severity -1 serious
[ adding debian-wb-team to Cc ]
On Fri, Oct 07, 2022 at 01:55:41PM +0200, Samuel Thibault wrote:
> Control: severity -1 important
>
> Andreas Beckmann, le ven. 07 oct. 2022 13:38:15 +0200, a ecrit:
> > Justification: fails to build from source (but built
On Wed, Sep 14, 2022 at 01:38:01PM +0200, Guillem Jover wrote:
>...
> [ Mostly to summarize the status re dpkg. ]
>...
> * Lack of bits/endianness arch "aliases" (#962848). The main problem
> with this one is that we cannot simply add such aliases, as then
> those would silently be
On Mon, Sep 12, 2022 at 04:08:08PM +0200, Tobias Frost wrote:
>...
> The problem is that if you want to exclude an arch explicitly, you have to
> list all archs you want to build it on. IOW, I'm missing an easy way to say
> "not on THIS architecture", somthing like "[!armel]"
>...
> I don't
On Sun, Sep 11, 2022 at 05:08:57PM +0200, Samuel Thibault wrote:
>...
> The issue we see is that some DDs end up setting a hardcoded list in
> the "Architecture" field, rather than just letting builds keep failing
> on these archs (and then possibly succeeding after some time whenever
> somebody
On Sun, Sep 11, 2022 at 09:25:40PM +0200, Samuel Thibault wrote:
> Paul Gevers, le dim. 11 sept. 2022 21:16:08 +0200, a ecrit:
> >
> > - color packages that "never" had a successful built on an architecture
> > different. That information is already available because that's what marks
> > the
On Sun, Jul 17, 2022 at 09:02:23PM +0200, Moritz Mühlenhoff wrote:
>...
> but the quickly vaninishing
> upstream support for i386 and the lack of active porters make i386
> problematic from the Security Team's point of view.
>
> For packages where new upstream releases are being introduced
> this
On Fri, Aug 21, 2020 at 02:08:44PM +0200, Sylvain Beucler wrote:
> Hello,
>
> ghostscript failed to build on armhf for stretch-security:
> https://buildd.debian.org/status/fetch.php?pkg=ghostscript=armhf=9.26a%7Edfsg-0%2Bdeb9u7=1597941103=0
> "./soobj/dxmainc.o: file not recognized: File
# arnold seems to have had some problem uploading in May 2019
gb rcpp_1.0.0-1~bpo9+1 . armel armhf . stretch-backports
gb r-cran-spatstat.utils_1.13-0-1~bpo9+1 . armel armhf . stretch-backports
gb lme4_1.1-20-3~bpo9+1 . armel . stretch-backports
gb r-cran-stringi_1.2.4-2~bpo9+1 . armhf .
# was building when all machines at ARM went down
gb qemu_1:2.1+dfsg-12+deb8u9 . armel armhf . jessie-security
# retry build failures of packages that are in jessie
gb nsis_2.46-10+deb8u1 . armhf . jessie-security
gb postgis_2.1.4+dfsg-3+deb8u1 . i386 . jessie-security
Thanks in advance
Adrian
On Sat, Apr 07, 2018 at 07:40:04PM +0200, Philipp Kern wrote:
> On 4/7/18 1:47 PM, Adrian Bunk wrote:
> > # Builds in reproducible [1]
> > gb ruby-crb-blast_0.6.9-1 . all
> >
> > Thanks
> > Adrian
> >
> > [1]
> > https://tests.reproducib
# Builds in reproducible [1]
gb ruby-crb-blast_0.6.9-1 . all
Thanks
Adrian
[1]
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-crb-blast.html
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for
#894025 is now fixed
gb python-certbot-apache_0.23.0-1 . all
gb python-certbot-nginx_0.23.0-1 . all
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
gb adios_1.13.0-2 . armhf alpha m68k x32
gb tumbler_0.2.0-2 . armhf
gb ayatana-indicator-power_2.0.93-2 . amd64 arm64 armel i386 mips mips64el
mipsel powerpc ppc64el s390x alpha hppa ia64 m68k sh4 x32
Thanks in advance
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly
#866354 is a libstdc++6 ABI change in gcc 6 -> 7 only affecting armel
caused by the #727621 backport to the stretch gcc (the symbols in the
backport to gcc-6 and in upstream gcc >= 7 are at different versions).
Cases where binNMUs are required are handled in #874124.
Breaks for stretch -> buster
#871567 is fixed
gb mlpcap_0.9-17 . ppc64el
#871354 is fixed
gb aspectj-maven-plugin_1.10-1 . all
gb jdependency_1.2-1 . all
gb maven-compiler-plugin_3.6.2-1 . all
# victim of the cython breakage caused by #873791
gb python-intbitset_2.3.0-2 . all amd64 arm64 i386 mips mipsel ppc64el s390x
On Mon, Jul 03, 2017 at 04:37:34PM +0200, Steinar H. Gunderson wrote:
> On Mon, Jul 03, 2017 at 11:32:17AM -0300, Lisandro Damián Nicanor Pérez Meyer
> wrote:
> > I have uploaded qtbase with a backported patch that should fix this. Please
> > ask for a give back with a dep wait on
#854610 libsofthsm2 is not installable because of wrong libssl dependency
This looks like being caused by building in an unclean chroot.
Who is responsible for backports binNMUs, in this case for libsofthsm2
on amd64?
Thanks
Adrian
--
"Is there not promise of rain?" Ling Tan asked
On Tue, Mar 21, 2017 at 04:45:02PM +, Wookey wrote:
> On 2017-03-20 01:49 +0200, Adrian Bunk wrote:
> > With debhelper >= 9.20160114 running dh_update_autotools_config
> > automatically, all (or at least most) of the following should
> > now build:
>
> Thank
On Mon, Mar 20, 2017 at 10:10:07AM -0300, Breno Leitao wrote:
> Hi Adrian,
Hi Breno,
> On Mon, Mar 20, 2017 at 01:49:08AM +0200, Adrian Bunk wrote:
> > # ppc64el needs -o to override Failed
> > gb lft_2.2-4 . arm64 ppc64el
>
> I gave back this package
With debhelper >= 9.20160114 running dh_update_autotools_config
automatically, all (or at least most) of the following should
now build:
gb tcpreen_1.4.4-2 . arm64
gb mcrypt_2.6.8-1.3 . arm64
gb subnetcalc_2.1.3-1 . arm64
gb id-utils_4.6+git20120811-4 . arm64
gb netperfmeter_1.2.3-1 . arm64
gb
Below are various give-backs, many of the armel/armhf ones were build
failures caused by #853793.
I will do further actions (often filing RC bugs) on packages that
still fail when retrying.
gb libbson_1.5.4-1 . mips mipsel
gb gmerlin-avdecoder_1.2.0~dfsg-9 . armel armhf
gb
On Sat, Jan 28, 2017 at 03:59:45PM -0300, Martín Ferrari wrote:
> On 28/01/17 11:58, Adrian Bunk wrote:
> > Source: prometheus
> > Version: 1.5.0+ds-1
> > Severity: serious
> >
> > https://buildd.debian.org/status/fetch.php?pkg=prometheus=armhf=1.5.0%2Bds-1=14
Packages in this list:
- source upload >= 7 days ago
- no RC bugs in the package
- I cannot exclude the possibility that it might now build
I will do further actions (often filing RC bugs) on packages that
still fail when retrying.
gb rcpp_0.12.9-1 . mips64el
gb qevercloud_3.0.3+ds-2 . mips64el
Packages in this list:
- source upload >= 10 days ago
- no RC bugs in the package
- I cannot exclude the possibility that it might now build
I will do further actions (often filing RC bugs) on packages that
still fail when retrying.
gb guile-2.0_2.0.13+1-4 . mipsel
gb google-perftools_2.5-2 .
Packages in this list:
- source upload >= 7 days ago
- no RC bugs in the package
- I cannot exclude the possibility that it might now build
I will do further actions (often filing RC bugs) for all packages that
still fail after retrying.
gb prometheus-alertmanager_0.5.1+ds-1 . amd64 s390x
gb
Packages in this list:
- source upload > 15 days ago
- no RC bugs in the package
- I cannot exclude the possibility that it might now build
I will do further actions (often filing RC bugs) for all packages that
still fail after retrying.
gb libwebp_0.5.1-3 . armhf
gb yadifa_2.2.2-1 . ppc64el
gb
Packages in this list:
- source upload > 30 days ago
- no RC bugs in the package
- I cannot exclude the possibility that it might now build
I will file RC bugs for all packages that still fail after retrying.
gb ergo_3.5-1 . mips mipsel
gb psi4_1:1.0-1 . armel mips mipsel
gb gss-ntlmssp_0.7.0-1
https://buildd.debian.org/status/package.php?p=consul
Please give back consul on arm64,
Go stuff is changing so quickly that I don't want to submit an RC bug
for a 5 months old build FTBFS without checking that it still fails.
gb consul_0.6.4~dfsg-3 . arm64
Thanks in advance
Adrian
--
50 matches
Mail list logo
