https://bugzilla.redhat.com/show_bug.cgi?id=1668968 --- Comment #4 from Petr Pisar <ppisar@xxxxxxxxxx> --- (In reply to Luigi Cantoni from comment #2) > I do not it appears have [e] enabled. Yes. It is so and that's good. > Also 3 of my systems have the yum check enabled and all three have this > error (the others are updated by image copies). Aha. "yum check" could do something strange. I've never used that. I will look at it. > I did enable the testing update because of an earlier bug I reported was > fixed in testing and I was able to verify it did fix my system. > I am sure I did not do this on all three systems so I am 95% sure this is > not the cause. When you mentioned testing updates, I noticed that updates-modular and updates-testing-modular contain the same perl:5.26 build: # dnf module info perl:5.26 | grep -E '^(Version|Repo)' Version : 20181205105946 Repo : updates-testing-modular Version : 20180417112647 Repo : fedora-modular Version : 20181205105946 Repo : updates-modular This is not how it should work. A module build should be moved from testing to updates. Not to be copied and existing in both of them. This is some glitch in producing composes (reported < https://pagure.io/releng/issue/8074>). However, it should not affect DNF. > I do not know what would have set me to the module enabled version request > even though its does not appear set. > If you enabled some other module that requires perl module, then both would become enabled. dnf has "dnf module list --enabled" command that lists all enabled module streams. However the output is a bit more verbose than "dnf module list". > I will do "dnf module disable perl:5.26" as you indicate it should not do > any harm. > Interestingly it now looks like this > dnf module list | grep perl > perl 5.24 [x] minimal, default > Practical Extraction and Report Language > perl 5.26 [x] minimal, default > Practical Extraction and Report Language > perl-bootstrap 5.24 > Perl bootstrap module for bootrapping Perl module > perl-bootstrap 5.26 > Perl bootstrap module for bootrapping Perl module > perl 5.24 [x] minimal, default > Practical Extraction and Report Language > perl 5.26 [x] minimal, default > Practical Extraction and Report Language > perl-bootstrap 5.24 > Perl bootstrap module for bootrapping Perl module > perl-bootstrap 5.26 > Perl bootstrap module for bootrapping Perl module > > I have retested (no reboot between dnf and test), same errors come up with > 0yum-daily.cron when run manually. There are various flags for a module. A module can be: default - the module is available unless disabled enabled - the module is available disabled - the module is not available and attempts to use it indirectly will result it verbose warnings (or errors?) none-of-that - the module is not available but an indirect use will switch the module to enabled default is defined by distribution and cannot be changed by a user. enabled/disabled can be switched by a user ("dnf module enable", "dnf module disable" commands). These two flags are mutually exclusive. A user can unset enabled/disabled flag by "dnf module reset" command. I believe that in your case that should not be any difference between the original state (no flags) and disabled ([x] flag). You can try disabling perl-bootstrap module. (perl-bootstrap is used only for building perl module and users should not use it. Though Fedora release engineers made it available). But I don't believe it will help. The offending packages are part from perl:5.26 module build in versions: 20181205105946 20181207064909 20181207083312 20181207093623 Fedora 29 repositories contain these versions: 20180417112647 - base 20181205105946 - updates and testing So the packages are delivered by 20181205105946 version in updates repository. But you disabled the perl:5.26 module and it did not help. Do you have the packages already installed on your system (rpm -q perl-Archive-Zip)? Then of course disabling a module would not help because they were already in the system. If DNF see the packages in repositories can be verified with "dnf info perl-Archive-Zip" command. Finally, if you do not use any modules, you can actually disable the modular repositories completely. In /etc/yum.repos.d/ directory there are four files: # ls -1 *modular* fedora-modular.repo fedora-rawhide-modular.repo fedora-updates-modular.repo fedora-updates-testing-modular.repo Each of them contains bunch of repository sections and every section has "enabled" option. If the option's value is 0, the repository is disabled and DNF should not consider the repository at all. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ perl-devel mailing list -- perl-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to perl-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@xxxxxxxxxxxxxxxxxxxxxxx
