Reprozip

------------------

Bugfixes:
* You can now use X11 forwarding even with a remote Docker daemon
* reprounzip-vagrant now works in paths containing spaces

------------------

Bugfixes:
* Files opened through a shebang were stored with a wrong process number
* Running with Docker on non-Linux machine didn't work (e.g. docker-machine); now only X11 doesn't work.
* Some fixes to the graph command

Features:
* `--memory` option for `reprounzip vagrant setup`, to set the VM's RAM.

------------------

Behavior change:
* .rpz pack format changed (version 1 -> 2). Pack is now uncompressed, data is in a nested TGZ archive; allows faster retrieval of metadata (config & trace).
* reprozip trace warnings are now info messages; won't show up without -v

Bugfixes:
* After restarting a Vagrant machine, /dev and /proc wouldn't be mounted anymore
* Files or links referenced in a shebang could be missed by the tracer

Features:
* Runs in the configuration file now have an 'id' field, that will be shown by 'reprounzip info' and can be selected when running
* Reworked `reprounzip graph`: level of details, regex filters & replace, JSON output
* Added *run* argument to `reprounzip showfiles`, to show inputs & outputs of a single run

------------------

Behavior change:
* reprounzip-docker will now re-use the resulting image from the previous run when running again, instead of starting from scratch; a 'reset' command has been added to undo runs and uploads.

Bugfixes:
* Couldn't reset an input file to the original (packed) file on Python 3
* Don't show a warning about network connections when they didn't succeed
* Hide traceback when failing because Vagrant is not installed
* Fix input/output file detection assigning files to the same run
* Fix selecting multiple runs in 'docker run'

Features:
* Display the relative portion of the path when unhandled xxx_at() syscalls are used, to give an idea of what's been missed
* Add --dont-find-inputs-outputs to reprozip trace and reset, so you can clear that out if too many files would be selected (or if you don't use the feature)
* Rewrote reprounzip-vistrails plugin; uses a proper VisTrails package that now lives in the VisTrails distribution.
* Check pack format in unpackers; won't try to unpack version 2
* It is now possible to select multiple runs with `unpackername run 1-4`

------------------

(reprozip only)

Bugfixes:
* Files (or links) created with rename, link or symlink then read will no longer be packed.
* A buffer overflow could happen in the log module, for instance when the experiment passes a very long argument to execve (over 4kB in a single argument) and running in debug mode (-v -v)

----------------

Behavior change:
* No longer accept passing `-v` after the subcommand; use `reprozip -v testrun ...`, not `reprozip testrun -v`.
* Rely on `PTHREAD_EVENT_EXEC` to handle `execve()`. Makes tracing more reliable, and enable it to behave correctly on weird kernels (like UML).
* Rely on `PTRACE_EVENT_FORK` to handle `fork`/`vfork`/`clone`. Fixes vfork() deadlocking under trace.
* Completely changed the structure of input and output files (old packs will still be loaded, but new packs are not retro-compatible).
* Using one of the `run` commands without specifying a number will no longer default to running all of them; it will error out if there are multiple runs.

Bugfixes:
* Fix insertion speed in SQLite3 database

Features:
* Makes VMs (Vagrant or Docker) more resilient to massive breakage of system libraries (obliterating /lib or /usr, when using very different operating systems) by putting busybox in / and using [rpzsudo](https://github.com/remram44/static-sudo).
* No longer use `dpkg -S` to identify packages, do a single pass over internal dpkg database (this is considerably faster).