Bug 2174705 - Please build rubygem-addressable for EPEL8 and EPEL9
Summary: Please build rubygem-addressable for EPEL8 and EPEL9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: rubygem-addressable
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Troy Dawson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2175210
Blocks: 2168260
TreeView+ depends on / blocked
 
Reported: 2023-03-02 08:02 UTC by Steve Traylen
Modified: 2023-03-24 03:28 UTC (History)
5 users (show)

Fixed In Version: rubygem-addressable-2.8.1-3.el9 rubygem-addressable-2.8.1-3.el8
Clone Of:
Environment:
Last Closed: 2023-03-24 02:35:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Steve Traylen 2023-03-02 08:02:15 UTC
Please can rubygem-addressable be built for EPEL8 and EPEL9.

The current rawhide - rubygem-addressable-2.8.1-2.fc39

both builds and installs in both and EPEL8 and EPEL9 mock but only of the
tests are disabled due to a lack of:

BuildRequires: rubygem(public_suffix)
BuildRequires: rubygem(rspec-its)

Add me as co-maintainer if you like: stevetraylen.

Many thanks

Steve.

Comment 1 Troy Dawson 2023-03-02 14:29:27 UTC
Hi Steve,
I have given you collaborator access, specific to epel*
That should give you everything you need to branch, commit, and build rubygem-addressable on epel.
This is the first time I've tried setting that permission, so if you don't have enough access, let me know.

Comment 2 Steve Traylen 2023-03-03 10:56:10 UTC
Hi Troy,

I could authenticated clone but the request branch: failed for lack of permissions https://pagure.io/releng/fedora-scm-requests/issue/51736  

Steve.

Comment 3 Troy Dawson 2023-03-03 14:22:32 UTC
I believe collaborator not being able to branch is a bug on the releng side, but I don't want to hold you up while that get's fixed.
I have bumped up your priviledges, you should be able to branch now.

Comment 4 Steve Traylen 2023-03-03 14:35:31 UTC
Hmm.

Despite the 500 error:

```
From ssh://pkgs.fedoraproject.org/rpms/rubygem-addressable
 * [new branch]      epel8      -> origin/epel8
 * [new branch]      epel9      -> origin/epel9
```
so maybe it did work... or you did.

Steve.

Comment 5 Fedora Update System 2023-03-15 08:10:13 UTC
FEDORA-EPEL-2023-7d3fb79249 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7d3fb79249

Comment 6 Fedora Update System 2023-03-15 08:10:15 UTC
FEDORA-EPEL-2023-7e82f80959 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7e82f80959

Comment 7 Fedora Update System 2023-03-16 17:31:31 UTC
FEDORA-EPEL-2023-7d3fb79249 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7d3fb79249

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2023-03-16 19:12:24 UTC
FEDORA-EPEL-2023-7e82f80959 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-2023-7e82f80959

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2023-03-24 02:35:15 UTC
FEDORA-EPEL-2023-7e82f80959 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2023-03-24 03:28:08 UTC
FEDORA-EPEL-2023-7d3fb79249 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.