[EPEL-devel] Re: Getting %ldconfig_scriptlets in CentOS 7

On Fri, Sep 17, 2021 at 2:57 PM Mikhail Ramendik wrote: > > On Fri, 17 Sept 2021 at 15:08, Sérgio Basto wrote: > > >> WIth an unmodified .spec file, he gets a message that >> the %ldconfig_scriptlets macro is unknown, or else he gets it built but >> not linked and so not running. He had to add

[EPEL-devel] Re: [CentOS-devel] Updated KDE Plasma Desktop ready for testing on CentOS Stream 8

fedoraproject.org/metalink?repo=epel-next-$releasever=$basearch > > > > Hope this helps. > > Troy > > > > On Wed, Jul 28, 2021 at 3:13 AM Massi aka Ergosum > > > > wrote: > > > >> Il giorno mar 27 lug 2021 alle ore 17:24 Troy Dawson

[EPEL-devel] Re: Updated KDE Plasma Desktop ready for testing on CentOS Stream 8

Pull request with a fix. https://github.com/mbugni/centos-remix/pull/2 I have tested this, and verified that it works, and that when you do a "dnf update" after, nothing needs to be updated. Troy On Wed, Jul 28, 2021 at 8:25 AM Troy Dawson wrote: > First off, thank

[EPEL-devel] Re: proposed recommendation - missing devel packages

to break this out from a question in the FAQ to it's own page. Troy On Wed, Sep 22, 2021 at 8:42 PM Orion Poplawski wrote: > On 7/1/21 4:05 PM, Troy Dawson wrote: > > I believe this is a recommendation, versus a policy. > > I wanted to get people's thoughts on it, and if ya'

[EPEL-devel] Re: python-gevent and pytest-cov in el9

On Fri, Sep 24, 2021 at 1:03 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

[EPEL-devel] Re: why ccache is not available on epel7 ?

It looks available to me [root@centos7 yum.repos.d]# yum list ccache ... Available Packages ccache.x86_64 3.7.7-1.el7 epel Possibly you have an exclude on one of your configurations? Troy On Fri, Oct 8, 2021 at 6:55 AM Sérgio Basto wrote: >

[EPEL-devel] Won't be at weekly EPEL meeting

I'm sorry for sending this via email, I should have said something at the last EPEL Steering Committee meeting. I will not be available at this weeks (Wed Sept. 29) EPEL Steering Committee meeting. Does someone else want to run the meeting? Or do we want to cancel it this week? Troy

[EPEL-devel] Re: [Fedocal] Reminder meeting : EPEL Steering Committee

Just a reminder, I won't be there this week. If you want to have it anyway, someone should start the meeting. #topic Old Business - epel9-next #topic EPEL-7 #topic EPEL-8 #topic EPEL-Packaging-SIG #topic General Issues / Open Floor Troy On Tue, Sep 28, 2021 at 9:00 AM wrote: > Dear all, > >

[EPEL-devel] Re: gfal2-util -> python3-gfal2-util upgrade path

Would you mind opening a bugzilla with this information. The epel package maintainers for gfal2 way, or may not, be monitoring the epel-devel mailing list. On Fri, Oct 1, 2021 at 8:06 AM Carl Edquist wrote: > Dear EPEL Devs, > > We ran into an issue on el7 attempting to upgrade from gfal2-util

[EPEL-devel] Re: To buildroot, or not to buildroot

*this is worth a discussion in todays EPEL Steering Committee Meeting* It sounds like the epel9-next is going to startup by building against the CS buildroot. Changing it at this time would cause a delay. Thus we need to write some "verify build deps are released" checker. I have an idea of

[EPEL-devel] Re: To buildroot, or not to buildroot

On Thu, Oct 7, 2021 at 6:28 AM Neal Gompa wrote: > On Thu, Oct 7, 2021 at 9:24 AM Troy Dawson wrote: > > > > > > > > On Wed, Oct 6, 2021 at 7:39 PM Neal Gompa wrote: > >> > >> On Wed, Oct 6, 2021 at 3:36 PM Troy Dawson wrote: > >> > &

[EPEL-devel] Re: To buildroot, or not to buildroot

On Wed, Oct 6, 2021 at 7:39 PM Neal Gompa wrote: > On Wed, Oct 6, 2021 at 3:36 PM Troy Dawson wrote: > > > > *this is worth a discussion in todays EPEL Steering Committee Meeting* > > > > It sounds like the epel9-next is going to startup by building against &g

[EPEL-devel] To buildroot, or not to buildroot

This was originally "python-gevent and pytest-cov in el9" But I wanted to talk about and discuss this paragraph from Carl on it's own. On Fri, Sep 24, 2021 at 7:43 PM Carl George wrote: > On a related note, EPEL 9 Next _is_ being set up to build against the > CentOS Stream 9 buildroot. This

[EPEL-devel] KDE Plasma Desktop in EPEL 8 has been updated

RHEL 8.5 updated qt5 from 5.12 to 5.15. This allowed us to update the KDE Plasma Desktop in epel 8 to the latest version, per the update schedule[1]. That update is complete, tested and pushed to epel stable. ** New Versions qt5 - 5.15 (5.15.2 mainly) plasma - 5.23.3 kf5 - 5.88 ** Known Bugs -

[EPEL-devel] EPEL 9 is now available

On behalf of the EPEL Steering Committee, I’m pleased to announce the availability of EPEL 9. This is the culmination of five months of work between the EPEL Steering Committee, the Fedora Infrastructure and Release Engineering team, and other contributors. Package maintainers can now request

[EPEL-devel] Re: [Fedocal] Reminder meeting : EPEL Steering Committee

Just a reminder, that there will not be a EPEL Steering Committee Meeting this week, or next week. We will talk to ya'll in the new year on January 5, 2022 On Tue, Dec 21, 2021 at 10:00 AM wrote: > Dear all, > > You are kindly invited to the meeting: >EPEL Steering Committee on 2021-12-22

[EPEL-devel] Re: [Fedocal] Reminder meeting : EPEL Steering Committee

No meeting this week. See you on January 5, 2022 On Tue, Dec 28, 2021 at 8:00 AM wrote: > Dear all, > > You are kindly invited to the meeting: >EPEL Steering Committee on 2021-12-29 from 16:00:00 to 17:00:00 > US/Eastern >At fedora-meet...@irc.libera.chat > > The meeting will be about:

[EPEL-devel] Re: EPEL9 Rollout Proposals

On Thu, Nov 18, 2021 at 1:04 PM Mohan Boddu wrote: > On Thu, Nov 18, 2021 at 2:32 PM Troy Dawson wrote: > > > > In our last EPEL Steering Committee meeting, Carl brought up a new > proposal for our epel9 / epel9-next rollout. Sometimes IRC isn't the best > way t

[EPEL-devel] Re: Plan for EPEL-9

Looks like not yet. My branch requests are also getting rejected. On Wed, Nov 17, 2021 at 10:35 AM Miro Hrončok wrote: > On 09. 11. 21 16:07, Troy Dawson wrote: > > The people on the rel-eng team that do the branches need to have their > > fedscm-admin updated with the correc

[EPEL-devel] Re: Plan for EPEL-9

I'd say open a ticket. At this point, I don't know what the status is. Some step(s) have not been done. On Wed, Nov 17, 2021 at 10:44 AM Miro Hrončok wrote: > On 17. 11. 21 19:41, Troy Dawson wrote: > > Looks like not yet. My branch requests are also getting rejected. > > I s

[EPEL-devel] Re: EPEL 9 Next Bodhi updates: Set lower days to stable limit?

On Fri, Nov 19, 2021 at 8:46 AM Stephen John Smoogen wrote: > On Fri, 19 Nov 2021 at 11:42, Miro Hrončok wrote: > > > > Hello EPEL people, > > > > what do you think about setting the Bodhi days to stable limit to 3 days > for > > EPEL 9 Next (at least until RHEL 9 GA)? > > > > I think EPEL-9

[EPEL-devel] KDE Status in EPEL8

for all the packages to be rebuilt, as long as the builders co-operate. We expect the packages to be in epel8-testing by Monday, November 15. Thank you for your patience. Troy Dawson ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org

[EPEL-devel] Re: RFC: generating openssl3 packages from openssl spec

On Wed, Nov 10, 2021 at 8:38 AM Michel Alexandre Salim < mic...@michel-slm.name> wrote: > On Tue, 2021-11-09 at 19:40 -0500, Neal Gompa wrote: > > On Tue, Nov 9, 2021 at 7:38 PM Michel Alexandre Salim > > wrote: > > > > > > Hi all, > > > > > > Per

[EPEL-devel] KDE Plasma Desktop in EPEL 8 has been updated

RHEL 8.5 updated qt5 from 5.12 to 5.15. This allowed us to update the KDE Plasma Desktop in epel 8 to the latest version, per the update schedule[1]. That update is complete, tested and pushed to epel stable. ** New Versions qt5 - 5.15 (5.15.2 mainly) plasma - 5.23.3 kf5 - 5.88 ** Known Bugs -

[EPEL-devel] Re: [Fedocal] Reminder meeting : EPEL Steering Committee

We have three topics that may, or may not take alot of time. So we'll have a different agenda this week. 1 - Mock config, which repo do we use for the default epel config. https://pagure.io/epel/issue/133 (This has had some pretty good discussion on the issue itself, it's possible this will be

[EPEL-devel] Re: EPEL9 Rollout Proposals

On Fri, Nov 19, 2021 at 2:16 PM Miroslav Suchý wrote: > Dne 18. 11. 21 v 20:31 Troy Dawson napsal(a): > > - epel9-next stays the way it is currently setup. > > Ehm, what is the current setup? > > Sorry about that. You are correct. I didn't say how epel9-next is currently s

[EPEL-devel] Re: can't install synergy on CentOS/Rocky 8 ...

On Sun, Nov 21, 2021 at 6:51 AM KC wrote: > Hi, > > Just reporting that synergy installation fail on CentOS 8 & Rocky 8. > > > dnf install synergy > Last metadata expiration check: 4:17:16 ago on Sun 21 Nov 2021 06:28:05 PM > CST. > Error: > Problem: conflicting requests > - nothing provides

[EPEL-devel] Re: KDE Status in EPEL8

. -- This requires breeze-gtk, which is still being worked on to get it to work on epel8 Troy Dawson On Thu, Nov 11, 2021 at 3:19 PM Troy Dawson wrote: > The qt5 libraries in RHEL 8.5 are at a higher version than they were in > RHEL 8.4. > This is causing RHEL 8 machines that have the K

[EPEL-devel] Proposal for update to Stalled EPEL Requests policy

As I was writing examples for requesting EPEL packages, the wording of the Stalled EPEL Requests policy was bothering me. I have created a pull request to clarify a stalled request. https://pagure.io/epel/pull-request/129 It's not really a change in policy, just clarifying what I think we

[EPEL-devel] EPEL8 buildroot removed CentOS Devel repo

packages in that repo, please follow the steps in the EPEL Documentation[1]. Thank You Troy Dawson [1] - https://docs.fedoraproject.org/en-US/epel/epel-faq/#rhel_8_has_binaries_in_the_release_but_is_missing_some_corresponding__devel_package

[EPEL-devel] Re: Planning to add a "distribution" component to EPEL product in BZ

On Thu, Oct 28, 2021 at 1:29 PM Ben Cotton wrote: > On Thu, Oct 28, 2021 at 4:18 PM Troy Dawson wrote: > > > > Will we be able to add additional people, like a normal package, so that > we all get the emails? > > If we can, then I don't mind being the initial pers

[EPEL-devel] Re: Planning to add a "distribution" component to EPEL product in BZ

On Thu, Oct 28, 2021 at 1:02 PM Kevin Fenzi wrote: > On Thu, Oct 28, 2021 at 03:10:38PM -0400, Ben Cotton wrote: > > Hi folks, > > > > In a conversation with Carl George and Troy Dawson earlier this week, > > we discussed the possibility of creating a "distrib

[EPEL-devel] Re: Plan for EPEL-9

On Tue, Nov 9, 2021 at 6:31 AM Miro Hrončok wrote: > On 08. 11. 21 15:56, Troy Dawson wrote: > > > > On Mon, Nov 8, 2021 at 3:31 AM Neal Gompa > <mailto:ngomp...@gmail.com>> wrote: > > > > On Mon, Nov 8, 2021 at 2:18 AM Remi Collet >

[EPEL-devel] Re: Plan for EPEL-9

On Mon, Nov 8, 2021 at 3:31 AM Neal Gompa wrote: > On Mon, Nov 8, 2021 at 2:18 AM Remi Collet > wrote: > > > > As both RHEL-9 Beta and CentOS 9 Stream are available, > > what are the plan for EPEL-9 ? > > > > > > I really this should be available ASAP to be > > available to our users at GA

[EPEL-devel] KDE Plasma Desktop on epel9 plans

for your patience. Troy Dawson ___ 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

[EPEL-devel] Re: Is anyone still using EPEL8 Playground?

On Fri, Dec 10, 2021 at 10:21 AM Davide Cavalca via epel-devel < epel-devel@lists.fedoraproject.org> wrote: > On Fri, 2021-12-10 at 05:29 -0800, Troy Dawson wrote: > > We (The EPEL Steering Committee) are following up on EPEL issue > > 136[1] regarding the statu

[EPEL-devel] Re: Builds for EPEL9

On Sat, Dec 11, 2021 at 1:58 AM Frank Crawford wrote: > Folks, > > I'm looking at building a package that currently exists in EPEL8 for > EPEL9. I have a new branch epel9 branch for my package, but when I try > to do a mock build or scratch build it fails with the error: > > Error: Error

[EPEL-devel] Is anyone still using EPEL8 Playground?

get from epel8-next and/or COPR, please let us know. Otherwise we will shut it down and call it an interesting experiment. Troy Dawson on behalf of the EPEL Steering Committee [1] - https://pagure.io/epel/issue/136 ___ epel-devel mailing list -- epel

[EPEL-devel] Re: EPEL 9 Next Bodhi updates: Set lower days to stable limit?

Just want to say that this was discussed at the EPEL Steering Committee Meeting. Passed: epel9 will have 7 day and epel9-next will have 3 day waiting period in bodhi. 6 votes for, 0 votes against, 1 abstain This is valid until RHEL 9 GA. At that time the epel9-next will become the same as

[EPEL-devel] Re: python-unversioned-command for epel8 (provides /usr/bin/python)

On Thu, Jul 22, 2021 at 2:45 PM Miro Hrončok wrote: > On 22. 07. 21 22:33, Troy Dawson wrote: > > > > > > On Thu, Jul 22, 2021 at 12:50 PM Miro Hrončok > <mailto:mhron...@redhat.com>> wrote: > > > > On 22. 07. 21 21:47, Miro Hrončok wrote: >

[EPEL-devel] python-unversioned-command for epel8 (provides /usr/bin/python)

I've been bitten by this yet again. A package needing /usr/bin/python and not python2 or python3. And it's way down in the code so it's hard to patch. But, it works fine on Fedora. Is anyone in the middle of porting python-unversioned-command over to epel8? If not, does anyone object to me

[EPEL-devel] Re: python-unversioned-command for epel8 (provides /usr/bin/python)

On Thu, Jul 22, 2021 at 12:50 PM Miro Hrončok wrote: > On 22. 07. 21 21:47, Miro Hrončok wrote: > > On 22. 07. 21 21:25, Troy Dawson wrote: > >> I've been bitten by this yet again. A package needing /usr/bin/python > and > >> not python2 or python3. And it's way

[EPEL-devel] Updated KDE Plasma Desktop ready for testing on CentOS Stream 8

8 * kde-partitionmanager - would need a newer kpmcore Feel free to install and test. Troy Dawson [1] - https://fedoraproject.org/wiki/SIGs/KDE/EPEL#Installation ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send

[EPEL-devel] Proposed change to bodhi days to stable for epel

Currently the default days to stable for EPEL is 14 days. I believe when it was first put in it was set to that time because we wanted things more stable and better tested. But experience has found that if a package is going to get tested, it usually is in the first few days of when it was built.

[EPEL-devel] Re: Nemo for EPEL8?

Hi Michal, Looking through the past emails on the list, it looks like the Cinnamon desktop people stopped maintaining it for epel, back around the time we were branching things for epel8. I think more than being a co-maintainer, that you would be the epel maintainer.

[EPEL-devel] Re: python-unversioned-command for epel8 (provides /usr/bin/python)

On Tue, Jul 27, 2021 at 2:04 PM Neal Gompa wrote: > On Tue, Jul 27, 2021 at 5:09 AM Tomas Orsava wrote: > > > > If I understand what you're describing correctly, this is not a bug. > > In the default state, /usr/bin/python should *not* exist, that's correct > behaviour. If you want it to exist,

[EPEL-devel] Re: Updated KDE Plasma Desktop ready for testing on CentOS Stream 8

ote: > Il giorno ven 23 lug 2021 alle ore 00:21 Troy Dawson > ha scritto: > > > > Feel free to install and test. > > Troy Dawson > > > > Hi, > maybe I'm missing something, but after a fresh install I'm getting: > > # dnf upgrade > Last metadata ex

[EPEL-devel] Re: Updated KDE Plasma Desktop ready for testing on CentOS Stream 8

I've been able to install, and update all of the packages listed here. So, unless you are able to give more details about how your machine is setup, there isn't much I can help with. On Tue, Jul 27, 2021 at 6:39 AM Troy Dawson wrote: > What does "fresh install" mean in this co

[EPEL-devel] Re: Updated KDE Plasma Desktop ready for testing on CentOS Stream 8

el-next --mirrorlist= https://mirrors.fedoraproject.org/metalink?repo=epel-next-$releasever=$basearch Hope this helps. Troy On Wed, Jul 28, 2021 at 3:13 AM Massi aka Ergosum wrote: > Il giorno mar 27 lug 2021 alle ore 17:24 Troy Dawson > ha scritto: > > > > I've been able to i

[EPEL-devel] Re: [Fedocal] Reminder meeting : EPEL Steering Committee

This week's meeting will have two votes. 1 - Change the bodhi "days to stable" for epel. [1] The original proposal was to change it from 14 to 7. There was some talk of leaving it and getting stats, as well as changing it to 8 days. So, we'll probably have some discussion before the vote. 2 -

[EPEL-devel] Re: Packages disappearing from the EPEL 9 buildroot

On Wed, Dec 29, 2021 at 7:15 AM Stephen John Smoogen wrote: > > > On Wed, 29 Dec 2021 at 06:29, Mattias Ellert > wrote: > >> Hi! >> >> Two packages I built for EPEL 9 are now reported by koschei as having >> missing build dependencies. >> >>

[EPEL-devel] Re: Status of python-gevent in EL9

On Wed, Dec 29, 2021 at 7:30 AM Stephen John Smoogen wrote: > > > On Wed, 29 Dec 2021 at 10:19, Orion Poplawski wrote: > >> Can someone shed light on the status of python-gevent in EL9? It seems >> to have been built for CS9: >> >>

[EPEL-devel] EPEL Playground shutting down

Last year I sent out an email asking if anyone was using EPEL Playground. Nobody said they were. I did an analysis of what was being built on epel8-playground. The only builds being built were also being built at the same time on epel8. Thus, it appeared that nobody that was building on it was

[EPEL-devel] Re: EPEL Playground shutting down

On Tue, Jan 11, 2022 at 10:09 AM Yaakov Selkowitz wrote: > On Tue, 2022-01-11 at 09:51 -0800, Troy Dawson wrote: > > Last year I sent out an email asking if anyone was using EPEL Playground. > > Nobody said they were. > > I did an analysis of what was being built on epel8-

[EPEL-devel] Re: The incredibly shrinking RHEL

On Sat, Jan 15, 2022 at 12:33 PM Orion Poplawski wrote: > > I've done some poking, and this is what I've come up with for *new* > missing -devel packages in CS9 with their approximate number of users in > rawhide: > > 389-ds-base-devel 2 > accel-config-devel 0 > anthy-unicode-devel 3 >

[EPEL-devel] Re: Guidelines for adding subpackages not shipped by RHEL

On Mon, Jan 10, 2022 at 9:32 AM Petr Pisar wrote: > Hello, > > I happened to hit a request for adding web-assets-devel binary package of > web-assets component to EPEL 9 (bug #2036086) while web-assets-filesystem > binary package is shipped in RHEL. I recall it is allowed, but ones need to >

[EPEL-devel] Re: Handling packages with missing dependencies provided by HA-RS repos?

On Thu, Mar 10, 2022 at 2:17 PM Diego Herrera wrote: > I've been checking the packages that won't install on EPEL [1] and found > out that drbd-pacemaker cant get installed > because of a missing dependency (pacemaker). While researching why, I saw > that pacemaker exists on EPEL7 because it's >

[EPEL-devel] Re: Packaging issue with nodejs and mongodb-server

MongoDB was retired from Fedora and epel7 a couple of years ago, due to the license issues. Thus there is no longer a mongodb-server in epel7.https://bugzilla.redhat.com/show_bug.cgi?id=1855725 Problem: nodejs had a major update in epel7, and mongodb relies on the v8 in nodejs. Why the major

[EPEL-devel] Re: Plea: Take a moment before you branch everything for EPEL 9

On Thu, Feb 17, 2022 at 6:03 AM Miro Hrončok wrote: > On 17. 02. 22 13:52, Stephen John Smoogen wrote: > > > > > > On Thu, 17 Feb 2022 at 07:11, Miro Hrončok > > wrote: > > > > Hello EPEL packagers. > > > > I get it that you want as much as possible packages

[EPEL-devel] epel8-playground officially decommissioned

EPEL Playground was shut down in January 2022 EPEL 8 Playground was a place that developers and maintainers could "play around" with updated, or changed packages in epel. EPEL Playground never really worked out and ended up being more of a burden than helpful. If developers or maintainers want

[EPEL-devel] Re: Modules for EPEL9

It was talked about December 2021, and pushed off to the new year. https://pagure.io/epel/issue/135 It's the new year, and you are the first this year to ask for it. So, time to get it back in the discussions. Could you please put what modules you want to build in that ticket, so we can help

[EPEL-devel] Re: slowing down the stalled request process

On Wed, Mar 30, 2022 at 8:02 AM Stephen John Smoogen wrote: > > > On Wed, 30 Mar 2022 at 10:55, Troy Dawson wrote: > >> >> >> Current process (two bugzilla pings, two weeks total time): >>> - 1st request >>> - one week goes by >>>

[EPEL-devel] Re: slowing down the stalled request process

On Tue, Mar 29, 2022 at 10:04 PM Carl George wrote: > EPEL has a stalled request policy [0] that allows packagers to get > themselves added as collaborators on epel* branches. Prior to this > policy being implemented, requests to add Fedora packages to EPEL > would often go unanswered for long

[EPEL-devel] Re: slowing down the stalled request process

On Wed, Mar 30, 2022 at 12:21 PM Troy Dawson wrote: > > > On Wed, Mar 30, 2022 at 8:02 AM Stephen John Smoogen > wrote: > >> >> >> On Wed, 30 Mar 2022 at 10:55, Troy Dawson wrote: >> >>> >>> >>> Current process (two bugzilla pin

[EPEL-devel] KDE ready for testing in RHEL9Beta / CentOS Stream 9

ixed until the RHEL 9.1 timeframe. Troy Dawson [1] - https://bugzilla.redhat.com/show_bug.cgi?id=2058657 [2] - https://docs.fedoraproject.org/en-US/epel/#_el9 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an ema

[EPEL-devel] Re: KDE ready for testing in RHEL9Beta / CentOS Stream 9

On Tue, Mar 22, 2022 at 6:53 AM Troy Dawson wrote: > For those of you who want to use KDE on RHEL9 Beta, or CentOS Stream 9, it > is available via EPEL. It is currently plasma 5.23.5, kf5 5.90.0, qt5 > 5.15.2. There might be an update before RHEL 9.0 is released. > > The

[EPEL-devel] Re: Removing playground from package.cfg files

On Fri, Jan 28, 2022 at 12:01 AM Miro Hrončok wrote: > On 28. 01. 22 3:37, Troy Dawson wrote: > > > > > > On Wed, Jan 26, 2022 at 7:54 AM Troy Dawson > <mailto:tdaw...@redhat.com>> wrote: > > > > > > > > On Wed, Jan 26, 2022 at 7:37 A

[EPEL-devel] Re: Removing playground from package.cfg files

On Wed, Jan 26, 2022 at 7:54 AM Troy Dawson wrote: > > > On Wed, Jan 26, 2022 at 7:37 AM Miro Hrončok wrote: > >> On 26. 01. 22 16:30, Troy Dawson wrote: >> > EPEL 8 Playground is going away. >> > One of the steps in that process [1] is to clean out pla

[EPEL-devel] Re: Removing playground from package.cfg files

On Fri, Jan 28, 2022 at 7:28 AM Troy Dawson wrote: > > > On Fri, Jan 28, 2022 at 12:01 AM Miro Hrončok wrote: > >> On 28. 01. 22 3:37, Troy Dawson wrote: >> > >> > >> > On Wed, Jan 26, 2022 at 7:54 AM Troy Dawson > > <mailto:tdaw...@redh

[EPEL-devel] epel8-playground branch retires - happening now

Hello, I am currently in the middle of retiring all of the epel8-playground branches. I apologize for not sending an email ahead of time. For informations sake, I am retiring them with fedpkg retire "epel8-playground decommissioned : https://pagure.io/epel/issue/ 136" Just so people know

[EPEL-devel] Re: Incompatible upgrades: Upgrading varnish in epel7

On Tue, Feb 8, 2022 at 2:25 AM Ingvar Hagelund via epel-devel < epel-devel@lists.fedoraproject.org> wrote: > Varnish is a web cache. It is extremely fast, reliable, modern, and > programmable. It may also be used as a level-7 router or swiss army > knife. > > I maintain the varnish package in

[EPEL-devel] [DRAFT] Missing Sub-Package Policy

I have gotten a first draft of the Missing Sub-Package Policy up as a pull request. Feel free to give comments and suggestions. https://pagure.io/epel/pull-request/155 https://tdawson.fedorapeople.org/epel-docs/public/epel/epel-policy-missing-sub-packages/ Troy

[EPEL-devel] Re: epel8-playground branch retires - happening now

Turns out there was a flaw in the way I was looking for epel8-playground branches. I missed about 530 branches when I was retiring them. I am retiring those branches now. I apologize for the noise this might make. Troy On Mon, Jan 31, 2022 at 12:12 PM Troy Dawson wrote: > Hello, >

[EPEL-devel] Re: EPEL 9: Interested in fails to install reports?

On Thu, Jan 27, 2022 at 4:40 AM Neal Gompa wrote: > On Thu, Jan 27, 2022 at 7:37 AM Miro Hrončok wrote: > > > > Hello EPEL, > > > > would you be interested in automated bugzilla reports for EPEL 9 > packages that > > fail to install in the buildroot? Or is it too soon? > > > > When testing

[EPEL-devel] Re: The incredibly shrinking RHEL

On Fri, Jan 14, 2022 at 8:13 AM Stephen John Smoogen wrote: > > > On Fri, 14 Jan 2022 at 10:57, Stephen John Smoogen > wrote: > >> >> >> I mirrored the source rpms down and did the following for 8 and 9-stream. >> ``` >> $ for i in AppStream BaseOS PowerTools; do echo $i; find ./$i -type f >>

[EPEL-devel] Re: Removing playground from package.cfg files

On Wed, Jan 26, 2022 at 7:37 AM Miro Hrončok wrote: > On 26. 01. 22 16:30, Troy Dawson wrote: > > EPEL 8 Playground is going away. > > One of the steps in that process [1] is to clean out playground from all > the > > various package.cfg files. > > I will not be

[EPEL-devel] Removing playground from package.cfg files

have any concerns and/or comments. Troy Dawson [1] - https://pagure.io/epel/issue/136#comment-774581 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code

[EPEL-devel] Re: The incredibly shrinking RHEL

On Thu, Jan 13, 2022 at 8:12 PM Orion Poplawski wrote: > While working on EPEL9, it seems that even more packages are missing > from RHEL9 than were in RHEL8. The latest I found was cppunit, which > appears to be completely missing from the CS9 repos despite having been > built (See >

[EPEL-devel] Re: [HEADS UP] ImageMagick side-tag for epel8

On Fri, Apr 8, 2022 at 12:46 PM Sérgio Basto wrote: > On Thu, 2022-03-31 at 11:54 +0100, Sérgio Basto wrote: > > > This update changes a library soname, which makes it an > > > incompatible > > > upgrade. It must follow the EPEL incompatible upgrades policy [0]. > > > This email can count as

[EPEL-devel] Re: [HEADS UP] ImageMagick side-tag for epel8

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: > > > > On Fri, Apr 8, 2022 at 12:46 PM Sérgio Basto wrote: > > On Thu, 2022-03-31 at 11:54 +0100, Sérgio Basto wrote: > > > This update changes

[EPEL-devel] epel9-next cleanup

Hello All, Because of the wonderful enthusiasm of our epel maintainers, we have many packages (119) in epel9-next that are also in regular epel9.[1] All of the current epel9-next packages are equal to, or superseded by the current epel9 packages, thus there is no need for them to be in

[EPEL-devel] Re: Upgrade of mlpack in epel-7

On Mon, Oct 30, 2023 at 11:10 PM Benson Muite wrote: > On 10/30/23 16:37, Troy Dawson wrote: > > On Sun, Oct 29, 2023 at 10:35 AM Benson Muite > > mailto:benson_mu...@emailplus.org>> wrote: > > > > Would like to upgrade mlpack from 3.4.2 to 4.2.1 > >

[EPEL-devel] Re: Upgrade of mlpack in epel-7

On Sun, Oct 29, 2023 at 10:35 AM Benson Muite wrote: > Would like to upgrade mlpack from 3.4.2 to 4.2.1 > Version 3 is no longer maintained, and there do not seem to be > dependencies on mlpack, at least in Fedora. This is prompted by > CVE-2021-28021, CVE-2021-42715, CVE-2021-42716, and

[EPEL-devel] gpsd status in epel9

gpsd-minimal has been added to RHEL 9.2 and CentOS Stream 9. Although it has a different name than gpsd that is in Fedora and EPEL, the binary packages inside have the same name. Thus gpsd-minimal and gps-minimal-clients conflict with gpsd and gpsd-clients from EPEL. The RHEL packages have a

[EPEL-devel] Re: retirement of klee from EPEL 9

On Thu, Sep 28, 2023 at 8:37 PM Carl George wrote: > It recently came to my attention that the klee package in EPEL 9 > needed to be rebuilt against the LLVM 15 library that shipped in RHEL > 9.2. I filed a bug for this [0], and then noticed it was assigned to > "Orphan Owner". It looks like

[EPEL-devel] Re: Proposed incompatible security update for llhttp in EPEL9

o vote > yes when we hold the official vote in next week's steering committee > meeting. > > On Wed, Aug 9, 2023 at 1:35 PM Troy Dawson wrote: > > > > On Tue, Aug 8, 2023 at 4:11 PM Ben Beasley > wrote: > >> > >> This email proposes upgrading the llhtt

[EPEL-devel] Re: EPEL conflicts with Satellite 6 packages

On Tue, Apr 19, 2022 at 6:29 AM Troy Dawson wrote: > > > On Mon, Apr 18, 2022 at 3:49 PM Amos wrote: > >> On Mon, Apr 18, 2022 at 4:57 PM Kevin Fenzi wrote: >> >>> >>> Yeah, I'll echo smooge here. Can you expand on exactly what you are >>> hi

[EPEL-devel] Re: [HEADS UP] ImageMagick side-tag for epel8

Hi Sérgio, We aren't sure if you saw this or not, but you have permission to move ahead with the re-builds. Let us know if you need help with anything. On Wed, Apr 13, 2022 at 3:06 PM Carl George wrote: > On Fri, Apr 8, 2022 at 5:17 PM Troy Dawson wrote: > > > > > > &g

[EPEL-devel] Re: Does EPEL 9 Koji have older c9s packages than local mock?

Short answer: Yes Longer Answer: epel9 currently has what is going to be in RHEL 9.0. CentOS Stream 9 (what you get with local mock) has several updated packages that will be in RHEL 9.1 If you find that your packages will only build on the current CentOS STream 9, then you should build them in

[EPEL-devel] EPEL7 packages still in epel-testing

It was pointed out that we have 160 packages in epel7-testing. 10 of those are legitimate updates that are less than a week old. Then there are 3 that are less than a year old. And then there are 147 that are between 2 and 6 years old. (Yep, there are none that are between 1 and 2 years old). So,

[EPEL-devel] Re: EPEL7 packages still in epel-testing

That shows how much I've read the policies in detail. That got transferred over to the regular (non-wiki) docs https://docs.fedoraproject.org/en-US/epel/epel-policy/#a_yet_again_little_bit_bigger_minor_version_updates That policy in particular is for updates that do not have ABI changes, but

[EPEL-devel] Re: EPEL conflicts with Satellite 6 packages

On Mon, Apr 18, 2022 at 3:49 PM Amos wrote: > On Mon, Apr 18, 2022 at 4:57 PM Kevin Fenzi wrote: > >> >> Yeah, I'll echo smooge here. Can you expand on exactly what you are >> hitting? >> >> I can't seem to find the orig thread from 2016 in my mailbox, so I'm >> really not sure what the issue

[EPEL-devel] Re: Does EPEL 9 Koji have older c9s packages than local mock?

On Tue, Apr 26, 2022 at 7:38 AM Miro Hrončok wrote: > On 22. 04. 22 19:53, Miro Hrončok wrote: > > Hello, > > > > I've been trying to debug a segfault during %check that only occurs in > epel9 > > Koji, but not in mock. > > > > At the end, I compared the list of packages with: > > > > $ koji

[EPEL-devel] Re: How to remove builds from EPEL 9 Next?

On Fri, May 27, 2022 at 5:38 AM Neal Gompa wrote: > On Fri, May 27, 2022 at 8:00 AM Miro Hrončok wrote: > > > > Hey EPEL folks, > > > > The python-Rtree package was unable to build in EPEL 9 before RHEL 9.0 > GA, as > > the frozen set of packages from CentOS Stream made it segfault during >

[EPEL-devel] Re: CentOS Stream 8 and 9 - KDE un-updateable for a week

On Wed, May 4, 2022 at 8:01 AM Troy Dawson wrote: > > On Wed, Apr 27, 2022 at 9:31 AM Troy Dawson wrote: > >> During the past week qt5 was updated on CentOS Stream 8 and 9 to version >> 5.15.3. This caused updates to break for KDE users running CentOS Stream 8 >&g

[EPEL-devel] Cleaning up EPEL9 duplicate packages

There are 4 packages that are in epel9 that were also released with RHEL 9.0. This isn't that big of a surprise, we knew about them. Three managed to get branched and built before we had the check in place. One had a race condition with the build in RHEL. Two are easy to remove: ** pybind11 -

[EPEL-devel] Re: EL7 - Invalid version flag: or

On Fri, Jul 8, 2022 at 7:32 AM Justin Schoeman wrote: > Good day, > > Apologies if this is the wrong place to report this (or if this is just > a piece of idiocy on my part). > > Recently, I have started getting the following messages with 'yum update > --security' on some of my Centos 7

[EPEL-devel] Re: Update pam_radius to v2.0

Thank you for asking. Go for it. On Mon, Jun 6, 2022 at 12:55 AM Iker Pedrosa wrote: > Hi, > > I'd like to update pam_radius from v1.4 to v2.0 in EPEL9 and 8. The newer > version includes several patches to make the PAM module thread-safe. > > I've opened a ticket in the steering committee's

[EPEL-devel] Re: BTW Thanks

On Thu, Jun 9, 2022 at 4:29 PM Leon Fauster via epel-devel < epel-devel@lists.fedoraproject.org> wrote: > Not sure it was already said. With the release of RHEL9, EPEL9 (repo) > was in such a good state that the first steps with EL9 felt super > pleasant (compared to the EL8 start). So, thank you

[EPEL-devel] Thoughts: epel-release auto-enable crb repo

When I first created the EPEL issue to auto-enable crb repo[1] I was only thinking of CAN we do it. I wasn't thinking SHOULD we do it. We've come to the point that we actually can do it. But before we go down that road, I wanted to take a step back and ask, should we do it. The more I think

<    1   2   3   4   5   6   >