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

repo_checker: consider using Tumbleweed docker container to ensure latest tooling #1054

Closed
jberry-suse opened this issue Aug 15, 2017 · 4 comments
Assignees
Labels

Comments

@jberry-suse
Copy link
Contributor

@jberry-suse jberry-suse commented Aug 15, 2017

Per mailinglist thread concerning error due to older libsolv it seems a proper solution would be to run the repo-checker inside a container so as to keep up with Tumbleweed and not break on future feature additions.

@jberry-suse

This comment has been minimized.

Copy link
Contributor Author

@jberry-suse jberry-suse commented Aug 15, 2017

As noted in IRC by ‎Pharaoh_Atem‎: "the issue is that in libsolv-tools 0.6.28, the SUSE packaging was updated to turn on rich deps for %suse_version >= 1330".

Given the plans to run the repo_checker against Leap 15.0 and SLE 15 it likely makes sense to run each in a up-to-date container of the target product.

@jberry-suse

This comment has been minimized.

Copy link
Contributor Author

@jberry-suse jberry-suse commented Aug 18, 2017

Post update to SP3, ended up branching libsolv and building with rich deps enabled. That repo was then added on packagelists and deployed.

@jberry-suse

This comment has been minimized.

Copy link
Contributor Author

@jberry-suse jberry-suse commented Aug 18, 2017

Seems like further reason to find a way to utilize the target project environment or perhaps just the subset of tools used by the bots.

@jberry-suse

This comment has been minimized.

Copy link
Contributor Author

@jberry-suse jberry-suse commented Nov 13, 2017

We should likely document somewhere that it is run this way as also relevant for #1210 since that environment will need to be reproduced in one form or another.

@lnussel moved to Tortuga physical machine in his office for more umph (cpu) as needed and setup as Tumbleweed nspawn container using machinectl.

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

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.