Re: Bugzilla components of retired packages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Mar 31, 2015 at 08:03:57AM -0600, Kevin Fenzi wrote:
> On Mon, 30 Mar 2015 10:34:35 -0500
> Michael Cronenworth <mike@xxxxxxxxxx> wrote:
> 
> > Can we get retired packages out of the active Bugzilla component list?
> 
> If they are completely retired, yeah, this might be possible. 
> 
> > I just created a bug for a retired package and had to fix it...
> > 
> > Bugzilla allows components to be disabled rather than deleted in case
> > the bugs need to be searched for or a package comes out of retirement.
> > 
> > Unfortunately the only way I see to automate this process is the REST
> > API in 5.0.
> 
> We use python-bugzilla to interface with bugzilla. 
> 
> Specfically this script: 
> http://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/pkgdb2/files/pkgdb-sync-bugzilla

The script is actually upstream at:
https://github.com/fedora-infra/pkgdb2/blob/master/utility/pkgdb-sync-bugzilla
It can be dropped from ansible now that a new release has been deployed.

My question was more: enhance this script or make a new one?

> So, we would need to enhance this script to handle the case of a
> package being retired in all branches in a product. Note that if they
> have any active branches we can't do this as at least the change I see
> via the interface is per component. 
> 
> Anyhow, if someone can see how to do this/provide patches sounds like a
> great idea. If we have to wait for 5.0, that would be good to know too. 

+1

Pierre

Attachment: pgpPm8Ly369X0.pgp
Description: PGP signature

_______________________________________________
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/infrastructure

[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux