[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#807670: marked as done (Can't build linux-tools-4.2 package)

Your message dated Sat, 12 Dec 2015 12:21:49 +0000
with message-id <1449922909.3836.13.camel@decadent.org.uk>
and subject line Re: Can't build linux-tools-4.2 package
has caused the Debian Bug report #807670,
regarding Can't build linux-tools-4.2 package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
807670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807670
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-perf
Version: 4.2
Source: linux-tools-4.2-2


Hello!
When I try to build source package I got error.
Command: dpkg-buildpackage -uc -us -nc -d -S -i -I --source-option=--unapply-patches 
Result:
dpkg-buildpackage: source package linux-tools
dpkg-buildpackage: source version 4.2-2
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Ben Hutchings <ben@decadent.org.uk>
 dpkg-source -i -I --unapply-patches --before-build linux-tools-4.2
dpkg-source: info: using options from linux-tools-4.2/debian/source/options: --compression=xz 
dpkg-source: info: applying gitignore.patch
dpkg-source: info: applying modpost-symbol-prefix.patch
can't find file to patch at input line 15
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|From: Chris Boot <debian@bootc.net>
|Date: Mon, 01 Jul 2013 23:10:02 +0100
|Subject: modpost symbol prefix setting
|Forwarded: not-needed
|
|[bwh: The original version of this was added by Bastian Blank.  The
|upstream code includes <generated/autoconf.h> so that <linux/export.h>
|can tell whether C symbols have an underscore prefix.  Since we build
|modpost separately from the kernel, <generated/autoconf.h> won't exist.
|However, no Debian Linux architecture uses the symbol prefix, so we
|can simply omit it.]
|
|--- a/scripts/mod/modpost.c
|+++ b/scripts/mod/modpost.c
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
dpkg-source: info: the patch has fuzz which is not allowed, or is malformed dpkg-source: info: if patch 'modpost-symbol-prefix.patch' is correctly applied by quilt, use 'quilt refresh' to update it dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/modpost-symbol-prefix.patch/ --reject-file=- < linux-tools-4.2/debian/patches/modpost-symbol-prefix.patch gave error exit status 1 dpkg-buildpackage: error: dpkg-source -i -I --unapply-patches --before-build linux-tools-4.2 gave error exit status 2
If I execute build command again without cleaning catalog source package will be build successfully. I make my build with git-buildpackage software. And I have separated debian and upstream branches, which specified in debian/gbp.conf. If I manually create .gitignore file like this doing patch gitignore.path that build will be successful too. I have many other packages which do not behave strangely. 

Whats wrong with tis repo?

--- End Message ---
--- Begin Message --- 
On Fri, 11 Dec 2015 17:07:29 +0300 Alexey <alukardd@alukardd.org>
wrote:
> Package: linux-perf
> Version: 4.2
> Source: linux-tools-4.2-2
> 
> 
> Hello!
> When I try to build source package I got error.
[...]

It builds fine on the build daemons:
https://buildd.debian.org/status/package.php?p=linux-tools&suite=sid

So you are probably doing something wrong when unpacking the source
package.  The BTS is not a support channel; please see
<https://www.debian.org/support>.

Ben.

-- 
Ben Hutchings
Knowledge is power.  France is bacon.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: