Summary: | nx-x11-1.5.0-r8 forgets .so symlinks | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nico Baggus <mlspamcb> |
Component: | New packages | Assignee: | Gentoo NX Server project <nx> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | fcoiffie, martin.adler, scruggsj, si |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Nico Baggus
2006-05-20 06:58:40 UTC
From a build on another system...
>>> Install nx-x11-1.5.0-r8 into /var/tmp/portage/nx-x11-1.5.0-r8/image/ category net-misc
ln: creating symbolic link `/var/tmp/portage/nx-x11-1.5.0-r8/image/usr/NX/lib/lib/X11/libX11.so' to `libX11.so.6.2': No such file or directory
ln: creating symbolic link `/var/tmp/portage/nx-x11-1.5.0-r8/image/usr/NX/lib/lib/X11/libX11.so.6' to `libX11.so.6.2': No such file or directory
ln: creating symbolic link `/var/tmp/portage/nx-x11-1.5.0-r8/image/usr/NX/lib/lib/Xext/libXext.so' to `libXext.so.6.4': No such file or directory
ln: creating symbolic link `/var/tmp/portage/nx-x11-1.5.0-r8/image/usr/NX/lib/lib/Xext/libXext.so.6' to `libXext.so.6.4': No such file or directory
ln: creating symbolic link `/var/tmp/portage/nx-x11-1.5.0-r8/image/usr/NX/lib/lib/Xrender/libXrender.so' to `libXrender.so.1.2': No such file or directory
ln: creating symbolic link `/var/tmp/portage/nx-x11-1.5.0-r8/image/usr/NX/lib/lib/Xrender/libXrender.so.1' to `libXrender.so.1.2': No such file or directory
ln: creating symbolic link `/var/tmp/portage/nx-x11-1.5.0-r8/image/usr/NX/lib/../nxcompext/libXcompext.so' to `libXcompext.so.1.5.0': No such file or directory
ln: creating symbolic link `/var/tmp/portage/nx-x11-1.5.0-r8/image/usr/NX/lib/../nxcompext/libXcompext.so.1' to `libXcompext.so.1.5.0': No such file or directory
Merging also has no mentioning of them. >>> Merging net-misc/nx-x11-1.5.0-r8 to / --- /usr/ --- /usr/NX/ --- /usr/NX/bin/ >>> /usr/NX/bin/nxagent >>> /usr/NX/bin/nxauth >>> /usr/NX/bin/nxviewer >>> /usr/NX/bin/nxpasswd >>> /usr/NX/bin/nxdesktop --- /usr/NX/lib/ >>> /usr/NX/lib/libX11.so.6.2 >>> /usr/NX/lib/libXext.so.6.4 >>> /usr/NX/lib/libXrender.so.1.2 >>> /usr/NX/lib/libXcompext.so.1.5.0 *** Bug 133878 has been marked as a duplicate of this bug. *** Can confirm this. Same senario here. *** Bug 134122 has been marked as a duplicate of this bug. *** Thanks for reporting this. I will take a look at the ebuilds and see if I can add those symlinks back in. :) Right now I am busy working on the NX 2.0.0 ebuilds. Then I will fully look at all this issue for both 1.5.0 and 2.0.0 ebuilds to make sure that the same mistake is not repeated. I will do at manual install of everything and compare the output of the ebuild install and the manual install. This will take some time though -- a few days at the least. Maybe this should be a high priority because it seems like this is a major bug. Cheers. I installed this yesterday and the symlinks are there. grundle lib # equery files nx-x11 [ Searching for packages matching nx-x11... ] * Contents of net-misc/nx-x11-1.5.0-r8: /usr /usr/NX /usr/NX/bin /usr/NX/bin/nxagent /usr/NX/bin/nxauth /usr/NX/bin/nxdesktop /usr/NX/bin/nxpasswd /usr/NX/bin/nxviewer /usr/NX/lib /usr/NX/lib/libX11.so -> libX11.so.6.2 /usr/NX/lib/libX11.so.6 -> libX11.so.6.2 /usr/NX/lib/libX11.so.6.2 /usr/NX/lib/libXcompext.so -> libXcompext.so.1.5.0 /usr/NX/lib/libXcompext.so.1 -> libXcompext.so.1.5.0 /usr/NX/lib/libXcompext.so.1.5.0 /usr/NX/lib/libXext.so -> libXext.so.6.4 /usr/NX/lib/libXext.so.6 -> libXext.so.6.4 /usr/NX/lib/libXext.so.6.4 /usr/NX/lib/libXrender.so -> libXrender.so.1.2 /usr/NX/lib/libXrender.so.1 -> libXrender.so.1.2 /usr/NX/lib/libXrender.so.1.2 The only instance I know if is where the symlinks fail like that is on amd64 machines. For those having this issue, are you using amd64 processors? If so, can you try nx-x11-bin? The new ebuilds for nx 2.0.0 will hopefully have better amd64 and xorg7 support which I intend on putting in nx 1.5.0. :D Cheers. I am using x86 and had this problem when coverting from 1.4 to 1.5 series. I have run updates on the 1.5 series since then without issue. For me this happened on x86 environments. when upgrading freenx from ancient to 1.5 Hi, I wonder if Portage is removing the symlinks when the older version is uninstalled? Re-emerging freenx should fix this problem. Best regards, Stu Not just remerging will work, first emerge --unmerge followed by an emerge will solve this... And yes it might have been a problem with portage. I can't verify anymore becaus installing the current nx version gave problems, so I unmerged the whole lot and am remerging now... |