Missing step in orphaning package process? (Re: kernel component on bugzilla and call for "old bugs hunting season" to open)

[Tomasz Kłoczko]

Trying to look on one of the top tickets found:

https://bugzilla.redhat.com/show_bug.cgi?id=502717

Looks like this ticket is about package which is no longer in Fedora.

Does it mean that current Fedora package orphaning process is not closing
all such package tickets in Bugzilla?
If yes it will be some number of the tickets which is possible to close now
automatically.

kloczek
--
Tomasz Kłoczko | LinkedIn: *http://lnkd.in/FXPWxH <http://lnkd.in/FXPWxH>*

[Pierre-Yves Chibon]

On Fri, Jan 26, 2018 at 10:20:27PM +0000, Tomasz Kłoczko wrote:
>     Trying to look on one of the top tickets found:
>     https://bugzilla.redhat.com/show_bug.cgi?id=502717
>     Looks like this ticket is about package which is no longer in Fedora.
>     Does it mean that current Fedora package orphaning process is not closing
>     all such package tickets in Bugzilla?
>     If yes it will be some number of the tickets which is possible to close
>     now automatically. 
Indeed they are not closed automatically and that is in purpose. Orphaned
packages are still in the repos and thus the bug may very well still be valid.
Leaving it open allows maintainers or other users to find them and be aware of
the issue and potentially catch up with the discussion that occurred on the
ticket.
They are then closed when the release goes EOL.

So that's a yes and no :)

Pierre

[Tomasz Kłoczko]

On 27 January 2018 at 06:57, Pierre-Yves Chibon <pingou(a)pingoured.fr&gt; wrote:

>  On Fri, Jan 26, 2018 at 10:20:27PM +0000, Tomasz Kłoczko wrote:
>  >    Trying to look on one of the top tickets found:
>  >    https://bugzilla.redhat.com/show_bug.cgi?id=502717
>  >    Looks like this ticket is about package which is no longer in Fedora.
>  >    Does it mean that current Fedora package orphaning process is not
>  closing
>  >    all such package tickets in Bugzilla?
>  >    If yes it will be some number of the tickets which is possible to
>  close
>  >    now automatically.
>
>  Indeed they are not closed automatically and that is in purpose. Orphaned
>  packages are still in the repos and thus the bug may very well still be
>  valid.
>  Leaving it open allows maintainers or other users to find them and be
>  aware of
>  the issue and potentially catch up with the discussion that occurred on the
>  ticket.
>  They are then closed when the release goes EOL.
>  
It is only one obstacle to make it happen.
As long as package is orphaned no longer it has maintainer (human
maintainer).

Go to https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora -> enter as
component name gdhcpd and you will suddenly find that you are able to open
the ticket for Fedora 26, 27 and rawhide (sic!)
Go to https://src.fedoraproject.org/rpms/gdhcpd and look on right side
where are branches names and you will find that latest Fedora version for
which this package has been released was  Fedora 11 (no EPEL)
As admin of this package is listed "orphan (orphan)
<https://src.fedoraproject.org/user/orphan>- main admin"
How this dummy packages is maintaining still assigned to this package
Bugzilla tickets?

Is that all still correct?

kloczek
-- 
Tomasz Kłoczko |  LinkedIn: *http://lnkd.in/FXPWxH <http://lnkd.in/FXPWxH>*

[Kevin Fenzi]

On 01/28/2018 03:12 PM, Tomasz Kłoczko wrote:

>  It is only one obstacle to make it happen.
>  As long as package is orphaned no longer it has maintainer (human
>  maintainer).
>  
>  Go to https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora -> enter as
>  component name gdhcpd and you will suddenly find that you are able to open
>  the ticket for Fedora 26, 27 and rawhide (sic!)
>  Go to https://src.fedoraproject.org/rpms/gdhcpd and look on right side
>  where are branches names and you will find that latest Fedora version for
>  which this package has been released was  Fedora 11 (no EPEL)
>  As admin of this package is listed "orphan (orphan)
>  <https://src.fedoraproject.org/user/orphan>- main admin"
>  How this dummy packages is maintaining still assigned to this package
>  Bugzilla tickets?
>  
>  Is that all still correct? 
Yes. The idea is that a orphaned package could be taken over again by
someone and they would want to know the existing bugs already filed on it.

It might be worth closing retired components to bugs, but they too could
be revived and readded.

kevin