On Wed, Sep 21, 2016 at 5:21 AM, Malte Forkel 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
Am 21.09.2016 um 06:04 schrieb kamaraju kusumanchi:
> On Tue, Sep 20, 2016 at 7:39 AM, Malte Forkel wrote:
>> Am 20.09.2016 um 07:33 schrieb kamaraju kusumanchi:
>>> On Sat, Sep 17, 2016 at 4:33 AM, Malte Forkel
>> wrote:
>>>> Hi,
>>>>
>>
On Tue, Sep 20, 2016 at 7:39 AM, Malte Forkel wrote:
> Am 20.09.2016 um 07:33 schrieb kamaraju kusumanchi:
>> On Sat, Sep 17, 2016 at 4:33 AM, Malte Forkel
> wrote:
>>> Hi,
>>>
>>> according to the man page, dpkg-source -b takes an argument that is "th
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
>
> wrote:
> >> Hi,
> >>
> >> according to the man page, dpkg-source -b takes an argument
Am 20.09.2016 um 07:33 schrieb kamaraju kusumanchi:
> On Sat, Sep 17, 2016 at 4:33 AM, Malte Forkel
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"
On Sat, Sep 17, 2016 at 4:33 AM, Malte Forkel 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 wo
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
Hi,
Micha Feigin wrote:
> Currently I am trying to build the diff for the source trio
> (orig.tar.gz/diff.gz/.dsc). The problem is that using the standard diff
> arguments diff -ruN doesn't work. dpkg-source -x returns an error for
> the diff line (the first one in the file)
io
> (orig.tar.gz/diff.gz/.dsc). The problem is that using the standard diff
> arguments diff -ruN doesn't work. dpkg-source -x returns an error for
> the diff line (the first one in the file) and for the file dates that
> diff adds.
> What are the arguments for diff to build a di
-ruN doesn't work. dpkg-source -x returns an error for
the diff line (the first one in the file) and for the file dates that
diff adds.
What are the arguments for diff to build a diff file that dpkg-source -x
accepts?
The lines that cause the problem (example for one of the file in the
I am trying to install the dpkg source on a redhat 9 system -- my
ultimate goal is to get alien working.
I am running into the following error during make:
It says no rule to make archtable needed by archtable.h .
Now archtable is actually there and archtable.h is not, so what is
going on or is
Hi,
I upgraded to Potato on 22/5/99 and am having trouble with dpkg-source.
icarus:~/dnlds/lilo# dpkg-source -x lilo_21-5.dsc
dpkg-source: extracting lilo in lilo-21 shell-init: could not get current
directory: getcwd: cannot access parent directories: No such file or directory
icarus:~/dnlds
I'm trying to recompile the glibc2 Debian package with pgcc, hopefully
to squeeze out a bit more performance.
I downloaded the *.orig.tar.gz, *.dsc, and *.diff.gz files needed,
then did a "dpkg-sourc -x glibc*.dsc" and everything unpacked okay.
Before I modified anything at all, I tried to do a "
Hi Remco, hi Ben,
you wrote on: 02 Feb 99 at 09:22 (received 02.02.99)
about : _Re: dpkg-source_
>>> It will upgrade the package.
>> Does apt not respect packages that have been "held"?
>It does, so that's indeed a way to enforce your own packages.
>Thanks for pointing that out :-)
Thank
Ben Collins wrote:
> > > I was wondering, what will happen, when I get another distribution and
> > > do e.g. an "apt-get dist-upgrade", will it then replace the
> > > bla-package with a newer version (if there is a newer version in the
> > > new distribution) or will it leave my customized package
On Tue, Feb 02, 1999 at 01:18:29AM +0100, Remco van de Meent wrote:
> Frederick Page wrote:
> > I was wondering, what will happen, when I get another distribution and do
> > e.g. an "apt-get dist-upgrade", will it then replace the bla-package with
> > a newer version (if there is a newer version in
Frederick Page wrote:
> I was wondering, what will happen, when I get another distribution and do
> e.g. an "apt-get dist-upgrade", will it then replace the bla-package with
> a newer version (if there is a newer version in the new distribution) or
> will it leave my customized package alone?
It w
Hi all,
I was wondering about the following. I login as root, then "cd /usr/src"
then "dpkg-source -x /mnt/cdrom/(...)/bla.dsc". I customize the source and/
or compiling-options and issue "cd bla" and "debian/rules binary" in order
to get a pac
On Fri, 4 Dec 1998, Daniel Elenius wrote:
> Is it possible when installing a debian package with:
>
> dpkg-source -x packagename.dsc
> , followed by ./configure, make, make install,
The correct method is:
dpkg-source -x packagename.dsc
cd packagename.dsc
debian/rules build
debian/
On Fri, 4 Dec 1998, Daniel Elenius wrote:
> Is it possible when installing a debian package with:
>
> dpkg-source -x packagename.dsc
> , followed by ./configure, make, make install,
>
> to get dpkg/dselect to understand that the package has been installed,
> so that I c
Is it possible when installing a debian package with:
dpkg-source -x packagename.dsc
, followed by ./configure, make, make install,
to get dpkg/dselect to understand that the package has been installed,
so that I can later uninstall it with dpkg/dselect?
On Tue, Sep 22, 1998 at 04:40:13PM -0700, [EMAIL PROTECTED] wrote:
> On Tue, 22 Sep 1998, Marcus Brinkmann wrote:
>
> > dpkg-source -x foo_version.dsc
> > cd foo_version
> > debian/rules binary or dpkg-buildpackage -b -us -uc
> >
> > Marcus
>
On Tue, 22 Sep 1998, Marcus Brinkmann wrote:
> dpkg-source -x foo_version.dsc
> cd foo_version
> debian/rules binary or dpkg-buildpackage -b -us -uc
>
> Marcus
Thanks - I appreciate it. :) The output of dpkg-buildpackage even showed
how to call aclocal to get
ng but the kitchen sink as
> far as the development environment goes. Any help is appreciated. :)
dpkg-source -x foo_version.dsc
cd foo_version
debian/rules binary or dpkg-buildpackage -b -us -uc
Marcus
--
"Rhubarb is no Egyptian god."Debian GNU/Linuxfing
Hi, any chance someone could tell me the correct incantations for
compiling dpkg from source? I've tried both the versions in hamm and
slink, but the INSTALL file is just a default gnu configure one, and
./configure (it's installation instructions) does nothing useful. I also
tried autoconf and
Try holding the key down while clicking the HREF link to d/l the
file. When the Save As dialog pops up add the .gz back on the end and
it does not touch the file. I do this kinda often.
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
that make me think some directory names should be changed, but,
> > after the change, no directory name is changed. What am I missing here ?
>
> No actually it is not. The correct way is to use dpkg-source. The
> command is 'dpkg-source -x .dsc'. This will recreate the
&
On Tue, 28 Apr 1998, Mario Filipe wrote:
> I need some packages that are in hamm, but i'm using bo. So i tried to use
> dpkg-source only problem is that it complains :
>
> dpkg-source: error: tarfile `./perl_5.004.04.orig.tar.gz' contains object
> (perl5.004_04/) not in
-BEGIN PGP SIGNED MESSAGE-
Hi
I need some packages that are in hamm, but i'm using bo. So i tried to use
dpkg-source only problem is that it complains :
dpkg-source: error: tarfile `./perl_5.004.04.orig.tar.gz' contains object
(perl5.004_04/) not in expected directory (per
Christian Lynbech <[EMAIL PROTECTED]> writes:
> I do not remember (or perhaps understand) whether it meant that no
> dpkg-source could unpack it or whether you had to use a specific
> version of dpkg-source.
(For the second time) Upgrade to dpkg-dev 1.4.0.19 *and* patch 2.2 or
be
There was a message (which I did not keep) saying that the problem was
not the patch problem but related to how the ppp-2.3.1 source was
packed (pristine sources).
I do not remember (or perhaps understand) whether it meant that no
dpkg-source could unpack it or whether you had to use a specific
Christian Lynbech writes:
> What all of this means is only that your version of `dpkg-source' must
> match your version of `patch'.
Which it does, and yet I still can't install the ppp-2.3.1 source.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, W
not `patch'.
Secondly, the problem with `patch' is only with the command line
arguments used to specify the backup file extension. A recent version
of `patch' changed that, and `dpkg-source' changed with it, but newer
version of `patch' has (should we say: by popular demand
Jim Pick writes:
> You need to upgrade your patch package to the one in unstable, I believe.
> The patch in unstable creates patch files that can't be read by the patch
> in stable.
What will happen then when I make patches for use on systems that don't have
this new version of patch?
gunzip ppp_
Jim Pick <[EMAIL PROTECTED]> writes:
> > dpkg-source: error: tarfile `./ppp_2.3.1.orig.tar.gz' contains
> > object (ppp-2.3.1/) not in expected directory (ppp-2.3.1.orig)
>
> You need to upgrade your patch package to the one in unstable, I
> believe.
You
ing the dpkg-source man page, issued
> the command:
>
> dpkg-source -x ppp_2.3.1-3.dsc
>
> and got this result:
>
> dpkg-source: error: tarfile `./ppp_2.3.1.orig.tar.gz' contains object
> (ppp-2.3.1/) not in expected directory (ppp-2.3.1.orig)
>
Having a desire to look at the ppp_2.3.1 sources, I went to unstable on
ftp.debian.org and got what I guessed were the appropriate files:
ppp_2.3.1-3.diff.gz, ppp_2.3.1-3.dsc, and ppp_2.3.1.orig.tar.gz. I stuck
these in a directory, and, after perusing the dpkg-source man page, issued
the
> 3 files in dir to install sources: *.diff.gz, *.orig.tar.gz and *.dsc
>
> dpkg-source -x fails with:
>
> "diff patches file whose dir does not appear in tarfile"
>
> I could comment some lines in *.dsc for the dir specified in the
> error message, but I d
3 files in dir to install sources: *.diff.gz, *.orig.tar.gz and *.dsc
dpkg-source -x fails with:
"diff patches file whose dir does not appear in tarfile"
I could comment some lines in *.dsc for the dir specified in the
error message, but I don't
understand the formats. How do
In article <[EMAIL PROTECTED]> Marc Fleureck wrote:
: Hi,
: I ran dpkg-source (dpkg-dev 1.4.0.8) on 3 files: *.diff.gz, *.dsc and
: *.orig.tar.gz, as you described in the readme (dpkg-source -x *.dsc).
:
: Its says:
:
: "Can't locate POSIX.pm in @INC at /usr/bin/dpkg-source li
Hi,
I ran dpkg-source (dpkg-dev 1.4.0.8) on 3 files: *.diff.gz, *.dsc and
*.orig.tar.gz, as you described in the readme (dpkg-source -x *.dsc).
Its says:
"Can't locate POSIX.pm in @INC at /usr/bin/dpkg-source line 8.
" BEGIN failed--compilation aborted at /usr/bin/dpkg-sou
41 matches
Mail list logo
