On Thu, Oct 04, 2018 at 04:16:50PM +0200, Bernhard Schmidt wrote:
> on behalf of Jonas I'm filing a transition bug to track removal of the old
> libsrtp0 from Debian.
>
> src:srtp has built libsrtp0 and libsrtp0-dev. It is several years out of date.
> The successor is src:libsrtp2 building libsrtp2-1 and libsrtp2-dev. Most rdeps
> have already migrated. We'd like to avoid releasing libsrtp0 with Buster if
> possible.
The release team is not usually involved in these things, that don't
really count as "transitions" usually.
The normal procedure is:
1 File a RC bug against src:srtp so the autoremoval clocks starts
ticking. If the package is a key-package (not the case) or you want
it removed from testing sooner than you can get the releease team
involved of course.
2 File a RM bug against ftp.debian.org, tagged moreinfo as the removal
can't be processed right away
3 File RC bugs against all the reverse dependencies, stating that they
need to migrate away from src:srtp, make these bugs block the RM bug
filed at point 2.
According to my dak rm:
Checking reverse dependencies...
# Broken Depends:
asterisk: asterisk-modules [hurd-i386]
gst-plugins-bad1.0: gstreamer1.0-plugins-bad [hurd-i386 kfreebsd-amd64 kfreebsd-i386]
kopete: kopete [amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x]
opal: libopal-dev [amd64 armel i386 mips mipsel]
libopal3.10.10 [amd64 armel i386 mips mipsel]
resiprocate: librecon-1.11 [amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x]
# Broken Build-Depends:
kopete: libsrtp0-dev
Those are the packages you should interact with.
> There has been an incomplete attempt to update libsrtp 1.x in experimental a
> few years ago (building libsrtp1). This has never gained traction and has been
> superseded by libsrtp2. The only accidental rdep inside experimental is waiting
> for the buildds to catch up, then I'll request removal from experimental as
> well.
Right, you can file the RM already, specifying that it's fine to break
rdeps.
But there is also src:qtwebengine-opensource-src that is build-depending
on libsrtp-dev (which is experimental only). You'll need to bug that
package as well.
Really, the release team is not the body you need to involve for these
changes, they need to be all handled by the maintainer of srtp (or
anybody else, with the maintainer's ack), and a transition tracker won't
really help you, all you need is asking `dak rm`'s opinion :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature