Bug 2043397
Summary: | perl-Email-Abstract for EPEL9 | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Emmanuel Seyman <emmanuel> |
Component: | perl-Email-Abstract | Assignee: | Paul Howarth <paul> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel9 | CC: | paul, perl-devel, spotrh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | perl-Email-Abstract-3.009-3.el9 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-02-09 02:03:02 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: | 2031796 |
Description
Emmanuel Seyman
2022-01-21 07:39:41 UTC
Hi Spot, this one, along with perl-Mail-Transport, needs to be built in the middle of a bootstrap cycle for perl-Mail-Message. I am happy to do the builds of all three packages if you give me commit access to them. Emmanuel: perl-Mail-Message depends on perl-Text-Autoformat (Bug #2046233) so if you could work on that it will help things along. Cheers, Paul. Paul, you should have admin rights on perl-Mail-Transport, perl-Mail-Message, and perl-Email-Abstract now. Email-Abstract has an epel9 branch, but until Mail-Message is done, it won't build. (In reply to Tom "spot" Callaway from comment #2) > Paul, you should have admin rights on perl-Mail-Transport, > perl-Mail-Message, and perl-Email-Abstract now. Email-Abstract has an epel9 > branch, but until Mail-Message is done, it won't build. Thanks. perl-Mail-Transport and perl-Mail-Message look OK but I don't see me listed for perl-Email-Abstract yet. That won't matter for epel9 because it's already branched but it'd be nice to have for when epel10 comes around. I've done the branch requests for perl-Mail-Transport and perl-Mail-Message and should be able to handle all three packages once they're done. FEDORA-EPEL-2022-93d3b108e8 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-93d3b108e8 FEDORA-EPEL-2022-93d3b108e8 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-93d3b108e8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. (In reply to Paul Howarth from comment #3) > (In reply to Tom "spot" Callaway from comment #2) > > Paul, you should have admin rights on perl-Mail-Transport, > > perl-Mail-Message, and perl-Email-Abstract now. Email-Abstract has an epel9 > > branch, but until Mail-Message is done, it won't build. > > Thanks. perl-Mail-Transport and perl-Mail-Message look OK but I don't see me > listed for perl-Email-Abstract yet. That won't matter for epel9 because it's > already branched but it'd be nice to have for when epel10 comes around. I've > done the branch requests for perl-Mail-Transport and perl-Mail-Message and > should be able to handle all three packages once they're done. Not sure how that broke, but it is fixed now. (In reply to Tom "spot" Callaway from comment #6) > (In reply to Paul Howarth from comment #3) > > Thanks. perl-Mail-Transport and perl-Mail-Message look OK but I don't see me > > listed for perl-Email-Abstract yet. That won't matter for epel9 because it's > > already branched but it'd be nice to have for when epel10 comes around. I've > > done the branch requests for perl-Mail-Transport and perl-Mail-Message and > > should be able to handle all three packages once they're done. > > Not sure how that broke, but it is fixed now. Thanks. FEDORA-EPEL-2022-93d3b108e8 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. |