[pkg-go] Bug#1006426: marked as done (unable to start container: could not find "rootlessport" with podman 4.0.1)

[Debian Bug Tracking System]

Your message dated Fri, 25 Feb 2022 23:03:39 +0000
with message-id <E1nNjch-0006av-Lx at fasolo.debian.org>
and subject line Bug#1006426: fixed in libpod 4.0.1+ds1-2
has caused the Debian Bug report #1006426,
regarding unable to start container: could not find "rootlessport" with podman 4.0.1
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 at bugs.debian.org
immediately.)


-- 
1006426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006426
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Alby Doyle <adoyle.h at gmail.com>
Subject: unable to start container: could not find "rootlessport" with podman 4.0.1
Date: Fri, 25 Feb 2022 18:17:33 +0800
Size: 4924
URL: <http://alioth-lists.debian.net/pipermail/pkg-go-maintainers/attachments/20220225/ba8c5a81/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Debian FTP Masters <ftpmaster at ftp-master.debian.org>
Subject: Bug#1006426: fixed in libpod 4.0.1+ds1-2
Date: Fri, 25 Feb 2022 23:03:39 +0000
Size: 4972
URL: <http://alioth-lists.debian.net/pipermail/pkg-go-maintainers/attachments/20220225/ba8c5a81/attachment-0001.eml>