Build a package using format 3.0 (quilt)
Allison Randal
allison at lohutok.net
Sat Feb 25 00:33:41 UTC 2012
Hi Víctor,
The directory layout you have there should be fine. Change the name of
the tarball to guallet_0.1.10.orig.tar.gz. (Note that the dash "-"
changes to an underscore "_", and add ".orig" before ".tar.gz".
Allison
On 02/24/2012 04:17 PM, Víctor Fernández wrote:
> Using your bzr branch, I get the same error.
> My "goal" is build a .deb package with sources. For get this, I try to
> execute dpkg-buildpackage, but as the format is 3.0 (quilt) it asks me
> for a source tarball.
> My problem (by now) is build the source tarball, and try to guess how
> dpkg-buildpackage (or dh) wants it for understand it (the package
> source) and build with it the .deb.
> By now, if i'm using python, the most oviously way to get the source is
> using distutils, because generates a .tar.gz with sources. Ok, I get a
> guallet-0.1.10.tar.gz file, using python setup.py sdist. Now I copy it,
> where?, At parent folder?. By now, build a source tarball (in .tar.gz)
> is not a problem for me, because it doesn't throws any error. The
> problem comes when I try the dpkg-buildpackage command.
>
> Error message trow by dpkg-buildpackage:
> dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor):
> -g -O2
> dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor):
> dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin:
> vendor): -g -O2
> dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor):
> -g -O2
> dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor):
> -Wl,-Bsymbolic-functions
> dpkg-buildpackage: source package guallet
> dpkg-buildpackage: source version 0.1.10-0extras11.10.1~ppa1
> dpkg-buildpackage: source changed by Allison Randal <allison at lohutok.net
> <mailto:allison at lohutok.net>>
> dpkg-buildpackage: host architecture i386
> dpkg-source --before-build extras-guallet
> dpkg-checkbuilddeps: warning: can't parse dependency libobasis35-en_us
> dpkg-checkbuilddeps: warning: can't parse dependency libobasis35-en_us-calc
> dpkg-checkbuilddeps: warning: can't parse dependency libobasis35-en_us-res
> dpkg-checkbuilddeps: warning: can't parse dependency
> libobasis35-en_us-writer
> dpkg-checkbuilddeps: warning: can't parse dependency libobasis35-en_us-math
> dpkg-checkbuilddeps: warning: can't parse dependency libobasis35-en_us-base
> fakeroot debian/rules clean
> dh clean --with python2
> dh_testdir
> dh_auto_clean
> running clean
> 'build/lib.linux-i686-2.6' does not exist -- can't clean it
> 'build/bdist.linux-i686' does not exist -- can't clean it
> 'build/scripts-2.6' does not exist -- can't clean it
> running clean
> 'build/lib.linux-i686-2.7' does not exist -- can't clean it
> 'build/bdist.linux-i686' does not exist -- can't clean it
> 'build/scripts-2.7' does not exist -- can't clean it
> dh_clean
> dpkg-source -b extras-guallet
> dpkg-source: error: can't build with source format '3.0 (quilt)': no
> orig.tar file found
> dpkg-buildpackage: error: dpkg-source -b extras-guallet gave error exit
> status 255
>
> As I can see on second line starting by the bottom, the source code
> can't found the orig.tar file. When that happened the file generated by
> distutils (using python setup.py sdist) was moved to parent folder of
> extras-guallet (as showns below, it would be projects)
> projects/
> myotherproject/
> extras-guallet/
> setup.py
> README
> MANIFEST
> bin/
> dist/
> guallet-0.1.10.tar.gz
> debian/
> ... ... ...
> guallet-0.1.10.tar.gz
>
> In short, how to use dpkg-buildpackage with a debian source in format
> 3.0(quilt)
>
> 2012/2/25 Allison Randal <allison at lohutok.net <mailto:allison at lohutok.net>>
>
> On 02/24/2012 12:12 PM, Víctor Fernández wrote:
> > Hello. I'm trying to build a .deb package. But I need to use the
> format
> > 3.0 (quilt) that requies an orig.tar file. The code is in python. I
> > tryed to do a python setup.py sdist, and copy outside main directory.
> > But when I try to build with dpkg-buildpackage, it trows an error
> > (dpkg-source -b; error 255)
>
> Hi Víctor,
>
> Did you apply the patches to MANIFEST and MANIFEST.in? These make sure
> that setup.py includes all the necessary files when it builds the
> tarball. It's two separate revisions, revision 21 and revision 31, but
> if you just pull the current versions of the two files from my branch,
> you'll get all the relevant changes:
>
> http://bazaar.launchpad.net/~allison/+junk/extras-guallet/view/head:/MANIFEST
> <http://bazaar.launchpad.net/%7Eallison/+junk/extras-guallet/view/head:/MANIFEST>
>
> http://bazaar.launchpad.net/~allison/+junk/extras-guallet/view/head:/MANIFEST.in
> <http://bazaar.launchpad.net/%7Eallison/+junk/extras-guallet/view/head:/MANIFEST.in>
>
>
> If that doesn't fix the problem, could you send the full command-line
> output, and steps to reproduce the error?
>
> Thanks,
> Allison
>
>
More information about the Ubuntu-app-devel
mailing list