Bug#308339: Wrong source package name

Jeroen van Wolffelaar Jeroen van Wolffelaar <jeroen@wolffelaar.nl>, 308339@bugs.debian.org
Thu May 12 22:24:02 2005


On Thu, May 12, 2005 at 11:51:02PM +0200, Arnaud Vandyck wrote:
> Mon, 9 May 2005 19:47:46 +0200, 
> Jeroen van Wolffelaar <jeroen@wolffelaar.nl> wrote: 
> 
> > On Mon, May 09, 2005 at 07:25:24PM +0200, Wolfgang Baer wrote:
> 
> [...]
> 
> >> Well, I think it was due to the old jakarta-log4j source package
> >> which has currently a pending removal request and you have just
> >> removed :-)
> >> 
> >> http://packages.qa.debian.org/j/jakarta-log4j.html
> >
> > Right, but you can instead just supersede that package by a new upload
> > building other binary packages, thus completely rendering the go via
> > ftp-master unneeded -- that was my point. Library name transitions would
> > otherwise always need to go via ftp-master, which would be one big mess.
> >
> > If the name stays like this, next time it'll be log4j1.3, log4j1.4,
> > etc., each time requiring ftp-master intervention.  I'm saying the
> > source package should always remain at log4j.
> 
> I don't understand how you manage libraries that have incompatible
> API's? How do we do with ant? bsh? servlet? struts?
> 
> You mean creating a tarball with the two different versions of the lib?!
> And why do you want we change the name of the source package when the
> first one is removed?

What I mean is to indeed have different binary package package names,
the libraries are incompatible anyway.

My only point is to have the *same* _source_ package name. This does
mean that the old library will get deleted on upload, so that all
depending packages will need to be updated in about the same timeframe.
This usually should be easily doable, and when doing so, it means less
work for all and no obsolete packages hanging around for long times --
no need to ask for removals, and a swift transition.

This is of course of medium/long-term importance, and of course this all
is to be decided how to precisely do when the situation arises.

Thanks,
--Jeroen

-- 
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl