Bug#925464: new upstream release (1.3rc1)

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#925464: new upstream release (1.3rc1)

Antoine Beaupré-2
Package: mumble
Version: 1.2.18-1+deb9u1
Severity: normal

Upstream has finally got their act together and made a release on the
1.3 branch. It's just an rc1, but maybe it would be better to ship
that with buster than the current git snapshot. That might need some
convincing with the release team, but I think it's worth the trouble.

See:

https://github.com/mumble-voip/mumble/issues/2865

A.

-- System Information:
Debian Release: 9.8
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mumble depends on:
ii  libasound2                 1.1.3-5
ii  libavahi-client3           0.6.32-2
ii  libavahi-common3           0.6.32-2
ii  libavahi-compat-libdnssd1  0.6.32-2
ii  libc6                      2.24-11+deb9u4
ii  libg15daemon-client1       1.9.5.3-8.3+b1
ii  libgcc1                    1:6.3.0-18+deb9u1
ii  libopus0                   1.2~alpha2-1
ii  libprotobuf10              3.0.0-9
ii  libpulse0                  10.0-1+deb9u1
ii  libqt4-dbus                4:4.8.7+dfsg-11
ii  libqt4-network             4:4.8.7+dfsg-11
ii  libqt4-sql                 4:4.8.7+dfsg-11
ii  libqt4-sql-sqlite          4:4.8.7+dfsg-11
ii  libqt4-svg                 4:4.8.7+dfsg-11
ii  libqt4-xml                 4:4.8.7+dfsg-11
ii  libqtcore4                 4:4.8.7+dfsg-11
ii  libqtgui4                  4:4.8.7+dfsg-11
ii  libsndfile1                1.0.27-3
ii  libspeechd2                0.8.6-4+deb9u1
ii  libspeex1                  1.2~rc1.2-1+b2
ii  libspeexdsp1               1.2~rc1.2-1+b2
ii  libssl1.1                  1.1.0j-1~deb9u1
ii  libstdc++6                 6.3.0-18+deb9u1
ii  libx11-6                   2:1.6.4-3+deb9u1
ii  libxi6                     2:1.7.9-1
ii  lsb-release                9.20161125

mumble recommends no packages.

Versions of packages mumble suggests:
pn  mumble-server      <none>
ii  speech-dispatcher  0.8.6-4+deb9u1

-- no debconf information

Reply | Threaded
Open this post in threaded view
|

Bug#925464: new upstream release (1.3rc1)

Chris Knadle
Hello again Antoine.  :)

Antoine Beaupre:
> Package: mumble
> Version: 1.2.18-1+deb9u1
> Severity: normal

Filed against stable rather than unstable; oops.  ;-)

> Upstream has finally got their act together and made a release on the
> 1.3 branch. It's just an rc1, but maybe it would be better to ship
> that with buster than the current git snapshot. That might need some
> convincing with the release team, but I think it's worth the trouble.
>
> See:
>
> https://github.com/mumble-voip/mumble/issues/2865
>
> A.

Okay I've read through issue #2865 -- thank you for discussing the release
issues there.  I totally agree that it would be preferable to ship 1.3.0-rc1
rather than the release I had to do from git because:

  - the release from git doesn't come with a GPG signature,
    so no GPG verification can be done
  - DFSG tarball repacking required due to non-free documents in git submodules
    (which also wrecks GPG verification)
  - the release version numbers when shipping from git are terrible
  - the debian/watch file can't be used when making a tarball from git,
    at least when also needing to make DFSG modifications afterwards,
    AFAICT
  - when users write bug reports, they're for a version that doesn't exist
    upstream  :(

I'm willing to do the work needed to release this to Buster, assuming the
Release Team are agreeable, due to all of the issues above.  What I'll do to
start with is have a look at the -rc1 tarball ASAP to see if it requires DFSG
repacking.

And thanks for your continued in Mumble, BTW.  It helps me to know that doing
the work I do helps others.

   -- Chris

--
Chris Knadle
[hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#925464: new upstream release (1.3rc1)

Chris Knadle
Here's an update on this bug:

I've completed the packaging for 1.3.0-rc1 -- that took a lot more work than it
should have because there are still unreleasable codec documentation files in
the upstream tarball (and new unreleasable files too, argh!).  [Each time I find
new unreleasable files it means starting the work over, in order to keep the
unreleasable files out of the Git history.]

Unfortunately the resulting debdiff between the package before the Buster freeze
and 1.3.0~rc1+dfsg-1 is about 10 MB in size.  And it looks like it's a lot of
real "sprinkled" changes throughout the code, not just the result of file
re-ordering or repack file removal.  It's a large amount of actual change.

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.

   -- Chris

--
Chris Knadle
[hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#925464: new upstream release (1.3rc1)

Antoine Beaupré-2
On 2019-04-17 01:31:49, Chris Knadle wrote:

[...]

Wow, that must have all been a lot of work, thanks! :)

> 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!

I can change the severity of this bug, if you agree, which should
eventually kick the package out of testing...

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. ;)

Cheers,

A.
--
Nature hides her secret because of her essential loftiness, but not by
means of ruse.
                       - Albert Einstein

Reply | Threaded
Open this post in threaded view
|

Bug#925464: new upstream release (1.3rc1)

Chris Knadle
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
[hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#925464: new upstream release (1.3rc1)

Chris Knadle
In reply to this post by Antoine Beaupré-2
Update on the bug:

Chris Knadle:
[..]
> 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.

The release team has rejected the change in #927266 (which is not unexpected,
and I agree with their decision).

   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927266

So Debian Buster will release with mumble 1.3.0~git20190125.440b173+dfsg-2

   -- Chris

--
Chris Knadle
[hidden email]