Bug 2333630 - rust-just: add to EPEL 10
Summary: rust-just: add to EPEL 10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rust-just
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Aleksei Bavshin
QA Contact:
URL:
Whiteboard:
Depends On: 2333631
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-12-21 04:55 UTC by Carl George 🤠
Modified: 2024-12-28 00:32 UTC (History)
3 users (show)

Fixed In Version: rust-just-1.38.0-1.el10_0
Clone Of:
Environment:
Last Closed: 2024-12-28 00:32:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Carl George 🤠 2024-12-21 04:55:20 UTC
Description of problem:
I would like to use the just command in CentOS 10.  Please add it to EPEL 10.  If you do not wish to maintain this package in EPEL 10, or do not think you will be able to do this in a timely manner, I would be happy to be a co-maintainer of the package (FAS carlwgeorge).


Additional info:
I tried a local mock build, and it failed missing crate(lexiclean/default).  I didn't see anything else in the log, so it seems most of the build dependencies are already present in EPEL 10.

Comment 1 Fabio Valentini 2024-12-21 10:42:46 UTC
I don't know why these aren't shown on *first* run, but there are more missing dependencies:

 Problem 1: nothing provides requested (crate(derive-where/default) >= 1.2.7 with crate(derive-where/default) < 2.0.0~)
 Problem 2: nothing provides requested (crate(dirs/default) >= 5.0.1 with crate(dirs/default) < 6.0.0~)
 Problem 3: nothing provides requested (crate(dotenvy/default) >= 0.15.0 with crate(dotenvy/default) < 0.16.0~)
 Problem 4: nothing provides requested (crate(edit-distance/default) >= 2.0.0 with crate(edit-distance/default) < 3.0.0~)
 Problem 5: nothing provides requested (crate(executable-path/default) >= 1.0.0 with crate(executable-path/default) < 2.0.0~)
 Problem 6: nothing provides requested (crate(shellexpand/default) >= 3.1.0 with crate(shellexpand/default) < 4.0.0~)
 Problem 7: nothing provides requested (crate(snafu/default) >= 0.8.0 with crate(snafu/default) < 0.9.0~)
 Problem 8: nothing provides requested (crate(strum/default) >= 0.26.0 with crate(strum/default) < 0.27.0~)
 Problem 9: nothing provides requested (crate(strum/derive) >= 0.26.0 with crate(strum/derive) < 0.27.0~)
 Problem 10: nothing provides requested (crate(target/default) >= 2.0.0 with crate(target/default) < 3.0.0~)
 Problem 11: nothing provides requested (crate(temptree/default) >= 0.2.0 with crate(temptree/default) < 0.3.0~)
 Problem 12: nothing provides requested (crate(which/default) >= 6.0.0 with crate(which/default) < 8.0.0~)

I'll start working on importing and building them in epel10.0-build-side-102506.

Comment 2 Fedora Update System 2024-12-21 14:22:53 UTC
FEDORA-EPEL-2024-f017ddda07 (rust-derive-where-1.2.7-1.el10_0, rust-dirs-5.0.1-4.el10_0, and 14 more) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-f017ddda07

Comment 3 Fedora Update System 2024-12-22 02:23:39 UTC
FEDORA-EPEL-2024-f017ddda07 has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-f017ddda07

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

Comment 4 Fedora Update System 2024-12-23 01:35:00 UTC
FEDORA-EPEL-2024-f017ddda07 has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-f017ddda07

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

Comment 5 Fedora Update System 2024-12-28 00:32:51 UTC
FEDORA-EPEL-2024-f017ddda07 (rust-derive-where-1.2.7-1.el10_0, rust-dirs-5.0.1-4.el10_0, and 15 more) has been pushed to the Fedora EPEL 10.0 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.