Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE: ability to restrict sources used during a compose #4298

Open
miabbott opened this issue Aug 9, 2024 · 2 comments
Open

RFE: ability to restrict sources used during a compose #4298

miabbott opened this issue Aug 9, 2024 · 2 comments

Comments

@miabbott
Copy link

miabbott commented Aug 9, 2024

If a user has multiple sources defined when doing composes, osbuild will try to do depsolving using all of the sources regardless of the distro specified in the blueprint or the type of compose. This can lead to undesirable results if multiple sources contain multiple versions of RPMs.

The current method to avoid using undesired sources is to remove them from osbuild, complete the compose you want to do, and then re-add the removed sources at a later time.

For instances of osbuild that support multiple distro versions and multiple composes requiring additional sources, it could be useful to be able to restrict which sources are being used during the compose of an artifact. Perhaps at the blueprint level?

@achilleas-k
Copy link
Member

Thanks for the write-up. I agree, this would be a useful feature, but this would have to happen in osbuild-composer, so I'll move it there.

@achilleas-k achilleas-k transferred this issue from osbuild/osbuild Aug 9, 2024
@achilleas-k
Copy link
Member

There are some plans floating around for dropping the internal management of these things (sources and blueprints) from osbuild-composer entirely and instead having the user pass them on the command line when starting a compose (something like composer-cli compose start --blueprint ./bp.toml --source ./myrepo.toml --source ./another.toml qcow2).

If we end up doing that, it solves this problem too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants