[opensuse-packaging] Issue with "inked against libraries in /usr or /opt"
Hello, I'm trying to build DeviceKit-disks [1] but get the following error; binary /sbin/umount.devkit is linked against libraries in /usr or /opt libdbus-glib-1.so.2 => /usr/lib64/libdbus-glib-1.so.2 (0x00007f9b15c73000) libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f9b15a2c000) libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f9b15765000) libpolkit-dbus.so.2 => /usr/lib64/libpolkit-dbus.so.2 (0x00007f9b15558000) libpolkit.so.2 => /usr/lib64/libpolkit.so.2 (0x00007f9b1533e000) libpcre.so.0 => /usr/lib64/libpcre.so.0 (0x00007f9b14b76000) Any idea on how to fix this? Cheers, Magnus [1] https://build.opensuse.org/package/show?package=DeviceKit-disks&project=home%3AMBoman%3Abranches%3AGNOME%3AFactory -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Sun, May 10, 2009 at 10:39 AM, Magnus Boman <captain.magnus@gmail.com> wrote:
Hello,
I'm trying to build DeviceKit-disks [1] but get the following error;
binary /sbin/umount.devkit is linked against libraries in /usr or /opt libdbus-glib-1.so.2 => /usr/lib64/libdbus-glib-1.so.2 (0x00007f9b15c73000) libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f9b15a2c000) libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f9b15765000) libpolkit-dbus.so.2 => /usr/lib64/libpolkit-dbus.so.2 (0x00007f9b15558000) libpolkit.so.2 => /usr/lib64/libpolkit.so.2 (0x00007f9b1533e000) libpcre.so.0 => /usr/lib64/libpcre.so.0 (0x00007f9b14b76000)
Any idea on how to fix this?
Install the binary in /usr/sbin? -J -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Sun, 2009-05-10 at 10:42 +0530, CyberOrg wrote:
On Sun, May 10, 2009 at 10:39 AM, Magnus Boman <captain.magnus@gmail.com> wrote:
Hello,
I'm trying to build DeviceKit-disks [1] but get the following error;
binary /sbin/umount.devkit is linked against libraries in /usr or /opt libdbus-glib-1.so.2 => /usr/lib64/libdbus-glib-1.so.2 (0x00007f9b15c73000) libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f9b15a2c000) libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f9b15765000) libpolkit-dbus.so.2 => /usr/lib64/libpolkit-dbus.so.2 (0x00007f9b15558000) libpolkit.so.2 => /usr/lib64/libpolkit.so.2 (0x00007f9b1533e000) libpcre.so.0 => /usr/lib64/libpcre.so.0 (0x00007f9b14b76000)
Any idea on how to fix this?
Install the binary in /usr/sbin?
All other umount commands are in /sbin so probably want to keep it in there. Can't see that device-mapper (aka lvm2) is doing anything special to be able to install into /sbin either. Cheers, Magnus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Magnus Boman escribió:
Hello,
I'm trying to build DeviceKit-disks [1] but get the following error;
binary /sbin/umount.devkit is linked against libraries in /usr or /opt libdbus-glib-1.so.2 => /usr/lib64/libdbus-glib-1.so.2 (0x00007f9b15c73000) libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f9b15a2c000) libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f9b15765000) libpolkit-dbus.so.2 => /usr/lib64/libpolkit-dbus.so.2 (0x00007f9b15558000) libpolkit.so.2 => /usr/lib64/libpolkit.so.2 (0x00007f9b1533e000) libpcre.so.0 => /usr/lib64/libpcre.so.0 (0x00007f9b14b76000)
Any idea on how to fix this?
Yes, install the application umount.devkit in /usr/sbin .. if that does not cover the required usecase, fill an enhacement request on bugzilla requesting some libraries to be moved to /%{_lib} . at least libpcre and libglib-2.0 should be moved there for other reasons, (i.e to link grep dynamically or not using static libglib-2.0 in syslog-ng...) but that is still not implemented. If you fill such request, please add me to the CC list. -- "If this is the best God can do, I am not impressed" -George Carlin (1937-2008) Cristian Rodríguez R. Software Developer Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
On Sun, 2009-05-10 at 01:39 -0400, Cristian Rodríguez wrote:
Magnus Boman escribió:
Hello,
I'm trying to build DeviceKit-disks [1] but get the following error;
binary /sbin/umount.devkit is linked against libraries in /usr or /opt libdbus-glib-1.so.2 => /usr/lib64/libdbus-glib-1.so.2 (0x00007f9b15c73000) libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f9b15a2c000) libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f9b15765000) libpolkit-dbus.so.2 => /usr/lib64/libpolkit-dbus.so.2 (0x00007f9b15558000) libpolkit.so.2 => /usr/lib64/libpolkit.so.2 (0x00007f9b1533e000) libpcre.so.0 => /usr/lib64/libpcre.so.0 (0x00007f9b14b76000)
Any idea on how to fix this?
Yes, install the application umount.devkit in /usr/sbin .. if that does not cover the required usecase, fill an enhacement request on bugzilla requesting some libraries to be moved to /%{_lib} . at least libpcre and libglib-2.0 should be moved there for other reasons, (i.e to link grep dynamically or not using static libglib-2.0 in syslog-ng...) but that is still not implemented.
Ok, thanks to both yourself and cyberorg. Works after I moved it.
If you fill such request, please add me to the CC list.
I probably wont file a bug report since I don't know the history behind this. Cheers, Magnus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi, Am Sonntag, 10. Mai 2009 07:39:36 schrieb Cristian Rodríguez:
Magnus Boman escribió:
Hello,
I'm trying to build DeviceKit-disks [1] but get the following error;
binary /sbin/umount.devkit is linked against libraries in /usr or /opt libdbus-glib-1.so.2 => /usr/lib64/libdbus-glib-1.so.2 (0x00007f9b15c73000) libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f9b15a2c000) libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f9b15765000) libpolkit-dbus.so.2 => /usr/lib64/libpolkit-dbus.so.2 (0x00007f9b15558000) libpolkit.so.2 => /usr/lib64/libpolkit.so.2 (0x00007f9b1533e000) libpcre.so.0 => /usr/lib64/libpcre.so.0 (0x00007f9b14b76000)
Any idea on how to fix this?
Yes, install the application umount.devkit in /usr/sbin ..
If you do this, the [u]mount command will not detect this helper script. So umount -t devkit ... will not work [u]mount only searches in /sbin for such helper scripts.
if that does not cover the required usecase, fill an enhacement request on bugzilla requesting some libraries to be moved to /%{_lib} .
This would be a solution but the result might be, that someday we have nearly all libs in /lib .
at least libpcre and libglib-2.0 should be moved there for other reasons, (i.e to link grep dynamically or not using static libglib-2.0 in syslog-ng...) but that is still not implemented.
If you fill such request, please add me to the CC list.
Aother solution might be to install the script to /usr/sbin/ and write a wrapper script, which call /usr/sbin/umount.,devkit if it is available or patch the mount command to search also in /usr/sbin/ -- MFG Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Michael Calmer wrote:
Aother solution might be to install the script to /usr/sbin/ and write a wrapper script, which call /usr/sbin/umount.,devkit if it is available or patch the mount command to search also in /usr/sbin/
Is there a reason why not to search also /usr/sbin ? -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o Package Maintainer Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Mon, May 11, 2009 at 1:40 PM, Michael Calmer <mc@suse.de> wrote:
Yes, install the application umount.devkit in /usr/sbin ..
If you do this, the [u]mount command will not detect this helper script. So
umount -t devkit ... will not work
[u]mount only searches in /sbin for such helper scripts.
So install in /usr/sbin and symlink in /sbin? Cheers -J -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi, Am Montag, 11. Mai 2009 10:27:03 schrieb CyberOrg:
On Mon, May 11, 2009 at 1:40 PM, Michael Calmer <mc@suse.de> wrote:
Yes, install the application umount.devkit in /usr/sbin ..
If you do this, the [u]mount command will not detect this helper script. So
umount -t devkit ... will not work
[u]mount only searches in /sbin for such helper scripts.
So install in /usr/sbin and symlink in /sbin?
Uh, don't do this. If /usr is not mounted at the time when this helper is called, you have a dead link. -- MFG Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Am Montag, 11. Mai 2009 10:27:03 schrieb CyberOrg:
On Mon, May 11, 2009 at 1:40 PM, Michael Calmer <mc@suse.de> wrote:
Yes, install the application umount.devkit in /usr/sbin ..
If you do this, the [u]mount command will not detect this helper script. So
umount -t devkit ... will not work
[u]mount only searches in /sbin for such helper scripts.
So install in /usr/sbin and symlink in /sbin?
symlink in /sbin would contradict the check. It is there because binaries in /bin and /sbin must not use anything in /usr, because this might not be available at that point of time. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Montag 11 Mai 2009 schrieb Adrian Schröter:
Am Montag, 11. Mai 2009 10:27:03 schrieb CyberOrg:
On Mon, May 11, 2009 at 1:40 PM, Michael Calmer <mc@suse.de> wrote:
Yes, install the application umount.devkit in /usr/sbin ..
If you do this, the [u]mount command will not detect this helper script. So
umount -t devkit ... will not work
[u]mount only searches in /sbin for such helper scripts.
So install in /usr/sbin and symlink in /sbin?
symlink in /sbin would contradict the check. It is there because binaries in /bin and /sbin must not use anything in /usr, because this might not be available at that point of time.
"at that point of time" needs explanation I guess: /usr is possibly mounted later in the boot process, most prominently from a network share. So if devkit is the possible host of a /usr filesystem, all its requirements need to be out of /usr. This doesn't seem to be the case here though. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Mon, 2009-05-11 at 14:48 +0200, Stephan Kulow wrote:
Am Montag 11 Mai 2009 schrieb Adrian Schröter:
Am Montag, 11. Mai 2009 10:27:03 schrieb CyberOrg:
On Mon, May 11, 2009 at 1:40 PM, Michael Calmer <mc@suse.de> wrote:
Yes, install the application umount.devkit in /usr/sbin ..
If you do this, the [u]mount command will not detect this helper script. So
umount -t devkit ... will not work
[u]mount only searches in /sbin for such helper scripts.
So install in /usr/sbin and symlink in /sbin?
symlink in /sbin would contradict the check. It is there because binaries in /bin and /sbin must not use anything in /usr, because this might not be available at that point of time.
"at that point of time" needs explanation I guess: /usr is possibly mounted later in the boot process, most prominently from a network share. So if devkit is the possible host of a /usr filesystem, all its requirements need to be out of /usr. This doesn't seem to be the case here though.
But this is only the umount command, so it wouldn't be affected by startup. Also, if I change it back to /sbin, and then change; --libexecdir=%{_prefix}/lib/DeviceKit-disks to be; --libexecdir=%{_lib}/DeviceKit-disks ...as well? Would that be enough for it to be officially blessed? Or I am not even allowed to use "%{_datadir}" for the package and need to change that as well? Cheers, Magnus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Le jeudi 14 mai 2009, à 13:17 +1000, Magnus Boman a écrit :
Also, if I change it back to /sbin, and then change; --libexecdir=%{_prefix}/lib/DeviceKit-disks to be; --libexecdir=%{_lib}/DeviceKit-disks
On which libraries do all this depend? Wasn't there glib, policykit, etc? Those ones still live in /usr, so it wouldn't work if they are needed.Wasn't there glib, policykit, etc? Those ones still live in /usr, so it wouldn't work if they are needed.
...as well? Would that be enough for it to be officially blessed? Or I am not even allowed to use "%{_datadir}" for the package and need to change that as well?
Does this binary need the data in %{_datadir}? :-) Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Michael Calmer escribió:
This would be a solution but the result might be, that someday we have nearly all libs in /lib .
if we move a lot more of stuff to /sbin or /bin yes, otherwise I fail to see why that would happen.
Aother solution might be to install the script to /usr/sbin/ and write a wrapper script, which call /usr/sbin/umount.,devkit if it is available or patch the mount command to search also in /usr/sbin/
Wont work either. If this is an official opensuse package and needs to be in /sbin to implement a feature, please fill a bug. -- "If this is the best God can do, I am not impressed" -George Carlin (1937-2008) Cristian Rodríguez R. Software Developer Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
participants (8)
-
Adrian Schröter -
Cristian Rodríguez -
CyberOrg -
Magnus Boman -
Michael Calmer -
Pavol Rusnak -
Stephan Kulow -
Vincent Untz