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.

Sign up for GitHub

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

Jump to bottom

Support for rpmdb in /usr #7346

Closed
2 tasks done
marmarek opened this issue Mar 13, 2022 · 0 comments
Closed
2 tasks done

Support for rpmdb in /usr #7346

marmarek opened this issue Mar 13, 2022 · 0 comments
Labels
C: builder Qubes Builder C: Fedora P: default Priority: default. Default priority for new issues, to be replaced given sufficient information.
Milestone
Release 4.1 updates

Comments

@marmarek
Copy link
Member

marmarek commented Mar 13, 2022 •
edited
Loading

How to file a helpful issue

The problem you're addressing (if any)

Fedora 36 has rpmdb moved to /usr: https://fedoraproject.org/wiki/Changes/RelocateRPMToUsr
Currently it breaks at least the template build, but probably few other things too.

The solution you'd like

Adjust / verify:

  • template builder
  • VM's part of qubes-dom0-update

The value to a user, and who that user might be

Necessary for Fedora 36 template (#7342 )
@marmarek marmarek added T: enhancement C: builder Qubes Builder C: Fedora P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. labels Mar 13, 2022
@andrewdavidwong andrewdavidwong added this to the Release 4.1 updates milestone Mar 13, 2022
@xaki23 xaki23 mentioned this issue May 21, 2022
Merged
marmarek added a commit to marmarek/qubes-builder-rpm that referenced this issue May 26, 2022
@marmarek
Do not hardcode specific rpmdb location
3c944dd 
prepare-chroot-base always uses rpm from the host, so it can very well
keep the rpmdb location as the host's rpm preference. The template build
script will do import+export anyway, so it will do the database
relocation implicitly.
Adjust cleanup calls to not depend on specific rpmdb location.

QubesOS/qubes-issues#7346
@marmarek marmarek mentioned this issue May 26, 2022
Merged
marmarek added a commit to marmarek/qubes-builder-rpm that referenced this issue May 26, 2022
@marmarek
Do not hardcode specific rpmdb location
595f877 
prepare-chroot-base always uses rpm from the host, so it can very well
keep the rpmdb location as the host's rpm preference. The template build
script will do import+export anyway, so it will do the database
relocation implicitly.
Adjust cleanup calls to not depend on specific rpmdb location.

QubesOS/qubes-issues#7346
marmarek added a commit to marmarek/qubes-builder-rpm that referenced this issue May 26, 2022
@marmarek
Do not hardcode specific rpmdb location
c0b3d78 
prepare-chroot-base always uses rpm from the host, so it can very well
keep the rpmdb location as the host's rpm preference. The template build
script will do import+export anyway, so it will do the database
relocation implicitly.
Adjust cleanup calls to not depend on specific rpmdb location.

QubesOS/qubes-issues#7346
marmarek added a commit to marmarek/qubes-builder-rpm that referenced this issue May 26, 2022
@marmarek
Do not hardcode specific rpmdb location
d04af9b 
prepare-chroot-base always uses rpm from the host, so it can very well
keep the rpmdb location as the host's rpm preference. The template build
script will do import+export anyway, so it will do the database
relocation implicitly.
Adjust cleanup calls to not depend on specific rpmdb location.

QubesOS/qubes-issues#7346
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: builder Qubes Builder C: Fedora P: default Priority: default. Default priority for new issues, to be replaced given sufficient information.
Projects
None yet
Milestone
Release 4.1 updates
Development

No branches or pull requests
2 participants
@marmarek @andrewdavidwong