On Wed, Oct 28, 2015 at 09:06:10PM -0000, Dx wrote:
> There's this pending pull request, which i have no idea what to do with:
> https://github.com/bitlbee/bitlbee/pull/43
>
> It changes the format from "1.0" to "3.0 (quilt)" and by doing so it
> breaks the build (it's got a red X from the travis-ci build).
>
> Specifically, dpkg-buildpackage throws:
>
> >dpkg-source: error: can't build with source format '3.0 (quilt)': no
> upstream tarball found at ../bitlbee_3.4.1.orig.tar.{bz2,gz,lzma,xz}
>
> I don't know enough about deb packaging to fix it so i left it on hold.
> Some help would definitely be welcome.
You need to have an upstream tarball (named e.g. bitlbee_3.4.1.orig.tar.gz)
available in the parent directory.
The 1.0 format falls back to a "native" package if it can't find the upstream
tarball, which is probably not what you want.
On Wed, Oct 28, 2015 at 09:06:10PM -0000, Dx wrote: /github. com/bitlbee/ bitlbee/ pull/43 3.4.1.orig. tar.{bz2, gz,lzma, xz}
> There's this pending pull request, which i have no idea what to do with:
> https:/
>
> It changes the format from "1.0" to "3.0 (quilt)" and by doing so it
> breaks the build (it's got a red X from the travis-ci build).
>
> Specifically, dpkg-buildpackage throws:
>
> >dpkg-source: error: can't build with source format '3.0 (quilt)': no
> upstream tarball found at ../bitlbee_
>
> I don't know enough about deb packaging to fix it so i left it on hold.
> Some help would definitely be welcome.
You need to have an upstream tarball (named e.g. bitlbee_ 3.4.1.orig. tar.gz)
available in the parent directory.
The 1.0 format falls back to a "native" package if it can't find the upstream
tarball, which is probably not what you want.
Cheers,
Jelmer