Your message dated Tue, 29 Jun 2021 11:18:26 +0000
with message-id <e1lybl4-0004fo...@fasolo.debian.org>
and subject line Bug#990333: fixed in libpod 3.2.2+ds1-1
has caused the Debian Bug report #990333,
regarding Fwd: [containers/podman] Release v3.2.2 - v3.2.2
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 ow...@bugs.debian.org
immediately.)
--
990333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpod
Please update package in experimental
---------- Forwarded message ---------
From: Matthew Heon <notificati...@github.com>
Date: Fri, Jun 25, 2021, 17:04
Subject: [containers/podman] Release v3.2.2 - v3.2.2
To: containers/podman <pod...@noreply.github.com>
Cc: Subscribed <subscri...@noreply.github.com>
v3.2.2 <https://github.com/containers/podman/releases/tag/v3.2.2>
Repository: containers/podman <https://github.com/containers/podman> · Tag:
v3.2.2 <https://github.com/containers/podman/tree/v3.2.2> · Commit: d577c44
<https://github.com/containers/podman/commit/d577c44e359f9f8284b38cf984f939b3020badc3>
· Released by: mheon <https://github.com/mheon>
Changes
- Podman's handling of the Architecture field of images has been
relaxed. Since 3.2.0, Podman required that the architecture of the image
match the architecture of the system to run containers based on an image,
but images often incorrectly report architecture, causing Podman to reject
valid images (#10648 <https://github.com/containers/podman/issues/10648>
and #10682 <https://github.com/containers/podman/issues/10682>).
- Podman no longer uses inotify to monitor for changes to CNI
configurations. This removes potential issues where Podman cannot be run
because a user has exhausted their available inotify sessions (#10686
<https://github.com/containers/podman/issues/10686>).
Bugfixes
- Fixed a bug where the podman cp would, when given a directory as its
source and a target that existed and was a file, copy the contents of the
directory into the parent directory of the file; this now results in an
error.
- Fixed a bug where the podman logs command would, when following a
running container's logs, not include the last line of output from the
container when it exited when the k8s-file driver was in use (#10675
<https://github.com/containers/podman/issues/10675>).
- Fixed a bug where Podman would fail to run containers if
systemd-resolved was incorrectly detected as the system's DNS server (
#10733 <https://github.com/containers/podman/issues/10733>).
- Fixed a bug where the podman exec -t command would only resize the
exec session's TTY after the session started, leading to a race condition
where the terminal would initially not have a size set (#10560
<https://github.com/containers/podman/issues/10560>).
- Fixed a bug where Podman containers using the slirp4netns network mode
would add an incorrect entry to /etc/hosts pointing the container's
hostname to the wrong IP address.
- Fixed a bug where Podman would create volumes specified by images with
incorrect permissions (#10188
<https://github.com/containers/podman/issues/10188> and #10606
<https://github.com/containers/podman/issues/10606>).
- Fixed a bug where Podman would not respect the uid and gid
options to podman
volume create -o (#10620
<https://github.com/containers/podman/issues/10620>).
- Fixed a bug where the podman run command could panic when parsing the
system's cgroup configuration (#10666
<https://github.com/containers/podman/issues/10666>).
- Fixed a bug where the remote Podman client's podman build -f - ...
command did not read a Containerfile from STDIN (#10621
<https://github.com/containers/podman/issues/10621>).
- Fixed a bug where the podman container restore --import command would
fail to restore checkpoints created from privileged containers (#10615
<https://github.com/containers/podman/issues/10615>).
- Fixed a bug where Podman was not respecting the TMPDIR environment
variable when pulling images (#10698
<https://github.com/containers/podman/issues/10698>).
- Fixed a bug where a number of Podman commands did not properly support
using Go templates as an argument to the --format option.
API
- Fixed a bug where the Compat Inspect endpoint for Containers did not
include information on container healthchecks (#10457
<https://github.com/containers/podman/issues/10457>).
- Fixed a bug where the Libpod and Compat Build endpoints for Images did
not properly handle the devices query parameter (#10614
<https://github.com/containers/podman/issues/10614>).
Misc
- Fixed a bug where the Makefile's make podman-remote-static target to
build a statically-linked podman-remote binary was instead producing
dynamic binaries (#10656
<https://github.com/containers/podman/issues/10656>).
- Updated the containers/common library to v0.38.11
—
This release has 2 assets:
- Source code (zip)
- Source code (tar.gz)
Visit the release page
<https://github.com/containers/podman/releases/tag/v3.2.2> to download them.
—
You are receiving this because you are watching this repository.
View it on GitHub <https://github.com/containers/podman/releases/tag/v3.2.2>
or unsubscribe
<https://github.com/containers/podman/unsubscribe_via_email/AAOKTJGE37Z22HE5ORNXP6TTUTVMRANCNFSM4BUBNXIQ>
from all notifications for this repository.
--- End Message ---
--- Begin Message ---
Source: libpod
Source-Version: 3.2.2+ds1-1
Done: Reinhard Tartler <siret...@tauware.de>
We believe that the bug you reported is fixed in the latest version of
libpod, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 990...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Reinhard Tartler <siret...@tauware.de> (supplier of updated libpod package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 28 Jun 2021 08:15:51 -0400
Source: libpod
Architecture: source
Version: 3.2.2+ds1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Go Packaging Team
<pkg-go-maintain...@lists.alioth.debian.org>
Changed-By: Reinhard Tartler <siret...@tauware.de>
Closes: 990333
Changes:
libpod (3.2.2+ds1-1) experimental; urgency=medium
.
* New upstream relases, Closes: #990333
* Bump dependency on golang-github-containers-common
Checksums-Sha1:
729dc6c96df3e88eb3b2a35dc728e8373b9beafb 5132 libpod_3.2.2+ds1-1.dsc
76c52b48e6fc8dccebdebf075750963c530992b0 1970296 libpod_3.2.2+ds1.orig.tar.xz
48c1050aa66075d2254190ef16b2405f644ebede 14888 libpod_3.2.2+ds1-1.debian.tar.xz
Checksums-Sha256:
606075576eeddbe1e4a91183fb2dfe1ad330b01b5b207764bfc041569c096d32 5132
libpod_3.2.2+ds1-1.dsc
edc76d15455186d49f10f50cea54c1299b2bdc6d9bfb8ba5d1f10d5a9142e7c8 1970296
libpod_3.2.2+ds1.orig.tar.xz
ce0c62daacae37f245797e64521077affe6f7584c3031a8290718a7a8fb2b861 14888
libpod_3.2.2+ds1-1.debian.tar.xz
Files:
a6a287bf5380b0279320771045e16ebd 5132 admin optional libpod_3.2.2+ds1-1.dsc
64faac6a07c6b59c2c87616614022c93 1970296 admin optional
libpod_3.2.2+ds1.orig.tar.xz
bd0aeeda0b536fe0542eb0b47838c4ce 14888 admin optional
libpod_3.2.2+ds1-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmDa/dsUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJsvTzRAAgO6A+lW1Ut3iEAXalRyoAOskj38I
dIfgnplqU0jt2AO0lBqyZvlLCIIKkXjsLjDmKSrsTo1FAvAQJFXRO3uvQMQ7XXti
O5c2yqTDgwAg0FuZ3Q1+jUJepEzA9vR75TNWaCwAemd5cBX0fIL0db8Nq7vwYm5w
dBniwrE8u835dGhwlL/avFY0V6R/D/AVfjddtggUlBLOtDqvWM3Mykm08VIv3B8H
0ip0TDjsRBEv5U/3XCvt10Um7874G+NEo1lGca1XgWejY2S+Usy9eaosBiMj+/0p
jFLTfxSUfPMgBx5/lje3HYaz+C67Ycz1JFguPBFF3oP8ucK3IWTklE1mNhoQpAwk
i+ESXiubI/qwj1dHK6DemaVT4DudSl+M5dm7dVcJe5ApBgB5xIvN71S/oozwXSE6
lK7Iw89CaqeIsMlPyu1cLzoFt33I7+C20EzAcOT8X+ntEm7vhoRiwVIr1uy4izzA
ikBh3YCrugghFPmxsOfgAISxi5X3yapizsgk4KqzVC1wFgZVg5vM6OEVNAmqhNW8
3+wfUCfoyTsMxIDvCfscIhRtpx4o6skL/b1Idk5Zr5SdxENHm+24Y47YMPu9zylF
LNVD1Tj+wdR8iKR+MXaldnpSzrGLGiaPaPc6FJa3OalM2Fy00if/ss6zbpqJjRRr
036+SHPx9Q+rLVc=
=4ubU
-----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
