Your message dated Sat, 2 Mar 2019 13:27:40 +0100
with message-id <[email protected]>
and subject line Re: Bug#247035: /usr/bin/dpkg-deb: [DPKG-DEB] fails to -I
files >2GB
has caused the Debian Bug report #247035,
regarding dpkg-deb: Fails to -I files when control.tar.gz > 2GiB
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
247035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=247035
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.10.21
Severity: normal
File: /usr/bin/dpkg-deb
dpkg-deb fails when attempting to -I a file that is >2GB in size. The
following is taken from dpkg-scanpackages:
$ dpkg-deb -I bigfile_1.0_all.deb control
tar: Read 7662 bytes from -
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
dpkg-deb: subprocess tar returned error exit status 2
This is on a 32-bit x86 platform, I don't have a 64bit platform to test
with. The file size in question is 4,768,504,298 bytes.
dpkg-buildpackage generated it and dpkg -i works.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.23-pre4
Locale: LANG=C, LC_CTYPE=C
Versions of packages dpkg depends on:
ii dselect 1.10.20 a user tool to manage Debian packa
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi!
On Sun, 2004-05-02 at 18:40:16 -0400, Christopher W. Curtis wrote:
> Package: dpkg
> Version: 1.10.21
> Severity: normal
> File: /usr/bin/dpkg-deb
> dpkg-deb fails when attempting to -I a file that is >2GB in size. The
> following is taken from dpkg-scanpackages:
>
> $ dpkg-deb -I bigfile_1.0_all.deb control
> tar: Read 7662 bytes from -
> tar: Unexpected EOF in archive
> tar: Unexpected EOF in archive
> tar: Error is not recoverable: exiting now
> dpkg-deb: subprocess tar returned error exit status 2
>
> This is on a 32-bit x86 platform, I don't have a 64bit platform to test
> with. The file size in question is 4,768,504,298 bytes.
> dpkg-buildpackage generated it and dpkg -i works.
I think those error above were problems in tar(1) itself, not having
large file support back then. dpkg-deb just extracts this into a
directory and then feeds the specified file in chunks to stdout. So
I'd consider this a non-issue nowadays.
On Mon, 2004-05-03 at 10:37:02 -0400, Christopher W. Curtis wrote:
> A followup to my previous message: I had changed something somewhere in
> my build environment and started generating corrupt packages. I had
> been putting the files in the DEBIAN/ subdirectory. This bug is
> either invalid or can be easily have it's priority dropped (unless it is
> someone's intention to generate >2GB control sections).
If you are feeding this kind of sizes into dpkg, and th text junk is
part of the control paragraph, then this will end up in the status
database, and being part of each database load, and in memory, so you
might have a hard time proceeding anyway. But if've got the memory it
should be fine. :)
Closing now as a problem in an unrelated part of the system, which
should be fixed now.
Thanks,
Guillem
--- End Message ---
