Bug#159877: marked as done (apt-ftparchive needs to support bzip2 and stored data.tar compression types)
Your message dated Fri, 14 May 2010 17:42:43 +0200
with message-id <AANLkTimIwSWi6LL_LQJxC1K5FDqbFStg8HLavHsERI7Z@mail.gmail.com>
and subject line Close: apt-ftparchive needs to support bzip2 and stored data.tar compression types
has caused the Debian Bug report #159877,
regarding apt-ftparchive needs to support bzip2 and stored data.tar compression types
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 owner@bugs.debian.org
immediately.)
--
159877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=159877
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: <submit@bugs.debian.org>
- Subject: apt-ftparchive needs to support bzip2 and stored data.tar compression types
- From: Adam Heath <doogie@brainfood.com>
- Date: Fri, 6 Sep 2002 13:22:45 -0500 (CDT)
- Message-id: <Pine.LNX.4.33.0209061316030.6356-100000@gradall.private.brainfood.com>
Package: apt-utils
Severity: wishlist
I have recently added support to dpkg-dev 1.11, for configuable compression
types of the data member in debs. I encode the type in the deb by way of
changing the extension of the filename.
The types I support are gzip(default), bzip2, and stored. Their extensions
are .gz, .bz2, and nothing(ie, data.tar).
There is code in dpkg HEAD that can link to libz and libbz2 statically or
dynamically, or call external gzip/bzip2 binaries. apt-ftparchive should
probably do something similiar.
--- End Message ---
--- Begin Message ---
It turns out source format v3 has reached real world
in the last months and as far as i can see apt-ftparchive
hasn't exploded so far. ;)
I have therefore the strong feeling that the feature requested
here was implemented some (long ago) time before now -
as a result i am closing this bug now but feel free to reopen it
if you disagree.
Best regards,
David Kalnischkies
--- End Message ---
Reply to: