[EPEL-devel] Re: Modules again

2020-05-18 Thread Orion Poplawski

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


or add to /etc/mock/templates/centos-8.tpl:

config_opts['module_enable'] = ['mariadb-devel']

koji does some magic to essentially auto-enable some modules that I 
don't believe mock has.


--
Orion Poplawski
Manager of NWRA Technical Systems  720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/



smime.p7s
Description: S/MIME Cryptographic 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: Incompatible upgrade for oniguruma in EPEL 7

2020-05-18 Thread David Alger
+1 makes sense to me; also side-note, in my testing jq seems to work just fine 
built against oniguruma 6.9.4
___
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: Documentation for EPEL modules?

2020-05-18 Thread Petr Pisar
On Sat, May 16, 2020 at 11:43:00AM +0200, Antonio Trande wrote:
> On 15/05/20 14:57, Stephen Gallagher wrote:
> > On Fri, May 15, 2020 at 7:57 AM Petr Pisar  wrote:
> >>
> >> On Fri, May 15, 2020 at 06:30:04AM -0500, Richard Shaw wrote:
> >>> On Fri, May 15, 2020 at 6:15 AM Petr Pisar  wrote:
> >>>
>  On Fri, May 15, 2020 at 12:42:15PM +0200, Antonio Trande wrote:
> > Shortly (Martin is in Cc to confirm):
> >
> > 1) Make a module:
> >
> > $ fedpkg clone cmake3
> > $ fedpkg request-repo --namespace modules --exception cmake3-latest
> > $ fedpkg request-branch --namespace modules --repo cmake3-latest epel8
> >
>  This will request for creating "cmake3-latest" module and "cmake3-latest"
>  repository and "epel8" stream and "epel8" branch. I don't know if you
>  really
>  want to create "cmake3-latest:epel8" module stream.
> 
> >>>
> >>> Since this is a module, is there any point in using the cmake3 namespace
> >>> over just cmake?
> >>>
> >> I cannot see any point. Maybe if there were cmake-2 or cmake-4 
> >> incompatible to
> >> cmake-3 but installable in parallel, then it would make sense. (Like 
> >> Python.)
> >> Because you cannot install more streams of the same module at the same 
> >> time.
> >> Otherwise I would also go with plain "cmake" module name.
> > 
> > 
> > It turns out, cmake already has a presence[1] in the modules namespace
> > of dist-git. It is a relic of the Modularity 1.0 effort, but it's
> > already there and that will make this easier.
> 
> Petr, can you take care of this module for epel8, too?
> 
I cannot because of a lack of time and interest in CMake. But I can transfer
an ownership of the module to whoever wants it. Also please note that at that
time CMake bundled various libraries and a second build-only cmake-bootstrap
module was needed to build the cmake module properly. I will include it into
the gift.

-- 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