From: Ben Hutchings <ben@decadent.org.uk>
To: Henning Schild <henning.schild@siemens.com>
Cc: linux-kernel@vger.kernel.org,
Ben Hutchings <ben.hutchings@codethink.co.uk>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org,
Konrad Schwarz <konrad.schwarz@siemens.com>
Subject: Re: [PATCH] builddeb: introduce variables for control-file customization
Date: Mon, 04 Dec 2017 14:35:47 +0000 [thread overview]
Message-ID: <1512398147.2768.20.camel@decadent.org.uk> (raw)
In-Reply-To: <20171204100150.1f040839@md1em3qc>
[-- Attachment #1: Type: text/plain, Size: 2056 bytes --]
On Mon, 2017-12-04 at 10:01 +0100, Henning Schild wrote:
> Am Fri, 1 Dec 2017 18:47:38 +0000
> schrieb Ben Hutchings <ben@decadent.org.uk>:
>
> > On Fri, 2017-12-01 at 19:34 +0100, Henning Schild wrote:
> > > Am Fri, 1 Dec 2017 16:51:12 +0000
> > > schrieb Ben Hutchings <ben@decadent.org.uk>:
> > >
> > > > On Fri, 2017-12-01 at 15:56 +0000, Henning Schild wrote:
> > > > > The debian packages coming out of "make *deb-pkg" lack some
> > > > > critical information in the control-files e.g. the "Depends:"
> > > > > field. If one tries to install a fresh system with such a
> > > > > "linux-image" debootstrap or multistrap might try to install
> > > > > the kernel before its deps and the package hooks will fail.
> > > >
> > > > I assume you're talking about those hook scripts being run while
> > > > the packages they belong to are only unpacked? I hadn't thought
> > > > about this issue, but it seems to me that those hook scripts
> > > > generally ought to be fixed to handle this case properly. Most
> > > > of the packages installing hook scripts for kernel packages are
> > > > not going to be dependencies of linux-image packages, so it will
> > > > never be safe for them to assume their package has been fully
> > > > installed.
> > >
> > > Yes these hook scripts fail when installing the kernel on another
> > > system. Indeed we seem to have a case where packages installed on
> > > the build-machine cause install-time deps for the package.
> >
> > Can you give an example? I don't see how that would happen.
>
> Scripts in /etc/kernel/ will end up as hooks for the kernel-package, if
> you do not set KDEB_HOOKDIR. Looking at an example system that pulls in
> things like "pm-utils, grub-pc .. initramfs". With this mechanism any
> package placing a hook in /etc/kernel can influence the deps.
[...]
That is not a dependency. That is an extension mechanism.
Ben.
--
Ben Hutchings
Lowery's Law:
If it jams, force it. If it breaks, it needed replacing anyway.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-04 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 16:13 [PATCH] builddeb: introduce variables for control-file customization Henning Schild
2017-11-27 23:57 ` Jim Davis
2017-11-28 8:41 ` Henning Schild
2017-12-01 16:51 ` Ben Hutchings
2017-12-01 18:34 ` Henning Schild
2017-12-01 18:47 ` Ben Hutchings
2017-12-04 9:01 ` Henning Schild
2017-12-04 13:15 ` Riku Voipio
2017-12-04 14:35 ` Ben Hutchings [this message]
2017-12-04 16:48 ` [PATCH v2] scripts: builddeb: allow customization of "Depends:" fields Henning Schild
2017-12-04 16:50 ` Henning Schild
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=1512398147.2768.20.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=ben.hutchings@codethink.co.uk \
--cc=henning.schild@siemens.com \
--cc=konrad.schwarz@siemens.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=yamada.masahiro@socionext.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox