Hi,
On Sat, 2021-02-20 at 10:49 +0100, Miroslav Suchý wrote:
Do you want to make Fedora 34 better? Please spend 1 minute of your
time and try to run:
# Run this only if you use default Fedora modules
# next time you run any DNF command default modules will be
enabled again
sudo dnf module reset '*'
sudo dnf --releasever=34 --setopt=module_platform_id=platform:f34
\
--enablerepo=updates-testing --enablerepo=updates-testing-
modular \
distro-sync
This command does not replace `dnf system-upgrade`, but it will
reveal potential problems. You may also run `dnf
upgrade` before running this command.
I think we should do this exact same test but after Fedora release ,
For example on Dec 6 2020, I upgrade from F31 to F32 and I had these
results [1] I did a dnf distro-sync , but we found some mistakes if we
verify why package have lower versions in Fedora n+1 , sometimes
maintainer didn't send package to bodhi, other times package it is in
updates-testing forever and many other issues.
Best regards,
[1]
libappindicator-0:12.10.0-29.fc31.i686
libappindicator-0:12.10.0-29.fc31.x86_64
libappindicator-gtk3-0:12.10.0-29.fc31.i686
libappindicator-gtk3-0:12.10.0-29.fc31.x86_64
microcode_ctl-2:2.1-39.3.fc31.x86_64
perl-Net-DNS-SEC-0:1.17-1.fc31.x86_64
perl-Type-Tiny-0:1.010006-1.fc31.noarch
python2-pillow-0:6.2.2-3.fc31.x86_64
python2-setuptools-0:41.6.0-1.fc31.noarch
slirp4netns-0:1.1.6-1.fc31.x86_64
tpm2-abrmd-selinux-0:2.3.1-2.fc31.noarch
xawtv-0:3.107-2.fc31.x86_64
Downgrading:
baobab x86_64 3.34.0-2.fc32k
libappindicator x86_64 12.10.0-28.fc32
libappindicator-gtk3 x86_64 12.10.0-28.fc32
microcode_ctl x86_64 2:2.1-39.fc32
perl-Net-DNS-SEC x86_64 1.12-4.fc32
perl-Type-Tiny noarch 1.010004-1.fc32
python2-pillow x86_64 6.2.2-2.fc326 k
python2-setuptools noarch 41.2.0-2.fc32
slirp4netns x86_64 1.1.4-1.fc32
tpm2-abrmd-selinux noarch 2.3.1-1.fc32
xawtv x86_64 107-1.fc32
If you have have rdma-core.i686 installed you have to pass `
--allowerasing`.
https://bugzilla.redhat.com/show_bug.cgi?id=1919864
If you get this prompt:
...
Total download size: XXX M
Is this ok [y/N]:
you can answer N and nothing happens, no need to test the actual
upgrade.
But very likely you get some dependency problem now. In that case,
please report it against the appropriate package. Or
against fedora-obsolete-packages if that package should be removed in
Fedora 34. Please check existing reports against
fedora-obsolete-packages first:
https://red.ht/2kuBDPu
and also there is already bunch of "Fails to install" reports:
https://bugzilla.redhat.com/show_bug.cgi?id=F34FailsToInstall
Thank you
P.S. sent from workstation successfully upgraded to F34 :)
--
Miroslav Suchy, RHCA
Red Hat, Associate Manager, Community Packaging Tools, #brno,
#fedora-buildsys
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure --
Sérgio M. B.