Antoine Beaupré: > On 2019-04-17 01:31:49, Chris Knadle wrote: > > [...] > > Wow, that must have all been a lot of work, thanks! :)
You're welcome. >> I doubt this package is going to get accepted by the Release Team, because >> upload after the freeze is meant for only small targeted fixes. I'll make >> the >> request to see if it's possible, but I expect that the chances of this being >> accepted to be very low. > > I agree. In fact, I think it might even be better to *remove* mumble > from buster at this point, and maintain it through backports. We > *definitely* do not want a RC in buster that we'll have to maintain for > years... Much easier to do through backports! Mmm... no, I don't agree there. Backports are a separate repository that users have to find and specifically configure to use, and -- more importantly -- the only backports that can exist are for packages that have been uploaded to Debian and transitioned to Testing. i.e. the package *must* exist in Debian Testing already for an upload to be allowed to Backports. The Debian backport for mumble is done by another maintainer, not me, and backports are also messy because bugs to backports should go to the backports mailing list, *not* the BTS. It's possible to set the package up to cause that to happen by setting a Bugs: line with a 'mailto:<email>', but not all of the bug reporting software comply with that. (reportbug does, reportbug-ng does not, at least last I checked.) There's always a running 'diff' between the package in Testing and the backport, and the 'diff' slowly gets bigger as there are changes in libraries, newer versions of debhelper, and so on. And in the case of Mumble the backport is in a separate offline Git repository away from the one used for the main package. Backports may be easier for (some) users, but they're harder for maintainers -- or at least that's my experience with them so far. > I can change the severity of this bug, if you agree, which should > eventually kick the package out of testing... Heh... :-p Please don't. I understand the sentiment but it makes a bigger mess rather than easing one. > I'm sorry, but I think it's just "partie remise" as we say in french: > we'll get it in bullseye! And this time it will be awesome. ;) Dude I did my best to try to get upstream to release a viable snapshot of some kind before the soft freeze -- I mean really, I pleaded with them -- but it didn't happen. It didn't make sense to release the old Mumble 1.2 to Buster, the upstream snapshots for Mumble 1.3 that were available were broken, upstream asked me to release directly from Git instead, and the upstream repo uses submodules such that making a tarball required creating a script to do it which breaks the debian/watch stuff. I did the best that could be done, and there's no opportunity to re-do it. *shrug* C'est la vie!! ;-) -- Chris -- Chris Knadle chris.kna...@coredump.us
