Michael Meskes wrote:
:
: 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). :-)
yea, it was a typo -- I meant 1.4.0.1 :-)
: Anyway, there's another nasty problem with dpkg-
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 (/
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
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 $rootcomman
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-- roo
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 .*//; }
> substr
On Thu, 19 Sep 1996, Heiko Schlittermann wrote:
> : If you figure out what's going on here can you let me know? I've run
> : into the same problem while rebuilding for m68kers and was unable to
> : determine the cause.
>
> Until Ian is back, you'll might use my diff as appended
> Heiko
Coo
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 `-rw-r
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-
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, givin
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 terr
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 wi
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-
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
dpkg
14 matches
Mail list logo
