Replies: 2 comments 1 reply
|
In general you shouldn't need to worry about the details of the specific backend implementations. For comparing the package databases between two deployments I would do a If you really really want to mount it, you can do so with |
1 reply
|
The command you're looking for is Here's a proof of concept I made for diffing the package db using Python (currently only supports pacman & composefs backend): https://github.com/Smujb/bootc-tools/blob/main/bootc-db-diff |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
For testing/troubleshooting of a (staged) deployment on the ostree backend you can just go into
/sysroot/ostree/boot.X/fedora/XXX/and then browse the filesystem of that deployment.How is this supposed to be done on the composefs backend? This would be useful for querying a package database of a deployment to show changelogs between them for example. In the spirit of what
rpm-ostree db diffdoes. As far as I can tell, there is currently no documentation regarding this.Although I noticed when I
mount /sysroot/composefs/images/XXX /mntthere is a skeleton of a filesystem but all the files are "empty", so that is definitely the wrong approach to do that.All reactions