From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Devel discussion list <devel@lists.altlinux.org>
Subject: Re: [devel] [PATCH for rpm] Add triggers circumvension for packagekit offline update
Date: Fri, 1 Nov 2019 21:58:44 +0300
Message-ID: <20191101185842.GA7204@altlinux.org> (raw)
In-Reply-To: <7d94a565-0723-68ca-717b-f86ef1256356@altlinux.org>
[-- Attachment #1: Type: text/plain, Size: 1731 bytes --]
On Thu, Oct 31, 2019 at 04:19:16PM +0300, Aleksei Nikiforov wrote:
> 31.10.2019 15:59, Dmitry V. Levin пишет:
> > On Thu, Oct 31, 2019 at 02:58:08PM +0300, Aleksei Nikiforov wrote:
> >> Joint change with Oleg Solovyov (mcpain@)
> >
> > Thanks.
> >
> > It's not clear from the commit message why one might need to disable
> > rpmdb --rebuilddb after rpm update.
> >
> > Could you elaborate, please?
>
> packagekit offline update is implemented in following way:
> 1) system is preparing for offline update: all new installed packages
> are downloaded, etc.
> 2) system is rebooting into special systemd offline update mode upon
> user request.
> 3) in this offline update mode packagekit offline update service is
> performing system update using packagekit service activated via dbus.
> 4) Last step of systemd offline update is a reboot request. It must be
> made by offline update service. And packagekit offline update service
> does request it.
>
> Thus, rpmdb --rebuilddb from rpm scripts would be in race against reboot
> request. Testing showed that it doesn't work properly in such
> conditions. In best case, rpmdb --rebuilddb doesn't do anything at all
> before reboot happens. Instead of hoping to get it work properly in such
> conditions, disabling it in rpm scripts and calling it right after
> update but before reboot request from packagekit offline update works fine:
OK, I cannot say that I like this approach, but at least it makes sense.
The alternative is invoking pk-offline-update in a separate pid namespace
which is probably not as simple as disabling rpm %post.
Could you add the rationale from your post into the commit message,
please?
--
ldv
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2019-11-01 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 11:58 Aleksei Nikiforov
2019-10-31 12:59 ` Dmitry V. Levin
2019-10-31 13:19 ` Aleksei Nikiforov
2019-11-01 18:58 ` Dmitry V. Levin [this message]
2019-11-05 12:40 ` [devel] [PATCH for rpm v3] " Aleksei Nikiforov
2019-10-31 13:24 ` [devel] [PATCH for rpm v2] " Aleksei Nikiforov
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=20191101185842.GA7204@altlinux.org \
--to=ldv@altlinux.org \
--cc=devel@lists.altlinux.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
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git