Your message dated Sun, 23 Feb 2025 15:37:15 +0000
with message-id <e1tme2d-00ewmx...@fasolo.debian.org>
and subject line Bug#1040417: fixed in docker-compose 2.26.1-1
has caused the Debian Bug report #1040417,
regarding docker-compose V1 is depreciated.
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.)
--
1040417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: docker-compose
Version: 1.29.2-3
As per https://www.docker.com/blog/new-docker-compose-v2-and-v1-deprecation/
Docker V1 is depreciated.
This is still in Sid:
https://tracker.debian.org/pkg/docker-compose
Also this issue is present:
Problems while searching for a new upstream version high
uscan had problems while searching for a new upstream version:
In debian/watch no matching files for watch line
https://github.com/docker/compose/tags .*/v?(1\S*)\.tar\.gz
Problem is v1 is no longer supported, so v2 should be compiled and used
instead as there is no support from docker-compose developers anymore, yet
latest version (Bookworm) of Debian still uses it.
Is this a problem?
Kind regards
Pete
--- End Message ---
--- Begin Message ---
Source: docker-compose
Source-Version: 2.26.1-1
Done: Reinhard Tartler <siret...@tauware.de>
We believe that the bug you reported is fixed in the latest version of
docker-compose, 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 1040...@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 docker-compose
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: Sun, 23 Feb 2025 09:56:17 -0500
Source: docker-compose
Architecture: source
Version: 2.26.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Go Packaging Team <team+pkg...@tracker.debian.org>
Changed-By: Reinhard Tartler <siret...@tauware.de>
Closes: 1040417 1098732
Changes:
docker-compose (2.26.1-1) experimental; urgency=medium
.
[ Nicolas Peugnet ]
* Upgrade to docker-compose v2 (Closes: #1040417, #1098732)
.
[ Reinhard Tartler ]
* Add myself to uploaders
Checksums-Sha1:
262381853bee21eed4bc77e5fb4ef46452145c0c 3802 docker-compose_2.26.1-1.dsc
865754e35434ed961958d1a9c24d6885e470bd7e 283860
docker-compose_2.26.1.orig.tar.xz
7f12a4628577950a3c3abe46a2a7932ccdf558f5 9472
docker-compose_2.26.1-1.debian.tar.xz
Checksums-Sha256:
a286a08387cfc6795f413988e29b1bd814ff5694c28c32fdf688da950451fefa 3802
docker-compose_2.26.1-1.dsc
9b2f3ec4ccced49125d8ae46e09d45d435623a4c58ba609b3ec160baeb400242 283860
docker-compose_2.26.1.orig.tar.xz
a805575267a0f3ad33f8fd0f9dcf26f93eddaf603521b4c3d1d788aeb8436856 9472
docker-compose_2.26.1-1.debian.tar.xz
Files:
00f44800a88651652dc13ddef5daeeef 3802 golang optional
docker-compose_2.26.1-1.dsc
e2e7a4cfeb7a6a3b88a3d8ec1e58476f 283860 golang optional
docker-compose_2.26.1.orig.tar.xz
c91b6098430257e72e9617488a8ca512 9472 golang optional
docker-compose_2.26.1-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAme7ObsUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJst/BRAAvccvEABH/WIe5xMmm7WVP553ys7N
ev5fjjTpOa22CKcIynUmz8mi0LWNpzyc9vulFDESERgpkaJE46kSGfp8/t/pVBhH
LmqXzvLI3JEEB0odbvd2aAK2/ZEz8LQv4MQBWYGsfxV05rOpE5pXHGJyrSpK5Epq
EAFb8a1Q98NQP0ylW02OXL8Y4IdNAnUXU3sjAmon0lrAQhjx2fYhzXOiGOIHAkPf
Vn8JLZ64Tqy9S/z8QDVpziBeMBO7aSVp0xxEiuEuAf8I2gacTW7FreCw05R1E5XM
MZPm/CpoNVXCaqdWEWs8qjKRCZ7N3Z7PgsqYSh96lKwNfXHzTdBH7rtxsGjbaXWr
Ibm3gl4zznM1jMvze+w9PHsO2oRPg7feOHldOjnV14A90ysCLU/0hXZGe3elO0+A
G1u2IET/55HKvpFuGa5L5dq21KEwOWWrdvSIFyFIufwKhr7bWDV8uG21e3CtLR1d
Gy00i3rB2X+nQm8kYdC9zQTTr6Y1loU2dufWY6WtP4xiwWEJMWUjioQwmlvtUHj8
EoSyw1EhehfDmDOSEEsJUwb5/FOiwEg7gAJtsq9p5sbjwSaGjdBozOdOCmV421An
5iXEDN1dUpR+McpkhP0h5te8FQDNFodrN3uJPWmCfxJlO1CFqcSueuwvZVo0/MhW
18GZCYpzQYLFHrI=
=dUUV
-----END PGP SIGNATURE-----
pgp0R2gsxbYO3.pgp
Description: PGP signature
--- End Message ---
