Bug 2032971 - [RFE:EPEL9] EPEL9 branch for fuse-sshfs
Summary: [RFE:EPEL9] EPEL9 branch for fuse-sshfs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: fuse-sshfs
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-15 15:47 UTC by Pat Riehecky
Modified: 2021-12-27 00:20 UTC (History)
3 users (show)

Fixed In Version: fuse-sshfs-3.7.2-2.el9
Clone Of:
Environment:
Last Closed: 2021-12-27 00:20:38 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Pat Riehecky 2021-12-15 15:47:31 UTC 
Description of problem:

Can fuse-sshfs be branched for EPEL9

Version-Release number of selected component (if applicable): current fedora version


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Vasiliy Glazov 2021-12-15 16:13:52 UTC 
At that moment I see some errors during build for epel-next-9.
Comment 2 Vasiliy Glazov 2021-12-16 20:13:54 UTC 
I requested epel9 branch.
You can check this scratch build now https://koji.fedoraproject.org/koji/taskinfo?taskID=80095327
Comment 3 Fedora Update System 2021-12-18 06:31:07 UTC 
FEDORA-EPEL-2021-33e76dba63 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-33e76dba63
Comment 4 Fedora Update System 2021-12-19 01:55:23 UTC 
FEDORA-EPEL-2021-33e76dba63 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-2021-33e76dba63

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2021-12-27 00:20:38 UTC 
FEDORA-EPEL-2021-33e76dba63 has been pushed to the Fedora EPEL 9 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.