rust-repro-env 0.3.3-1 source package in Ubuntu
Changelog
rust-repro-env (0.3.3-1) unstable; urgency=medium * Package repro-env 0.3.3 from crates.io using debcargo 2.6.1 -- kpcyrd <email address hidden> Sun, 18 Feb 2024 13:51:27 +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 | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
rust-repro-env_0.3.3-1.dsc | 3.6 KiB | 290094afb86120ea20e1c36e5420a024f33dea7187c6cc3b6b020a9663de2004 |
rust-repro-env_0.3.3.orig.tar.gz | 75.3 KiB | 9350456e4be48bc83f2e6cbb5d9a3a9177b629578402d83811dd60c14ae86c12 |
rust-repro-env_0.3.3-1.debian.tar.xz | 3.4 KiB | 43ba6154395e783b335f806f8af6c37374b0c7cb117823165c06e6dcd173ebd0 |
Available diffs
- diff from 0.3.2-3 to 0.3.3-1 (55.4 KiB)
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