Description of problem:
Here is a list of remaining package not in repos after updating (dnf update --releasever=30)
Version-Release number of selected component (if applicable):
# dnf list extras --quiet
beignet.x86_64 1.3.2-5.fc29 @fedora
clutter-gst2.x86_64 2.0.18-5.fc28 @fedora
cockpit-integration-tests.x86_64 151-2.fc26 @updates
cockpit-kubernetes.x86_64 194-2.fc29 @updates
compat-libicu60.x86_64 60.2-2.fc29 @fedora
ghostscript-fonts.noarch 5.50-36.fc26 @@commandline
hesiod.x86_64 3.2.1-14.fc29 @updates-testing
ladspa-swh-plugins.x86_64 0.4.17-2.fc29 @fedora
libgltf.x86_64 0.1.0-10.fc29 @fedora
mozjs24.x86_64 24.2.0-11.fc26 @@commandline
net6.x86_64 1.3.14-17.fc29 @fedora
obby.x86_64 0.4.8-17.fc29 @fedora
pam_pkcs11.x86_64 0.6.8-8.fc24 @anaconda
python2-custodia.noarch 0.6.0-4.fc29 @fedora
python2-sssdconfig.noarch 2.1.0-2.fc29 @updates
python2-yubico.noarch 1.3.2-10.fc29 @fedora
sobby.x86_64 0.4.7-18.fc29 @fedora
dnf update --releasever (initial install from f24 or older).
they remains on the system despite been removed from repos
They should be all obsoleted
should we expect them to be handled by the fedora-obsolete package or by the package or origin (cockpit for the related sub-packages ?).
Is any of the package blocking a clean upgrade to F30? The purpose of fedora-obsolete-packages is not to remove all removed packages, but to unblock broken upgrades be removing packages that cause trouble.
Well, I think theses will block at some point...
But since I guess I've removed the one really blocking my transition, it doesn't worth to take theses into account.
Closing. thx for the answer.
Okay, I've founded the one blocking:
it's python2-rpkg (that is not available on f30 without been obsoleted obviously).
I will forward to the rpkg component.