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

pkglistgen: sync solv cache to shared location #1407

Closed
jberry-suse opened this issue Feb 15, 2018 · 3 comments
Closed

pkglistgen: sync solv cache to shared location #1407

jberry-suse opened this issue Feb 15, 2018 · 3 comments
Assignees

Comments

@jberry-suse
Copy link
Contributor

@jberry-suse jberry-suse commented Feb 15, 2018

As discussed previous a shared location would be handy for testing to compare result against live which will have historical builds that cannot be reproduced.

Essentially need ~/.cache/opensuse-packagelists/solv/ sync'd before and after each run.

@jberry-suse

This comment has been minimized.

Copy link
Contributor Author

@jberry-suse jberry-suse commented Mar 7, 2018

@lnussel I know you suggested OBS, but perhaps just another git repo that way we can periodically rebase into single commit to drop old files.

I suppose OBS has the advantage of permissions as we could add factory-staging or the tools group (probably tools makes more sense) and thus avoid needing to add people to another group. Dunno.

@jberry-suse

This comment has been minimized.

Copy link
Contributor Author

@jberry-suse jberry-suse commented Mar 8, 2018

Assuming this will store solv files outside of individual products it should likely live outside of product project tree in OBS if we use that. As such perhaps openSUSE:Tools or where?

Alternatively, we create a new git repo (presumably under openSUSE namespace which I cannot do). Perhaps package-lists-archive, package-lists-solv-archive or similar. With #1441 the git option is likely easier since the packagelists code always does a clean checkout due to mentioned osc sync issues. Perhaps it won't apply to this type of package setup. Either way.

For local development read access is all that is required which is easy on OBS or git. We can use a deploy key for deployed push to git.

@coolo

This comment has been minimized.

Copy link
Member

@coolo coolo commented Dec 10, 2018

Discussed the options and @lnussel and @DimStar77 preferred a package within the target project - and behlert has no objections. So going ahead with this option

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.