rpm 4.16 landed -> errors!

Neal Gompa ngompa13 at gmail.com
Tue Mar 16 18:57:10 CET 2021


On Tue, Mar 16, 2021 at 1:39 PM Jan Rękorajski <baggins at pld-linux.org> wrote:
>
> On Tue, 16 Mar 2021, Elan Ruusamäe wrote:
>
> >
> > On 16.03.2021 16:45, Elan Ruusamäe wrote:
> > >
> > > the automatic upgrade is failing:
> > >
> > > - https://gitlab.com/pld-linux/pld/-/jobs/1094531330#L214
> > >
> > oh, and user is left without rpmdb:
> >
> >
> > [@46a17bd0ade9 /]# rpm -q rpm poldek
> > warning: Found bdb Packages database while attempting sqlite backend:
> > using bdb backend.
> > warning: Generating 6 missing index(es), please wait...
> > package rpm is not installed
> > package poldek is not installed
> >
> > [@46a17bd0ade9 /]# rpm -q rpm poldek
> > warning: Found bdb Packages database while attempting sqlite backend:
> > using bdb backend.
> > package rpm is not installed
> > package poldek is not installed
> > [@46a17bd0ade9 /]#
>
> First, regarding lost database.
> You do have a backup of the database from before the update:
>
> Backup of the rpm database has been created in /var/lib/rpm.rpmbackup-4.16.1.2-6
>
> There is also the new database, that rpm was unable to move:
>
> error: replace files in /var/lib/rpm with files from /var/lib/rpmrebuilddb.42 to recover
>
> Is /var/lib/rpm a mountpoint? That would be the explanation that comes
> to mind. There must be something that prevented rpm from renaming temporary
> directory in /var/lib to rpm.
>
> I've been (live) testing upgrade path and I assumed it does work.
> Never encountered problems after squashing rpm5 oddities.
>
> I've been also asking over and over for testing and no one came with any
> issues like this.
>

This is probably an overlayfs specific issue, I've seen various
problems with renames (which is what rpm does for rebuilding
databases) in containers.



-- 
真実はいつも一つ!/ Always, there's only one truth!


More information about the pld-devel-en mailing list