[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1076109: marked as done (docker.io: upload docker 26.1, containerd 7, et. al., to sid)



Your message dated Thu, 3 Apr 2025 17:17:17 +0200
with message-id <ad51b76a-50a8-4ad9-86ad-a97e066e8417@debian.org>
and subject line Re: Coordingating/planning various golang transitions
has caused the Debian Bug report #1076109,
regarding docker.io: upload docker 26.1, containerd 7, et. al., to sid
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1076109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076109
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---

Package: docker.io

Version: 20.10.25+dfsg1-3

Severity: normal

 

Hello Debian Team,

 

As docker.io package is updated version 26.1.4+dfsg1-5 in experimental.

 

We feel like it’s a bigger task as updating docker.io requires updating its dependency packages as well such as containerd, runc, etc.

 

We tried installing docker.io package from experimental in Debian Trixie and Bookworm by adding experimental sources to /etc/apt/sources.list.

 

Did some basic tests of Docker. The package seems to be working fine.

 

Please let me know what process should be followed, along with the testing procedures and other to be followed to bring it to sid/Trixie and bookworm-backports, so that we will also try help in the process and contribute as well.

 

 

Thanks & Regards,

Badrikesh


--- End Message ---
--- Begin Message ---
Hi,

On Thu, 1 Aug 2024 12:45:29 +0800 Shengjing Zhu <zhsj@debian.org> wrote:
On Thu, Aug 1, 2024 at 12:43 PM Mathias Gibbens <gibmat@debian.org> wrote:
>   * For some reason golang-google-genproto hasn't yet migrated into
> testing. I pinged the release team this morning to see if they can help
> figure out why.

You can check https://release.debian.org/britney/update_output.txt.
I think some Breaks in that package make it needs to be migrated with
other packages stuck in proposed migration.

I think this was all handled some time ago.

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply to: