Zpaq package isnt up to date (wasnt updated over 2 years)

Bug #1074840 reported by thometal
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
zpaq (Debian)
Fix Released
Unknown
zpaq (Ubuntu)
Won't Fix
Wishlist
Unassigned

Bug Description

The current version is 6.15 but the package version is just 1.10, so nearly 2 years of development the package wasnt updated.

The newer version comes with:
- significant faster and better compression engine
- ability to create incremental backups
- ability to create encrypted archives

Also homepage for the project isnt correct anymore, now its:

http://mattmahoney.net/dc/zpaq.html

On the bottom of the page you find the history of zpaq

License is: gplv3 + public domain + mit license

The benefient of the archiver is that it can enhanced with custom algorithms that the default decoder will also able to decompress the file, during a intermediate language how to decompress the file.

Development thread: http://encode.ru/threads/456-zpaq-updates

thometal (thometal)
summary: - Zpaq package isnt uptodate (wasnt updated over 2 years)
+ Zpaq package isnt up to date (wasnt updated over 2 years)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in zpaq (Ubuntu):
status: New → Confirmed
thometal (thometal)
description: updated
tags: added: upgrade-software-version
Revision history for this message
Jari Aalto (jari-aalto) wrote :

The zpaq 1.x is completely different from other zpaq versions, so in practice the 1.x is the final version of the development branch. If someone want's to package any later versions, please name it "zpaq2".

This is analogue to Apache 1.x and Apache 2.x that are completely different code base.

Jari (The Debian mainainer)

Revision history for this message
thometal (thometal) wrote :

I dont think so. Which development branch do you mean? The author of zpaq doesnt use any source versioning tool.

Why do you think its the end of the "Development branch"?

Version 6.15 is still compartible to 1.10 you can dempress archives which where created with zpaq 1.10 with 6.** and earlier.

So I think we dont need a new package for this.

Revision history for this message
Brian Murray (brian-murray) wrote :

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist.

summary: - Zpaq package isnt up to date (wasnt updated over 2 years)
+ [needs-packaging] Zpaq package isnt up to date (wasnt updated over 2
+ years)
Changed in zpaq (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
thometal (thometal) wrote : Re: [needs-packaging] Zpaq package isnt up to date (wasnt updated over 2 years)

Recent quote from the author in the development thread of zpaq about the old package:

"Didn't know zpaq was in Ubuntu. v1.10 is really old. It is single threaded and uses interpreted ZPAQL so it is pretty slow. "

http://encode.ru/threads/456-zpaq-updates?p=31251&viewfull=1#post31251

So please update it to a more recent version. Also I think a new package would confuse the users.

Logan Rosen (logan)
summary: - [needs-packaging] Zpaq package isnt up to date (wasnt updated over 2
- years)
+ Zpaq package isnt up to date (wasnt updated over 2 years)
tags: removed: needs-packaging zpaq
Changed in zpaq (Debian):
status: Unknown → New
Revision history for this message
Jari Aalto (jari-aalto) wrote :

I'm the Debian maintainer of zpaq. I'd like to explain why the zpaq hasn't been updated since.

* Not having any manual pages. the pages were hand written by me.
  The pages are quite extensive in size and coverage.

* After 1.10 the zpaq infrastructure changed radically.
   It was split into library part and client part.

It was not possible to upgrade to new versions as the manual pages and all the source code very very much incompatible. It was not possible to merge in changes. After every new release this divergency has increased.

The situation is comparable to apache1 and apache2: The Apache2 is a rewrite and not upgradeable in source level.

I suggest that somebody opens a RFP (request for package) for "zpaq2" or "zpaq-new" that is based on the new infrastructure. The packager also probably needs to start from scratch to e.g. write the associated manual pages.

There are no viable solutions or possibilities as far as I can see to update 1.10 any further.

Possibly this bug might be marked as "wontfix" in Debian tag parlance.

Michael Bienia (geser)
Changed in zpaq (Ubuntu):
status: Confirmed → Won't Fix
Changed in zpaq (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.