Is there some way I can find out more about why people untag builds from c9s-pending?
For example, today jantill untagged oath-toolkit-2.6.6-2.el9 from c9s-pending, but "pskctool" and "oathtool" are still present in https://gitlab.com/redhat/centos-stream/release-engineering/pungi-centos/-/b...
The reason I care about oath-toolkit is that Ceph requires liboath-devel, and now I'm not sure what version is going to ship in CentOS 9 Stream.
- Ken
On Thu, Aug 5, 2021, at 11:07, Ken Dreyer wrote:
Is there some way I can find out more about why people untag builds from c9s-pending?
For example, today jantill untagged oath-toolkit-2.6.6-2.el9 from c9s-pending, but "pskctool" and "oathtool" are still present in https://gitlab.com/redhat/centos-stream/release-engineering/pungi-centos/-/b...
The reason I care about oath-toolkit is that Ceph requires liboath-devel, and now I'm not sure what version is going to ship in CentOS 9 Stream.
- Ken
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
This package was marked unwanted: https://github.com/minimization/content-resolver-input/blob/master/configs/s...
Maybe the ceph dependency has been satisfied elsewhere?
--Brian
On Thu, Aug 5, 2021 at 12:44 PM Brian Stinson brian@bstinson.com wrote:
This package was marked unwanted: https://github.com/minimization/content-resolver-input/blob/master/configs/s...
Maybe the ceph dependency has been satisfied elsewhere?
After searching around, I found that there was another ticket where it was agreed to block oath-toolkit in the CentOS 9 tags so it's no longer in c9s-pending.
I also found that Pungi just skips any missing additional_packages. Pungi logs that pskctool and oathtool are unavailable, but it doesn't fail the compose.
I think this means the next step is to remove "pskctool" and "oathtool" from https://gitlab.com/redhat/centos-stream/release-engineering/pungi-centos/-/b...
- Ken