On Mon, Jun 13, 2022 at 5:03 AM Josh Boyer wrote:
> However, if a package needs something
> at runtime it would be better to first inquire about putting that
> dependency in BaseOS or AppStream rather than just blindly using it
> from CRB.
>
My first attempt as requesting a critical runtime CRB
I'm totally top-posting, and I apologize for that.
For right now, I'm going to put my enable-crb script in epel-release, but
not automatically run it in a %post script or anything.
The debate about putting it in a post script, or a separate package, can go
on independently of the script.
This
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.
> >
> > For right now, I'm going to put my enable-crb script in epel-release,
> but not automati
On Fri, Jun 17, 2022 at 1:20 PM Carl George wrote:
> 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:
> >
On Fri, Jun 17, 2022 at 1:41 PM Troy Dawson wrote:
>
>
> On Fri, Jun 17, 2022 at 1:20 PM Carl George wrote:
>
>> On Fri, Jun 17, 2022 at 8:33 AM Troy Dawson wrote:
>> >
>> >
>> >
>> > On Thu, Jun 16, 2022 at 10:22 PM Carl George wrote:
&
It was a configuration mix up that pulled in ALL the modules instead of
just the default ones.
It only lasted a week (I think) and has been fixed.
It was just bad timing, nothing you could have done to prevent, or fix it.
I thought we'd caught all the packages that were built that might have been
On Sat, Jun 4, 2022 at 3:54 PM Neal Gompa wrote:
> Let me start with examples that I get *regularly*: Pagure fails to
> install from EPEL on RHEL/CentOS/Alma/etc. because python3-markdown is
> not available. KDE Plasma fails to install because of a mass of
> missing dependencies.
>
> I get
Just so people know, the rawhide version of fusioninventory-agent builds on
epel9 without any changes.
On Fri, Jul 29, 2022 at 6:37 AM R Groux
wrote:
> Hi,
>
> could it be possible to include the fusioninventory agents packages into
> the epel 9 ?
>
> this is the Bugzilla url
>
>
be the last major update for Plasma. It will
continue to stay on 5.24, which is an LTS release. The libraries in RHEL 8
are just too old for the newer Plasma's.
Troy Dawson
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe
I don't want to discourage anyone from taking this, but I just want to
point out that conky requires wireless-tools and tolua++ to build.
Neither of which is in epel8 or epel9.
On Wed, Jul 27, 2022 at 9:44 AM Barris, Alexander J. [US-US] via epel-devel
wrote:
> Hi all,
>
> Would someone be
On Mon, May 2, 2022 at 1:22 AM Alex Iribarren
wrote:
> Hi,
>
> On 4/29/22 21:17, Stephen John Smoogen wrote:
> >
> >
> > On Fri, 29 Apr 2022 at 14:28, Germano Massullo
> > mailto:germano.massu...@gmail.com>> wrote:
> >
> > Recent CentOS Stream Qt update broke some EPEL packages like
>
On Wed, Apr 27, 2022 at 4:38 PM Sérgio Basto wrote:
> On Wed, 2022-04-27 at 23:44 +0100, Sérgio Basto wrote:
> > On Wed, 2022-04-13 at 17:54 -0500, Carl George wrote:
> > > > This was approved [0] in today's EPEL Steering Committee meeting.
> > > > Please continue with the process for
On Fri, Apr 29, 2022 at 11:28 AM Germano Massullo <
germano.massu...@gmail.com> wrote:
> Recent CentOS Stream Qt update broke some EPEL packages like keepassxc
> that needed a rebuild against the new Qt version.
> Can we talk about a way to prevent this from happening again?
>
> Best regards
>
On Fri, Apr 29, 2022 at 12:19 PM Troy Dawson wrote:
> On Fri, Apr 29, 2022 at 11:28 AM Germano Massullo <
> germano.massu...@gmail.com> wrote:
>
>> Recent CentOS Stream Qt update broke some EPEL packages like keepassxc
>> that needed a rebuild against the new Qt ve
On Thu, Apr 28, 2022 at 2:57 AM Sérgio Basto wrote:
> A qui, 28-04-2022 às 10:48 +0100, Sérgio Basto escreveu:
>
> A qua, 27-04-2022 às 16:58 -0700, Troy Dawson escreveu:
>
>
>
> On Wed, Apr 27, 2022 at 4:38 PM Sérgio Basto wrote:
>
> On Wed, 2022-04-27 at 23:4
and plasma releases. Since we knew that the qt5 update was
coming, we held off rebuilding everything until qt5 came out. Now that it
is out, we are updating everything.
Troy Dawson
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe
On Fri, Apr 29, 2022 at 11:28 AM Germano Massullo <
germano.massu...@gmail.com> wrote:
> Recent CentOS Stream Qt update broke some EPEL packages like keepassxc
> that needed a rebuild against the new Qt version.
> Can we talk about a way to prevent this from happening again?
>
> Best regards
>
>
Hi Miro,
Thank you for looking into this.
One thing to keep in mind is that what is in CentOS Stream 9 right now, is
going into RHEL 9.1, so some of this won't be in epel9 for another 6-7
months.
I've noticed that in your query's you do a RHEL9 query. Where is that
coming from?
I just want to
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
On Wed, May 4, 2022 at 1:00 PM Miro Hrončok wrote:
> On 04. 05. 22 15:40, Troy Dawson wrote:
> > I just want to make sure that you are querying RHEL 9.0 and not 9.1.
>
> Well, I was querying 9.1, so you have a point. However, with 9.0 it is
> almost
> the same:
>
>
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
> and 9. The epel 8 and 9 packages affected are being rebuilt at this time.
&g
Hi Lynn,
I think you need to contact whoever setup your spacewalk / satellite
system. They are the owners of epel7-centos7-x86_64, not the EPEL
community.
epel7-centos7-x86_64 is a custom repository, that I am betting is on your
spacewalk system.
There are three clues for this.
1st - epel7 is
the man
pages?
Troy
On Tue, Aug 23, 2022 at 6:40 AM Alex Talaran wrote:
> attached a new spec using 4.10 which should match el9 (desired distro
> version) as you noted.
> srpm and rpm still seem to build fine without man pages, still not sure
> how to generate them.
>
> On 2022
; the names? i left it the same as in the original spec file, and named
> this one -epel after previous discussion on list
>
> On 2022-08-24 17:13, Troy Dawson wrote:
> > I'm sure having all the fence agents in one package is nice for you, but
> > if someone has both Fe
On Thu, Sep 1, 2022 at 12:19 AM Miro Hrončok wrote:
> On 31. 08. 22 23:08, Stephen Smoogen wrote:
> >
> > When EPEL-8 was launched, it came with some support for modules with the
> hope
> > that a module ecosystem could be built from Fedora packages using RHEL
> modules
> > as an underlying
Hi All,
EPEL2RHEL is part of the RHEL 8 and 9 new package workflow. When a RHEL
maintainer wants to add a package to RHEL 8 or 9 they start a "new package
workflow". There are several automations that happen when they start that
workflow. One of them is checking if the package is already in
When EPEL-8 was launched, it came with some support for modules with the
hope that a module ecosystem could be built from Fedora packages using RHEL
modules as an underlying tool. This has never happened and we have ended up
with a muddle of modular packages which will 'build' but may not install
On Wed, Oct 19, 2022 at 5:42 PM Dave Dykstra via epel-devel <
epel-devel@lists.fedoraproject.org> wrote:
> Hello all,
>
> It is been pointed out to me that I pushed out an update of a package to
> EPEL that did not follow the incompatible upgrades policy:
>
>
list.
It would be best if it was one of the epel ones, or even both.
Troy
> Dave
>
> On Thu, Oct 20, 2022 at 01:18:30PM -0700, Troy Dawson wrote:
> > On Wed, Oct 19, 2022 at 5:42 PM Dave Dykstra via epel-devel <
> > epel-devel@lists.fedoraproject.org> wrote:
> >
>
We have been asked for a transition plan, for people using epel 8 modules.
Although we have talked about a transition plan, I realized we didn't write
anything outside of chats and talking to one another. I believe this is
what we said, but if others can verify and/or correct me, that would be
On Fri, Oct 21, 2022 at 9:59 AM Leon Fauster via epel-devel <
epel-devel@lists.fedoraproject.org> wrote:
> Am 21.10.22 um 17:11 schrieb Troy Dawson:
> ...
> > == Transition Steps
> > === 1 - Verify that you are using an EPEL 8 Module
> > dnf list installed | grep epe
On Wed, Oct 19, 2022 at 2:44 AM Nick Howitt via epel-devel <
epel-devel@lists.fedoraproject.org> wrote:
> On a server I don't use very often, I am trying to update
> mock-core-configs with yum and I am seeing:
>
> Resolving Dependencies
> --> Running transaction check
> ---> Package
For those that are wondering, the latest version in rawhide build on epel9
without any changes needed.
So it should be fairly straightforward.
Troy
On Mon, Sep 19, 2022 at 4:20 AM Stephen Smoogen wrote:
>
> This went to the mailing list admins versus the list. I don't think this
> person is
ww.madisoncollege.edu)
> ------
> *From:* Troy Dawson
> *Sent:* Monday, September 26, 2022 11:46 AM
> *To:* EPEL Development List
> *Subject:* [EPEL-devel] Re: EPEL RHEL 9 mirror error
>
> I was able to reproduce the error.
> If you do a RHEL install, and select a security
I was able to reproduce the error.
If you do a RHEL install, and select a security profile, it will
automatically turn on gpg checking for everything.[1]
You then get the error you were showing.
To get around this you need to add the --nogpgcheck option
dnf install --nogpgcheck
On Fri, Sep 23, 2022 at 10:37 AM Nick Jahn wrote:
> Errors during downloading metadata for repository
> 'dl.fedoraproject.org_pub_epel_9_x86_64_':
> - Status code: 404 for
> https://dl.fedoraproject.org/pub/epel/9/x86_64/repodata/repomd.xml (IP:
> 38.145.60.24)
> Error: Failed to download
qt6 is being updated from 6.2.3 to 6.3.1 in epel9.[1]
There is no soname bump, and everything should be backward compatible.
Why announce it?
Our KDE Plasma Desktop policy is to do a major update only once a year in
the main epel repositories.
qt6 is currently NOT part of the KDE Plasma Desktop.
lsyncd and autossh - already in epel9
geoip - https://bugzilla.redhat.com/show_bug.cgi?id=2066787
"Please do NOT branch GeoIP for EPEL 9, because MaxMind, the GeoIP
upstream, has clearly declared the end of life for GeoIP"
webalizer - nobody has asked for it. And maybe someone needs to port
On Wed, Sep 28, 2022 at 3:09 PM Troy Dawson wrote:
> When EPEL-8 was launched, it came with some support for modules with the
> hope that a module ecosystem could be built from Fedora packages using RHEL
> modules as an underlying tool. This has never happened and we have
On Thu, Oct 6, 2022 at 8:50 AM Stephen Smoogen wrote:
>
>
> On Wed, 31 Aug 2022 at 17:08, Stephen Smoogen wrote:
>
>>
>> When EPEL-8 was launched, it came with some support for modules with the
>> hope that a module ecosystem could be built from Fedora packages using RHEL
>> modules as an
There hasn't been a qt update in CentOS Stream 8 or 9 since May 2022, so
you'll have to give more information.
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
ny changes they
might face.
* Answer2: Because February 14th was voted down by our significant others.
EPEL Steering Committee
On Wed, Sep 28, 2022 at 3:09 PM Troy Dawson wrote:
> When EPEL-8 was launched, it came with some support for modules with the
> hope that a module ecosystem cou
When EPEL-8 was launched, it came with some support for modules with the
hope that a module ecosystem could be built from Fedora packages using RHEL
modules as an underlying tool. This has never happened and we have ended up
with a muddle of modular packages which will 'build' but may not install
On Fri, Oct 7, 2022 at 5:54 AM Stephen Smoogen wrote:
>
>
> On Fri, 7 Oct 2022 at 05:59, Miro Hrončok wrote:
>
>> On 07. 10. 22 9:33, Petr Pisar wrote:
>> > Does EPEL have any communication channel to EPEL users besides this
>> mailing
>> > list? If it does, do you plan to announce this change
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
> > submit a ticket requesting to orphan a certain package's EPEL branch(es)
> > and set the EPEL
Hi Alex,
I've been looking into this some.
What distribution do you want this for?
I haven't seen anywhere in your emails saying if this is for RHEL 8 or RHEL
9?
The spec file you have attached is for fence-agents-4.11, which is only in
Fedora, so that doesn't let me know either.
The major
Yes, and if you can, tag it with "meeting"
If it doesn't let you tag it with meeting, let me know and I'll do it.
On Fri, Dec 2, 2022 at 11:49 AM Richard Fearn
wrote:
> It looks like the next step is to get this on the agenda for the EPEL
> Steering Committee meeting.
>
> Should I create a
I have cleaned up the epel-next (both 8 and 9) repo's.
If a package was newer in regular epel than in epel-next, the epel-next
package was untagged from epel{8,9}-next.
If a package was the same version-release in both epel and epel-next, I
made sure the epel version was installable on CentOS
I'm sorry, I clicked, "Send" too quickly.
If the document doesn't have that Note in it yet, please wait an hour an
check again.
On Tue, Dec 6, 2022 at 9:57 AM Troy Dawson wrote:
> The ELN Extras page[1] was updated with one note. I thought I'd share
> that note with the epel-de
The ELN Extras page[1] was updated with one note. I thought I'd share that
note with the epel-devel mailing list.
NOTE: **You** are responsible when your package fails to build on ELN
Extras. Remember to check your packages on the ELN Status Page.[2]
ELN Extras packages get rebuilt much more
I'll probably take it.
I generally avoid perl due to dependencies, but this looks fairly
straightforward.
What is this ultimately for?
On Mon, Dec 19, 2022 at 7:16 AM Vladimir Pachnik <
vladimir.pach...@gooddata.com> wrote:
> Any takers?
>
>
> > On 13. 12. 2022, at 15:2
Packages do not automatically get transferred over from epel7 to a newer
epel. People have to request them.
Nobody has requested it for epel9.
https://docs.fedoraproject.org/en-US/epel/epel-package-request/
On Tue, Dec 13, 2022 at 9:15 AM Dan Horák wrote:
> Hi,
>
> isn't anybody already
On Mon, Dec 12, 2022 at 7:35 AM Vladimir Pachnik <
vladimir.pach...@gooddata.com> wrote:
> would anyone be able to take over the build of 'perl-Net-Domain-TLD'
package for EPEL9 as per
https://bugzilla.redhat.com/show_bug.cgi?id=2144550 ?
For those who are wondering, The fedora package builds
.
We will continue to provide security and critical bug fixes, but no major
updates.
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
Just so people don't need to go to the bug.
This has already been reported for RHEL 9.
https://bugzilla.redhat.com/show_bug.cgi?id=2140266
If I understand "Approved Release" correctly, the fix will come out in RHEL
9.2
On Tue, Jan 24, 2023 at 3:57 AM Sérgio Basto wrote:
>
it sounds counter-intuitive, it will save the
maintainers time.
We haven't officially made this change yet. So if anyone sees any issues
and/or problems. Please let us know.
Thank You
Troy Dawson
Fedora KDE SIG
[1] - https://fedoraproject.org/wiki/SIGs/KDE/EPEL#Update_Schedule
[2] - Currently epel9
t confused as to what you want to happen.
Is this a heads up, that you are going to change something?
Do you want us to discuss what is the best thing to do?
Are you letting us know about the problem, and want someone else to
implement a solution?
Troy Dawson
_
On Thu, Nov 10, 2022 at 12:24 PM Neal Gompa wrote:
> On Thu, Nov 10, 2022 at 3:11 PM wrote:
> >
> > Hi,
> >
> > I have 2 systems running el8. When I run yum update qt5-qtbase I get the
> > following error on both systems:
> >
> > (tom-lp-21 pts7) # yum update qt5-qtbase
> > Updating
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 think this whole process should be automated. File bugs that say
> > "Heads up:
> > your package will be
I am officially canceling this weeks meeting.
Reasons:
We have postponed the epel10 discussion until next week.
I, and several other members will not be able to be there.
Talk to you next week, February 8
Troy
On Tue, Jan 31, 2023 at 8:00 AM wrote:
> Dear all,
>
> You are kindly invited to
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 11:38 AM Carl George wrote:
> >>
> >> On Tue, Mar 7, 2023 at 8:52 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
>> >
>> > RHEL has been very good (lately) about their NVR's being higher than
>> EPEL's.
>> >
On Thu, Mar 16, 2023 at 3:35 PM Neal Gompa wrote:
> On Thu, Mar 16, 2023 at 6:10 PM Troy Dawson wrote:
> >
> > On Mon, Feb 20, 2023 at 6:33 AM Troy Dawson wrote:
> >>
> >>
> >>
> >> On Sun, Feb 19, 2023 at 6:25 PM Gary Buhrmaster <
> ga
On Thu, Mar 16, 2023 at 3:43 PM Kevin Fenzi wrote:
> On Thu, Mar 16, 2023 at 03:10:23PM -0700, Troy Dawson wrote:
> >
> > This is what I have on my ticket. Respond soon (by tomorrow end of day)
> if
> > you think I need changes.
> >
> > Subject:
> > N
On Mon, Feb 20, 2023 at 6:33 AM Troy Dawson wrote:
>
>
> On Sun, Feb 19, 2023 at 6:25 PM Gary Buhrmaster
> wrote:
>
>> On Mon, Sep 5, 2022 at 9:33 AM Dominik 'Rathann' Mierzejewski
>> wrote:
>>
>> > It would be really nice if the wording of the bug co
On Fri, Mar 17, 2023 at 6:48 AM Patrick Riehecky wrote:
> On Fri, 2023-03-17 at 06:22 -0700, Troy Dawson wrote:
> > On Thu, Mar 16, 2023 at 6:31 PM Patrick Riehecky via epel-devel
> > wrote:
> > > On Thu, 2023-03-16 at 16:05 -0700, Troy Dawson wrote:
> > > >
On Thu, Mar 16, 2023 at 6:31 PM Patrick Riehecky via epel-devel <
epel-devel@lists.fedoraproject.org> wrote:
> On Thu, 2023-03-16 at 16:05 -0700, Troy Dawson wrote:
> >
> >
> > On Thu, Mar 16, 2023 at 3:43 PM Kevin Fenzi wrote:
> > > On Thu, Mar 16, 2023 at
On Fri, Mar 17, 2023 at 3:17 AM Carl George wrote:
> 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 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 users consume EPEL
> > packages. Depending how quick they are, the rebuild distros might not
> > have their 9.2 rebuild
On Tue, Mar 21, 2023, 4:05 AM Quinn Comendant wrote:
> On 9 Sep 2022, Troy Dawson wrote:
>
> webalizer - nobody has asked for it. And maybe someone needs to port
> webalizer to use libmaxminddb
>
> I came here specifically to ask for Webalizer and found this thread.
>
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 Fri, Mar 3, 2023 at 5:42 AM Daniel P. Berrangé
> wrote:
> >> >
On Sun, Feb 19, 2023 at 4:34 PM Maxwell G wrote:
> 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, 202
On Sun, Feb 19, 2023 at 6:25 PM Gary Buhrmaster
wrote:
> On Mon, Sep 5, 2022 at 9:33 AM Dominik 'Rathann' Mierzejewski
> wrote:
>
> > It would be really nice if the wording of the bug could contain some
> > kind of a "thank you" note to the EPEL maintainers of the package in
> > question. Not
On Mon, Feb 20, 2023 at 6:45 AM Neal Gompa wrote:
> On Mon, Feb 20, 2023 at 9:44 AM Troy Dawson wrote:
> >
> > On Sun, Feb 19, 2023 at 4:34 PM Maxwell G wrote:
> >>
> >> Hi Troy,
> >>
> >> On Tue Nov 1, 2022 at 07:07 -0700, Troy Dawson w
On Fri, Mar 3, 2023 at 3:42 AM Daniel P. Berrangé
wrote:
> A few weeks back there was a little snafu (since resolved) with the
> capstone package in EPEL.
>
> This package is being introduced to RHEL 9.2, and thus has been added
> to CentOS 9 Stream repos. A bug was filed against capstone in
A bug was found in /usr/bin/crb [1] dealing with how crb determines if you
are on a RHEL system or not. A fix was made and tested on every RHEL
compatible distro I could find. So I'm very confident about those.
But for real RHEL systems that use subscription-manager, I only have access
to a few
ction", we should advise against making any changes at that point, as
> often the RHEL package will be exactly one release higher than the
> current EPEL package, and updating the EPEL package further (either
> release or version) will screw up the upgrade path.
>
> On Mon, Mar 2
This is mainly for EPEL10 planning, but others might find it useful, so I'm
sending it to the email vs the epel10 discussion on discourse.
I was talking with Carl about creating a dnf variable for the epel 10
repos. He had been talking about using $releasever and $releaseminor. But
we also
On Fri, Mar 31, 2023 at 11:19 AM Miroslav Suchý wrote:
> Dne 31. 03. 23 v 16:42 Troy Dawson napsal(a):
> > How to set it, I suggest triggers. But that needs a bit more
> investigation and testing.
>
> May I suggest file trigger?
>
> https://rpm-software-managem
nks.
>
> On Thu, Mar 30, 2023, 8:28 AM Troy Dawson wrote:
>
>> It doesn't look like they've done their merge yet, so I'll see if I can
>> get your change in.
>> How does this sound?
>>
>> Subject:
>> Notice: will be automatically retired fro
On Mon, Apr 10, 2023 at 10:40 AM Ben Beasley
wrote:
> When I took over maintenance of the flintqs package[1]—which contains
> William Hart’s quadratic sieve implementation, as modified for
> sagemath—I built it for EPEL7, EPEL8, and EPEL9. My thoughts were, “Why
> not? Someone might find it
Due to several ongoing bugs, we are updating plasma in epel8 to the latest
5.24 version, 5.24.7.
The previous version in epel8 was 5.24.6
It is currently in epel8-testing. You can update to it now with
dnf --enablerepo=epel-testing update
If you would like to leave karma, the bodhi link is
On Sat, Mar 25, 2023 at 12:51 PM Miro Hrončok wrote:
> On 20. 03. 23 12:20, Neal Gompa wrote:
> >> I could think of other reasons as well. E.g. it's not important for
> customers
> >> but it's important for Red Hat. Or maybe it is a not-so-important
> dependency of
> >> something else.
> >>
> >
It looks good to me.
Thanks for doing that.
On Sun, Jan 29, 2023 at 9:26 AM Orion Poplawski wrote:
> The python-qt5 package in RHEL 8 does not ship the webkit package. I'm
> assuming that this is unlikely to be changed since qt5-qtwebkit isn't in
> RHEL but is in EPEL.
>
> I think I'm close
On Wed, Feb 8, 2023 at 1:19 PM Michel Alexandre Salim <
sali...@fedoraproject.org> wrote:
> On Wed, 2023-02-08 at 14:09 -0500, Neal Gompa wrote:
> > On Wed, Feb 8, 2023 at 12:37 PM Troy Dawson
> > wrote:
> > >
> > > On Wed, Feb 8, 2023 at 9:21
On Wed, Feb 8, 2023 at 9:21 AM Michel Alexandre Salim <
sali...@fedoraproject.org> wrote:
> Hi all,
>
> Per the incompatible upgrade policy[1] I'm proposing upgrading
> libkdumpfile from 0.4.1 to the latest 0.5.1 in both EPEL 8 and 9.
>
> Bugzilla issues:
> -
EPEL 8 Modules are now officially retired.
- The EPEL 8 modules are being archived.
- The mirror manager is being pointed to the archive
- Tags, targets and configurations are being removed so new builds cannot
happen.
- The dnf epel-modular.repo will remain, but will still default to disabled
-
, 2023 at 2:57 PM Troy Dawson wrote:
> I have a new update set. This is just the packages failing to install
> with the updated qt5. The qt5 packages are updated to match the versions
> that are now in RHEL. All other packages are still the same versions and
> patches as
On Thu, Jul 20, 2023 at 2:41 AM Otto Liljalaakso
wrote:
> Recently, I adopted the orphaned Zim package for Fedora. The previous
> maintainer had added the package to EPEL, while I am not involved with
> EPEL at all. Consequently, I will not maintain the EPEL branches anymore.
>
> From going
On Tue, Aug 8, 2023 at 4:11 PM Ben Beasley wrote:
> This email proposes upgrading the llhttp package in EPEL9 from 6.0.10 to
> 8.1.1, which would break the ABI and bump the SONAME version, under the
> EPEL Incompatible Upgrades Policy[1].
>
> The llhttp package is a C library (transpiled from
The EPEL Steering Committee meeting has been canceled this week.
If you need your EPEL fix, you can watch the "State of EPEL" presentation
at Flock
https://flock2023.sched.com/event/1Or5D/state-of-epel
or any of the other great presentations at Flock.
On Tue, Aug 1, 2023 at 9:00 AM wrote:
>
There is a new qt5 update in CentOS Stream 9. This update will be going
out when RHEL 9.3 is released six months from now. Again, that is RHEL
9.3, NOT 9.2.
I am currently rebuilding KDE for CentOS Stream 9. This will take some
time to rebuild and make it through testing. I am suspecting it
On Thu, May 4, 2023 at 12:57 PM Marcin Dulak wrote:
> Hi,
>
> I have a bugzilla opened about a CenOS Stream package missing during EPEL9
> builds
> https://bugzilla.redhat.com/show_bug.cgi?id=2182460, for over a month
> with no response.
>
> Can something be done about this, apart from trying to
I just noticed this went to the the wrong mailling list.
Not many people are going to see this on epel-devel-owners.
On Wed, May 10, 2023 at 7:02 AM Stephen Smoogen wrote:
>
>
> On Wed, 10 May 2023 at 09:46, Troy Dawson wrote:
>
>> For those EPEL maintainers deciding
Hi Sérgio,
Thank you for the update and reminder.
I've put kdenlive on my KDE list of packages that I check and update.
It will automatically get updated in step with the other KDE packages in
epel.
That means that for epel9, it will be the F37 version of kdenlive - 22.12.3.
For epel9-next it
On Mon, May 15, 2023 at 3:15 AM Miro Hrončok wrote:
> Hello,
>
> I'm working on adding python3.11-rpm to EPEL 9 and EPEL 9 Next.
>
> See https://src.fedoraproject.org/rpms/python3-rpm/pull-request/3 and 4.
>
> I decided to reuse the python3-rpm component (currently epel7 only). Let
> me
> know
investigation of the security implications. I don't think it would be
> good to automatically switch fully to the --userns mode with a setuid
> installation and "allow setuid-mount extfs = no", because then users
> will get subtle differences with other behavior depending on whethe
that need a rebuild due to the qt5 update.
I'm sorry for the inconvenience, and appreciate the patience you have shown.
Troy
On Fri, May 5, 2023 at 7:11 AM Troy Dawson wrote:
> There is a new qt5 update in CentOS Stream 9. This update will be going
> out when RHEL 9.3 is released six
That makes it more clear for epel7.
But it will be strange for epel7 to have a higher version than epel8 and 9.
Would the apptainer maintainers be willing to create an update that has the
--userns option, as well as the original option?
Then for epel7 the rpm's would have the original option
-EPEL-NEXT-2023-22498da84c
On Wed, May 17, 2023 at 8:58 AM Troy Dawson wrote:
> KDE is still not able to be upgraded in CentOS Stream 9.
> This is my fault.
> I tried to combine the rebuilds needed for the new qt5, with updating the
> rest of the KDE Plasma Desktop. This didn't
401 - 500 of 518 matches
Mail list logo
