rust-repro-env 0.3.2-3 source package in Ubuntu

Changelog

rust-repro-env (0.3.2-3) unstable; urgency=medium

  * Team upload.
  * Package repro-env 0.3.2 from crates.io using debcargo 2.6.1

 -- Peter Michael Green <email address hidden>  Tue, 30 Jan 2024 17:53:18 +0000

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.3.2-3.dsc 3.6 KiB ee23e78aaeae585d71b174a61ef13d88f8910351c1b21be0345fe9b47fa9ee7c
rust-repro-env_0.3.2.orig.tar.gz 53.7 KiB 18ebc300884f7a692593857ff98e5ece9cf5800624f479d8da0a1fe8217b57e3
rust-repro-env_0.3.2-3.debian.tar.xz 3.4 KiB 0d99f023a01495fd3f518d2381b310dd5eec9334fa5dc26809f4704b6b1a73f1

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