On Fri, Jan 26, 2024 at 8:08 AM David Trudgian via epel-devel <epel-devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > Hi all, > > I’ve had some discussion with Jonathan Wright elsewhere about the topic of this message, but wanted to verify my understanding is correct before I embark on it, and thought I’d do so on list. > > singularity-ce is currently packaged at v4.0.3 in Fedora Rawhide, and v.3.11.5 elsewhere (Fedora releases and EPEL). > > We want to make a v4 available to EPEL users, as many would be interested in it, but I wouldn’t consider it a compatible update because there are some CLI changes, and small behaviour changes. > > My understanding is that in order to provide a 4.x in EPEL, without any incompatible update happening for users: > > 1) I create a new package, singularity-ce4, to package the 4.x version. In rawhide, this will be the same as the singularity-ce package currently in rawhide, but needs new package review etc. Creating a versioned package does NOT require a new review[1], though if you feel that packaging changes are going to be large enough to warrant one, you may still request it. > > 2) For rawhide / upcoming f40 *only*, the new singularity-ce4 package will provide/obsolete singularity-ce as it is the same thing … and singularity-ce can be retired in rawhide. > 3) When singularity-ce4 is added to EPEL it will *not* provide/obsolete singularity-ce, but a message can be added to %post to inform people about the availability of v4. Do not do this. %post messages are really only intended to inform users of failures and, frankly, no one reads them until something has gone wrong. Even then, it's only going to be the sysop for the machine that sees it, who may not be the person who deals with Singularity. I don't know anything about Singularity, but if it has a user interface of any kind (like the CLI), what you might want to do is add a wrapper around it that prints your message. That's much more likely to be viewed by the people who would care. > At some point in the future, if 3.x is no longer maintainable for good reason, then the incompatible update procedure can be pursued to make singularity-ce4 provide/obsolete singularity-ce in EPEL 7/8/9 - and singularity-ce is fully retired. EPEL 10 will only get singularity-ce4. Is v3 still supported upstream today? If not, you probably want to make the message above a deprecation notice and add an EOL date. > Apologies for the multiple complex queries lately. I really appreciate your guidance! > [1] https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/#_package_review_process -- _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
