https://bugzilla.redhat.com/show_bug.cgi?id=2488341

Carl George 🤠 <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|[email protected]    |[email protected]
             Status|NEW                         |ASSIGNED
                 CC|                            |[email protected]



--- Comment #1 from Carl George 🤠 <[email protected]> ---
What's the strategy here in regards to the Fedora package?  Normally the latest
version will be packaged there first.  This compat package is a newer version
than what is currently in rawhide.

Compat packages are usually needed when there is a need for a different version
than the existing default.  slurm isn't yet in EPEL 10, so it may be a better
approach to update the rawhide spec file to version 26.05, and then
fast-forward the epel10 branch to that commit.  Once there is a default slurm
package in EPEL 10, then future versions would make sense as versioned compat
packages.  If the intent is to move to a future where there are only versioned
slurm packages, that change should happen in Fedora first before being brought
to EPEL.  Some examples: python-django5 / python-django6, python3.14 /
python3.15

Technically compat packages qualify for a review exception, but there's no harm
in doing a review anyways to verify the parallel or conflicting aspects.

https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/#_package_review_exceptions

What library soname version will this be?  This is obscured in the spec file by
an overly greedy glob, which is probably the first thing that needs to be
fixed.

https://docs.fedoraproject.org/en-US/packaging-guidelines/#_listing_shared_library_files

The rawhide package has these:

libpmi.so.0
libpmi2.so.0
libslurm.so.44
libslurm_pmi-25.11.4.so
libslurmfull-25.11.4.so

If those are all different in the compat package, ideally the libs subpackage
could be set up as a parallel package and not a conflicting one.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2488341

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202488341%23c1

-- 
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Reply via email to