(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.
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
(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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
>
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
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
>
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
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
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 can
&
was 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
Description: Fix
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] --
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
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
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
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
>
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
>
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,
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
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
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:
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
50 matches
Mail list logo
