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

Accepted docker-compose 2.26.1-3 (source) into unstable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 26 Feb 2025 07:21:23 -0500
Source: docker-compose
Architecture: source
Version: 2.26.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Changed-By: Reinhard Tartler <siretart@tauware.de>
Closes: 1040417 1098732
Changes:
 docker-compose (2.26.1-3) unstable; urgency=medium
 .
   * Upload to unstable
 .
 docker-compose (2.26.1-2) experimental; urgency=medium
 .
   [ Nicolas Peugnet ]
   * Fix compose-spec v2.1.3 patch to avoid nil pointer dereference
 .
 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
 .
 docker-compose (1.29.2-8) experimental; urgency=medium
 .
   * Merge changes from NMUs in unstable
 .
 docker-compose (1.29.2-7) experimental; urgency=medium
 .
   * Drop docker-compose package. Since docker-compose will soon be
     replaced by the Go reimplementation in docker-compose 2.x,
     this package will only ship the Python library from now on.
Checksums-Sha1:
 93d04b085a86b61913044fd1f83ab335f6800604 3802 docker-compose_2.26.1-3.dsc
 3b3d9c0886c936e2a304baa554a3f39ccc23ec92 9548 docker-compose_2.26.1-3.debian.tar.xz
Checksums-Sha256:
 0cb248470913da58d21dfdc8bfe4ab0652974e5d20cfe00e366efe424be41af9 3802 docker-compose_2.26.1-3.dsc
 e79055e16785de0cc93a8015cff6c7e53a6b6f17ab8841f4172f01670b621112 9548 docker-compose_2.26.1-3.debian.tar.xz
Files:
 ef898eafc019688128d2cd1648cb2574 3802 golang optional docker-compose_2.26.1-3.dsc
 962e491cf34575dcbc3e4b59938021a0 9548 golang optional docker-compose_2.26.1-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAme/B48UHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJssjSxAAynw9Gd8ZuAko59JPWHlxIf6G1UUh
3T7sRXJLAtQV3FFncrj1LAFAlR8Q73yYTMOsc0iJZTLFrx03YPOsGpcL6KF1ATmz
EBWNSolGyxqfbJUrOABmyiTO1G7q+6DoPCcqh+87LIIzVa7VQ3rz8pwDBtZ+MHdm
bZErf5k03EF0iRV7HVQ7Sa4zvgzF+/NUF1ikOGopgTOzmpaekk9WuVHB5Qxxoivy
Fp8JYQhG0BUuFwbP0RxrIpyiDJ3m5bdx4qAF6jAI6xHwFp3/HpJLHAy6UFJDDYNE
d4yHpdwyZQmiIdER5vlLoVESczs5uKaUapVW39AalUGGPCf9bcntUs22euFfft9G
NoWZ278o+5TtZfeafsjKjDhf2pGhDQdvBhKZhEvqGQkrs0CU20TODK5D3vg2+KEz
eKvQT17eaAnL0vHJ+TnNv2/avIbmzf/yuNg+DYTHwBMLk9CWZ9grhMiJLGAeVkQo
KQsO4VcQvknWnXh+0DDfR4ccG1jjtjlevqShqaGbLyduigbA/Ai79I3w0IEVPxJ1
fcEUFwtH66dkuyEBbcj3QGkmUy4leCns0BmR5Nj5YtNOFMoC7+L7CHmvFYps/3zs
AnjoYzz9F7veUyhEGXsi5pKr+EWvP+TmJOMeuws+qAXp5hKQYzGLQIKovhklbcVc
QLvDFC/jPEyqIDo=
=UVB/
-----END PGP SIGNATURE-----

Attachment: pgpuTU2Hwce5V.pgp
Description: PGP signature


Reply to: