' expects the command and all its arguments as a
shell expression whereas all the rest expect the command and its
arguments as separate arguments to themselves.
Please see the manpage for dpkg-buildpackage and make sure that it
implements what the manpage in 1.4.0 says:
-rgain-root-command
as separate arguments to themselves.
Hmmm.
: implements what the manpage in 1.4.0 says:
:-rgain-root-command
: When dpkg-buildpackage needs to execute part of the
...
: There are several solutions that wouldn't necessarily break anything:
:
: 3. Switch from using su to using
On Fri, 27 Sep 1996, Heiko Schlittermann wrote:
Ian Jackson wrote:
: Please REVERSE the change you made to make the default rootcommand be
: `eval'.
Yes, please do, dpkg-buildpackage 1.4.0.1 is *BROKEN* for me as I can
no longer use sudo to build my packages.
Just trying ... sudo can't cope
Package: dpkg-dev
Version: 1.4.0
1) dpkg-buildpackage is supposed to pass the v, m, and C flags to
dpkg-genchanges, but it doesn't.
The following patch corrects this:
--- dpkg-buildpackage~ Wed Sep 11 17:20:10 1996
+++ dpkg-buildpackage Sun Sep 22 01:38:03 1996
@@ -106,7 +106,7
Heiko Schlittermann writes:
Perhaps someone should release dpkg_1.4.1 ... If there are no
voluntaries, I'd do it.
But please name it 1.4.0.1 (as Ian proposed). :-)
Anyway, there's another nasty problem with dpkg-buildpackage, namely that is
doesn't quote the commands executed via $rootcommand
Heiko Schlittermann wrote:
Yes, dpkg-source bails out if tar reports hardlinks:
And if tar converts non ascii-characters in file names to octal representation.
This happens with the kbd package which has a file with a Unicode-encoded
name for demonstration purposes.
I have already reported this
Karl Sackett wrote:
:
: Package: dpkg-dev
: Version: 1.4.0
:
: The umask for my account is set to 077. Those portions of dpkg-buildpackage
: which run as root create files with protection set to 600 and owned by
: root.root. Because of this, the non-root portions of dpkg-buildpackage
: cannot
On Thu, 19 Sep 1996, Dale Scheetz wrote:
On Thu, 19 Sep 1996, Heiko Schlittermann wrote:
@@ -710,6 +710,7 @@
listed by tar as \`$_');
$fn= $filesinarchive[$efix++]; $mode= $1;
if ($mode =~ m/^l/) { $_ =~ s/ -\ .*//; }
+if (/ link to /) {
On Fri, 20 Sep 1996, Heiko Schlittermann wrote:
Hmm, should the root portions change the umask before creating any
files? (I think, it's no good idea.)
I also think it's a bad idea of dpkg to change the umask. His
debian/rules should fix the permissions of files it creates. This is a
-buildpackage, namely that is
: doesn't quote the commands executed via $rootcommand. Here's a patch:
:
: --- dpkg-buildpackage.old Fri Sep 20 11:25:32 1996
: +++ dpkg-buildpackage Fri Sep 20 11:25:08 1996
... I'll apply it.
Any other patches out there?
Heiko
--
email : [EMAIL PROTECTED
Dale Scheetz writes:
I am converting the joe package to the new source format and have run into
a strange problem. The first time I run dpkg-buildpackage the .orig tree
is tarred up ok. The second time I run it, it tries to use the tar.gz file
created in the previous run but fails, giving
On Thu, 19 Sep 1996, Michael Meskes wrote:
dpkg-source: error: tarfile `joe_2.8.orig.tar.gz' contains unexpected
object listed by tar as `-rw-r--r-- root/users0 Jan 22 22:45 1995
joe-2.8.orig/jmacsrc link to joe-2.8.orig/.jmacsrc', expected
`joe-2.8.orig/jmacsrc'
dpkg-source:
llucius wrote:
:
: On Wed, 18 Sep 1996, Dale Scheetz wrote:
: dpkg-source: building joe using existing joe_2.8.orig.tar.gz
: dpkg-source: building joe using existing joe_2.8.orig.tar.gz
: dpkg-source: error: tarfile `joe_2.8.orig.tar.gz' contains unexpected
: object listed by tar as
Package: dpkg-dev
Version: 1.4.0
The umask for my account is set to 077. Those portions of dpkg-buildpackage
which run as root create files with protection set to 600 and owned by
root.root. Because of this, the non-root portions of dpkg-buildpackage
cannot access the files debian/files
On Thu, 19 Sep 1996, Heiko Schlittermann wrote:
@@ -710,6 +710,7 @@
listed by tar as \`$_');
$fn= $filesinarchive[$efix++]; $mode= $1;
if ($mode =~ m/^l/) { $_ =~ s/ -\ .*//; }
+if (/ link to /) { $_ =~ s/ link to .*//; }
Michael Meskes wrote:
:
: dpkg-source -b joe-2.8
: dpkg-source: building joe using existing joe_2.8.orig.tar.gz
: dpkg-source: building joe using existing joe_2.8.orig.tar.gz
: dpkg-source: error: tarfile `joe_2.8.orig.tar.gz' contains unexpected
: object listed by tar as `-rw-r--r--
I am converting the joe package to the new source format and have run into
a strange problem. The first time I run dpkg-buildpackage the .orig tree
is tarred up ok. The second time I run it, it tries to use the tar.gz file
created in the previous run but fails, giving:
dpkg-source -b joe-2.8
On Wed, 18 Sep 1996, Dale Scheetz wrote:
dpkg-source -b joe-2.8
dpkg-source: building joe using existing joe_2.8.orig.tar.gz
dpkg-source: building joe using existing joe_2.8.orig.tar.gz
dpkg-source: error: tarfile `joe_2.8.orig.tar.gz' contains unexpected
object listed by tar as `-rw-r--r--
On Wed, 18 Sep 1996, Dale Scheetz wrote:
I am converting the joe package to the new source format and have run into
a strange problem.
What version of tar are you using? tar 1.11.11 is a beta that changes
tar's behavior in all sorts of terrible ways. GNU accidentally
released it and then
On Wed, 18 Sep 1996, Guy Maor wrote:
On Wed, 18 Sep 1996, Dale Scheetz wrote:
I am converting the joe package to the new source format and have run into
a strange problem.
What version of tar are you using? tar 1.11.11 is a beta that changes
tar's behavior in all sorts of terrible
Package: dpkg
Version: 1.3.14
When using dpkg-buildpackage with the -r option the command debian/rules
binary etc. should be quoted IMO. Otherwise using su -c as root command
results in debian/rules being called without an argument.
Michael
--
Michael Meskes
Package: dpkg
Version: 1.3.12
sfere:/home/ftp/pub/debian/binary/base$ dpkg-buildpackage -h
[...]
Usage: dpkg-buildpackage [options]
Options: -rgain-root-command
[...]
-si (default) src includes orig for rev. 0 or 1} genchanges
-sa uploaded src includes orig
Dale Scheetz writes (Re: dpkg-buildpackage and -source questions):
On Fri, 30 Aug 1996, Ian Jackson wrote:
If you get this message [deleted]
you should upgrade your cpio. [...]
This resolved the problem for me. At least at this point I can unpack
hello ok. Shouldn't dpkg have a depends
If you get this message:
dpkg-source: error: tarfile `./exmh_1.6.9.orig.tar.gz' contains object with
newline in its name
(exmh-1.6.9.orig/?exmh-1.6.9.orig/exmh.README?exmh-1.6.9.orig/COPYRIGHT?exmh-1.6.9.orig/e...(rest
of output deleted)
You should upgrade your cpio. Unfortunately the
On Fri, 30 Aug 1996, Ian Jackson wrote:
If you get this message:
dpkg-source: error: tarfile `./exmh_1.6.9.orig.tar.gz' contains object with
newline in its name
(exmh-1.6.9.orig/?exmh-1.6.9.orig/exmh.README?exmh-1.6.9.orig/COPYRIGHT?exmh-1.6.9.orig/e...(rest
of output deleted)
You
Karl Sackett writes (dpkg-buildpackage and -source questions):
Regarding the -r option for dpkg-buildpackage, are there any
examples of what's called for here? Is the gain-root-command
something each developer provides for himself, or is there a command
or shell somewhere that performs
Regarding the -r option for dpkg-buildpackage, are there any examples of what's
called for here? Is the gain-root-command something each developer provides
for himself, or is there a command or shell somewhere that performs this
function?
Invoked as root, dpkg-buildpackage works fine. But when
Peter Tobias asks me in private email:
...
BTW: I didn't have much time the last weeks (and I won't have much
time the next weeks) so I wasn't able to check if this new source
format will also work for packages like netstd (packages which contain
lots of sub packages each with its own original
Ian Jackson wrote:
BTW: I didn't have much time the last weeks (and I won't have much
time the next weeks) so I wasn't able to check if this new source
format will also work for packages like netstd (packages which contain
lots of sub packages each with its own original source. Do you
401 - 429 of 429 matches
Mail list logo