On 18/02/2025 14:45, Colin Watson wrote:
On Tue, Feb 18, 2025 at 01:44:35PM +0100, Nicolas Peugnet wrote:
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.
Ok, I just did it.
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.
Thank you for your quick answer and your tips. Sorry, I noticed only
after sending my email that you are not a maintainer of docker-compose.
One last question, the Debian developer reference states that:
It is not OK to simply take over a package without assent of the current
maintainer — that would be package hijacking. You can, of course, contact the
current maintainer and ask them for permission to take over the package.
So I am adding the persons listed as uploaders, to make sure they read
this email.
As the v2 of docker-compose has been rewritten in Go, I started
packaging it from scratch and I indent to maintain it within Debian's Go
team. Do you agree to let me and the Debian Go team take over the package?
Is there anything else I would need to do in order to not do a "package
hijack"?
--
Nicolas Peugnet
