From: "Espen Carlsen" <ec@numascale.com>
To: "'Paul Bolle'" <pebolle@tiscali.nl>
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, 8 Jul 2015 17:42:23 +0200 [thread overview]
Message-ID: <00fe01d0b994$af584380$0e08ca80$@numascale.com> (raw)
In-Reply-To: <1436365587.20619.19.camel@tiscali.nl>
From: Paul Bolle [mailto:pebolle@tiscali.nl]
> On ma, 2015-07-06 at 21:37 +0200, Espen Carlsen wrote:
> 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?
Correct. And modifying the two ln -sf commands in mkspec makes that happen on a Ubuntu system.
I have tested my suggested changes on:
CentOS 6.5, 7.0, Ubuntu 14.04 and 12.04. After the patch the kernel-devel package will be correct on all systems.
Without the patch, only CentOS generates correct packages.
Espen
next prev parent reply other threads:[~2015-07-08 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 11:47 [PATCH, resend] build: fix broken kernel RPM source symlink Espen Carlsen
2015-07-04 10:19 ` Paul Bolle
2015-07-06 19:37 ` Espen Carlsen
2015-07-08 14:26 ` Paul Bolle
2015-07-08 15:42 ` Espen Carlsen [this message]
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='00fe01d0b994$af584380$0e08ca80$@numascale.com' \
--to=ec@numascale.com \
--cc=daniel@numascale.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=pebolle@tiscali.nl \
--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