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:
>> >>
>> >> On Wed, Jun 15, 2022 at 5:12 PM Troy Dawson
On Friday, June 17, 2022 9:03:07 AM CDT Patrick Riehecky via epel-devel wrote:
> This way any extra ideas for actions can be added easily later on.
> Perhaps a "check" or "status" to see if CRB is enabled/disabled/not-
> what-the-os-ships.
+1. Having some logic to check if CRB is actually enabled
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:
> >> >
> >> > I'm totally top-posting, and I apologize for
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.
>> >
>> > For right now, I'm going to put my enable-crb script in
On Fri, 2022-06-17 at 06:33 -0700, 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.
> > >
> > > For right now, I'm going to put my enable-crb
On Fri, Jun 17, 2022 at 9:33 AM Troy Dawson wrote:
> I notice that you said crb-enable, crb-disable.
> Do you like having the name first, or the function first?
I'd put in a vote for "object action" like Carl denoted.
As a side note, and this is more for personal learning/clarification,
is
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 automatically run it in a %post script or
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
> automatically run it in a %post script or anything.
> The debate about putting it in a post script, or a
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 Tue, Jun 14, 2022 at 2:20 PM Josh Boyer wrote:
>
> Not fully sure I understand the results, but this looks promising.
To clarify, the FINAL_EPEL.json files contain CRB packages as the keys
and their arrays are packages from EPEL that depend on them.
For for example:
On Tue, Jun 14, 2022 at 2:20 PM Josh Boyer wrote:
>
> One thing I caught on initial glance, I think it's getting confused on
> multilib.
>
> That seems to be highlighting that lutris.x86_64 depends on gvfs.i686.
> I don't think that's actually the case, because gvfs.x86_64 is shipped
> in
On Tue, Jun 14, 2022 at 2:15 PM Mike Rochefort wrote:
>
> On Mon, Jun 13, 2022 at 4:18 PM Chris Adams wrote:
> >
> > Once upon a time, Josh Boyer said:
> > > If the dependency is only needed at build time, which is what CRB
> > > content is intended for
> >
> > If that's the intent, then it's
On Mon, Jun 13, 2022 at 4:18 PM Chris Adams wrote:
>
> Once upon a time, Josh Boyer said:
> > If the dependency is only needed at build time, which is what CRB
> > content is intended for
>
> If that's the intent, then it's not implemented correctly. For example,
> there are well over 100 perl
On Mon, Jun 13, 2022, 4:17 PM Chris Adams wrote:
> Once upon a time, Josh Boyer said:
> > If the dependency is only needed at build time, which is what CRB
> > content is intended for
>
> If that's the intent, then it's not implemented correctly. For example,
> there are well over 100 perl
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
Once upon a time, Josh Boyer said:
> If the dependency is only needed at build time, which is what CRB
> content is intended for
If that's the intent, then it's not implemented correctly. For example,
there are well over 100 perl modules in CRB 9. They may only be used
_by Red Hat_ in
On Mon, 2022-06-13 at 07:41 -0400, Josh Boyer wrote:
> On Sun, Jun 12, 2022 at 6:50 AM Sérgio Basto
> wrote:
> >
> > On Sun, 2022-06-05 at 00:54 +0200, Neal Gompa wrote:
> > > Let me start with examples that I get *regularly*: Pagure fails
> > > to
> > > install from EPEL on
Am 13.06.22 um 13:41 schrieb Josh Boyer:
On Sun, Jun 12, 2022 at 6:50 AM Sérgio Basto wrote:
On Sun, 2022-06-05 at 00:54 +0200, 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
On Sun, Jun 12, 2022 at 6:50 AM Sérgio Basto wrote:
>
> On Sun, 2022-06-05 at 00:54 +0200, 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
On Sun, 2022-06-05 at 00:54 +0200, 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.
if epel
On Sat, Jun 4, 2022 at 3:52 PM Troy Dawson wrote:
>
> 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
Once upon a time, Andrew C Aitchison said:
> On Wed, 8 Jun 2022, Maxwell G via epel-devel wrote:
> >On Wednesday, June 8, 2022 2:54:51 PM CDT Michel Alexandre Salim wrote:
> >>without messing with config files (which I
> >>hate, because that means newer crb.repo changes won't be picked up).
> >
>
On Wed, 8 Jun 2022, Maxwell G via epel-devel wrote:
On Wednesday, June 8, 2022 2:54:51 PM CDT Michel Alexandre Salim wrote:
without messing with config files (which I
hate, because that means newer crb.repo changes won't be picked up).
I thought files marked `%config(noreplace)` don't get
On Wednesday, June 8, 2022 2:54:51 PM CDT Michel Alexandre Salim wrote:
> without messing with config files (which I
> hate, because that means newer crb.repo changes won't be picked up).
I thought files marked `%config(noreplace)` don't get updated automatically
even
if the user didn't modify
On Wed, 2022-06-08 at 15:06 -0500, Chris Adams wrote:
> Once upon a time, Michel Alexandre Salim
> said:
> > This won't be ready until EPEL 10 or even 11, but one thing I've
> > discussed with the DNF maintainer is the possibility of having
> > something like /etc/yum.repos.d/reponame.repo.d/
Once upon a time, Michel Alexandre Salim said:
> This won't be ready until EPEL 10 or even 11, but one thing I've
> discussed with the DNF maintainer is the possibility of having
> something like /etc/yum.repos.d/reponame.repo.d/ where you can drop
> overrides, similar to how you can drop
On Sat, 2022-06-04 at 20:47 -0400, Stephen Smoogen wrote:
>
>
> On Sat, 4 Jun 2022 at 18:54, Neal Gompa wrote:
> > On Sat, Jun 4, 2022 at 10:52 PM Troy Dawson
> > wrote:
> > >
> > > When I first created the EPEL issue to auto-enable crb repo[1] I
> > > was only thinking of CAN we do it. I
On Mon, 6 Jun 2022 at 10:44, Patrick Riehecky via epel-devel <
epel-devel@lists.fedoraproject.org> wrote:
> I realize this is a bit of a pipe dream, but is there "some way" to
> ship a repo file from EPEL that points to the crb repo(s)? Folks not
> wanting it could block the package/not install
I realize this is a bit of a pipe dream, but is there "some way" to
ship a repo file from EPEL that points to the crb repo(s)? Folks not
wanting it could block the package/not install weak deps. Getting the
right repos is a bit tricky but I figured I'd voice the idea...
Pat
On Sat, 2022-06-04
Jun 4, 2022 4:01:42 PM Troy Dawson :
> 3 - We are taking the choice away from users
> After I stopped and thought about it, there are plenty of scenarios where
> people want epel for just one or two packages, which do not require crb.
>
> 4 - All the many small side cases.
> auto-enabling crb
On Sat, Jun 4, 2022 at 21:17 Manuel Wolfshant
wrote:
> On 6/5/22 03:47, Stephen Smoogen wrote:
>
>
>
> On Sat, 4 Jun 2022 at 18:54, Neal Gompa wrote:
>
>> On Sat, Jun 4, 2022 at 10:52 PM Troy Dawson wrote:
>> >
>> > When I first created the EPEL issue to auto-enable crb repo[1] I was
>> only
On Sat, Jun 4, 2022 at 8:52 PM Troy Dawson wrote:
> What do others think?
Almost everything *I* care to do with el eventually
needs epel and/or CRB/Powertools.
I also do not think CRB/Powertools should be
auto-enabled by epel (epel does not own them,
and should not touch them).
And, yes, a
On 6/5/22 03:47, Stephen Smoogen wrote:
On Sat, 4 Jun 2022 at 18:54, Neal Gompa wrote:
On Sat, Jun 4, 2022 at 10:52 PM Troy Dawson
wrote:
>
> 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
On Sat, 4 Jun 2022 at 18:54, Neal Gompa wrote:
> On Sat, Jun 4, 2022 at 10:52 PM Troy Dawson wrote:
> >
> > 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
On Sat, Jun 4, 2022 at 10:52 PM Troy Dawson wrote:
>
> 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
35 matches
Mail list logo
