Bug#343997: fglrx-driver: Problem with diversion

2006-01-03 Thread Daniel Leidert
Please fix this issue soon. In the worst case, change back to the last
working solution and reopen
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341458 until we have a
better solution.

Regards, Daniel



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



Bug#343997: fglrx-driver: Problem with diversion

2006-01-02 Thread Bruno Harbulot

Christian Marillat wrote:

Flavio Stanchina <[EMAIL PROTECTED]> writes:

Christian Marillat wrote:
I had a feeling that diverting the ldconfig symlink was not a good idea,
even if lintian and several actual people complained that I should do
so, but I didn't anticipate this particular problem.

Are there other packages that divert library symlinks? How do they solve
this problem? Would it work if I added a shlibs file with the same
contents as the xlibmesa-gl.shlibs file?



May be a good exemple is the nvidia package ?


Recent versions of the ATI installer (>= 8.16, I think) can produce 
Debian packages. They use the diversion.
I was using the deb packages from the ATI installer, but the fglrx 
packages in the deb repository seem to conflict with them. (It wouldn't 
be a problem without this issue about the symlink, because I don't 
really mind which ones I use as long as it works). It's almost 
impossible to force the "old" packages (that I had installed with the 
ATI installer) not to be replaced with the packages in the debian 
repository (same version and revision number).
Would it be possible to use a different package name, or perhaps simply 
to provide the packages produced by the ATI installer? (Perhaps I should 
fill in another bug report.)




What if a program links against libGL.so.1.2 (the actual file) rather
than the symlink?


Were you talking about package dependencies only? Otherwise, it's a 
shared library, so it shouldn't really matter if the dynamic linking is 
done against a symlink or an actual file.



Regards,

Bruno.


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



Bug#343997: fglrx-driver: Problem with diversion

2005-12-19 Thread Christian Marillat
Flavio Stanchina <[EMAIL PROTECTED]> writes:

> Christian Marillat wrote:
>> The new diversion is broken. Here is the dpkg-shlibdeps output :
>> 
>> dpkg-shlibdeps: warning: diversions involved - output may be incorrect
>>  diversion by fglrx-driver from: /usr/X11R6/lib/libGL.so.1
>> 
>> After that my package depends on fglrx-driver instead of the xlibmesa-gl.
>
> Let me see if I understand the problem correctly: if someone builds a
> package that links against libGL.so.1 while fglrx-driver is installed,
> the package will depend on fglrx-driver instead of xlibmesa-gl?

Yes.

> I had a feeling that diverting the ldconfig symlink was not a good idea,
> even if lintian and several actual people complained that I should do
> so, but I didn't anticipate this particular problem.
>
> Are there other packages that divert library symlinks? How do they solve
> this problem? Would it work if I added a shlibs file with the same
> contents as the xlibmesa-gl.shlibs file?

May be a good exemple is the nvidia package ?

> What if a program links against libGL.so.1.2 (the actual file) rather
> than the symlink?

Franckly I don't know. The previous package was working correctly.

Christian


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



Bug#343997: fglrx-driver: Problem with diversion

2005-12-19 Thread Flavio Stanchina
Christian Marillat wrote:
> The new diversion is broken. Here is the dpkg-shlibdeps output :
> 
> dpkg-shlibdeps: warning: diversions involved - output may be incorrect
>  diversion by fglrx-driver from: /usr/X11R6/lib/libGL.so.1
> 
> After that my package depends on fglrx-driver instead of the xlibmesa-gl.

Let me see if I understand the problem correctly: if someone builds a
package that links against libGL.so.1 while fglrx-driver is installed,
the package will depend on fglrx-driver instead of xlibmesa-gl?

I had a feeling that diverting the ldconfig symlink was not a good idea,
even if lintian and several actual people complained that I should do
so, but I didn't anticipate this particular problem.

Are there other packages that divert library symlinks? How do they solve
this problem? Would it work if I added a shlibs file with the same
contents as the xlibmesa-gl.shlibs file?

What if a program links against libGL.so.1.2 (the actual file) rather
than the symlink?

-- 
Ciao, Flavio


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



Bug#343997: fglrx-driver: Problem with diversion

2005-12-19 Thread Christian Marillat
Package: fglrx-driver
Version: 8.20.8-1
Severity: normal

Hi,

The new diversion is broken. Here is the dpkg-shlibdeps output :

dpkg-shlibdeps: warning: diversions involved - output may be incorrect
 diversion by fglrx-driver from: /usr/X11R6/lib/libGL.so.1

After that my package depends on fglrx-driver instead of the xlibmesa-gl.

I think you need to prvides a new package quicly, before maintainers
upload broken packages.

Christian

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-rc2
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages fglrx-driver depends on:
ii  libc62.3.5-9 GNU C Library: Shared libraries an
ii  libstdc++5   1:3.3.6-10  The GNU Standard C++ Library v3
ii  libx11-6 6.8.2.dfsg.1-11 X Window System protocol client li
ii  libxext6 6.8.2.dfsg.1-11 X Window System miscellaneous exte
ii  xserver-xorg 6.8.2.dfsg.1-11 the X.Org X server

Versions of packages fglrx-driver recommends:
ii  fglrx-k 8.20.8-1+2.6.15-rc2-10.00.Custom ATI binary kernel module for Linux

-- no debconf information


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