Ubuntu
rust-repro-env package

rust-repro-env 0.4.0-1 source package in Ubuntu

Changelog

rust-repro-env (0.4.0-1) unstable; urgency=medium

  * Package repro-env 0.4.0 from crates.io using debcargo 2.6.1
  * Fixes a bug causing some repro-env.lock to regress over time

 -- kpcyrd <email address hidden>  Thu, 29 Feb 2024 19:24:12 +0100

Upload details

Uploaded by:
Rust Maintainers
Uploaded to:
Sid
Original maintainer:
Rust Maintainers
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
rust-repro-env_0.4.0-1.dsc 3.8 KiB f710ce7b777e54b09bac9ca71380f725b7af3ee7e5ddfa7e4fb1ac1da58af5e8
rust-repro-env_0.4.0.orig.tar.gz 84.3 KiB 559e5a237dd08ff57b78defb59bb6b87e97966acad79a65c156a47f93febbe37
rust-repro-env_0.4.0-1.debian.tar.xz 3.7 KiB 95448d58c89413ddc82cf8987f36f9447977b8bb02b08f40f2eabab1758cc29e

Available diffs

No changes file available.

Binary packages built by this source

librust-repro-env-dev: Dependency lockfiles for reproducible build environments 📦🔒 - Rust source code

 Source code for Debianized Rust crate "repro-env"

repro-env: Dependency lockfiles for reproducible build environments

 Tracks a description of a desired state in *repro-env.toml*, for example, the
 latest version of some official container image, with the latest patch level
 and the latest version of some additional packages.
 It also tracks a resolved variant in *repro-env.lock* that tracks the
 specific versions and checksums of the packages needed to set up the described
 environment (at the patch-level available at the time of writing).
 .
 The purpose of *repro-env.toml* is to make it trivial to re-resolve the
 specification if new patches become available. This file is read by *repro-
 env update*.
 .
 The purpose of *repro-env.lock* is to document which compiler versions have
 been used for the release binary associated with a given release. Recording
 this information is essential for reproducible builds and allows future
 forensic investigation of the build environment. It can be either committed
 into the source-code repository or attached to a release as an artifact, along
 with the compiled binary. This file is read by *repro-env build*.

repro-env-dbgsym: debug symbols for repro-env