On Thu, Feb 07, 2008 at 07:02:16PM +0100, Luk Claes wrote: > Uwe Steinmann wrote: > > On Wed, Feb 06, 2008 at 07:57:03PM +0100, Luk Claes wrote: > >> Debian Bug Tracking System wrote: > >>> Processing commands for [EMAIL PROTECTED]: > >>> > >>>> reassign 418318 ftp.debian.org > >>> Bug#418318: Don't build a php4-specific package because of php4's removal > >>> Bug reassigned from package `php4-ps' to `ftp.debian.org'. > >> Shouldn't you just remove the php4-ps binary package in your next upload > >> fixing this bug? > > That's what I thought as well but Wiesiek Swiatek told me: > > > > <quote> > > You should reassign this bug to ftp.debian.org metapackage with ask to > > removal this package from unstable. > > Upload new package as "php-ps" is not enougn, becouse source (php4-ps) > > still is aviable in unstable. > > </quote> > > If you really want to change the source package name, then you indeed > have to ask for removal of this package. Though I would advise to upload > the new source package first if that's the case and read [1] to have a > decent bug title for package removals. This is still very confusing for me. Reading [1] I get the impression that everything is done automatically. The source package php4-ps used to produce two binary packages php4-ps and php5-ps. Now that php4 isn't supported anymore, only php5-ps will be left, which is somewhat strange. A source package php4-ps produces a binary package php5-ps. That's why I created a new source package php-ps which produces php5-ps. Isn't this one of the cases where rene takes care of automatic removal?
'Source packages which have had all their binary packages taken over by another source packages' Uwe -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: 02331 840446 Fax: 02331 843920
signature.asc
Description: Digital signature