Package: x2goserver Version: 4.0.1.18
i have been unable to complete the update for x2goserver here on fedora 20 (64bit). i have not changed the config files or repo files that are relevant to x2goserver since the last successful update was run.
i run yum update and receive the following output in the terminal:
yum update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile
- fedora: ftp.nluug.nl
- rpmfusion-free: mirror.nl.leaseweb.net
- rpmfusion-free-updates: mirror.nl.leaseweb.net
- updates: ftp.nluug.nl Resolving Dependencies --> Running transaction check ---> Package x2goserver.x86_64 0:4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 will be updated --> Processing Dependency: x2goserver = 4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 for package: x2goserver-extensions-4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20.x86_64 ---> Package x2goserver.x86_64 0:4.0.1.18-5.fc20 will be an update ---> Package x2goserver-xsession.x86_64 0:4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 will be updated ---> Package x2goserver-xsession.x86_64 0:4.0.1.18-5.fc20 will be an update --> Finished Dependency Resolution Error: Package: x2goserver-extensions-4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20.x86_64 (@x2go-releases) Requires: x2goserver = 4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 Removing: x2goserver-4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20.x86_64 (@x2go-releases) x2goserver = 4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 Updated By: x2goserver-4.0.1.18-5.fc20.x86_64 (updates) x2goserver = 4.0.1.18-5.fc20 Available: x2goserver-4.0.1.6-5.fc20.x86_64 (fedora) x2goserver = 4.0.1.6-5.fc20 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
expected outcome: package updates correctly.
Hi Ura & Orion,
On Wed, Jan 21, 2015 at 1:54 PM, ura <ura@ureka.org> wrote:
Package: x2goserver Version: 4.0.1.18
i have been unable to complete the update for x2goserver here on fedora 20 (64bit). i have not changed the config files or repo files that are relevant to x2goserver since the last successful update was run.
i run yum update and receive the following output in the terminal:
yum update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile
- fedora: ftp.nluug.nl
- rpmfusion-free: mirror.nl.leaseweb.net
- rpmfusion-free-updates: mirror.nl.leaseweb.net
- updates: ftp.nluug.nl Resolving Dependencies --> Running transaction check ---> Package x2goserver.x86_64 0:4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 will be updated --> Processing Dependency: x2goserver = 4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 for package: x2goserver-extensions-4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20.x86_64 ---> Package x2goserver.x86_64 0:4.0.1.18-5.fc20 will be an update ---> Package x2goserver-xsession.x86_64 0:4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 will be updated ---> Package x2goserver-xsession.x86_64 0:4.0.1.18-5.fc20 will be an update --> Finished Dependency Resolution Error: Package: x2goserver-extensions-4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20.x86_64 (@x2go-releases) Requires: x2goserver = 4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 Removing: x2goserver-4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20.x86_64 (@x2go-releases) x2goserver = 4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 Updated By: x2goserver-4.0.1.18-5.fc20.x86_64 (updates) x2goserver = 4.0.1.18-5.fc20 Available: x2goserver-4.0.1.6-5.fc20.x86_64 (fedora) x2goserver = 4.0.1.6-5.fc20 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
expected outcome: package updates correctly.
x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
The problem is based on these circumstances: packages.x2go.org. This is normal.
- You have X2Go installed from packages.x2go.org. The version string starts with: 4.0.1.18-0
- The version of x2goserver in the fedora 20 updates repo has a higher version string: 4.0.1.18-5
- You have the package x2goserver-extensions installed from
- The x2goserver packages in Fedora 20 (both the base repo and the updates repo) do not include the x2goserver-extensions package.
Orion, It looks like the files that are in the packages.x2go.org x2goserver-extensions package[1] are included in the Fedora x2goserver[2] package, correct? if so, I think Ura can solve this problem by removing x2goserver-extensions, and then running yum update.
-Mike#2
[1] http://packages.x2go.org/fedora/20/main/x86_64/rpms/x2goserver/ [2] http://koji.fedoraproject.org/koji/buildinfo?buildID=602993
On 01/24/2015 06:26 PM, Michael DePaulo wrote:
Hi Ura & Orion,
On Wed, Jan 21, 2015 at 1:54 PM, ura <ura@ureka.org> wrote:
Package: x2goserver Version: 4.0.1.18
i have been unable to complete the update for x2goserver here on fedora 20 (64bit). i have not changed the config files or repo files that are relevant to x2goserver since the last successful update was run.
i run yum update and receive the following output in the terminal:
yum update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile
- fedora: ftp.nluug.nl
- rpmfusion-free: mirror.nl.leaseweb.net
- rpmfusion-free-updates: mirror.nl.leaseweb.net
- updates: ftp.nluug.nl Resolving Dependencies --> Running transaction check ---> Package x2goserver.x86_64 0:4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 will be updated --> Processing Dependency: x2goserver = 4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 for package: x2goserver-extensions-4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20.x86_64 ---> Package x2goserver.x86_64 0:4.0.1.18-5.fc20 will be an update ---> Package x2goserver-xsession.x86_64 0:4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 will be updated ---> Package x2goserver-xsession.x86_64 0:4.0.1.18-5.fc20 will be an update --> Finished Dependency Resolution Error: Package: x2goserver-extensions-4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20.x86_64 (@x2go-releases) Requires: x2goserver = 4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 Removing: x2goserver-4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20.x86_64 (@x2go-releases) x2goserver = 4.0.1.18-0.0x2go1.1.git20141006.949.main.fc20 Updated By: x2goserver-4.0.1.18-5.fc20.x86_64 (updates) x2goserver = 4.0.1.18-5.fc20 Available: x2goserver-4.0.1.6-5.fc20.x86_64 (fedora) x2goserver = 4.0.1.6-5.fc20 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
expected outcome: package updates correctly.
x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
The problem is based on these circumstances: packages.x2go.org. This is normal.
- You have X2Go installed from packages.x2go.org. The version string starts with: 4.0.1.18-0
- The version of x2goserver in the fedora 20 updates repo has a higher version string: 4.0.1.18-5
- You have the package x2goserver-extensions installed from
- The x2goserver packages in Fedora 20 (both the base repo and the updates repo) do not include the x2goserver-extensions package.
Orion, It looks like the files that are in the packages.x2go.org x2goserver-extensions package[1] are included in the Fedora x2goserver[2] package, correct? if so, I think Ura can solve this problem by removing x2goserver-extensions, and then running yum update.
or:
yum shell
remove x2goserver-extensions upgrade run
I could probably have the Fedora x2goserver package provide x2goserver-extensions to help with such situations.
-Mike#2
[1] http://packages.x2go.org/fedora/20/main/x86_64/rpms/x2goserver/ [2] http://koji.fedoraproject.org/koji/buildinfo?buildID=602993
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane orion@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com
thanks for responding here. i just ran: yum remove x2goserver-extensions
and yum also elected to remove x2goserver, agent and xsession as dependencies. do you advise to remove all of these too?
The problem is based on these circumstances: packages.x2go.org. This is normal.
- You have X2Go installed from packages.x2go.org. The version string starts with: 4.0.1.18-0
- The version of x2goserver in the fedora 20 updates repo has a higher version string: 4.0.1.18-5
- You have the package x2goserver-extensions installed from
- The x2goserver packages in Fedora 20 (both the base repo and the updates repo) do not include the x2goserver-extensions package.
Orion, It looks like the files that are in the packages.x2go.org x2goserver-extensions package[1] are included in the Fedora x2goserver[2] package, correct? if so, I think Ura can solve this problem by removing x2goserver-extensions, and then running yum update.
or:
yum shell
remove x2goserver-extensions upgrade run
I could probably have the Fedora x2goserver package provide x2goserver-extensions to help with such situations.
-Mike#2
[1] http://packages.x2go.org/fedora/20/main/x86_64/rpms/x2goserver/ [2] http://koji.fedoraproject.org/koji/buildinfo?buildID=602993
--
*ura soul* /founder & co-creator/
web: www.ureka.org <https://www.ureka.org>
YouTube <https://www.youtube.com/user/neekos72> Twitter <https://twitter.com/ura_soul1> Facebook <https://www.facebook.com/ureka.community>
Yes, you should do so and then reinstall the x2goserver and x2goserver-xesssion packages. Doing so will reinstall the necessary dependencies (e.g., nxagent).
Of course, you should do so via a local console or command-line SSH, not via an X2Go session.
And if you have made any changes to files under /etc/x2go/, you should back them up 1st.
-Mike#2
On Sun, Jan 25, 2015 at 7:38 AM, ura <ura@ureka.org> wrote:
thanks for responding here. i just ran: yum remove x2goserver-extensions
and yum also elected to remove x2goserver, agent and xsession as dependencies. do you advise to remove all of these too?
The problem is based on these circumstances: packages.x2go.org. This is normal.
- You have X2Go installed from packages.x2go.org. The version string starts with: 4.0.1.18-0
- The version of x2goserver in the fedora 20 updates repo has a higher version string: 4.0.1.18-5
- You have the package x2goserver-extensions installed from
- The x2goserver packages in Fedora 20 (both the base repo and the updates repo) do not include the x2goserver-extensions package.
Orion, It looks like the files that are in the packages.x2go.org x2goserver-extensions package[1] are included in the Fedora x2goserver[2] package, correct? if so, I think Ura can solve this problem by removing x2goserver-extensions, and then running yum update.
or:
yum shell
remove x2goserver-extensions upgrade run
I could probably have the Fedora x2goserver package provide x2goserver-extensions to help with such situations.
-Mike#2
[1] http://packages.x2go.org/fedora/20/main/x86_64/rpms/x2goserver/ [2] http://koji.fedoraproject.org/koji/buildinfo?buildID=602993
[...]
ok, i just removed them. yum upgrade did nothing and yum run is not a valid yum directive. in any case, after re-installing the packages and running yum update, i now see no warnings in yum and the x2go client/server connection is running fine.
thanks again.
On 25/01/15 12:51, Michael DePaulo wrote:
Yes, you should do so and then reinstall the x2goserver and x2goserver-xesssion packages. Doing so will reinstall the necessary dependencies (e.g., nxagent).
Of course, you should do so via a local console or command-line SSH, not via an X2Go session.
And if you have made any changes to files under /etc/x2go/, you should back them up 1st.
-Mike#2
On Sun, Jan 25, 2015 at 7:38 AM, ura <ura@ureka.org <mailto:ura@ureka.org>> wrote:
thanks for responding here. i just ran: yum remove x2goserver-extensions and yum also elected to remove x2goserver, agent and xsession as dependencies. do you advise to remove all of these too?The problem is based on these circumstances: 1. You have X2Go installed from packages.x2go.org <http://packages.x2go.org>. The version string starts with: 4.0.1.18-0 2. The version of x2goserver in the fedora 20 updates repo has a higher version string: 4.0.1.18-5 3. You have the package x2goserver-extensions installed from packages.x2go.org <http://packages.x2go.org>. This is normal. 4. The x2goserver packages in Fedora 20 (both the base repo and the updates repo) do not include the x2goserver-extensions package. Orion, It looks like the files that are in the packages.x2go.org <http://packages.x2go.org> x2goserver-extensions package[1] are included in the Fedora x2goserver[2] package, correct? if so, I think Ura can solve this problem by removing x2goserver-extensions, and then running yum update.or: yum shell > remove x2goserver-extensions > upgrade > run I could probably have the Fedora x2goserver package provide x2goserver-extensions to help with such situations.-Mike#2 [1] http://packages.x2go.org/fedora/20/main/x86_64/rpms/x2goserver/ [2] http://koji.fedoraproject.org/koji/buildinfo?buildID=602993[...]
--
*ura soul* /founder & co-creator/
web: www.ureka.org <https://www.ureka.org>
YouTube <https://www.youtube.com/user/neekos72> Twitter <https://twitter.com/ura_soul1> Facebook <https://www.facebook.com/ureka.community>
On Sun, Jan 25, 2015 at 8:29 AM, ura <ura@ureka.org> wrote:
ok, i just removed them. yum upgrade did nothing and yum run is not a valid yum directive. in any case, after re-installing the packages and running yum update, i now see no warnings in yum and the x2go client/server connection is running fine.
thanks again.
Ura,
Great :)
On Sat, Jan 24, 2015 at 11:43 PM, Orion Poplawski <orion@cora.nwra.com> wrote:
I could probably have the Fedora x2goserver package provide x2goserver-extensions to help with such situations.
Orion,
Yes, please do so when you get a chance.
-Mike#2
On 25.01.2015 05:43 AM, Orion Poplawski wrote:
[...]
I could probably have the Fedora x2goserver package provide x2goserver-extensions to help with such situations.
Please do. For both Fedora and EPEL, if possible.
I just had to work around this in http://code.x2go.org/gitweb?p=x2gomatebindings.git;a=blobdiff;f=x2gomatebind...
Thank you very much in advance.
Mihai
On 03/18/2015 12:10 AM, Mihai Moldovan wrote:
On 25.01.2015 05:43 AM, Orion Poplawski wrote:
[...]
I could probably have the Fedora x2goserver package provide x2goserver-extensions to help with such situations.
Please do. For both Fedora and EPEL, if possible.
I just had to work around this in http://code.x2go.org/gitweb?p=x2gomatebindings.git;a=blobdiff;f=x2gomatebind...
Thank you very much in advance.
Mihai
Sure, but why even have the x2goserver-extensions sub-package? It requires x2goserver and x2goserver requires it, so you can't install one without the other.
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 http://www.nwra.com
On 18.03.2015 11:02 PM, Orion Poplawski wrote:
On 03/18/2015 12:10 AM, Mihai Moldovan wrote:
On 25.01.2015 05:43 AM, Orion Poplawski wrote:
[...]
I could probably have the Fedora x2goserver package provide x2goserver-extensions to help with such situations. Please do. For both Fedora and EPEL, if possible.
I just had to work around this in http://code.x2go.org/gitweb?p=x2gomatebindings.git;a=blobdiff;f=x2gomatebind...
Thank you very much in advance. [...] Sure, but why even have the x2goserver-extensions sub-package? It requires x2goserver and x2goserver requires it, so you can't install one without the other.
To be *perfectly honest*? I don't know, ask Mike#1.
To my understanding, it helps keeping components separated, and if we really must fix a specific component ONLY, we... could. Potentially. In theory. If the current world was completely different. Not in reality though, as we depend on x2goserver-version-release for each sub-component. This is also true for the DPKG versions.
Anyway, even though the logic behind this may be flawed because the packages really depend on each other in a circular fashion, it's somewhat "natural" to have a specific component package for each component.
We might (really) want to consider merging the packages for the 4.1.0.0 release, unless I miss some important bit of information. I don't want to do it for the old 4.0.1.x release line, unless we're going to have another LTS release based on that, as suggested by Mike#1. (Avoid flogging a dead horse and everything.)
Additionally, the same applies to x2goserver-xsession, which is currently also a separate package in Fedora and EPEL, but is depending on x2goserver and vice versa. *If* we do something like this, we do it *consistently*.
Hence, for consistency's sake, I'd prefer upstream and downstream to follow the same packaging layout.
Mihai
Hi Mihai, hi Orion,
On So 22 Mär 2015 03:12:31 CET, Mihai Moldovan wrote:
On 18.03.2015 11:02 PM, Orion Poplawski wrote:
On 03/18/2015 12:10 AM, Mihai Moldovan wrote:
On 25.01.2015 05:43 AM, Orion Poplawski wrote:
[...]
I could probably have the Fedora x2goserver package provide x2goserver-extensions to help with such situations. Please do. For both Fedora and EPEL, if possible.
I just had to work around this in http://code.x2go.org/gitweb?p=x2gomatebindings.git;a=blobdiff;f=x2gomatebind...
Thank you very much in advance. [...] Sure, but why even have the x2goserver-extensions sub-package? It requires x2goserver and x2goserver requires it, so you can't install one
without the other.To be *perfectly honest*? I don't know, ask Mike#1.
it's again related to mapping the .deb packaging to the way we package
for .rpm distros.
First, the objective was: having the same package names for both ways
of packaging, so that people can read/write docs alike for both distro
types.
Second, in .spec files, there is no such thing as a "Recommends:"
package relationship, so I used "Requires:" for what is under
"Recommends:" in the .deb way of packaging.
Third, the package x2goserver-extensions and x2goserver-xsession have
been contributed by me to X2Go. In the beginning, I wanted to make
sure to provide some extra stuff that people can add to their X2Go
Server installations. I did not want to enforce their usage on already
deployed systems.
Then... The more bugs had been reported against x2goserver-xsession,
the more I elevated the level of dependency (from nothing to Suggests:
to Recommends:).
About x2goserver-extensions: keeping it as a separate package allows
people (with a .deb based distro--it is under Recommends: IIRC) to
remove the package and disable extensions globally. But now that
several of our own X2Go components use the extension add-on package,
this has virtually become a not-to-do scenario, actually.
I hope that helps to clarify the history of those add-on packages,
that should actually by merged into the main x2goserver package. And...
o Don't forget to scan the wiki.x2go.org site for those package
names and update the passages appropriately.
o Don't forget to provide transitional dummy package that allow
smooth upgrade of systems having old versions of those packages
installed.
light+love Mike
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby 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 23.03.2015 04:35 PM, Mike Gabriel wrote:
it's again related to mapping the .deb packaging to the way we package for .rpm distros.
First, the objective was: having the same package names for both ways of packaging, so that people can read/write docs alike for both distro types.
Second, in .spec files, there is no such thing as a "Recommends:" package relationship, so I used "Requires:" for what is under "Recommends:" in the .deb way of packaging.
This is both true and false at the same time. Back then, RPM didn't have "weak dependencies", but they were "recently" added to SuSE and Fedora: https://en.opensuse.org/Libzypp/Dependencies#Weak_dependencies -- http://lists.rpm.org/pipermail/rpm-maint/2014-February/003666.html
Third, the package x2goserver-extensions and x2goserver-xsession have been contributed by me to X2Go. In the beginning, I wanted to make sure to provide some extra stuff that people can add to their X2Go Server installations. I did not want to enforce their usage on already deployed systems.
Then... The more bugs had been reported against x2goserver-xsession, the more I elevated the level of dependency (from nothing to Suggests: to Recommends:).
About x2goserver-extensions: keeping it as a separate package allows people (with a .deb based distro--it is under Recommends: IIRC)
Sorry! My fault, I have not seen that it's under "Recommends". You're right.
to remove the package and disable extensions globally. But now that several of our own X2Go components use the extension add-on package, this has virtually become a not-to-do scenario, actually.
So using x2goserver without x2goserver-extensions doesn't work anyway, as it currently stands? It's probably even "worse" for heuler (just an estimation, I didn't actually check.)
I hope that helps to clarify the history of those add-on packages, that should actually by merged into the main x2goserver package.
If that's the best course of action, I'm keeping that in mind. x2goserver-xsession could probably still stay a different package, because I don't remember any core server component making use of it, other than for desktop type session support. This said, it may still be a better idea to merge x2goserver and x2goserver-xsession, because it likely confuses users to have to install "some additional package" to get features always exposed by the clients.
And...
o Don't forget to scan the wiki.x2go.org site for those package names and update the passages appropriately. o Don't forget to provide transitional dummy package that allow smooth upgrade of systems having old versions of those packages installed.
Yep, thanks for the reminder.
I'm just adding another thought here: while weak dependencies may work for recent SUSE versions, especially SLE{S,D} 11, OpenSUSE 11 and maybe even 12 may have no support for this. OpenSUSE 11 is long since EOL, OpenSUSE 12 has been EOL'd recently, but SLE{S,D} 11 is still alive and kicking according to https://www.suse.com/lifecycle/ until end of march 20_19_ or 20_22_ (ouch...)
For Fedora/RHEL/EPEL, the "weak dependencies" situation is even worse. We cannot rely on them on these platforms.
Generally, we should regard weak dependencies as currently non-existent on RPM-based platforms. Hopefully support for that sort of thing will one day be universal...
Mihai
On 03/23/2015 09:35 AM, Mike Gabriel wrote:
Hi Mihai, hi Orion,
On So 22 Mär 2015 03:12:31 CET, Mihai Moldovan wrote:
On 18.03.2015 11:02 PM, Orion Poplawski wrote:
On 03/18/2015 12:10 AM, Mihai Moldovan wrote:
On 25.01.2015 05:43 AM, Orion Poplawski wrote:
[...]
I could probably have the Fedora x2goserver package provide x2goserver-extensions to help with such situations. Please do. For both Fedora and EPEL, if possible.
I just had to work around this in http://code.x2go.org/gitweb?p=x2gomatebindings.git;a=blobdiff;f=x2gomatebind...
Thank you very much in advance. [...] Sure, but why even have the x2goserver-extensions sub-package? It requires x2goserver and x2goserver requires it, so you can't install one without the other.
To be *perfectly honest*? I don't know, ask Mike#1.
it's again related to mapping the .deb packaging to the way we package for .rpm distros.
First, the objective was: having the same package names for both ways of packaging, so that people can read/write docs alike for both distro types.
Second, in .spec files, there is no such thing as a "Recommends:" package relationship, so I used "Requires:" for what is under "Recommends:" in the .deb way of packaging.
Third, the package x2goserver-extensions and x2goserver-xsession have been contributed by me to X2Go. In the beginning, I wanted to make sure to provide some extra stuff that people can add to their X2Go Server installations. I did not want to enforce their usage on already deployed systems.
Then... The more bugs had been reported against x2goserver-xsession, the more I elevated the level of dependency (from nothing to Suggests: to Recommends:).
About x2goserver-extensions: keeping it as a separate package allows people (with a .deb based distro--it is under Recommends: IIRC) to remove the package and disable extensions globally. But now that several of our own X2Go components use the extension add-on package, this has virtually become a not-to-do scenario, actually.
I hope that helps to clarify the history of those add-on packages, that should actually by merged into the main x2goserver package. And...
o Don't forget to scan the wiki.x2go.org site for those package names and update the passages appropriately. o Don't forget to provide transitional dummy package that allow smooth upgrade of systems having old versions of those packages installed.
light+love Mike
Thanks, Mike. I'm pretty sure I've asked this before as well. I'll try not to ask it again.
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 http://www.nwra.com
On 24.03.2015 10:40 PM, Orion Poplawski wrote:
Thanks, Mike. I'm pretty sure I've asked this before as well. I'll try not to ask it again.
But it was great to bring that up and it led to a very interesting point!
It looks like keeping the packages split up doesn't make sense with the current package interactions.
Having this on reference on the mailing list is another advantage.
Mihai
Processing control commands:
close -1 Bug #755 [x2goserver] cannot upgrade x2goServer on fedora 20 using yum Marked Bug as done archive -1 Bug #755 {Done: Stefan Baur <X2Go-ML-1@baur-itcs.de>} [x2goserver] cannot upgrade x2goServer on fedora 20 using yum archived 755 to archive/55 (from 755)
-- 755: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=755 X2Go Bug Tracking System Contact owner@bugs.x2go.org with problems
-
Michael DePaulo -
Mihai Moldovan -
Mike Gabriel -
Orion Poplawski -
ura -
X2Go Bug Tracking System