when zodbot is asked about a package upstreamed to RHEL, it does not so state:
rather it unhelpfully provides half the story, and says: orphaned
this would permit 'ad hoc' fixes needed in EPEL to be identified more easily, by running a package list through zodbot queries, and looking for the marker about upstreamed tt RHEL
[herrold @centos-7 ~]$ cat /etc/redhat-release ; rpm -qi pcp
CentOS Linux release 7.4.1708 (Core)
Name : pcp
Version : 3.11.8
Release : 7.el7
Architecture: x86_64
Install Date: Wed 15 Nov 2017 03:18:03 PM EST
...
Build Date : Fri 04 Aug 2017 06:28:44 PM EDT
Build Host : c1bm.rdu2.centos.org
Kevin commented:
Well, it's not wrong (it does tell you that it's orphaned in Fedora EPEL, which is true), it just doesn't say it's also in RHEL now. I think we could get the information about if something is currently in RHEL (we have some json that does this now).
... and not only report as orphaned
which is only part of the story
clone from
https://pagure.io/fedora-infrastructure/issue/6514
when zodbot is asked about a package upstreamed to RHEL, it does not so state:
rather it unhelpfully provides half the story, and says: orphaned
this would permit 'ad hoc' fixes needed in EPEL to be identified more easily, by running a package list through zodbot queries, and looking for the marker about upstreamed tt RHEL
16:04 =orc_fedo> whoowns pcp 16:04 =zodbot> nathans (orphan in Fedora EPEL)
[herrold @centos-7 ~]$ cat /etc/redhat-release ; rpm -qi pcp CentOS Linux release 7.4.1708 (Core) Name : pcp Version : 3.11.8 Release : 7.el7 Architecture: x86_64 Install Date: Wed 15 Nov 2017 03:18:03 PM EST ... Build Date : Fri 04 Aug 2017 06:28:44 PM EDT Build Host : c1bm.rdu2.centos.org
Kevin commented: