From: <doiggl@velocitynet.com.au>
To: reiserfs-devel@vger.kernel.org
Subject: Reiser4 reiser4-for-4.1.5.patch.gz patch failed to build with linux-4.2.tar.xz
Date: Tue, 01 Sep 2015 23:37:12 +1000 [thread overview]
Message-ID: <c23690c5c7cc7267f4c591fe76620dbd@mail.velocitynet.com.au> (raw)
Hello,
Just found out Reiser4 reiser4-for-4.1.5.patch.gz patch failed to build
with linux-4.2.tar.xz
Can a version be provided/patched for 4.2x please ?
Thanks Glenn
Error log:
.
.
[ 140s] + cd /home/abuild/rpmbuild/BUILD
[ 140s] + rm -rf kernel-vanilla-4.2.0
[ 140s] + /usr/bin/mkdir -p kernel-vanilla-4.2.0
[ 140s] + cd kernel-vanilla-4.2.0
[ 140s] + /usr/bin/xz -dc /home/abuild/rpmbuild/SOURCES/linux-4.2.tar.xz
[ 140s] + /bin/tar -xf -
[ 161s] + STATUS=0
.
.
[ 165s] + cd linux-4.2
[ 165s] + /home/abuild/rpmbuild/SOURCES/apply-patches --vanilla
/home/abuild/rpmbuild/SOURCES/series.conf ..
[ 165s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i
../patches.rpmify/reiser4-for-4.1.5.patch
[ 165s] 3 out of 8 hunks FAILED -- saving rejects to file
fs/fs-writeback.c.rej
[ 165s] 1 out of 1 hunk FAILED -- saving rejects to file
include/linux/mm.h.rej
[ 165s] 1 out of 2 hunks FAILED -- saving rejects to file
include/linux/writeback.h.rej
[ 165s] ++ echo '*** patch ../patches.rpmify/reiser4-for-4.1.5.patch
failed ***'
[ 165s] *** patch ../patches.rpmify/reiser4-for-4.1.5.patch failed ***
[ 166s] error: Bad exit status from /var/tmp/rpm-tmp.VdiQ8y (%prep)
build location and log
========================
https://build.opensuse.org/package/show/home:doiggl/kernel-vanilla
https://build.opensuse.org/build/home:doiggl/openSUSE_13.1/x86_64/kernel-vanilla/_log
https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.2.tar.xz
reply other threads:[~2015-09-01 13:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c23690c5c7cc7267f4c591fe76620dbd@mail.velocitynet.com.au \
--to=doiggl@velocitynet.com.au \
--cc=reiserfs-devel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).