care 2.2.1-1 source package in Ubuntu

Changelog

care (2.2.1-1) unstable; urgency=low

  * Initial release (Closes: #779349)
 -- Remi Duraffort <email address hidden>   Fri, 27 Feb 2015 10:45:03 +0200

Upload details

Uploaded by:
Rémi Duraffort
Sponsored by:
Matthias Klose
Uploaded to:
Vivid
Original maintainer:
Rémi Duraffort
Architectures:
amd64 armel armhf i386 sh4 x32
Section:
utils
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Xenial release universe utils

Builds

Vivid: [FULLYBUILT] amd64 [FULLYBUILT] armhf [FULLYBUILT] i386

Downloads

File Size SHA-256 Checksum
care_2.2.1.orig.tar.gz 225.4 KiB 0251c4d2c7e4ec4c64c57162e4b99960005d4055cb72eb17d826a02eb53c6661
care_2.2.1-1.debian.tar.xz 7.5 KiB d6a062b1f83fb008c1532657142430988f5a7ca9f44aaf522cc76ee976b5b817
care_2.2.1-1.dsc 1.8 KiB 702aa7b179a83ef22b5fd3bfe51a55b94cc73aa76318b89d5410e4b89a29e44d

View changes file

Binary packages built by this source

care: make linux programs reproducible on all linux systems

 CARE monitors the execution of the specified command to create an archive that
 contains all the material required to re-execute it in the same context.
 .
 That way, the command will be reproducible everywhere, even on Linux systems
 that are supposed to be not compatible with the original Linux system. CARE is
 typically useful to get reliable bug reports, demonstrations, artifact
 evaluation, tutorials, portable applications, minimal rootfs, file-system
 coverage, ...
 .
 By design, CARE does not record events at all. Instead, it archives
 environment variables and accessed file-system components -- before
 modification -- during the so-called initial execution. Then, to reproduce
 this execution, the re-execute.sh script embedded into the archive restores
 the environment variables and relaunches the command confined into the saved
 file-system.