We don't have a version limit for shotwell in rawhide, so it will inevitably be updated whenever somebody next runs mclazy:
https://forge.fedoraproject.org/workstation/mclazy/src/branch/main/modules.xml I don't think it's a good idea to use rawhide version limits unless we really want to ensure a package is never updated *ever* again, like for gtk3 or glibmm2.4. Otherwise, we'll forget to remove the limit. My suggestion is GNOME maintainers should just not create unstable releases unless they intend to do a stable release within the next few months. The unstable releases exist to be packaged, after all: there is no reason to create them if you don't want distros to package them. That just doesn't make sense. So I'm actually OK with shipping the unstable version. But alternatively, we could remove Shotwell from release automation, and only update it manually. This is a problem for non-GNOME packages as well, like Flatpak. Upstreams should think carefully about what they are trying to achieve in creating an unstable release. Do you expect distros to package it, or is there some other purpose for the unstable release?
-- _______________________________________________ devel 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
