FYI dnf-plugins-extras is a package that aggregates all plugins that the
community produces. Bottom line, please don't blame dnf, blame the individual
plugins.
Reading your problem and couple other just like it I think it might make sense
not to have the dnf-plugins-extras metapackage that installs all the plugins
automatically. It seems to be only upsetting people when one (often not the
desired one) plugin breaks everything else. I'm CCing Igor to consider this
proposal.
Thanks
Jan
On 8. 4. 2015 at 12:14:17, Tom Hughes wrote:
So this morning I cloned an up to date rawhide VM and attempted to
convert
it to F22 by using "dnf distro-sync" on it. Obviously that is a fairly
advanced use case but I think one tale of what happened at the end of that
process will highlight why I often find myself shouting WTF at dnf when
going beyond basic install/update of packages. There were other issues
along the way before I got to this point...
Having eventually completed the distro-sync I wanted to check for any
orphans that needed sorting out. Google told me dnf-plugins-extras was that
I needed to replace package-cleanup, so I installed it, only to find that
every use of dnf now reported:
fedora22 [~] % sudo dnf upgrade
Failed to synchronize cache for repo '_local' from
'file:///var/lib/dnf/plugins/local': Cannot download repomd.xml: Cannot
download repodata/repomd.xml: All mirrors were tried, disabling.
After shouting WTF yet again I determined that dnf-plugins-extras includes
python-dnf-plugins-extras-local which apparently tries to use a non-existent
local directory as a hidden extra repo.
Fine whatever, we don't need that, so lets remove it:
fedora22 [~] % sudo dnf erase python-dnf-plugins-extras-local
Dependencies resolved.
============================================================================
==== Package Arch Version
Repository Size
===========================================================================
===== Removing:
dnf-plugins-extras noarch 0.0.6-2.fc22 @System
0 python-beautifulsoup4 noarch 4.3.2-3.fc21 @System
605 k python-dnf-plugins-extras noarch 0.0.6-2.fc22
@System 0 python-dnf-plugins-extras-debug noarch 0.0.6-2.fc22
@System 26 k python-dnf-plugins-extras-local noarch 0.0.6-2.fc22
@System 11 k python-dnf-plugins-extras-orphans noarch
0.0.6-2.fc22 @System 9.3 k python-dnf-plugins-extras-repoclosure
noarch 0.0.6-2.fc22 @System 9.4 k python-dnf-plugins-extras-repograph
noarch 0.0.6-2.fc22 @System 9.5 k
python-dnf-plugins-extras-repomanage noarch 0.0.6-2.fc22 @System
12 k python-dnf-plugins-extras-snapper noarch 0.0.6-2.fc22
@System 4.4 k python-dnf-plugins-extras-tracer noarch 0.0.6-2.fc22
@System 7.7 k python-html5lib noarch
1:0.999-5.fc21 @System 1.2 M python-psutil
x86_64 2.1.3-1.fc22 @System 518 k snapper
x86_64 0.2.5-2.fc22 @System 1.0 M snapper-libs
x86_64 0.2.5-2.fc22 @System 846 k tracer
noarch 0.5.8-1.fc22 @System 272 k
Transaction Summary
============================================================================
==== Remove 16 Packages
Installed size: 4.5 M
Is this ok [y/N]: y
WTF! Oh, of course, removing that removes dnf-plugins-extras and then
everything else counts as auto installed and gets removed. After ceasing
banging my head on the desk I let it go ahead and then add back
python-dnf-plugins-extras-orphans to get the plugin I actually wanted.
So now I run "dnf orphans" at last and am a little surprised to get 589
lines of output:
fedora22 [~] % sudo dnf orphans
CharLS-devel-1.0-8.fc22.x86_64
...
zsh-5.0.7-6.fc22.x86_64
But those are F22 packages I hear you say! Indeed they are, and list
confirms that they do exist in configured repositories:
fedora22 [~] % sudo dnf list --showduplicates zsh
Using metadata from Wed Apr 8 11:02:28 2015 (0:53:45 hours old)
Installed Packages
zsh.x86_64 5.0.7-6.fc22 @System
Available Packages
zsh.x86_64 5.0.7-6.fc22 @System
zsh.x86_64 5.0.7-6.fc22
fedora-base
WTF!
Tom