On Fri, Feb 10, 2006 at 01:23:54PM +0100, Christian Hammers wrote:
> Hello Jeroen
> 
> On 2006-02-10 Jeroen van Wolffelaar wrote:
> > > The mysql-dfsg-5.0 source packages used to produce
> > >   mysql-server-4.1
> > >   mysql-client-4.1
> > > for a short while but removed those packages from the
> > > control file. "britney"(?) now thinks that it accidently failed
> > > to build those and blocks mysql-dfsg-5.0 from entering testing.
> > 
> > That's because those packages still are built by mysql-dfsg-4.1 and
> > mysql-dfsg. Please either:
> > - stop building those packages from there,
>    Would uploading a new version of the mysql-dfsg-4.1 source
>    package with a 4.1.x version i.e. a lower one as that of the
>    zombie packages be enough? This would easily possible as the
>    package will be removed soon anyway.

Yeah, as long as you stop building it. I'd suggest stopping to build
anything except the library.

> > - request us to remove those source packages (you can retitle and
> >   reassign this bug), or
>    I still have 26 open bugs asking other packages no longer to link
>    against libmysqlclient12 which is produced by the source package
>    mysql-dfsg-4.1, too.

If people had ample time to migrate and there's no important packages
left, this doesn't need to hold up removal. It's a manageable number of
packages to NMU. Please consult with the release team if you have any
suspicion that such forced migration would cause any problems. I don't
see any really important or big packages listed that haven't migrated yet.

> > - bump the version numbers of those 4.0 and 4.1 packages so that they
> >   would supersede the versions built by mysql-dfsg-5.0
>    I don't like to upload a "mysql-server-4.1 (5.0.x)" package as this
>    would confuse the users of testing/unstable. Can it be avoided?

Yeah, you'd need to epoch it to not have a weird version number.

--Jeroen

-- 
Jeroen van Wolffelaar
[EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to