Skip to content

Conversation

dx3mod
Copy link
Contributor

@dx3mod dx3mod commented Sep 14, 2025

rpmfile.0.8.0

RPM package reader

Old versions were not used and had broken dependencies.



🐫 Pull-request generated by opam-publish v2.5.1

@dx3mod dx3mod force-pushed the opam-publish-rpmfile.0.8.0 branch from ce5b7ac to 3e2ed1c Compare September 14, 2025 18:33
@jmid
Copy link
Contributor

jmid commented Sep 14, 2025

Thanks for the contribution.

Removing old versions as in 3e2ed1c is not a viable solution to solving red CI lights. It is also against the opam-repo policy: https://github.com/ocaml/opam-repository/tree/master/governance/policies#1-removal-of-packages-should-be-avoided

We will be happy to help formulate constraints to make the rpmfile.0.8.0 release fit in 🙂

@dx3mod
Copy link
Contributor Author

dx3mod commented Sep 15, 2025

I understood you

@mseri
Copy link
Member

mseri commented Sep 16, 2025

If yoy add x-maintenance-intent: [(latest)] (see
https://github.com/ocaml/opam-repository/blob/master/governance/policies/archiving.md) to this release, this will make sure all the old versions will be archived. You could also manually set x-maintained: false on the relevant packages, or x-maintenance-intent: [(none)] if you want to remove an old package altogether and they will all be removed at the next archive phase. Would this be a suitable solution?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants