Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd rpm-ostree support for modules #1435
Comments
This comment has been minimized.
This comment has been minimized.
|
I haven't tried, offhand my understanding is we'd only support the default streams, although I'm not even sure of that. Enhancements here block on rebasing libdnf but that's only the start...some of what libdnf does today is wrong for rpm-ostree (like the sqlite database in |
This comment has been minimized.
This comment has been minimized.
|
Marking this as hard. Let me know if that needs to be adjusted. |
This comment has been minimized.
This comment has been minimized.
|
The libdnf rebase is done now! Note there is a hack in fedora-coreos-config to disable modular repos we'll want to drop once rpm-ostree becomes module aware. |
This comment has been minimized.
This comment has been minimized.
|
Related: #1404 (comment). I haven't looked into this yet, so not sure how much work it'll actually be. At the very least though, if we don't want to block the next release on this, we should see if we can just tell libdnf to be module-unaware as it was before the rebase. |
For now, we don't natively support modules. But we still want to be able to install modular packages if the repos are enabled, but libdnf automatically filters them out. So for now, let's tell libdnf that we do want to be able to see them. Related: coreos#1435
This comment has been minimized.
This comment has been minimized.
|
I was looking at this today and how Anyway, short term fix in #1797 at least so we can get a release out soon. |
This comment has been minimized.
This comment has been minimized.
|
Was chatting with @imcleod about this. One thing we need to look into here is that libdnf should be overriding packages from the default stream if a modular repo is enabled, even if it's older than the same RPM from a non-modular repo. It doesn't seem like that's what we're seeing today. |
This comment has been minimized.
This comment has been minimized.
|
Current state of this is best summarized in Basically, modules are implemented by filtering the repodata which we don't do, so rpm-ostree will tend to just pick the highest NEVRA. In some cases this will work fine, in others it won't. |
This is a follow-up hack to coreos#1797 to force libdnf to let us use modular packages as if they were regular packages until we actually support modules correctly (coreos#1435). A repo marked as a modular hotfix means that libdnf doesn't try to filter out modular RPMs from the repo as it usually does. Resolves: https://pagure.io/releng/failed-composes/issue/717
This comment has been minimized.
This comment has been minimized.
This is a follow-up hack to coreos#1797 to force libdnf to let us use modular packages as if they were regular packages until we actually support modules correctly (coreos#1435). A repo marked as a modular hotfix means that libdnf doesn't try to filter out modular RPMs from the repo as it usually does. Resolves: https://pagure.io/releng/failed-composes/issue/717
This is a follow-up hack to #1797 to force libdnf to let us use modular packages as if they were regular packages until we actually support modules correctly (#1435). A repo marked as a modular hotfix means that libdnf doesn't try to filter out modular RPMs from the repo as it usually does. Resolves: https://pagure.io/releng/failed-composes/issue/717
See devel list thread. It looks like cri-o might start going modular. Can rpm-ostree support this (I know we inherit most functionality from dnf libraries, but there are probably some things to consider).
I saw #744 but this question wasn't really addressed there I don't think.