F30 update: libdnf, etc
by SternData
Wait a day or ???
Problem 1: package python2-hawkey-0.31.0-2.fc29.x86_64 requires
libdnf(x86-64) = 0.31.0-2.fc29, but none of the providers can be installed
- libdnf-0.31.0-2.fc29.x86_64 does not belong to a distupgrade repository
- problem with installed package python2-hawkey-0.31.0-2.fc29.x86_64
Problem 2: package system-config-services-0.111.4-2.fc24.noarch
requires python-slip >= 0.1.11, but none of the providers can be installed
- python2-slip-0.6.4-12.fc29.noarch does not belong to a distupgrade
repository
- problem with installed package
system-config-services-0.111.4-2.fc24.noarch
Problem 3: problem with installed package
system-config-firewall-1.2.29-21.fc29.noarch
- package system-config-firewall-1.2.29-21.fc29.noarch requires
python2-slip-dbus >= 0.2.7, but none of the providers can be installed
- python2-slip-dbus-0.6.4-12.fc29.noarch does not belong to a
distupgrade repository
Problem 4: package python3-hawkey-0.28.1-1.fc30.x86_64 requires
libdnf(x86-64) = 0.28.1-1.fc30, but none of the providers can be installed
- cannot install both libdnf-0.28.1-1.fc30.x86_64 and
libdnf-0.31.0-2.fc29.x86_64
- problem with installed package python3-hawkey-0.31.0-2.fc29.x86_64
- package python2-libdnf-0.31.0-2.fc29.x86_64 requires libdnf(x86-64)
= 0.31.0-2.fc29, but none of the providers can be installed
- python3-hawkey-0.31.0-2.fc29.x86_64 does not belong to a distupgrade
repository
- problem with installed package python2-libdnf-0.31.0-2.fc29.x86_64
(try to add '--allowerasing' to command line to replace conflicting
packages or '--skip-broken' to skip uninstallable packages)
--
-- Steve
4 years, 11 months
Smooth DNF Update (Yesterday Evening)
by Peter G.
I spotted an article on another site indicating release of F30. I wasn't expecting it for a week! Thus caught unprepared, for the first time ever, I did a dnf system-upgrade on my UEFI system. I had to remove cclive and, for some odd reason, there was a problem with getting the updates repo, so I blocked metalink= and unblocked baseurl= in fedora-updates.repo and everything worked smoothly. After a preliminary 2 hours, everything appears to be working as in F29.
4 years, 11 months
Freeradius bootstrap overwrite my certs
by Rafael Leiva-Ochoa
Hi Everyone,
I recently upgraded to Freeradius 3.0.19-1 and I noticed after I
restarted the service I was getting the following errors:
Apr 29 22:01:29 freeradius systemd[1]: Starting FreeRADIUS high performance
RADIUS server....
Apr 29 22:01:30 freeradius sh[1970]: make: *** No rule to make target
'server.cnf', needed by 'passwords.mk'. Stop.
Apr 29 22:01:30 freeradius systemd[1]: radiusd.service: Control process
exited, code=exited status=2
Apr 29 22:01:30 freeradius systemd[1]: radiusd.service: Failed with result
'exit-code'.
Apr 29 22:01:30 freeradius systemd[1]: Failed to start FreeRADIUS high
performance RADIUS server..
Apr 29 22:01:30 freeradius audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=radiusd comm="systemd
" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
I got it from Fedora 28 Repo: freeradius-3.0.19-1.fc28.armv7hl. After a lot
of digging, I found that a "bootstrap" script on the /etc/raddb/certs/
directory was being called on the /usr/lib/systemd/system/radiusd.service.
This script overwrote my current certificate files. I had to comment out
the ExecStartPre=/bin/sh /etc/raddb/certs/bootstrap to fix the problem. I
am not sure if anyone else encountered this problem before.
Here is what I have on my /usr/lib/systemd/system/radiusd.service script
for systemd
[Unit]
Description=FreeRADIUS high performance RADIUS server.
After=syslog.target network-online.target ipa.service dirsrv.target
krb5kdc.service
[Service]
Type=forking
PIDFile=/var/run/radiusd/radiusd.pid
ExecStartPre=-/bin/chown -R radiusd.radiusd /var/run/radiusd
#ExecStartPre=/bin/sh /etc/raddb/certs/bootstrap
ExecStartPre=/bin/chgrp -R radiusd /etc/raddb/certs/
ExecStartPre=/usr/sbin/radiusd -C
ExecStart=/usr/sbin/radiusd -d /etc/raddb
ExecReload=/usr/sbin/radiusd -C
ExecReload=/bin/kill -HUP $MAINPID
[Install]
WantedBy=multi-user.target
Is this being addressed on future releases?
Thanks,
Rafael
4 years, 11 months
Another issue to be aware of when you upgrade from F29 to F30
by Alan
Make sure you turn off any Gnome extensions that you have downloaded
from gnome.org. There is an issue where some gnome extensions that are
loaded from the user account will cause gnome-shell to crash. What you
will see is you try to log in and after a few seconds it returns back
to the login screen. (And yes, it is a reported bug. And yes, it still
happens, because it just happened on the upgrade I am doing now.)
The way I have fixed the problem is to delete anything in
~/.local/share/gnome-shell/extensions/ and then redownload the ones you
need.
Hope that helps.
4 years, 11 months