Bug#328080: marked as done (java-package: make several j2sdk1.5-sun updates cohabit)

Tue Sep 13 11:18:10 UTC 2005

Your message dated Tue, 13 Sep 2005 13:03:22 +0200
with message-id <20050913110322.GQ17317 at A-Eskwadraat.nl>
and subject line Bug#328080: java-package: make several j2sdk1.5-sun updates cohabit
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 13 Sep 2005 10:10:04 +0000
>From rv at eychenne.org Tue Sep 13 03:10:04 2005
Return-path: <rv at eychenne.org>
Received: from router.spheregroup.net (esmtp.spheregroup.net) [213.246.197.240] 
	by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
	id 1EF7jo-0004s0-00; Tue, 13 Sep 2005 03:10:04 -0700
Received: from comet.rv-int ([213.246.197.242])
	by spheregroup.net (pandora [213.246.197.150])
	(MDaemon.PRO.v6.8.5.R)
	with ESMTP id 1-md50000000510.tmp
	for <submit at bugs.debian.org>; Tue, 13 Sep 2005 12:08:24 +0200
Received: from rv by comet.rv-int with local (Exim 4.50)
	id 1EF7j1-0008SL-PC
	for submit at bugs.debian.org; Tue, 13 Sep 2005 12:09:15 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: =?iso-8859-15?q?Herv=E9_Eychenne?= <rv at eychenne.org>
To: Debian Bug Tracking System <submit at bugs.debian.org>
Subject: java-package: make several j2sdk1.5-sun updates cohabit
X-Mailer: reportbug 3.8
Date: Tue, 13 Sep 2005 12:09:15 +0200
Message-Id: <E1EF7j1-0008SL-PC at comet.rv-int>
X-Spam-Processed: pandora, Tue, 13 Sep 2005 12:08:24 +0200
	(not processed: message from trusted or authenticated source)
X-MDRemoteIP: 213.246.197.242
X-Return-Path: rv at eychenne.org
X-MDaemon-Deliver-To: submit at bugs.debian.org
Reply-To: rv at eychenne.org
Delivered-To: submit at bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: java-package
Version: 0.24
Severity: normal

For Sun sdk, java-package creates a package whose files are
mostly installed under /usr/lib/j2sdk1.5-sun/, whatever update
version it is... So installing the package created for update number
4 replaces the update 3, for example.
So it's hard to make several updates cleanly cohabit at the same time
(for test purpose before migration, for example).

A workaround could be to include the revision number in the directory
(/usr/lib/j2sdk1.5_03-sun/, /usr/lib/j2sdk1.5_04-sun/).
What do you think?

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.11
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages java-package depends on:
ii  coreutils                     5.2.1-2    The GNU core utilities
ii  debhelper                     4.2.32     helper programs for debian/rules
ii  fakeroot                      1.2.10     Gives a fake root environment

-- no debconf information

---------------------------------------
Received: (at 328080-done) by bugs.debian.org; 13 Sep 2005 11:03:24 +0000
>From jeroen at wolffelaar.nl Tue Sep 13 04:03:24 2005
Return-path: <jeroen at wolffelaar.nl>
Received: from a-eskwadraat.nl [131.211.39.72] 
	by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
	id 1EF8ZQ-00063q-00; Tue, 13 Sep 2005 04:03:24 -0700
Received: from jeroen by a-eskwadraat.nl with local (Exim 4.50)
	id 1EF8ZO-0003We-O4; Tue, 13 Sep 2005 13:03:22 +0200
Date: Tue, 13 Sep 2005 13:03:22 +0200
To: rv at eychenne.org, 328080-done at bugs.debian.org
Subject: Re: Bug#328080: java-package: make several j2sdk1.5-sun updates cohabit
Message-ID: <20050913110322.GQ17317 at A-Eskwadraat.nl>
References: <E1EF7j1-0008SL-PC at comet.rv-int>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <E1EF7j1-0008SL-PC at comet.rv-int>
User-Agent: Mutt/1.5.9i
From: Jeroen van Wolffelaar <jeroen at wolffelaar.nl>
Delivered-To: 328080-done at bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02

On Tue, Sep 13, 2005 at 12:09:15PM +0200, Hervé Eychenne wrote:
> For Sun sdk, java-package creates a package whose files are
> mostly installed under /usr/lib/j2sdk1.5-sun/, whatever update
> version it is... So installing the package created for update number
> 4 replaces the update 3, for example.
> So it's hard to make several updates cleanly cohabit at the same time
> (for test purpose before migration, for example).
> 
> A workaround could be to include the revision number in the directory
> (/usr/lib/j2sdk1.5_03-sun/, /usr/lib/j2sdk1.5_04-sun/).
> What do you think?

I think 'bad idea'. Minor revisions like this are never been done in new
package names, php 4.0.* isn't coinstalleable with php 4.4.*, it's all called
'php4'. Only php5 is a different package name.

If you want to test such minor updates, you can either install them
alternatingly, or use a chroot to stage your install (a chroot is relatively
easy to do). If it's very mission critical, you'd probably have extra hardware
to test it on anyway. For less critical things, just installing it, testing,
and reverting to the older version if something breaks, works just as good,
and provides a lot less hassle for everyone else (our dependency and
alternative system can't handle new packagename with minor update very well,
especially due to the many, automatically generated and unpredicteable in
advance, package names that involves, they are not designed for that).
for that).

Sorry,
--Jeroen

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