Source: slurm-wlm
Version: 23.11.4-1.4
X-Debbugs-CC: bdr...@debian.org, vor...@debian.org, mckins...@debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of slurm-wlm the autopkgtest of slurm-wlm fails in
testing when that
Source: slurm-wlm
Version: 23.11.4-1.4
X-Debbugs-CC: bdr...@debian.org, vor...@debian.org, mckins...@debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of slurm-wlm the autopkgtest of slurm-wlm fails in
testing when that
Hi,
On 22-04-2024 10:39 a.m., Andreas Beckmann wrote:
Nice. Is there a chance to get isolation-machine supported on salsa.d.o,
too?
I don't know. I'm not involved with salsa.
For this concrete case it may be as simple as adding dependency on sudo.
In case it is trivial for you to rerun the
Control: severity -1 serious
Control: retitle -1 erfs: no longer functional, should be removed
Hi
On 22-04-2024 1:37 p.m., Skyper x wrote:
The erfs service was shut down and this tool is no longer functional. It should
be removed.
Please file an RM bug against the ftp.debian.org pseudo
Hi Holger,
On 22-04-2024 9:05 a.m., Holger Wansing wrote:
A patch for above two issues is attached (against the bookworm branch; any
such changing needs to be ported to master/trixie as well).
Feel free to push. Bonus points if you remove the deleted text from
translations too (where you're
Hi Holger,
On 22-04-2024 9:05 a.m., Holger Wansing wrote:
A patch for above two issues is attached (against the bookworm branch; any
such changing needs to be ported to master/trixie as well).
Feel free to push. Bonus points if you remove the deleted text from
translations too (where you're
Hi
On 22-04-2024 1:40 p.m., RL wrote:
I think that whole chapter [2] could be
improved.
Can we please do this for trixie only? Changing the text now is going to
kill translations.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
Source: fuse-zip
Version: 0.5.0-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list to
Source: ganeti-instance-debootstrap
Version: 0.16-8
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
Source: firejail
Version: 0.9.72-2
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list to
Hi
On 21-04-2024 5:56 p.m., Sebastian Andrzej Siewior wrote:
The problem is that libcrypt-smime-perl < 0.29 fails with openssl >= 3.2.0.
This was solved by the Perl team with their 0.29 upload. This and 0.30
didn't migrate to testing and in the meantime we got OpenSSL into
unstable which relies
Hi
On 21-04-2024 5:56 p.m., Sebastian Andrzej Siewior wrote:
The problem is that libcrypt-smime-perl < 0.29 fails with openssl >= 3.2.0.
This was solved by the Perl team with their 0.29 upload. This and 0.30
didn't migrate to testing and in the meantime we got OpenSSL into
unstable which relies
Source: erfs
Version: 1.4-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list to use
Source: drm-info
Version: 2.6.0-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list to
Source: dpdk-kmods
Version: 0~20230205+git-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to
Hi,
On 21-04-2024 1:59 p.m., Martin-Éric Racine wrote:
That service unit is provided by systemd-timesyncd, which systemd
recommends. Basically, unless your testing environment explicitly
installs another package providing time-daemon, this shouldn't happen,
since systemd would have pulled
Source: dahdi-linux
Version:
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list to use
Source: openssl, libcrypt-smime-perl
Control: found -1 openssl/3.2.1-3
Control: found -1 libcrypt-smime-perl/0.28-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of openssl the autopkgtest of
Source: openssl, libcrypt-smime-perl
Control: found -1 openssl/3.2.1-3
Control: found -1 libcrypt-smime-perl/0.28-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of openssl the autopkgtest of
Source: daemontools
Version: 1:0.76-10
X-Debbugs-CC: debian...@bugs.debian.org
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for
Source: dm-writeboost
Version: 2.2.16-0.1
X-Debbugs-CC: a...@debian.org
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64
Source: dhcpcd
Version: 1:10.0.6-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list to
Hi,
On 18-04-2024 10:25 p.m., Paul Gevers wrote:
I'll hopefully do the changes tomorrow. (RL work is a bit busy at the
moment.)
The test ran. Unfortunately zfs-test-suite-1 failed.
https://ci.debian.net/packages/z/zfs-linux/unstable/amd64/45683824/
4089s Results Summary
4089s PASS 681
Hi,
On Sun, 7 Apr 2024 11:54:35 +0200 Paul Gevers wrote:
153s crash: /usr/lib/debug/boot/vmlinux-6.6.15-amd64: no.gnu_debuglink section
153s 153s crash: /usr/lib/debug/boot/vmlinux-6.6.15-amd64: no
debugging
data available
Interestingly the test passes in unstable, stable and oldstable. So
Hi,
On 20-04-2024 3:22 p.m., Lucas Nussbaum wrote:
The following packages have unmet dependencies:
sbuild-build-depends-main-dummy : Depends: libreoffice-draw-nogui but it is
not installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.
I recall rene
Hi,
On 20-04-2024 3:22 p.m., Lucas Nussbaum wrote:
The following packages have unmet dependencies:
sbuild-build-depends-main-dummy : Depends: libreoffice-draw-nogui but it is
not installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.
I recall rene
Hi,
On 14-04-2024 5:14 a.m., 陈 晟祺 wrote:
I would have aron to review & upload a new version, then we can test on
debci infra and see whether it solves the problem.
I forgot I promised changes to the settings. Without those changes, it
doesn't end nicely:
Hi Dirk,
On 18-04-2024 4:41 a.m., Dirk Eddelbuettel wrote:
I uploaded a first
beta release r-base_4.3.3.20240409-1 to 'experimental' a week ago, I just
followed up with a rc release r-base_4.3.3.20240416-1.
Thanks for preparing in experimental, as that triggers some QA.
Given these
Hi,
On 09-04-2024 6:23 p.m., Paride Legovini wrote:
* runner/autopkgtest talks to the backend with a simple text
protocol. While this enables users to add another backend without
changes to the src:autopkgtest code trivially, the drawback of that
is loosing all nuance of what really is going on
Hi,
On 09-04-2024 6:23 p.m., Paride Legovini wrote:
PS: would it be worth it to enable dashboards for autopkgtest on
salsa to manage this project? I assume issues on salsa are disabled
on purpose to avoid bug reports in multiple places. Could we make
adding issues project members only?
I'm in
Hi,
On 14-04-2024 5:14 a.m., 陈 晟祺 wrote:
When using non-ramdisk tmpdir (/var/tmp) and some large tests skipped [1],
the tests would run with 2 core + 4GB memory + ~10GB disk space.
I also tried 2GB / 3GB, and both will be interrupted by OOM killer.
So, let's settle on 2+4 for now. That sounds
Source: oscar4
Version: 5.2.0+dfsg-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: oscar4
Version: 5.2.0+dfsg-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: mdevctl
Version: 1.3.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed
Source: mdevctl
Version: 1.3.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed
reopen -1
reassign -1 debci
On 12-04-2024 7:03 a.m., Paul Gevers wrote:
On Thu, 4 Apr 2024 12:06:16 +0200 Paul Gevers wrote:
I tried to run with the new --lxcpath option but it fails:
"""
admin@ci-worker01:~$ /usr/bin/autopkgtest debputy -- lxc --sudo
autopkgtest-testing-i386
Hi,
On 12-04-2024 4:42 a.m., 陈 晟祺 wrote:
- If I limit the test file size to 1G, quite many tests would fail even with
adequate resources
Ack. To be fair, I was more thinking to make current test conditional on
the available free disk space. But yeah, that might also lead to issues
as the
Hi
On 11-04-2024 5:18 p.m., 陈 晟祺 wrote:
If possible, could you help to build with latest code on salsa then run
autopkgtest again on a normal debci VM?
As I'm doing this live on the infrastructure, I don't want to do
anything there except testing what's in the archive, sorry.
My private
Hi,
With the default size of the ramdisk and 2 cpu's the test crashes with:
Test: /usr/share/zfs/zfs-tests/tests/functional/large_files/setup (run
as root) [00:00] [PASS]
Test:
/usr/share/zfs/zfs-tests/tests/functional/large_files/large_files_001_pos
(run as root) [00:00] [PASS]
Test:
Hi,
Some additional info from my side.
I have just run the following:
root@ci-worker13:~# /usr/bin/autopkgtest --no-built-binaries
--test-name=zfs-test-suite --timeout-factor=3 --user debci zfs-linux --
qemu --cpus=2 --ram-size=8192 /var/lib/debci/qemu/testing-amd64.img
The test failed and
Hi
On 11-04-2024 8:35 a.m., Christian Kastner wrote:
Yes, images can be built now, but without ifupdown their network
interface is left unconfigured, and thus autopkgtests can't download
packages.
Somewhere in the back of my mind I was fearing this.
So ifupdown seems to be needed, and this
tags -1 bookworm
On 09-04-2024 7:23 p.m., Andreas Beckmann wrote:
Please remove the obsolete ruby-arel from bookworm.
I'm tagging it as such, so it shows up in the SRM tooling.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
tags -1 bookworm
On 09-04-2024 7:23 p.m., Andreas Beckmann wrote:
Please remove the obsolete ruby-arel from bookworm.
I'm tagging it as such, so it shows up in the SRM tooling.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
Hi,
On 08-04-2024 3:51 a.m., 陈 晟祺 wrote:
With resources limited to one CPU (AMD EPYC 7551) and 2G memory,
my local test could now reproduce the test hang and following time out error.
Ouch.
I think it is caused by insufficient resources (e.g. OOM killer, but I am not
sure).
Even we can
Hi Yves-Alexis,
On 08-04-2024 10:13 a.m., Yves-Alexis Perez wrote:
thanks for the report. I might try to investigate a bit but at that point
honestly I don't have much clue what happens.
Can we try and find out together?
Could you please provide a bit more context in the bug report so we
Hi,
On 07-04-2024 7:20 p.m., Christian Kastner wrote:
I'm not a maintainer but I use autopkgtest a lot. I hope it's OK if I
contribute input.
Yes, absolutely. Comments from all people that want to contribute
constructively are welcome. Even more so from users and contributors.
Paul
Hi,
On Sun, 17 Mar 2024 23:37:03 +0100 Sebastian Ramacher
wrote:
Justification: fails to build from source (but built successfully in the past)
This package is a key package (hence we can't trivially remove it from
testing) and the failure is blocking the time_t transition. Can this
Hi,
On Sun, 17 Mar 2024 23:37:03 +0100 Sebastian Ramacher
wrote:
Justification: fails to build from source (but built successfully in the past)
This package is a key package (hence we can't trivially remove it from
testing) and the failure is blocking the time_t transition. Can this
Hi,
On Sun, 17 Mar 2024 23:37:03 +0100 Sebastian Ramacher
wrote:
Justification: fails to build from source (but built successfully in the past)
This package is a key package (hence we can't trivially remove it from
testing) and the failure is blocking the time_t transition. Can this
Source: gem2deb
Version: 2.2.2
Severity: serious
X-Debbugs-CC: ruby...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:ruby3.1
Dear maintainer(s),
With a recent upload of ruby3.1 (in the time_t transition) the
autopkgtest of
Source: gem2deb
Version: 2.2.2
Severity: serious
X-Debbugs-CC: ruby...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:ruby3.1
Dear maintainer(s),
With a recent upload of ruby3.1 (in the time_t transition) the
autopkgtest of
Source: gem2deb
Version: 2.2.2
Severity: serious
X-Debbugs-CC: ruby...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:ruby3.1
Dear maintainer(s),
With a recent upload of ruby3.1 (in the time_t transition) the
autopkgtest of
Package: autopkgtest
Severity: wishlist
Hi all,
The following issues have come up several times over the years. I
propose to discuss them in one place (this bug report) to define the
solution strategy. I haven't gone through all the details myself, so I
might be thinking in the wrong
Hi,
On 07-04-2024 2:29 p.m., 陈 晟祺 wrote:
Could you please provide more detailed information on the test settings on
ci.d.o.?
E.g., CPU type, #cores, memory size, etc.
The host that runs this is an m3-large instance at equinix [1].
We create the qemu image with autopkgtest-build-qemu
Source: crash
Version: 8.0.4-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list to use
Source: borgbackup2
Version: 2.0.0b8-2
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the
Source: crmsh
Version: 4.6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it started to fail in
testing several days ago. Can you please investigate the situation and
fix it? I copied some of the
Source: crmsh
Version: 4.6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it started to fail in
testing several days ago. Can you please investigate the situation and
fix it? I copied some of the
Source: zfs-linux
Version: 2.2.3-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine timeout
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the
Source: strongswan
Version: 5.9.13-2
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list
Source: squashfuse
Version: 0.5.0-2
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list
Source: snapd
Version: 2.61.2-2
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list to
Source: securefs
Version: 0.13.1+ds-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list
Source: tgt
Version: 1:1.0.85-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list to
Hi,
On Sat, 09 Sep 2023 18:51:52 -0700 Russ Allbery wrote:
"""
+``systemd`` uses dependency and ordering information contained within the
++enabled unit files to decide which services to run and in which order.
"""
^ is that "+" before "enabled" really intended? It looks weird to me.
Paul
Hi,
On Sat, 09 Sep 2023 18:51:52 -0700 Russ Allbery wrote:
"""
+``systemd`` uses dependency and ordering information contained within the
++enabled unit files to decide which services to run and in which order.
"""
^ is that "+" before "enabled" really intended? It looks weird to me.
Paul
Control: severity -1 normal
Control: retitle -1 autopkgtest-virt-docker --podman --init unsure
Hi,
On 30-12-2023 8:26 p.m., Paul Gevers wrote:
I recently added support for isolation-machine testing on ci.d.n and
when I ran the autopkgtest of src:autopkgtest, it failed. It failed the
podman
Source: xdp-tools
Version: 1.4.2-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list to
Source: vagrant-lxc
Version: 1.4.3-3
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list
Source: vagrant-libvirt
Version: 0.12.2-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the
Source: vagrant-libvirt
Version: 0.12.2-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the
Source: vagrant-lxc
Version: 1.4.3-3
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the list
control: notfixed -1 1.15.5-1
On 04-04-2024 6:04 p.m., Paul Gevers wrote:
So, marking the bug as not affecting the version in testing to avoid
autoremoval.
And also removing the fixed version. There was only a *time* that
liferea was broken (by liblzma), not a version of liferea, nor
The mystery continues.
On 04-04-2024 10:08 p.m., Paul Gevers wrote:
I forgot that on amd64, autopkgtest's autopkgtest now runs in qemu which
doesn't benefit yet as much from tmpfs as lxc does, so it's not a good
comparison.
On ci-worker13:
"""
root@elbrus:/tmp/autopkgte
The mystery continues.
On 04-04-2024 10:08 p.m., Paul Gevers wrote:
I forgot that on amd64, autopkgtest's autopkgtest now runs in qemu which
doesn't benefit yet as much from tmpfs as lxc does, so it's not a good
comparison.
On ci-worker13:
"""
root@elbrus:/tmp/autopkgte
Control: tags -1 pending
Hi Samuel,
On 02-04-2024 2:50 p.m., Samuel Thibault wrote:
Should we perhaps make autopkgtest really try this last attempt?
We have been and still are working on several merge requests that should
improve the situation in these weird times:
Package: liferea
Version: 1.15.6-1
X-Debbugs-CC: debian-s390@lists.debian.org
Severity: normal
User: debian-s390@lists.debian.org
Usertag: s390x
Hi,
Today I was debugging the failing autopkgtest of liferea, a graphical
rss reader, on s390x [1]. Previously I already worked around another
crash
Package: liferea
Version: 1.15.6-1
X-Debbugs-CC: debian-s...@lists.debian.org
Severity: normal
User: debian-s...@lists.debian.org
Usertag: s390x
Hi,
Today I was debugging the failing autopkgtest of liferea, a graphical
rss reader, on s390x [1]. Previously I already worked around another
crash
Hi,
On 05-04-2024 9:36 p.m., Julian Andres Klode wrote:
Dear ftp and release teams, please ensure that the testing-proposed-updates
upload lands and that the signed uploads are processed accordingly. I
don't know how to handle the signing with the proposed-updates, but I'm
sure you can
Hi William,
I noticed you "binNMU"-ed siridb-server in Ubuntu where it built
successfully on all arches. In Debian I got the bug below reported. Any
idea what the difference could be between the state of Debian and the
state of Ubuntu that causes this?
reproducible-builds [1] confirms that
Hi William,
I noticed you "binNMU"-ed siridb-server in Ubuntu where it built
successfully on all arches. In Debian I got the bug below reported. Any
idea what the difference could be between the state of Debian and the
state of Ubuntu that causes this?
reproducible-builds [1] confirms that
Control: retitle -1 autopkgtest: test_copy_timeout fails on tmpfs
Hi,
On 04-04-2024 10:08 a.m., Paul Gevers wrote:
Overall, I
expect the host to be *faster* than the old hosts, but ironically the
tests that seems to fail is: __main__.SchrootRunner.test_copy_timeout.
Yes, it's too fast
Control: retitle -1 autopkgtest: test_copy_timeout fails on tmpfs
Hi,
On 04-04-2024 10:08 a.m., Paul Gevers wrote:
Overall, I
expect the host to be *faster* than the old hosts, but ironically the
tests that seems to fail is: __main__.SchrootRunner.test_copy_timeout.
Yes, it's too fast
control: notfound -1 1.15.4-1
On 04-04-2024 5:42 p.m., Paul Gevers wrote:
I've scheduled retries on the reproducible build infrastructure.
amd64 and i386 both build fine (while on amd64 there was the same
failure in the past as in this bug report).
So, marking the bug as not affecting
control: notfound -1 1.15.4-1
On 04-04-2024 5:42 p.m., Paul Gevers wrote:
I've scheduled retries on the reproducible build infrastructure.
amd64 and i386 both build fine (while on amd64 there was the same
failure in the past as in this bug report).
So, marking the bug as not affecting
Hi,
On Fri, 15 Mar 2024 22:42:34 +0100 Paul Gevers wrote:
The problem is somewhere in liblzma.
In hind-sight, this is all to likely that it's caused by CVE-2024-3094,
the xz backdoor.
I've scheduled retries on the reproducible build infrastructure. As the
version in unstable is stuck
Hi,
On Fri, 15 Mar 2024 22:42:34 +0100 Paul Gevers wrote:
The problem is somewhere in liblzma.
In hind-sight, this is all to likely that it's caused by CVE-2024-3094,
the xz backdoor.
I've scheduled retries on the reproducible build infrastructure. As the
version in unstable is stuck
Source: pytest-testinfra
Version: 10.1.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: ruby-graphlient
Version: 0.7.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: pytest-testinfra
Version: 10.1.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: ruby-asana
Version: 0.10.13-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: ruby-graphlient
Version: 0.7.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: ruby-asana
Version: 0.10.13-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: ruby-asana
Version: 0.10.13-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: ruby-graphlient
Version: 0.7.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: translate-toolkit
Version: 3.12.2-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: translate-toolkit
Version: 3.12.2-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: translate-toolkit
Version: 3.12.2-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: pcp
Version: 6.2.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from
Source: pcp
Version: 6.2.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from
201 - 300 of 19922 matches
Mail list logo
