# reproducible builds

A software build practice that enables verification by reproducing byte-for-byte identical binary packages from a given source.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Build systems à la trace

DevFeed: [Build systems à la trace](<https://devfeed.tech/articles/build-systems-a-la-trace-143192.md>)

Original publisher: [Read original article](<https://fzakaria.com/2026/11/18/build-systems-a-la-trace>)

Author: Farid Zakaria

Published: 2026-11-18T18:00:00Z

Content type: article

Language: en

Sources: [Farid Zakaria's Blog](<https://devfeed.tech/sources/farid-zakaria-s-blog.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [Build tool](<https://devfeed.tech/topics/build-tool.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [make](<https://devfeed.tech/topics/make.md>)

Tags: [bazel](<https://devfeed.tech/tags/bazel.md>), [build-system](<https://devfeed.tech/tags/build-system.md>), [build-systems](<https://devfeed.tech/tags/build-systems.md>), [trace](<https://devfeed.tech/tags/trace.md>)

### AI overview

genrulify turns a recorded Nix build into Bazel and Buck rules by using Rewind's deterministic VM trace to capture commands, dependencies, environment, file descriptors, and filesystem states. It models each command as a unit of work, tracks successive versions of files to handle in-place changes, and uses MLIR passes to simplify the graph. The initial output is one `genrule` per command, with inputs and outputs made explicit; recorded commands run in a sandbox that recreates their original context. Pattern matching can raise commands into abstractions such as `cc_object`, but these remain macros over genrules and do not change execution semantics. The article reports that Bazel and buck2 produced GNU hello with the same NAR hash served by cache.nixos.org, and argues that the explicit graph enables parallel scheduling even when the original build used `make -j1`. This conversion describes a build after it has run; the excerpt does not establish that future dynamic dependencies are known in advance.

### Source excerpt

As a build systems enthusiast, Build Systems à la Carte is one of my favourite papers. It defines a way to think about build systems that is both precise and surprisingly practical.

## What if every Nix build were bit-reproducible?

DevFeed: [What if every Nix build were bit-reproducible?](<https://devfeed.tech/articles/what-if-every-nix-build-were-bit-reproducible-126397.md>)

Original publisher: [Read original article](<https://fzakaria.com/2026/11/09/what-if-every-nix-build-were-bit-reproducible>)

Published: 2026-11-09T18:00:00Z

Content type: article

Language: en

Sources: [Farid Zakaria's Blog](<https://devfeed.tech/sources/farid-zakaria-s-blog.md>)

Topics: [Nix](<https://devfeed.tech/topics/nix.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>)

Tags: [builds](<https://devfeed.tech/tags/builds.md>), [built-from-source](<https://devfeed.tech/tags/built-from-source.md>), [cache](<https://devfeed.tech/tags/cache.md>), [cascade](<https://devfeed.tech/tags/cascade.md>), [change](<https://devfeed.tech/tags/change.md>), [content](<https://devfeed.tech/tags/content.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [hash](<https://devfeed.tech/tags/hash.md>), [input](<https://devfeed.tech/tags/input.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-distribution](<https://devfeed.tech/tags/linux-distribution.md>), [making](<https://devfeed.tech/tags/making.md>), [model](<https://devfeed.tech/tags/model.md>), [multiple](<https://devfeed.tech/tags/multiple.md>), [nix](<https://devfeed.tech/tags/nix.md>), [rebuilds](<https://devfeed.tech/tags/rebuilds.md>), [reproducibility](<https://devfeed.tech/tags/reproducibility.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [scheduling](<https://devfeed.tech/tags/scheduling.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

Rewind, a deterministic virtual machine, can make Nix builds bit-reproducible by capturing implicit inputs such as time, randomness, and scheduling in a controlled environment. The article's example shows a build with a random UUID and timestamp failing Nix's determinism check on the host but producing the same bytes and content-addressed store path across Rewind builds and stores. Reproducibility can therefore enable cache hits across machines and avoid input-addressed rebuild cascades and multiple output variants. Rewind requires KVM and an advertised rewind-amd or rewind-intel host feature; fixed-output derivations are refused because the VM has no network. Reproducibility is limited to the same Rewind version and CPU vendor: changing Rewind forces rebuilds, and Intel and AMD produce different, though individually reproducible, outputs.

### Source excerpt

The holy grail of build systems and package managers is bit-reproducible1 builds. This is such a desired trait that nearly every Linux distribution has a reproducible builds project to track the progress and validity of their builds. Why is bit-reproducibility so important? Trust. You can trust that the software you are running has not been tampered with and is the same as what the developers intended if you can verify that when built from source, the output is identical. Making software bit-reproducible though is hard. There are a lot of ways that can introduce non-determinism into a build: timestamps, random seeds, thread scheduling, and more. Most distributions that have achieved "reproducible builds" have done so for only a subset of their packages, usually those that comprise the core of the ISO or distribution. Nix's default model, the extensional model (input-addressed), famously works around the need for bit-reproducibility by hashing the inputs to a build and using that hash as the store path. This lets the build be repeatable even if the output is not bit-for-bit identical. It is an incredibly pragmatic solution to making builds repeatable, but it does not solve the problem of trust. We are still trusting the outputs uploaded to cache.nixos.org have not been tampered with. Nix also has an experimental content-addressed model (intensional model) where the /nix/store paths are based on the content of the output, but crucially, it does not guarantee that the builds are bit-reproducible. This leaves us with an undesirable situation regardless of the model. For the extensional model, the smallest change in the inputs changes the store path which causes a cascade of rebuilds. For the intensional model, a single derivation can produce multiple different outputs. Extensional model input-addressed one byte changes glibc zlib openssl curl x7mq2v... 9kd0zl... p3vn8a... c1rw5y... ba4ks1... h0wq7f... 6jtm9d... rz2pl8... rebuilt rebuilt rebuilt rebuilt One input changes, every path dow

## This Shit is Hard: Nobody has ever been pwned by Helvetica...or have they?

DevFeed: [This Shit is Hard: Nobody has ever been pwned by Helvetica...or have they?](<https://devfeed.tech/articles/this-shit-is-hard-nobody-has-ever-been-pwned-by-helvetica-or-have-they-105768.md>)

Original publisher: [Read original article](<https://www.chainguard.dev/unchained/this-shit-is-hard-nobody-has-ever-been-pwned-by-helvetica-or-have-they>)

Published: 2026-10-28T00:00:00Z

Content type: article

Language: en

Sources: [Chainguard: Unchained](<https://devfeed.tech/sources/chainguard-unchained.md>)

Topics: [chainguard os](<https://devfeed.tech/topics/chainguard-os.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [Data integrity in software engineering](<https://devfeed.tech/topics/data-integrity-in-software-engineering.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [000](<https://devfeed.tech/tags/000.md>), [2](<https://devfeed.tech/tags/2.md>), [2005](<https://devfeed.tech/tags/2005.md>), [2015](<https://devfeed.tech/tags/2015.md>), [2019](<https://devfeed.tech/tags/2019.md>), [2020](<https://devfeed.tech/tags/2020.md>), [2022](<https://devfeed.tech/tags/2022.md>), [2023](<https://devfeed.tech/tags/2023.md>), [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [fonts](<https://devfeed.tech/tags/fonts.md>), [pwned](<https://devfeed.tech/tags/pwned.md>), [risk](<https://devfeed.tech/tags/risk.md>), [security](<https://devfeed.tech/tags/security.md>), [source](<https://devfeed.tech/tags/source.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [this](<https://devfeed.tech/tags/this.md>), [this-shit-is-hard](<https://devfeed.tech/tags/this-shit-is-hard.md>)

### AI overview

Fonts are executable, complex data parsed by historically vulnerable software, yet many Linux distributions ship upstream font binaries without building them from source. Chainguard OS rebuilt 2,347 files across 323 families from available sources, while 205 files in 17 packages remain prebuilt because no sources exist. The work exposed stale or incorrect upstream binaries, packaging and build bugs, and architecture-dependent output differences. Chainguard added lint rules requiring documented exceptions and tracking issues, plus upgrade and rendering checks to compare rebuilt fonts with releases. The article frames direct exploitation through a poisoned distribution font as low probability, requiring both a compromised release and an unpatched renderer, and reports no known cases of distribution font poisoning. Its stronger benefits are provenance, verifiability, and the ability to fix neglected fonts; rebuilding remains difficult where sources, reliable toolchains, or maintainers are lacking.

### Source excerpt

Fonts are an overlooked software supply chain risk. Learn how Chainguard rebuilt thousands of fonts from source to improve security and trust.

## One Signed Answer: SLSA Verification Summaries for registry.k8s.io Images

DevFeed: [One Signed Answer: SLSA Verification Summaries for registry.k8s.io Images](<https://devfeed.tech/articles/one-signed-answer-slsa-verification-summaries-for-registry-k8s-io-images-104466.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/10/28/registry-k8s-io-verification-summaries/>)

Author: The Kubernetes Authors

Published: 2026-10-28T00:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [slsa levels](<https://devfeed.tech/topics/slsa-levels.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [builder](<https://devfeed.tech/tags/builder.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [identity](<https://devfeed.tech/tags/identity.md>), [image](<https://devfeed.tech/tags/image.md>), [images](<https://devfeed.tech/tags/images.md>), [k8s](<https://devfeed.tech/tags/k8s.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [manifest](<https://devfeed.tech/tags/manifest.md>), [policy](<https://devfeed.tech/tags/policy.md>), [promotion](<https://devfeed.tech/tags/promotion.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [registry](<https://devfeed.tech/tags/registry.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [repository](<https://devfeed.tech/tags/repository.md>), [slsa](<https://devfeed.tech/tags/slsa.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

The Kubernetes image promoter now evaluates staging-image provenance against each project's policy in kubernetes/k8s.io, copies accepted attestations to registry.k8s.io, and publishes a signed SLSA verification summary (VSA) for each promoted image. Consumers can check the summary signer, verifier ID, result, and required build level with cosign and jq, or download it and run slsa-verifier with crane. Pin both signer and level: PASSED alone may mean only that promotion used a reviewed manifest, and an image without a policy can receive SLSA_BUILD_LEVEL_UNEVALUATED. SPO's v1.1.1 operator images, binaries, and Helm chart reach level 3; its bundle reaches only level 1 in that release, so a level 3 check fails. Projects need signed staging provenance, a manifest policy, and a test run. Cloud Build can provide level 1; level 3 requires provenance from an isolated GitHub workflow, then verification and attachment to the matching staging digest. Roll out policies in warn mode, test with kpromo cip, verify summaries, then use require to block violations. Summaries are created once at promotion, and most images promoted before October 2026 lack them; multi-architecture platform images need,

### Source excerpt

The Kubernetes community has been signing its container images since v1.24, and the images that kpromo, the Kubernetes image promoter (rewritten earlier this year), copies to registry.k8s.io get a signature. A signature answers one question: did this image go through the official promotion process? It does not answer the more interesting one: how was this image built, and from which source? Projects can attach signed SLSA provenance to their images to answer that. But to check it yourself, you have to know who builds each image, which identity signs its provenance, which builder it claims and which repository it comes from, for every project you pull from. That is a lot to ask, and in practice few people do it. Since October 2026, the image promoter does this work for you, once, at promotion time, and publishes the answer as a signed SLSA verification summary (VSA) for every image it promotes. In this blog post, I'd like to explain how it works, how you can verify it, and how your project can get its images verified at SLSA build level 1 or 3. How does it work? A project declares a provenance policy in its promoter manifest in kubernetes/k8s.io: who may sign its build attestations, which builders it trusts and at which level, and which source repositories its images come from. When a reviewed pull request promotes an image, the promoter evaluates the attestations of the staging image against that policy with the SLSA verifier, copies the accepted attestations to registry.k8s.io and writes the summary: flowchart LR build["Project build"] staging[("Staging registry")] policy["Provenance policy
in kubernetes/k8s.io"] promoter["Image promoter"] prod[("registry.k8s.io")] users["Users and clusters"] build -- "image and
signed provenance" --> staging staging --> promoter policy --> promoter promoter -- "image, attestations,
verification summary" --> prod prod -- "verify one summary" --> users The summaries are signed by a dedicated identity, promoter-summaries@

## Who wrote this byte?

DevFeed: [Who wrote this byte?](<https://devfeed.tech/articles/who-wrote-this-byte-98446.md>)

Original publisher: [Read original article](<https://fzakaria.com/2026/10/23/who-wrote-this-byte>)

Published: 2026-10-23T17:00:00Z

Content type: article

Language: en

Sources: [Farid Zakaria's Blog](<https://devfeed.tech/sources/farid-zakaria-s-blog.md>)

Topics: [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [reproducibility](<https://devfeed.tech/topics/reproducibility.md>), [Nix](<https://devfeed.tech/topics/nix.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Data integrity in software engineering](<https://devfeed.tech/topics/data-integrity-in-software-engineering.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [GPU instancing](<https://devfeed.tech/topics/gpu-instancing.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [git](<https://devfeed.tech/tags/git.md>), [hash](<https://devfeed.tech/tags/hash.md>), [input](<https://devfeed.tech/tags/input.md>), [nix](<https://devfeed.tech/tags/nix.md>), [package](<https://devfeed.tech/tags/package.md>), [reproducibility](<https://devfeed.tech/tags/reproducibility.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

Rewind VM's `rewind blame` traces the first program that wrote a differing byte between two build runs. In the `tiles` example, varying Python's random hash seed changes the order of dependencies written to a pkg-config file; blame traces the difference through `install` to `python3`, and sorting the dependencies fixes it. Rewind records file writes and opens in the guest kernel, then reads those traces to identify byte provenance without replaying both runs. Its checks can vary random seeds, thread schedules, and directory-entry order, each of which can expose different sources of non-reproducibility. The excerpt also describes a visual comparison in the Rewind app and says recording overhead was measured as small enough to keep enabled in every run.

### Source excerpt

git blame for your build's bytes. 🔍 A build is bit reproducible when the same inputs give the same bytes. Why does reproducibility matter? They provide certainty that software is genuine and has not been tampered with. See reproducible-builds.org. Nix is infamously not bit reproducible, but rather input-addressed: the hash of a package is calculated from the inputs rather than the output.

## A beginner's guide to the Jenesis build tool

DevFeed: [A beginner's guide to the Jenesis build tool](<https://devfeed.tech/articles/a-beginner-s-guide-to-the-jenesis-build-tool-97869.md>)

Original publisher: [Read original article](<https://vladmihalcea.com/jenesis-build-tool/>)

Author: vladmihalcea

Published: 2026-10-23T13:18:34Z

Content type: tutorial

Language: en

Sources: [Vlad Mihalcea](<https://devfeed.tech/sources/vlad-mihalcea.md>)

Topics: [Build tool](<https://devfeed.tech/topics/build-tool.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [beginner](<https://devfeed.tech/tags/beginner.md>), [build](<https://devfeed.tech/tags/build.md>), [build-tool](<https://devfeed.tech/tags/build-tool.md>), [guide](<https://devfeed.tech/tags/guide.md>), [java](<https://devfeed.tech/tags/java.md>), [tool](<https://devfeed.tech/tags/tool.md>)

### AI overview

Jenesis can build an existing Maven project directly from its POMs, but its behavior differs in several practical ways. In the Hypersistence Utils trial, Maven and Jenesis produced jars with the same entries apart from Jenesis's CycloneDX SBOM; matching debug information required adding `-g` to Jenesis's javac settings. Test runs passed on JDK 25, though shared local databases required setting `jenesis.process.concurrency=1` to prevent modules from interfering. Dependency tie-breaking differed from Maven, and full dependency pinning changed Maven's resolutions and froze transitive versions, so the author retained only three managed versions to align both tools. Jenesis reproduced the build and skipped unchanged steps on reruns, but incremental test selection missed tests that referenced changed classes through annotations. The article also notes that Jenesis requires Java 25 or newer and needs configuration for test JVM properties, environment variables, and other Maven plugin behavior.

### Source excerpt

Introduction In this article, I'm going to show you how we can build the Hypersistence Utils project with Jenesis, a new Java build tool created by Rafael Winterhalter, who's a Java Champion, author of Byte Buddy and a major contributor to Mockito. If you haven't heard of it yet, check out this introductory article first. What is Jenesis Jenesis is a build tool whose engine is just plain Java code that you can embed into your project in the build/jenesis folder. I first heard of Jenesis at JavaZone 2026 during this talk... Read More The post A beginner's guide to the Jenesis build tool appeared first on Vlad Mihalcea.

## RELAY: Scaling Historical Build Restoration through Rule Reuse and Agentic Repair

DevFeed: [RELAY: Scaling Historical Build Restoration through Rule Reuse and Agentic Repair](<https://devfeed.tech/articles/relay-scaling-historical-build-restoration-through-rule-reuse-and-agentic-repair-93705.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.27784>)

Author: Olivier Nourry, Yoshiki Higo

Published: 2026-10-21T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [builds](<https://devfeed.tech/topics/builds.md>), [rule-engine](<https://devfeed.tech/topics/rule-engine.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [approach](<https://devfeed.tech/tags/approach.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [automated](<https://devfeed.tech/tags/automated.md>), [base](<https://devfeed.tech/tags/base.md>), [base-images](<https://devfeed.tech/tags/base-images.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [can](<https://devfeed.tech/tags/can.md>), [cases](<https://devfeed.tech/tags/cases.md>), [change](<https://devfeed.tech/tags/change.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [relay](<https://devfeed.tech/tags/relay.md>), [repair](<https://devfeed.tech/tags/repair.md>), [restoration](<https://devfeed.tech/tags/restoration.md>), [reuse](<https://devfeed.tech/tags/reuse.md>), [scaling](<https://devfeed.tech/tags/scaling.md>)

### AI overview

Across 14,159 OSS-Fuzz cases, 69.7% no longer complete reconstruction and verification as external build resources change. Relay uses an LLM to derive and validate deterministic repair rules from representative failures, then reuses those rules without further model calls; unresolved cases go to a per-case agent. The abstract reports that rule derivation can be fully automated and rules restore as many builds as per-case agents with fewer build executions, while agents can repair cases rules cannot. Applying rules first and escalating the remainder restores more builds than either method alone, at lower cost than using agents alone.

### Source excerpt

arXiv:2610.27784v1 Announce Type: new Abstract: Vulnerability benchmarks and software engineering research depend on rebuilding historical software. Yet builds rely on external resources, such as base images and packages, that change independently of the source code. In this study, we examine this environment decay on 14,159 OSS-Fuzz cases. We find that 69.7% no longer complete reconstruction and verification, and that most failures share a small number of recurring failure symptoms. A recurring failure can therefore be diagnosed once and its repair reused. We present Relay, a hybrid framework that uses an LLM to derive and validate deterministic repair rules from representative failures, reuses them without model calls, and escalates cases unresolved by rules to a per-case agent. We evaluate Relay in human-guided and fully automated rule-derivation campaigns and compare it with a per-case agent approach. We find that rule derivation can be fully automated, and that reusable rules restore as many builds as per-case agents with fewer build executions. However, agents restore cases that the rules cannot. Our results show that a hybrid approach that applies rules first and escalates the remaining cases to an agent restores more builds than either approach alone and at a lower cost than using agents alone.

## Quarkus builds: challenges and safeguards for reproducibility

DevFeed: [Quarkus builds: challenges and safeguards for reproducibility](<https://devfeed.tech/articles/quarkus-insights-263-everything-you-didn-t-want-to-know-about-quarkus-build-reproducibility-87684.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-insights-263-quarkus-build-reproducibility/>)

Author: James Cobb (https://twitter.com/insectengine)

Published: 2026-10-12T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [bazel](<https://devfeed.tech/topics/bazel.md>), [Maven](<https://devfeed.tech/topics/maven.md>)

Tags: [build-tool](<https://devfeed.tech/tags/build-tool.md>), [bytecode](<https://devfeed.tech/tags/bytecode.md>), [development](<https://devfeed.tech/tags/development.md>), [java](<https://devfeed.tech/tags/java.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [reproducibility](<https://devfeed.tech/tags/reproducibility.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>)

### AI overview

Quarkus Insights episode 263 examines why bit-for-bit reproducible builds are difficult in Quarkus, where ahead-of-time bytecode generation and parallel build steps introduce sources of nondeterminism. The team describes fixes for ordering, shared counters, collections and composite indexing, alongside multi-tiered checks and nightly CI verification. They also discuss using diffoscope and LLMs to categorize failures, with engineers making the architectural decisions.

### Source excerpt

This summary was generated using AI, reviewed by humans - watch the video for the full story. Quarkus Insights # 263: Everything You Didn't Want to Know About Quarkus Build Reproducibility Achieving reproducible builds in modern software is often described as straightforward: pin your dependencies, use a deterministic compiler, and let your build tool do the rest. In a framework like Quarkus, however, where the build process performs heavy ahead-of-time bytecode generation and executes build steps across multiple parallel threads, determinism is anything but simple. In episode 263, community contributor Teymur (Tim) Babayev and Quarkus core maintainers Guillaume Smet and Ladislav Thon join host Holly Cummins to unpack the technical challenges of making Quarkus builds bit-for-bit reproducible, the insidious sources of non-determinism they uncovered, and the infrastructure now in place to ensure our binaries continue to stay reproducible. Quarkus News Holly opened the episode with an unusual announcement: for the first time in months, there was no new minor or micro release during the week. With the release cadence briefly paused, Guillaume took a well-earned break from preparing backports. The core team is currently focused on iterating on the Quarkus 4 betas leading up to the final release, with micro releases on earlier streams reserved strictly for critical CVEs. Community members are encouraged to try out the Quarkus 4 beta, test their applications, and report any issues or feedback. What Is Build Reproducibility and Why Does It Matter? Guillaume kicked off the technical discussion by defining build reproducibility according to the principles of Reproducible Builds: given the exact same source code, same Java Development Kit (JDK), same operating system, and identical build inputs, the build must produce the exact same binary output bit-for-bit. Two major requirements drive the need for reproducible builds: Supply chain security and forensics: High-profile securi

## Updating \`apk add\` and \`apt install\` definitions in Dockerfiles with Renovate

DevFeed: [Updating \`apk add\` and \`apt install\` definitions in Dockerfiles with Renovate](<https://devfeed.tech/articles/updating-apk-add-and-apt-install-definitions-in-dockerfiles-with-renovate-53102.md>)

Original publisher: [Read original article](<https://www.jvt.me/posts/2026/09/18/renovate-regex-dockerfile-apk/>)

Author: Jamie Tanna

Published: 2026-09-18T17:30:05Z

Content type: article

Language: en

Sources: [Jamie Tanna](<https://devfeed.tech/sources/articles-on-jamie-tanna-software-engineer.md>)

Topics: [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [renovate](<https://devfeed.tech/topics/renovate.md>), [APK](<https://devfeed.tech/topics/apk.md>), [apt](<https://devfeed.tech/topics/apt.md>), [Package Management](<https://devfeed.tech/topics/package-management.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>)

Tags: [apk](<https://devfeed.tech/tags/apk.md>), [apt](<https://devfeed.tech/tags/apt.md>), [blogumentation](<https://devfeed.tech/tags/blogumentation.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [chainguard-images](<https://devfeed.tech/tags/chainguard-images.md>), [dockerfiles](<https://devfeed.tech/tags/dockerfiles.md>), [renovate](<https://devfeed.tech/tags/renovate.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>)

### AI overview

This article explains how Renovate now natively updates pinned packages installed with apk add, apt install, and apt-get install in Dockerfiles. It discusses reproducible builds, support for Wolfi and Chainguard Images, and the temporary need to configure registry URLs explicitly.

### Source excerpt

If you're writing Dockerfiles that install packages using system package managers, such as apk or apt, you might be pinning your versions of packages, to make sure that you have more reproducible builds, or if you're on a rolling release distribution like Wolfi and Chainguard Images, you want to make sure you only get package versions you want. When these system package manager versions are pinned, it can then be a little cumbersome to keep them updated in an automated fashion, as most tools don't have a way to automagically parse your files and propose updates. So you're probably one one of two camps - "I'll get my AI agent to go and update it for me" or "we'll not update anything until things break". I've previously had this managed - at least for apk add updates - by using a Custom Regex Manager with Renovate to keep them updated, which required you break the install command over multiple lines: # ... RUN apk upgrade --no-cache && \ apk add --no-cache \ bash=5.2.37-r2 \ py3-pip \ python3 \ rsyslog=8.2412.0-r1 \ runit=2.2.0 ENV APP_HOST=0.0.0.0 ENV app_port=5000 ENV SNAPP_PORT 5000 This isn't that much of a problem - as it also improves readability - but you generally want the tools to work around you, not vice versa. As of earlier this morning, we've shipped inbuilt support in Renovate, so if you have a Dockerfile with apk add, or an apt install (or apt-get install) like below, you'll be able to receive package updates for them 🎉 For instance, with the following Dockerfile: # SPDX-License-Identifier: AGPL-3.0-only # Via https://docs.renovatebot.com/modules/manager/dockerfile/#run-apt-install-support FROM debian:trixie RUN apt-get update \ && apt-get install -y --no-install-recommends \ # newlines for readability only curl=8.14.1-2 \ git=1:2.47.3-0+deb13u1 \ && rm -rf /var/lib/apt/lists/* Renovate will detect that you have a package pin for curl and git, and if there are updates available, will propose them. Right now, we don't currently auto-detect the distributi

## Supporter spotlight: Jochen Sprickerhof on reproducible builds

DevFeed: [Supporter spotlight: Jochen Sprickerhof on reproducible builds](<https://devfeed.tech/articles/supporter-spotlight-jochen-sprickerhof-on-reproducible-builds-34163.md>)

Original publisher: [Read original article](<https://reproducible-builds.org/news/2026/09/15/supporter-spotlight-jochen-sprickerhof/>)

Published: 2026-09-15T03:54:00Z

Content type: news

Language: en

Sources: [Reproducible Builds](<https://devfeed.tech/sources/reproducible-builds-org.md>)

Topics: [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Debian](<https://devfeed.tech/topics/debian.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [F-Droid](<https://devfeed.tech/topics/f-droid.md>), [Robotics](<https://devfeed.tech/topics/robotics.md>), [Point cloud](<https://devfeed.tech/topics/point-cloud.md>)

Tags: [debian](<https://devfeed.tech/tags/debian.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [org](<https://devfeed.tech/tags/org.md>), [programming](<https://devfeed.tech/tags/programming.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [robotics](<https://devfeed.tech/tags/robotics.md>)

### AI overview

An interview with Jochen Sprickerhof, a freelance programmer and Reproducible Builds core team member, covering his work on Debian, F-Droid, software projects, and bit-for-bit reproduction of Debian packages.

### Source excerpt

The Reproducible Builds project relies on several projects, supporters and sponsors for financial support, but they are also valued as ambassadors who spread the word about our project and the work that we do. This is the ninth installment in a series featuring the projects, companies and individuals who support the Reproducible Builds project. We started this series by featuring the Civil Infrastructure Platform project, and followed this up with a post about the Ford Foundation as well as recent ones about ARDC, the Google Open Source Security Team (GOSST), Bootstrappable Builds, the F-Droid project, David A. Wheeler, Simon Butler and Kees Cook. Today, however, we will be talking with Jochen Sprickerhof, one of the newer members of the Reproducible Builds project core team. Vagrant Cascadian: Could you tell me a bit about yourself? What sort of things do you work on? Jochen Sprickerhof: I am a freelance programmer working on Open Source. Mainly doing Debian, F-Droid and some smaller software projects. In general I made it a habit to look into every software I use and try to fix bugs or add features I need. In Debian, I maintain about 180 packages with topics covering home banking, build systems and robotics. Most of my time, I currently work on reproduce.debian.net, where we try to bit-for-bit reproduce the packages distributed by Debian. Vagrant: Could you describe the path that lead you to working on reproducible builds? Jochen: I started my Debian journey as a teenager, converting my school to Debian and serving as its system administrator for 13 years. After studying Applied System Science, I joined the university's robotics labs, where I worked on the Robot Operating System (ROS) and the Point Cloud Library (PCL). In the end, I enjoyed programming more than writing papers, so I eventually left academia for a robotics startup. Some years ago, I realized that the open source work I was doing in my spare time was actually the work I cared most about. Nowadays I

## How Developer Can Build More Reliable Software for Regulated Industries

DevFeed: [How Developer Can Build More Reliable Software for Regulated Industries](<https://devfeed.tech/articles/how-developer-can-build-more-reliable-software-for-regulated-industries-50841.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/how-developer-can-build-more-reliable-software-for-regulated-industries/>)

Author: Saifullah Adenwalla

Published: 2026-08-28T12:08:22Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>)

Tags: [authorization](<https://devfeed.tech/tags/authorization.md>), [automated](<https://devfeed.tech/tags/automated.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [logging](<https://devfeed.tech/tags/logging.md>), [regulatory](<https://devfeed.tech/tags/regulatory.md>)

### AI overview

This practical article explains how developers can build reliable software for regulated industries. It focuses on translating regulatory requirements into observable, testable behavior and applying practices such as validation, idempotency, authorization, structured logging, automated testing, reproducible builds, and recovery procedures in Node.js applications.

### Source excerpt

null Continue reading How Developer Can Build More Reliable Software for Regulated Industries on SitePoint.

## Reproducible Builds summit 2026 to take place in Gothenburg

DevFeed: [Reproducible Builds summit 2026 to take place in Gothenburg](<https://devfeed.tech/articles/reproducible-builds-summit-2026-to-take-place-in-gothenburg-34162.md>)

Original publisher: [Read original article](<https://reproducible-builds.org/news/2026/08/12/reproducible-builds-summit-in-gothenburg/>)

Published: 2026-08-12T00:00:00Z

Content type: news

Language: en

Sources: [Reproducible Builds](<https://devfeed.tech/sources/reproducible-builds-org.md>)

Topics: [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [builds](<https://devfeed.tech/topics/builds.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [event](<https://devfeed.tech/tags/event.md>), [events](<https://devfeed.tech/tags/events.md>), [inclusive](<https://devfeed.tech/tags/inclusive.md>), [innovation](<https://devfeed.tech/tags/innovation.md>), [org](<https://devfeed.tech/tags/org.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [summit](<https://devfeed.tech/tags/summit.md>), [tools](<https://devfeed.tech/tags/tools.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

The Reproducible Builds summit will take place in Gothenburg, Sweden, from September 22 to 24, 2026. The event will bring together participants to discuss project status, collaboration, broader adoption, and technical solutions.

### Source excerpt

This event is happening soon -- see below for registration instructions! We are extremely pleased to announce the upcoming Reproducible Builds summit, which will take place from September 22nd--24th 2026 in the city of Gothenburg, Sweden. This year, we are thrilled to host the tenth edition of this exciting event, following the success of previous summits in various iconic locations around the world, including Vienna (2025), Hamburg (2023--2024), Venice (2022), Marrakesh (2019), Paris (2018), Berlin (2017), Berlin (2016) and Athens (2015). If you're excited about joining us this year, please make sure to read the event page which has more details about the event and location. As in previous years, we will be sending invitations to all those who attended our previous summit events or expressed interest to do so. However, even if you do not receive a personal invitation, please do email the organizers and we will find a way to accommodate you. About the event The Reproducible Builds Summit is a unique gathering that brings together attendees from diverse projects, united by a shared vision of advancing the Reproducible Builds effort. During this enriching event, participants will have the opportunity to engage in discussions, establish connections and exchange ideas to drive progress in this vital field. Our aim is to create an inclusive space that fosters collaboration, innovation and problem-solving. Schedule Although the exact content of the meeting will be shaped by the participants, the main goals will include: Update & exchange about the status of reproducible builds in various projects. Improve collaboration both between and inside projects. Expand the scope and reach of reproducible builds to more projects. Work together and hack on solutions. Establish space for more strategic and long-term thinking than is possible in virtual channels. Brainstorm designs on tools enabling users to get the most benefits from reproducible builds. Discuss how reproducible builds w

## Fighting Hyrum's Law in LLVM

DevFeed: [Fighting Hyrum's Law in LLVM](<https://devfeed.tech/articles/fighting-hyrum-s-law-in-llvm-31128.md>)

Original publisher: [Read original article](<https://maskray.me/blog/fighting-hyrums-law-in-llvm>)

Published: 2026-05-10T07:00:00Z

Content type: article

Language: en

Sources: [MaskRay](<https://devfeed.tech/sources/maskray.md>)

Topics: [LLVM](<https://devfeed.tech/topics/llvm.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [hashing](<https://devfeed.tech/topics/hashing.md>)

Tags: [clang](<https://devfeed.tech/tags/clang.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [hash](<https://devfeed.tech/tags/hash.md>), [lld](<https://devfeed.tech/tags/lld.md>), [llvm](<https://devfeed.tech/tags/llvm.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [test](<https://devfeed.tech/tags/test.md>)

### AI overview

This article examines how LLVM can develop dependencies on unspecified or incidental behavior under Hyrum's Law, causing output variation that harms reproducible builds, bisection, and bug reports. It describes hash-seed perturbation, reverse container iteration, and iterator invalidation checks as mechanisms for exposing such dependencies.

### Source excerpt

With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody. -- Hyrum's Law In a compiler, the most common form of Hyrum's Law is dependence on unspecified behavior -- hash bucket order, the order of equal elements after std::sort, padding offsets. The same framing covers a few cases that are technically undefined behavior (use of an invalidated iterator) or plain incidental properties (ABI struct layout, ELF section offsets). When the compiler itself harbors such a dependency, the symptom is usually output that varies build-to-build: an unstable sort that lands differently after the standard library changes, a hash map whose iteration order shifts when the hash function does. Occasionally the variation is run-to-run within a single build -- DenseMap<void *, X> keys with an ASLR-derived seed reorder buckets each invocation. Either way, reproducible builds, bisection, and bug reports all assume same input -> same output, and a stealth Hyrum dependency breaks that. This post surveys some mechanisms that perturb the contract's blind spots so dependencies cannot quietly form.

## Reviving a Static Blog with Nix and Reproducible Builds

DevFeed: [Reviving a Static Blog with Nix and Reproducible Builds](<https://devfeed.tech/articles/reviving-the-blog-21147.md>)

Original publisher: [Read original article](<https://ocramius.github.io/blog/reviving-the-blog/>)

Published: 2026-02-22T00:00:00Z

Content type: tutorial

Language: en

Sources: [Marco Pivetta](<https://devfeed.tech/sources/marco-pivetta.md>)

Topics: [Nix](<https://devfeed.tech/topics/nix.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [Composer](<https://devfeed.tech/topics/composer.md>), [PHP](<https://devfeed.tech/topics/php.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [WordPress](<https://devfeed.tech/topics/wordpress.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [github](<https://devfeed.tech/tags/github.md>), [php](<https://devfeed.tech/tags/php.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [wordpress](<https://devfeed.tech/tags/wordpress.md>)

### AI overview

The author returns to blogging and explains how they stabilized a Sculpin-based static website by using Nix Flakes to pin dependencies and support reproducible builds. The article also covers Composer dependency hashing and deployment to GitHub Pages.

### Source excerpt

I'm back! The last time I blogged was in 2017: a lot has changed since then, and after a decade of ignoring blogging, I will attempt to put some regularity into it again. The times call for it: having a personal space that is really "our own" is extremely important, and it is as important as having something to read that is written by other humans, and not slop. I mainly stopped blogging for two reasons: Wordpress and similar tools are terrible, for rarely changing content. I'd rather not blog, than host a dynamic website just for serving static webpages My static site generation pipeline heavily relied on my workstation's software dependencies, which shifted continuously, breaking the website build at all times. Stabilizing the build Note: This section describes the Nixification of the blog, done in this pull request. You can skip this, if you prefer reading the PR instead. The first thing to do is to get everything under control again. Since a few years back, I started heavily relying on Nix, a lazy functional language that is perfect to achieve reproducible builds and environments. At the time of this writing, this website is built via Sculpin, a static website generator whose dependency upgrades I've neglected for far too long. In order to "freeze" the build in time, I used a Nix Flake to pin all the dependencies down, preventing any further shifts in dependency versions: { inputs = { nixpkgs.url = "github:nixos/nixpkgs?ref=nixos-unstable"; flake-utils.url = "github:numtide/flake-utils"; }; outputs = { self, nixpkgs, flake-utils, composer2nix, ... }@inputs: flake-utils.lib.eachDefaultSystem ( system: { packages = { # things that will stay extremely stable will go here }; } ); } The above will "pin" dependencies such as composer or php, preventing them from drifting apart, unless a commit moves them. This is also thanks to the built-in flake.lock mechanism of Nix Flakes. Because Composer does not compute content hashes of PHP dependencies, NixOS cannot directly u

## Strengthening your Software Supply Chain

DevFeed: [Strengthening your Software Supply Chain](<https://devfeed.tech/articles/strengthening-your-software-supply-chain-23031.md>)

Original publisher: [Read original article](<https://www.javaadvent.com/2025/12/strengthening-your-software-supply-chain.html>)

Author: Andres Almiray

Published: 2025-12-12T03:03:02Z

Content type: article

Language: en

Sources: [Java Advent Calendar](<https://devfeed.tech/sources/java-advent-calendar.md>)

Topics: [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>), [slsa levels](<https://devfeed.tech/topics/slsa-levels.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [Build tool](<https://devfeed.tech/topics/build-tool.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>)

Tags: [2021](<https://devfeed.tech/tags/2021.md>), [2025](<https://devfeed.tech/tags/2025.md>), [apache](<https://devfeed.tech/tags/apache.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [build](<https://devfeed.tech/tags/build.md>), [build-tool](<https://devfeed.tech/tags/build-tool.md>), [building](<https://devfeed.tech/tags/building.md>), [components](<https://devfeed.tech/tags/components.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [develop](<https://devfeed.tech/tags/develop.md>), [devops](<https://devfeed.tech/tags/devops.md>), [java](<https://devfeed.tech/tags/java.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [maven](<https://devfeed.tech/tags/maven.md>), [processes](<https://devfeed.tech/tags/processes.md>), [projects](<https://devfeed.tech/tags/projects.md>), [software](<https://devfeed.tech/tags/software.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [tool](<https://devfeed.tech/tags/tool.md>), [tools](<https://devfeed.tech/tags/tools.md>), [wikipedia](<https://devfeed.tech/tags/wikipedia.md>)

### AI overview

Build tools such as Maven, Gradle, and Ant provide some supply-chain security support, but the excerpt says that using them alone does not secure artifacts, pipelines, compiler toolchains, or other components against tampering. It presents SLSA as a framework of standards and controls for improving integrity and securing packages and infrastructure, and notes that attacks such as Log4Shell or the attempted XZ backdoor might have been prevented or had less impact with timely techniques, metadata, and tools. The excerpt begins with reproducible artifacts: rebuilding the same source with the same tools and instructions in a compatible environment should produce bit-for-bit identical output for comparison. It also says JReleaser supports the features covered in the article. The supplied text cuts off during this section.

### Source excerpt

According to Wikipedia, a software supply chain is the components, libraries, tools, and processes used to develop, build, and publish a software artifact. The Java space provides thousands upon thousands of libraries that may be consumed as dependencies for building projects. Many of these libraries rely on Apache Maven as their build tool of choice, [...] The post Strengthening your Software Supply Chain appeared first on JVM Advent.

## Inside Go -- How It Really Works: Series Kickoff

DevFeed: [Inside Go -- How It Really Works: Series Kickoff](<https://devfeed.tech/articles/inside-go-how-it-really-works-series-kickoff-39762.md>)

Original publisher: [Read original article](<https://furkankolcu.com/post/inside-go-how-it-really-works-series-kickoff>)

Author: Furkan Kolcu

Published: 2025-09-11T10:16:52Z

Content type: article

Language: en

Sources: [Furkan Kolcu](<https://devfeed.tech/sources/furkan-kolcu-software-engineer-blog.md>)

Topics: [Go Language](<https://devfeed.tech/topics/go-language.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [Code](<https://devfeed.tech/topics/code.md>), [Optimization](<https://devfeed.tech/topics/optimization.md>), [escape analysis](<https://devfeed.tech/topics/escape-analysis.md>), [generic programming](<https://devfeed.tech/topics/generic-programming.md>), [modules](<https://devfeed.tech/topics/modules.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>)

Tags: [compilation](<https://devfeed.tech/tags/compilation.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [deep-dive](<https://devfeed.tech/tags/deep-dive.md>), [generics](<https://devfeed.tech/tags/generics.md>), [go](<https://devfeed.tech/tags/go.md>), [go-compiler](<https://devfeed.tech/tags/go-compiler.md>), [go-concurrency](<https://devfeed.tech/tags/go-concurrency.md>), [go-performance](<https://devfeed.tech/tags/go-performance.md>), [go-runtime](<https://devfeed.tech/tags/go-runtime.md>), [golang](<https://devfeed.tech/tags/golang.md>), [how-go-works](<https://devfeed.tech/tags/how-go-works.md>), [inside-go](<https://devfeed.tech/tags/inside-go.md>), [internals](<https://devfeed.tech/tags/internals.md>), [memory-management](<https://devfeed.tech/tags/memory-management.md>), [performance](<https://devfeed.tech/tags/performance.md>), [technology](<https://devfeed.tech/tags/technology.md>)

### AI overview

This article launches a technical series about how Go works internally. The planned installments cover compilation, memory management, garbage collection, concurrency, the runtime, performance tuning, interfaces, generics, modules, and reproducible builds, with code examples and runtime experiments.

### Source excerpt

A deep-dive series into Go's internals. From compilation to memory management, concurrency, and performance tuning, each part unpacks how Go operates under the hood with clear explanations and real-life code examples.

## Reproducible Builds summit 2025 to take place in Vienna

DevFeed: [Reproducible Builds summit 2025 to take place in Vienna](<https://devfeed.tech/articles/reproducible-builds-summit-2025-to-take-place-in-vienna-34161.md>)

Original publisher: [Read original article](<https://reproducible-builds.org/news/2025/08/20/reproducible-builds-summit-in-vienna/>)

Published: 2025-08-20T00:00:00Z

Content type: news

Language: en

Sources: [Reproducible Builds](<https://devfeed.tech/sources/reproducible-builds-org.md>)

Topics: [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [builds](<https://devfeed.tech/topics/builds.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [announce](<https://devfeed.tech/tags/announce.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [event](<https://devfeed.tech/tags/event.md>), [org](<https://devfeed.tech/tags/org.md>), [summit](<https://devfeed.tech/tags/summit.md>), [technical](<https://devfeed.tech/tags/technical.md>)

### AI overview

The Reproducible Builds summit is scheduled for October 28-30, 2025, in Vienna, Austria. The eighth summit will bring participants together to discuss project status, collaboration, tools, and the future of reproducible builds.

### Source excerpt

We are extremely pleased to announce the upcoming Reproducible Builds summit, which will take place from October 28th--30th 2025 in the historic city of Vienna, Austria. This year, we are thrilled to host the eighth edition of this exciting event, following the success of previous summits in various iconic locations around the world, including Hamburg (2023--2024), Venice (2022), Marrakesh (2019), Paris (2018), Berlin (2017), Berlin (2016) and Athens (2015). If you're excited about joining us this year, please make sure to read the event page which has more details about the event and location. As in previous years, we will be sending invitations to all those who attended our previous summit events or expressed interest to do so. However, even if you do not receive a personal invitation, please do email the organizers and we will find a way to accommodate you. About the event The Reproducible Builds Summit is a unique gathering that brings together attendees from diverse projects, united by a shared vision of advancing the Reproducible Builds effort. During this enriching event, participants will have the opportunity to engage in discussions, establish connections and exchange ideas to drive progress in this vital field. Our aim is to create an inclusive space that fosters collaboration, innovation and problem-solving. With your help, we will bring this (and several other areas) into life: The main seminar room. Schedule Although the exact content of the meeting will be shaped by the participants, the main goals will include: Update & exchange about the status of reproducible builds in various projects. Improve collaboration both between and inside projects. Expand the scope and reach of reproducible builds to more projects. Work together and hack on solutions. Establish space for more strategic and long-term thinking than is possible in virtual channels. Brainstorm designs on tools enabling users to get the most benefits from reproducible builds. Discuss how reproduc

## Untangling Python Packages Part 2

DevFeed: [Untangling Python Packages Part 2](<https://devfeed.tech/articles/untangling-python-packages-part-2-83754.md>)

Original publisher: [Read original article](<https://dagster.io/blog/untangling-python-packages-part-2>)

Author: Dennis Hume

Published: 2025-08-07T00:00:00Z

Content type: tutorial

Language: en

Sources: [Dagster](<https://devfeed.tech/sources/dagster.md>)

Topics: [Python](<https://devfeed.tech/topics/python.md>), [Package Management](<https://devfeed.tech/topics/package-management.md>), [pip](<https://devfeed.tech/topics/pip.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>)

Tags: [build-system](<https://devfeed.tech/tags/build-system.md>), [development-tools](<https://devfeed.tech/tags/development-tools.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [packaging](<https://devfeed.tech/tags/packaging.md>), [python](<https://devfeed.tech/tags/python.md>), [python-packages](<https://devfeed.tech/tags/python-packages.md>)

### AI overview

This tutorial explains how Dagster configures pyproject.toml for a modern Python project. It covers project metadata and dependencies, named dependency groups, build backend settings, and Dagster-specific tooling configuration. It also describes using uv to lock dependencies and install selected groups.

### Source excerpt

A deep dive into how Dagster leverages pyproject.toml for modern Python packaging, from project metadata and dependencies to build systems and development tooling.

## Reproducible Builds mourns the passing of Lunar

DevFeed: [Reproducible Builds mourns the passing of Lunar](<https://devfeed.tech/articles/reproducible-builds-mourns-the-passing-of-lunar-34160.md>)

Original publisher: [Read original article](<https://reproducible-builds.org/news/2024/11/14/reproducible-builds-mourns-the-passing-of-lunar/>)

Published: 2024-11-14T15:00:00Z

Content type: news

Language: en

Sources: [Reproducible Builds](<https://devfeed.tech/sources/reproducible-builds-org.md>)

Topics: [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [free software](<https://devfeed.tech/topics/free-software.md>), [Debian](<https://devfeed.tech/topics/debian.md>), [open-source-security](<https://devfeed.tech/topics/open-source-security.md>)

Tags: [debian](<https://devfeed.tech/tags/debian.md>), [free-software](<https://devfeed.tech/tags/free-software.md>), [org](<https://devfeed.tech/tags/org.md>), [reports](<https://devfeed.tech/tags/reports.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>)

### AI overview

The Reproducible Builds community announces the death of founding member Jérémy Bobbio, known as Lunar, and reflects on his contributions to Reproducible Builds, Debian, Tor, and free software security.

### Source excerpt

The Reproducible Builds community sadly announces it has lost its founding member. Jérémy Bobbio aka 'Lunar' passed away on Friday November 8th in palliative care in Rennes, France. Lunar was instrumental in starting the Reproducible Builds project in 2013 as a loose initiative within the Debian project. Many of our earliest status reports were written by him and many of our key tools in use today are based on his design. Lunar was a resolute opponent of surveillance and censorship, and he possessed an unwavering energy that fueled his work on Reproducible Builds and Tor. Without Lunar's far-sightedness, drive and commitment to enabling teams around him, Reproducible Builds and free software security would not be in the position it is in today. His contributions will not be forgotten, and his high standards and drive will continue to serve as an inspiration to us as well as for the other high-impact projects he was involved in. Lunar's creativity, insight and kindness were often noted. He will be greatly missed. Other tributes: Anargeek.net [FR] LWN Debian Stefano Zacchiroli Linuxfr.org [FR] Software Heritage A history of the Reproducible Builds project

## DebConf24 closes in Busan and DebConf25 dates announced

DevFeed: [DebConf24 closes in Busan and DebConf25 dates announced](<https://devfeed.tech/articles/debconf24-closes-in-busan-and-debconf25-dates-announced-47070.md>)

Original publisher: [Read original article](<https://bits.debian.org/2024/08/debconf24-closes.html>)

Author: Jean-Pierre Giraud and Donald Norwood

Published: 2024-08-10T14:00:00Z

Content type: news

Language: en

Sources: [Bits from Debian](<https://devfeed.tech/sources/bits-from-debian.md>)

Topics: [Debian](<https://devfeed.tech/topics/debian.md>), [Linux Kernel](<https://devfeed.tech/topics/linux-kernel.md>), [free software](<https://devfeed.tech/topics/free-software.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [Localization (l10n)](<https://devfeed.tech/topics/localization.md>), [apt](<https://devfeed.tech/topics/apt.md>)

Tags: [announce](<https://devfeed.tech/tags/announce.md>), [apt](<https://devfeed.tech/tags/apt.md>), [busan](<https://devfeed.tech/tags/busan.md>), [conference](<https://devfeed.tech/tags/conference.md>), [debconf](<https://devfeed.tech/tags/debconf.md>), [debconf24](<https://devfeed.tech/tags/debconf24.md>), [debconf25](<https://devfeed.tech/tags/debconf25.md>), [debian](<https://devfeed.tech/tags/debian.md>), [developers](<https://devfeed.tech/tags/developers.md>), [free-software](<https://devfeed.tech/tags/free-software.md>), [go-programming](<https://devfeed.tech/tags/go-programming.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-kernel](<https://devfeed.tech/tags/linux-kernel.md>), [perl](<https://devfeed.tech/tags/perl.md>), [programming](<https://devfeed.tech/tags/programming.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [ruby](<https://devfeed.tech/tags/ruby.md>)

### AI overview

DebConf24 in Busan brought together more than 339 Debian developers and contributors from 48 countries for talks, discussions, workshops, community activities, and project work. The report also covers DebCamp, newcomer training, Debian packaging, infrastructure, reproducible builds, localization, and programming-language team updates.

### Source excerpt

On Saturday 3 August 2024, the annual Debian Developers and Contributors Conference came to a close. Over 339 attendees representing 48 countries from around the world came together for a combined 108 events made up of more than 50 Talks and Discussions, 37 Birds of a Feather (BoF - informal meeting between developers and users) sessions, 12 workshops, and activities in support of furthering our distribution and free software (25 patches submitted to the Linux kernel), learning from our mentors and peers, building our community, and having a bit of fun. The conference was preceded by the annual DebCamp hacking session held July 21st through July 27th where Debian Developers and Contributors convened to focus on their Individual Debian-related projects or work in team sprints geared toward in-person collaboration in developing Debian. This year featured a BootCamp that was held for newcomers with a GPG Workshop and a focus on Introduction to creating .deb files (Debian packaging) staged by a team of dedicated mentors who shared hands-on experience in Debian and offered a deeper understanding of how to work in and contribute to the community. The actual Debian Developers Conference started on Sunday July 28 2024. In addition to the traditional 'Bits from the DPL' talk, the continuous key-signing party, lightning talks and the announcement of next year's DebConf25, there were several update sessions shared by internal projects and teams. Many of the hosted discussion sessions were presented by our technical core teams with the usual and useful meet the Technical Committee and the ftpteam and a set of BoFs about packaging policy and Debian infrastructure, including talk about APT and Debian Installer and an overview about the first eleven years of Reproducible Builds. Internationalization and localization have been subject of several talks. The Python, Perl, Ruby, and Go programming language teams, as well as Med team, also shared updates on their work and efforts. More

## Reproducible Builds at FOSDEM 2024

DevFeed: [Reproducible Builds at FOSDEM 2024](<https://devfeed.tech/articles/reproducible-builds-at-fosdem-2024-34158.md>)

Original publisher: [Read original article](<https://reproducible-builds.org/news/2024/02/08/reproducible-builds-at-fosdem-2024/>)

Published: 2024-02-08T00:00:00Z

Content type: news

Language: en

Sources: [Reproducible Builds](<https://devfeed.tech/sources/reproducible-builds-org.md>)

Topics: [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [FOSDEM](<https://devfeed.tech/topics/fosdem.md>), [Arch Linux](<https://devfeed.tech/topics/archlinux.md>), [Debian](<https://devfeed.tech/topics/debian.md>), [Fedora](<https://devfeed.tech/topics/fedora.md>), [coreboot](<https://devfeed.tech/topics/coreboot.md>), [software bill of materials](<https://devfeed.tech/topics/software-bill-of-materials.md>)

Tags: [coreboot](<https://devfeed.tech/tags/coreboot.md>), [debian](<https://devfeed.tech/tags/debian.md>), [fedora](<https://devfeed.tech/tags/fedora.md>), [fosdem](<https://devfeed.tech/tags/fosdem.md>), [org](<https://devfeed.tech/tags/org.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [software-bill-of-materials](<https://devfeed.tech/tags/software-bill-of-materials.md>)

### AI overview

The article reports on Reproducible Builds activities at FOSDEM 2024. It highlights Holger Levsen's talk covering the project's history, current state, and future goals, along with other talks on reproducibility, confidential computing, RISC-V bootstrapping, reproducible development environments, HPC experiments, configuration options, and software bills of materials.

### Source excerpt

Core Reproducible Builds developer Holger Levsen presented at the main track at FOSDEM on Saturday 3rd February this year in Brussels, Belgium. Titled Reproducible Builds: The First Ten Years... In this talk Holger 'h01ger' Levsen will give an overview about Reproducible Builds: How it started with a small BoF at DebConf13 (and before), then grew from being a Debian effort to something many projects work on together, until in 2021 it was mentioned in an Executive Order of the President of the United States. And of course, the talk will not end there, but rather outline where we are today and where we still need to be going, until Debian stable (and other distros!) will be 100% reproducible, verified by many. h01ger has been involved in reproducible builds since 2014 and so far has set up automated reproducibility testing for Debian, Fedora, Arch Linux, FreeBSD, NetBSD and coreboot. More information can be found on FOSDEM's own page for the talk, including a video recording and slides. Separate from Holger's talk, however, there were a number of other talks about reproducible builds at FOSDEM this year: Reproducible builds for confidential computing: Why remote attestation is worthless without it by Malte Poll and Paul Meyer. RISC-V Bootstrapping in Guix and Live-Bootstrap by Ekaitz. rix: an R package for reproducible dev environments with Nix by Bruno Rodrigues. Making reproducible and publishable large-scale HPC experiments by Philippe Swartvagher. Documenting and Fixing Non-Reproducible Builds due to Configuration Options by RANDRIANAINA Georges Aaron. ... and there was even an entire track on Software Bill of Materials.

## Farewell from the Reproducible Builds Summit 2023!

DevFeed: [Farewell from the Reproducible Builds Summit 2023!](<https://devfeed.tech/articles/farewell-from-the-reproducible-builds-summit-2023-34157.md>)

Original publisher: [Read original article](<https://reproducible-builds.org/news/2023/11/02/farewell-from-the-reproducible-builds-summit-2023/>)

Published: 2023-11-02T00:00:00Z

Content type: news

Language: en

Sources: [Reproducible Builds](<https://devfeed.tech/sources/reproducible-builds-org.md>)

Topics: [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [reproducibility](<https://devfeed.tech/topics/reproducibility.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Embedded Systems](<https://devfeed.tech/topics/embedded-systems.md>)

Tags: [adb](<https://devfeed.tech/tags/adb.md>), [apache](<https://devfeed.tech/tags/apache.md>), [buildroot](<https://devfeed.tech/tags/buildroot.md>), [builds](<https://devfeed.tech/tags/builds.md>), [coreboot](<https://devfeed.tech/tags/coreboot.md>), [debian](<https://devfeed.tech/tags/debian.md>), [dockerignore-usage](<https://devfeed.tech/tags/dockerignore-usage.md>), [fedora](<https://devfeed.tech/tags/fedora.md>), [germany](<https://devfeed.tech/tags/germany.md>), [github](<https://devfeed.tech/tags/github.md>), [linux](<https://devfeed.tech/tags/linux.md>), [maven](<https://devfeed.tech/tags/maven.md>), [openwrt](<https://devfeed.tech/tags/openwrt.md>), [org](<https://devfeed.tech/tags/org.md>), [reproducibility](<https://devfeed.tech/tags/reproducibility.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [security](<https://devfeed.tech/tags/security.md>), [summit](<https://devfeed.tech/tags/summit.md>), [systemd](<https://devfeed.tech/tags/systemd.md>), [ubuntu](<https://devfeed.tech/tags/ubuntu.md>)

### AI overview

A recap of the seventh Reproducible Builds summit in Hamburg, Germany, covering project updates, reproducibility practices, verification services, filesystem images and containers, package reproducibility, SBOMs, and related discussions.

### Source excerpt

Farewell from the Reproducible Builds summit, which just took place in Hamburg, Germany: This year, we were thrilled to host the seventh edition of this exciting event. Topics covered this year included: Project updates from openSUSE, Fedora, Debian, ElectroBSD, Reproducible Central and NixOS Mapping the "big picture" Towards a snapshot service Understanding user-facing needs and personas Language-specific package managers Defining our definitions Creating a "Ten Commandments" of reproducibility Embedded systems Next steps in GNU Guix' reproducibility Signature storage and sharing Public verification services Verification use cases Web site audiences Enabling new projects to be "born reproducible" Collecting reproducibility success stories Reproducibility's relationship to SBOMs SBOMs for RPM-based distributions Filtering diffoscope output Reproducibility of filesystem images, filesystems and containers Using verification data A deep-dive on Fedora and Arch Linux package reproducibility Debian rebuild archive service discussion ... as well as countless informal discussions and hacking sessions into the night. Projects represented at the venue included: Debian, openSUSE, QubesOS, GNU Guix, Arch Linux, phosh, Mobian, PureOS, JustBuild, LibreOffice, Warpforge, OpenWrt, F-Droid, NixOS, ElectroBSD, Apache Security, Buildroot, Systemd, Apache Maven, Fedora, Privoxy, CHAINS (KTH Royal Institute of Technology), coreboot, GitHub, Tor Project, Ubuntu, rebuilderd, repro-env, spytrap-adb, arch-repro-status, etc. A huge thanks to our sponsors and partners for making the event possible: Event facilitation Platinum sponsor If you weren't able to make it this year, don't worry; just look out for an announcement in 2024 for the next event.

## Blog: How we Sign and Verify Falco Plugins and Rules

DevFeed: [Blog: How we Sign and Verify Falco Plugins and Rules](<https://devfeed.tech/articles/blog-how-we-sign-and-verify-falco-plugins-and-rules-32523.md>)

Original publisher: [Read original article](<https://falco.org/blog/sign-verify-plugins-rules/>)

Published: 2023-10-18T00:00:00Z

Content type: article

Language: en

Sources: [Falco](<https://devfeed.tech/sources/falco-falco.md>)

Topics: [Falco](<https://devfeed.tech/topics/falco.md>), [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>), [open-source-security](<https://devfeed.tech/topics/open-source-security.md>), [Security](<https://devfeed.tech/topics/security.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [branch-protection-rules](<https://devfeed.tech/tags/branch-protection-rules.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [falco](<https://devfeed.tech/tags/falco.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [rules](<https://devfeed.tech/tags/rules.md>), [security](<https://devfeed.tech/tags/security.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>)

### AI overview

This article explains how Falco v0.36.0, falcoctl 0.6.1, and the 0.7.0 Helm chart improve the security of Falco plugins and rule sets. It describes their OCI-based distribution and discusses safeguards against software supply chain attacks, including signing, verification, branch protection, code review, reproducible builds, dependency pinning, build isolation, and MFA.

### Source excerpt

Falco v0.36.0 and the Software Supply Chain (SSC) security The latest stable Falco release, v0.36.0, alongside falcoctl 0.6.1 and the 0.7.0 Helm chart introduced new features and improvements to the security of Falco's software supply chain artifacts. Falco's two main downloadable artifacts are plugins and rule sets. They're shipped in the OCI specification format and distributed through the official Falcosecurity OCI repositories. Software supply chain attacks aim at injecting malicious code into software components, to compromise downstream users. These types of attacks are among the primary threats in today's threat landscape. In particular, attackers abuse trust relationships existing between the different open-source stakeholders. The increase in attacks on open-source software throughout the last few years demonstrates that attackers consider them a viable means for spreading malware. SSC safeguards Securing the software supply chain may seem daunting at first glance, but there are a lot of safeguards that can be put in action. And there are ways to categorize them, and ways to prioritize them. Safeguards against supply chain attacks can be classified by control type: directive, preventive, detective, corrective, and recovery. But there ain't no such thing as a free lunch. Besides safeguard classifications, the utility-to-cost ratio can also be an important factor in deciding where to start in improving the supply chain security of software, and can be pretty easy to measure it. There are cheap preventive safeguards that can be implemented in open source projects especially, where stakeholders platea can be pretty wide considering the contributions. For example, branch protection rules are usually simple per-code repository configurations in providers (e.g. GitHub) and alongside pull request-based flows enforcing code review quorum, are also standard best practices nowadays. The same applies to reproducible builds, dependency pinning, build steps isolation, MF

## DebConf23 closes in Kochi and DebConf24 announced

DevFeed: [DebConf23 closes in Kochi and DebConf24 announced](<https://devfeed.tech/articles/debconf23-closes-in-kochi-and-debconf24-announced-47040.md>)

Original publisher: [Read original article](<https://bits.debian.org/2023/09/debconf23-closes.html>)

Author: Jean-Pierre Giraud and Donald Norwood

Published: 2023-09-18T14:30:00Z

Content type: news

Language: en

Sources: [Bits from Debian](<https://devfeed.tech/sources/bits-from-debian.md>)

Topics: [Debian](<https://devfeed.tech/topics/debian.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [Python](<https://devfeed.tech/topics/python.md>), [Perl](<https://devfeed.tech/topics/perl.md>), [Ruby](<https://devfeed.tech/topics/ruby.md>)

Tags: [2023](<https://devfeed.tech/tags/2023.md>), [announce](<https://devfeed.tech/tags/announce.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [conference](<https://devfeed.tech/tags/conference.md>), [debconf](<https://devfeed.tech/tags/debconf.md>), [debconf23](<https://devfeed.tech/tags/debconf23.md>), [debconf24](<https://devfeed.tech/tags/debconf24.md>), [debian](<https://devfeed.tech/tags/debian.md>), [developers](<https://devfeed.tech/tags/developers.md>), [events](<https://devfeed.tech/tags/events.md>), [newcomers](<https://devfeed.tech/tags/newcomers.md>), [perl](<https://devfeed.tech/tags/perl.md>), [programming](<https://devfeed.tech/tags/programming.md>), [python](<https://devfeed.tech/tags/python.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [ruby](<https://devfeed.tech/tags/ruby.md>)

### AI overview

DebConf23 concluded in Kochi after bringing together Debian developers and contributors for talks, discussions, workshops, team sprints, and community activities. The event included work on Mobian/Debian, Reproducible Builds, Python in Debian, and updates from several Debian technical teams.

### Source excerpt

On Sunday 17 September 2023, the annual Debian Developers and Contributors Conference came to a close. Over 474 attendees representing 35 countries from around the world came together for a combined 89 events made up of Talks, Discussons, Birds of a Feather (BoF) gatherings, workshops, and activities in support of furthering our distribution, learning from our mentors and peers, building our community, and having a bit of fun. The conference was preceded by the annual DebCamp hacking session held September 3d through September 9th where Debian Developers and Contributors convened to focus on their Individual Debian related projects or work in team sprints geared toward in-person collaboration in developing Debian. In particular this year Sprints took place to advance development in Mobian/Debian, Reproducible Builds, and Python in Debian. This year also featured a BootCamp that was held for newcomers staged by a team of dedicated mentors who shared hands-on experience in Debian and offered a deeper understanding of how to work in and contribute to the community. The actual Debian Developers Conference started on Sunday 10 September 2023. In addition to the traditional 'Bits from the DPL' talk, the continuous key-signing party, lightning talks and the announcement of next year's DebConf4, there were several update sessions shared by internal projects and teams. Many of the hosted discussion sessions were presented by our technical teams who highlighted the work and focus of the Long Term Support (LTS), Android tools, Debian Derivatives, Debian Installer, Debian Image, and the Debian Science teams. The Python, Perl, and Ruby programming language teams also shared updates on their work and efforts. Two of the larger local Debian communities, Debian Brasil and Debian India shared how their respective collaborations in Debian moved the project forward and how they attracted new members and opportunities both in Debian, F/OSS, and the sciences with their HowTos of demonst

[Next page](<https://devfeed.tech/topics/reproducible-builds.md?cursor=WyIyMDIzLTA5LTE4VDE0OjMwOjAwKzAwOjAwIiwgIjA1MThiMThmLTkxZWYtNDlhNi1iYzJmLWE4NmM5YjVlOGY4ZiJd>)