v1.0.0: dist-upgrade fails on file conflicts (ruby-rubygems, libhashkit-dev); resume refuses after partial upgrade flips OS detection to Ubuntu 24
Ubuntu 22.04.5 → 24.04, Plesk Obsidian 18.0.79.2, tool v1.0.0. Server originally upgraded 18.04→20.04→22.04 with the corresponding Plesk tools.
Bug 1 — file conflict, ruby: dist-upgrade aborted with trying to overwrite '/usr/bin/gem', which is also in package ruby 2:2.7.0+1bbox1~focal2. A legacy Brightbox ruby package (from the focal era) survived two prior dist-upgrades; the tool didn't detect or remove it. Fixed manually with dpkg --remove --force-depends ruby ruby2.7 + apt -f install.
Bug 2 — file conflict, libhashkit: on resume, aborted again with trying to overwrite '/usr/share/man/man3/hashkit_clone.3.gz', which is also in package libhashkit2:amd64 1.0.18-4.2ubuntu4. Jammy's libmemcached family conflicts with noble's 1.1.4 split. Fixed manually by removing libhashkit2/libhashkit-dev/libmemcached11/libmemcachedutil2.
Bug 3 — resume refuses after partial upgrade: after the manual fixes, enough of noble had installed (base-files) that the tool detects "Ubuntu 24" and exits with "Your distribution is not supported yet" — even though its own finish phase never ran. The Ubuntu18to20Upgrader supports resume with as target = True; this tool apparently does not, leaving no way to complete the finishing actions via the tool. Completed manually with apt-get dist-upgrade + plesk repair installation. Reboot.
Bug 4 — --prepare-feedback gated behind the same check: the command you direct failed users to run also exits "not supported yet" in this state, so the feedback archive can't be generated exactly when it's needed.
All four suggest v1.0.0 needs (a) pre-flight file-conflict detection for known jammy→noble package splits and stale third-party packages, (b) resume support when current OS detects as the target, and (c) allowing --prepare-feedback to run regardless of detected OS.
ubuntu22to24-scrubbed.log
Feedback archive cannot be generated — --prepare-feedback exits with the same "not supported yet" error (Bug 4). Full tool log attached instead: /var/log/plesk/ubuntu22to24.log.
v1.0.0: dist-upgrade fails on file conflicts (ruby-rubygems, libhashkit-dev); resume refuses after partial upgrade flips OS detection to Ubuntu 24
Ubuntu 22.04.5 → 24.04, Plesk Obsidian 18.0.79.2, tool v1.0.0. Server originally upgraded 18.04→20.04→22.04 with the corresponding Plesk tools.
Bug 1 — file conflict, ruby: dist-upgrade aborted with trying to overwrite '/usr/bin/gem', which is also in package ruby 2:2.7.0+1bbox1~focal2. A legacy Brightbox ruby package (from the focal era) survived two prior dist-upgrades; the tool didn't detect or remove it. Fixed manually with dpkg --remove --force-depends ruby ruby2.7 + apt -f install.
Bug 2 — file conflict, libhashkit: on resume, aborted again with trying to overwrite '/usr/share/man/man3/hashkit_clone.3.gz', which is also in package libhashkit2:amd64 1.0.18-4.2ubuntu4. Jammy's libmemcached family conflicts with noble's 1.1.4 split. Fixed manually by removing libhashkit2/libhashkit-dev/libmemcached11/libmemcachedutil2.
Bug 3 — resume refuses after partial upgrade: after the manual fixes, enough of noble had installed (base-files) that the tool detects "Ubuntu 24" and exits with "Your distribution is not supported yet" — even though its own finish phase never ran. The Ubuntu18to20Upgrader supports resume with as target = True; this tool apparently does not, leaving no way to complete the finishing actions via the tool. Completed manually with apt-get dist-upgrade + plesk repair installation. Reboot.
Bug 4 — --prepare-feedback gated behind the same check: the command you direct failed users to run also exits "not supported yet" in this state, so the feedback archive can't be generated exactly when it's needed.
All four suggest v1.0.0 needs (a) pre-flight file-conflict detection for known jammy→noble package splits and stale third-party packages, (b) resume support when current OS detects as the target, and (c) allowing --prepare-feedback to run regardless of detected OS.
ubuntu22to24-scrubbed.log
Feedback archive cannot be generated — --prepare-feedback exits with the same "not supported yet" error (Bug 4). Full tool log attached instead: /var/log/plesk/ubuntu22to24.log.