Hi Jan,
I guess, this one is yours... http://serverfault.com/questions/482596/centos-6-x2go-dependancy-issues-when...
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Wednesday 2013-02-27 16:38, Mike Gabriel wrote:
Hi Jan,
I guess, this one is yours... http://serverfault.com/questions/482596/centos-6-x2go-dependancy-issues-when...
Already fixed yesterday.
Jan Engelhardt <jengelh <at> inai.de> writes:
On Wednesday 2013-02-27 16:38, Mike Gabriel wrote:
Hi Jan,
I guess, this one is yours... http://serverfault.com/questions/482596/centos-6-x2go-dependancy-issues-when...
trying-to-run-yum-update
Already fixed yesterday.
Hello,
Any idea when the updated RPM's are being released? As currently anyone who tries to install or upgrade x2goserver on RHEL based systems will not be able to at all, making the current version of x2goserver completely broken. I personally use x2go quite a bit and cannot use it at all now because I removed the package and tried a reinstall. Another ideas is it possible to role back the release until the new RPM's are ready?
Thanks
Daniel Gibbs
On Sunday 2013-03-03 03:05, Daniel Gibbs wrote:
http://serverfault.com/questions/482596/centos-6-x2go-dependancy-issues-when...
trying-to-run-yum-update
Already fixed yesterday.
Any idea when the updated RPM's are being released?
As soon as the automatic compile and mirroring is done. Principally, it is in the order of minutes within commit.
The last change was made around 2013-03-01 20:34:09, which makes yum complete an install for x2goserver/nx-libs on F18.
Jan Engelhardt <jengelh <at> inai.de> writes:
On Sunday 2013-03-03 03:05, Daniel Gibbs wrote:
http://serverfault.com/questions/482596/centos-6-x2go-dependancy-issues-
when-
trying-to-run-yum-update
Already fixed yesterday.
Any idea when the updated RPM's are being released?
As soon as the automatic compile and mirroring is done. Principally, it is in the order of minutes within commit.
The last change was made around 2013-03-01 20:34:09, which makes yum complete an install for x2goserver/nx-libs on F18.
I can see an update in F18 and RHEL_6 i686 however nothing for RHEL_6 x86_64. So this is still an issue the nxagent and has not been updated since 21-Feb-2013. Please can this be checked and updated like the others. Thanks
On Tuesday 2013-03-05 13:14, Daniel Gibbs wrote:
Any idea when the updated RPM's are being released?
As soon as the automatic compile and mirroring is done. Principally, it is in the order of minutes within commit.
The last change was made around 2013-03-01 20:34:09, which makes yum complete an install for x2goserver/nx-libs on F18.
I can see an update in F18 and RHEL_6 i686 however nothing for RHEL_6 x86_64. So this is still an issue the nxagent and has not been updated since 21-Feb-2013. Please can this be checked and updated like the others. Thanks
Looks like the build failed there, and the culprit is a known offender: broken debuginfo scripts part of ancient rpm releases.
Jan Engelhardt <jengelh <at> inai.de> writes:
On Tuesday 2013-03-05 13:14, Daniel Gibbs wrote:
Any idea when the updated RPM's are being released?
As soon as the automatic compile and mirroring is done. Principally, it is in the order of minutes within commit.
The last change was made around 2013-03-01 20:34:09, which makes yum complete an install for x2goserver/nx-libs on F18.
I can see an update in F18 and RHEL_6 i686 however nothing for RHEL_6 x86_64.
this is still an issue the nxagent and has not been updated since 21-Feb-
Please can this be checked and updated like the others. Thanks
Looks like the build failed there, and the culprit is a known offender: broken debuginfo scripts part of ancient rpm releases.
https://build.opensuse.org/package/live_build_log?arch=x86_64&package=nx-
So 2013. libs&project=X11%3ARemoteDesktop%3Ax2go&repository=RHEL_6
I cannot believe this has still not been fixed! Do the developers of x2go realise that no one can install x2goserver on RHEL x64 and it variants currently? Its completely broken. I would of thought with an issue as serious as this that it would be a number one priority. Almost 2 weeks and it has yet to be fixed. This bug makes this really good project look bad. Does anyone know if this is even being dealt with? If its going to take time to fix then maybe a post on your front page making people aware the developers are sorting it out. Thanks
Am 10.03.2013 21:28, Daniel Gibbs schrieb:
I cannot believe this has still not been fixed! Nor can I - I'll take care of this immediately.
Do the developers of x2go realise that no one can install x2goserver on RHEL x64 and it variants currently?
Yes of course. All of us are using RHEL - it's one of the most used distros after all. I have no idea how this could happen.
Its completely broken.
Yea, totally! I so sorry.
I would of thought with an issue as serious as this that it would be a number one priority.
Of course it is! Some devs are even spending there spare time to fix this!
Almost 2 weeks and it has yet to be fixed.
This is open source! And it's for free. This should really be fixed so much quicker the bugs in commercial software!
This bug makes this really good project look bad.
I'm sure all the core devs feel really bad and can't sleep all night, just like me.
Does anyone know if this is even being dealt with?
Yes I do.
If its going to take time to fix then maybe a post on your front page making people aware the developers are sorting it out.
I'll put it on the starting page immediately!
Now serious: You get x2go for free (and if you ever even considered reading the license you'd know that there is not any warranty that it works at all)! And as far as _I_ know ,you did not pay a single cent or contributed to its development. If you want to have this fixed you are fee provide a patch or pay Mike or Alex to fix it. Until then I think you should seriously consider your tone.
Morty
On Sunday 2013-03-10 22:35, Moritz Strübe wrote:
Am 10.03.2013 21:28, Daniel Gibbs schrieb:
I cannot believe this has still not been fixed! Do the developers of x2go realise that no one can install x2goserver on RHEL x64 and it variants currently?
Yes of course. All of us are using RHEL - it's one of the most used distros after all. I have no idea how this could happen.
Most used does not necessarily mean most developed for. I rely on user submissions, because I do not run RHEL. (N.B. I am not an x2go developer either.)
RHEL is an old system, but more than that, it is also a system that lacks a lot of components that x2go requires. These two issues require additional time to what is needed to produce packages for contemporary distributions.
Almost 2 weeks and it has yet to be fixed.
This is open source! And it's for free. This should really be fixed so much quicker the bugs in commercial software!
It is open, and it is libre. But it is not necessarily gratis. Developers and contributors have to invest time, some do it exclusively using their spare time. If they do not, so be it. You cannot dictate what they are to do in their free time.
Hi Daniel,
On So 10 Mär 2013 21:28:46 CET Daniel Gibbs wrote:
[...] [...]
Looks like the build failed there, and the culprit is a known offender: broken debuginfo scripts part of ancient rpm releases.
https://build.opensuse.org/package/live_build_log?arch=x86_64&package=nx- libs&project=X11%3ARemoteDesktop%3Ax2go&repository=RHEL_6
I cannot believe this has still not been fixed! Do the developers of x2go realise that no one can install x2goserver on RHEL x64 and it variants currently? Its completely broken. I would of thought with an issue as serious as
this that it would be a number one priority. Almost 2 weeks and it has yet to be
fixed. This bug makes this really good project look bad. Does anyone know if this is
even being dealt with? If its going to take time to fix then maybe a post on your front page making people aware the developers are sorting it out. Thanks
May I suggest something?
From what I have read in this thread, the problem is:
o you want X2Go installable on RHEL o the only person doing the RPMs does not have a machine with RHEL to test his packages on
@Jan: would it make sense that Daniel provided you with a login on a
RHEL machine? Whould that help?
If so, can the two of you please get together?
@Daniel: some background info.
Unfortunately, the people coding X2Go (Alex, me, Heinz, Morty,
Reinhard, Arw, ...) tend to run on Debian (or Ubuntu) monoculture
sites, only. I personally changed over to .deb packaged distros more
than 10 years ago. On the other hand I have just become Debian
Developer, so that is the packaging style I focus on.
Thanks to Jan and his employer (who pays for it) we have RPM packages
for concurrent RPM-based distros. Note that Jan at the time of writing
rather is on the periphery of the project, simply providing the RPMs
and (very good) patches. The packaging is not so much an upstream
issue, as you might guess.
So, actually you are absolutely free (as an alternative) to package
for RHEL yourself and provide a download URL on our website. That is
one realm of possibilities. Another surely is to arrange with Jan to
cooperate on the RPM pacakges.
I understand that you want X2Go to be spread around the global and
also make it available on business Linux distros (like RHEL). Thanks
for that disposition and maybe there is a niche for you to help out in
our project.
light+love, Mike
--
DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Mike Gabriel <mike.gabriel <at> das-netzwerkteam.de> writes:
Hi Daniel,
On So 10 Mär 2013 21:28:46 CET Daniel Gibbs wrote:
[...] [...]
Looks like the build failed there, and the culprit is a known offender: broken debuginfo scripts part of ancient rpm releases.
https://build.opensuse.org/package/live_build_log?arch=x86_64&package=nx- libs&project=X11%3ARemoteDesktop%3Ax2go&repository=RHEL_6
I cannot believe this has still not been fixed! Do the developers of x2go realise that no one can install x2goserver on RHEL x64 and it variants currently?
Its
completely broken. I would of thought with an issue as serious as
this that it would be a number one priority. Almost 2 weeks and it has yet to be
fixed. This bug makes this really good project look bad. Does anyone know if this is
even being dealt with? If its going to take time to fix then maybe a post on your front page making people aware the developers are sorting it out. ThanksMay I suggest something?
From what I have read in this thread, the problem is:
o you want X2Go installable on RHEL o the only person doing the RPMs does not have a machine with RHEL to test his packages on
@Jan: would it make sense that Daniel provided you with a login on a
RHEL machine? Whould that help?If so, can the two of you please get together?
@Daniel: some background info.
Unfortunately, the people coding X2Go (Alex, me, Heinz, Morty,
Reinhard, Arw, ...) tend to run on Debian (or Ubuntu) monoculture
sites, only. I personally changed over to .deb packaged distros more
than 10 years ago. On the other hand I have just become Debian
Developer, so that is the packaging style I focus on.Thanks to Jan and his employer (who pays for it) we have RPM packages
for concurrent RPM-based distros. Note that Jan at the time of writing
rather is on the periphery of the project, simply providing the RPMs
and (very good) patches. The packaging is not so much an upstream
issue, as you might guess.So, actually you are absolutely free (as an alternative) to package
for RHEL yourself and provide a download URL on our website. That is
one realm of possibilities. Another surely is to arrange with Jan to
cooperate on the RPM pacakges.I understand that you want X2Go to be spread around the global and
also make it available on business Linux distros (like RHEL). Thanks
for that disposition and maybe there is a niche for you to help out in
our project.light+love, Mike
Thank you for the info Mike it is much appreciated. It has given me a good understanding on to how you guys work with the different distros. Also sorry if I caused upset. I am happy to help Jan out if he requires my help. I do not have RHEL but do have a CentOS server which is binary compatible so testing on that would work well.
My current understanding of the issue is as follows.
nxagent-3.5.0.17-3.1.x86_64 is asking for a dependency that is only available on OpenSuse which is xorg-x11-fonts-core. I believe this issue was resolved however when the rpm's attempted to be built it failed for some reason. Because of this the rpm's in the repo for RHEL_6 have not updated.
I believe this is the current error:
[ 669s] RPM build errors: [ 669s] Bad exit status from /var/tmp/rpm-tmp.tWnA7V (%install)
I have tried to install other version of nxagent from fedora 17 and 18 just in case this would work with no success.
I am not sure if me giving Jan access to a server would help in this case. But I am happy to do this if it would help. A recommendation for Jan if he doesn't have any access to an RHEL system might be to use something like Virtualbox and create a CentOS Virtual Machine. This will make it very easy to test x2go on RHEL based systems.
@Jan Please feel free to email me if I can be of any assistance. Thank you
On Tuesday 2013-03-12 19:31, Daniel Gibbs wrote:
I am happy to help Jan out if he requires my help.
I do have RHish VMs, but that does not help the motivation :)
My current understanding of the issue is as follows.
nxagent-3.5.0.17-3.1.x86_64 is asking for a dependency that is only available on OpenSuse which is xorg-x11-fonts-core. I believe this issue was resolved
Was indeed resolved.
however when the rpm's attempted to be built it failed for some reason. Because of this the rpm's in the repo for RHEL_6 have not updated.
I believe this is the current error: [ 669s] RPM build errors: [ 669s] Bad exit status from /var/tmp/rpm-tmp.tWnA7V (%install)
The error is
[ 122s] Processing files: libNX_FS6-3.5.0.17-0 [ 122s] error: File not found by glob: /var/tmp/nx-libs-3.5.0.17-build/usr/lib64/nx/libNX_FS.so.6* [ 122s] Processing files: libNX_FS-devel-3.5.0.17-0 [ 122s] error: File not found: /var/tmp/nx-libs-3.5.0.17-build/usr/lib64/nx/libNX_FS.so [ 122s] Processing files: libNX_ICE6-3.5.0.17-0 [ 122s] error: File not found by glob: /var/tmp/nx-libs-3.5.0.17-build/usr/lib64/nx/libNX_ICE.so.6*
This is because some files were not properly installed, and that in turn is because of some yet undiscovered problem in nx-libs's Makefiles that only triggers on older systems. I have found some problems that exist between bash-3.x and bash-4.x (that's where RH6 differs from F18), but apparently not all.
On Wednesday 2013-03-13 15:17, Jan Engelhardt wrote:
I believe this is the current error: [ 669s] RPM build errors: [ 669s] Bad exit status from /var/tmp/rpm-tmp.tWnA7V (%install)
After enabling some trace in shell..
/* [1] /usr/lib/rpm/find-debuginfo.sh::206 */
So RHEL6's rpmbuild is broken. Good luck getting that fixed.
Jan Engelhardt <jengelh <at> inai.de> writes:
On Wednesday 2013-02-27 16:38, Mike Gabriel wrote:
Hi Jan,
I guess, this one is yours... http://serverfault.com/questions/482596/centos-6-x2go-dependancy-issues-when...
yum-update
Already fixed yesterday.
Fixed how? I still have this issue on Scientific Linux 6 . Tried to submit a bug but was not added to the mailing list or something.
On Wednesday 2013-03-06 20:30, Vincent wrote:
Jan Engelhardt <jengelh <at> inai.de> writes:
On Wednesday 2013-02-27 16:38, Mike Gabriel wrote:
Hi Jan,
I guess, this one is yours... http://serverfault.com/questions/482596/centos-6-x2go-dependancy-issues-when...
yum-update
Already fixed yesterday.
Fixed how? I still have this issue on Scientific Linux 6 .
For example, in rpm lingo, nxagent.rpm requires "libXcomp.so.3()(64bit)". Both nx.rpm as well as x2go's libXcomp3.rpm would provide it. Therefore, in the eyes of rpm, both were suitable for installation, and the two would compete.
This was fixed by adding a primitive set of versioned symbols to the libraries, such that nxagent.rpm requires "libXcomp.so.3(X2GO)(64bit)" which only libXcomp3 can satisfy, not nx.
Jan Engelhardt <jengelh <at> inai.de> writes:
On Wednesday 2013-02-27 16:38, Mike Gabriel wrote:
Hi Jan,
I guess, this one is yours... http://serverfault.com/questions/482596/centos-6-x2go-
dependancy-issues-when-trying-to-run- yum-update
Already fixed yesterday.
can anyone force that build? I can't use X2Go now :(. Still volunteering for testing build before release, it's an unnecessairy bug imho