On Jo, 06 nov 14, 20:08:50, basti wrote:
> Hello,
> I know that this can be a bit off-topic.
> When I try to build a package based on git and use
>
> git-buildpackage => docs are not include in deb-file.
> dpkg-buildpackage => docs ARE include in deb-file.
>
> dh_in
Hello,
I know that this can be a bit off-topic.
When I try to build a package based on git and use
git-buildpackage => docs are not include in deb-file.
dpkg-buildpackage => docs ARE include in deb-file.
dh_installdocs is included in rules at anytime.
I don't understand.
How can e
ith the new version
of kernel-package yet. Both methods work fine for building the
kernel image package, but only the second one works for building
a headers package. Note that I was referring specifically to
make-kpkg and not dpkg-buildpackage in general.
--
.''`. Stephen Powell
On Mon, 26 May 2014, Ralf Mardorf wrote:
> I build kernel packages without fakeroot, since I'm running my scripts
> as root.
There's no reason to ever build any packages as root. It's not
necessary, and can lead to overwriting files that you want if there are
bugs in the build scripts.
> I read s
On Tue, May 27 2014, Ralf Mardorf wrote:
> "Note that when building a headers package you must run the entire
> make-kpkg command under fakeroot: you can't use the --rootcmd fakeroot
> option in this case." -
> https://lists.debian.org/debian-user/2012/10/msg2.html
Is that accurate?
-
"Note that when building a headers package you must run the entire
make-kpkg command under fakeroot: you can't use the --rootcmd fakeroot
option in this case." -
https://lists.debian.org/debian-user/2012/10/msg2.html
So I'm 50% mistaken and 50% right ;). I anyway need to run my scripts as
root
On Tue, May 27, 2014 at 11:20:01AM +0300, Mihamina Rakotomandimby wrote:
> On 05/27/2014 11:15 AM, Chris Bannister wrote:
> >On Mon, May 26, 2014 at 05:06:01PM +0200, Ralf Mardorf wrote:
> >>>On Mon, 2014-05-26 at 18:58 +0400, Reco wrote:
> >fakeroot
> >>>
> >>>... regarding to some claims on
On 05/27/2014 11:15 AM, Chris Bannister wrote:
On Mon, May 26, 2014 at 05:06:01PM +0200, Ralf Mardorf wrote:
>On Mon, 2014-05-26 at 18:58 +0400, Reco wrote:
> >fakeroot
>
>... regarding to some claims on this list is a PITA, at least when
>building a kernel. I run my scripts to build kernel-rt
On Mon, May 26, 2014 at 05:06:01PM +0200, Ralf Mardorf wrote:
> On Mon, 2014-05-26 at 18:58 +0400, Reco wrote:
> > fakeroot
>
> ... regarding to some claims on this list is a PITA, at least when
> building a kernel. I run my scripts to build kernel-rts as root.
It's a good idea to recommend best
On 05/26/2014 05:58 PM, Reco wrote:
On Mon, 26 May 2014 14:17:51 +0300
George Shuklin wrote:
How can I to rebuild deb second time? It looks like I miss some cleanup
command.
Usually the 'fakeroot debian/rules clean' returns the package's sources
to the initial state. Such behaviour is require
l package?
>
> If you're building a kernel, you only root privs for the 'make
> modules_install" and "make install" steps.
>
> If you're building a package using "make deb-pkg", pass
> "KBUILD_PKG_ROOTCMD=fakeroot" for fakeroot to be used when n
l" steps.
If you're building a package using "make deb-pkg", pass
"KBUILD_PKG_ROOTCMD=fakeroot" for fakeroot to be used when needed.
If you're building a package using "dpkg-buildpackage", fakeroot is
used when needed.
You can also use "KBUILD_
bian/source/options
file to ignore changes in some file(s), e.g.:
extend-diff-ignore = "(^|/)build/.*/neutron/api/__init__.py$"
Of course, you can adjust regexp/path. And finally, i will suggest to
replace the dpkg-buildpackage by the debuild, which call the
dpkg-buildpackage and then the li
ally worked every time.
But that's irrelevant. What is relevant is that dpkg-buildpackage uses
fakeroot. So, if OP used dpkg-buildpackage more-or-less successfully -
'fakeroot debian/rules' should work for him too.
Reco
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.or
On 2014-05-26 17:06 +0200, Ralf Mardorf wrote:
> On Mon, 2014-05-26 at 18:58 +0400, Reco wrote:
>> fakeroot
>
> ... regarding to some claims on this list is a PITA, at least when
> building a kernel.
*All* Debian packages are built using fakeroot, and this works just
fine.
> I run my scripts to
On Mon, 2014-05-26 at 18:58 +0400, Reco wrote:
> fakeroot
... regarding to some claims on this list is a PITA, at least when
building a kernel. I run my scripts to build kernel-rts as root.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Troubl
Hi.
On Mon, 26 May 2014 14:17:51 +0300
George Shuklin wrote:
> How can I to rebuild deb second time? It looks like I miss some cleanup
> command.
Usually the 'fakeroot debian/rules clean' returns the package's sources
to the initial state. Such behaviour is required by Debian Policy
Manual ch
Good day.
I'm playing with dpkg, but I got rather strange problem: Package can not
be build second time after 1st package was build.
dpkg-buildpackage -sa
dpkg-source: warning: newly created empty file
'build/lib.linux-x86_64-2.7/neutron/api/__init__.py' will not be
Yes i want to and i am going to read New Maintainers Guide.If i have further
problem ,I will share and explain more precisely my problem.
And very thanks for replied and advice.
--
Iyi calismalar.Basarilar...
Semih Gokalp
Istanbul/Turkiye
>
> and download "xyz_1.0.orig.tar.gz" , "xyz._1.0.diff.gz" and
> "xyz_1.0.dsc" and automaticly extract "xyz.orig.tar.gz" to "xyz-1.0"
> folder and I have been applying some patch and other things to xyz-1.0 and
>
> # dpkg-buildpack
> You should do "dpkg-source -x xyz_1.2.dsc". This command will unpack
> xyz-1.2.orig.tar.gz
> and apply xyz_1.2.diff.gz. Only then you should apply your patch and then
> do
> 'dpkg-buildpackage'.
>
Thanks for reply.It works.
Thanks again.
--
Iyi calisma
>
> and download "xyz_1.0.orig.tar.gz" , "xyz._1.0.diff.gz" and
> "xyz_1.0.dsc" and automaticly extract "xyz.orig.tar.gz" to "xyz-1.0"
> folder and I have been applying some patch and other things to xyz-1.0 and
>
> # dpkg-buildpack
z" and "xyz_1.0.dsc"
and automaticly extract "xyz.orig.tar.gz" to "xyz-1.0" folder and I have
been applying some patch and other things to xyz-1.0 and
# dpkg-buildpackage
and deb package is builded successfully :) I dont have any problem.
But i want to app
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Apr 24, 2007 at 03:59:56AM -0700, John Pye wrote:
> Hi all,
>
> I'm trying to get my head around package building with Debian, coming
> from my earlier experiences with RPMs.
two bits:
the debian-mentors mailing list and website (google will f
y of building a .deb package from a single
> tarball like this?
Not that I know of. But you can do it from an expanded source directory
in several ways:
$ cd $sourcedir ; dpkg-buildpackage -rfakeroot
or if you just want the .deb and don't need build-dependencies checked:
$ cd $sourc
ckages using
dpkg-buildpackage -us -uc -rfakeroot
I am not sure where subversion comes into picture in your problem. May be I
am not understanding the question properly.
Roberto has written a very good document on customizing debian packages with
detailed instructions. But unfortunately I could not
On Tue, Apr 24, 2007 at 03:59:56AM -0700, John Pye wrote:
> Hi all,
>
> So: assuming I have complete control over what is in my tarball, what
> is the neatest, tidiest and safest way to set up and run an
> actual .deb build?
>
Since you mention subversion in the subject line, you want
svn-buildpa
Hi all,
I'm trying to get my head around package building with Debian, coming
from my earlier experiences with RPMs.
One technique which I found quite good with RPMs was the ability to
create a tarball that *included* the necessary .spec file, and then
just typing "rpmbuild -ta mytarball.tar.bz2"
> .libs/display_options.o: In function `compDisplayInitOptions':
> ../src/display_options.c:268: undefined reference to `XStringToKeysym'
> ../src/display_options.c:285: undefined reference to `XStringToKeysym'
> ../src/display_options.c:302: undefined reference to `XStringToKeysym'
> ../src/displa
Adam Porter wrote:
Magnus Pedersen wrote:
I'm building from the 0.14 release tarballs and this is my buildcommand
and path:
[EMAIL PROTECTED]:~/Desktop/beryl/build/beryl-core-0.1.4$
dpkg-buildpackage -rfakeroot
The final error looks like this:
/home/magnus/Desktop/beryl/build/beryl
Magnus Pedersen wrote:
> I'm building from the 0.14 release tarballs and this is my buildcommand
> and path:
>
> [EMAIL PROTECTED]:~/Desktop/beryl/build/beryl-core-0.1.4$
> dpkg-buildpackage -rfakeroot
>
> The final error looks like this:
>
> /home/magnus/Desk
Adam Porter wrote:
Magnus Pedersen wrote:
I'm trying to build .debs of beryl:
I can build the source without problems with :
./configure
make
But when I try to build with dpkg-buildpackage -rfakeroot I end up with
a lot linies like this and an error:
/home/magnus/Desktop/beryl/beryl
Magnus Pedersen wrote:
> I'm trying to build .debs of beryl:
>
> I can build the source without problems with :
> ./configure
> make
>
> But when I try to build with dpkg-buildpackage -rfakeroot I end up with
> a lot linies like this and an error:
>
> /h
I'm trying to build .debs of beryl:
http://beryl-project.org .
I can build the source without problems with :
./configure
make
But when I try to build with dpkg-buildpackage -rfakeroot I end up with
a lot linies like this and an error:
/home/magnus/Desktop/beryl/beryl-core-
Scott Edwards wrote:
> I'm building a lib under sarge in a debootstrap chroot as a normal
> user (and fakeroot). When it gets to this part, it's trying to modify
> the system /etc/ld.so.conf (which is naughty afaict). What's the
> proper way to prepare this?
>
> Thanks
>
> - Scott.
Hi Scott,
On 2006-11-18, Scott Edwards wrote:
> I'm building a lib under sarge in a debootstrap chroot as a normal
> user (and fakeroot). When it gets to this part, it's trying to modify
> the system /etc/ld.so.conf (which is naughty afaict). What's the
> proper way to prepare this?
>
> Thanks
>
> - Scott.
I'm building a lib under sarge in a debootstrap chroot as a normal
user (and fakeroot). When it gets to this part, it's trying to modify
the system /etc/ld.so.conf (which is naughty afaict). What's the
proper way to prepare this?
Thanks
- Scott.
make[3]: Entering directory `/usr/local/src/lib
http://www.devarticles.com/c/a/PHP/Executing-Microsoft-SQL-Server-Stored-Procedure-from-PHP-on-Linux
).
I use “apt-get source php4”, “apt-get build-dep php4“ and dpkg-buildpackage to build.There are several obstacles that are easely overcome while running dpkg-buildpackage in the source php4-4.4.4 dir, these
David Madore wrote:
> I'm trying to compile a Debian kernel package from "unstable" (on a
> "testing" system) using dpkg-buildpackage, with a few minor changes to
> the config file. I've upgraded a few packages (such as kernel-package
> and dh-kpatches) t
Hi.
I'm trying to compile a Debian kernel package from "unstable" (on a
"testing" system) using dpkg-buildpackage, with a few minor changes to
the config file. I've upgraded a few packages (such as kernel-package
and dh-kpatches) to "unstable", so testin
i would like to know how to compile a package without using the default
Makefile. I have downloaded the *.tar.gz and *.diff.gz. And, i have to
specify a switch on ./configure. I tried running
#./configure -thread // to make the binary multi-threaded
then
#dpkg-builpackage // to build deb
10:17:58PM -0700, [EMAIL PROTECTED] wrote:
Is anyone successfully using "distcc" with "dpkg-buildpackage"?
I tried:
---
MAKE="make -j4" CC=distcc DISTCC_HOSTS="localhost kas"
dpkg-buildpackage
---
but "distcc" wasn't used : (
Frequently the pa
On Sat, Apr 17, 2004 at 10:17:58PM -0700, [EMAIL PROTECTED] wrote:
> Is anyone successfully using "distcc" with "dpkg-buildpackage"?
>
> I tried:
> ---
> MAKE="make -j4" CC=distcc DISTCC_HOSTS="localhost kas" dpkg-buildpackage
> ---
>
Is anyone successfully using "distcc" with "dpkg-buildpackage"?
I tried:
---
MAKE="make -j4" CC=distcc DISTCC_HOSTS="localhost kas" dpkg-buildpackage
---
but "distcc" wasn't used : (
Jack
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
w
On Mon, Mar 31, 2003 at 09:09:22AM +0530, Muralikrishnan B wrote:
> On Mon, 2003-03-31 at 03:12, David Z Maze wrote:
> > Muralikrishnan B <[EMAIL PROTECTED]> writes:
> >
> > > How can get I dpkg-buildpackage to install the source package i'm
> > &
On Mon, 2003-03-31 at 03:12, David Z Maze wrote:
> Muralikrishnan B <[EMAIL PROTECTED]> writes:
>
> > How can get I dpkg-buildpackage to install the source package i'm
> > compiling in a different path (just like ./configure
> > --prefix=/custom/path) ?
>
Muralikrishnan B <[EMAIL PROTECTED]> writes:
> How can get I dpkg-buildpackage to install the source package i'm
> compiling in a different path (just like ./configure
> --prefix=/custom/path) ?
You'd need to edit the debian/rules script to configure the package
appro
On Sat, Mar 29, 2003 at 07:11:39PM +0530, Muralikrishnan B wrote:
> How can get I dpkg-buildpackage to install the source package i'm
> compiling in a different path (just like ./configure
> --prefix=/custom/path) ?
Why? dpkg will have enough informatio to cleanly remove anything y
How can get I dpkg-buildpackage to install the source package i'm
compiling in a different path (just like ./configure
--prefix=/custom/path) ?
rgds
--mkb
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Jason Healy <[EMAIL PROTECTED]> wrote:
>At 988753708s since epoch (05/01/01 10:48:28 -0400 UTC), Jeremy Rosen wrote:
>> Usually, I just type dpkg-buildpackage in the proper directory, and
>> everything is built correctly. But since a couple of days, dpkg gives me
&
At 988753708s since epoch (05/01/01 10:48:28 -0400 UTC), Jeremy Rosen wrote:
>
> I have a small problem with dpkg-buildpackage.
>
> I have a software I upgrade from time to time with cvs, which comes bundled
> with a debian directory containing everything to build the .deb archiv
Hello all...
I have a small problem with dpkg-buildpackage.
I have a software I upgrade from time to time with cvs, which comes bundled
with a debian directory containing everything to build the .deb archive.
Usually, I just type dpkg-buildpackage in the proper directory, and everything
is
On Thursday 26 April 2001 01:15, Stephen E. Hargrove wrote:
> i just did a dpkg-buildpackage on a tar.gz i downloaded. it appears to
> have worked. my question is, what do i do now to get everything pulled
> into a .deb file or get the stuff installed?
dpkg-buildpackage creates a .de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i just did a dpkg-buildpackage on a tar.gz i downloaded. it appears to
have worked. my question is, what do i do now to get everything pulled
into a .deb file or get the stuff installed?
if there's a document online explaining all of this,
e with the changed
> configuration file (because dpkg-buildpackage wipes out my build tree
> everytime it runs).
debian/rules has a number of targets, dpkg-buildpackage automatically
calls the clean target. However you can also do something like e.g.
$ fakeroot debian/rules binary
to bypass clea
changed
configuration file (because dpkg-buildpackage wipes out my build tree
everytime it runs).
Thanks in advance for any help.
With best regards
Michael Meding
[EMAIL PROTECTED] wrote:
>I have been trying to build a debian package out of plain sources using
>deb-make
deb-make is largely obsolete. Use dh_make instead (from the dh-make
package).
>and dpkg-buildpackage. I need to pass an argument to configure
>(--with-qt2) but I don't
I have been trying to build a debian package out of plain sources using
deb-make and dpkg-buildpackage. I need to pass an argument to configure
(--with-qt2) but I don't know how to do it from dpkg-buildpackage. I know I
can edit configure.in and set it there, but I don't think that&#x
On 10 Jan 00 17:33:06 GMT, Fredrik Liljegren wrote:
>I would like dpkg-buildpackage to use egcs' optimizations for Pentium II,
>and let the whole system understand that it is a "i686" and not i386 to get
>proper defaults...
>
>I grep'd i386 in /etc and found th
I would like dpkg-buildpackage to use egcs' optimizations for Pentium II,
and let the whole system understand that it is a "i686" and not i386 to get
proper defaults...
I grep'd i386 in /etc and found that it's mentioned in quite a lot of
locations. Is there any standar
gt;
> dpkg-source -x packagename.dsc
> cd packagename.dsc
> debian/rules build
> debian/rules binary
>
> cd ..
> dpkg -i packagename.deb
>
Ummm, what's wrong with
dpkg-source -x packagename.dsc
cd packagename
dpkg-buildpackage
cd ..
dpkg -i packagename.deb
I think you don
Hi,
From /usr/doc/kernel-package/Problems.gz (not that one would
think of looking there, but this has been seen while building
kernels)
g) dpkg-gencontrol fails if LC_ALL is set to de_DE. Actually, I can't
really confirm this works for anything except en_US. This is true as of
Hi!
I've got a problem with building Packages with dpkg-builpackage. I
thought it should be possible to rebuild Packages from their sources who
were extracted from *.orig.tar.gz with dpkg-source -x. But instead
dpkg returned
vampira:[xldlas-0.85] # dpkg-buildpackage -us -uc
no utmp
63 matches
Mail list logo
