On Tue, Jun 27, 2006 at 01:09:40PM +0200, Jeroen van Wolffelaar wrote:
On Tue, Jun 27, 2006 at 09:07:03AM +0100, Roger Leigh wrote:
It sounds like a bug that dpkg is using the old v7 tar format which
had that 99 char limitation.s
tar has a fixed-length field for short (upto 100 bytes)
On Tue, 2006-06-27 at 13:09 +0200, Jeroen van Wolffelaar wrote:
But on the other hand, according to the 'be strict in what you send,
liberal in what you accept' mantra, it makes sense for tar to not create
tarfiles which in the past have caused issues for certain programs while
there's a
Russ Allbery [EMAIL PROTECTED] writes:
I just built new xml-security-c packages to fix the current FTBFS bug, and
lintian returned the following error message:
E: libxml-security-c-doc: deb-created-with-broken-tar file:
On Tuesday 27 June 2006 11:07, Roger Leigh wrote:
--cut--
(along with several other files). These filenames are indeed exactly 100
characters long, as mentioned in the referenced bug. The bug, however,
indicates that this may not have really been a bug in tar but rather was
a bug in dpkg
On Tue, Jun 27, 2006 at 09:07:03AM +0100, Roger Leigh wrote:
Russ Allbery [EMAIL PROTECTED] writes:
I just built new xml-security-c packages to fix the current FTBFS bug, and
lintian returned the following error message:
E: libxml-security-c-doc: deb-created-with-broken-tar file:
I just built new xml-security-c packages to fix the current FTBFS bug, and
lintian returned the following error message:
E: libxml-security-c-doc: deb-created-with-broken-tar file:
/usr/share/doc/libxml-security-c-doc/c/apiDocs/winutils_2XSECBinHTTPURIInputStream_8hpp-source.html
N:
N: The
6 matches
Mail list logo
