Hi,
After upgrading from F21 to F22 and switching to dnf, my update/install process is very very slow.
Eg. dnf install tmux took more than 5 minutes. Most of the time I just give up after waiting more than 30 minutes. In F21 it would have taken a few seconds.
Please advise:
# dnf clean all Cleaning repos: fedora updates Cleaning up Everything # time dnf -4y update Fedora 22 - x86_64 347 kB/s | 41 MB 02:01
Updates ... (After 15-20 minutes, it finally starts downloading packages) [...]
(2/836): kernel-debug-core-4.1.3-200.fc22.x86_64.rpm 57 kB/s | 21 MB 06:12 (3/836): kernel-core-4.1.3-200.fc22.x86_64.rpm 53 kB/s | 19 MB 06:14 [MIRROR] kernel-debug-devel-4.1.3-200.fc22.x86_64.rpm: Curl error (28): Timeout was reached for ftp://mirror.easyspeedy.com/fedora/updates/22/x86_64/k/kernel-debug-devel-4.1.3-200.fc22.x86_64.rpm [Connection time-out]
Regards Martin
Hello Martin, sounds more like a mirrors issue; to confirm that please clean your cache and try to upgrade your system again but this time using yum.
On Sun, Aug 2, 2015, 14:33 Martin Møller Skarbiniks Pedersen < traxplayer@gmail.com> wrote:
Hi,
After upgrading from F21 to F22 and switching to dnf, my update/install process is very very slow.
Eg. dnf install tmux took more than 5 minutes. Most of the time I just give up after waiting more than 30 minutes. In F21 it would have taken a few seconds.
Please advise:
# dnf clean all Cleaning repos: fedora updates Cleaning up Everything # time dnf -4y update Fedora 22 - x86_64 347 kB/s | 41 MB 02:01 Updates ... (After 15-20 minutes, it finally starts downloading packages) [...]
(2/836): kernel-debug-core-4.1.3-200.fc22.x86_64.rpm 57 kB/s | 21 MB 06:12 (3/836): kernel-core-4.1.3-200.fc22.x86_64.rpm 53 kB/s | 19 MB 06:14 [MIRROR] kernel-debug-devel-4.1.3-200.fc22.x86_64.rpm: Curl error (28): Timeout was reached for ftp://mirror.easyspeedy.com/fedora/updates/22/x86_64/k/kernel-debug-devel-4.1.3-200.fc22.x86_64.rpm [Connection time-out]
Regards Martin
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 02/08/15 13:46, Martin Cigorraga wrote:
Hello Martin, sounds more like a mirrors issue; to confirm that please clean your cache and try to upgrade your system again but this time using yum.
.
It has been unusually slow, about eleven hours ago I gave up and went to bed, later this morning I did update one computer at about one-quarter normal speed, will wait to do the other two.
Just my observation here ...
Bob
On 2 August 2015 at 19:46, Martin Cigorraga martincigorraga@gmail.com wrote:
Hello Martin, sounds more like a mirrors issue; to confirm that please clean your cache and try to upgrade your system again but this time using yum.
OK. yum-deprecated works very fast. A few seconds to install a program etc. However I am afraid that the dnf/yum database is somehow broken now.
# time yum-deprecated update --> Finished Dependency Resolution Error: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just pointing out that there is a problem. Eg.:
1. You have an upgrade for elfutils-libs which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of elfutils-libs of the different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package requires what). You can try redoing the upgrade with --exclude elfutils-libs.otherarch ... this should give you an error message showing the root cause of the problem.
2. You have multiple architectures of elfutils-libs installed, but yum can only see an upgrade for one of those architectures. If you don't want/need both architectures anymore then you can remove the one with the missing update and everything will work.
3. You have duplicate versions of elfutils-libs installed already. You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove this checking, however this is almost never the correct thing to do as something else is very likely to go wrong (often causing much more problems).
Protected multilib versions: elfutils-libs-0.163-1.fc22.i686 != elfutils-libs-0.161-6.fc22.x86_64 Error: Protected multilib versions: elfutils-libelf-0.163-1.fc22.i686 != elfutils-libelf-0.161-6.fc22.x86_64
real 0m27.083s
Regards Martin
On Sun, Aug 2, 2015, 14:33 Martin Møller Skarbiniks Pedersen < traxplayer@gmail.com> wrote:
Hi,
After upgrading from F21 to F22 and switching to dnf, my update/install process is very very slow.
Eg. dnf install tmux took more than 5 minutes. Most of the time I just give up after waiting more than 30 minutes. In F21 it would have taken a few seconds.
Please advise:
# dnf clean all Cleaning repos: fedora updates Cleaning up Everything # time dnf -4y update Fedora 22 - x86_64 347 kB/s | 41 MB 02:01 Updates ... (After 15-20 minutes, it finally starts downloading packages) [...]
(2/836): kernel-debug-core-4.1.3-200.fc22.x86_64.rpm 57 kB/s | 21 MB 06:12 (3/836): kernel-core-4.1.3-200.fc22.x86_64.rpm 53 kB/s | 19 MB 06:14 [MIRROR] kernel-debug-devel-4.1.3-200.fc22.x86_64.rpm: Curl error (28): Timeout was reached for ftp://mirror.easyspeedy.com/fedora/updates/22/x86_64/k/kernel-debug-devel-4.1.3-200.fc22.x86_64.rpm [Connection time-out]
Regards Martin
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Luckily dnf works as expected here :P
As of the multilib stuff check the conflicting packages, most likely they have been installed as dependencies from a third-party repository.
On Sun, Aug 2, 2015, 17:17 Martin Møller Skarbiniks Pedersen < traxplayer@gmail.com> wrote:
On 2 August 2015 at 19:46, Martin Cigorraga martincigorraga@gmail.com wrote:
Hello Martin, sounds more like a mirrors issue; to confirm that please clean your cache and try to upgrade your system again but this time using yum.
OK. yum-deprecated works very fast. A few seconds to install a program etc. However I am afraid that the dnf/yum database is somehow broken now.
# time yum-deprecated update --> Finished Dependency Resolution Error: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just pointing out that there is a problem. Eg.:
1. You have an upgrade for elfutils-libs which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of elfutils-libs ofthe different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package requires what). You can try redoing the upgrade with --exclude elfutils-libs.otherarch ... this should give you an error message showing the root cause of the problem.
2. You have multiple architectures of elfutils-libs installed, but yum can only see an upgrade for one of those architectures. If you don't want/need both architectures anymore then you can remove the one with the missing update and everything will work. 3. You have duplicate versions of elfutils-libs installed already. You can use "yum check" to get yum show these errors. ...you can also use --setopt=protected_multilib=false to remove this checking, however this is almost never the correct thing to do as something else is very likely to go wrong (often causing much more problems). Protected multilib versions: elfutils-libs-0.163-1.fc22.i686 !=elfutils-libs-0.161-6.fc22.x86_64 Error: Protected multilib versions: elfutils-libelf-0.163-1.fc22.i686 != elfutils-libelf-0.161-6.fc22.x86_64
real 0m27.083s
Regards Martin
On Sun, Aug 2, 2015, 14:33 Martin Møller Skarbiniks Pedersen < traxplayer@gmail.com> wrote:
Hi,
After upgrading from F21 to F22 and switching to dnf, my update/install process is very very slow.
Eg. dnf install tmux took more than 5 minutes. Most of the time I just give up after waiting more than 30 minutes. In F21 it would have taken a few seconds.
Please advise:
# dnf clean all Cleaning repos: fedora updates Cleaning up Everything # time dnf -4y update Fedora 22 - x86_64 347 kB/s | 41 MB 02:01 Updates ... (After 15-20 minutes, it finally starts downloading packages) [...]
(2/836): kernel-debug-core-4.1.3-200.fc22.x86_64.rpm 57 kB/s | 21 MB 06:12 (3/836): kernel-core-4.1.3-200.fc22.x86_64.rpm 53 kB/s | 19 MB 06:14 [MIRROR] kernel-debug-devel-4.1.3-200.fc22.x86_64.rpm: Curl error (28): Timeout was reached for ftp://mirror.easyspeedy.com/fedora/updates/22/x86_64/k/kernel-debug-devel-4.1.3-200.fc22.x86_64.rpm [Connection time-out]
Regards Martin
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
-- Til uvedkommende, der læser med: Der er ingen grund til at læse min mail. Jeg har intet at gøre med FARC, al-Jihad, al-Qaida, Hamas, Hizb al-Mujahidin eller ETA. Jeg har aldrig gjort Zakat, går ikke ind for Istishad, har ikke lavet en bilbombe eller kernevåben og jeg ved dårligt nok, hvad Al Manar og бомба betyder. Men tak for den udviste interesse.
Leve Ligemageriet! Styrk pøbelvældet! Bevar misundelsesafgifterne og cafepengene! Hurra for ældrebyrden! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 08/02/2015 01:17 PM, Martin Møller Skarbiniks Pedersen wrote:
You can try redoing the upgrade with --exclude elfutils-libs.otherarch ... this should give you an error message showing the root cause of the problem.
...
3. You have duplicate versions of elfutils-libs installedalready. You can use "yum check" to get yum show these errors.
Have you tried "yum-deprecated --exclude elfutils-libs.i686" and "yum-deprecated check" yet?
On Sun, 2 Aug 2015 22:17:09 +0200, Martin Møller Skarbiniks Pedersen wrote:
Protected multilib versions: elfutils-libs-0.163-1.fc22.i686 !=elfutils-libs-0.161-6.fc22.x86_64 Error: Protected multilib versions: elfutils-libelf-0.163-1.fc22.i686 != elfutils-libelf-0.161-6.fc22.x86_64
What do you get for
rpm -qa elfutils*
and
dnf list elfutils* ( or: yum list elfutils* )
?
Typically (normally!), the i686 and x86_64 builds of a multilib package are made available in the x86_64 repo at the same time. The only chance to get a version mismatch as above is when you're assigned to a broken mirror, or if your installation is broken by duplicate packages, or if you somehow managed to upgrade only either arch (causing a version mismatch to begin with).
What is the case for you needs to be examined.
-
Bob Goodwin -
Gordon Messmer -
Martin Cigorraga -
Martin Møller Skarbiniks Pedersen -
Michael Schwendt