Re: Proposal: disable comps component in Bugzilla

2022-09-21 Thread Ben Cotton
On Wed, Sep 21, 2022 at 10:22 AM Kevin Kofler via devel wrote: > > Bugzilla does not allow you to use the DUPLICATE status without giving a > concrete Bugzilla bug ID of which the bug is allegedly a duplicate, Good point. I'll use another closure type then. The point is: I'll go through the

Re: Proposal: disable comps component in Bugzilla

2022-09-21 Thread Kevin Kofler via devel
Ben Cotton wrote: > I'll close ones that already exist in Pagure as DUPLICATE Bugzilla does not allow you to use the DUPLICATE status without giving a concrete Bugzilla bug ID of which the bug is allegedly a duplicate, so you cannot use it for bugs that are duplicated on external bug trackers.

Re: Proposal: disable comps component in Bugzilla

2022-09-21 Thread Ben Cotton
On Tue, Sep 20, 2022 at 12:49 PM Kevin Fenzi wrote: > > Amusingly I think we in the past discussed closing the pagure project to > issues and using bugzilla only. ;) I'd entertain arguments for doing that. But I think the "have the issues with the 'code'" aspect is more valuable in this

Re: Proposal: disable comps component in Bugzilla

2022-09-20 Thread Kevin Kofler via devel
Ben Cotton wrote: > On Tue, Sep 20, 2022 at 10:03 AM Neal Gompa wrote: >> >> The main reason would be blocker review, but I'm not sure how often it >> comes up in the past few cycles. > > Rarely, which is why I think using distribution as a proxy is fine. > For the curious, a total of 16 comps

Re: Proposal: disable comps component in Bugzilla

2022-09-20 Thread Kevin Fenzi
On Tue, Sep 20, 2022 at 10:01:36AM -0400, Ben Cotton wrote: > comps, the system of XML files used to put packages into functional > groups is hosted on a Pagure repo[1] but also has a Bugzilla > component. In the interests of simplicity, I propose to disable the > comps component and use the

Re: Proposal: disable comps component in Bugzilla

2022-09-20 Thread Ben Cotton
On Tue, Sep 20, 2022 at 10:03 AM Neal Gompa wrote: > > The main reason would be blocker review, but I'm not sure how often it > comes up in the past few cycles. Rarely, which is why I think using distribution as a proxy is fine. For the curious, a total of 16 comps bugs have ever been a part of

Re: Proposal: disable comps component in Bugzilla

2022-09-20 Thread Neal Gompa
On Tue, Sep 20, 2022 at 10:02 AM Ben Cotton wrote: > > comps, the system of XML files used to put packages into functional > groups is hosted on a Pagure repo[1] but also has a Bugzilla > component. In the interests of simplicity, I propose to disable the > comps component and use the Pagure repo

Proposal: disable comps component in Bugzilla

2022-09-20 Thread Ben Cotton
comps, the system of XML files used to put packages into functional groups is hosted on a Pagure repo[1] but also has a Bugzilla component. In the interests of simplicity, I propose to disable the comps component and use the Pagure repo for all comps issues. In the case where a change in comps is