hello, i am updating my testsystem and have same problems which i have on other system: emerge -vuaDN world don't update the system while i have more then 150 confilcts with different versions of the same slot and it is impossible to get th system up to date without emerge --nodeps for many packages. i think, my problems come with the calibre package. i have unmask it some times ago because at this time, i think, all calibre packages are masked. but the newest calibre need the newest qt5 and perl-5.22 and perl-5.22 make much problems because the most virtual/perl-* modules where not emerged without --nodeps and want to reinstall perl-5.22. this is also with some other perl modules. after update to perl-5.22 it is imposible to use emerge -vuaDN because this command will reinstall perl-5.20 and i think, that don't work while there are many version conflicts of the perl-modules. please change the settings for all perl-modules to allow installation with all perl-versions and block only this modules for a specific perl-version if it is impossible to install this modul with this version. i change my settings and mask the newest calibre versions and hope, that the update make no more problems. goodby Reproducible: Always Steps to Reproduce: try to update to perl-5.22 or install newest calibra-2.35.0 package which need perl-5.22
There are still some open issues with 5.22. [1] Can you provide more information please? emerge --info and logfiles as described in [2] [1] https://wiki.gentoo.org/wiki/Project:Perl/5.22_Known_Issues [2] https://wiki.gentoo.org/wiki/Bugzilla/Bug_report_guide
The issues that you are finding with the perl updates are likely false-positive reports due to one or more unrelated conflicts. To ensure that perl and all of its rdeps upgrade properly, please: 1 - make sure there are no perl-core/* packages in @world 2 - resolve all conflicts not related to perl packages (masks, slot conflicts, useflag mismatches, blockers, etc) If you attach the full output of your emerge command we may be able to help in identifying the specific blocker(s) that are keeping emerge from completing a full dependency calculation.
No one output - no one deal with it, words are too generic.
hello, you must wait some time. my testsystem is offline at the moment and i have much other things to do. but if i have tim again or have same problems with the next system, which must be updated, i will give you more information. goodby
