From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Rusty Howell" <rustyhowell@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] debian packaging: set md5sums for conffiles
Date: Wed, 27 Jul 2022 12:53:39 +0200 [thread overview]
Message-ID: <20220727125339.70e1886c@booty> (raw)
In-Reply-To: <20220726211328.2122681-1-rustyhowell@gmail.com>
Hello Rusty,
On Tue, 26 Jul 2022 15:13:28 -0600
"Rusty Howell" <rustyhowell@gmail.com> wrote:
> Currently in an image created with debian package management, dpkg is missing the md5sums in
> /var/lib/dpkg/status for files designated as conffiles. They are just listed as "newconffile",
> which is an intermediate state when dpkg installs a package with an conf file. Also, when the
> device first boots the script /usr/sbin/run-postinsts does not cause /var/lib/dpkg/status to update
> those hashes either.
>
> The problem here is that when using a package feed, all the conf files are listed as "newconffile",
> which will indicate to dpkg to replace them all on the first update. dpkg will not follow the rules for
> confold, confnew, confdef.
This patch does not apply on the current master branch of oe-core.
Maybe you wrote it on an older commit or on a branch (e.g. kirkstone)?
Also we require you so sign-off the patches you send on the mailing
list ('git commit -s' does that automatically).
Best regards.
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-07-27 10:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 21:13 [PATCH] debian packaging: set md5sums for conffiles Rusty Howell
2022-07-27 10:53 ` Luca Ceresoli [this message]
2022-07-27 11:48 ` [OE-core] " Alexander Kanavin
2022-07-27 12:25 ` Ross Burton
2022-07-27 13:56 ` Ross Burton
2022-07-27 14:08 ` Ross Burton
2022-07-27 14:32 ` Rusty Howell
2022-07-27 14:35 ` Alexander Kanavin
2022-07-27 15:31 ` Rusty Howell
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=20220727125339.70e1886c@booty \
--to=luca.ceresoli@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rustyhowell@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.