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 <smooge@xxxxxxxxx> wrote: > > > On Tue, 19 May 2020 at 06:05, Paul Howarth <paul@xxxxxxxxxxxx> wrote: > > > > > On Mon, 18 May 2020 22:29:54 -0600 > > > Orion Poplawski <orion@xxxxxxxx> 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. =========================================================================================================================================== Package Architecture 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 Complete! INFO: Finish: run 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. -- Petr
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
