From: Ross Burton <Ross.Burton@arm.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "alex.kanavin@gmail.com" <alex.kanavin@gmail.com>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Rusty Howell <rustyhowell@gmail.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] debian packaging: set md5sums for conffiles
Date: Wed, 27 Jul 2022 14:08:39 +0000 [thread overview]
Message-ID: <7536019F-34C9-44D8-9380-425C4FE67207@arm.com> (raw)
In-Reply-To: <22FA8BA8-2F9D-4914-9C05-5385EBA4D90A@arm.com>
> So we’re definitely not generating the DEBIAN/md5sums files that dpkg-deb likes to have. However, this file in proper Debian packages doesn’t contain hashes for the conffiles, so I can only imagine that dpkg generates them on install, which leads to the question of where that is meant to happen.
dpkg —configure does this, but we’re neutering it by renaming all foo.dpkg-new files to foo in the deb install() function.
If we’re going to rename foo.dpkg-new to foo, then that is where we go and update the status file.
Alternatively, we don’t do that, and every package needs to run its configure step on first boot.
Ross
next prev parent reply other threads:[~2022-07-27 14:09 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 ` [OE-core] " Luca Ceresoli
2022-07-27 11:48 ` Alexander Kanavin
2022-07-27 12:25 ` Ross Burton
2022-07-27 13:56 ` Ross Burton
2022-07-27 14:08 ` Ross Burton [this message]
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=7536019F-34C9-44D8-9380-425C4FE67207@arm.com \
--to=ross.burton@arm.com \
--cc=alex.kanavin@gmail.com \
--cc=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.