2015-04-01 16:40 GMT-03:00 Kevin Fenzi <kevin(a)scrye.com>:
There's some confusion around this, so I thought I would post to
try
and clear up things. In the event I am wrong on any of the below, please
do feel free to correct me. ;)
In the past the proposal was to have a yum-dnf package that provided
/usr/bin/yum, called dnf and conflicted with the yum package. I was
against that plan, but I think the one we settled on is worth doing.
It's somewhat of a middle ground between "yum is gone right now,
deal with it" and "you can keep using yum forever".
For f22 (and rawhide):
* dnf is installed by default. By that I mean it is in the 'core' group
in comps.
* dnf-yum is installed by default. By that I mean it is in the 'core'
group in comps next to dnf.
* yum is installed if something that depends on yum pulls it in or say
a user installs it manually.
* yum requires dnf-yum. So, if you install yum manually you will also
pull in dnf-yum (and the dnf plugin that handles history migrate).
* When you run 'yum' you get:
% sudo yum list foobar
Yum command has been deprecated, use dnf instead.
See 'man dnf' and 'man yum2dnf' for more information.
To transfer transaction metadata from yum to DNF, run 'dnf migrate'
Redirecting to '/usr/bin/dnf list foobar'
...then the ouput from dnf list foobar...
* If you wish to still use yum, the yum package provides now
a /usr/bin/yum-deprecated command that is the old yum
command renamed. It also has the notice message as above
on it.
I am using rawhide, and was trying to use dnf sometime ago, and
it was looking promising. But suddenly it stopped being useful,
and yum became again functional, so, I have been using only
yum.
And have been using yum with mock, because it does not work
with dnf, but now, when doing a review, I was surprised with this
in root.log:
DEBUG util.py:452: Executing command: ['/usr/bin/yum',
'--installroot', '/var/lib/mock/fedora-rawhide-x86_64/root/',
'--releasever', '23', 'resolvedep', 'ccache'] with env
{'CCACHE_UMASK': '002', 'LANG': 'en_US.UTF-8',
'HOME': '/builddir',
'CCACHE_DIR': '/tmp/ccache', 'SHELL': '/bin/bash',
'PATH':
'/usr/bin:/bin:/usr/sbin:/sbin', 'LC_MESSAGES': 'C',
'PROMPT_COMMAND':
'printf "\x1b]0;<mock-chroot>\x07<mock-chroot>"',
'TERM': 'vt100',
'HOSTNAME': 'mock'} and shell False
DEBUG util.py:388: Yum command has been deprecated, use dnf instead.
DEBUG util.py:388: See 'man dnf' and 'man yum2dnf' for more information.
DEBUG util.py:388: To transfer transaction metadata from yum to DNF,
run 'dnf migrate'Redirecting to '/usr/bin/dnf --installroot
/var/lib/mock/fedora-rawhide-x86_64/root/ --releasever 23 resolvedep
ccache'
DEBUG util.py:388: No such command: resolvedep. Please use /usr/bin/dnf --help
DEBUG util.py:388: It could be a DNF plugin command.
so, lets run again (without fedora-review -o--yum) to ge back the dnf error
in root.log:
DEBUG util.py:452: Executing command: ['/usr/bin/dnf', 'builddep',
'--installroot', '/var/lib/mock/fedora-rawhide-x86_64/root/',
'--releasever', '23',
'/var/lib/mock/fedora-rawhide-x86_64/root//builddir/build/SRPMS/ebay-cors-filter-1.0.1-1.fc23.src.rpm']
with env {'LANG': 'en_US.UTF-8', 'HOME': '/builddir',
'CCACHE_DIR':
'/tmp/ccache', 'SHELL': '/bin/bash', 'PATH':
'/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf
"\x1b]0;<mock-chroot>\x07<mock-chroot>"', 'HOSTNAME':
'mock',
'LC_MESSAGES': 'C', 'TERM': 'vt100',
'CCACHE_UMASK': '002'} and shell
False
DEBUG util.py:388: No such command: builddep. Please use /usr/bin/dnf --help
DEBUG util.py:388: It could be a DNF plugin command.
I will review using a release other than rawhide.
* If you are using the yum python bindings directly, that will
continue
to work if you have the yum package installed.
Note that this landed before Beta freeze, but there were some issues
with the initial package doing this. There is an update available:
https://admin.fedoraproject.org/updates/yum-3.4.3-505.fc22
I think this helps those users who read any of the docs out there
that say to 'yum install foo' at the cost of those people who need
some specific command line behavior from yum. The second group
is much better positioned to use yum-deprecated or know whats
going on than the first group.
I understand that there is need to update, to use new tools, but
I am afraid, yum only had a small window of time broken for me
some time ago, after that, I could simply not use dnf to update
rawhide, while with yum, sometimes needing --skip-broken (and
doing that when I knew the packages broken would not break
my system), I would be able to update.
kevin
Thanks,
Paulo