--- Brian Dessent ha scritto:
The setup.exe source (install.cc,
Installer::installOne) looks like it
expects an error peeking from try_decompress in
this situation, but
running in the debugger shows
try_decompress-peek() successfully
reading '0'. Note that if you bunzip2 the empty
On Mon, May 05, 2008 at 08:13:58PM -0600, Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Brian Dessent on 5/5/2008 3:11 PM:
| I have an empty meta-package to pull in other packages copied from one
| of the _obsolete packages. I understand these are created via
Christopher Faylor wrote:
Yes, I'm confused by this. I did replace all of the zero length tar files
with the 46 byte versions. That's what I've always done when creating an
empty package.
Here is a summary of the situation:
The current stable/release version of setup will never warn if it
Thrall, Bryan wrote:
I've built setup.exe from source (updated today), and the ChangeLog says
Brian Dessent fixed the Invalid or unsupported tar format problem with
empty tar.bz2 files, but I am still seeing the error popup.
I have an empty meta-package to pull in other packages copied from
Brian Dessent wrote on Monday, May 05, 2008 4:12 PM:
And again, to recap: the reason for generating an error instead of
silently moving on in this situation was to diagnose the case where
the maintainer used a strange tar implementation to create a package
-- without the error the package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Brian Dessent on 5/5/2008 3:11 PM:
| I have an empty meta-package to pull in other packages copied from one
| of the _obsolete packages. I understand these are created via 'tar -T
| /dev/null -cjf foo.tar.bz2' (see
|
