Diederik de Haas:
Hi Chris,
On Wednesday, 7 December 2022 10:13:00 CET Chris Knadle wrote:
So I'd suggest skipping 1.4 altogether and go straight for 1.5.
You _could_ now release a development snapshot (to Experimental?),
especially if the package needs to go through NEW and then the update to
the 1.5 released version should be (relatively) small (I'd guess).
I want to release Mumble 1.5 when possible ... but this isn't about
releasing to Unstable vs Experimental --
The reason I mentioned Experimental is that you can use that to get things
through NEW if needed, while not blocking potential updates for Unstable/
Testing/Bookworm. Mostly because one doesn't know how long that'll take.
I'm aware of Experimental, I believe I've uploaded to Experimental before. It's
a worthwhile thought for aa release that may not be fitting (yet) for Unstable,
which the current Mumble 1.5 would theoretically fit that because it's not
released yet. Keep in mind -- any release to Experimental cannot be uploaded to
Unstable with the same version #. i.e. anything in Experimental is strictly a
work-in-progress. I believe once a package is released to Unstable with a higher
version # than that of Experimental, the Experimental version is removed.
it's about the fact that there
isn't a 1.5 source tarball to work from to do any release at all.
With snapshot I did mean using 'some' upstream git commit, like current HEAD.
I'll try to find an example of that as I *know* they exist.
Yes, I know. Many upstream packages that are in Git can be exported directly to
a tarball and then built as a Debian package. Mumble is NOT one of those.
Mumble's Git repo has submodules that are considered separate such that "git
archive" won't export the submodules, and the code won't build without them.
Also the submodules contain files that have restrictive copyright, making them
unreleasable. So the process of /building/ a releasable tarball from several
"git archive" operations, extraction, file deletion, re-tarring is messy with
Mumble when trying to export it from Git.
-- Chris
--
Chris Knadle
chris.kna...@coredump.us
