On Wed, 2025-04-23 at 22:01 -0600, dann frazier wrote:
> > Please see NEWS.Debian:
> https://salsa.debian.org/qemu-team/edk2/-/blob/08d4411d458eefc4df5d48acce4f995d4ae6087d/debian/qemu-efi-aarch64.NEWS
Thanks for pointing that out; since the NEWS entry is specific to
arm64 it hadn't popped up as
Source: logcheck
Version: 1.4.3
Severity: serious
On a fresh minimal trixie install, logcheck fails to read the systemd
journal and exits with the following error:
> Logcheck failed: Your log entries may not have been checked.
>
> Details:
> Could not run journalctl or save output
Adding th
This isn't an i386-specific issue, but rather a flaky test (or maybe
more than one) that do some sort of time sampling. I've previously
filed #1102485 about this showing up as flaky autopkgtests which pass
when re-run.
I'd strongly prefer the tests actually be fixed than just skipped,
but I ha
Any progress investigating this? Otherwise I fear keepassxc will fall
out of testing before the trixie release.
Mathias
signature.asc
Description: This is a digitally signed message part
On Wed, 2025-03-12 at 18:09 +, Martin Dosch wrote:
> Dear all,
>
> I'd like to see crowdsec in trixie, as I am using it myself.
> Is there any chance to get [1081196] fixed by delivering upstreams
> sshd-logs.yaml? This file is not in the repo and I failed to figure out
> how it is created.
In my testing I needed to make one additional change to the base lxc
apparmor profile, and I've replied to the upstream bug report asking
for feedback, since I'm not an apparmor expert. Once I get an ACK on
that I'll update the lxc package for Debian.
Mathias
signature.asc
Description: This is
On Mon, 3 Mar 2025 14:43:30 +0100 Helmut Grohne wrote:
> [Y]ou moved the systemd units formerly present in incus to the incus-base
> package. The way this is done is normally correct and works for trixie
> -> sid upgrades. Unfortunately, the earlier version has also been
> backported to bookworm-b
On Tue, 13 Aug 2024 20:06:11 +0200 Santiago Vila
wrote:
> During a rebuild of all packages in unstable in the year 2028, your
package failed to build:
[snip]
Any progress looking into this? Currently dput-ng is ~9 days from
autorm, although this email should reset the countdown. Still, we're
On Mon, 2025-01-20 at 21:00 +0100, Simon Josefsson wrote:
> Although shouldn't the FTBFS bug really on 'sigstore-go' rather than
> 'golang-github-google-certificate-transparency'? The former is what is
> failing to build, not the latter. It would have been nice if the
> g-g-g-c-t test suite trigg
I'm seriously considering just disabling the tests for this package.
I can't reproduce the most recently reported failure on any of my
machines, although I don't doubt that it is reproducible for Lucas.
Upstream knows about the tests being flaky, and there's a similar bug
against the package i
Any thoughts on this? I'm leaning towards disabling the dqlite tests;
I don't know if we want to consider doing that for this package as
well.
Mathias
signature.asc
Description: This is a digitally signed message part
Source: yubikey-manager
Version: 5.5.1-1
Severity: serious
Justification: Renders yubioath-desktop unusable
python3-ykman 5.5.1-1 recently migrated to testing, and it appears to
be incompatible with yubioath-desktop 5.1.0-3, rendering it totally
unusable as it no longer recognizes my yubikeys. M
Source: oci-seccomp-bpf-hook
Version: 1.2.10+ds-1
Severity: serious
Justification: FTBFS
Tags: sid ftbfs
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_bu
Source: golang-github-google-certificate-transparency
Version: 1.3.1-1
Severity: serious
Justification: FTBFS
Tags: sid ftbfs
Affects: sigstore-go
X-Debbugs-CC: si...@josefsson.org
The recent update of golang-github-google-certificate-transparency is
missing (at least) golang-github-jackc-pgerrc
Control: retitle -1 dh-make-golang: FTBFS: dh_auto_test: error: cd _build && go
test -vet=off -v -p 4 github.com/Debian/dh-make-golang returned exit code 1
It looks like this FTBFS was caused by the recent update to golang-
github-charmbracelet-glamour. In an otherwise up-to-date amd64 sid
envi
Source: golang-github-biogo-hts
Version: 1.4.5+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: sid ftbfs
This package fails to build on 32bit architectures:
>dh_auto_test -O--buildsystem=golang
> cd obj-i686-linux-gnu && go test -vet=off -v -p 22
> github.com/biogo/hts/bam githu
Source: golang-github-biogo-hts
Version: 1.4.5+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: sid ftbfs
A test is failing when this package is built. Maybe related to the
sbuild unshare backend switch?
> === RUN TestEOF
> bgzf_test.go:118: Expected error:read /tmp/TestEOF2778629558/
Source: zabbix
Version: 1:7.0.3+dfsg-1
Severity: serious
Justification: FTBFS
Tags: sid ftbfs patch
Affects: src:golang-github-go-logr-logr src:golang-github-go-sql-driver-mysql
src:golang-github-mattn-go-sqlite3
Recently a couple golang libraries were updated, and unfortunately
they're causing
Source: go-cve-dictionary
Version: 0.3.1-5
Severity: serious
Justification: Failure to migrate to testing
src:go-cve-dictionary has been stuck migrating to testing for 429
days. The last Debian release to include this package was bullseye.
I think this package is a good candidate to RM prior
Control: retitle -1 goval-dictionary: Migration blocked for 429 days, consider
RM'ing
Control: tags -1 - sid ftbfs
The root cause of the FTBFS is in another package (#1085474),
although this package should still be considered for RM.
signature.asc
Description: This is a digitally signed messa
Additionally, this package has been stuck migrating to testing for
301 days. It has never been included in a Debian release.
I think this package is a good candidate to RM prior to trixie.
signature.asc
Description: This is a digitally signed message part
Source: gost
Version: 0.1.2-2
Severity: serious
Justification: Failure to migrate to testing
src:gost has been stuck migrating to testing for 429 days. The last
Debian release to include this package was bullseye.
I think this package is a good candidate to RM prior to trixie.
signature.asc
Source: goval-dictionary
Version: 0.2.0-6
Severity: serious
Justification: FTBFS
Tags: sid ftbfs
src:goval-dictionary currently FTBFS. Additionally, it's been blocked
from migration to testing for 429 days. The last Debian release to
include this package was bullseye.
I think this package is
Source: go-exploitdb
Version: 0.0~git20181130.7c961e7-3
Severity: serious
Justification: Failure to migrate to testing
src:go-exploitdb has been stuck migrating to testing for 430 days.
The last Debian release to include this package was bullseye.
I think this package is a good candidate to R
Source: vuls
Version: 0.6.1-5
Severity: serious
Justification: Failure to migrate to testing
src:vuls has been stuck migrating to testing for 408 days. The last
Debian release to include this package was bullseye.
I think this package is a good candidate to RM prior to trixie.
signature.asc
Source: golang-github-go-sql-driver-mysql
Version: 1.8.1-1
Severity: serious
Justification: FTBFS
Tags: sid ftbfs
X-Debbugs-Cc: vs...@debian.org
The recent upload of src:golang-github-go-sql-driver-mysql 1.8.1-1
missed adding golang-filippo-edwards25519-dev to the Depends: stanza
for the corresp
Source: golang-github-go-redis-redis
Version: 6.15.0-2
Severity: serious
Justification: Failure to migrate to testing
src:golang-github-go-redis-redis has been stuck migrating to testing
for 1015 days. The last Debian release to include this package was
bullseye.
I think this package is a goo
Control: severity -1 important
It appears that this is a flaky test, as a subsequent build attempt
on ppc64el succeeded.
Mathias
signature.asc
Description: This is a digitally signed message part
ACK, I noticed that this morning as well.
FYI, we've started a grpc/protobuf transition for golang packages, so
you may observe a higher occurrence of package build issues than normal
while we work through things.
Mathias
signature.asc
Description: This is a digitally signed message part
Source: golang-github-henrybear327-go-proton-api
Version: 1.0.0-3
Severity: serious
Justification: FTBFS
Tags: sid ftbfs
A test is failing due to an expired gpg key:
> === RUN TestDecrypt
> message_types_test.go:28:
> Error Trace:
> /<>/_build/src/github.com/henrybear
(Touching bug to reset AUTORM countdown.)
signature.asc
Description: This is a digitally signed message part
Control: tags -1 + help unreproducible
Control: severity -1 important
Lowering bug severity to important since I can't reproduce this issue
on any of my systems. Additionally, looking at the various reproducible
builds shows the most recent arm64 build passed, while the amd64 one
failed.
Mathia
Control: forwarded -1 https://github.com/canonical/dqlite/issues/643
Looks like a flaky test, and unrelated to the time_t transition.
Mathias
signature.asc
Description: This is a digitally signed message part
On Sat, 2024-04-20 at 22:40 +0800, Shengjing Zhu wrote:
> On Sat, Apr 20, 2024 at 10:28 PM Mathias Gibbens wrote:
> >
> > Hi Anthony,
> >
> > A few weeks ago you uploaded a new version of golang-google-protobuf
> > to unstable which caused a FTBFS in
Hi Anthony,
A few weeks ago you uploaded a new version of golang-google-protobuf
to unstable which caused a FTBFS in golang-github-golang-protobuf-1-5
v1.5.3 [1,2,3]. This has been blocking the transition of various golang
packages from unstable to testing.
I've verified that v1.5.4 of golang
(Touching bug to reset AUTORM countdown.)
signature.asc
Description: This is a digitally signed message part
On Tue, 2024-03-05 at 14:19 +0100, Helmut Grohne wrote:
> debvm-create --include=incus
> # This should have created a file named rootfs.ext4.
> debvm-run
Thanks for sharing that!
> Rather than adding debvm on top of your testing, I think adding
> autopkgtests with isolation-machine should get y
Control: tags -1 + pending
It's easy enough to add iproute2 as a dependency, so I've done so.
Incus already has quite a number of dependencies, and I'd like to keep
that list as small as possible, which is why I was initially reluctant
to add iproute2. I would be interested to know more about wh
Control: tags -1 + moreinfo
Hi Helmut,
iproute2 is Priority: important, which according to Policy §2.5 means
that it is generally expected to be present on a Debian system. Do you
have a specific use case where for some reason you don't have iproute2
installed?
I'm initially reluctant to exp
Control: severity -1 normal
Hi Stefano,
I suspect you're seeing this on the host system running Incus? If so,
that's expected behavior.
Incus' default mode of operation when launching a VM is to
dynamically inject the `incus-agent` binary into the VM's environment.
(`incus-agent` should neve
Source: golang-github-katalix-go-l2tp
Version: 0.1.6-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
In a clean sid schroot, one of the tests is timing out:
> transport_test.go:388: test sender function reported an error: failed to
> send Hello message: transmit of avpMsgTy
Hi Sergio,
raft 0.21.0-1 was uploaded to unstable yesterday. Could you rebase on
top of that release for the time_t transition? Until the transition is
complete, we'll refrain from making further uploads to unstable.
Free, I'll make a debian/experimental branch in salsa to track the
NMU chang
ACK -- I won't plan to make any uploads of src:lxc to unstable until
after the time_t transition is complete.
For the team, I've applied the NMU to the debian/experimental branch
up in salsa.
Mathias
signature.asc
Description: This is a digitally signed message part
Sphinx 7.0.0 dropped the `style` key
(https://github.com/sphinx-doc/sphinx/pull/11381). Version 7.2.6 was
uploaded to unstable early last month, causing this FTBFS.
signature.asc
Description: This is a digitally signed message part
-2.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Run tests with LC_ALL=en_US.utf8 (Closes: #1052803)
+
+ -- Mathias Gibbens Fri, 10 Nov 2023 19:12:55 +
+
golang-github-gosexy-gettext (0~git20130221-2.1) unstable; urgency=medium
[ Dr. Tobias Quathamer ]
diff --git a/debian
Hi all,
I'm working on fixing bug #1052803 for golang-github-gosexy-gettext.
That package's tests started failing, and I'm pretty sure it was caused
by the upload of src:glibc 2.37-8 which backported a patch from bug
#874160 that treats language encodings like C.UTF-8 as the C locale.
This ch
Hi Steve,
This library is a dependency of LXD and the hopefully soon to be
packaged Incus, so I'd like to prevent it from being AUTORM'ed from
testing in a month. Have you had a chance to look into this build
failure?
Also, if you'd like to move the package to being team-maintained with
the G
On Sun, 2023-08-06 at 15:20 +0100, Richard Lewis wrote:
> A gentle reminder on the last bit of this - getting it into bookworm
> point release. (i think i read somewhere that 12.2 would be at the
> end of august)
ACK -- the 12.2 point release has been announced for October 7th,
with a processing
On Mon, 2023-09-04 at 01:00 -0700, John Johansen wrote:
> I took a quick look through v6.1..v6.3.1
>
> there is a patch that I think is the likely fix, it first landed in v6.2
>
> 1cf26c3d2c4c apparmor: fix apparmor mediating locking non-fs unix sockets
Thanks for the pointer John -- I think t
Source: dh-make-golang
Version: 0.6.0-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Something has changed in sid's golang environment since August 4
which is causing dh-make-golang to fail to determine a package's
dependencies and generate a correct d/control. For example, this wo
Andreas, thanks for the report, and Richard, thanks for your work as
well. I think the changes look good, and if there's no other concerns
I'll merge the salsa MR, and upload a new version to unstable. Once
that's done, I'll also file a bug for uploading the updated version to
stable-proposed-upd
Hi Helmut,
On Thu, 27 Apr 2023 15:00:05 +0200 Helmut Grohne wrote:
> Attempting to unpack lxd-client/5.0.2-3+b2 from Debian bookworm
> on a minimal Debian bullseye with lxc/1:4.0.6-2+deb11u1
> installed, causes an unpack error from dpkg due to
> /usr/share/bash-completion/completions/lxc being co
Control: forwarded -1 https://github.com/lxc/lxc/issues/4289
signature.asc
Description: This is a digitally signed message part
Hi Mario,
I'm currently on travel with not-so-great network connectivity, so I
haven't been able to reproduce this on my travel laptop, but will
attempt to do so when I'm back from my trip.
I expect that this issue will have to be forwarded to the lxc
developers; if you want to do so you can
Control: severity -1 normal
You can disable the checking of the systemd journal:
> $ sudo cat /etc/logcheck/logcheck.logfiles.d/journal.logfiles
> ## The word 'journal' tells logcheck to check log entries in the
> ## systemd journal
>
> # (This is enabled by default, but if you do not want to
Control: retitle -1 gopacket: FTBFS with libpcap >= 1.10.2
Control: tags -1 + confirmed
Control: forwarded -1 https://github.com/google/gopacket/issues/1088
It appears that libpcap 1.10.2 introduced some change that is causing
the test failure. Manually downgrading to libpcap 1.10.1-4 from
snaps
Source: prometheus-blackbox-exporter
Version: 0.23.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
There appear to be inconsistent test failures in prometheus-blackbox-
exporter, specifically TestGRPCTLSConnection and TestNoTLSConnection. I
noticed this while rebuilding the p
Source: vip-manager
Version: 1.0.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
vip-manager is failing to build in a clean sid schroot:
> github.com/cybertec-postgresql/vip-manager/ipmanager
> # github.com/cybertec-postgresql/vip-manager/ipmanager
> src/github.com/cybertec-
Control: block 1026137 by 1026139
Updating the B-D to golang-github-golang-protobuf-1-5-dev conflicts
with golang-github-golang-protobuf-1-3-dev that is pulled in by the
version of golang-google-grpc-dev in experimental or one of its
dependencies. Once that's resolved it should be pretty straigh
Source: notary
Version: 0.7.0+ds1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
notary appears to be failing to build due to a protobuf-related
error. In a clean sid schroot:
> cd _build && go install -trimpath -v -p 16 -tags pkcs11
> github.com/theupdateframework/nota
Source: docker.io
Version: 20.10.19+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
In a clean sid schroot, docker.io has a test that fails:
> make[1]: Entering directory '/<>'
> ## Test engine:
> cd /<>/_build/src/github.com/docker/docker \
> && TESTFLAGS='-test.short'
Control: tags -1 + confirmed fixed-upstream pending
On Fri, 2022-11-04 at 06:24 +0100, Helmut Grohne wrote:
> lxc fails to build from source in unstable. It seems very likely that
> this is due to glibc 2.36. A non-parallel build log fails as follows:
Thanks for the report! This was indeed caus
Source: zabbix
Version: 1:6.0.9+dfsg-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
While rebuilding the reverse build dependencies of another golang
package I'm updating, I noticed that zabbix fails to build in a clean
sid chroot. I suspect this was likely caused by the rec
Control: tags -1 + pending
Hi Marco,
On Sat, 2022-10-08 at 04:53 +0200, Marco d'Itri wrote:
> On Jul 30, Mathias Gibbens wrote:
>
> > Feel free to apply it directly yourself. :) If this does fix the
> > issue, it would probably be good to contact Lucas and see if we
part of my DD application process, where I
was asked to find and fix an existing bug, and submit the fix as a
patch to the BTS. That's why I haven't directly committed the fix to
the salsa repo, even though I'm part of the Go Packaging Team. :)
Mathias
From: Mathias Gibbens
Des
I'm not 100% certain, but I expect this failure is due to the new
version of unicode-data that was just uploaded to unstable a couple of
days ago.
Mathias
signature.asc
Description: This is a digitally signed message part
Control: tags -1 + confirmed
Control: forwarded -1 https://github.com/go4org/go4/issues/55
This appears to be caused by golang v1.19's changing of its sorting
algorithm [1], which isn't the first time that has caused this test to
fail [2].
Mathias
[1] -- https://go.dev/doc/go1.19#sort
[2] -- h
Control: tags -1 + confirmed
It looks like this is triggering a bug in g++ 12 that's been reported
upstream with a simple test case:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105580. For now, I'm
inclined to suppress -Wnull-dereference for the affected source file,
since I know that there is
Control: tags -1 + confirmed
Control: forwarded -1 https://github.com/canonical/raft/issues/292
This has been reported by others to the upstream developers already,
and seems to be caused by an update to libuv1.
Mathias
signature.asc
Description: This is a digitally signed message part
Hi Aloïs,
On Mon, 2022-07-25 at 13:47 +0200, Aloïs Micard wrote:
> > I've been unable to reproduce this locally, but have also seen
> > instances in the past where the buildds have difficulty running
> tests
> > that utilize IPv6.
> >
> > Maybe there's no "ip6-localhost" defined in /etc/h
Control: tags -1 +moreinfo +unreproducible
Control: severity -1 important
On Sat, 16 Jul 2022 15:43:55 +0200 Lucas Nussbaum
wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
Thanks for the report. However, locally I haven't been able to
reproduce this F
forwarded 1002268 https://github.com/brandond/homeplug_exporter/issues/7
thanks
Unfortunately the root cause of this FTBFS was the library
github.com/prometheus/common dropping their `log` package in v0.27.0.
That library was updated in Debian, and it wasn't caught that the
update would break th
tags 1013554 + ipv6
thanks
I've been unable to reproduce this locally, but have also seen
instances in the past where the buildds have difficulty running tests
that utilize IPv6.
Maybe there's no "ip6-localhost" defined in /etc/hosts when the
package is built? Would it be worth tryin literal
Checking today, it appears that golang-github-seccomp-containers-
golang no longer has any rdeps in main.
> $ build-rdeps golang-github-seccomp-containers-golang-dev
> Reverse Build-depends in main:
> --
>
> No reverse build-depends found for
> golang-github-seccomp
tags 1004902 + pending
thanks
Thanks for the report! I've fixed the error locally and plan to get a
new version uploaded in the near future.
Mathias
On Thu, 2022-02-03 at 11:13 +0100, Andreas Beckmann wrote:
> Source: openrct2
> Version: 0.3.5.1+ds-2
> Severity: serious
> Tags: ftbfs
> Justifi
There was something weird with me not receiving Michael's initial
reply. I did review my server's logs, but didn't see anything
indicating what the problem was. I do want to include his reply, so
others who see this bug can have the whole context:
> On Wed, Dec 08, 2021 at 02:01:03PM +0100, Mich
Source: snapd
Version: 2.51.7-2
Severity: serious
Justification: packaging not up to Debian standards
X-Debbugs-CC: mwhud...@debian.org, lfara...@debian.org, vor...@debian.org,
m...@zygoon.pl, michael.v...@ubuntu.com, ian.john...@canonical.com
I had initially reached out to the individuals list
Upstream recently merged a fix for the tests. I'm not sure what their
release schedule is; would it be possible to cherry-pick that commit
and do an upload of dqlite to unstable? I've got a personal interest in
dqlite being available again in testing, as it's one of the (many!)
dependencies for p
This FTBFS was caused by version 8.1.0 of python3-pil migrating to
testing a couple of weeks ago. There's an upstream bug about this:
https://github.com/OpenTTD/nml/pull/182. Their solution of restricting
the maximum version of pillow won't work for Debian.
Pillow also has an issue open:
htt
Hi,
This weekend I upgraded my main system to stretch to help shake out
bugs before the final release, and discovered that tellico has fallen
out of testing due to this bug. I've tried to reproduce tellico
crashing as reported under a few scenarios, but it runs fine for me:
* Starting tellico
80 matches
Mail list logo
