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
On Mon, Aug 12, 2024 at 8:03 AM Helmut Grohne wrote:
>
> I also appreciate a reply explaining why these were reintroduced (and
> I'm hoping for something along the lines of "by accident"). If there are
> any problems with moving the files, please let me know.
>
Sorry, that was re-introduced by a
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
On Thu, Aug 8, 2024 at 10:42 AM Simon McVittie wrote:
> > For rootless podman the situation is less clear, but from a security
> > assessment POV, I would consider any process running as root in the
> container
> > [with CAP_SYS_ADMIN] to have the same privileges as the UID starting
> > the conta
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
On Sun, Aug 4, 2024 at 10:27 PM Jeremy Bícha
wrote:
> That is not the actual contents of the .deb. Download the .deb and
> open it in file-roller or something to check for yourself. Or look at
> the build log.
>
> https://buildd.debian.org/status/package.php?p=rust-async-broadcast
>
> Some Rust a
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
| 20
debian/patches/series| 1 +
modified debian/changelog
@@ -1,3 +1,10 @@
+wasmedge (0.13.5+dfsg-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS with gcc-14, Closes: #1075633
+
+ -- Reinhard Tartler Sat, 03 Aug 2024 11:
Hi,
I took the liberty of uploading the proposed change above as an NMU to the
archive.
This is following the procedure outlined at
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu
* Upload fixing only release-critical bugs older than 7 days, with no
maintainer activity
@@
+google-guest-agent (2026.00-6.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Build against google/protobuf@v1.5, Closes: #109
+
+ -- Reinhard Tartler Sat, 03 Aug 2024 10:32:11 -0400
+
google-guest-agent (2026.00-6.1) unstable; urgency=medium
* Non-maintainer
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-k8s-apiserver
Version : 0.20.15
Upstream Author : Kubernetes authors
* URL or Web page : https://github.com/kubernetes/apimachinery
* License : Apache-2.0
Programming lang: golang
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-containerd-aufs
Version : 1.0.0-1
Upstream Author : containerd
* URL : https://github.com/containerd/aufs
* License : Apache-2.0
Programming Lang: Go
Description
Control: tag -1 confirmed
Adrian Bunk writes:
> Source: containerd
> Version: 1.7.18~ds1-4
> Severity: serious
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/c/containerd/49714060/log.gz
>
> ...
> 10s
> src/github.com/containerd/containerd/cmd/containerd/builtins/aufs_linux.go:21:8:
>
ts-0.5.1+git20240203.4e34d9b+ds1/debian/changelog 2024-04-26 09:44:36.0 -0400
+++ mirrorbits-0.5.1+git20240203.4e34d9b+ds1/debian/changelog 2024-07-28 14:24:29.0 -0400
@@ -1,3 +1,10 @@
+mirrorbits (0.5.1+git20240203.4e34d9b+ds1-2.1) unstable; urgency=medium
+
+ * Non-maintain
Source: mirrorbits
Version: 0.5.1+git20240203.4e34d9b+ds1-2
Severity: serious
Tags: ftbfs
Justification: FTBFS
The package mirrorbits has uninstallable build-dependencies. I've tried to work
around this by building it against golang-github-golang-protobuf-1-5-dev
instead.
This is causing this er
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: golang-github-gogo-sta...@packages.debian.org,
debian...@lists.debian.org
Control: affects -1 + src:golang-github-gogo-status
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove the package golang-github-gogo-status from u
axum is already at the thirty-first
revision. Are the autopkgtests passing on your computer? I wonder what
can be done avoid needing that many uploads, causing avoidable load on
the test machines and help unblocking other packages from their
migration to testing faster.
best,
-rt
From: Reinhard Tartl
On 2024-07-24 10:42, Jochen Sprickerhof wrote:
* Reinhard Tartler [2024-07-24 09:36]:
Looking closer at the tests, it appears that they are iterating over
all installed network interfaces, and try to query them for
statistics. In that 'unshare -nr' context, they still find
On 2024-07-24 09:11, Jochen Sprickerhof wrote:
While you are correct that the buildd did succeed but please note that
the bug is not fixed and can still be reproduced with sbduild
--chroot-mode=unshare and on the reproducible builds infrastructure, as
noted by Santiago above. Please also note
I'd appreciate any kind of reply, ideally in the form of: "please hold of,
here is a list
of things we need to consider and/or look at first.".
thank you so much for your assistance!
-rt
On Sat, Jul 13, 2024 at 6:53 PM Reinhard Tartler wrote:
> Hi,
>
> We currently shi
Control: reopen -1
On Sat, Jul 20, 2024 at 8:45 AM Jonas Smedegaard wrote:
> Quoting Reinhard Tartler (2024-07-20 08:10:13)
> > with the patch above, autopkgtest now passes for me. Find the buildlog
> > attached.
> >
> > If it helps you, I could upload as an NMU ma
al compilation constraint throughout the
codebase that allows `cargo test --no-default features`, as well as
`--no-default-fetaures --features $F` for $F in all features indivually
to pass.
Thank you for your timely reponses!
From: Reinhard Tartler
Date: Sat, 20 Jul 2024 07:05:45 +0200
Subje
Control: reopen -1
> Oh - now after I did a release without the feature-fencing patch, I
> found the relevant build log:
> https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-axum/47457177/log.gz
the most recent run at
https://ci.debian.net/packages/r/rust-axum/testing/amd64/49206913/
fai
Aurelien Jarno writes:
> I have just uploaded a NMU to delayed/2 using the above strategy. Please
> feel free to ask me to delay or cancel it. You will find the
> corresponding debdiff attached.
I've looked over the patch, it LGTM. Thank you for providing the patch!
I understand it is going to
Reinhard Tartler writes:
> Why does this error not reproduce outside of autopkgtest? -- either some
> dependency mismatch in debian, or somethign really subtle in
> autopkgtest. In either case, I'd like to keep my suggestion to disable
> the failing tests in in debian/tests/con
> Quoting Jonas Smedegaard (2024-07-17 09:22:41)
>
> Oh - now after I did a release without the feature-fencing patch, I
> found the relevant build log:
> https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-axum/47457177/log.gz
Thanks. At the end of the log, we see this summary:
1760s a
Reinhard Tartler writes:
> Source: rust-axum
> Version: 0.6.20-21
> Severity: serious
> Tags: ftbfs
> Justification: FTBFS
>
> Seem the buildds are having trouble building this package:
>
> error[E0433]: failed to resolve: use of undeclared type `TestClient`
>
Source: rust-axum
Version: 0.6.20-21
Severity: serious
Tags: ftbfs
Justification: FTBFS
Seem the buildds are having trouble building this package:
error[E0433]: failed to resolve: use of undeclared type `TestClient`
--> axum/src/routing/tests/mod.rs:1039:18
|
1039 | let client = Test
On Sat, Jul 13, 2024 at 2:57 PM Simon Josefsson wrote:
> Reinhard Tartler writes:
>
> > My takeaway is that we need to update a large number of packages at the
> > same time, starting with src:golang-google-genproto
> > and src:golang-google-grpc. This will unblock a
Hi,
We currently ship docker version 20.10 in Debian oldstable, stable and
currently testing. This is an EOL version that I really don't think Debian
trixie should be shipping with.
I've been working over the last couple of weeks (months?) on updating
podman and docker to recent versions, includi
On 2024-07-13 11:59, Matthias Geiger wrote:
ncts thankfully ported netavark to zbus 4.0 [0]. Unless you object I'd
flip the switch tomorrow and upload zbus 4.0 to unstable. The patch
from the PR should work fine; I will create a MR on salsa later.
That's awesome!
[0] https://github.com/co
Simon Richter writes:
> I have several containers that are allowed to address the docker
> instance they are running on to start additional containers, without
> ever having a need to run the docker daemon themselves.
>
> Since Docker has quite an extensive list of dependencies, it would be
> nic
Control: tag -1 confirmed
On Tue, Jun 4, 2024 at 12:39 PM Eberhard Beilharz wrote:
>
> It looks like the version of buildah included in Debian (and Ubuntu)
> doesn't
> support heredocs although this has been fixed for a while in upstream. It
> looks
> like that patch got intentionally reverted i
Source: rust-parsec-interface
Version: 0.29.1-1
Severity: serious
Tags: upstream ftbfs
Justification: FTBFS
Forwarded: https://github.com/parallaxsecond/parsec-interface-rs/issues/152
I'm getting a bunch of "unnecessary qualification" issues:
@siretart ➜ /workspaces/parsec-interface-rs (main) $
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org
* Package name: golang-github-distribution-reference
Version : 0.6.0-1
Upstream Author : Distribution
* URL : https://github.com
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-moby-docker-image-spec
Version : 1.3.1-1
Upstream Author : Moby
* URL : https://github.com/moby/docker-image-spec
* License : Apache-2.0
Programming Lang: Go
Description
Antoine Sirinelli writes:
> When I create a new custom network, the dns is not enabled:
>
> $ podman network create test
> test
> $ podman network inspect test
> [
> {
> "name": "test",
> "id":
> "9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08",
>
Control: reassign -1 init-system-helpers
Paul Menzel writes:
> Dear Debian folks,
>
>
> On Debian sid/unstable installing *docker.io* the error below is shown:
>
> Setting up docker.io (20.10.14+dfsg1-1+b1) ...
> Installing new version of config file /etc/default/docker ...
> Inst
On 2024-07-02 07:29, Prusty, Badrikesh wrote:
I have created, "bp/docker26" branch in my fork, did some incremental
changes to fix override_dh_auto_install:
https://salsa.debian.org/badrikesh/docker/-/commits/bp%2Fdocker26
62f28e5 golang-github-docker-docker-dev.install: update install files
Control: Retitle -1 docker.io -- please update to v26.0.0 or above
On 2024-06-12 03:00, Prusty, Badrikesh wrote:
As we know there are many golang dependencies that requires update and
some new golang dependencies are also needed to be added for Docker 24
and above.
So, there are some major de
Package: gnome-session
Version: 46.0-2
Severity: wishlist
Please make gnome-desktop depend on xdg-desktop-portal-gnome.
Currently, gnome-session has Depends: xdg-desktop-portal-gnome |
xdg-desktop-portal-backend
If a gnome user manages to end up with xdg-desktop-portal-gtk installed without
xdg
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: golang-github-kurin-bla...@packages.debian.org,
debian...@lists.debian.org
Control: affects -1 + src:golang-github-kurin-blazer
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove the package golang-github-kurin-blazer fro
I just realized that we have an open bug that we can use to track this,
so let me post a status with some context.
On Sun, Jun 23, 2024 at 1:38 PM Reinhard Tartler wrote:
>
> On Sat, Jun 22, 2024 at 7:01 PM Reinhard Tartler
> wrote:
>
>>
>> I took the liberty of packag
On 2024-06-28 09:49, Maytham Alsudany wrote:
Letting you know that trillian doesn't need to be packaged anymore (it
was only a test dependency of golang-google-go-tpm-dev, and so I just
disabled the tests).
I managed to get trillian updated to build against the version of
grpc/genproto we have
Package: golang-github-grpc-ecosystem-grpc-gateway-dev
Severity: normal
Version: 1.16.0-4
Dear Maintainer,
I'm currently looking at updating GRPC in Debian and am staging all changes in
experimental.
When trying to update your package, I noticed that it does build fine with the
newer GRPC,
but
Package: golang-github-lightstep-lightstep-tracer-common-dev
Severity: normal
Dear Maintainer,
This package currently depends on https://github.com/gogo/protobuf,
which is deprecated and hasn't been updated in two years.
Is this still maintained upstream and needed in Debian? If not, please
cons
Package: golang-google-cloud
Severity: normal
Dear Maintainer,
I'm trying to update the grpc package in Debian and am currently staging
all relevant packages in experimental. For this, I'm test rebuild all
packages and encountered an issue in the 'golang-google-cloud' package.
during the rebuild
Control: tag -1 +help
Maytham Alsudany writes:
> This package is severely outdated, and a new version is needed for
> github.com/google/trillian (indirect dependency of miniflux).
I took a look at updating this package, because I suspect it will be
needed for newer versions of golang-google-grp
Denis Manente writes:
> If the package is no longer being maintained, maybe it would be better to
> remove it completely.
I'm working on updating the package to the latest upstream version. I'm
interested in seeing a usable and maintained version of the cfssl
program, as well as the libraries as
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: zcrypto
Version : 0.0~git20240512.0fef58d-1
Upstream Author : The ZMap Project
* URL : https://github.com/zmap/zcrypto
* License : Apache 2.0, ISC, MIT
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-zmap-zlint
Version : 3.6.2-1
Upstream Author : The ZMap Project
* URL : https://github.com/zmap/zlint
* License : Apache-2.0
Programming Lang: Go
Description : X.509
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-cloudflare-backoff
Version : 0.0~git20161212.647f3cd-1
Upstream Author : Cloudflare
* URL : https://github.com/cloudflare/backoff
* License : BSD-2-clause
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: fulcio
Version : 1.4.5-1
Upstream Author : sigstore
* URL : https://github.com/sigstore/fulcio
* License : Apache-2.0
Programming Lang: Go
Description : Sigstore OIDC PKI
Fulcio
Source: golang-github-containerd-cgroups
Severity: wishlist
Please package new upstream version 3.0.0
It is needed for containerd 1.7 and podman
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental')
Architec
Source: containerd
Severity: wishlist
X-Debbugs-Cc: debian...@lists.debian.org
Docker 26+ requires updated versions of containerd 1.7.
Also, this version is moving away from gogoproto, which helps untangling the
protobuf mess.
I'm currently working on this and have a building source package. Ho
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: golang-gogott...@packages.debian.org
Control: affects -1 + src:golang-gogottrpc
User: ftp.debian@packages.debian.org
Usertags: remove
The binary package gogottrpc is no longer built from source. Please remove it
from unstable to allow src
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-containerd-imgcrypt
Version : 1.1.11-1
Upstream Author : containerd
* URL : https://github.com/containerd/imgcrypt
* License : Apache-2.0
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-containerd-log
Version : 0.1.0-1
Upstream Author : containerd
* URL : https://github.com/containerd/log
* License : Apache-2.0
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-kubernetes-cri-api
Version : v0.25.3
Upstream Author : Kubernetes
* URL : https://github.com/kubernetes/cri-api
* License : Apache-2.0
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-containerd-nri
Version : 0.6.1-1
Upstream Author : containerd
* URL : https://github.com/containerd/nri
* License : Apache-2.0
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-containerd-errdefs
Version : 0.1.0-1
Upstream Author : containerd
* URL : https://github.com/containerd/errdefs
* License : Apache-2.0
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: protobuild
Version : 0.3.0-1
Upstream Author : containerd
* URL : https://github.com/containerd/protobuild
* License : Apache-2.0
Programming Lang: Go
Description : Build
Jochen Sprickerhof writes:
> containerd uses sysctl during the build which fails as a normal user:
>
> === RUN TestLinuxSandboxContainerSpec
> sandbox_run_linux_test.go:241: TestCase "spec should reflect original
> config"
> sandbox_run_linux_test.go:71: Check PodSandbox annotations
Adding debian-go@, I think this topic deserves a wider audience
On Mon, Jun 3, 2024 at 2:31 PM Reinhard Tartler wrote:
> Basically notary insists on golang-github-golang-protobuf-1-3-dev,
> whereas golang-github-grpc-ecosystem-grpc-gateway.v2-dev (which is coming
> via the opentelem
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: golang-github-google-cel...@packages.debian.org,
debian...@lists.debian.org
Control: affects -1 + src:golang-github-google-cel-go
User: ftp.debian@packages.debian.org
Usertags: remove
I don't know what happened here, but somehow we ended
Package: wnpp
Owner: Reinhard Tartler
Severity: wishlist
* Package name: golang-github-go-jose-go-jose.v3
Version : 3.0.3
Upstream Author : https://github.com/go-jose/go-jose
* URL or Web page : https://github.com/go-jose/go-jose
* License : Apache 2.0
Description
Package: golang-opentelemetry-contrib-dev
Version: 0.25.0-1
Severity: normal
$ apt install -s golang-opentelemetry-contrib-dev
NOTE: This is only a simulation!
apt needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the rele
1 - 100 of 1031 matches
Mail list logo
