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

rojig ♲📦: Prepare server-side design for rojig-only #1237

Open
cgwalters opened this issue Feb 7, 2018 · 2 comments
Open

rojig ♲📦: Prepare server-side design for rojig-only #1237

cgwalters opened this issue Feb 7, 2018 · 2 comments
Assignees

Comments

@cgwalters
Copy link
Member

cgwalters commented Feb 7, 2018

As part of rojig ♲📦 we want to support OS vendors shipping in "rojig only" mode, where they don't have a public OSTree repository; more strongly, support a mode where OSTree repositories are just optional caches.

Today,
rpm-ostree compose tree --ex-output-jigdo-set also requires --repo and things like the "did the commit change" detection logic rely on it.

What we want is something like: --ex-jigdo-repo that contains the input repository that contains jigdoRPMs - we then parse it server side and pull out the latest jigdoRPM, pull out the commit, and from there we have the "input checksum" we use to detect changes.

@cgwalters cgwalters changed the title jigdo ♲📦: Prepare server-side design for jigdo-only rojig ♲📦: Prepare server-side design for rojig-only Feb 22, 2018
@cgwalters
Copy link
Member Author

I started hacking on this, basically supporting drop the --repo argument to compose tree.

One thing I really quickly realized is that this basically requires depending on some sane way to version rpm-md repositories. In this mode, we're accepting an rpm-md repo as input and also our output is an rpm-md repo. Do we modify the input repository in place? Do we do something like what pungi does and output separate datestamped repos?

We might be able to punt on this a bit for now...basically mutate the input repo in place (require it to be file://). Anyone who wants to e.g. implement datestamped repos could do that by just CoW'ing the repo.

However, punting here defers the layered package problem; rpm-ostree deploy $version should also pin layered packages. Like yum distro-sync --version X. We could try adding just a little bit more metadata on top of pungi compose directories.

@cgwalters
Copy link
Member Author

PR in #1512

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

No branches or pull requests

1 participant