Package: src:libconfig-model-openssh-perl
Version: 2.9.4.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh
Package: src:libconfig-model-lcdproc-perl
Version: 2.055-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh
Package: src:kalzium
Version: 4:22.12.3-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with kf5
Package: src:gnome-bluetooth3
Version: 42.7-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:libapi-gitforge-perl
Version: 0.007-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build
Package: src:gcr4
Version: 4.1.0-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:gccintro
Version: 1.0-4
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build
Package: src:gcc-11-doc
Version: 11.3.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build
Package: src:emacs-wgrep
Version: 3.0.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with elpa
Package: src:dosbox
Version: 0.74-3-4
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:emacs-web-server
Version: 1.5.1-5
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with
Package: src:elpa
Version: 2022.11.001-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build
Package: src:emacs-helm-ag
Version: 0.59-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build --with elpa
Package: src:dradio
Version: 3.8-2.1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build
dh: warning:
Package: src:cvs
Version: 2:1.12.13+real-29
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary -Snone
Package: src:d2x-rebirth
Version: 0.58.1-1.3
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
dh_auto_clean: warning: Compatibility
Package: src:d1x-rebirth
Version: 0.58.1-1.2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
dh_auto_clean: warning: Compatibility
Package: src:crowdsec
Version: 1.4.6-6
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:cloud-init
Version: 23.3.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
py3versions: no
Package: src:cclib-data
Version: 1.6.2-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with
Package: src:calamares-extensions
Version: 1.3.2-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:barrier
Version: 2.4.0+dfsg-4
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:bosh
Version: 0.6-11
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary
Package: src:astroquery
Version: 0.4.6+dfsg-4
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
dh_auto_clean
I: pybuild base:310:
Package: src:ap-utils
Version: 1.5-5
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build
reopen 1052899
fixed 1052899 1.1.2-1
tags 1052899 + fixed-in-experimental
thanks
Hi. This is currently happening in trixie and sid:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-fido2.html
In cases like this one, it's better to keep the bug open, as packages in
Version: 0.0~git20210309.652d3b4-2
Hello.
For a long time, I was doing archive rebuilds using an absolutely
minimal /etc/hosts file with only two lines: one for localhost
and another one for the hostname.
After I added the IPv6 lines that debian-installer creates
by default, several packages
The second patch is merely the result of running the script.
Note: The patches are relative to the version in trixie/sid,
where this problem should be fixed first.
Thanks.commit 6699c65d1b7a891d16cab082e4e0c7d083568f34
Author: Santiago Vila
Date: Sun Dec 3 22:36:00 2023 +0100
generat
El 30/11/23 a las 19:26, Bruno Haible escribió:
hello.c: In function 'main':
hello.c:31:63: warning: implicit declaration of function 'getpid'
[-Wimplicit-function-declaration]
31 | printf (_("This program is running as process number %d."), getpid
());
|
El 29/10/23 a las 14:08, cage escribió:
Maybe this reports could be useful someway:
https://savannah.gnu.org/bugs/?64748
Yes, it helped.
But I was unable to reproduce the bug.
So what I did is to apply all the patches for po-mode from git
(the one in the URL above and others). I assume that
Hello.
I've received the report below from the Debian bug system.
To fix it, I tried applying the following two patches to the 0.21 version:
https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commit;h=95ac95545141d1d72638dd3995c0171d8ad34f77
El 30/11/23 a las 5:56, Vladimir Petko escribió:
Package: gettext
Version: 0.21-13
Severity: important
X-Debbugs-Cc: vladimir.pe...@canonical.com
Dear Maintainer,
When build the package in sid chroot with `sbuild -c sid-amd64` the package
fails to build from source due to the failure of
reassign 1057009 crash
found 1057009 8.0.3+ds1
thanks
El 27/11/23 a las 21:59, Guillaume Morin escribió:
Package: hello
Version: 8.0.3+ds1
Severity: wishlist
Hello,
crash 8.0.4 has fixes for Linux 6.4+. Considering Linux 6.5 is availabe
in sid, it would be useful to have it packaged.
Thank
Source: ticketbooth
Version: 1.0.3.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During an incremental rebuild of all packages in trixie, this
package failed to build from source:
3/3 =
test: Validate
; urgency=medium
+
+ * Team upload.
+ * Apply patch by Michael R. Crusoe to request a single core
+in the tests. Closes: #1031192.
+
+ -- Santiago Vila Tue, 21 Nov 2023 00:35:00 +0100
+
toil (5.9.2-2) unstable; urgency=medium
* Add patch to handle errors when testing on ec2.
diff -Nru toil
Package: src:python3-onelogin-saml2
Version: 1.12.0-3
Severity: important
I've recently fixed a build error related to expired certificates
used in the tests. However, I see that the current package in unstable
will FTBFS in the future:
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: python3-onelogin-sa...@packages.debian.org, sanv...@debian.org
Control: affects -1 + src:python3-onelogin-saml2
[ Reason ]
This upload fixes Bug #1036255: FTBFS due
Source: python-ase
Version: 3.22.1-3
Severity: serious
Tags: ftbfs
Dear maintainer:
During an incremental rebuild of all packages in trixie,
this package failed to build:
[...]
/<>/doc/about.rst:51: ERROR: Broken link: :git:`COPYING`:
Non-existing path: ../COPYING
/<>/doc/about.rst:51: ERROR:
owner 1036255 !
thanks
El 18/5/23 a las 20:36, Andrey Rakhmatullin escribió:
https://github.com/SAML-Toolkits/python-saml/commit/a6a21109179571c9ca23f92e03017759741603c2
looks like a fix for this, though I haven't tested it.
Thanks a lot for the hint. Yes, such commit was the beginning of the
El 23/9/23 a las 23:05, Alexandre Detiste escribió:
Source: conda-package-handling
Version: 2.2.0-1
Severity: minor
User: python3-...@packages.debian.org
Usertags: python3-six-removal
conda-package-handling as been cleaned up from Python2/six code
severity 1002789 serious
thanks
Hello. This bug has been hidden for me because the package
had a missing build-dependency on tzdata (#1031362). Such bug
is now reassigned to libpython3.11-stdlib, where it probably belongs.
Now, when I build the package in bookworm using a chroot with
tzdata
+
+ * Team upload.
+ * Disable flaky test. Closes: #976506.
+
+ -- Santiago Vila Fri, 17 Nov 2023 11:30:00 +0100
+
conda-package-handling (1.7.2-2) unstable; urgency=medium
* Team upload.
diff --git a/debian/patches/series b/debian/patches/series
index 3d1dca5..b36fda0 100644
--- a/debian
tags 1027378 + bullseye
thanks
Hello. I see that back in February you reopened this bug
"for stable" (meaning bullseye at the time).
I'm adding this tag mainly for documentation purposes, but
I personally lost my hope to see bugs like this one fixed in bullseye,
as there are too many of them
retitle 1029423 libpython3.11-stdlib: missing dependency on tzdata
retitle 1029424 libpython3.11-stdlib: missing dependency on tzdata
retitle 1029430 libpython3.11-stdlib: missing dependency on tzdata
retitle 1031362 libpython3.11-stdlib: missing dependency on tzdata
thanks
# This reassign documents the fact that all those bugs are really #1037168,
# not bugs in the affected packages.
#
reassign 1029423 libpython3.11-stdlib
reassign 1029424 libpython3.11-stdlib
reassign 1029430 libpython3.11-stdlib
reassign 1031362 libpython3.11-stdlib
fixed 1029423 3.11.5-1
fixed
tags 1029430 - unreproducible
thanks
Hello. I'm going to reassign this to libpython3.11-stdlib
for the reasons explained in #1037168.
Before doing so, however, I'm attaching these two build logs
as a reference. One of them has tzdata in the chroot and the other
does not. This was indeed
Package: src:sunpy
Version: 4.1.2-1
Severity: serious
Tags: ftbfs bookworm upstream
Dear maintainer:
During a rebuild of all packages in bookworm, this package failed to build.
The error I got is the same in reproducible-builds:
A more simple approach would be to modify debian/rules so that
(all) the tests are skipped after a certain date,
as in the attached patch.
Thanks.--- a/debian/rules
+++ b/debian/rules
@@ -7,6 +7,9 @@ export PYBUILD_TEST_ARGS=../../../ndcube
export http_proxy=127.0.0.1:9
export HOME=$(shell
s, in pseudocode:
skipif(currentdate >
hardcoded-expiration-date-of-leapsecond-file-at-upload-time)
but I don't really know if it worth the effort.
I'm tagging this as "upstream" because I believe there should be an easier way
to deal with this.
Thanks.commit 079219c8ad4bc798065a285
Package: src:intel-graphics-compiler
Version: 1.0.12504.6-1
Severity: serious
Tags: ftbfs bookworm
Control: close -1 1.0.15136.3-1
Dear maintainer:
During a rebuild of all packages in bookworm, this package failed to build
with the following error:
cd /<>/build/IGC/VectorCompiler/lib/BiF &&
El 25/7/23 a las 23:32, Jonathan Wiltshire escribió:
This request was approved but not uploaded in time for the previous point
release (11.7). Should it be included in 11.8 or should this request be
abandoned and closed?
Hi. Since the debdiff was already approved by you (RMs), I've just
to 1 so that the package may be
+built on systems with a single core. Closes: #1055625.
+
+ -- Santiago Vila Sun, 12 Nov 2023 23:25:00 +0100
+
pyzoltan (1.0.1-5) unstable; urgency=medium
* Standards version bumped to 4.6.1 (non changes).
diff -Nru pyzoltan-1.0.1/debian/rules pyzoltan
found 1054449 116-1
found 1054449 116-5
affects 1054449 src:shim
thanks
Hi. In commit e38e2a8af632a660d3c01a936796622fce186020
it looks that you added passwd to the Build-Depends.
The bug (after preinst moved to postinst) was about adding it
to the Depends field.
In fact, the changelog was
Note: The build does not hang when using sbuild
with a chroot of type "file", like this:
[bookworm-file]
type=file
profile=sbuild
description=Debian bookworm
file=/chroot/bookworm.tar.gz
groups=sbuild
root-groups=sbuild
preserve-environment=true
Previously, I was using a chroot of type
Package: schroot
Version: 1.6.13-3
Dear maintainer:
Files copyfiles and nssdatabases at /etc/schroot/buildd
have duplicate entries. For example, this is copyfiles:
---
# Files to copy into the chroot from the host system.
#
# [ ]
tags 1055625 + patch
thanks
Ok, thanks to the fact that the package is reproducible, I've just
checked that the package builds the same regardless of NPROCS
being set to 1 or 2 in debian/rules.
Therefore, we can build it using NPROCS = 1 for everybody,
and nothing is lost. As I said before,
tags 1054849 + bookworm
thanks
I'm adding this tag because I see Adrian has just added version in bookworm
using "found". The package indeed FTBFS in bookworm in reproducible-builds:
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/arm64/haskell-clash-prelude.html
However, I
Package: src:pyzoltan
Version: 1.0.1-5
Severity: important
Tags: ftbfs
Dear maintainer:
During a mass-rebuild of all packages in bookworm, this
package failed to build in this way:
[...]
raise RuntimeError(msg)
E RuntimeError: test geometric_partitioner.py failed with
Note: I should also include some changes in debian/salsa-ci.yml and gbp.conf.
The final debdiff may differ slightly in that minor detail only.
Thanks.
by switching to autopkgtest-pkg-pybuild. Closes: #1033822.
+ [ Bastian Germann ]
+ * Fix OpenSSL version parsing, take 1.
+ [ Arnaud Rebillout ]
+ * Fix OpenSSL version parsing, take 2. Closes: #1055598.
+
+ -- Santiago Vila Wed, 08 Nov 2023 21:38:44 +0100
+
oscrypto (1.3.0-1) unstable
Note: I've asked Paul Gevers if it's desirable/recommended to fix
autopkgtests in stable when fixing FTBFS bugs in stable.
If yes, we should include the changes in -2 too.
Thanks.
Package: src:oscrypto
Version: 1.3.0-1
Severity: serious
Tags: ftbfs
Control: close -1 1.3.0-4
Hello. This package currently FTBFS in bookworm:
[...]
oscrypto.errors.LibraryNotFoundError: Error detecting the version of libcrypto
[...]
Full log here:
El 8/11/23 a las 14:42, kyriah.picc...@easymailer.live escribió:
Package: base-files
Severity: normal
Dear Maintainer,
/efi is a replacement for the historical and now discouraged ESP (EFI System
Partition) mountpoint /boot/efi.
Systemd upstream agrees:
tags 1031024 + bookworm
thanks
Hi.
I'd like to see this fixed in bookworm, as I'm trying to keep bookworm
free of FTBFS bugs like this one.
Since I'm not a big fan of NMUs, I propose the attached diff to be uploaded
to bookworm. If it's ok for you, you can use it "as is". Also, if you prefer
tags 1055490 - wontfix
thanks
Hi. Thanks a lot for caring about your own bug.
I prefer not to use wontfix here. I reserve such tag
for bugs which are actually bugs but we prefer not
to fix for some reason.
Thanks.
El 7/11/23 a las 9:23, Mathieu Malaterre escribió:
In man page author name is
Franc,ois
when, in an UTF-8 system (default in etch), it should be
François
Quite funny when you realize that `recode` is exactly about encoding :)
Hello. This and many other bugs will be fixed in recode 3.7 or
Hi. Just FYI: After the upload, the package is currently
BD-Uninstallable on hurd-amd64:
https://buildd.debian.org/status/package.php?p=mpi-defaults=sid
(I guess this should be fixed somewhere else).
Thanks.
owner 1050845 !
owner 1055458 !
thanks
El 6/11/23 a las 20:13, Samuel Thibault escribió:
AIUI the debian/control part is auto-generated.
Oh, I see. There is a control.in and a control (mandated by policy),
and dpkg-buildpackage aborts if control is not ok.
I use a similar trick in base-files
El 6/11/23 a las 19:01, Samuel Thibault escribió:
Source: mpi-defaults
Version: 1.14
Severity: important
Tags: patch
Hello,
Could you apply the attached patch to add hurd-amd64 support?
Hello. There is a very similar request here for loong64:
Well, I finally disabled dh_auto_test on single-cpu systems.
(The exit status would be ignored anyway).
Somebody else should look at the test suite some day, as
I'm not a user of rclone myself.
Thanks.
affects 1037168 src:jc
affects 1037168 src:kopeninghours
affects 1037168 src:python-pycdlib
affects 1037168 src:reposurgeon
affects 1037168 src:gnucash
thanks
Those packages above show libpython3.11-stdlib in
their build logs and have a "missing BD:tzdata" bug.
I'm also including gnucash (not
Note: I'd like to see this fixed in stable, but RMs require
(rightly so) that this is fixed in unstable first.
Thanks. You may look into disabling prody's part which uses biopython, maybe
this will make it easier to fix the comparison issue in unstable. I don't know
whether this is possible,
tags 1037168 + bookworm
thanks
Hello. I'm not reopening this bug, but I also think it would be good
to have it fixed in bookworm in a point release, for consistency.
There are a number of packages which FTBFS in bookworm if we follow
Policy 4.2 strictly, because they have a missing BD on
Hello Luca.
Thanks a lot for implementing this!
I'm going to answer to an old message of yours, because
I think that things have changed a little bit since then.
El 18/10/23 a las 19:17, Luca Boccassi escribió:
We can do an upload, but note that it won't have any effect on package
builds,
Version: 1.6.13-3
El 2/8/22 a las 15:28, Guillem Jover escribió:
On Sat, 2012-01-28 at 09:26:03 +0100, Marc Haber wrote:
To allow this, the COPYFILES functionality could be changed to allow
two file names per line. If only one is given, behavior is not
changed, preserving
severity 1051924 serious
thanks
Hi. I also found this. Raising to serious, as it's a FTBFS bug.
Thanks.
severity 1030904 serious
thanks
Actually, this fails more than 80% of the time for me,
on machines with 2 CPUs from Hetzner, and I also
get failures on AWS.
Moreover, it fails in reproducible-builds:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libgovirt.html
And there
reopen 1041491
tags 1041491 + bookworm
fixed 1041491 0-1335+ds-1.1
thanks
Hello. I'm reopening this because packages in stable must build in stable.
Cc:ing all involved parties: Please keep FTBFS bugs open when they happen
in stable, otherwise they become a lot more difficult to find, as they
hang, just try GRUB_CMDLINE_LINUX="nr_cpus=1"
in /etc/default/grub.
Thanks.commit fbad1ce77ea0410d14b015e3cf2a8e0c72ba78cc
Author: Santiago Vila
Date: Thu Nov 2 11:09:41 2023 +0100
Skip tests when DEB_BUILD_OPTIONS has parallel=1, because the machine hangs
in such case.
diff --
Version: 2.3.1-2~deb10u1
I no longer have access to the Scaleway machines on which this
used to fail (randomly), so there is no point in keeping this open.
Closing with version in buster.
Thanks.
Version: 0.0~git20161104.0.a20c98e-1+bullseye
There is little point in keeping this open. I'm closing it
using a fake version number (as ftpmaster would do) to indicate
that it does no longer happen in bullseye (because in fact
the package does not even exist in bullseye).
Thanks.
El 13/10/23 a las 8:04, Andrius Merkys escribió:
To summarize: The failing test is buggy because when it fails
it does not necessarily mean that the package was misbuilt,
and in my opinion the best thing to do would be to disable it,
both in stable and unstable.
Trivial patch in the second
Version: 0.18.0-1
El 8/2/22 a las 9:50, s3v escribió:
Dear Maintainer,
astroid (versioned as 2.8.4-1) added runtime dependency to
python3-typing-extensions [1][2] and your package actually builds fine.
Unfortunately no intervention was performed in time and khard was
removed from testing
El 1/11/23 a las 16:37, Chris Lamb escribió:
Chris Lamb wrote:
However, if you don't see these files when you "dpkg -c" the .deb
files, that suggests something strange is going on...
I am seeing them, at least:
$ dget --quiet golang-github-go-git-go-git-dev
$ dpkg -c
severity 1000401 normal
thanks
El 22/11/21 a las 16:55, Chris Lamb escribió:
Source: golang-github-go-git-go-git
Version: 5.4.2-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
El 31/10/23 a las 11:23, Michael R. Crusoe escribió:
> (Ok, I *can* checkout such tag, but the fact that I can't
> see it in a normal way makes me to suspect there may be
> something wrong).
>
> (Maybe it is because I have a personal dislike for non-linear
> history in git, but I don't
El 30/10/23 a las 21:16, Johannes Schauer Marin Rodrigues escribió:
Quoting Luca Boccassi (2023-10-18 19:17:40)
We can do an upload, but note that it won't have any effect on package
builds, given the buildds use stable/oldstable
actually we forgot something here. The upload *does* have an
are only skipped when the system has a single CPU.
+Closes: #1030885.
+
+ -- Santiago Vila Sun, 29 Oct 2023 21:45:00 +0100
+
python-cogent (2023.2.12a1+dfsg-2) unstable; urgency=medium
* Restrict to 64 bit architectures
diff -Nru
python-cogent-2023.2.12a1+dfsg/debian/patches/fix-build
El 29/10/23 a las 14:20, Mark Hindley escribió:
Lucas,
I am afraid I still cannot reproduce this.
I attach my successful .buildinfo. What are the differences to yours?
Hello. The problem is that failed builds do not produce .buildinfo files,
so we can't compare buildinfo files in this case.
Dear Release Managers:
Please reject the upload I made for bookworm.
Following the suggestion from Holger, I've fixed this issue
in the optimal way in unstable:
https://tracker.debian.org/news/1474401/accepted-python-cogent-2023212a1dfsg-4-source-into-unstable/
and now I'd like to upload the
El 29/10/23 a las 7:59, Mike Gabriel escribió:
ERROR:./tests/test-geonames.c:110:assert_first_names: assertion failed (geonames_city_get_country
(city) == expected_country): ("United States of America" == "\303\211tats Unis")
not ok /translations -
El 28/10/23 a las 18:48, Santiago Vila escribió:
Just put it inside your chroot replacing /usr/bin/make.
I forgot, sorry: you will also need this in the environment to enable shuffle:
export GNUMAKEFLAGS=--shuffle
but for some reason I did not even need that to reproduce the problem.
Thanks.
El 28/10/23 a las 17:44, Bdale Garbee escribió:
Lucas Nussbaum writes:
During a rebuild of all packages in sid, your package failed to build
on amd64.
I am unable to reproduce this problem building in a fresh, minimal sid
chroot environment. Is this a repeatable failure? If so, any
El 28/10/23 a las 3:27, gregor herrmann escribió:
Lucas, maybe it would make sense to update your chroots to the
usr-merged flavour, as that seems to be the default now?
He knows :-)
https://salsa.debian.org/lucas/collab-qa-tools/-/issues/2
Thanks.
El 28/10/23 a las 0:18, gregor herrmann escribió:
On Fri, 27 Oct 2023 23:53:22 +0200, Lucas Nussbaum wrote:
My build chroot is still unmerged. I think it's the same on the buildd.
I don't think the latter is still the case but I don't have the
capacity to keep all usr-merge details in my
El 27/10/23 a las 19:36, Sam Hartman escribió:
Yep, it's some sort of DNS issue. A kind developer gave me access to a
similarly configured machine on which I can reproduce the problem.
Outside the chroot:
PING ip-10-84-234-64(ip-10-84-234-64 (fe80::816:edff:fe35:ded1%ens5)) 56
data bytes
64
El 18/8/23 a las 11:33, Simon McVittie escribió:
Does your archive rebuild infrastructure build other things in parallel on
the same machine,
Usually yes, however...
or any other factor like that which could make it more
likely to get stuck / take a long time than a production buildd?
it
severity 105458 normal
thanks
El 26/10/23 a las 13:51, jaylaa.maldon...@allfreemail.net escribió:
Package: cream
Version: 0.43-3.1
Severity: serious
Dear Maintainer,
cream depends on non-existent package gvim, which is a policy violation. Please
fix.
Have you actually tried to install
Hello.
I've checked and this seems to be enough to reproduce the hang on any system:
taskset -c 0 dpkg-buildpackage -uc -us -b
My proposal to fix the FTBFS bug, since the exit status for
dh_auto_test is already ignored, would be not to run the tests
at all on systems on which we know the build
Version: 1.53.3-1
Hello.
I'm closing this bug with the version in bullseye because the
random FTBFS failures I experienced at the time do not happen
anymore in bullseye.
Unfortunately, there is now a different FTBFS problem
in bookworm and trixie which I still would like to address:
501 - 600 of 6087 matches
Mail list logo
