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

Alternative dependencies not recognized #386

Open
0 opened this issue May 5, 2017 · 2 comments
Open

Alternative dependencies not recognized #386

0 opened this issue May 5, 2017 · 2 comments

Comments

@0
Copy link
Contributor

0 commented May 5, 2017

Debian has support for alternative dependencies for a package, so that the presence of any single one is sufficient. For example, bcfg2-server depends on python-pyinotify | python-gamin. If neither is already present, apt installs one.

The problem is that bcfg2 sees the installed dependency as an extra entry and tries to remove it.

My current workaround is to explicitly add one of the alternative dependencies to the bundle.

@AlexanderS
Copy link
Member

That is expected. The bcfg2-server does not know if some package is installed on the server. Currently or-dependencies are simply ignored. AFAIK apt tries to install always the first package (if it has no other information), so the server could try to search all specified packages (and dependencies) for one of the dependencies and simply pick the first one if nothing is found. But this behavior currently does not exist.

@solj
Copy link
Member

solj commented May 10, 2017

Yeah, this is expected behavior. You have to explicitly tell the server which dependency you want because we don't want to make that choice for you. Perhaps we should document this behavior?

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

3 participants