Just a couple of process notes. Sam Hartman <hartm...@debian.org> writes:
> I propose to upload a version of krb5 to unstable in about a week that > is basically identical to the krb5 in experimental. I will include some > debconf fixes, a news file, and other minor changes. See the > experimental branch of [2] for ongoing work towards this upload. > > [2] git://git.debian.org/git/pkg-k5-afs/debian-krb5.git debian-release should sign off on the timing before we start the transition, and it may be that they'll want you to hold off due to other things already in motion. The goal is generally to avoid tangling together multiple transitions, which makes it very hard to get things to migrate into testing. > Unfortunately, there are a lot of packages that reverse depend on > libkrb53. All of these packages will need to be rebuilt. > Here's where I need sanity checking. > > I assume that after the new krb5 has made its way into unstable and has > built on all arches, I should send mail to all these packages asking > them to upload a new version built against the new krb5. You, and the maintainer, shouldn't have to do anything here. Since the API didn't change for applications that don't use Kerberos v4, this can be done via binNMUs triggered by the release team. Maintainers should generally *not* do sourceful uploads since the name of the development package has not changed. Build dependencies should similarly not need to change. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
