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

Changelog

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

  * No-change rebuild for CVE-2024-3094

 -- William Grant <email address hidden>  Mon, 01 Apr 2024 16:15:54 +1100

Upload details

Uploaded by:
William Grant
Uploaded to:
Noble
Original maintainer:
Ubuntu Developers
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Oracular release universe misc
Noble release universe misc

Downloads

File Size SHA-256 Checksum
rust-repro-env_0.4.0.orig.tar.gz 84.3 KiB 559e5a237dd08ff57b78defb59bb6b87e97966acad79a65c156a47f93febbe37
rust-repro-env_0.4.0-1build1.debian.tar.xz 3.8 KiB 49dadfbea3190088473828fe57d7776eaa8b071cb1dc1aea5c5814c06557def3
rust-repro-env_0.4.0-1build1.dsc 3.8 KiB 9ab0de86d5a0aff062a5e050e5acd402a6cf3a4a95679fdc4053591535ce959e

View changes file

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