Raising severity
severity 291194 serious
tags 291194 lenny-ignore
thanks
I just ran into this bug when using a modified tar that defaults to
create posix archives:
<-- snip -->
# dpkg -i ddd_3.3.12~rc2-0.0.bunk_amd64.deb
(Reading database ... 193488 files and directories currently installed.)
Preparing to replace ddd 1:3.3.11-1 (using ddd_3.3.12~rc2-0.0.bunk_amd64.deb) ...
Unpacking replacement ddd ...
dpkg: error processing ddd_3.3.12~rc2-0.0.bunk_amd64.deb (--install):
corrupted filesystem tarfile - corrupted package archive
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Processing triggers for menu ...
Errors were encountered while processing:
ddd_3.3.12~rc2-0.0.bunk_amd64.deb
#
<-- snip -->
Quoting the info file of tar:
<-- snip -->
...
posix
...
This archive format will be the default format for future versions
of GNU `tar'.
...
<-- snip -->
If this change in tar happens before squeeze Debian will already not be
able to follow it due to this bug, since due to the nature of dpkg it
has to support such kind of changes one release before they happen.
If this change in tar e.g. happens in 2012 (which will according to past
experiences be between squeeze and squeeze+1) then dpkg in squeeze will
already have to support it. That's why this 4 years old bug really has
to be fixed for squeeze.
Changing the severity in a way that it's not a problem for lenny, but
has to be fixed for squeeze.
debian-release Cc'ed due to setting the lenny-ignore tag.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
Reply to: