Hi Lucas, thanks for this report.
I took a look and it seems to me that the failure happens when running
the testsuite, and seems to be scoped to 32bit architectures such as armhf or
i386.
The relevant test code appears to be here:
https://sources.debian.org/src/golang-mongodb-mongo-driver/1.1
Control: severity -1 important
Control: retitle -1 "Tests fail on 32-bit architecture"
Hi Lucas, thanks for filing this bug. I took a closer look at it and
believe it is known upstream for quite a while (since Jun 2019) as
https://github.com/xlab/treeprint/issues/10.
I agree that this is an impor
Awesome, thank you so much for checking and letting me know!
On April 10, 2025 3:20:49 PM EDT, Blair Noctis wrote:
>Source: netavark
>Version: 1.14.0-2
>Severity: normal
>X-Debbugs-Cc: n...@debian.org
>
>Dear maintainer,
>
>I'm about to upgrade the prost family from 0.12 to 0.13.
>An upgrade of t
Package: librust-axum-core-dev
Version: 0.7.9-12
Severity: important
Dear Maintainer,
Looking at the package tracker at
https://tracker.debian.org/pkg/rust-axum, it appears to me that
migration to testing is held up. It also occurs to me that debci
triggers autopkgtest against rust-tonic 0.10.2,
Control: Tag -1 upstream
The full context of this conversation is archived at
https://bugs.debian.org/1100135
Sam Hartman writes:
> package: apparmor
> version: 4.1.0~beta5-3
> severity: important
> x-debbugs-cc: pod...@packages.debian.org, pa...@packages.debian.org,
> golang-github-container
On 2025-03-25 02:10, Jonas Smedegaard wrote:
Control: tags -1 moreinfo
Hi Reinhard,
Quoting Reinhard Tartler (2025-03-24 23:31:08)
thanks for your recent upload of rust-rustls-native-certs. Looking at
https://tracker.debian.org/pkg/rust-rustls-native-certs, it appears
that it would benefit
Package: librust-rustls-native-certs-dev
Version: 0.6.3-5
Severity: important
Hi Jonas,
thanks for your recent upload of rust-rustls-native-certs. Looking at
https://tracker.debian.org/pkg/rust-rustls-native-certs, it appears that it
would benefit from additional Breaks relationships to help the
On 2025-03-21 07:48, Jonas Smedegaard wrote:
Quoting Reinhard Tartler (2025-03-21 11:57:14)
Looking at the package tracker at
https://tracker.debian.org/pkg/rust-axum, it appears to me that
migration to testing is held up. It also occurs to me that debci
triggers autopkgtest against rust-tonic
Control: tag -1 moreinfo
Hi Simon, thanks for reporting this issue, and sorry for not getting
back to you earlier.
Simon Josefsson writes:
> Hi. I've seen this build failure a couple of times when doing reverse
> builds on Salsa, and it seems unrelated to the packages I'm doing
> reverse buil
On 2025-03-15 14:00, Jonas Smedegaard wrote:
What's the best way to proceed here? Trying to backport
https://github.com/hyperium/tonic/commit/9c1f2f9402d97cfa4c9d9065b5af2fb99d2ef521
to tonic 0.10 or attempting to package 0.12?
I don't know what is best until I have solved the puzzle.
What I
Reinhard Tartler writes:
> Package: librust-tonic-dev
> Version: 0.10.2+dfsg-12
> Severity: serious
> Justification: Breaks compilation of depending packages
>
> [...]
> The following packages have unmet dependencies:
> librust-tonic-dev : Depends: librust-axum-0.6-dev b
Package: librust-tonic-dev
Version: 0.10.2+dfsg-12
Severity: serious
Justification: Breaks compilation of depending packages
When trying to use librust-tonic-dev as a build dependencies, it fails to
install with:
Install main build dependencies (apt-based resolver)
---
Package: wnpp
Severity: normal
X-Debbugs-Cc: lcd4li...@packages.debian.org
Control: affects -1 + src:lcd4linux
I intend to orphan the lcd4linux package. I no longer have the capacity to
effectively maintain the package nor do I have the hardware to test.
The package description is:
Small program
Am Mittwoch, 5. Februar 2025, 08:26 schrieb Abou Al Montacir:
> Hi Reinhard,
>
> On Tue, 2025-02-04 at 13:40 +0100, Reinhard Karcher wrote:
> > Package: fp-compiler-3.2.2
> > Version: 3.2.2+dfsg-43
> > Severity: serious
> > Justification: unnown
> >
> >
Package: fp-compiler-3.2.2
Version: 3.2.2+dfsg-43
Severity: serious
Justification: unnown
Dear Maintainer,
Upgrade to version 3.2.2+dfsg-43 from -40 produced compilation errors.
I used the lazarus command compilation. The compilation aborted with
the following messassages:
Kompiliere Package fre
On Sun, Feb 2, 2025 at 12:52 PM Nicolas Peugnet wrote:
> On 02/02/2025 2:43 PM, Reinhard Tartler wrote:
> > On Sat, Feb 1, 2025 at 7:42 PM Nicolas Peugnet wrote:
> >>>> Then I realized that the docker.io package is in fact a "Multiple
> >>>> Upstre
On Sat, Feb 1, 2025 at 7:42 PM Nicolas Peugnet wrote:
> On 01/02/2025 6:05 PM, Reinhard Tartler wrote:
> > On Wed, Jan 29, 2025 at 7:15 PM Nicolas Peugnet
> wrote:
> >> Thank you for the pointers. Indeed in the case of packages from
> >> "docker/cli" an
On Wed, Jan 29, 2025 at 7:15 PM Nicolas Peugnet wrote:
> On 26/01/2025 1:16 PM, Reinhard Tartler wrote:
>
> Thank you for the pointers. Indeed in the case of packages from
> "docker/cli" and "docker/docker" it is just a matter of adding them to
> the golang-gi
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-multiformats-go-varint
Version : 0.0.7-1
Upstream Author : Multiformats
* URL : https://github.com/multiformats/go-varint
* License : Expat
Programming Lang: Go
On 2025-01-28 12:09, Jonathan Wiltshire wrote:
[ Reason ]
golang-github-containers-buildah in bookworm FTBFS on the buildds since
unshare
became the default.
[ Impact ]
Policy violation for golang-github-containers-buildah (must build on
the
autobuild network) and inability to fix any other i
On Sat, Jan 25, 2025 at 12:18 PM Nicolas Peugnet wrote:
> On 25/01/2025 5:43 PM, Reinhard Tartler wrote:
> > that's awesome, thank you.
> >
> > Let me know when you have a package ready, I'd be happy to take a look at
> > it. Maybe we can use it in an
Package: lazarus-src-3.8
Version: 3.8_3.8+dfsg1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
I upgraded lazarus from 3.6 to 3.8
* What exactly did you do (or not do) that was effective (or
ineffective)?
aptitude u
is component.
>
> I did check the dependency tree and it should not be too difficult. I am
> currently packaging one of the missing dependencies:
> https://github.com/compose-spec/compose-go (will post the ITP soon).
>
> --
> Nicolas Peugnet
>
>
--
regards,
Reinhard
Control: severity -1 important
Control: merge -1 1080433
Thanks for reporting this bug. It has been reported before on another
architecture.
Merging.
-rt
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-multiformats-go-base32
Version : 0.1.0-1
Upstream Author : Multiformats
* URL : https://github.com/multiformats/go-base32
* License : BSD-3-clause
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-multiformats-go-base36
Version : 0.2.0-1
Upstream Author : Multiformats
* URL : https://github.com/multiformats/go-base36
* License : Apache 2.0
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-ipfs-go-cid
Version : 0.4.1-1
Upstream Author : IPFS Project
* URL : https://github.com/ipfs/go-cid
* License : Expat
Programming Lang: Go
Description : Content ID
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-awslabs-soci-snapshotter
Version : 0.4.1-1
Upstream Author : Amazon Web Services - Labs
* URL : https://github.com/awslabs/soci-snapshotter
* License : Apache-2.0
Hi,
I've prepared a change that should fix this issue with the --delete
option in the debian tar package. Please review:
2 files changed, 56 insertions(+)
debian/patches/series | 1 +
.../tar-1.35-revert-fix-savannah-bug-633567.patch | 55
++
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-notaryproject-notation-go
Version : 1.2.1-1
Upstream Author : Notary Project
* URL : https://github.com/notaryproject/notation-go
* License : Apache-2.0
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-notaryproject-notation
Version : 1.2.0-1
Upstream Author : Notary Project
* URL : https://github.com/notaryproject/notation
* License : Apache-2.0
Programming Lang: Go
Hi Olaf,
Good news, aspectc++ built on most platforms in Debian :-)
https://buildd.debian.org/status/package.php?p=aspectc%2B%2B
On 2024-12-06 20:34, Adrian Bunk wrote:
Control: reopen -1
On Fri, Dec 06, 2024 at 01:21:04PM +, Debian Bug Tracking System
wrote:
...
aspectc++ (1:2.3+git20
Control: retitle -1 autopkgtest-virt-qemu sometimes hangs when large
number of build dependencies
I've looked more into the issue, and found that reducing the number of
packages avoids this issue.
I believe it is possible that the number of dependency is hitting some
limit, possibly with how
Curiously, disabling the autopkgtest `builtin-tests` (which strictly
speaking doesn't even require qemu), makes the package pass in debci:
https://salsa.debian.org/go-team/packages/podman/-/commit/0d29ddc882b313e4a397826a9cbea7fa593f1f8c
What's so special about this particular test?
Package: autopkgtest
Version: 5.42
Severity: normal
Dear Maintainer,
I'm observing that the podman package keeps failing with 'tmpfail' result:
https://ci.debian.net/packages/p/podman/testing/amd64/
Note that the package is configured to use qemu instead of debci. This
is holding up migration
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-notaryproject-notation-plugin-framework-go
Version : 1.0.0-1
Upstream Author : Notary Project
* URL :
https://github.com/notaryproject/notation-plugin-framework-go
* License
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-notaryproject-notation-core-go
Version : 1.1.0-1
Upstream Author : Notary Project
* URL : https://github.com/notaryproject/notation-core-go
* License : Apache-2.0
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-notaryproject-tspclient-go
Version : 0.2.0-1
Upstream Author : Notary Project
* URL : https://github.com/notaryproject/tspclient-go
* License : Apache-2.0
Programming Lang
Control: owner -1 !
Glad to help!
I'll keep adding "blocks" relationships to this bug as I identify
additional missing dependencies.
best,
-rt
On Sun, Nov 17, 2024 at 6:59 AM Suyan wrote:
> Hi, Reinhard!
>
> Thanks for the heads up.
> I'm not currently workin
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-fahedouch-go-logrotate
Version : 0.2.1-1
Upstream Author : fahed dorgaa
* URL : https://github.com/fahedouch/go-logrotate
* License : Apache-2.0
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-rootless-containers-bypass4netns
Version : 0.4.1-1
Upstream Author : Akihiro Suda, https://github.com/AkihiroSuda
* URL : https://github.com/rootless-containers/bypass4netns
On 2024-11-15 11:10, Jonathan Wiltshire wrote:
Control: tag -1 moreinfo
Hi,
I'm fine with these changes, but what you've uploaded doesn't match the
proposal because 0.0~git20230203.6f710f8-1+deb12u2 has never been in
the
archive. Do you want to upload it as well and I'll take both, or shall
I
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-freddierice-go-losetup
Version : 2.0.1-1
Upstream Author : Freddie Rice
* URL : https://github.com/freddierice/go-losetup
* License : Expat
Programming Lang: Go
uild, deploy, and manage containers
> in production environments.
> The goal of nerdctl is to facilitate experimenting the cutting-edge
> features of containerd that are not present in Docker.
> The packages that nerdctl depends on all exist in Debian, such as
> containerd.
> Our team is packaging and maintaining this package.
>
>
--
regards,
Reinhard
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-containerd-nydus-snapshotter
Version : 0.13.4-1
Upstream Author : containerd
* URL : https://github.com/containerd/nydus-snapshotter
* License : Apache-2.0
Programming
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-karpeleslab-reflink
Version : 1.0.1-1
Upstream Author : Karpelès Lab Inc.
* URL : https://github.com/KarpelesLab/reflink
* License : Expat
Programming Lang: Go
Hi Andrea,
Please consider merging
https://salsa.debian.org/debian-iot-team/mbedtls/-/merge_requests/5
It does fix the arm64 build failure as evidenced here:
https://salsa.debian.org/siretart/mbedtls/-/jobs/6573314
Best,
-rt
Hi Ford,
seems that pong2 needs some updates. Are you interested in keeping it
alive for trixie? If so, maybe you could make a new upstream release that
we could package in Debian?
Many greetings!
-rt
Matthias Klose writes:
> Package: src:pong2
> Version: 0.1.3-3
> Severity: important
> Tags:
kworm; urgency=medium
+
+ * Team upload
+ * apt_info.py: fix apt_upgrades_pending and apt_upgrades_held, Closes:
#1077694
+
+ -- Reinhard Tartler Wed, 06 Nov 2024 20:15:44 -0500
+
prometheus-node-exporter-collectors (0.0~git20230203.6f710f8-1+deb12u2)
bookworm; urgency=medium
* Team upload
Package: criu
Version: 3.17.1-3
Severity: normal
Dear Maintainer,
while working on #1054814, I've thought that running the upstream
testsuite might be a good idea. The testsuite is fairly comprehensive,
and not exactly straight-forward to run, but I got it to (mostly) pass
using qemu running as r
Control: tag -1 patch
I believe the change in
https://salsa.debian.org/debian/criu/-/merge_requests/4 should address
this issue.
Best,
-rt
Package: criu
Version: 3.17.1-3
Severity: normal
Please update to upstream version 3.19
See release notes:
https://criu.org/Download/criu/3.18
https://criu.org/Download/criu/3.19
We had to upgrade the golang bindings to version 7.2, and it appears that they
require newer versions of criu than w
s-node-exporter-collectors (0.0~git20230203.6f710f8-1+deb12u3)
unstable; urgency=medium
+
+ * Non Maintainer Upload
+ * apt_info.py: fix apt_upgrades_pending and apt_upgrades_held, Closes:
#1077694
+
+ -- Reinhard Tartler Sat, 02 Nov 2024 08:22:11 -0400
+
prometheus-node-exporter-collectors (0.
Santiago Vila writes:
> Package: src:moment-timezone.js
> Version: 0.5.45+dfsg-1+2024a
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
>
> ---
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-areyoulazy-libhosty
Version : 2.0.1-1
* URL : https://github.com/areYouLazy/libhosty
* License : Apache-2.0
Programming Lang: Go
Description : A pure golang library to
Reinhard Tartler writes:
> Jochen Sprickerhof writes:
>
>> Source: golang-github-containerd-cgroups
>> Version: 1.0.4-1
>> Severity: normal
> can you please show a build log that fails because of the unshare change in
> sbuild?
>
> I'd like to make sure
Jochen Sprickerhof writes:
> Source: golang-github-containerd-cgroups
> Version: 1.0.4-1
> Severity: normal
>
> Hi,
>
> src:golang-github-containerd-cgroups tries to access
> /sys/kernel/mm/hugepages which is not guaranteed to be there in
> containers:
>
> https://systemd.io/CONTAINER_INTERFACE/
Hi Moritz,
I've forwarded this bug upstream on their Matrix channel, and to their
github at: https://github.com/containers/podman/issues/24192
Seems upstream believes a remediation requires code changes in the Linux
kernel. What's the best way to proceed with this bug here?
-rt
Control: reopen -1
Control: reassign -1 ftp.debian.org
Control: retitle -1 RoM: Please remove src:libpod from unstable
We followed upstream's renaming libpod->podman (finally), and now start
accumulating (RC) bugs for src:libpod.
It seems it is (no longer) showing up on
https://ftp-master.debia
Control: found 1.35+dfsg-3
I can still reproduce this while trying to run the podman upstream test
suite. This has been noted as a bug before in
https://github.com/containers/podman/issues/21373.
Interestingly, this has been reported as fixed in 1.35 (cf.
https://git.savannah.gnu.org/cgit/ta
reassign 994454 libpod
close 5.2.0+ds1-5
affects 994454 golang-github-containers-common
thanks
"Bastien Roucariès" writes:
> Package: golang-github-containers-common
> Severity: important
>
> Dear Maintainer,
>
> This package [golang-github-containers-common] is used in conjunction
> of podman
Package: golang-github-coreos-pkg-dev
Version: 4-3
Severity: important
Dear Maintainer,
Your package has autopkgtest, that's great! Unfortunately, on ppc64el,
it has failed three times in a row:
https://ci.debian.net/packages/g/golang-github-coreos-pkg/testing/ppc64el/51243460/
https://ci.debia
On 2024-09-01 09:29, Reinhard Tartler wrote:
I currently suspect that this is actually a timing issue indicating a
flaky
test. I've retriggered the autopkgtest to see if that theory holds.
FTR: that run did succeed:
https://ci.debian.net/packages/c/crowdsec/unstable/arm64/51181261/
Does
On 2024-09-01 08:34, Cyril Brulebois wrote:
Hey Kibi, thanks for your prompt response!
Reinhard Tartler (2024-09-01):
While working on updating the docker.io package in experimental, I've
noticed an autopkgtest failure on arm64 that did not happen on amd64:
https://ci.debian.net/packa
Package: crowdsec
Version: 1.4.6-9
Severity: important
Dear Maintainer,
While working on updating the docker.io package in experimental, I've noticed an
autopkgtest failure on arm64 that did not happen on amd64:
https://ci.debian.net/packages/c/crowdsec/unstable/arm64/51171995/
274s === RUN T
om: Hadmut Danisch
To: Reinhard Tartler
Cc: 1054...@bugs.debian.org
On 31.08.24 16:12, Reinhard Tartler wrote:
Do you have thoughts on how do we provide an upgrade path from existing
systems to this new file?
Soft way:
Just add this template to the package (it will do no harm unless
actived) a
On 2024-08-31 08:31, Hadmut Danisch wrote:
Attached is the unit file (template type) I wrote and that works for me
to run multiple instances.
Do you have thoughts on how do we provide an upgrade path from existing
systems to this new file?
-rt
Control: severity -1 wishlist
Control: tag -1 help
Hadmut Danisch writes:
> the debian package for the docker-registry is built to run exactly one
> instance with exactly one config file.
This is correct, and keeps the package easy and simple to use for the
intended use-case.
> However, the d
retitle -1 test_with_chroot is flaky
Hi,
Seems I made a mistake in my previous report. It is actually the test
'test_without_chroot' that is flaky. Also, I noticed this comment in
https://sources.debian.org/src/reform-setup-wizard/1.0-11/debian/tests/control/#L7-L25:
# Since this test is ski
Package: reform-setup-wizard
Severity: serious
Version: 1.0-11
Hallo Johannes,
I notice that the autopkgtest
https://sources.debian.org/src/reform-setup-wizard/1.0-11/debian/tests/test_without_chroot/
is not running reliably:
https://ci.debian.net/packages/r/reform-setup-wizard/unstable/amd64/
On 2024-08-24 11:28, Étienne Mollier wrote:
Hi Reinhard,
Reinhard Tartler, on 2024-08-24:
Actually, I've been able to compile pystack on the machine
(see https://github.com/bloomberg/pystack, and amazing tool)
and was able to get a trace of what the stuck process is doing:
This is a
On 2024-08-23 15:59, Étienne Mollier wrote:
Control: tags -1 + confirmed
Hi Reinhard,
Thanks for your time investigating this issue! On the good news
front, I confirm I can reproduce the problem with qemu-user, so
this facilitate debugging even without direct access to the real
hardware
Source: python-biopython
Version: 1.83+dfsg1-3
Severity: important
I've been looking at why debci appears to be stuck on riscv64 for the
python-biopython package:
https://ci.debian.net/packages/p/python-biopython/testing/riscv64/
For that reason, I've been trying to reproduce it on the debian po
Source: mediaconch
Version: 24.06-1 fail
Severity: important
Here are recent instances where the test
https://sources.debian.org/src/mediaconch/24.06-1/debian/tests/check-mediaconch-gui/#L28
has failed on armhf:
https://ci.debian.net/packages/m/mediaconch/testing/armel/50799168/
https://ci.debia
Control: retitle -1 Integration tests are flaky
Control: severity -1 important
Control: forwarded -1 https://github.com/onsi/ginkgo/issues/1452
This test failure has happened before, and appears to consistently
succeed on a retry.
For this reason, I took the liberty of downgrading the issue sev
Control: retitle -1 docker-registry: FLAKY test:
DriverSuite.TestDeleteOnlyDeletesSubpaths
Control: severity -1 important
Thanks for filing this report.
Looking at the test code in
https://sources.debian.org/src/docker-registry/2.8.2%2Bds1-1/registry/storage/driver/testsuites/testsuites.go/#L7
in sid as well (modulo
being built by
the buildds).
Best,
-rt
--
regards,
Reinhard
Niko Tyni writes:
>
> This package fails to build from source on current sid.
>
>../../../enforcer/src/utils/kaspcheck.c:101:33: error: implicit
> declaration of function ‘exit’ [-Wimplicit-function-declaration]
> 101 | exit(0);
> |
On 2024-08-11 12:55, Johannes Schauer Marin Rodrigues wrote:
Hi,
Quoting Reinhard Tartler (2024-08-11 17:25:00)
while looking at
https://ci.debian.net/packages/r/reform-setup-wizard/unstable/arm64/50343230/
I
noticed that your package is using podman to run an autopkgtest:
https
On 2024-08-11 11:50, Diederik de Haas wrote:
For Debian, I do think that this workaround is acceptable, at least
for
the purposes of allowing further testing in the "testing"
Distribution,
so that we get additional datapoints whether there actually are
runtime
issues that stem from unitialized
nd an improved patch attached to this message
Best,
-rtFrom: Reinhard Tartler
Date: Sat, 3 Aug 2024 10:46:50 -0400
Subject: don't fail on maybe-uninitialized warnings
Bugs-Upstream: https://github.com/WasmEdge/WasmEdge/issues/3640
This warning was introduced with gcc 14. It is likely a fals
Source: reform-setup-wizard
Version: 1.0-7
Severity: important
Hi,
while looking at
https://ci.debian.net/packages/r/reform-setup-wizard/unstable/arm64/50343230/ I
noticed that your package is using podman to run an autopkgtest:
https://sources.debian.org/src/reform-setup-wizard/1.0-7/debian/tes
On 2024-08-11 08:55, Diederik de Haas wrote:
On 03 Aug 2024 11:08:58 -0400 Reinhard Tartler
wrote:
I noticed this package is listed as low-NMU. As such, I'm taking the
liberty of uploading the following patch as NMU to sid:
...
new file debian/patches/don-t-fail-on-unknown-gcc-warnings.
i-team/autopkgtest/-/merge_requests/396
> Control: tags -1 + help
>
> On Sat, 10 Aug 2024 at 11:24:51 -0400, Reinhard Tartler wrote:
> > I personally find that wording a bit too strong. How about something like
> > this:
> >
> ...
> > > However, this also
On 2024-08-09 04:52, Simon McVittie wrote:
On Thu, 08 Aug 2024 at 11:12:07 -0400, Reinhard Tartler wrote:
In short, it seems to me if you are running a workload that requires
CAP_SYS_ADMIN,
then it is appropriate to pass that argument to podman. It is clearly
much
better than
using
ter than
using --privileged (cf.
https://www.redhat.com/sysadmin/podman-inside-container)
Since you assigned this bug to podman, may I ask what the ask is?
It's not clear how to improve the podman packaging in this context.
--
regards,
Reinhard
Simon McVittie writes:
> It is possible to run systemd + polkitd inside a podman container by
> running it as "podman run ... --cap-add=CAP_SYS_ADMIN", but I am unsure
> whether this undermines or defeats podman's security model. A question
> for the podman maintainers: what is the security impa
Package: golang-github-opencontainers-runc-dev
Version: 1.1.12+ds1-3
Severity: wishlist
Dear Maintainer,
Please package https://github.com/opencontainers/runc/releases/tag/v1.1.13
This is the thirteenth patch release in the 1.1.z release branch of runc. It
brings in Go 1.22.x compatibility and f
Source: lxd
Version: lxd_5.0.2+git20231211.1364ae4-5
Severity: important
I'm currently updating go-criu from v6 to v7, and noticed that both the the lxd
package FTBFS with this change:
117s src/github.com/canonical/lxd/lxd/instance/drivers/driver_lxc.go:26:2:
cannot find package "github.com/chec
Source: incus
Version: 6.0.1-1
Severity: important
I'm currently updating go-criu from v6 to v7, and noticed that both the incus
as well as the lxd package FTBFS with this change:
102s
src/github.com/lxc/incus/internal/server/instance/drivers/driver_lxc.go:28:2:
cannot find package "github.com/
On Mon, Aug 5, 2024 at 2:44 PM Paul Gevers wrote:
> Hi
>
> On 05-08-2024 14:03, Reinhard Tartler wrote:
> > I need some help to understand how skipped tests lead to delaying the
> > package migration to testing. My naive understanding is that this flag
> > would rather
> In Jonas' defence, it is everything but obvious on what exactly to
> declare the Breaks relationships.
Sorry, I mean to write: "In Jonas' defense, it is absolutely NOT obvious".
My bad.
-rt
Matthias Geiger writes:
> - From my limited observation this only happens in experimental for rust
> crates. I don't know what causes this. The autopkgtest ran fine when I
> built the packages before uploading.
I believe this problem is much more widespread in testing than
experimental and is ho
ntrol.rs?ref_type=heads#L149,
but before proposing that, I'd need to understand your concern better.
My question is basically: what needs to be done so that
https://tracker.debian.org/pkg/rust-event-listener can actually migrate
testing?
--
regards,
Reinhard
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: rust-async-broadc...@packages.debian.org,
debian-r...@lists.debian.org
Control: affects -1 + src:rust-async-broadcast
User: release.debian@packages.debian.org
Usertags: binnmu
nmu rust-async-broadcast_0.7.1-1 . riscv64 . unstable . -m
Source: golang-github-backblaze-blazer
Version: 0.6.2-1
Severity: serious
Tags: upstream ftbfs
Justification: FTBFS
X-Debbugs-Cc: debian...@lists.debian.org
Your package currently FTBFS:
# github.com/Backblaze/blazer/internal/pyre/proto
src/github.com/Backblaze/blazer/internal/pyre/proto/pyre.pb.
On 2024-08-04 07:53, Paul Gevers wrote:
Agree. I'm a bit surprised it's printed, because I thought output to
stdout at that level would already be ignored (as you can see in my
comments in the merge request [1]). I'll think about the best solution
(probably just 2> /dev/null) as I don't think
On 2024-08-04 03:08, Paul Gevers wrote:
Control: tags -1 moreinfo
Hi Reinhard,
I'm puzzled.
On 03-08-2024 23:58, Reinhard Tartler wrote:
diff --git a/setup-commands/create-normal-user
b/setup-commands/create-normal-user
index 0d0e828..9d66694 100755
--- a/setup-commands/create-normal
Would you consider the following patch? It makes autopkgtest work for me:
diff --git a/setup-commands/create-normal-user
b/setup-commands/create-normal-user
index 0d0e828..9d66694 100755
--- a/setup-commands/create-normal-user
+++ b/setup-commands/create-normal-user
@@ -21,7 +21,7 @@ create ()
Package: autopkgtest
Version: 5.37
Severity: normal
Dear Maintainer,
I'm trying to use the autopkgtest podman server to run a test that
requires the capability "isolation-container". From the manpage, I
understand that I need to create a container image with like this:
$ autopkgtest-build-podma
1 - 100 of 1138 matches
Mail list logo
