Bug 2133001
Summary: | hsxkpasswd-3.6-13.fc38 FTBFS: t/02-generate-passwords.t fails with perl-Type-Tiny-2.000001-1.fc38 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Petr Pisar <ppisar> |
Component: | hsxkpasswd | Assignee: | Petr Pisar <ppisar> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | eclipseo, rc040203 |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | hsxkpasswd-3.6-14.fc38 hsxkpasswd-3.6-14.fc37 hsxkpasswd-3.6-12.fc36 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-01-17 01:35:59 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2117176 |
Description
Petr Pisar
2022-10-07 12:39:37 UTC
Type-Tiny bisected to a first bead commit: commit 4baba12312f45d2e657468e26b64c643687651d1 (HEAD) Author: Toby Inkster <mail.uk> Date: Sun Sep 11 19:16:15 2022 +0100 Bring multisig functionality into the v2 API The new Type-Tiny raises an exception now: $ perl -Ilib -e 'use Crypt::HSXKPasswd; Crypt::HSXKPasswd->new(dictionary_list => [qw(seme tes words)])' Alternative signatures must be CODE, HASH, or ARRAY refs at /usr/share/perl5/vendor_perl/Type/Params/Signature.pm line 28. Petr, I think, hsxkpasswd should be retired, because it seems dead and unmaintained. Checking what other distros do, I could not find any other distro, which ships it. Sadly I retired it due to lack of upstream response. I think this package has not yet been retired from Fedora. Today a bug report at upstream received a fix. > I think this package has not yet been retired from Fedora.
>
> Today a bug report at upstream received a fix.
Would it be possible to have this fix in fc36 and fc37, too?
This bug is blocking me from applying updates/bug fixes to fc36 and fc37.
Sure. I will do the builds. FEDORA-2023-f643ebf370 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f643ebf370 FEDORA-2023-c74ab55c24 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-c74ab55c24 FEDORA-2023-f643ebf370 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-f643ebf370` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-f643ebf370 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-c74ab55c24 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-c74ab55c24` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-c74ab55c24 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-f643ebf370 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-c74ab55c24 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |