On Sun, Jan 12, 2020 at 04:38:55AM -0500, Neal Gompa wrote:
On Sun, Jan 12, 2020 at 4:03 AM Nicolas Mailhot via devel
<devel(a)lists.fedoraproject.org> wrote:
>
> Le samedi 11 janvier 2020 à 13:09 -0500, Neal Gompa a écrit :
> >
> > The only reason I mentioned it is because since we distro-sync
> > between
> > releases, it doesn't actually matter as much as it used to.
>
> rawhide does not distro-sync (and some may say that rawhide does not
> matter, but early problem detection by rawhide users is one big reason
> distro sync works so well for other releases)
It sometimes does. Sometimes it does not.
It is strongly recommended that you should be using 'dnf
distro-sync'
for Rawhide if you want to use it as a daily driver. That handles all
the cases that occur in a rolling branch effectively.
It does not.
For example, right now on my laptop:
Error:
Problem: problem with installed package awscli-1.16.309-1.fc32.noarch
- package awscli-1.16.309-1.fc32.noarch requires python3.8dist(botocore) = 1.13.45, but
none of the providers can be installed
- python3-botocore-1.13.45-2.fc32.noarch does not belong to a distupgrade repository
- awscli-1.16.309-1.fc32.noarch does not belong to a distupgrade repository
(try to add '--skip-broken' to skip uninstallable packages)
(--skip-broken doesn't do anything here, same exact output)
distro-sync is only going to work if the repo(s) are all consistent for
you to sync to. :( Which I think we should get to, but it's not the case
yet.
kevin