[1]
https://lists.fedoraproject.org/archives/search?q=A+coordinated+plan+for+ansible-collection+updates+in+EPEL%3F=1=epel-devel%40lists.fedoraproject.orgÚte-asc
--
Happy automating,
Maxwell G (@gotmax23)
Pronouns: He/They
___
epel-devel mailing l
On Tue May 16, 2023 at 11:04 +0200, Miro Hrončok wrote:
> On 15. 05. 23 16:49, Maxwell G wrote:
> > On Mon May 15, 2023 at 12:14 +0200, Miro Hrončok wrote:
> >> Hello,
> >>
> >> I'm working on adding python3.11-rpm to EPEL 9 and EPEL 9 Next.
> >>
> &
the other alt python stacks in RHEL 8.
> If there is a significant demand, I can try add this (and python39-rpm) to
> EPEL
> 8 as well.
As I said on IRC, I'd like that for fedrq.
--
Maxwell G (@gotmax23)
Pronouns: He/They
___
epel-de
> https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
--
Happy packaging,
Maxwell G (@gotmax23)
Pronouns: He/They
___
epel-d
ual.
--
Happy automating,
Maxwell G (@gotmax23)
Pronouns: He/They
___
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
of Red Hat Developer Tools. I mention it because it means the
> EPEL considerations are different in terms of buildroot availability
> and requirements.
rust is also available in EPEL 7 proper[1].
[1] https://src.fedoraproject.org/rpms/rust/tree/epel7
--
Maxwell
On Tue Feb 28, 2023 at 23:44 +0100, Fabio Valentini wrote:
> On Sun, Feb 26, 2023 at 5:56 PM Maxwell G wrote:
> >
> > I think the intention was to push this to epel9-next first, but then I
> > accidentally opened the last two PRs against epel9 instead of
> > epel9-
ext. FTR, python3.11 won't be available until ~May when 9.2 comes
out, so we can't yet built this in epel9 proper. Can you confirm that
you'd like this in epel9-next? I think giving this some time to incubate
in epel9-next definitely makes sense.
Hi Troy,
On Tue Nov 1, 2022 at 07:07 -0700, Troy Dawson wrote:
> On Fri, Sep 2, 2022 at 10:55 AM Davide Cavalca via epel-devel <
> epel-devel@lists.fedoraproject.org> wrote:
>
> > On Thu, 2022-09-01 at 12:12 -0500, Maxwell G via epel-devel wrote:
> > > I t
2023-01-31T14:05:11Z David Moreau-Simard :
Hi,
Answer in-line but I also want to extend an invititation to everyone here
to join #ansible-packaging on libera.chat (or #packaging:ansible.com on
Matrix) which is a low signal-to-noise ratio channel to talk about
Ansible packaging things such
2023-01-31T13:02:09Z Sagi Shnaidman :
Hi, Orion
Thanks for raising this question.
I use both ways - either ansible distro with all-inclusive, or ansible
(distro or "core") with specific collection installed separately when I
need a newer version of collection, for example. I wonder if it's
ith newer ansible-core versions.
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/They
___
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.
ported content. You should open a ticket
on the pagure.io/epel tracker once you have a concrete proposal.
[1]: https://docs.fedoraproject.org/en-US/epel/epel-policy-retirement/
[2]: https://pagure.io/epel/pull-request/213
[3]:
https://docs.fedoraproject.org/en-US/ep
ct? Its seems not to be a "module" problem
> otherwise it would not install the epel version at all, right?
Have you tried adding `module_hotfixes=true` [1] to the EPEL repo
configuration file (/etc/yum.repos.d/epel.repo IIRC)?
[1]: https://dnf.readthedocs.io/en/latest/modularity.htm
perl_version} is
passed to the script as an argument, because the script of course
doesn't have access to the RPM context. This can be any executable
written in any language, but it should be straightforward to do this in
shell.
[1]:
https://rpm-software-management.github.io/rpm/manual/dep
know if you have any questions.
[1]: https://docs.fedoraproject.org/en-US/epel/epel-package-request/
--
Best,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to e
etween the issue tracker and the ML, so I'm -1 to also adding the
forums. In general, I find it easier to keep up with and participate in
discussions on mailing lists than on forums. However, it seems to me
that this is just for this one proposal, so I guess my comment is off
topic.
--
Best,
Max
On Thu Oct 6, 2022 at 19:11 +0200, Neal Gompa wrote:
> The cmake3 package has all the macros from the mainline cmake package in
> Fedora.
>
> It should be fully compatible, just swap %cmake_* for %cmake3_*.
Oops, I responded before I saw this.
--
Maxwell G (@gotmax23)
Pronouns
On Thu Oct 6, 2022 at 12:02 CDT, Michel Alexandre Salim wrote:
> I'm not sure either Paul or myself really care enough about EL7 to
> maintain a divergent spec.
The %cmake3* macros work everywhere.
--
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
Description: PGP sig
nflict with each other.
--
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
Description: This is a digitally signed message part.
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email
would have keep to modular repository available
forever.
Probably the idea of the notice is not worth of it.
I think it's worth adding notices to the module descriptions. We could
also add scriptlets to the old modular packages to print warnings if we
really wanted.
--
Best,
Maxwell G (@gotmax23
ages as long as they don't conflict with anything in
RHEL. EPEL packages may conflict with other EPEL packages, however.
--
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
Description: This is a digitally signed message part.
___
epel-devel
.
3. The maintainers won't have to remember to do it.
4. If we find out that a package is buildroot only, then we'll close the bug
and exclude it from the automatic retiring.
--
Best,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
___
epel
e probably not available for python38. If you want to
support lutris on EPEL 8, you'd have to package up the dependencies. However,
I'd recommend targeting python39 instead of python38. If you're interested in
doing that, I'd be happy to provide some more pointers.
--
Thanks,
Maxwell G (@gotmax
ure/new_issue
-
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
Description: This is a digitally signed message part.
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to
multiple ways to build against
packages that have not yet reached stable.
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
Description: PGP signature
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe
s://pagure.io/api/0/#issues-tab
According to the documentation, the only valid inputs to "Update issue
information" are "title" and "issue_content". https://pagure.io/pagure/issue/
4761 was opened for this and never closed. Is there some undocumented
parame
On Wednesday, August 10, 2022 4:07:29 PM CDT Troy Dawson wrote:
> On Sun, Aug 7, 2022 at 12:31 PM Kevin Fenzi wrote:
> > On Sat, Aug 06, 2022 at 10:05:40PM +0200, Maxwell G via epel-devel wrote:
> > > We could create an issue tracker for this. Packagers would have to
>
rvice manner, but I
don't think that's a huge deal for our case.
[1]:
https://docs.fedoraproject.org/en-US/fesco/Policy_for_orphan_and_retired_packages/#_orphaning_and_retiring_packages
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
si
es/FEDORA-EPEL-2022-5e2dae8961
[1]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-781937ed73
Out of all of the packages, only python38-itsdangerous-epel FTBFS, and I
filed [2] for that one.
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=2109363
--
Thanks,
Maxwell G (@gotmax23)
Pro
Hi everyone,
The weekly EPEL Steering Committee meeting is scheduled for today at 20:00 UTC
(4:00 p.m. EDT for those in the U.S.). It will take place in #fedora-meeting on
Libera.chat and bridged to #meeting:fedoraproject.org on Matrix.
Hope to see you all there!
--
Thanks,
Maxwell G
n testing that needs to be synced with some
upcoming updates in c8s in order to avoid an FTI, and I don't want the
karma to be reset.
I'm already handling the go rebuild, but I wouldn't mind handling this
one as well.
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
Descrip
ck if CRB is actually enabled would allow us to
create a scriptlet for epel-release to print a warning instructing users to
run `crb enable` if necessary.
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
Description: This is a
On Tuesday, June 14, 2022 5:26:11 PM CDT Richard Shaw wrote:
> I think the non-response maintainer process should be started.
It seems that someone has already done just that:
https://pagure.io/fesco/issue/2808
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
Descript
cfiles using the %include macro. This way, you can
easily
create a script to update virtual provides for bundled go packages without
having to copy/paste text into the specfile. This also keeps your specfile
cleaner. If anyone is interested, feel free to look at moby-engine for an
of containerd, its unbundled go dependencies, and moby-engine
(bundled go package). Long term, I'm not sure I'll have the time or the
interest to maintain these packages. Note that on EPEL 7, containerd bundles
its dependencies; moby-engine is not packaged there.
--
Thanks,
Maxwell G (@gotmax23
modify it all. Am I missing something or are we talking
about different things?
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
Description: This is a digitally signed message part.
___
epel-devel mailing list -- epel
CLJH3QPXWNZGNTG3KIQHFZB4WFVOAN/
#S57EJSNCP6YOY7QXGGI4NATDR2FKQZWO
--
Maxwell G
Pronouns: He/Him/His
gotmax@e.email
signature.asc
Description: This is a digitally signed message part.
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe
pel-release/pull-request/21
[2]: With my ansible hat on, it also doesn't help that the two most popular
epel roles on Ansible Galaxy don't enable CRB/Powertools, but I disgress.
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
De
On Tuesday, May 24, 2022 12:53:36 PM CDT Maxwell G via epel-devel wrote:
> I think it's better to add `Requires:
> python%{python3_pkgversion}-rpm-macros`.
> To be fair, they both do effectively the same thing: set %__python3 to the
> correct value. In any case, I submit
Let's see
what the RHEL Python maintainers have to say... As far as I know, `%
{py38_dist}` doesn't exist at all.
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
Description: This is a digitally signed message part.
___
epel-deve
; are you referring to?
> And the goal for some of us is to have one spec file
> work across all currently supported releases.
I agree; divergent dist-git branches are a nuisance.
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
Description: This is a digi
(also X11))', 'SGI-B-2.0', 'SGI-B-2.0', 'SMLNJ',
> 'MIT-enna', 'MIT-feh', 'mpich2']
>
> mpich2 or GPL-1.0-only
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
Description: This is a digitally signed message part.
___
epel
eck
> %{__python3} setup.py test
I was going to suggest using `%pytest`, but then I remembered that https://
pagure.io/releng/issue/10679 is still outstanding :(.
> %files -n python38-%{srcname}
[...]
> %{python3_sitelib}/*
Globs like this are against the Python Packaging Guidelines.
-
May 16, 2022 8:32:58 PM Maxwell G :
On Tuesday, April 19, 2022 3:14:56 PM CDT Kevin Fenzi wrote:
> In epel8 I will be converting the 'ansible' epel8 package into the
> upstream ansible-5 meta collections package (which also pulls in
> ansible-core).
>
Hi everyone,
I have reb
ay around?
>
Well, in this case, the issue is that ansible-core bumped its minimal Python
version requirement for the controller to 3.8. They had no choice but to build
it for a non-default Python version.
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
the tests/nose
> dep).
Unless you are planning to remove python3-passlib (the python36 version) or
make it a modular package, I think it is better to just create a new SRPM named
python38-passlib with no subpackages.
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
s
ps the EPEL SIG can create some policy or provide some docs about this
process?
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
Description: This is a digitally signed message part.
___
epel-devel mailing list -- epel-devel@list
lection-* RPM packages or from Ansible
Galaxy. If you would like to do this, you can switch to ansible-core with `dnf
swap ansible ansible-core`.
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His
signature.asc
Description: This is a digitally signed message part.
__
49 matches
Mail list logo
