[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#399760: marked as done (ITP: paq -- high compression ratio archiver)



Your message dated Sat, 24 Nov 2007 11:59:33 -0700
with message-id <E1Iw0E1-0005r9-Fv@merkel.debian.org>
and subject line WNPP bug closing
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: wnpp
Severity: wishlist

* Package name    : paq
  Version         : 8ja
  Upstream Author : Matt Mahoney <matmahoney@yahoo.com>
* URL             : Homepage: http://cs.fit.edu/~mmahoney/compression
* License         : GPL
  Programming Lang: C++
  Description     : high compression ratio archiver

 PAQ is a series of open source data compression archivers that have
 evolved through collaborative development to top rankings on several
 benchmarks measuring compression ratio (although at the expense of
 speed and memory usage).

- - 

PAQ is a complete rewrite of PAQ6 and variants (PAQAR, PAsQDa).
Compression ratio is similar to PAQAR but 3 times faster. However it
lacks x86 and a dictionary, so does not compress Windows executables
and English text files as well as PAsQDa. It does include models for
color .bmp, .tiff, and .jpeg files, so compresses these files better.
The primary difference from older PAQs is it uses a neural network to
combine models rather than a gradient descent mixer.

Test results are shown on the Calgary corpus (14 individual files or
concatenated into a single file of 3,141,622 bytes). All options set
for maximum compression. Programs are ordered by increasing
compression on the concatenated corpus. For sources to many programs,
see <ftp://ftp.elf.stuba.sk/pub/pc/pack/>.

  Program         Options        14 files   Seconds  Concatenated
  -------         -------        --------   -------  ------------
  gzip 1.2.4      -9             1,017,624     2     1,021,863
  bzip2 1.0.0     -9               828,347     5       859,448
  7zip 3.11       a -mx=9          822,059    20       821,872
  winrar 3.20 b3  best, solid      754,270     7       760,953
  PAQ8F          -4                606,605   828***    120 MB
		 -6                605,650   840***    435 MB

  ***Tested on a 2.2 GHz AMD-64 (in 32 bit XP), adjusted times 4.17.

The above data is from PAQ homepage at 
http://cs.fit.edu/~mmahoney/compression/



--- End Message ---
--- Begin Message ---
Hello,

This is an automatic mail sent to close the ITP you have reported or 
are involved with.

Your ITP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.

As this is an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not 
intended by owners and submitters (like you) to be closed, for
example if the ITP is still of your interest, or there has been 
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).

To re-open it, you simply have to mail control@bugs.debian.org
with a body text like this:

 reopen 216740
 stop

Further comments on the work done in the bug sent to
216740@bugs.debian.org would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <damog@debian.org>.

A similar process is being applied to other kind of wnpp bugs.

Thanks for your cooperation,

 -- David Moreno Garza <damog@debian.org>.
 


--- End Message ---

Reply to: