/44304
[2] https://youtu.be/PxWxK5PgUuE
[3]
https://lists.centos.org/hyperkitty/list/de...@lists.centos.org/thread/QCO73CKFMPNMERUWIQ47OVJMMUM7YUXU/
[4] https://flocktofedora.org/
--
Carl George
--
___
epel-devel mailing list -- epel-devel
> 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
> Do not reply to spam, report it:
> http
ct/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
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
Hello,
Corresponding to the end of life (EOL) of CentOS Stream 8 [0], EPEL 8
Next is also now EOL. EPEL 8 will continue to be available until the
EOL of RHEL 8 on 2029-05-31 [1].
Regards,
Carl George on behalf of the EPEL Steering Committee
[0]
https://lists.centos.org/hyperkitty/list/annou
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.o
edoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
We discussed this today at the EPEL Steering Committee meeting.
https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-05-15/epel.2024-05-15-18.00.html
/VIP6GZFVNFRC2MZUB6OUEDF2SSW4BBVI/
[2] https://github.com/klee/klee/blob/v3.0/.github/workflows/build.yaml#L39
[3] https://github.com/klee/klee/pull/1648
[4] https://github.com/klee/klee.github.io/pull/347
[5]
https://src.fedoraproject.org/rpms/klee/c/35fdedce2021112b996a9d38bf3e93cf5cf236c8
--
Carl George
Closing the loop here, I've retired klee in EPEL 9.
https://lists.fedoraproject.org/archives/list/epel-annou...@lists.fedoraproject.org/thread/SP2624QZPY33N3NZNX5QLSMO2HZBHNNQ/
On Fri, Sep 29, 2023 at 12:01 PM Kevin Fenzi wrote:
>
> On Thu, Sep 28, 2023 at 10:37:28PM -0500, Carl George
.
https://docs.fedoraproject.org/en-US/epel/epel-policy-retirement/#process_no_time_or_desire
Here is a general guide for requesting packages in EPEL (tldr; file a bugzilla).
https://docs.fedoraproject.org/en-US/epel/epel-package-request/
--
Carl George
___
epel-devel mai
[4] https://docs.fedoraproject.org/en-US/epel/epel-policy-retirement/
--
Carl George
___
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
but please centralize your
feedback on the Discussion thread.
https://discussion.fedoraproject.org/t/revisting-conflicts-policy-for-epel-compat-packages/90605
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubs
On Thu, Aug 24, 2023 at 1:44 AM Carl George wrote:
>
> I am performing an incompatible upgrade of the caddy package in EPEL
> 9. In accordance with the incompatible upgrade policy [0], I proposed
> this upgrade just over a week ago on the epel-devel mailing list [1].
> For r
/caddyserver/caddy/releases/tag/v2.5.0
[4] https://github.com/caddyserver/caddy/releases/tag/v2.6.0
[5] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-8849a14e7f
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
-centos
[3] https://copr.fedorainfracloud.org/coprs/g/caddy/caddy/
[4] https://caddyserver.com/docs/v2-upgrade
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le
-0b57e19163
--
Carl George
___
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
/caddy/
[7] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-0b57e19163
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code
bugs.
Package maintainers can create branches with fedpkg, e.g. `fedpkg
request-branch epel9`.
https://docs.fedoraproject.org/en-US/epel/fedora-package-in-epel/
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to
___
> 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: htt
only be exploited by someone with write access to the
> > > filesystem
> > > > > boots, that is, root. Only with setuid-root apptainer/singularity
> > > does it
> > > > > become a privilege escalation.
> > > > > >
> > > &g
On Thu, Apr 27, 2023 at 10:20 AM Dave Dykstra via epel-devel
wrote:
>
> On Thu, Apr 27, 2023 at 02:11:46AM -0500, Carl George wrote:
> > On Wed, Apr 26, 2023 at 11:20 AM Dave Dykstra via epel-devel
> ...
> > > The summary of the CVE is that the way that apptainer & si
le update across all three platforms, especially
this late in the RHEL 7 lifecycle.
> install the rpm on RHEL8 & 9 directly from github, and it would not
> be good to have different behavior when installed from EPEL.
>
> Dave
>
>
> On Thu, Apr 27, 2023 at 02:42:13A
> 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
> Do not reply to spam, report it:
>
update in
> EPEL so the RHEL version can have a higher version and release.
> When RHEL . is released, EPEL automation will remove
> from EPEL and close this bug.
>
>
> On Tue, Mar 28, 2023 at 9:14 AM Carl George wrote:
>
>> I'm also late to the party with this feedb
oraproject.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_g
On Wed, Mar 8, 2023 at 9:43 AM Troy Dawson wrote:
>
>
>
> On Wed, Mar 8, 2023 at 6:31 AM Troy Dawson wrote:
>>
>> On Tue, Mar 7, 2023 at 7:16 PM Carl George wrote:
>>>
>>> On Tue, Mar 7, 2023 at 2:18 PM Troy Dawson wrote
>>> >
>>
On Tue, Mar 7, 2023 at 2:18 PM Troy Dawson wrote:
>
>
>
> On Tue, Mar 7, 2023 at 11:38 AM Carl George wrote:
>>
>> On Tue, Mar 7, 2023 at 8:52 AM Troy Dawson wrote:
>> >
>> > On Mon, Mar 6, 2023 at 8:48 PM Carl George wrote:
>> >>
&
On Tue, Mar 7, 2023 at 8:52 AM Troy Dawson wrote:
>
> On Mon, Mar 6, 2023 at 8:48 PM Carl George wrote:
>>
>> On Fri, Mar 3, 2023 at 5:42 AM Daniel P. Berrangé
>> wrote:
>> >
>> >
>> > There is also the case of the RHEL rebuilds whose us
ail 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/ep
ist -- 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 Archiv
el@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:
am.com/dberrange :|
> ___
> 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://doc
es/list/epel-devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel
://docs.fedoraproject.org/en-US/epel/epel-policy-retirement/#process_package_in_rhel
--
Carl George
___
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
-US/epel/epel-policy-retirement/#process_package_in_rhel
--
Carl George
___
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
On Wed, Nov 23, 2022 at 2:27 PM Maxwell G via epel-devel
wrote:
>
> On Wed Nov 23, 2022 at 00:52 CST, Carl George wrote:
> > I would also ask that feedback be provided there instead of as email
> > replies here on the list.
>
> I don't think there's been a formal disc
this thread on the Fedora Discussion site for the full proposal.
https://discussion.fedoraproject.org/t/epel-10-proposal/44304
I would also ask that feedback be provided there instead of as email
replies here on the list.
--
Carl George
___
epel-devel mailing
inary
relationship.
https://packages.fedoraproject.org/pkgs/webkitgtk/webkit2gtk4.0/
Whichever way you discover the source name, use that as the component
for your bugzilla request.
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora=webkitgtk
--
Carl George
__
> 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 Gui
. To avoid hard
dependencies on the tools I wrap the commands in an if statement that
checks for the relevant binary.
https://src.fedoraproject.org/rpms/caddy/blob/rawhide/f/caddy.spec#_232-250
Grepping through other spec files I see a quite a few other examples
of setsebool and semanage commands in script
the exception flag because it would fall under the second bullet
point for exceptions.
https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/#_package_review_process
If the package is intended to be EPEL-only, make sure to retire the
rawhide branch.
--
Carl George
___
ps://bugzilla.redhat.com/show_bug.cgi?id=2098360
>
> On 2022-06-17 16:28, Carl George wrote:
> > On Fri, Jun 17, 2022 at 8:31 AM Alex Talaran wrote:
> >>
> >> would anyone be willing to package this in epel or help get it in the
> >> existing package please?
&g
chroot as an explicit argument. Instead of making the majority of
users do `dnf copr enable epel-9-`, why can't we have a
tiny number of users do `dnf copr enable
centos-stream-9-` and have the plugin guess the correct thing
for the majority of users?
[0] https://bugzilla.redha
t are disabled in the RHEL spec file. Similar to the previous
option, this would be EPEL-only and would be allowed because the srpm
and rpm names don't conflict with RHEL.
- Rebuild the Fedora spec file with all subpackages somewhere where
replacing base packages is allowed, such as a copr or a CentOS
On Fri, Jun 17, 2022 at 8:33 AM Troy Dawson wrote:
>
>
>
> On Thu, Jun 16, 2022 at 10:22 PM Carl George wrote:
>>
>> On Wed, Jun 15, 2022 at 5:12 PM Troy Dawson wrote:
>> >
>> > I'm totally top-posting, and I apologize for that.
>> >
>&g
to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
I think it would be nice to be able to both enable and disable from
the same script. This would come in handy when you are looking for
things that don't install when crb is disabled. I don't see a
This would allow epel-release to recommmend
centos-release-crb. There was push back to this idea because there is
a desire for the "enable crb" action in CentOS Stream to look roughly
similar to how it works in RHEL (`dnf config-manager --set-enabled
crb` and `subscription-manager rep
On Wed, Apr 13, 2022 at 5:05 PM Carl George wrote:
>
> On Fri, Apr 8, 2022 at 5:17 PM Troy Dawson wrote:
> >
> >
> >
> > On Fri, Apr 8, 2022 at 3:00 PM Sérgio Basto wrote:
> >>
> >> On Fri, 2022-04-08 at 13:08 -0700, Troy Dawson wrote:
> >&
t; List Archives:
> https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
This was approved [0] in today's EPEL Steering Committee meeting.
Please continue with the proc
On Fri, Apr 8, 2022 at 2:23 AM Nick Howitt via epel-devel
wrote:
>
>
>
> On 08/04/2022 04:38, Carl George wrote:
> > On Thu, Apr 7, 2022 at 7:33 PM Gemneye via epel-devel
> > wrote:
> >>
> >>>>
> >>>> Error: Package: hwinfo-21.68-
Obviously that's not what happened
here. The quickest fix is to rebuild hwinfo against the new soname.
I did that for EPEL8 a few days ago, and just submitted the EPEL7 one
now. Follow along in the bugzilla for future updates.
[0] https://bugzilla.redhat.
fedoraproject.org/archives/list/de...@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
This update changes a library soname, which makes it an incompatible
upgrade. It must follow the EPEL incompatible upgrades policy [0
n-US/fesco/Policy_for_nonresponsive_package_maintainers/
--
Carl George
___
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/pr
On Thu, Mar 24, 2022 at 5:50 PM Kevin Fenzi wrote:
>
> On Wed, Mar 23, 2022 at 09:18:08PM -0500, Carl George wrote:
> > On Wed, Mar 23, 2022 at 2:54 PM Carl George wrote:
> > >
> > > Typically EPEL inherits policy from Fedora, diverging when necessary.
> >
On Wed, Mar 23, 2022 at 2:54 PM Carl George wrote:
>
> On Mon, Mar 14, 2022 at 4:23 PM Troy Dawson wrote:
> >
> >
> >
> > On Thu, Mar 10, 2022 at 2:17 PM Diego Herrera wrote:
> >>
> >> I've been checking the packages that won't install on EPEL
uld strictly forbid any dependency on HA or RS packages, because
that would require unnecessary duplication of HA/RS packages in EPEL
(which is allowed, but shouldn't be required IMO). I suggest a
compromise that we can make the policy:
"All EPEL package dependencies (build-time or run
/epel with all your EPEL questions.
https://discussion.fedoraproject.org/t/join-us-for-the-epel-office-hours-every-month/37235
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le
a-infrastructure
Closing the loop here, at the 2021-11-24 EPEL Steering Committee
meeting we voted and selected plan C.
https://meetbot.fedoraproject.org/teams/epel/epel.2021-11-24-21.00.html
We are in the process of finishing up the EPEL9 implementation and
plan to launch EPEL9 and EPEL9 Next together
email to epel-devel
beforehand to avoid a quick retire/unretire churn for the packages
other maintainers are interested in keeping around.
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to ep
dora-infrastructure
Agreed, for quick local builds it's fine to use epel8-next (c8s) to
verify it builds and then submit the koji build to the epel8 (rhel8)
target. If the local build works but the koji build doesn't, you
likely have a candidate for an official epel8-next koji build.
--
Carl George
he architectures that
EPEL does. As far as I can tell, the three most popular (Alma, Rocky,
Oracle) only offer x86_64 and aarch64 but are missing ppc64le and
s390x. That said CentOS Linux 8 doesn't offer s390x either, so we
already have this problem, but switch the EPEL mock chro
epel9 branches before building.
Plans B and C are more like the status quo, where packagers target
epel9, and do individual package rebuilds as needed after a RHEL minor
release.
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.
il 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/e
rastructure
Thanks everyone for the feedback so far. I would still like to talk
with the Fedora Infra folks in a bit more depth about the difficulty
level of each plan, but at this point in time I feel like plan C is
the best option because of the benefits.
- simple instructions to maintainers
-
t.org/archives/list/epel-devel@lists.fedoraproject.org
> > Do not reply to spam on the list, report it:
> > https://pagure.io/fedora-infrastructure
> ___
> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> To unsubscribe send
go with Plan B or C we will need to make the decision
> > fairly quickly.
>
> I like A. ;)
>
> I think B is risky because of the possible changes between beta and ga,
> and I think C is breaking the 'we build against rhel' implied promise as
> well as leaving
On Fri, Sep 24, 2021 at 3:05 PM Josh Boyer wrote:
>
> On Fri, Sep 24, 2021 at 4:02 PM Neal Gompa wrote:
> >
> > On Fri, Sep 24, 2021 at 3:59 PM Josh Boyer wrote:
> > >
> > > On Fri, Sep 24, 2021 at 3:46 PM Ken Dreyer wrote:
> > > >
> > > > Hi folks,
> > > >
> > > > The RHEL 9 composes do not
/wiki/EPEL_incompatible_upgrades_policy
https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Package_maintenance_and_update_policy
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email
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
> Do not reply t
://fedoraproject.org/wiki/EPEL_Next
--
Carl George
___
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
-2021-c0fcb78eb0
[5] https://fedoraproject.org/wiki/EPEL_Next#FAQ
[6] https://fedoraproject.org/wiki/EPEL_Next#Example_Workflow
On Tue, Sep 8, 2020 at 11:00 PM Carl George wrote:
>
> Howdy folks,
>
> A large part of my day job is working on CentOS Stream. Naturally I would
> like it t
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
--
Carl George
_
t Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
--
Carl George
___
, and would be happy to see them go away when
python34 is retired (which can happen independently of python3.9).
On Wed, Apr 7, 2021 at 2:36 AM Miro Hrončok wrote:
>
> On 07. 04. 21 4:50, Carl George wrote:
> > What do you mean by support? The only thing EPEL supports (using the
>
project.org/archives/list/epel-devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe
the guideline in place for package reviews to reference, to
prevent any further packages using non-standard prefixes from being
added.
On Thu, Jan 21, 2021 at 11:28 AM Kevin Fenzi wrote:
>
> On Thu, Jan 21, 2021 at 12:19:39AM -0600, Carl George wrote:
> > Howdy folks,
> >
> >
this purpose.
On Thu, Jan 21, 2021 at 4:57 AM Andrew C Aitchison
wrote:
>
>
> On Thu, 21 Jan 2021, Carl George wrote:
>
> > RHEL7 ships Python 3.6 packages using the python3 prefix. Currently
> > EPEL7 contains Python 3.6 packages using both the python3 and python
Agreed. And if a maintainer decides to stick with the python36 name,
they MUST provide the equivalent python3 name. I've captured those
for what I'll add to the guidelines.
On Thu, Jan 21, 2021 at 4:30 AM Miro Hrončok wrote:
>
> On 21. 01. 21 7:19, Carl George wrote:
> > I pro
, 2020 at 11:12:28PM -0500, Carl George wrote:
> > Here is my rough outline of the steps required to implement this proposal.
> > I imagine things would happen roughly in this order, but some things could
> > probably take place in parallel.
> >
> > 1. EPEL Steering C
in bodhi
9. document in the wiki
10. announcement email
Please let me know if I'm missing anything.
On Wed, Sep 23, 2020 at 8:43 PM Carl George wrote:
>
> I agree, using .el8.next for the dist macro makes the most sense. This will
> enable maintainers to use a similar workflow
:
>
> On Wed, Sep 16, 2020 at 09:54:00PM -0500, Carl George wrote:
> > At the EPEL Steering Committee last week, we had an extensive discussion of
> > this proposal, specifically focused on how to handle the dist macro. I
> > believe these are the possible choices.
>
s
> List Archives:
> https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedorapro
getting
published without review would degrade the experience for CentOS Stream
users. We could do a lower karma/time threashold than regular EPEL if
desired.
On Wed, Sep 9, 2020 at 11:55 AM Kevin Fenzi wrote:
>
> On Tue, Sep 08, 2020 at 11:00:42PM -0500, Carl George wrote:
> > Howdy f
uot;Eee pee
> cee ess")
>
> --
> Ben Cotton
> He / Him / His
> Senior Program Manager, Fedora & CentOS Stream
> Red Hat
> TZ=America/Indiana/Indianapolis
> ___
> epel-devel mailing list -- epel
>
> On Wed, Sep 9, 2020 at 5:51 AM Petr Pisar wrote:
> >
> > On Tue, Sep 08, 2020 at 11:00:42PM -0500, Carl George wrote:
> > > To solve this problem, I am proposing that we create a new repository
> > > called
> > > EPEL 8 Next.
> > >
> >
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 Arch
this idea at the last EPEL Steering Committee meeting, and
we plan to discuss it again during the next one. Please share your thoughts
on this proposal.
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send
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
--
Carl George
_
aproject.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
--
Carl
This update has been submitted to stable.
On Thu, May 28, 2020 at 12:53 PM Carl George wrote:
>
> Greetings,
>
> Per the EPEL incompatible upgrades policy [0], this is an announcement of a
> backwards incompatible update [1] of oniguruma in EPEL 7. This change was
> ap
://meetbot.fedoraproject.org/teams/epel/epel.2020-05-22-21.04.html
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1777660
[4] https://bugzilla.redhat.com/show_bug.cgi?id=1836692
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
:~]# repoquery --quiet --disablerepo \*
--queryformat '%{name}' --archlist src --enablerepo
epel-source,epel-testing-source --whatrequires oniguruma-devel
jq
```
Let me know your thoughts and concerns about moving forward with this.
--
Carl George
___
epel
sewhere.
>
> Thanks,
>
> --
> Michel Alexandre Salim
> profile: https://keybase.io/michel_slm
> chat via email: https://delta.chat/
> GPG key: 96A7 A6ED FB4D 2113 4056 3257 CAF9 AD10 ACB1 BEF2
> ___
> CentOS-devel mailing list
> cento
..@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.fe
ubscribe 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
>
> What day and time would people like?
> If you haven't been able to come to the meeting due to the time, what
> would be best for you?
>
> Troy
>
--
Carl George
___
epel-devel mailing list -- epel-devel@lists.fedorapr
Thanks for the feedback Neal. I have submitted the update.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-93f737b65e
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to
To facilitate packages that require a newer version of libsodium, I have
coordinated an update of libsodium in EPEL7 from version 1.0.5
(libsodium.so.13) to version 1.0.16 (libsodium.so.23). To avoid any ABI
breakage for existing packages, a new libsodium13 compatibility package has
been
(such as python34u). Currently our python3* packages
all conflict with each other. We have an open request to allow multiple
version of our python3* packages by using update-alternatives [0]. We may or
may not implement it, but it is another option that the EPEL might want to
consider.
- Carl
...@iuscommunity.org
ius-core...@lists.launchpad.net
Community members:
ius-commun...@lists.launchpad.net
Carl George
Rackspace GNU/Linux Engineer
From: Rahul Sundaram [methe...@gmail.com]
Sent: Friday, August 29, 2014 07:38 PM
To: EPEL Development List
Cc: core
99 matches
Mail list logo
