Dmedia 13.02 "Copy increasing"

In this release we'll turn on the copy-increasing behaviours.

There are two conditions under which new copies are created: the user requests a file that isn't available locally, or a user file has low durability.

And there are two ways the copy increasing happens: it is copied from a local drive to another local drive, or it is downloaded from a peer.

Milestone information

Code name:
Copy increasing
Jason Gerard DeRose
Release registered:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata


Assigned to you:
No blueprints or bugs assigned to you.
3 Jason Gerard DeRose
No blueprints are targeted to this milestone.
3 Fix Released

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon dmedia-13.02.0.tar.gz (md5, sig) tarball 14
last downloaded 2 weeks ago
Total downloads: 14

Release notes 

As there was more work than expected this month on our Dbase32 encoding and finalizing the V1 hashing protocol, we weren't able to turn on the copy-increasing behaviours. So the plan is to turn on both the copy-increasing and the copy-decreasing behaviours in 13.03 (which kinda makes more sense anyway as they are complimentary behaviours).

Note that as of 13.02, we are no longer making releases for Ubuntu 12.04 LTS (Precise) nor Ubuntu 12.10 (Quantal). We recommend most users skip the 13.02 and 13.03 releases, which are higher risk as we turn on the remaining Dmedia behaviours. Instead, upgrade to Ubuntu Raring after its stable release comes out in April (13.04).

For details on how the V0 => V1 migration will work, please see this post:

Changes include:

 * Fixed a critical issue in the confidence downgrading behaviour: if a FileStore was missing its corresponding dmedia/store doc in CouchDB, the files it contained would never be downgraded by the store atime; now when the dmedia/store doc is missing, all files are immediately downgraded

 * Dropped Python 3.2 support, now requiring Python 3.3 or newer; now using os.sync() instead of calling /bin/sync; extractor now uses new timeout kwarg with subprocess.check_call() and friends, preventing the extractor from hanging

 * Lots of prep work for the migration to Dbase32 encoding for document IDs and for the migration to the final, version one hashing protocol

 * Ported from UDisks to UDisks2, which we now use through Gio.VolumeMonitor rather than directly through DBus; currently the auto-format functionality isn't available (although it was disabled by default anyway)


This release does not have a changelog.

0 blueprints and 3 bugs targeted

Bug report Importance Assignee Status
1131742 #1131742 Downgrade by store atime even when store doc is missing 2 Critical Jason Gerard DeRose  10 Fix Released
1131595 #1131595 Drop Python 3.2 support, prep for Dbase32 3 High Jason Gerard DeRose  10 Fix Released
1132528 #1132528 Drop Udisks, use Gio + Udisks2 3 High Jason Gerard DeRose  10 Fix Released
This milestone contains Public information
Everyone can see this information.