Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #172334 > unrolled thread

Problem with dpkg-source -b outside current working dir

Back to article view | Back to linux.debian.user

Contents

  Problem with dpkg-source -b outside current working dir Malte Forkel <malte.forkel@berlin.de> - 2016-09-17 10:40 +0200
    Re: Problem with dpkg-source -b outside current working dir kamaraju kusumanchi <raju.mailinglists@gmail.com> - 2016-09-20 07:40 +0200
      Re: Problem with dpkg-source -b outside current working dir Malte Forkel <malte.forkel@berlin.de> - 2016-09-20 13:50 +0200
        Re: Problem with dpkg-source -b outside current working dir Lisi Reisz <lisi.reisz@gmail.com> - 2016-09-20 17:20 +0200
        Re: Problem with dpkg-source -b outside current working dir kamaraju kusumanchi <raju.mailinglists@gmail.com> - 2016-09-21 06:10 +0200
          Re: Problem with dpkg-source -b outside current working dir Malte Forkel <malte.forkel@berlin.de> - 2016-09-21 11:30 +0200
            Re: Problem with dpkg-source -b outside current working dir kamaraju kusumanchi <raju.mailinglists@gmail.com> - 2016-09-28 04:50 +0200

#172334 — Problem with dpkg-source -b outside current working dir

Hi,

according to the man page, dpkg-source -b takes an argument that is "the
 name  of the directory containing the debianized source tree". But that
does not work for me if the directory is not the current working directory.

When is execute dpkg-source in the package's source directory, i.e.
   SRCDIR$ dpkg-source -b .
everything works fine. But if I execute dpkg-source from a different
directory with the absolute path as its argument
   /tmp$ dpkg-source -b $SRCDIR
it complains that can't find the original tarball at
../pkg_vers.orig.tar.*. Shouldn't it look into $SRCDIR/..?

Im using dpkg-source from dpkg-dev 1.18.4ubuntu1.1 in Ubuntu 16.04.

Thanks, Malte

[toc] | [next] | [standalone]

#172519

On Sat, Sep 17, 2016 at 4:33 AM, Malte Forkel <malte.forkel@berlin.de> wrote:
> Hi,
>
> according to the man page, dpkg-source -b takes an argument that is "the
>  name  of the directory containing the debianized source tree". But that
> does not work for me if the directory is not the current working directory.
>
> When is execute dpkg-source in the package's source directory, i.e.
>    SRCDIR$ dpkg-source -b .
> everything works fine. But if I execute dpkg-source from a different
> directory with the absolute path as its argument
>    /tmp$ dpkg-source -b $SRCDIR
> it complains that can't find the original tarball at
> ../pkg_vers.orig.tar.*. Shouldn't it look into $SRCDIR/..?
>

Is the $SRCDIR variable set to anything? What is the output of

echo $SRCDIR

> Im using dpkg-source from dpkg-dev 1.18.4ubuntu1.1 in Ubuntu 16.04.

As explained in the FAQ
(https://www.debian.org/doc/manuals/debian-faq/ch-choosing.en.html#s3.2),
Ubuntu is based on Debian but not Debian. If you are running Ubutnu,
it is better to ask on Ubuntu list than here.

thanks
raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

[toc] | [prev] | [next] | [standalone]

#172526

Am 20.09.2016 um 07:33 schrieb kamaraju kusumanchi:
> On Sat, Sep 17, 2016 at 4:33 AM, Malte Forkel <malte.forkel@berlin.de>
wrote:
>> Hi,
>>
>> according to the man page, dpkg-source -b takes an argument that is "the
>>  name  of the directory containing the debianized source tree". But that
>> does not work for me if the directory is not the current working
directory.
>>
>> When is execute dpkg-source in the package's source directory, i.e.
>>    SRCDIR$ dpkg-source -b .
>> everything works fine. But if I execute dpkg-source from a different
>> directory with the absolute path as its argument
>>    /tmp$ dpkg-source -b $SRCDIR
>> it complains that can't find the original tarball at
>> ../pkg_vers.orig.tar.*. Shouldn't it look into $SRCDIR/..?
>>
>
> Is the $SRCDIR variable set to anything? What is the output of
>
> echo $SRCDIR
>
Sorry for the confusion. I just used SRCDIR as a placeholder for the
real directory name in my example. And I should have written SRCDIR
(instead of $SRCDIR) in the second part to make that clear.

>> Im using dpkg-source from dpkg-dev 1.18.4ubuntu1.1 in Ubuntu 16.04.
>
> As explained in the FAQ
> (https://www.debian.org/doc/manuals/debian-faq/ch-choosing.en.html#s3.2),
> Ubuntu is based on Debian but not Debian. If you are running Ubutnu,
> it is better to ask on Ubuntu list than here.
>
True. But I don't think there should be a difference in the
implementation of dpkg-source

[toc] | [prev] | [next] | [standalone]

#172533

On Tuesday 20 September 2016 12:39:50 Malte Forkel wrote:
> Am 20.09.2016 um 07:33 schrieb kamaraju kusumanchi:
> > On Sat, Sep 17, 2016 at 4:33 AM, Malte Forkel <malte.forkel@berlin.de>
>
> wrote:
> >> Hi,
> >>
> >> according to the man page, dpkg-source -b takes an argument that is "the
> >>  name  of the directory containing the debianized source tree". But that
> >> does not work for me if the directory is not the current working
>
> directory.
>
> >> When is execute dpkg-source in the package's source directory, i.e.
> >>    SRCDIR$ dpkg-source -b .
> >> everything works fine. But if I execute dpkg-source from a different
> >> directory with the absolute path as its argument
> >>    /tmp$ dpkg-source -b $SRCDIR
> >> it complains that can't find the original tarball at
> >> ../pkg_vers.orig.tar.*. Shouldn't it look into $SRCDIR/..?
> >
> > Is the $SRCDIR variable set to anything? What is the output of
> >
> > echo $SRCDIR
>
> Sorry for the confusion. I just used SRCDIR as a placeholder for the
> real directory name in my example. And I should have written SRCDIR
> (instead of $SRCDIR) in the second part to make that clear.
>
> >> Im using dpkg-source from dpkg-dev 1.18.4ubuntu1.1 in Ubuntu 16.04.
> >
> > As explained in the FAQ
> > (https://www.debian.org/doc/manuals/debian-faq/ch-choosing.en.html#s3.2),
> > Ubuntu is based on Debian but not Debian. If you are running Ubutnu,
> > it is better to ask on Ubuntu list than here.
>
> True. But I don't think there should be a difference in the
> implementation of dpkg-source

There only has to be a minor tweak and it would/could make a difference.  If 
you do not acknowledge this possibility, why tell us which version you are 
using??

Lisi

[toc] | [prev] | [next] | [standalone]

#172557

On Tue, Sep 20, 2016 at 7:39 AM, Malte Forkel <malte.forkel@berlin.de> wrote:
> Am 20.09.2016 um 07:33 schrieb kamaraju kusumanchi:
>> On Sat, Sep 17, 2016 at 4:33 AM, Malte Forkel <malte.forkel@berlin.de>
> wrote:
>>> Hi,
>>>
>>> according to the man page, dpkg-source -b takes an argument that is "the
>>>  name  of the directory containing the debianized source tree". But that
>>> does not work for me if the directory is not the current working
> directory.
>>>
>>> When is execute dpkg-source in the package's source directory, i.e.
>>>    SRCDIR$ dpkg-source -b .
>>> everything works fine. But if I execute dpkg-source from a different
>>> directory with the absolute path as its argument
>>>    /tmp$ dpkg-source -b $SRCDIR
>>> it complains that can't find the original tarball at
>>> ../pkg_vers.orig.tar.*. Shouldn't it look into $SRCDIR/..?
>>>
>>
>> Is the $SRCDIR variable set to anything? What is the output of
>>
>> echo $SRCDIR
>>
> Sorry for the confusion. I just used SRCDIR as a placeholder for the
> real directory name in my example. And I should have written SRCDIR
> (instead of $SRCDIR) in the second part to make that clear.
>

It seems to be working fine for me

// Create two empty directories and download source into one of them
rajulocal@hogwarts ~/x % mkdir x1 x2
rajulocal@hogwarts ~/x % cd x1
rajulocal@hogwarts ~/x/x1 % apt-get source python-popcon
Reading package lists... Done
Building dependency tree
Reading state information... Done
NOTICE: 'python-popcon' packaging is maintained in the 'Git' version
control system at:
git://github.com/venthur/python-popcon.git
Need to get 5,429 B of source archives.
Get:1 http://httpredir.debian.org/debian/ jessie/main python-popcon
1.1 (dsc) [1,489 B]
Get:2 http://httpredir.debian.org/debian/ jessie/main python-popcon
1.1 (tar) [3,940 B]
Fetched 5,429 B in 0s (15.2 kB/s)
dpkg-source: info: extracting python-popcon in python-popcon-1.1
dpkg-source: info: unpacking python-popcon_1.1.tar.gz
rajulocal@hogwarts ~/x/x1 % ls
python-popcon-1.1/  python-popcon_1.1.dsc  python-popcon_1.1.tar.gz

// Now to go the other directory and run dpkg-source based on the
previously unpacked source.
rajulocal@hogwarts ~/x/x1 % cd ../x2
rajulocal@hogwarts ~/x/x2 % dpkg-source -b
dpkg-source: --build needs a directory

Use --help for program usage information.
rajulocal@hogwarts ~/x/x2 % dpkg-source -b ../x1/python-popcon-1.1
dpkg-source: info: using source format `3.0 (native)'
dpkg-source: info: building python-popcon in python-popcon_1.1.tar.xz
dpkg-source: info: building python-popcon in python-popcon_1.1.dsc
rajulocal@hogwarts ~/x/x2 % ls
python-popcon_1.1.dsc  python-popcon_1.1.tar.xz


>From the man page of dpkg-source, I see that this option was added in
dpkg 1.17.14. Could you please tell which version you are using? In my
case it is

% dpkg --version
Debian `dpkg' package management program version 1.17.27 (amd64).
This is free software; see the GNU General Public License version 2 or
later for copying conditions. There is NO warranty.

thanks
raju

[toc] | [prev] | [next] | [standalone]

#172564

Am 21.09.2016 um 06:04 schrieb kamaraju kusumanchi:
> On Tue, Sep 20, 2016 at 7:39 AM, Malte Forkel <malte.forkel@berlin.de> wrote:
>> Am 20.09.2016 um 07:33 schrieb kamaraju kusumanchi:
>>> On Sat, Sep 17, 2016 at 4:33 AM, Malte Forkel <malte.forkel@berlin.de>
>> wrote:
>>>> Hi,
>>>>
>>>> according to the man page, dpkg-source -b takes an argument that is "the
>>>>  name  of the directory containing the debianized source tree". But that
>>>> does not work for me if the directory is not the current working
>> directory.
>>>>
>>>> When is execute dpkg-source in the package's source directory, i.e.
>>>>    SRCDIR$ dpkg-source -b .
>>>> everything works fine. But if I execute dpkg-source from a different
>>>> directory with the absolute path as its argument
>>>>    /tmp$ dpkg-source -b $SRCDIR
>>>> it complains that can't find the original tarball at
>>>> ../pkg_vers.orig.tar.*. Shouldn't it look into $SRCDIR/..?
>>>>
>>>
>>> Is the $SRCDIR variable set to anything? What is the output of
>>>
>>> echo $SRCDIR
>>>
>> Sorry for the confusion. I just used SRCDIR as a placeholder for the
>> real directory name in my example. And I should have written SRCDIR
>> (instead of $SRCDIR) in the second part to make that clear.
>>
> 
> It seems to be working fine for me
> 
> // Create two empty directories and download source into one of them
> rajulocal@hogwarts ~/x % mkdir x1 x2
> rajulocal@hogwarts ~/x % cd x1
> rajulocal@hogwarts ~/x/x1 % apt-get source python-popcon
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> NOTICE: 'python-popcon' packaging is maintained in the 'Git' version
> control system at:
> git://github.com/venthur/python-popcon.git
> Need to get 5,429 B of source archives.
> Get:1 http://httpredir.debian.org/debian/ jessie/main python-popcon
> 1.1 (dsc) [1,489 B]
> Get:2 http://httpredir.debian.org/debian/ jessie/main python-popcon
> 1.1 (tar) [3,940 B]
> Fetched 5,429 B in 0s (15.2 kB/s)
> dpkg-source: info: extracting python-popcon in python-popcon-1.1
> dpkg-source: info: unpacking python-popcon_1.1.tar.gz
> rajulocal@hogwarts ~/x/x1 % ls
> python-popcon-1.1/  python-popcon_1.1.dsc  python-popcon_1.1.tar.gz
> 
> // Now to go the other directory and run dpkg-source based on the
> previously unpacked source.
> rajulocal@hogwarts ~/x/x1 % cd ../x2
> rajulocal@hogwarts ~/x/x2 % dpkg-source -b
> dpkg-source: --build needs a directory
> 
> Use --help for program usage information.
> rajulocal@hogwarts ~/x/x2 % dpkg-source -b ../x1/python-popcon-1.1
> dpkg-source: info: using source format `3.0 (native)'
> dpkg-source: info: building python-popcon in python-popcon_1.1.tar.xz
> dpkg-source: info: building python-popcon in python-popcon_1.1.dsc
> rajulocal@hogwarts ~/x/x2 % ls
> python-popcon_1.1.dsc  python-popcon_1.1.tar.xz
> 
Your example works for me too. But you are using a native package, so
there is no original archive in the parent directory that dpkg-source
would have to access. May be you could try another package, e.g. fuse,
which is not a native package?

malte@ubuntu64_vb:~/x2$ dpkg-source -b ../x1/fuse-2.9.4/
pkg-source: info: using options from
../x1/fuse-2.9.4/debian/source/options: --compression=xz
dpkg-source: error: can't build with source format '3.0 (quilt)': no
upstream tarball found at ../fuse_2.9.4.orig.tar.{bz2,gz,lzma,xz}

> 
>>From the man page of dpkg-source, I see that this option was added in
> dpkg 1.17.14. Could you please tell which version you are using? In my
> case it is
> 
> % dpkg --version
> Debian `dpkg' package management program version 1.17.27 (amd64).
> This is free software; see the GNU General Public License version 2 or
> later for copying conditions. There is NO warranty.
> 
My version of dpkg is 1.18.4ubuntu1

Thanks, Malte

[toc] | [prev] | [next] | [standalone]

#172880

On Wed, Sep 21, 2016 at 5:21 AM, Malte Forkel <malte.forkel@berlin.de> wrote:
> Your example works for me too. But you are using a native package, so
> there is no original archive in the parent directory that dpkg-source
> would have to access. May be you could try another package, e.g. fuse,
> which is not a native package?
>
> malte@ubuntu64_vb:~/x2$ dpkg-source -b ../x1/fuse-2.9.4/
> pkg-source: info: using options from
> ../x1/fuse-2.9.4/debian/source/options: --compression=xz
> dpkg-source: error: can't build with source format '3.0 (quilt)': no
> upstream tarball found at ../fuse_2.9.4.orig.tar.{bz2,gz,lzma,xz}
>

I get the same error when I try it on fuse. I am not an expert on
dpkg-source but it looks like a bug to me.

thanks
raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web