![]() Can be acted as Centralized Storage system.Allows to mount remote filesystems locally.File / Folder sharing between *nix systems.Lifetime, sometimes those efforts are overtaken by events. ![]() Īble to fix it before Fedora 33 is end of life. This message is a reminder that Fedora 33 is nearing its end of life.įedora will stop maintaining and issuing updates for Fedora 33 on. Since 'dnf system-upgrade' does distro-sync, I'd expect that dnf should install any newly added packagereq type="mandatory" or packagereq type="default" from comps for the new release version true/false? If the idea is to drop 'installed environment groups: Fedora Workstation' and just have 'installed groups' (set explicitly) then should this bug be retitled? Last metadata expiration check: 0:09:01 ago on Mon 10:00:01 AM MDT.Īnd the subset of 'dnf group list -hidden' includes group installed after Fedora installation"īut on a clean install of 'Fedora-Workstation-Live-x86_64-31-1.9.iso' I see this: "Fedora Workstation product core" are not brought in on 'dnf systemd-upgrade', so I found myself reading this bug, but I don't understand it. I'm trying to figure out why new packages added to e.g. At that time this bug will be closed as EOL if it remains open with aĪble to fix it before Fedora 29 is end of life. It is Fedora's policy to close all bug reports from releases that are no longer ![]() This message is a reminder that Fedora 29 is nearing its end of life.įedora will stop maintaining and issuing updates for Fedora 29 on. More recent Fedora release includes newer upstream software that fixes Version prior this bug is closed as described in the policy above.Īlthough we aim to fix as many bugs as possible during every release's Of Fedora, you are encouraged change the 'version' to a later Fedora To see this bug fixed and are able to reproduce it against a later version ![]() Thank you for reporting this issue and we are sorry that we were notĪble to fix it before Fedora 26 is end of life. Plan to fix it in a currently maintained version, simply change the 'version' Package Maintainer: If you wish for this bug to remain open because you This bug will be closed as EOL if it remains open with a Fedora 'version' It is Fedora's policy to close allīug reports from releases that are no longer maintained. This message is a reminder that Fedora 26 is nearing its end of life.Īpproximately 4 (four) weeks from now Fedora will stop maintainingĪnd issuing updates for Fedora 26. This way we can also tell DNF to install the environment, as the group exclusion no longer happens in Anaconda code, so it should not break anything anymore. This is how a call to it could look like:ĭef install_specs(install=["pkg", main idea is that we drop our own group exclusion code and just tell DNF what to include and exclude in the transaction. In the proposed DNF API addition mhatina developed there is now a function called install_specs(), which takes two iterables of package/group/module/environment specifications, one including items to include and the other to exclude from the installation transaction. we never told DNF to install an environment, as that would pull all its groups in unconditionally, nullifying our group exclusion logic this included resolving groups belonging to the currently selected environment (if any) this was implemented by resolving all groups requested for installation to a list and then removing all excluded groups from this list (all this in DNF payload on the Anaconda side) Anaconda needs group exclusion to work, even just for the (-nobase and -nocore options for the %packages section) when the Anaconda DNF payload was first written DNF apparently did not support group exclusion in it's API I'm currently working on module installation support in Anaconda and I think the new PoC API mhatina added for this can fix this issue with environments as well.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |