> === RUN TestRuleAddAndLoad
> seccomp_test.go:588: Syscall should have returned error code!
> --- FAIL: TestRuleAddAndLoad (0.00s)
Source code is here:
https://sources.debian.org/src/golang-github-seccomp-libseccomp-golang/0.9.1-2/seccomp_test.go/#L529-L589
This test is basically
> === RUN TestRuleAddAndLoad
> seccomp_test.go:588: Syscall should have returned error code!
> --- FAIL: TestRuleAddAndLoad (0.00s)
Source code is here:
https://sources.debian.org/src/golang-github-seccomp-libseccomp-golang/0.9.1-2/seccomp_test.go/#L529-L589
This test is basically
> === RUN TestRuleAddAndLoad
> seccomp_test.go:588: Syscall should have returned error code!
> --- FAIL: TestRuleAddAndLoad (0.00s)
Source code is here:
https://sources.debian.org/src/golang-github-seccomp-libseccomp-golang/0.9.1-2/seccomp_test.go/#L529-L589
This test is basically
Control: tag -1 pending
Hello,
Bug #976543 in golang-github-rcrowley-go-metrics reported by you has been fixed
in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: forwarded -1 https://github.com/shirou/gopsutil/issues/881
I'm having a hard time seeing bugs like this as RC-critical. Looking at
the testsuite more specifically, I strongly believe this is upstream bug
https://github.com/shirou/gopsutil/issues/881
Lucas, can you please post
Control: forwarded -1 https://github.com/shirou/gopsutil/issues/881
I'm having a hard time seeing bugs like this as RC-critical. Looking at
the testsuite more specifically, I strongly believe this is upstream bug
https://github.com/shirou/gopsutil/issues/881
Lucas, can you please post
On Fri, Oct 30, 2020 at 5:31 AM Shengjing Zhu wrote:
>
> > I suspect this could be related to version of golang, in
> > unstable/testing it is 1.15 so we may need the newer golang version.
> > Can someone confirm if this is indeed the case? If yes, do we plan to
> > backport golang 1.15? I can
On Wed, Dec 9, 2020 at 2:32 PM Paul Gevers wrote:
>
> These kind of build failures should be fixed. Builds that regularly fail
> are not OK. Same goes for autopkgtest. Flaky tests are RC.
>
Agreed.
> > What's involved with retrying autopkgtests on arm64? -- CC'ing
> > debian-release@, maybe
successfully. That's why I'm optimistic about
retrying the autopkg tests for consul.
What's involved with retrying autopkgtests on arm64? -- CC'ing
debian-release@, maybe they have some input?
Best,
-rt
On Mon, Dec 7, 2020 at 6:43 AM Reinhard Tartler wrote:
> Ok, thanks!
>
> I have
On 12/6/20 4:03 PM, Joerg Jaspert wrote:
> Hi Maintainer,
>
> the following are comments from a review one ftp trainee has done on
> your package. While I will accept your package (nothing warrants a
> reject), please fix them in your next upload.
> [...]
Thank you again to whoever did this
Control: tag -1 pending
Hello,
Bug #975584 in consul reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
On Fri, Dec 4, 2020 at 3:24 PM Aurelien Jarno wrote:
>
> I have tried and for me the issue is reproducible with both old and new
> glibc. I am therefore reassign the bug to libpod.
>
This is because of an upstream update in a dependency. It should be very
straight-forward to fix. Unfortunately,
On Fri, Dec 4, 2020 at 3:24 PM Aurelien Jarno wrote:
>
> I have tried and for me the issue is reproducible with both old and new
> glibc. I am therefore reassign the bug to libpod.
>
This is because of an upstream update in a dependency. It should be very
straight-forward to fix. Unfortunately,
On Fri, Dec 4, 2020 at 3:24 PM Aurelien Jarno wrote:
>
> I have tried and for me the issue is reproducible with both old and new
> glibc. I am therefore reassign the bug to libpod.
>
This is because of an upstream update in a dependency. It should be very
straight-forward to fix. Unfortunately,
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: dnsname
Version : 1.1.1-1
Upstream Author : Containers
* URL : https://github.com/containers/dnsname
* License : Apache-2.0
Programming Lang: Go
Description : name resolution
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: dnsname
Version : 1.1.1-1
Upstream Author : Containers
* URL : https://github.com/containers/dnsname
* License : Apache-2.0
Programming Lang: Go
Description : name resolution
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: dnsname
Version : 1.1.1-1
Upstream Author : Containers
* URL : https://github.com/containers/dnsname
* License : Apache-2.0
Programming Lang: Go
Description : name resolution
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: dnsname
Version : 1.1.1-1
Upstream Author : Containers
* URL : https://github.com/containers/dnsname
* License : Apache-2.0
Programming Lang: Go
Description : name resolution
suggest changes) and I thought that it might be an
>> idea to make an attempt to properly package it and add it to the Debian
>> archives.
>>
>> Will be keen to hear what others think.
>
> I was looking for the package and I'm glad that you are working on
> packagi
suggest changes) and I thought that it might be an
>> idea to make an attempt to properly package it and add it to the Debian
>> archives.
>>
>> Will be keen to hear what others think.
>
> I was looking for the package and I'm glad that you are working on
> packagi
suggest changes) and I thought that it might be an
>> idea to make an attempt to properly package it and add it to the Debian
>> archives.
>>
>> Will be keen to hear what others think.
>
> I was looking for the package and I'm glad that you are working on
> packagi
Awesome, thanks!
On Sat, Nov 28, 2020, 15:50 Antonio Terceiro wrote:
> Hello Reinhard,
>
> On Sat, Nov 28, 2020 at 10:57:52AM -0500, Reinhard Tartler wrote:
> > please go ahead with packaging catatonit. Regarding the symlink, I don't
> > have a strong preference, your p
Awesome, thanks!
On Sat, Nov 28, 2020, 15:50 Antonio Terceiro wrote:
> Hello Reinhard,
>
> On Sat, Nov 28, 2020 at 10:57:52AM -0500, Reinhard Tartler wrote:
> > please go ahead with packaging catatonit. Regarding the symlink, I don't
> > have a strong preference, your p
Hi Antonio,
sorry for taking so long to get back to you
On Thu, Nov 5, 2020 at 1:15 PM Antonio Terceiro wrote:
> On Wed, Oct 07, 2020 at 06:39:43PM -0300, Antonio Terceiro wrote:
> > Package: podman
> > Version: 2.0.6+dfsg1-1
> > Severity: normal
> > Tags: patch
> >
> > I was testing some
Hi Antonio,
sorry for taking so long to get back to you
On Thu, Nov 5, 2020 at 1:15 PM Antonio Terceiro wrote:
> On Wed, Oct 07, 2020 at 06:39:43PM -0300, Antonio Terceiro wrote:
> > Package: podman
> > Version: 2.0.6+dfsg1-1
> > Severity: normal
> > Tags: patch
> >
> > I was testing some
Package: golang-github-seccomp-libseccomp-golang-dev
Severity: normal
X-Debbugs-Cc: Reinhard Tartler
For packaging a newer upstream version of buildah, the following upstream patch
is required:
https://github.com/seccomp/libseccomp-golang/commit/24f29379854785de68bbd44630cc093b22b4dc29
Package: golang-github-seccomp-libseccomp-golang-dev
Severity: normal
X-Debbugs-Cc: Reinhard Tartler
For packaging a newer upstream version of buildah, the following upstream patch
is required:
https://github.com/seccomp/libseccomp-golang/commit/24f29379854785de68bbd44630cc093b22b4dc29
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-manifoldco-promptui
Version : 0.8.0-1
Upstream Author : Manifold
* URL : https://github.com/manifoldco/promptui
* License : BSD-3-clause
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-manifoldco-promptui
Version : 0.8.0-1
Upstream Author : Manifold
* URL : https://github.com/manifoldco/promptui
* License : BSD-3-clause
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-manifoldco-promptui
Version : 0.8.0-1
Upstream Author : Manifold
* URL : https://github.com/manifoldco/promptui
* License : BSD-3-clause
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler
* Package name: golang-github-manifoldco-promptui
Version : 0.8.0-1
Upstream Author : Manifold
* URL : https://github.com/manifoldco/promptui
* License : BSD-3-clause
Programming Lang: Go
Description
Source: golang-github-containernetworking-plugins
Severity: wishlist
X-Debbugs-Cc: lib...@packages.debian.org
Please upgrade the package. This is necessary for packaging libpod 2.1.
I'm currently getting this compilation failure:
# github.com/containers/libpod/libpod
Source: golang-k8s-sigs-structured-merge-diff
Severity: wishlist
X-Debbugs-Cc: lib...@packages.debian.org
In order to package podman 2.1, we need to upgrade the package
golang-k8s-sigs-structured-merge-diff to version 4.0 or later. Otherwise podman
fails to build with:
Control: close -1
Control: tag -1 unreproducible
Hi Harald,
On Sun, Sep 20, 2020 at 11:32 AM Reinhard Tartler
wrote:
> Control: tag -1 upstream
>
> On Sun, Sep 20, 2020 at 9:28 AM Harald Dunkel wrote:
>
>> I think there is a misunderstanding: The problem is not the error
Control: close -1
Control: tag -1 unreproducible
Hi Harald,
On Sun, Sep 20, 2020 at 11:32 AM Reinhard Tartler
wrote:
> Control: tag -1 upstream
>
> On Sun, Sep 20, 2020 at 9:28 AM Harald Dunkel wrote:
>
>> I think there is a misunderstanding: The problem is not the error
Control: tag -1 upstream
On Sun, Sep 20, 2020 at 9:28 AM Harald Dunkel wrote:
> I think there is a misunderstanding: The problem is not the error,
> but the error *message*. Can you do without complaining about bad
> HTTP code and URLs that don't work? Surely they don't give a hint
> about what
Control: tag -1 upstream
On Sun, Sep 20, 2020 at 9:28 AM Harald Dunkel wrote:
> I think there is a misunderstanding: The problem is not the error,
> but the error *message*. Can you do without complaining about bad
> HTTP code and URLs that don't work? Surely they don't give a hint
> about what
Control: tag -1 moreinfo
Hi Harald,
On Tue, Sep 15, 2020 at 1:51 AM Harald Dunkel wrote:
> Package: podman
> Version: 2.0.6+dfsg1-1
>
> Unprivileged podman dies with some gibberish instead of a readable
> error message:
>
> % podman run -it debian /bin/bash
> Trying to pull quay.io/debian...
Control: tag -1 moreinfo
Hi Harald,
On Tue, Sep 15, 2020 at 1:51 AM Harald Dunkel wrote:
> Package: podman
> Version: 2.0.6+dfsg1-1
>
> Unprivileged podman dies with some gibberish instead of a readable
> error message:
>
> % podman run -it debian /bin/bash
> Trying to pull quay.io/debian...
Source: kubernetes
Version: 1.18.6-1
Severity: wishlist
X-Debbugs-Cc: siret...@gmail.com
I'm looking at packaging github.com/cri-o/cri-o, and noticed that it vendors
kubernetes sources:
- https://github.com/cri-o/cri-o/tree/master/vendor/k8s.io
Additionally, I note that the 'libpod' package
Control: tag -1 pending
Hello,
Bug #968207 in libpod reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
On 8/3/20 9:29 AM, Martin Pitt wrote:
> Dmitry, Reinhard, I'd be very happy to team-maintain this if you are
> interested. I don't like single-maintainer packages :) I can take the primary
> responsibility of keeping the code alive with both upstream code changes and
> changes in Debian, and
On 8/3/20 9:29 AM, Martin Pitt wrote:
> Dmitry, Reinhard, I'd be very happy to team-maintain this if you are
> interested. I don't like single-maintainer packages :) I can take the primary
> responsibility of keeping the code alive with both upstream code changes and
> changes in Debian, and
Thanks!
Will incorporate in the next upload.
Thanks!
Will incorporate in the next upload.
On Mon, Aug 3, 2020 at 8:30 AM Shengjing Zhu wrote:
> If I read the comments in upstream issue correctly, it will be solved in 2
> months (they said 6 months later at April). What's the urgent thing we need
> to address in this two months?
>
I realized that podman 2.0 requires this newer
On Mon, Aug 3, 2020 at 8:30 AM Shengjing Zhu wrote:
> If I read the comments in upstream issue correctly, it will be solved in 2
> months (they said 6 months later at April). What's the urgent thing we need
> to address in this two months?
>
I realized that podman 2.0 requires this newer
Hi,
I've uploaded 2.0.18 that I slated for experimental to unstable after some
light testing with the 2.0.4 common package, and it seems to work fine.
Thanks for the ping, Martin!
--
regards,
Reinhard
>From: Shengjing Zhu
>To: Debian Bug Tracking System
>Subject: Not ready for using
>Date: Fri, 29 May 2020 23:36:43 +0800
>
> Package: golang-google-protobuf
> Severity: serious
>
> Though it has been packaged, it's not ready for using.
>
> The current version will generate
>From: Shengjing Zhu
>To: Debian Bug Tracking System
>Subject: Not ready for using
>Date: Fri, 29 May 2020 23:36:43 +0800
>
> Package: golang-google-protobuf
> Severity: serious
>
> Though it has been packaged, it's not ready for using.
>
> The current version will generate
I have good news for you, podman 2.0.4 got out last Friday, and I've
uploaded it to unstable earlier today. Let me know how this version works
with your CI.
Best,
-rt
On Fri, Jul 31, 2020 at 7:01 AM Martin Pitt wrote:
> Hallo Reinhard,
>
> Reinhard Tartler [2020-07-31 6:42 -0400]:
Control: severity -1 important
Hi Martin,
On Wed, Jul 29, 2020 at 8:42 AM Martin Pitt wrote:
> Package: podman
> Version: 2.0.3+dfsg1-1
> Severity: serious
> Tags: upsteam fixed-upstream
>
> Version 2.0.3 breaks the REST API really hard, which breaks cockpit-podman
> and
> any other API user.
Control: severity -1 important
Hi Martin,
On Wed, Jul 29, 2020 at 8:42 AM Martin Pitt wrote:
> Package: podman
> Version: 2.0.3+dfsg1-1
> Severity: serious
> Tags: upsteam fixed-upstream
>
> Version 2.0.3 breaks the REST API really hard, which breaks cockpit-podman
> and
> any other API user.
I think I've implemented this feature here:
https://salsa.debian.org/debian/devscripts/-/merge_requests/189
AFAIUI it needs someone to approve and merge it.
-rt
On Wed, Jul 22, 2020 at 12:15 AM Olek Wojnar wrote:
> Hi mentors,
>
> I'm not the best with Perl and although I've looked through
On Tue, Jul 21, 2020 at 10:36 PM Reinhard Tartler
wrote:
> My attempt at merging the docker.io package can be found in my ppa here:
> https://launchpad.net/~siretart/+archive/ubuntu/podman/+packages
>
> it at least builds on my laptop in a clean groovy chroot.
>
> Let me k
nt changes?
On Tue, Jul 21, 2020 at 7:29 AM Reinhard Tartler wrote:
> Hi Ubuntu Server folks,
>
> I've been working quite a bit to get podman 2.0 (cf. https://podman.io/)
> and its friends buildah and skopeo into debian/unstable, and succeeded
> with that task yesterday (yay). Now, I ne
Hi Michael,
On Tue, Jun 23, 2020 at 5:55 PM Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
> continuity no longer builds the continuity binary package so I filed a bug
> to get that removed.
>
The continuity package in debian continues to build the binary package
Hi Michael,
On Tue, Jun 23, 2020 at 5:55 PM Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
> continuity no longer builds the continuity binary package so I filed a bug
> to get that removed.
>
The continuity package in debian continues to build the binary package
onents in golang dev package,
mirroring Debian to address libpod FTBFS
-- Reinhard Tartler Sat, 30 May 2020 11:56:59 -0400
docker.io (19.03.8-0ubuntu3) groovy; urgency=medium
* Provide the rootless component in golang dev package, mirroring Debian
(addresses nomad FTBFS).
-- Logan Rose
Didier, what's the best way to contact them? Can you subscribe people
that would be able to advise / give guidance how to best resolve the
FTBFS bugs mentioned above?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think this is also affecting many other package builds, such as
https://launchpad.net/ubuntu/+source/golang-github-containers-
storage/1.20.2-3/+build/19612159
Didier, Roche, how do you feel about adding those dependencies to the
ubuntu package?
** Changed in: docker.io (Ubuntu)
Status:
Control: reassign -1 libvdpau1
Control: severity normal
Hi,
I can't reproduce this on my intel-based laptop, running intel drivers in a
wayland session.
It seems like a nvidia (vdpau?) specific issue to me. Reassigning to libvdpau.
Best,
-rt
Control: reassign -1 libvdpau1
Control: severity normal
Hi,
I can't reproduce this on my intel-based laptop, running intel drivers in a
wayland session.
It seems like a nvidia (vdpau?) specific issue to me. Reassigning to libvdpau.
Best,
-rt
Control: tag -1 pending
Hello,
Bug #950816 in mpv reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: golang-github-containerd-go-cni
Severity: normal
Version: 0.0~git20190904.d20b7ee-1
When trying to rebuild golang-github-containerd-go-cni version
0.0~git20190904.d20b7ee-1 with golang-github-appc-cni_0.8.0-1 from
experimental:
dh_auto_test -O--builddirectory=_build
Package: golang-github-containerd-go-cni
Severity: normal
Version: 0.0~git20190904.d20b7ee-1
When trying to rebuild golang-github-containerd-go-cni version
0.0~git20190904.d20b7ee-1 with golang-github-appc-cni_0.8.0-1 from
experimental:
dh_auto_test -O--builddirectory=_build
> I don't understand, I have that in the control file:
>
> Maintainer: Debian Go Packaging Team
> Uploaders:
>Arnaud Rebillout ,
>
> Is it correct?
>
>
>- > debian/copyright is (license-reconcile) clean, thanks!
>- > debian/{rules,control}
> When I run "podman exec ..." on a running container, it always fails:
> $ sudo podman exec 8791af6116b9 ps
> Error: AppArmor not initialized correctly: OCI runtime error
> (This is a multi-process container running systemd; I don't know if
> that makes a difference to the behaviour.)
> I
I'd love to help, but I'm stuck at this step:
siretart@x1:/srv/scratch/packages/go-team-sponsorship/pup$ dgit --gbp
sbuild --run-lintian --run-piuparts
Format `3.0 (quilt)', need to check/update patch stack
gzip: warning: GZIP environment variable is deprecated; use an alias or
script
dgit: split
On 7/16/20 10:06 AM, Reinhard Tartler wrote:
> In order to get podman 2.0 to build, I had to backport some changes to
> the golang-github-docker-docker-dev package.
Actually, never mind, I managed to patch podman 2.0 to not require these
backports:
https://salsa.debian.org/debian/libpod/
Source: docker.io
Severity: normal
Control: block 964378 by -1
Hi,
In order to get podman 2.0 to build, I had to backport some changes to
the golang-github-docker-docker-dev package. Unfortunately they are not
included in any upstream release at time of writing. Please find
backported patches
On 7/16/20 7:45 AM, Shengjing Zhu wrote:
> On Thu, Jul 16, 2020 at 6:39 PM Reinhard Tartler wrote:
>>
>> Package: golang-blackfriday
>> Severity: normal
>> Control: block 964378 by -1
>>
>> This upgrade is a requirement of the new go-md2man 2.0 upstream v
Package: golang-github-shenwei356-bwt
Severity: serious
Justification: FTBFS
While trying to rebuild this package, it appears it build depends on the
package golang-github-shenwei356-bpool-dev
Find the buildlog attached to this email.
golang-github-shenwei356-bwt_0.0~git20200418.ae79c98-2
Package: golang-github-shenwei356-bwt
Severity: serious
Justification: FTBFS
While trying to rebuild this package, it appears it build depends on the
package golang-github-shenwei356-bpool-dev
Find the buildlog attached to this email.
golang-github-shenwei356-bwt_0.0~git20200418.ae79c98-2
Package: golang-blackfriday
Severity: normal
Control: block 964378 by -1
This upgrade is a requirement of the new go-md2man 2.0 upstream version,
which required by github.com/spf13/cobra, which in turns is required
by libpod 2.0, and thus blocks #964378.
I've actually already updated the package
Package: golang-blackfriday
Severity: normal
Control: block 964378 by -1
This upgrade is a requirement of the new go-md2man 2.0 upstream version,
which required by github.com/spf13/cobra, which in turns is required
by libpod 2.0, and thus blocks #964378.
I've actually already updated the package
Package: ratt
Version: 0.0~git20180127.c44413c-2+b10
Severity: wishlist
While working on a complex package change, I wish I was able to
"pass-through" additional options to sbuild when working with ratt.
In particular, I wish I could invoke 'ratt' in a way that would allow me
to use the options
Package: ratt
Version: 0.0~git20180127.c44413c-2+b10
Severity: wishlist
While working on a complex package change, I wish I was able to
"pass-through" additional options to sbuild when working with ratt.
In particular, I wish I could invoke 'ratt' in a way that would allow me
to use the options
Package: wnpp
Owner: Reinhard Tartler
Severity: wishlist
* Package name: golang-blackfriday-v2
Version : 2.0
Upstream Author : Russ Ross
* URL or Web page : https://github.com/russross/blackfriday
* License : BSD-2-clause
Description : Blackfriday: a markdown
Package: wnpp
Owner: Reinhard Tartler
Severity: wishlist
* Package name: golang-blackfriday-v2
Version : 2.0
Upstream Author : Russ Ross
* URL or Web page : https://github.com/russross/blackfriday
* License : BSD-2-clause
Description : Blackfriday: a markdown
Package: wnpp
Owner: Reinhard Tartler
Severity: wishlist
* Package name: golang-blackfriday-v2
Version : 2.0
Upstream Author : Russ Ross
* URL or Web page : https://github.com/russross/blackfriday
* License : BSD-2-clause
Description : Blackfriday: a markdown
Package: wnpp
Owner: Reinhard Tartler
Severity: wishlist
* Package name: golang-blackfriday-v2
Version : 2.0
Upstream Author : Russ Ross
* URL or Web page : https://github.com/russross/blackfriday
* License : BSD-2-clause
Description : Blackfriday: a markdown
currently in experimental need coordinated
uploads
because of incompatible changes introduced
in golang-github-vbauerster-mpb_5.0.3-1. But for now,
I think we should be good to update libpod at least in experimental.
Best,
-rt
On Mon, Jul 6, 2020 at 7:36 AM Reinhard Tartler wrote:
> Source: lib
Package: snapd
Version: 2.44.1-2
Severity: serious
While trying to rebuild the package, I noticed that one of the tests in
the testsuite fails:
=== RUN Test
--
FAIL: squashfs_test.go:130:
Package: snapd
Version: 2.44.1-2
Severity: serious
While trying to rebuild the package, I noticed that one of the tests in
the testsuite fails:
=== RUN Test
--
FAIL: squashfs_test.go:130:
Package: conmon
Version: 2.0.9-1
Severity: normal
Hi,
In the context of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964378, I took the
liberty of updating conmon to version 2.0.18 in salsa. The branch can be
found at:
https://salsa.debian.org/podman-team/conmon/-/tree/experimental
I
Source: singularity-container
Severity: normal
I'm pondering to upload the version of package
golang-github-vbauerster-mpb-dev currently in experimental to unstable
and did a test rebuild of all dependent packages.
Turns out that singularity-container fails with this error:
#
Cool, thanks! uploaded
(sorry for the delay)
On Sun, Jun 7, 2020 at 10:59 PM Shengjing Zhu wrote:
> On Mon, Jun 8, 2020 at 5:06 AM Reinhard Tartler
> wrote:
> >
> > Hi,
> >
> > I wonder about the timing to upload golang-github-opencontainers-selinux
> to uns
Control: tag -1 pending
Hello,
Bug #964045 in golang-github-shirou-gopsutil reported by you has been fixed in
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #964045 in golang-github-shirou-gopsutil reported by you has been fixed in
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Source: libpod
Severity: wishlist
Podman 2.0 is going to be supported in RHEL 8.3 long term and is thus a
great candidate for inclusion into Debian bullseye. Let's try to get it
packaged for debian.
I've looked at https://github.com/containers/libpod/blob/v2.0/go.mod to
understand what packages
Control: tag -1 pending
Hello,
Bug #963346 in golang-github-openshift-api reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi,
I wonder about the timing to upload golang-github-opencontainers-selinux to
unstable. The newer upstream version is needed for some upcoming other
packages.
Any objections?
--
regards,
Reinhard
Package: golang-github-klauspost-pgzip
Severity: wishlist
Needed by container/storage v1.16 branch
thanks
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.6.0-1-amd64 (SMP w/4
Package: golang-github-klauspost-pgzip
Severity: wishlist
Needed by container/storage v1.16 branch
thanks
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.6.0-1-amd64 (SMP w/4
Package: golang-github-klauspost-compress
Severity: wishlist
This is needed by containers/storage v1.16.
Thanks!
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.6.0-1-amd64
As another datapoint, the docker.io package serves as a build dependency
to many container-related packages in the archive. Dropping the package
would in the short-term mean breaking all packages that use this code
(nomad, buildah, podman, to name a few). In the long term, it might
cause increased
Control: tag -1 pending
Hello,
Bug #961421 in libpod reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
As annoying as it is, but unless anyone objects or has a better idea, I'm
going to disable that particular test for the time being in ubuntu.
That would be a very unfortunate delta to the debian package :-(
-rt
On Tue, May 26, 2020 at 6:43 AM Reinhard Tartler wrote:
> Hi,
>
> Long ti
Hi,
Long time no see :-)
I've been working on getting buildah, skopeo, podman into Debian, and
finally those tools are available. Now I wanted to dust of my Ubuntu
packaging skills and bring them over to ubuntu, and am encountering issues.
I figure most of them are due to changes I wasn't able
601 - 700 of 13013 matches
Mail list logo
