From: Paul Bolle <pebolle@tiscali.nl>
To: Espen Carlsen <ec@numascale.com>
Cc: "'Michal Marek'" <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
"'Daniel J Blueman'" <daniel@numascale.com>,
"'Steffen Persvold'" <sp@numascale.com>
Subject: Re: [PATCH, resend] build: fix broken kernel RPM source symlink
Date: Wed, 08 Jul 2015 16:26:27 +0200 [thread overview]
Message-ID: <1436365587.20619.19.camel@tiscali.nl> (raw)
In-Reply-To: <006601d0b823$2b144820$813cd860$@numascale.com>
On ma, 2015-07-06 at 21:37 +0200, Espen Carlsen wrote:
> To sum it all up, without the change to mkspec, the package 'kernel
> -devel' package generated on an Ubuntu system is broken, as
> '/lib/modules/4.1.0/build' points to a directory that will not be on
> the server where the package is installed on:
> user@build-ubuntu:/srv/user/rpmbuild/RPMS/x86_64$ rpm -qplv kernel-devel-4.1.0-1.x86_64.rpm
> lrwxrwxrwx 1 root root 35 Jul 4 18:31 /lib/modules/4.1.0/build -> /srv/user/rpmbuild/BUILD/kernel-4.1.0
> lrwxrwxrwx 1 root root 35 Jul 6 12:15 /lib/modules/4.1.0/source -> /srv/user/rpmbuild/BUILD/kernel-4.1.0
> drwxr-xr-x 2 root root 0 Jul 6 12:15 /usr/src/kernels/4.1.0
And you want this to read
lrwxrwxrwx 1 root root 35 Jul 4 18:31 /lib/modules/4.1.0/build -> /usr/src/kernels/4.1.0
lrwxrwxrwx 1 root root 35 Jul 6 12:15 /lib/modules/4.1.0/source -> /usr/src/kernels/4.1.0
drwxr-xr-x 2 root root 0 Jul 6 12:15 /usr/src/kernels/4.1.0
or something equivalent, right?
Paul Bolle
next prev parent reply other threads:[~2015-07-08 14:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 11:47 Espen Carlsen
2015-07-04 10:19 ` Paul Bolle
2015-07-06 19:37 ` Espen Carlsen
2015-07-08 14:26 ` Paul Bolle [this message]
2015-07-08 15:42 ` Espen Carlsen
2015-07-08 16:18 ` Paul Bolle
2015-07-08 18:47 ` Espen Carlsen
2015-07-08 18:52 ` Paul Bolle
2015-07-08 16:56 ` Paul Bolle
2015-07-09 9:29 ` Espen Carlsen
2015-08-19 15:14 ` Michal Marek
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=1436365587.20619.19.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=daniel@numascale.com \
--cc=ec@numascale.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sp@numascale.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
Powered by JetHome