From: Seebs <seebs@seebs.net>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: pseudo database integrity checking
Date: Mon, 27 Jun 2022 09:11:01 -0500 [thread overview]
Message-ID: <20220627091101.44f09689@seebsdell> (raw)
In-Reply-To: <ced1bde4cd0d5ef021c13088ffe4fd522648811c.camel@linuxfoundation.org>
On Mon, 27 Jun 2022 14:52:39 +0100
Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> b) We could add a new command to run an integrity check on the DB to
> pseudo. If we do that, we would then be able to show the user a decent
> error and above the timeout issue. The question is where/when to
> trigger it and whether races could occur against the check (e.g. where
> multiple fakeroot tasks are running in parallel against the same
> WORKDIR).
I thought there was a function that did roughly this once at some point.
-s
next prev parent reply other threads:[~2022-06-27 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 13:52 pseudo database integrity checking Richard Purdie
2022-06-27 14:11 ` Seebs [this message]
2022-06-27 14:14 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220627091101.44f09689@seebsdell \
--to=seebs@seebs.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox