Re: Determining native or non-native package inside pbuilder

2008-09-07 Thread Ben Finney
"Daniel Moerner" <[EMAIL PROTECTED]> writes: > Actually, most of the vcs-based package builders look in ../tarballs. > Git-buildpackage looks there if pristine-tar is not being used to > manage building, as does bzr-builddeb. Indeed, I mostly use the '${VCS}-buildpackage' commands, which is why I

Re: Determining native or non-native package inside pbuilder

2008-09-07 Thread Daniel Moerner
> dpkg-buildpackage expects it to be in ../foo_*. svn-buildpackage is the only > one > that uses ../tarballs AFAIK. > Actually, most of the vcs-based package builders look in ../tarballs. Git-buildpackage looks there if pristine-tar is not being used to manage building, as does bzr-builddeb. How

Re: Determining native or non-native package inside pbuilder

2008-09-07 Thread Felipe Sateler
Ben Finney wrote: > "Paul Wise" <[EMAIL PROTECTED]> writes: > >> On Sun, Sep 7, 2008 at 3:33 PM, Ben Finney <[EMAIL PROTECTED]> >> wrote: >> > "Paul Wise" <[EMAIL PROTECTED]> writes: >> > >> >> Usually this warning is produced because of an incorrectly named >> >> orig.tar.gz - foo-1.2.orig.tar.g

Re: Determining native or non-native package inside pbuilder

2008-09-07 Thread Paul Wise
On Sun, Sep 7, 2008 at 7:27 PM, Ben Finney <[EMAIL PROTECTED]> wrote: > Should I expect it to be found at '../tarballs/foo_1.2.3.orig.tar.gz'? > That's where 'dpkg-buildpackage' and other tools seem to expect it. > > Is 'pbuilder' different in this regard? I'd rather not have the same > file needi

Re: Determining native or non-native package inside pbuilder

2008-09-07 Thread Ben Finney
"Paul Wise" <[EMAIL PROTECTED]> writes: > On Sun, Sep 7, 2008 at 3:33 PM, Ben Finney <[EMAIL PROTECTED]> wrote: > > "Paul Wise" <[EMAIL PROTECTED]> writes: > > > >> Usually this warning is produced because of an incorrectly named > >> orig.tar.gz - foo-1.2.orig.tar.gz (bad) vs foo_1.2.orig.tar.gz

Re: Determining native or non-native package inside pbuilder

2008-09-07 Thread Paul Wise
On Sun, Sep 7, 2008 at 3:33 PM, Ben Finney <[EMAIL PROTECTED]> wrote: > "Paul Wise" <[EMAIL PROTECTED]> writes: > >> Usually this warning is produced because of an incorrectly named >> orig.tar.gz - foo-1.2.orig.tar.gz (bad) vs foo_1.2.orig.tar.gz (good). >> Perhaps that is the issue? > > Perhaps.

Re: Determining native or non-native package inside pbuilder

2008-09-07 Thread Ben Finney
"Paul Wise" <[EMAIL PROTECTED]> writes: > Usually this warning is produced because of an incorrectly named > orig.tar.gz - foo-1.2.orig.tar.gz (bad) vs foo_1.2.orig.tar.gz (good). > Perhaps that is the issue? Perhaps. But as far as I know, I have no control over the name of the tarball; it's gene

Re: Determining native or non-native package inside pbuilder

2008-09-07 Thread Paul Wise
Usually this warning is produced because of an incorrectly named orig.tar.gz - foo-1.2.orig.tar.gz (bad) vs foo_1.2.orig.tar.gz (good). Perhaps that is the issue? -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Troubl

Determining native or non-native package inside pbuilder

2008-09-06 Thread Ben Finney
Howdy all, I'm using a 'pbuilder' hook to run 'lintian' over the generated package: = B91_lintian = #! /bin/sh # Run lintian on the generated package echo "I: installing lintian and running it on the package" apt-get install -y --force-yes lintian &>/dev/null lintian --allow-root --color