-----BEGIN PGP SIGNED MESSAGE-----
On Monday 13 June 2011, Jeff Johnson <email@example.com> wrote:
> You can try reading the rpmdb with pre-rpm-5.3 to assess how much data
> is savable. (...)
Ok, I salvaged what I could and replaced the rest from a backup. I found out
that there (a) was a corrupted RPMDB, but re-running (b) dbconvert.sh later
on in a futile attempt to fix it made things worse. So byteswapping and
rebuilding largely helped. TA!
> > Do you have any hint/idea why "rpm -r /my/chroot -Uvh
> > /some/package.rpm" kills the RPMDB *outside* of the chroot? Did I miss
> > anything here?
> I don't know what operations were run, and with what utilities, so
> I cannot hazard a guess.
Only one, which is "rpm -r /srv/vm/buildroot -Uvh $(<
~/Packaging/baseset.txt)". I.e., basic chroot populating.
> If you believe that rpm is confused about outer <-> inner chroot(2)
> behavior, then you need to run
> strace -e open -o /tmp/xyzzy -f rpm …
> and examine the paths that were opened.
> In _ALL_ cases, doing
> chroot /your/chroot /bin/bash
> and avoiding -r "works".
Ok, I'll do that.
What's the preferred way to initially populate a chroot?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
-----END PGP SIGNATURE-----
Received on Mon Jun 13 17:05:59 2011