On Tue, Feb 18, 2025 at 01:44:35PM +0100, Nicolas Peugnet wrote: > On 16/02/2025 11:17, Nicolas Peugnet wrote: > > On Sun, 19 Jan 2025 23:57:11 +0000 Colin Watson <cjwat...@debian.org> > > wrote: > > > I uploaded docker-compose 1.29.2-6.4 earlier today to fix that. (I > > > can't help with packaging 2.x, though.) > > > > I am currently working on packaging the v2 of docker-compose. As it is > > now a Go package, I will be maintaining it withing Debian's Go team. > > > > It is not fully ready yet. I will see how to convert this bug into an ITP. > > So, here is my current packaging work: > https://salsa.debian.org/go-team/packages/docker-compose > > It still need one dependency not uploaded yet and one that is in NEW. But it > compiles fine and seems to work OK. It still need a lot of polishing though > and I plan to upload it first to experimental. > > Colin: do you have some advice on how to properly package docker-compose?
No, sorry. I don't know Go particularly well, and I hardly ever use Docker. > Also should I copy the content of the changelog from the v1 package? IMO yes. > Maybe it would be good to have an entry in the NEWS.Debian file? NEWS.Debian entries should be user-focused. So if you write one (I don't know whether it makes sense), it should be about things like incompatible changes that a user of the package would need to know about, as opposed to internal details such as which language the package is now written in. Cheers, -- Colin Watson (he/him) [cjwat...@debian.org]
