Greetings,
Upgrading F38 on my Dell XPS 13 laptop of something like 2012 vintage w a 1TB SSD, the scriplet/upgrade to setroubleshoot-server is hanging.
Seems that it's been this way for a least 5-10 minutes while everything before this has been running briskly.
Advice?
Max Pyziur pyz@brama.com
On Tue, 25 Apr 2023, Max Pyziur wrote:
Greetings,
Upgrading F38 on my Dell XPS 13 laptop of something like 2012 vintage w a 1TB SSD, the scriplet/upgrade to setroubleshoot-server is hanging.
Seems that it's been this way for a least 5-10 minutes while everything before this has been running briskly.
Advice?
My upgrade halted. The computer shutdown.
I hit the start button,
the selection for kernels came up only showing F37 kernels.
I hit the latest F37 kernel,
I got a login screen with the new F38 screen.
I logged in. Browser tabs are restored. Wifi connection, though, goes on and off.
I checked Postgresql installation; I have two version postgresql-14 (F37) and postgresql-15.
As best I can tell, the upgrade aborted leaving the system in, uh, challenged state.
Any advice on how to proceed here would be greatly appreciated.
I upgraded my desktop to F38 w no recollection of anything hanging like setroubleshoot-server, and am working from there.
Max
Max Pyziur pyz@brama.com _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Tue, 25 Apr 2023 16:10:06 -0400 (EDT) Max Pyziur pyz@brama.com wrote:
On Tue, 25 Apr 2023, Max Pyziur wrote:
Greetings,
Upgrading F38 on my Dell XPS 13 laptop of something like 2012 vintage w a 1TB SSD, the scriplet/upgrade to setroubleshoot-server is hanging.
Seems that it's been this way for a least 5-10 minutes while everything before this has been running briskly.
Advice?
My upgrade halted. The computer shutdown.
I hit the start button,
the selection for kernels came up only showing F37 kernels.
I hit the latest F37 kernel,
I got a login screen with the new F38 screen.
I logged in. Browser tabs are restored. Wifi connection, though, goes on and off.
I checked Postgresql installation; I have two version postgresql-14 (F37) and postgresql-15.
As best I can tell, the upgrade aborted leaving the system in, uh, challenged state.
Any advice on how to proceed here would be greatly appreciated.
Did the fedora packages for f38 get installed? fedora-release* fedora-repos* If they did, you can try a distro-sync using dnf Distro-Sync Command Command: distro-sync Aliases: dsync Deprecated aliases: distrosync, distribution-synchronization
dnf distro-sync [<package-spec>...] As necessary upgrades, downgrades or keeps selected installed packages to match the latest version available from any enabled repository. If no package is given, all installed packages are considered.
If it didn't, try restarting the sytem-upgrade process. How resource constrained is the laptop for memory. I vaguely recall the minimum required bumped to 2 GB because lower was causing problems. There was a discussion of minimum hardware requirements increasing, but I don't think it went through.
If it still has problems, try manually downloading the fedora packages from koji https://koji.fedoraproject.org/koji/packageinfo?packageID=9 https://koji.fedoraproject.org/koji/packageinfo?packageID=18771 and installing them with dnf -C And then run manual dnf updates for only part of the install packages, so that things are done in smaller batches than the full upgrade. At the end, you could run distro-sync.
On Tue, 25 Apr 2023, stan via users wrote:
On Tue, 25 Apr 2023 16:10:06 -0400 (EDT) Max Pyziur pyz@brama.com wrote:
On Tue, 25 Apr 2023, Max Pyziur wrote:
Greetings,
Upgrading F38 on my Dell XPS 13 laptop of something like 2012 vintage w a 1TB SSD, the scriplet/upgrade to setroubleshoot-server is hanging.
Seems that it's been this way for a least 5-10 minutes while everything before this has been running briskly.
Advice?
My upgrade halted. The computer shutdown.
I hit the start button,
the selection for kernels came up only showing F37 kernels.
I hit the latest F37 kernel,
I got a login screen with the new F38 screen.
I logged in. Browser tabs are restored. Wifi connection, though, goes on and off.
I checked Postgresql installation; I have two version postgresql-14 (F37) and postgresql-15.
As best I can tell, the upgrade aborted leaving the system in, uh, challenged state.
Any advice on how to proceed here would be greatly appreciated.
Did the fedora packages for f38 get installed? fedora-release* fedora-repos*
Thank you for your quick reply.
Using rpm -qa | grep -i fc38 | wc -l
I see that 4842 packages have been installed.
I watched the screen as it upgraded, and the package count was somewhere around 4842 when the scriplet to upgrade setroubleshoot-server started. (That's where the process hung).
Before you replied, I removed setroubleshoot-server from the laptop (dnf remove ...) and its related dependencies.
I then did dnf upgrade --refresh
and then dnf system-upgrade download --releasever=38 --allowerasing
I received the message: Error: Problem: The operation would result in removing the following protected packages: NetworkManager, dnf, grub2-tools-minimal, sudo, systemd, systemd-udev (try to add '--skip-broken' to skip uninstallable packages)
and then dnf system-upgrade download --releasever=38 --allowerasing --skip-broken
which produced the following error message
Error: Problem: The operation would result in removing the following protected packages: NetworkManager, dnf, grub2-tools-minimal, sudo, systemd, systemd-udev
I'm looking at your recommendations and now wondering how to proceed given that it seems I have probably about 4800+ packages that are both fc38 and fc37.
Any advice here would be great before I proceed to try something else.
Much thanks again.
Max
If they did, you can try a distro-sync using dnf Distro-Sync Command Command: distro-sync Aliases: dsync Deprecated aliases: distrosync, distribution-synchronization
dnf distro-sync [<package-spec>...] As necessary upgrades, downgrades or keeps selected installed packages to match the latest version available from any enabled repository. If no package is given, all installed packages are considered.If it didn't, try restarting the sytem-upgrade process. How resource constrained is the laptop for memory. I vaguely recall the minimum required bumped to 2 GB because lower was causing problems. There was a discussion of minimum hardware requirements increasing, but I don't think it went through.
If it still has problems, try manually downloading the fedora packages from koji https://koji.fedoraproject.org/koji/packageinfo?packageID=9 https://koji.fedoraproject.org/koji/packageinfo?packageID=18771 and installing them with dnf -C And then run manual dnf updates for only part of the install packages, so that things are done in smaller batches than the full upgrade. At the end, you could run distro-sync. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 4/25/23 13:38, Max Pyziur wrote:
On Tue, 25 Apr 2023, stan via users wrote:
On Tue, 25 Apr 2023 16:10:06 -0400 (EDT) Max Pyziur pyz@brama.com wrote:
On Tue, 25 Apr 2023, Max Pyziur wrote:
Greetings,
Upgrading F38 on my Dell XPS 13 laptop of something like 2012 vintage w a 1TB SSD, the scriplet/upgrade to setroubleshoot-server is hanging.
Seems that it's been this way for a least 5-10 minutes while everything before this has been running briskly.
Advice?
My upgrade halted. The computer shutdown.
I hit the start button,
the selection for kernels came up only showing F37 kernels.
I hit the latest F37 kernel,
I got a login screen with the new F38 screen.
I logged in. Browser tabs are restored. Wifi connection, though, goes on and off.
I checked Postgresql installation; I have two version postgresql-14 (F37) and postgresql-15.
As best I can tell, the upgrade aborted leaving the system in, uh, challenged state.
Any advice on how to proceed here would be greatly appreciated.
Did the fedora packages for f38 get installed? fedora-release* fedora-repos*
Thank you for your quick reply.
Using rpm -qa | grep -i fc38 | wc -l
I see that 4842 packages have been installed.
I watched the screen as it upgraded, and the package count was somewhere around 4842 when the scriplet to upgrade setroubleshoot-server started. (That's where the process hung).
Before you replied, I removed setroubleshoot-server from the laptop (dnf remove ...) and its related dependencies.
I then did dnf upgrade --refresh
and then dnf system-upgrade download --releasever=38 --allowerasing
I received the message: Error: Problem: The operation would result in removing the following protected packages: NetworkManager, dnf, grub2-tools-minimal, sudo, systemd, systemd-udev (try to add '--skip-broken' to skip uninstallable packages)
and then dnf system-upgrade download --releasever=38 --allowerasing --skip-broken
which produced the following error message
Error: Problem: The operation would result in removing the following protected packages: NetworkManager, dnf, grub2-tools-minimal, sudo, systemd, systemd-udev
I'm looking at your recommendations and now wondering how to proceed given that it seems I have probably about 4800+ packages that are both fc38 and fc37.
Any advice here would be great before I proceed to try something else.
You didn't try the main command that was suggested. "dnf distro-sync"
On Tue, 25 Apr 2023, Samuel Sieb wrote:
On 4/25/23 13:38, Max Pyziur wrote:
On Tue, 25 Apr 2023, stan via users wrote:
On Tue, 25 Apr 2023 16:10:06 -0400 (EDT) Max Pyziur pyz@brama.com wrote:
On Tue, 25 Apr 2023, Max Pyziur wrote:
Greetings,
Upgrading F38 on my Dell XPS 13 laptop of something like 2012 vintage w a 1TB SSD, the scriplet/upgrade to setroubleshoot-server is hanging.
Seems that it's been this way for a least 5-10 minutes while everything before this has been running briskly.
Advice?
My upgrade halted. The computer shutdown.
I hit the start button,
the selection for kernels came up only showing F37 kernels.
I hit the latest F37 kernel,
I got a login screen with the new F38 screen.
I logged in. Browser tabs are restored. Wifi connection, though, goes on and off.
I checked Postgresql installation; I have two version postgresql-14 (F37) and postgresql-15.
As best I can tell, the upgrade aborted leaving the system in, uh, challenged state.
Any advice on how to proceed here would be greatly appreciated.
Did the fedora packages for f38 get installed? fedora-release* fedora-repos*
Thank you for your quick reply.
Using rpm -qa | grep -i fc38 | wc -l
I see that 4842 packages have been installed.
I watched the screen as it upgraded, and the package count was somewhere around 4842 when the scriplet to upgrade setroubleshoot-server started. (That's where the process hung).
Before you replied, I removed setroubleshoot-server from the laptop (dnf remove ...) and its related dependencies.
I then did dnf upgrade --refresh
and then dnf system-upgrade download --releasever=38 --allowerasing
I received the message: Error: Problem: The operation would result in removing the following protected packages: NetworkManager, dnf, grub2-tools-minimal, sudo, systemd, systemd-udev (try to add '--skip-broken' to skip uninstallable packages)
and then dnf system-upgrade download --releasever=38 --allowerasing --skip-broken
which produced the following error message
Error: Problem: The operation would result in removing the following protected packages: NetworkManager, dnf, grub2-tools-minimal, sudo, systemd, systemd-udev
I'm looking at your recommendations and now wondering how to proceed given that it seems I have probably about 4800+ packages that are both fc38 and fc37.
Any advice here would be great before I proceed to try something else.
You didn't try the main command that was suggested. "dnf distro-sync"
When I try that command, it lists 27 problems, and then closes with
Problem 27: problem with installed package python3-mistune08-0.8.4-7.fc37.noarch - package python3-mistune08-0.8.4-7.fc37.noarch conflicts with python3-mistune provided by python3-mistune-0.8.4-5.fc37.noarch - installed package python3-mistune08-0.8.4-7.fc37.noarch obsoletes python3-mistune < 1 provided by python3-mistune-0.8.4-5.fc37.noarch - package python3-mistune08-0.8.4-7.fc37.noarch obsoletes python3-mistune < 1 provided by python3-mistune-0.8.4-5.fc37.noarch - problem with installed package python3-mistune-2.0.4-3.fc38.noarch - package python3-mistune08-0.8.4-7.fc37.noarch conflicts with python3-mistune provided by python3-mistune-2.0.4-1.fc37.noarch - python3-mistune-2.0.4-3.fc38.noarch does not belong to a distupgrade repository (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)
I've never used this command. I would appreciate any advice here.
Also, previously the question on RAM on the laptop, there 8GB installed. I would think that is enough, no?
Max
On Tue, 25 Apr 2023, Max Pyziur wrote:
packages: NetworkManager, dnf, grub2-tools-minimal, sudo, systemd, systemd-udev
I'm looking at your recommendations and now wondering how to proceed given that it seems I have probably about 4800+ packages that are both fc38 and fc37.
Any advice here would be great before I proceed to try something else.
You didn't try the main command that was suggested. "dnf distro-sync"
When I try that command, it lists 27 problems, and then closes with
Problem 27: problem with installed package python3-mistune08-0.8.4-7.fc37.noarch
- package python3-mistune08-0.8.4-7.fc37.noarch conflicts with
python3-mistune provided by python3-mistune-0.8.4-5.fc37.noarch
- installed package python3-mistune08-0.8.4-7.fc37.noarch obsoletes
python3-mistune < 1 provided by python3-mistune-0.8.4-5.fc37.noarch
- package python3-mistune08-0.8.4-7.fc37.noarch obsoletes python3-mistune <
1 provided by python3-mistune-0.8.4-5.fc37.noarch
- problem with installed package python3-mistune-2.0.4-3.fc38.noarch
- package python3-mistune08-0.8.4-7.fc37.noarch conflicts with
python3-mistune provided by python3-mistune-2.0.4-1.fc37.noarch
- python3-mistune-2.0.4-3.fc38.noarch does not belong to a distupgrade
repository (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)
I've never used this command. I would appreciate any advice here.
I've begun using this command. Example: dnf distro-sync perl*
And it removes all f38 installed packages where there is a an f37 package.
Is this the correct way to proceed?
Thank you again.
Max
Also, previously the question on RAM on the laptop, there 8GB installed. I would think that is enough, no?
Max
On Tue, 25 Apr 2023, Max Pyziur wrote:
On Tue, 25 Apr 2023, Max Pyziur wrote:
packages: NetworkManager, dnf, grub2-tools-minimal, sudo, systemd, systemd-udev
I'm looking at your recommendations and now wondering how to proceed given that it seems I have probably about 4800+ packages that are both fc38 and fc37.
Any advice here would be great before I proceed to try something else.
You didn't try the main command that was suggested. "dnf distro-sync"
When I try that command, it lists 27 problems, and then closes with
Problem 27: problem with installed package python3-mistune08-0.8.4-7.fc37.noarch
- package python3-mistune08-0.8.4-7.fc37.noarch conflicts with
python3-mistune provided by python3-mistune-0.8.4-5.fc37.noarch
- installed package python3-mistune08-0.8.4-7.fc37.noarch obsoletes
python3-mistune < 1 provided by python3-mistune-0.8.4-5.fc37.noarch
- package python3-mistune08-0.8.4-7.fc37.noarch obsoletes python3-mistune
< 1 provided by python3-mistune-0.8.4-5.fc37.noarch
- problem with installed package python3-mistune-2.0.4-3.fc38.noarch
- package python3-mistune08-0.8.4-7.fc37.noarch conflicts with
python3-mistune provided by python3-mistune-2.0.4-1.fc37.noarch
- python3-mistune-2.0.4-3.fc38.noarch does not belong to a distupgrade
repository (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)
I've never used this command. I would appreciate any advice here.
I've begun using this command. Example: dnf distro-sync perl*
And it removes all f38 installed packages where there is a an f37 package.
Is this the correct way to proceed?
Ok, I think that I now have a brick;; having run dnf distro-sync zlib*
I now get the following error: Traceback (most recent call last): File "/usr/bin/dnf", line 61, in <module> from dnf.cli import main File "/usr/lib/python3.11/site-packages/dnf/__init__.py", line 23, in <module> import dnf.pycomp File "/usr/lib/python3.11/site-packages/dnf/pycomp.py", line 23, in <module> import base64 File "/usr/lib64/python3.11/base64.py", line 11, in <module> import binascii ImportError: libz.so.1: cannot open shared object file: No such file or directory
MP
Thank you again.
Max
Also, previously the question on RAM on the laptop, there 8GB installed. I would think that is enough, no?
Max
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Am 25.04.2023 um 23:03 schrieb Max Pyziur pyz@brama.com:
I've begun using this command. Example: dnf distro-sync perl*
And it removes all f38 installed packages where there is a an f37 package.
Is this the correct way to proceed?
Thank you again.
First you should check, which version your system is on:
$ cat /etc/system-release
It says either F37 or F38
If say F37, you should continue with distro-sync, until you hopefully get a clean f37 again. Then you may start over.
to check you may issue:
$ rpm -qa | grep fc38
It should return nothing. Otherwise continue trying with distro-sync
-- Peter Boy https://fedoraproject.org/wiki/User:Pboy pboy@fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member Fedora docs team contributor Java developer and enthusiast
On 4/25/23 14:03, Max Pyziur wrote:
On Tue, 25 Apr 2023, Max Pyziur wrote:
You didn't try the main command that was suggested. "dnf distro-sync"
When I try that command, it lists 27 problems, and then closes with
Problem 27: problem with installed package python3-mistune08-0.8.4-7.fc37.noarch - package python3-mistune08-0.8.4-7.fc37.noarch conflicts with python3-mistune provided by python3-mistune-0.8.4-5.fc37.noarch - installed package python3-mistune08-0.8.4-7.fc37.noarch obsoletes python3-mistune < 1 provided by python3-mistune-0.8.4-5.fc37.noarch - package python3-mistune08-0.8.4-7.fc37.noarch obsoletes python3-mistune < 1 provided by python3-mistune-0.8.4-5.fc37.noarch - problem with installed package python3-mistune-2.0.4-3.fc38.noarch - package python3-mistune08-0.8.4-7.fc37.noarch conflicts with python3-mistune provided by python3-mistune-2.0.4-1.fc37.noarch - python3-mistune-2.0.4-3.fc38.noarch does not belong to a distupgrade repository (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)
I've never used this command. I would appreciate any advice here.
I've begun using this command. Example: dnf distro-sync perl*
And it removes all f38 installed packages where there is a an f37 package.
Right, because the F37 release package is still installed. Run "rpm -qa | grep release" and make sure you have an F38 version for every F37 one in the list. Then run "dnf remove '*release*37*. Then try the distro-sync again with the "--allowerasing" option.