On Tue, Aug 23, 2022 at 9:00 PM Maxwell G wrote:
>
> On Tuesday, August 23, 2022 7:49:15 PM CDT Neal Gompa wrote:
> > > * The Pagure API does not allow tagging existing issues. I had planned to
> > > liberally use tags to manage the issues.
> >
> > What? You can do this with the "update issue
On Tuesday, August 23, 2022 7:49:15 PM CDT Neal Gompa wrote:
> > * The Pagure API does not allow tagging existing issues. I had planned to
> > liberally use tags to manage the issues.
>
> What? You can do this with the "update issue information" API call:
> https://pagure.io/api/0/#issues-tab
On Tue, Aug 23, 2022 at 8:42 PM Maxwell G via epel-devel
wrote:
>
> On Wednesday, August 10, 2022 4:07:29 PM CDT Troy Dawson wrote:
> > 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
On Wednesday, August 10, 2022 4:07:29 PM CDT Troy Dawson wrote:
> 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
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
On Sat, Aug 06, 2022 at 10:05:40PM +0200, Maxwell G via epel-devel wrote:
> Hi EPEL folks,
>
> In the past couple EPEL SCo meetings, we have been discussing adding a
> new package retirement policy for EPEL packages.
That reads amusingly to me... to be clear 'new policy' not 'new packages'.
