On Wed, Mar 04, 2026 at 10:38:44AM -0500, Jeremy Cline wrote:
> On Wed, Mar 4, 2026, at 10:00 AM, Zbigniew Jędrzejewski-Szmek wrote:
> > On Wed, Mar 04, 2026 at 11:21:50AM +0100, Miro Hrončok via devel-announce 
> > wrote:
> >> Dear maintainers.
> >> 
> >> Based on the current fail to build from source policy, the following 
> >> packages
> >> will be retired from rawhide in a week.
> >
> >> sigul                                     kevin
> >
> > That seems bad. But it depends on python-nss which is no more.
> > What's the plan here?
> 
> The replacement[0] nearly has feature parity. There's a few things I need to 
> sort
> out, like adding support to rpmsign for IMA signatures via PKCS#11[1] and 
> adjusting
> or re-implementing robosignatory. I also hope to beg some folks for reviews 
> once
> I've got documentation in order.
> 
> There is also the small matter of Sequoia not having released with PKCS#11 
> support.
> I think it's all tied up to the PQC work and is waiting on RFC 9580 to be 
> accepted.
> I believe it's possible, although I have not yet tested it, to get gpg 
> working with
> keys in PKCS#11 so that might be a short-term solution. If that's the case we 
> might
> be able to get a replacement deployed to the staging environment in a couple 
> weeks.
> 
> [0] https://github.com/fedora-infra/siguldry/
> [1] https://github.com/rpm-software-management/rpm/pull/4125

Ah, so it'd be under a different package name. So I think retiring
sigul itself is OK…  I think I said this before, but anyway, if
reviews are to be done, please assign them to me.

Zbyszek
-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to