Re: [X2Go-User] Fwd: x2go ppa broken for upgrade to 4.1.0.4
Am 01.06.23 um 16:05 schrieb Buddy Butterfly: But lets talk about the root cause. In the Repo you can see in Packages.gz, that x2goserver-x2gokdrive depends on xserver-x2gokdrive and that package is just not listed in Packages.gz: http://ppa.launchpad.net/x2go/stable/ubuntu/dists/focal/main/binary-arm64/Packages.xz Yes, because that package doesn't exist yet, it still needs to be built. So the Packages.gz file is not wrong - it reflects the current state of the PPA. The fix is not to manually edit the Packages file, but to build the missing packages. Patience, young grasshopper ... ;) Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Fwd: x2go ppa broken for upgrade to 4.1.0.4
sry, I meant, it is a convenience wrapper for apt-get and apt-cache... But lets talk about the root cause. In the Repo you can see in Packages.gz, that x2goserver-x2gokdrive depends on xserver-x2gokdrive and that package is just not listed in Packages.gz: http://ppa.launchpad.net/x2go/stable/ubuntu/dists/focal/main/binary-arm64/Packages.xz Cheers, Matt Am 01.06.23 um 15:58 schrieb Buddy Butterfly: Hi Stefan, never mind. apt is just a wrapper around apt-get and aptitude for convenience. So all holds true, one or the other way. Cheers, Matt Am 01.06.23 um 15:56 schrieb Stefan Baur: Am 01.06.23 um 15:40 schrieb Buddy Butterfly: Hi Stefan, yes, you can trust me, that I always have a "clear" apt installation with apt update apt dist-upgrade And here's the issue. a) You should not run "apt dist-upgrade". Never. "dist-upgrade" is not officially supported by "apt". (It is supported with "apt-get", as far as I know.) b) The proper command to use instead is "apt full-upgrade", but ... c) You should always run "apt upgrade" before attempting a more invasive command like "apt full-upgrade". d) You should not use "-y" or a script containing the commands you listed, unless you are willing to risk breakage AND have a proper backup. e) Read, Understand, and Think before you approve an update, especially if it indicates package removals (which an "apt upgrade" will never do, unlike an "apt full-upgrade"). apt autoremove --purge apt autoclean apt clean This is how I usually run manual updates on machines, usually within a "screen" session when I'm logged in remotely, so a natwork issue won't interrupt any dpkg-configure calls: apt update apt full-upgrade -d -y # see explanation below apt upgrade apt full-upgrade # optional step apt autoremove --purge apt clean # Explanation: I want all packages to be available locally before # starting the upgrade, so that any transient network failures won't # matter. It'll either fail at the download stage already, which won't # break anything, or it will be able to access all packages even if # the network fails inbetween. Again, if any of these commands throw a warning/an error, do not blindly continue. IF, AND ONLY IF YOU HAVE A BACKUP THAT YOU HAVE VERIFIED TO BE WORKING: apt update && apt full-upgrade -d -y && \ apt upgrade -y && apt full-upgrade -y && \ apt autoremove --purge && apt clean In your case, apt upgrade should have shown that it has some packages it cannot upgrade due to unresolved dependencies, but should have continued to work. The mess only starts after using dist-upgrade/full-upgrade, because with that, you are actually authorizing uninstalls. It is basically "Yes, do as I say!"'s little brother. Kind Regards, Stefan Baur ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Fwd: x2go ppa broken for upgrade to 4.1.0.4
Hi Stefan, never mind. apt is just a wrapper around apt-get and aptitude for convenience. So all holds true, one or the other way. Cheers, Matt Am 01.06.23 um 15:56 schrieb Stefan Baur: Am 01.06.23 um 15:40 schrieb Buddy Butterfly: Hi Stefan, yes, you can trust me, that I always have a "clear" apt installation with apt update apt dist-upgrade And here's the issue. a) You should not run "apt dist-upgrade". Never. "dist-upgrade" is not officially supported by "apt". (It is supported with "apt-get", as far as I know.) b) The proper command to use instead is "apt full-upgrade", but ... c) You should always run "apt upgrade" before attempting a more invasive command like "apt full-upgrade". d) You should not use "-y" or a script containing the commands you listed, unless you are willing to risk breakage AND have a proper backup. e) Read, Understand, and Think before you approve an update, especially if it indicates package removals (which an "apt upgrade" will never do, unlike an "apt full-upgrade"). apt autoremove --purge apt autoclean apt clean This is how I usually run manual updates on machines, usually within a "screen" session when I'm logged in remotely, so a natwork issue won't interrupt any dpkg-configure calls: apt update apt full-upgrade -d -y # see explanation below apt upgrade apt full-upgrade # optional step apt autoremove --purge apt clean # Explanation: I want all packages to be available locally before # starting the upgrade, so that any transient network failures won't # matter. It'll either fail at the download stage already, which won't # break anything, or it will be able to access all packages even if # the network fails inbetween. Again, if any of these commands throw a warning/an error, do not blindly continue. IF, AND ONLY IF YOU HAVE A BACKUP THAT YOU HAVE VERIFIED TO BE WORKING: apt update && apt full-upgrade -d -y && \ apt upgrade -y && apt full-upgrade -y && \ apt autoremove --purge && apt clean In your case, apt upgrade should have shown that it has some packages it cannot upgrade due to unresolved dependencies, but should have continued to work. The mess only starts after using dist-upgrade/full-upgrade, because with that, you are actually authorizing uninstalls. It is basically "Yes, do as I say!"'s little brother. Kind Regards, Stefan Baur ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Fwd: x2go ppa broken for upgrade to 4.1.0.4
Am 01.06.23 um 15:40 schrieb Buddy Butterfly: Hi Stefan, yes, you can trust me, that I always have a "clear" apt installation with apt update apt dist-upgrade And here's the issue. a) You should not run "apt dist-upgrade". Never. "dist-upgrade" is not officially supported by "apt". (It is supported with "apt-get", as far as I know.) b) The proper command to use instead is "apt full-upgrade", but ... c) You should always run "apt upgrade" before attempting a more invasive command like "apt full-upgrade". d) You should not use "-y" or a script containing the commands you listed, unless you are willing to risk breakage AND have a proper backup. e) Read, Understand, and Think before you approve an update, especially if it indicates package removals (which an "apt upgrade" will never do, unlike an "apt full-upgrade"). apt autoremove --purge apt autoclean apt clean This is how I usually run manual updates on machines, usually within a "screen" session when I'm logged in remotely, so a natwork issue won't interrupt any dpkg-configure calls: apt update apt full-upgrade -d -y # see explanation below apt upgrade apt full-upgrade # optional step apt autoremove --purge apt clean # Explanation: I want all packages to be available locally before # starting the upgrade, so that any transient network failures won't # matter. It'll either fail at the download stage already, which won't # break anything, or it will be able to access all packages even if # the network fails inbetween. Again, if any of these commands throw a warning/an error, do not blindly continue. IF, AND ONLY IF YOU HAVE A BACKUP THAT YOU HAVE VERIFIED TO BE WORKING: apt update && apt full-upgrade -d -y && \ apt upgrade -y && apt full-upgrade -y && \ apt autoremove --purge && apt clean In your case, apt upgrade should have shown that it has some packages it cannot upgrade due to unresolved dependencies, but should have continued to work. The mess only starts after using dist-upgrade/full-upgrade, because with that, you are actually authorizing uninstalls. It is basically "Yes, do as I say!"'s little brother. Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Fwd: x2go ppa broken for upgrade to 4.1.0.4
Hi Stefan, yes, you can trust me, that I always have a "clear" apt installation with apt update apt dist-upgrade apt autoremove --purge apt autoclean apt clean then trying to install. But this dependency is just missing. Reverted to 4.1.0.3 for now. Put: Package: x2go* libx2go* Pin: version 4.1.0.3* Pin-Priority: 1001 into a file, for example, /etc/apt/preferences.d/pin-x2go then do the updates and installs. Awaiting the fix in the repo ;-) Cheers, Matt Am 01.06.23 um 15:35 schrieb Stefan Baur: Am 01.06.23 um 15:22 schrieb Buddy Butterfly: upgrade to version 4.1.0.4 broke x2go installations on Ubuntu trusty and focal The upgrade deployment is still in progress (see Mihai's earlier post on the list), so yes, there currently are missing packages, as they are still being built/still need to be built. and removes x2goserver when using PPA: That, however, should not happen, at least not when running apt update and apt upgrade on the command line. Things that might be helpful in debugging the issue: The output of grep -r x2go /etc/apt/sources.list* (as this will show all x2go-related repositories you are using) as well as cat /var/log/apt/history.log and, if your log rotation has already moved 2023-05-31's entries into the gzipped archive logs, zcat $(ls -1 -r /var/log/apt/history.log.?.gz) on an affected machine. The "Commandline" entries should show exactly which apt commands you ran. Kind Regards, Stefan Baur ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Fwd: x2go ppa broken for upgrade to 4.1.0.4
Am 01.06.23 um 15:22 schrieb Buddy Butterfly: upgrade to version 4.1.0.4 broke x2go installations on Ubuntu trusty and focal The upgrade deployment is still in progress (see Mihai's earlier post on the list), so yes, there currently are missing packages, as they are still being built/still need to be built. and removes x2goserver when using PPA: That, however, should not happen, at least not when running apt update and apt upgrade on the command line. Things that might be helpful in debugging the issue: The output of grep -r x2go /etc/apt/sources.list* (as this will show all x2go-related repositories you are using) as well as cat /var/log/apt/history.log and, if your log rotation has already moved 2023-05-31's entries into the gzipped archive logs, zcat $(ls -1 -r /var/log/apt/history.log.?.gz) on an affected machine. The "Commandline" entries should show exactly which apt commands you ran. Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
[X2Go-User] Fwd: x2go ppa broken for upgrade to 4.1.0.4
Hi, upgrade to version 4.1.0.4 broke x2go installations on Ubuntu trusty and focal and removes x2goserver when using PPA: x2goserver: sudo apt install x2goserver Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: x2goserver : Depends: x2goserver-x2gokdrive (< 4.1.0.4-0~1975~ubuntu20.04.1.1~) but it is not going to be installed Depends: x2goserver-x2gokdrive (>= 4.1.0.4-0~1975~ubuntu20.04.1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Then: sudo apt install x2goserver-x2gokdrive Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: x2goserver-x2gokdrive : Depends: xserver-x2gokdrive but it is not installable E: Unable to correct problems, you have held broken packages. Reason: Package xserver-x2gokdrive is missing. ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
