On Wed, 18 Oct 2017 09:45:52 -0000
Marcin Zajączkowski <mszpak@xxxxx> wrote:
> I will try `dnf distro-sync`, I would prefer to do not install it
> from scratch.
>
> In the meantime I removed all F27 packages with `rpm` do get rid of
> conflicts. However, it brought me to another issue with CA and curl
> ("curl error: Problem with the SSL CA cert (path access rights?)")
> and the fact that `update-ca-trust` doesn't see glibc in the proper
> version...
If you removed *all* F27 packages, then it is unlikely that distro-sync
will work to upgrade to F27. It will distro-sync back to F26. dnf has
to think that it is a version of F27 needing distro-sync to get it to
upgrade to F27.
If that doesn't work, you can install the F27 fedora release packages,
disable the F26 repositories in /etc/yum.repos.d and enable the F27
repositories there, and run dnf update. A lot more risky, but as a
last chance, worth a try. It will be messy, and require manual cleanup.
>
> Anyway, I wonder if it is safe to install packages with dnf being
> chrooted?
I've successfully used that technique for a rawhide instance, to update
it while I was running a released Fedora. It used the dnf and
repositories from rawhide, of course, not those from the version I
chrooted from.
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
