On Wed, Apr 23, 2025 at 09:04:48PM +0100, Gabriele wrote:
Thanks for reaching out. The package sources are available from the devel branch of the upstream repository (https://github.com/P403n1x87/austin/tree/debian). It would be great if one could specify a branch (I haven't looked into Debian packaging in a while, so I don't know if that's now available), since all sources are there.
OK. It's possible to add "-b debian" to the end of Vcs-Git; but ideally we'd move it to salsa.debian.org anyway, as in the long term it usually works out to be somewhat inconvenient to have the packaging in the same repository as upstream. (More often than not, package maintainers aren't the same people as upstream developers, at least not on a permanent basis; they're also often dealing with hundreds of packages from the distribution's end of things and it tends to be easier if they're all in a distribution-controlled repository. Salsa also has CI jobs that are optimized for doing a bunch of different quality checks on packages.)
I'd be very happy if someone was willing to take over the maintenance of the package, as keeping up-to-date with that has been a bit of a burden that eventually I had to give up :(.
Thanks for what you've done so far! If you aren't maintaining the packaging any more, would you mind if I imported the history of that branch into a repository under https://salsa.debian.org/python-team/packages/ and set the Debian Python Team as Maintainer? Of course I can give you commit access if you have a salsa account and tell me its username - I'm not trying to take it away from you, just to make sure that we can keep it up to date in Debian cooperatively.
All the best, -- Colin Watson (he/him) [cjwat...@debian.org]
