library renaming due to changed libstdc++ configuration (for kfreebsd-i386)

[Aurelien Jarno]

Here is some comments about how would be handled the transition 
on kfreebsd-i386, based on the mail of Matthias Klose to
debian-devel-announce.

On Tue, Nov 15, 2005 at 06:28:05AM +0100, Matthias Klose wrote:
> Another round of package renamings of some libraries written in C++ is
> needed. Background:

Details stripped, for those who haven't seen the mail, please have a
look at:

http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html


> What has to be done:
> 

[...]

> 
>  * Provide gcc-3.4 and gcc-4.0 packages configured using the default
>    (new) allocator. These packages are currently available from
>       http://people.debian.org/~doko/gcc-4.0/ (4.0.2-4)
>       http://people.debian.org/~doko/gcc-3.4/ (3.4.4-10)

Packages for kfreebsd-i386 are available from
  http://io.debian.net/~aurel32/

>  * Upload updated gcc-3.4 and gcc-4.0 packages.
>    Will be done on Wednesday Nov 16, around 22:00 UTC

The install script on gnuab is run more often than the Debian one (ie
every six hours instead of every day), so I will upload those packages
on Thursday Nov 17, around 15:00 UTC.

>  * Upgrade the buildd's to the updated gcc-3.4 and gcc-4.0 packages.

I will do that just after the install run, ie around 18:00 UTC on
Thursday.

>  * Build new packages with the updated gcc-3.4 and gcc-4.0 packages
>    only.

That is not really a problem for us as long as the packages are built by
the buildds.

  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  !!! If you are uploading packages built by hand, please use   !!!
  !!! the updated versions of gcc-3.4 or gcc-4.0 after Thursday !!! 
  !!! Nov 17, around 18:00 UTC                                  !!!
  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

>  * Rename and rebuild the libraries listed below. The new suffix for
>    these packages should be in any case "c2a" (instead of "c2"). No
>    new suffix is needed when the soname changes in a new upstream
>    upload. The libfoo1c2a packages need to conflict/replace the old
>    libfoo1c2 package (and keep existing conflict/replaces). You can
>    find more details in
>    http://lists.debian.org/debian-devel-announce/2005/07/msg00001.html

That does not concerns us.

>  * Once dependencies are fulfilled for all architectures, request
>    binNMU's for all other packages depending on a library package with
>    a changed package name. Request for binNMUs shold be sent to
>    debian-release at lists.debian.org.
>    If a source upload is necessary for other fixes, wait as well until
>    dependencies are fulfilled for all architectures.

After a discussion with Matthias Klose and Steve Langasek, Steve agreed
to maintain a list of binNMUed packages, for non-official ports (mainly
for amd64 and kfreebsd-i386):

http://ftp-master.debian.org/~vorlon/transition-binnmus.txt

However, other people who have access to the wanna-build database could 
trigger a binNMU, so a few packages may be missing from this list.
Therefore, I will check the output of my mirror script to try to detect
which packages have been binNMUed, and if I found some, I will ask Steve
to add them to the list.

I will handle the binNMU on the buildds, however, I have first to
install the new wanna-build suite, which supports binNMUs directly from
wanna-build. I have the code, I am currently checking what has changed,
and I will have to port our patches to the new version. If I fail to do
that, I would have to handle binNMU directly with sbuild, but that's
easily scriptable.

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32 at debian.org         | aurelien at aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net