Bug#308339: Wrong source package name

Jeroen van Wolffelaar Jeroen van Wolffelaar <jeroen@wolffelaar.nl>, 308339@bugs.debian.org
Mon May 9 18:09:02 2005


On Mon, May 09, 2005 at 07:25:24PM +0200, Wolfgang Baer wrote:
> Hi Jeroen,
> 
> Jeroen van Wolffelaar wrote:
> >Package: jakarta-log4j1.2
> >
> >Library packages should not have a version-specific source-package name,
> >unless there is a good reason to need to have multiple versions.
> >Considering the number of packages depending on log4j, this seems not to
> >be the case here.
> 
> 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.
 
--Jeroen

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