Hi, I'm considering dropping some packages from sway:rolling modulemd definition, however I don't clearly understand what would be the resulting upgrade behavior. Let's assume that the module is already enabled and all the packages are installed in the user's system. Also, the module was containing the same set of packages during f32 release (i.e. in fedora-modular). In an optimistic case I'd like to believe that once the package is removed from the modulemd file and a new module update is published, the override magic hacked into dnf would stop masking package from non-modular repository. NEVRA would be the only factor deciding the update priority and when we push new build of the package into f32-updates it would update the remaining modular build of the package with lower EVR. In a pessimistic case I expect that the package removed from the module will never be updated by dnf in the same release cycle since the already installed version originates from the modular repository. Upgrade to f33 would require module reset. I have zero knowledge on the modularity implementation so I would appreciate if anyone could clarify which behavior is more likely to happen before we start experimenting on real users :) -- With best regards, Aleksei Bavshin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
