Debian Bug report logs - #410039
No /usr/lib/xen folder so it's confusing other packages

Package: linux-image-2.6-xen-686; Maintainer for linux-image-2.6-xen-686 is Debian Kernel Team <debian-kernel@lists.debian.org>;

Reported by: Thomas GOIRAND <thomas@goirand.fr>

Date: Wed, 7 Feb 2007 10:03:01 UTC

Severity: wishlist

Done: Bastian Blank <waldi@debian.org>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#410039; Package linux-image-2.6-xen-686. Full text and rfc822 format available.

Acknowledgement sent to Thomas GOIRAND <thomas@goirand.fr>:
New Bug report received and forwarded. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Thomas GOIRAND <thomas@goirand.fr>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: No /usr/lib/xen folder so it's confusing other packages
Date: Wed, 07 Feb 2007 17:55:32 +0800
Package: linux-image-2.6-xen-686
Severity: wishlist

Hello,

Our package, dtc-xen, uses /usr/lib/python/xen installed by the
normal xen source package using make install. With this package,
there is no such folder, but instead something with version
number like this: /usr/lib/xen-3.0.3-1/lib/python. So we cannot
include the xen python bindings for xen.xm that we use to start
and stop a VM. Of course, there is no error when using the
source version of xen from xensource.com. I highly think
that not having this /usr/lib/python/xen folder under the
Debian package is really problematic.

As there would be a problem to just insert a symlink in the
package itself (diversion problems when upgrading or when you
want to have both versions installed at the same time), my
suggestion is that the postinst of the package creates a
symlink in /usr/lib/python/xen so that it always works. Note
that our package (dtc-xen) will not care if it's not the
corresponding kernel that is started, I believe, but this
would for sure solve our issues.

I'd appreciate A LOT if this was fixed. Note that I have filed
a bug only for this i686 version, but of course, the same
problem occurs when running on amd64 and other images.

Best regards and thanks for this work,

Thomas Goirand


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.17.7
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#410039; Package linux-image-2.6-xen-686. Full text and rfc822 format available.

Acknowledgement sent to Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #10 received at submit@bugs.debian.org (full text, mbox):

From: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
To: Thomas GOIRAND <thomas@goirand.fr>
Cc: 410039@bugs.debian.org, Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Re: Bug#410039: No /usr/lib/xen folder so it's confusing other packages
Date: Fri, 16 Feb 2007 08:04:54 +0100
Thomas GOIRAND <thomas@goirand.fr> writes:

> Package: linux-image-2.6-xen-686
> Severity: wishlist
>
> Hello,
>
> Our package, dtc-xen, uses /usr/lib/python/xen installed by the
> normal xen source package using make install. With this package,
> there is no such folder, but instead something with version
> number like this: /usr/lib/xen-3.0.3-1/lib/python. So we cannot
> include the xen python bindings for xen.xm that we use to start
> and stop a VM. Of course, there is no error when using the
> source version of xen from xensource.com. I highly think
> that not having this /usr/lib/python/xen folder under the
> Debian package is really problematic.

The problem is that multiple xen versions (3.0-unstable, 3.0.3, 3.0.4)
can be installed and they are incompatible with each other. If each
one contained /usr/lib/python/xen then the packages would have to
conflict.

What you need is a common package that contains wrapper scripts in
/usr/lib/python/xen that will pick the right
/usr/lib/xen-VERSION/lib/python subdir applicable to the running xen
version.

Maybe xen-utils-common is what you should be using?

> As there would be a problem to just insert a symlink in the
> package itself (diversion problems when upgrading or when you
> want to have both versions installed at the same time), my
> suggestion is that the postinst of the package creates a
> symlink in /usr/lib/python/xen so that it always works. Note
> that our package (dtc-xen) will not care if it's not the
> corresponding kernel that is started, I believe, but this
> would for sure solve our issues.

What if you remove the package? The postrm would remove the
symlink. But it would not create a symlink to an alternative version
normaly.

This sounds more like a job for update-alternatives but can you use
that on directories? And only if it truely doesn't matter what version
you end up with.

> I'd appreciate A LOT if this was fixed. Note that I have filed
> a bug only for this i686 version, but of course, the same
> problem occurs when running on amd64 and other images.
>
> Best regards and thanks for this work,
>
> Thomas Goirand

MfG
        Goswin



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#410039; Package linux-image-2.6-xen-686. Full text and rfc822 format available.

Acknowledgement sent to Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#410039; Package linux-image-2.6-xen-686. Full text and rfc822 format available.

Acknowledgement sent to Thomas Goirand <thomas@goirand.fr>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #20 received at 410039@bugs.debian.org (full text, mbox):

From: Thomas Goirand <thomas@goirand.fr>
To: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
Cc: 410039@bugs.debian.org
Subject: Re: Bug#410039: No /usr/lib/xen folder so it's confusing other packages
Date: Fri, 16 Feb 2007 22:11:29 +0800
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Goswin von Brederlow wrote:
> The problem is that multiple xen versions (3.0-unstable, 3.0.3, 3.0.4)
> can be installed and they are incompatible with each other. If each
> one contained /usr/lib/python/xen then the packages would have to
> conflict.

I understood that, for sure!

> What you need is a common package that contains wrapper scripts in
> /usr/lib/python/xen that will pick the right
> /usr/lib/xen-VERSION/lib/python subdir applicable to the running xen
> version.
> 
> Maybe xen-utils-common is what you should be using?

Maybe a script run at startup could check for the xen version that is
running and make the appropriate symlink? Sure that could be in a
xen-common package, for example... Is that what xen-utils-common does?

Thomas



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF1buQl4M9yZjvmkkRAtTDAJ9TOYMKkyfvTSs1xjEpcFniyCbz7QCg4P0a
eydB76cWR1OcL8U/zeRbSF0=
=4SYo
-----END PGP SIGNATURE-----



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#410039; Package linux-image-2.6-xen-686. Full text and rfc822 format available.

Acknowledgement sent to Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #25 received at 410039@bugs.debian.org (full text, mbox):

From: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
To: Thomas Goirand <thomas@goirand.fr>
Cc: 410039@bugs.debian.org, Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
Subject: Re: Bug#410039: No /usr/lib/xen folder so it's confusing other packages
Date: Fri, 23 Feb 2007 10:31:23 +0100
Thomas Goirand <thomas@goirand.fr> writes:

> Goswin von Brederlow wrote:
>> The problem is that multiple xen versions (3.0-unstable, 3.0.3, 3.0.4)
>> can be installed and they are incompatible with each other. If each
>> one contained /usr/lib/python/xen then the packages would have to
>> conflict.
>
> I understood that, for sure!
>
>> What you need is a common package that contains wrapper scripts in
>> /usr/lib/python/xen that will pick the right
>> /usr/lib/xen-VERSION/lib/python subdir applicable to the running xen
>> version.
>> 
>> Maybe xen-utils-common is what you should be using?
>
> Maybe a script run at startup could check for the xen version that is
> running and make the appropriate symlink? Sure that could be in a
> xen-common package, for example... Is that what xen-utils-common does?
>
> Thomas

/usr is (potentially) read-only. You can only write there during
install time which is not enough. You would have to put a static link
to /var/lib/xen and then have a dynamic link there or something.

MfG
        Goswin



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#410039; Package linux-image-2.6-xen-686. Full text and rfc822 format available.

Acknowledgement sent to Thomas Goirand <thomas@goirand.fr>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #30 received at 410039@bugs.debian.org (full text, mbox):

From: Thomas Goirand <thomas@goirand.fr>
To: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
Cc: 410039@bugs.debian.org
Subject: Re: Bug#410039: No /usr/lib/xen folder so it's confusing other packages
Date: Tue, 27 Feb 2007 18:45:12 +0800
Goswin von Brederlow wrote:
> Thomas Goirand <thomas@goirand.fr> writes:
> 
>> Goswin von Brederlow wrote:
>>> The problem is that multiple xen versions (3.0-unstable, 3.0.3, 3.0.4)
>>> can be installed and they are incompatible with each other. If each
>>> one contained /usr/lib/python/xen then the packages would have to
>>> conflict.
>> I understood that, for sure!
>>
>>> What you need is a common package that contains wrapper scripts in
>>> /usr/lib/python/xen that will pick the right
>>> /usr/lib/xen-VERSION/lib/python subdir applicable to the running xen
>>> version.
>>>
>>> Maybe xen-utils-common is what you should be using?
>> Maybe a script run at startup could check for the xen version that is
>> running and make the appropriate symlink? Sure that could be in a
>> xen-common package, for example... Is that what xen-utils-common does?
>>
>> Thomas
> 
> /usr is (potentially) read-only. You can only write there during
> install time which is not enough. You would have to put a static link
> to /var/lib/xen and then have a dynamic link there or something.
> 
> MfG
>         Goswin

Then what's the solution???

Thomas





Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#410039; Package linux-image-2.6-xen-686. Full text and rfc822 format available.

Acknowledgement sent to Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #35 received at 410039@bugs.debian.org (full text, mbox):

From: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
To: Thomas Goirand <thomas@goirand.fr>
Cc: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>, 410039@bugs.debian.org
Subject: Re: Bug#410039: No /usr/lib/xen folder so it's confusing other packages
Date: Mon, 12 Mar 2007 11:58:24 +0100
Thomas Goirand <thomas@goirand.fr> writes:

> Goswin von Brederlow wrote:
>> Thomas Goirand <thomas@goirand.fr> writes:
>> 
>>> Goswin von Brederlow wrote:
>>>> The problem is that multiple xen versions (3.0-unstable, 3.0.3, 3.0.4)
>>>> can be installed and they are incompatible with each other. If each
>>>> one contained /usr/lib/python/xen then the packages would have to
>>>> conflict.
>>> I understood that, for sure!
>>>
>>>> What you need is a common package that contains wrapper scripts in
>>>> /usr/lib/python/xen that will pick the right
>>>> /usr/lib/xen-VERSION/lib/python subdir applicable to the running xen
>>>> version.
>>>>
>>>> Maybe xen-utils-common is what you should be using?
>>> Maybe a script run at startup could check for the xen version that is
>>> running and make the appropriate symlink? Sure that could be in a
>>> xen-common package, for example... Is that what xen-utils-common does?
>>>
>>> Thomas
>> 
>> /usr is (potentially) read-only. You can only write there during
>> install time which is not enough. You would have to put a static link
>> to /var/lib/xen and then have a dynamic link there or something.
>> 
>> MfG
>>         Goswin
>
> Then what's the solution???
>
> Thomas

Beats me. The xen maintainer(s) have to make a choice there.

MfG
        Goswin



Reply sent to Bastian Blank <waldi@debian.org>:
You have taken responsibility. (Sat, 20 Sep 2008 12:39:50 GMT) Full text and rfc822 format available.

Notification sent to Thomas GOIRAND <thomas@goirand.fr>:
Bug acknowledged by developer. (Sat, 20 Sep 2008 12:39:50 GMT) Full text and rfc822 format available.

Message #40 received at 410039-done@bugs.debian.org (full text, mbox):

From: Bastian Blank <waldi@debian.org>
To: 410039-done@bugs.debian.org
Subject: no kernel bug
Date: Sat, 20 Sep 2008 11:31:34 +0200
/usr/lib/xen is nothing the kernel can use. So no bug for the kernel.
Please open a bug against a real package.

Bastian

-- 
Murder is contrary to the laws of man and God.
		-- M-5 Computer, "The Ultimate Computer", stardate 4731.3




Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Sun, 19 Oct 2008 07:27:41 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sat Apr 19 08:01:49 2014; Machine Name: buxtehude.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.