Le dim. 7 déc. 2025 à 12:45, Thomas Goirand <[email protected]> a écrit :
> On 12/6/25 10:35 PM, Jérémy Lal wrote: > > Package: python3-autobahn > > Version: 24.4.2+dfsg1-3 > > Severity: important > > Hi Jérémy, > > Thanks for taking the time to open this bug. > > > The very odd, and kind of kinky, git layout of python3-autobahn's salsa > repository > > makes it very hard to contribute. > > The layout isn't particularly odd, it's just a single branch with the > debian folder merged into upstream branch, patches un-applied. This is > more and more common in Debian. If I'm not mistaking, this is the layout > that dgit authors (ie: Ian Jackson) is using, and tag2upload last > summer, only supported that layout. > > > Please, per policy 4.14, document in debian/README.source what the joke > is about: > > Policy 4.14 only tells about source packages, at no point it involves > using git. Not mentioning how a package is maintain under Git doesn't > make a package not policy compliant. Remember Git packaging isn't > mandatory, even though I personally think it should be. Hopefully, the > Debian project is converging toward it. > > Anyways, you made me write this wiki entry, which was really overdue: > https://wiki.debian.org/OpenStack/git-tag-based-workflow > > Let me know if you think it needs improvements. > > Now, there's 500+ packages in the OpenStack team using that workflow and > git layout, more within the Home Assistant team, and more from other > DDs. It is my view that it isn't reasonable to maintain a > debian/README.source file on each of these packages. > > > Please, per policy 4.14, document in debian/README.source what the > > joke is about: > > The branch names are against the OpenStack upstream branches, as > autobahn is maintained so that OpenStack works, following the > requirements maintained upstream. If you do not know about the upstream > OpenStack branch names, they are described here: > > https://wiki.debian.org/OpenStack#OpenStack_releases_VS_Debian_releases > > However, you do not need to know about them, the default branch is > always the one matching Debian unstable, and that's where one should > contribute. > > It's now time to close this joke... :) > Thank you for the explanation. My problem was with those branch names, not the somewhat more and more common git layout. Please accept my excuses for the too strong reaction I had, I should have asked with a nicer tone. > Cheers, > > Thomas Goirand (zigo) > >
