The change has now been implemented.
We'll have to wait for a package to be affected before we see it, but I
*think* it should look like what we have there.
Note: It is still doing everything as separate steps. So package
maintainers will still get several emails.
I got to see the code, and I
That sounds great, thanks.
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 from EPEL when
> RHEL . is released
>
>
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 from EPEL when RHEL
. is released
Comment:
This issue is purely informational, you do not need to take any action.
Thank you for your
I'm also late to the party with this feedback, but just in case it's
not too late to include, can we include something about not updating
the package further? Beyond just "you do not need to take any
action", we should advise against making any changes at that point, as
often the RHEL package
On Mon, Mar 27, 2023 at 7:22 PM Troy Dawson wrote:
> I see your point. It sometimes also happens when the EPEL package is a
> dependency of the important package, the customers aren't actually asking for
> the EPEL package.
While I am sure that occasionally RH chooses to add
a package to
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.
> >>
> >
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.
Does Red Hat have any other motivation with RHEL other than a customer
needing
On Mon, Mar 20, 2023 at 5:37 AM Miro Hrončok wrote:
>
> On 17. 03. 23 0:08, Troy Dawson wrote:
> > This package has been considered important enough to Red Hat's customers
> > that
> > Red Hat has decided to promote it to be an official part of RHEL.
>
> I know I am late to the party, so feel
On 17. 03. 23 0:08, Troy Dawson wrote:
This package has been considered important enough to Red Hat's customers that
Red Hat has decided to promote it to be an official part of RHEL.
I know I am late to the party, so feel free to ignore me.
Is it OK to claim guessed reasons for new packages
On Fri, 2023-03-17 at 07:09 -0700, Troy Dawson wrote:
> 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
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
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 3:43 PM Kevin Fenzi
> > > wrote:
> > > > On Thu, Mar 16, 2023 at
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 03:10:23PM -0700, Troy Dawson 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 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
On Thu, Mar 16, 2023 at 7:08 PM Troy Dawson wrote:
>
> 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
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 <
> gary.buhrmas...@gmail.com> wrote:
> >>>
> >>> On Mon, Sep 5,
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:
> > Notice: will be automatically retired from
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:
> Notice: will be automatically retired from epel when RHEL
> . is released
>
> Comment:
> Thank you for your
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
>> wrote:
>>>
>>> On Mon, Sep 5, 2022 at 9:33 AM Dominik 'Rathann' Mierzejewski
>>> wrote:
>>>
>>> > It would be really nice if
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 could contain some
>> > kind of a "thank you"
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 wrote:
> >> > On Fri, Sep 2, 2022 at 10:55 AM Davide
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 wrote:
>> > On Fri, Sep 2, 2022 at 10:55 AM Davide Cavalca via epel-devel <
>> > epel-devel@lists.fedoraproject.org> 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, 2022-09-01 at 12:12 -0500, Maxwell G via
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, 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 everyone will understand this process as "great, I don't
> have to
Hi Troy,
On Tue Nov 1, 2022 at 07:07 -0700, Troy Dawson wrote:
> On Fri, Sep 2, 2022 at 10:55 AM Davide Cavalca via epel-devel <
> epel-devel@lists.fedoraproject.org> wrote:
>
> > On Thu, 2022-09-01 at 12:12 -0500, Maxwell G via epel-devel wrote:
> > > I think this whole process should be
On 01. 11. 22 15:07, Troy Dawson wrote:
Does this sound good to people?
Yes please.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to
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
On Mon, 2022-09-05 at 11:33 +0200, 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 everyone will understand this process as "great, I
> don't
> have
On Friday, 02 September 2022 at 18:25, Kevin Fenzi wrote:
> On Thu, Sep 01, 2022 at 12:12:07PM -0500, Maxwell G via epel-devel wrote:
> > On Wednesday, August 31, 2022 Troy Dawson wrote:
> > > EPEL2RHEL is part of the RHEL 8 and 9 new package workflow. When a RHEL
> > > maintainer wants to add a
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 automatically retired after the release of RHEL
> X.X" and
> provide some explanation.
Agreed. This is a pretty mechanical
On Thu, Sep 01, 2022 at 12:12:07PM -0500, Maxwell G via epel-devel wrote:
> On Wednesday, August 31, 2022 Troy Dawson wrote:
> > 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".
On Wednesday, August 31, 2022 Troy Dawson wrote:
> 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
On 01. 09. 22 0:19, Troy Dawson wrote:
** Solution(s)
A - At the very least, we need to change the wording of the bugs. I am
proposing the following
Subject: Remove from epel9 when rhel 9.1 is released
Comment: This package is being added to RHEL 9.1 at the next minor release.
After the
34 matches
Mail list logo
