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

libpriv/rpm: Always copy rpmdb even in user mode checkouts #5225

Merged
merged 1 commit into from
Jan 16, 2025

Conversation

cgwalters
Copy link
Member

I'm working on doing container reencapsulation and using a user-mode repo and got burned by the hardlinking here and rpm always writing to the repo even when reading it.

Most systems we care about have reflinks so it's cheap. And in practice most usage of this before was actually checking out from bare (not bare-user) repos, so we were copying anyways.

Copy link
Member

@jmarrero jmarrero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@cgwalters
Copy link
Member Author

/retest

1 similar comment
@cgwalters
Copy link
Member Author

/retest

@cgwalters cgwalters enabled auto-merge January 15, 2025 15:02
I'm working on doing container reencapsulation and using
a user-mode repo and got burned by the hardlinking here
and rpm always *writing* to the repo even when reading it.

Most systems we care about have reflinks so it's cheap. And in practice
most usage of this before was actually checking out from bare
(not bare-user) repos, so we were copying anyways.

Signed-off-by: Colin Walters <[email protected]>
@cgwalters cgwalters force-pushed the copy-bareuser-rpmdb branch from bfba66b to 7832cd4 Compare January 16, 2025 18:50
@cgwalters cgwalters disabled auto-merge January 16, 2025 18:50
@cgwalters cgwalters merged commit 2f470db into coreos:main Jan 16, 2025
16 checks passed
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

Successfully merging this pull request may close these issues.

3 participants