[EPEL-devel] Re: Modules again
On Wed, May 20, 2020 at 08:10:42AM +0200, Petr Pisar wrote: > Now you can ask why enabling mariadb-devel:10.3 does not enable mariadb:10.3 > automatically. Especially when mariadb-devel:10.3 run-requires mariadb:10.3 > according to "dnf module info mariadb-devel:10.3" command. The answer is a bug > in DNF. I think I recall the bugs has already been fixed, but apparantly it's > still (or again) there. > https://bugzilla.redhat.com/show_bug.cgi?id=1837841 -- Petr signature.asc Description: PGP signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Modules again
On Tue, May 19, 2020 at 04:05:02PM +0100, Paul Howarth wrote: > On Tue, 19 May 2020 09:07:30 -0400 > Stephen John Smoogen wrote: > > > On Tue, 19 May 2020 at 06:05, Paul Howarth wrote: > > > > > On Mon, 18 May 2020 22:29:54 -0600 > > > Orion Poplawski wrote: > > > > > > > On 5/17/20 6:34 AM, Paul Howarth wrote: > > > > > I'm trying to do a local build of gtkwave for EPEL-8. > > > > > > > > > > A koji scratch build somehow works: > > > > > http://koji.fedoraproject.org/koji/taskinfo?taskID=44609837 > > > > > > > > > > But a local build does not: > > > > > > > > > > $ mock -r epel-8-x86_64 gtkwave-3.3.104-2.fc31.src.rpm > > > > > ... > > > > > Error: > > > > > Problem: conflicting requests > > > > >- package > > > > > Judy-devel-1.0.5-18.module_el8.1.0+217+4d875839.i686 is excluded > > > > >- package > > > > > Judy-devel-1.0.5-18.module_el8.1.0+217+4d875839.x86_64 is > > > > > excluded > > > > > > > > > > Adding a repo with a local build of Judy doesn't help; that gets > > > > > excluded too. > > > > > > > > > > Any clues? > > > > > > > > > > Paul. > > > > > > > > Judy-devel appears to be part of the mariadb-devel module. > > > > Locally I can do: > > > > > > > > dnf module enable mariadb-devel > > > > dnf install Judy-devel > > > > > > > > This was discovered with: > > > > > > > > dnf module provides Judy-devel > > > > > > > > on RHEL 8.2, though that does not appear to work on CentOS 8.1. > > > > > > > > For mock, this seems to work: > > > > > > > > mock -r epel-8-x86_64 --config-opts module_enable=mariadb-devel > > > > --config-opts module_enable= gtkwave-3.3.104-2.el8.src.rpm > > > > > > I tried that and it didn't make any difference for me (building on > > > F-31). Maybe I need to wait for CentOS 8.2? > > > > > > > > Hmm do you have the Powertools enabled in that Mock? I see Judy-devel > > in the CentOS-8.1 tree in Powertools. > > Yes, I'm using vanilla configs straight from mock-core-configs for > this, and that has epel-8-x86_64.cfg, which pulls in centos-8.tpl, > which has the PowerTools repo defined and not disabled. > > (I generally use my own configs and don't touch the original ones, so I > know that if I try the original ones from upstream then they should > work as intended) > > Note that the error message doesn't say it can't find Judy-devel, it > says that it (and Judy) is/are excluded. I don't know why that is. > The message means that the Judy-devel package exists in a repository, but is not available for an installation, because a module it belongs to is not active (i.e. not enabled nor default). The correct procedure is enable the module it belongs to. "dnf module provides Judy-devel" command returns mariadb-devel:10.3 module. After enabling that module you get another error message that Judy package is excluded. That's because Judy package belongs to mariadb:10.3 module. You also need to enable that module. Then it works. It also works in mock: $ mock -r epel-8-x86_64 --config-opts module_enable=mariadb-devel --config-opts module_enable=mariadb install Judy-devel [...] INFO: installing package(s): Judy-devel No matches found for the following disable plugin patterns: local, spacewalk CentOS-8 - Base 539 kB/s | 2.2 MB 00:04 CentOS-8 - AppStream 1.3 MB/s | 7.0 MB 00:05 CentOS-8 - PowerTools 442 kB/s | 2.0 MB 00:04 CentOS-8 - Extras 5.7 kB/s | 5.9 kB 00:01 epel 5.2 kB/s | 4.7 kB 00:00 Dependencies resolved. === PackageArchitecture Version Repository Size === Installing: Judy-devel x86_64 1.0.5-18.module_el8.1.0+217+4d875839 PowerTools 76 k Installing dependencies: Judy x86_64 1.0.5-18.module_el8.1.0+217+4d875839 AppStream 131 k Transaction Summary === Install 2 Packages [...] Installed: Judy-devel-1.0.5-18.module_el8.1.0+217+4d875839.x86_64 Judy-1.0.5-18.module_el8.1.0+217+4d875839.x86_64 Compl
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-aa8ce752c3 pure-ftpd-1.0.49-4.el8 11 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-03d5f14bbe chromium-81.0.4044.138-1.el8 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-0d41abf072 perl-Mojolicious-8.42-1.el8 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-765ceaa306 clamav-0.102.3-1.el8 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-30aba92944 log4net-2.0.8-10.el8 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-2056b1c4a9 exim-4.93-3.el8 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-5660594875 python-markdown2-2.3.9-1.el8 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-c3fca161ee netdata-1.22.1-3.el8 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-38309f9f6f transmission-2.94-9.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing gdal-3.0.4-5.el8 knot-resolver-5.1.1-1.el8 mozilla-noscript-11.0.26-1.el8 msmtp-1.8.10-1.el8 pg-semver-0.30.0-1.el8 proj-6.3.2-4.el8 python-cooldict-1.04-1.el8 python-jsonpickle-1.4.1-4.el8 python-lrparsing-1.0.16-4.el8 python-pystalk-0.5.1-4.el8 rpminspect-data-fedora-0.10-1.el8 Details about builds: gdal-3.0.4-5.el8 (FEDORA-EPEL-2020-53ddeb81a7) GIS file format library Update Information: Upstream release of GDAL 3.0.4 disabled JAVA and LaTeX support for EPEL8, due to (yet) missing dependencies ChangeLog: References: [ 1 ] Bug #1741567 - Request to package gdal for EPEL 8 https://bugzilla.redhat.com/show_bug.cgi?id=1741567 knot-resolver-5.1.1-1.el8 (FEDORA-EPEL-2020-06e970da9c) Caching full DNS Resolver Update Information: - fixes CVE-2020-12667 ChangeLog: * Tue May 19 2020 Tomas Krizek - 5.1.1-1 - update to upstream version 5.1.1 (fixes CVE-2020-12667) mozilla-noscript-11.0.26-1.el8 (FEDORA-EPEL-2020-f820222a04) JavaScript white list extension for Mozilla Firefox Update Information: v 11.0.26 * UI adjustments for better mobile experience (thanks Bram Pitoyo for suggestions) * Updated HTML 5 events archive * Updated TLDs * Fixed hard reload needed after releasing restrictions (regression on Firefox Beta) * Fixed 3rd party scripts blocking regression on Firefox Trunk due to XBL removal (thanks guardao for reporting) * Fixed typo in unused yet code ChangeLog: * Tue May 19 2020 Dominik Mierzejewski - 11.0.26-1 - update to 11.0.26 (#1836699) References: [ 1 ] Bug #1836699 - mozilla-noscript-11.0.26 is available https://bugzilla.redhat.com/show_bug.cgi?id=1836699 msmtp-1.8.10-1.el8 (FEDORA-EPEL-2020-04ae3db1b5) SMTP client Update Information: Update to 1.8.10 ChangeLog: References: [ 1 ] Bug #1828854 - msmtp-1.8.7-2 package broken at least making mailq hang https://bugzilla.redhat.com/show_bug.cgi?id=1828854 pg-semver-0.30.0-1.el8 (FEDORA-EPEL-2020-7d109550d2) A semantic version data type for PostgreSQL Update Information: Update to 0.30.0: https://github.com/theory/pg-semver/compare/v0.21.0...v0.30.0 --
[EPEL-devel] Re: Modules again
It is amazing to me how often this setting makes things work. It seems like we're hard-coding this to "1" more widely. On Tue, May 19, 2020, 12:01 PM Paul Howarth wrote: > On Tue, 19 May 2020 09:21:46 -0700 > Kevin Fenzi wrote: > > > On Tue, May 19, 2020 at 11:48:04AM -0400, Stephen John Smoogen wrote: > > > On Tue, 19 May 2020 at 11:05, Paul Howarth > > > wrote: > > > > On Tue, 19 May 2020 09:07:30 -0400 > > > > Stephen John Smoogen wrote: > > > > > > > > > On Tue, 19 May 2020 at 06:05, Paul Howarth > > > > > wrote: > > > > > > > > Yes, I'm using vanilla configs straight from mock-core-configs for > > > > this, and that has epel-8-x86_64.cfg, which pulls in centos-8.tpl, > > > > which has the PowerTools repo defined and not disabled. > > > > > > > > (I generally use my own configs and don't touch the original > > > > ones, so I know that if I try the original ones from upstream > > > > then they should work as intended) > > > > > > > > Note that the error message doesn't say it can't find Judy-devel, > > > > it says that it (and Judy) is/are excluded. I don't know why that > > > > is. > > > > > > > > > > > Ohhh sorry. I missed the obvious. I am going to guess from past > > > problems, the system is trying to pull in mariadb which filters it > > > out and mariadb-devel which has it in. So when it sees the filters > > > it says 'nope can't do this sorry'. I wish there was a 'no I know > > > it might break my system do it anyway!' flag but I don't see one > > > looking through /usr/share/doc/mock/site-defaults.cfg . This was > > > one of the reasons for grobisplitter being used. > > > > You should be able to set: > > > > module_hotfixes = True > > > > in your dnf/yum/mock config. > > > > From the dnf man page: > > > > "Set this to True to disable module RPM filtering and make all RPMs > > from the repository available. The default is False. This allows > > user to create a repository with cherry-picked hotfixes that are > > included in a package set on a modular system." > > Ah, setting that option for the PowerTools repo allows the build to > work. Now if only there was a way to do that from the command line so I > didn't have to touch the mock config. > > Thanks! > > Paul. > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org > ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Modules again
On Tue, 19 May 2020 09:21:46 -0700 Kevin Fenzi wrote: > On Tue, May 19, 2020 at 11:48:04AM -0400, Stephen John Smoogen wrote: > > On Tue, 19 May 2020 at 11:05, Paul Howarth > > wrote: > > > On Tue, 19 May 2020 09:07:30 -0400 > > > Stephen John Smoogen wrote: > > > > > > > On Tue, 19 May 2020 at 06:05, Paul Howarth > > > > wrote: > > > > > > Yes, I'm using vanilla configs straight from mock-core-configs for > > > this, and that has epel-8-x86_64.cfg, which pulls in centos-8.tpl, > > > which has the PowerTools repo defined and not disabled. > > > > > > (I generally use my own configs and don't touch the original > > > ones, so I know that if I try the original ones from upstream > > > then they should work as intended) > > > > > > Note that the error message doesn't say it can't find Judy-devel, > > > it says that it (and Judy) is/are excluded. I don't know why that > > > is. > > > > > > > > Ohhh sorry. I missed the obvious. I am going to guess from past > > problems, the system is trying to pull in mariadb which filters it > > out and mariadb-devel which has it in. So when it sees the filters > > it says 'nope can't do this sorry'. I wish there was a 'no I know > > it might break my system do it anyway!' flag but I don't see one > > looking through /usr/share/doc/mock/site-defaults.cfg . This was > > one of the reasons for grobisplitter being used. > > You should be able to set: > > module_hotfixes = True > > in your dnf/yum/mock config. > > From the dnf man page: > > "Set this to True to disable module RPM filtering and make all RPMs > from the repository available. The default is False. This allows > user to create a repository with cherry-picked hotfixes that are > included in a package set on a modular system." Ah, setting that option for the PowerTools repo allows the build to work. Now if only there was a way to do that from the command line so I didn't have to touch the mock config. Thanks! Paul. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Modules again
On Tue, May 19, 2020 at 11:48:04AM -0400, Stephen John Smoogen wrote: > On Tue, 19 May 2020 at 11:05, Paul Howarth wrote: > > > On Tue, 19 May 2020 09:07:30 -0400 > > Stephen John Smoogen wrote: > > > > > On Tue, 19 May 2020 at 06:05, Paul Howarth wrote: > > > > > > > Yes, I'm using vanilla configs straight from mock-core-configs for > > this, and that has epel-8-x86_64.cfg, which pulls in centos-8.tpl, > > which has the PowerTools repo defined and not disabled. > > > > (I generally use my own configs and don't touch the original ones, so I > > know that if I try the original ones from upstream then they should > > work as intended) > > > > Note that the error message doesn't say it can't find Judy-devel, it > > says that it (and Judy) is/are excluded. I don't know why that is. > > > > > Ohhh sorry. I missed the obvious. I am going to guess from past problems, > the system is trying to pull in mariadb which filters it out and > mariadb-devel which has it in. So when it sees the filters it says 'nope > can't do this sorry'. I wish there was a 'no I know it might break my > system do it anyway!' flag but I don't see one looking > through /usr/share/doc/mock/site-defaults.cfg . This was one of the reasons > for grobisplitter being used. You should be able to set: module_hotfixes = True in your dnf/yum/mock config. From the dnf man page: "Set this to True to disable module RPM filtering and make all RPMs from the repository available. The default is False. This allows user to create a repository with cherry-picked hotfixes that are included in a package set on a modular system." kevin signature.asc Description: PGP signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Modules again
On Tue, 19 May 2020 at 11:05, Paul Howarth wrote: > On Tue, 19 May 2020 09:07:30 -0400 > Stephen John Smoogen wrote: > > > On Tue, 19 May 2020 at 06:05, Paul Howarth wrote: > > > > Yes, I'm using vanilla configs straight from mock-core-configs for > this, and that has epel-8-x86_64.cfg, which pulls in centos-8.tpl, > which has the PowerTools repo defined and not disabled. > > (I generally use my own configs and don't touch the original ones, so I > know that if I try the original ones from upstream then they should > work as intended) > > Note that the error message doesn't say it can't find Judy-devel, it > says that it (and Judy) is/are excluded. I don't know why that is. > > Ohhh sorry. I missed the obvious. I am going to guess from past problems, the system is trying to pull in mariadb which filters it out and mariadb-devel which has it in. So when it sees the filters it says 'nope can't do this sorry'. I wish there was a 'no I know it might break my system do it anyway!' flag but I don't see one looking through /usr/share/doc/mock/site-defaults.cfg . This was one of the reasons for grobisplitter being used. > Paul. > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org > -- Stephen J Smoogen. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Modules again
On Tue, 19 May 2020 09:07:30 -0400 Stephen John Smoogen wrote: > On Tue, 19 May 2020 at 06:05, Paul Howarth wrote: > > > On Mon, 18 May 2020 22:29:54 -0600 > > Orion Poplawski wrote: > > > > > On 5/17/20 6:34 AM, Paul Howarth wrote: > > > > I'm trying to do a local build of gtkwave for EPEL-8. > > > > > > > > A koji scratch build somehow works: > > > > http://koji.fedoraproject.org/koji/taskinfo?taskID=44609837 > > > > > > > > But a local build does not: > > > > > > > > $ mock -r epel-8-x86_64 gtkwave-3.3.104-2.fc31.src.rpm > > > > ... > > > > Error: > > > > Problem: conflicting requests > > > >- package > > > > Judy-devel-1.0.5-18.module_el8.1.0+217+4d875839.i686 is excluded > > > >- package > > > > Judy-devel-1.0.5-18.module_el8.1.0+217+4d875839.x86_64 is > > > > excluded > > > > > > > > Adding a repo with a local build of Judy doesn't help; that gets > > > > excluded too. > > > > > > > > Any clues? > > > > > > > > Paul. > > > > > > Judy-devel appears to be part of the mariadb-devel module. > > > Locally I can do: > > > > > > dnf module enable mariadb-devel > > > dnf install Judy-devel > > > > > > This was discovered with: > > > > > > dnf module provides Judy-devel > > > > > > on RHEL 8.2, though that does not appear to work on CentOS 8.1. > > > > > > For mock, this seems to work: > > > > > > mock -r epel-8-x86_64 --config-opts module_enable=mariadb-devel > > > --config-opts module_enable= gtkwave-3.3.104-2.el8.src.rpm > > > > I tried that and it didn't make any difference for me (building on > > F-31). Maybe I need to wait for CentOS 8.2? > > > > > Hmm do you have the Powertools enabled in that Mock? I see Judy-devel > in the CentOS-8.1 tree in Powertools. Yes, I'm using vanilla configs straight from mock-core-configs for this, and that has epel-8-x86_64.cfg, which pulls in centos-8.tpl, which has the PowerTools repo defined and not disabled. (I generally use my own configs and don't touch the original ones, so I know that if I try the original ones from upstream then they should work as intended) Note that the error message doesn't say it can't find Judy-devel, it says that it (and Judy) is/are excluded. I don't know why that is. Paul. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Modules again
On Tue, 19 May 2020 at 06:05, Paul Howarth wrote: > On Mon, 18 May 2020 22:29:54 -0600 > Orion Poplawski wrote: > > > On 5/17/20 6:34 AM, Paul Howarth wrote: > > > I'm trying to do a local build of gtkwave for EPEL-8. > > > > > > A koji scratch build somehow works: > > > http://koji.fedoraproject.org/koji/taskinfo?taskID=44609837 > > > > > > But a local build does not: > > > > > > $ mock -r epel-8-x86_64 gtkwave-3.3.104-2.fc31.src.rpm > > > ... > > > Error: > > > Problem: conflicting requests > > >- package Judy-devel-1.0.5-18.module_el8.1.0+217+4d875839.i686 is > > > excluded > > >- package Judy-devel-1.0.5-18.module_el8.1.0+217+4d875839.x86_64 > > > is excluded > > > > > > Adding a repo with a local build of Judy doesn't help; that gets > > > excluded too. > > > > > > Any clues? > > > > > > Paul. > > > > Judy-devel appears to be part of the mariadb-devel module. Locally I > > can do: > > > > dnf module enable mariadb-devel > > dnf install Judy-devel > > > > This was discovered with: > > > > dnf module provides Judy-devel > > > > on RHEL 8.2, though that does not appear to work on CentOS 8.1. > > > > For mock, this seems to work: > > > > mock -r epel-8-x86_64 --config-opts module_enable=mariadb-devel > > --config-opts module_enable= gtkwave-3.3.104-2.el8.src.rpm > > I tried that and it didn't make any difference for me (building on > F-31). Maybe I need to wait for CentOS 8.2? > > Hmm do you have the Powertools enabled in that Mock? I see Judy-devel in the CentOS-8.1 tree in Powertools. > > koji does some magic to essentially auto-enable some modules that I > > don't believe mock has. > > It writes its own mock configs, that I know. After that, I'm in the > dark... > > Thanks for trying. > Koji for EPEL does it by ugly magic (or fantastic if you love Rube Goldberg devices) ... we strip off all the module data using a program called grobisplitter and say do your best dnf versus using koji's built in determinator like we do for EPEL-5/6/7 and most Fedora. -- Stephen J Smoogen. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Modules again
On Mon, 18 May 2020 22:29:54 -0600 Orion Poplawski wrote: > On 5/17/20 6:34 AM, Paul Howarth wrote: > > I'm trying to do a local build of gtkwave for EPEL-8. > > > > A koji scratch build somehow works: > > http://koji.fedoraproject.org/koji/taskinfo?taskID=44609837 > > > > But a local build does not: > > > > $ mock -r epel-8-x86_64 gtkwave-3.3.104-2.fc31.src.rpm > > ... > > Error: > > Problem: conflicting requests > >- package Judy-devel-1.0.5-18.module_el8.1.0+217+4d875839.i686 is > > excluded > >- package Judy-devel-1.0.5-18.module_el8.1.0+217+4d875839.x86_64 > > is excluded > > > > Adding a repo with a local build of Judy doesn't help; that gets > > excluded too. > > > > Any clues? > > > > Paul. > > Judy-devel appears to be part of the mariadb-devel module. Locally I > can do: > > dnf module enable mariadb-devel > dnf install Judy-devel > > This was discovered with: > > dnf module provides Judy-devel > > on RHEL 8.2, though that does not appear to work on CentOS 8.1. > > For mock, this seems to work: > > mock -r epel-8-x86_64 --config-opts module_enable=mariadb-devel > --config-opts module_enable= gtkwave-3.3.104-2.el8.src.rpm I tried that and it didn't make any difference for me (building on F-31). Maybe I need to wait for CentOS 8.2? > koji does some magic to essentially auto-enable some modules that I > don't believe mock has. It writes its own mock configs, that I know. After that, I'm in the dark... Thanks for trying. Paul. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
