#reproducible — Public Fediverse posts

Hi All Nix, Guix users

I want a better term to address #nix, #guix, #lix etc
Coz whenever I mention something about Nix's benefits etc , I also mean guix, lix too
So I'm hunting for a better term to address things in common.
Coz Nix(and it's family is),
#Declarative, #idempotent, #bit2bit #reproducible, #Immutable, #hermetic, #provenant, pure #functional, #incremental, #Atomic etc etc

The terms I came up with are
#Congruent eng, #Invariant eng, Pure Functional Eng.
🧵

#nixos #guixos

Hi All Nix, Guix users

I want a better term to address #nix, #guix, #lix etc
Coz whenever I mention something about Nix's benefits etc , I also mean guix, lix too
So I'm hunting for a better term to address things in common.
Coz Nix(and it's family is),
#Declarative, #idempotent, #bit2bit #reproducible, #Immutable, #hermetic, #provenant, pure #functional, #incremental, #Atomic etc etc

The terms I came up with are
#Congruent eng, #Invariant eng, Pure Functional Eng.
🧵

#nixos #guixos

Hi All Nix, Guix users

I want a better term to address #nix, #guix, #lix etc
Coz whenever I mention something about Nix's benefits etc , I also mean guix, lix too
So I'm hunting for a better term to address things in common.
Coz Nix(and it's family is),
#Declarative, #idempotent, #bit2bit #reproducible, #Immutable, #hermetic, #provenant, pure #functional, #incremental, #Atomic etc etc

The terms I came up with are
#Congruent eng, #Invariant eng, Pure Functional Eng.
🧵

#nixos #guixos

Hi All Nix, Guix users

I want a better term to address #nix, #guix, #lix etc
Coz whenever I mention something about Nix's benefits etc , I also mean guix, lix too
So I'm hunting for a better term to address things in common.
Coz Nix(and it's family is),
#Declarative, #idempotent, #bit2bit #reproducible, #Immutable, #hermetic, #provenant, pure #functional, #incremental, #Atomic etc etc

The terms I came up with are
#Congruent eng, #Invariant eng, Pure Functional Eng.
🧵

#nixos #guixos

Hi All Nix, Guix users

I want a better term to address #nix, #guix, #lix etc
Coz whenever I mention something about Nix's benefits etc , I also mean guix, lix too
So I'm hunting for a better term to address things in common.
Coz Nix(and it's family is),
#Declarative, #idempotent, #bit2bit #reproducible, #Immutable, #hermetic, #provenant, pure #functional, #incremental, #Atomic etc etc

The terms I came up with are
#Congruent eng, #Invariant eng, Pure Functional Eng.
🧵

#nixos #guixos

📢 Next up at R-Ladies Rome!
Typst for Efficient Typesetting with Derek Sollberger (@Princeton)
Discover how Typst + Quarto, publication-quality PDFs—without the complexity of LaTeX.
📅 Registration: https://luma.com/k9bw4g7e
#RLadiesRome #RStats #Typst #Quarto #Reproducible

📢 Next up at R-Ladies Rome!
Typst for Efficient Typesetting with Derek Sollberger (@Princeton)
Discover how Typst + Quarto, publication-quality PDFs—without the complexity of LaTeX.
📅 Registration: https://luma.com/k9bw4g7e
#RLadiesRome #RStats #Typst #Quarto #Reproducible

📢 Next up at R-Ladies Rome!
Typst for Efficient Typesetting with Derek Sollberger (@Princeton)
Discover how Typst + Quarto, publication-quality PDFs—without the complexity of LaTeX.
📅 Registration: https://luma.com/k9bw4g7e
#RLadiesRome #RStats #Typst #Quarto #Reproducible

📢 Next up at R-Ladies Rome!
Typst for Efficient Typesetting with Derek Sollberger (@Princeton)
Discover how Typst + Quarto, publication-quality PDFs—without the complexity of LaTeX.
📅 Registration: https://luma.com/k9bw4g7e
#RLadiesRome #RStats #Typst #Quarto #Reproducible

📢 Next up at R-Ladies Rome!
Typst for Efficient Typesetting with Derek Sollberger (@Princeton)
Discover how Typst + Quarto, publication-quality PDFs—without the complexity of LaTeX.
📅 Registration: https://luma.com/k9bw4g7e
#RLadiesRome #RStats #Typst #Quarto #Reproducible

Just finished listening to the first episode of @Felienne and Hanna Schraffenberger’s #podcast CS off course:

https://rss.com/podcasts/computer-science-off-course/2968986/

What stuck most: how tools for building #software are designed to build but not to keep track of the thought process.
This would also be a way to make CS output truly #reproducible. I love the idea of having an atlas type annotation tool. Testing would be more involved, metrics for #reproducibility of #researchsoftware are still illdefined.

Just finished listening to the first episode of @Felienne and Hanna Schraffenberger’s #podcast CS off course:

https://rss.com/podcasts/computer-science-off-course/2968986/

What stuck most: how tools for building #software are designed to build but not to keep track of the thought process.
This would also be a way to make CS output truly #reproducible. I love the idea of having an atlas type annotation tool. Testing would be more involved, metrics for #reproducibility of #researchsoftware are still illdefined.

Just finished listening to the first episode of @Felienne and Hanna Schraffenberger’s #podcast CS off course:

https://rss.com/podcasts/computer-science-off-course/2968986/

What stuck most: how tools for building #software are designed to build but not to keep track of the thought process.
This would also be a way to make CS output truly #reproducible. I love the idea of having an atlas type annotation tool. Testing would be more involved, metrics for #reproducibility of #researchsoftware are still illdefined.

Just finished listening to the first episode of @Felienne and Hanna Schraffenberger’s #podcast CS off course:

https://rss.com/podcasts/computer-science-off-course/2968986/

What stuck most: how tools for building #software are designed to build but not to keep track of the thought process.
This would also be a way to make CS output truly #reproducible. I love the idea of having an atlas type annotation tool. Testing would be more involved, metrics for #reproducibility of #researchsoftware are still illdefined.

Just finished listening to the first episode of @Felienne and Hanna Schraffenberger’s #podcast CS off course:

https://rss.com/podcasts/computer-science-off-course/2968986/

What stuck most: how tools for building #software are designed to build but not to keep track of the thought process.
This would also be a way to make CS output truly #reproducible. I love the idea of having an atlas type annotation tool. Testing would be more involved, metrics for #reproducibility of #researchsoftware are still illdefined.

Bugs were squashed and #reproducible (?) pizza was baked in Darmstadt at the #NixOS 26.05 bug squashing party. Doesn't that look delicious?

Bugs were squashed and #reproducible (?) pizza was baked in Darmstadt at the #NixOS 26.05 bug squashing party. Doesn't that look delicious?

Bugs were squashed and #reproducible (?) pizza was baked in Darmstadt at the #NixOS 26.05 bug squashing party. Doesn't that look delicious?

Bugs were squashed and #reproducible (?) pizza was baked in Darmstadt at the #NixOS 26.05 bug squashing party. Doesn't that look delicious?

Bugs were squashed and #reproducible (?) pizza was baked in Darmstadt at the #NixOS 26.05 bug squashing party. Doesn't that look delicious?

I've just updated the Reproducible project template repo based on a few small #reproducible research websites I've needed to create. This workflow is now my default for doing talks and workshops, quicker than PowerPoint with many benefits! Details: http://robinlovelace.net/reproducible-project-template/

I've just updated the Reproducible project template repo based on a few small #reproducible research websites I've needed to create. This workflow is now my default for doing talks and workshops, quicker than PowerPoint with many benefits! Details: http://robinlovelace.net/reproducible-project-template/

I've just updated the Reproducible project template repo based on a few small #reproducible research websites I've needed to create. This workflow is now my default for doing talks and workshops, quicker than PowerPoint with many benefits! Details: http://robinlovelace.net/reproducible-project-template/

I've just updated the Reproducible project template repo based on a few small #reproducible research websites I've needed to create. This workflow is now my default for doing talks and workshops, quicker than PowerPoint with many benefits! Details: http://robinlovelace.net/reproducible-project-template/

I've just updated the Reproducible project template repo based on a few small #reproducible research websites I've needed to create. This workflow is now my default for doing talks and workshops, quicker than PowerPoint with many benefits! Details: http://robinlovelace.net/reproducible-project-template/

Listening to Bernhard M. Wiedemann talking at #oSC26 about:

What happened with #reproducible #builds in @opensuse and #SLES

https://events.opensuse.org/conferences/oSC26/program/proposals/5089

Once upon a time the syslog-ng project also did a couple of changes to allow reproducible builds (no timestamp or git hash).

Listening to Bernhard M. Wiedemann talking at #oSC26 about:

What happened with #reproducible #builds in @opensuse and #SLES

https://events.opensuse.org/conferences/oSC26/program/proposals/5089

Once upon a time the syslog-ng project also did a couple of changes to allow reproducible builds (no timestamp or git hash).

Listening to Bernhard M. Wiedemann talking at #oSC26 about:

What happened with #reproducible #builds in @opensuse and #SLES

https://events.opensuse.org/conferences/oSC26/program/proposals/5089

Once upon a time the syslog-ng project also did a couple of changes to allow reproducible builds (no timestamp or git hash).

Listening to Bernhard M. Wiedemann talking at #oSC26 about:

What happened with #reproducible #builds in @opensuse and #SLES

https://events.opensuse.org/conferences/oSC26/program/proposals/5089

Once upon a time the syslog-ng project also did a couple of changes to allow reproducible builds (no timestamp or git hash).

Listening to Bernhard M. Wiedemann talking at #oSC26 about:

What happened with #reproducible #builds in @opensuse and #SLES

https://events.opensuse.org/conferences/oSC26/program/proposals/5089

Once upon a time the syslog-ng project also did a couple of changes to allow reproducible builds (no timestamp or git hash).

📣 The Turing Way’s June Community Forum!

Join our second Community Forum of 2026:
🗓 25th June 2026
⏰ 5:00 PM (UK), 6:00 PM (Central Europe), 12:00 PM (Eastern US), 9:00 AM (Western US)

🔍 What to expect:
- Insights from our working groups and projects
- Highlights from our steering committee
- A focused discussion on our work with JupyterHub

👉 Register here: https://forms.gle/GapNn9Vx8aMz8o6A7

Let’s come together to share, learn, and shape what’s next 🚀

#openscience #openresearch #reproducible

📣 The Turing Way’s June Community Forum!

Join our second Community Forum of 2026:
🗓 25th June 2026
⏰ 5:00 PM (UK), 6:00 PM (Central Europe), 12:00 PM (Eastern US), 9:00 AM (Western US)

🔍 What to expect:
- Insights from our working groups and projects
- Highlights from our steering committee
- A focused discussion on our work with JupyterHub

👉 Register here: https://forms.gle/GapNn9Vx8aMz8o6A7

Let’s come together to share, learn, and shape what’s next 🚀

#openscience #openresearch #reproducible

📣 The Turing Way’s June Community Forum!

Join our second Community Forum of 2026:
🗓 25th June 2026
⏰ 5:00 PM (UK), 6:00 PM (Central Europe), 12:00 PM (Eastern US), 9:00 AM (Western US)

🔍 What to expect:
- Insights from our working groups and projects
- Highlights from our steering committee
- A focused discussion on our work with JupyterHub

👉 Register here: https://forms.gle/GapNn9Vx8aMz8o6A7

Let’s come together to share, learn, and shape what’s next 🚀

#openscience #openresearch #reproducible

📣 The Turing Way’s June Community Forum!

Join our second Community Forum of 2026:
🗓 25th June 2026
⏰ 5:00 PM (UK), 6:00 PM (Central Europe), 12:00 PM (Eastern US), 9:00 AM (Western US)

🔍 What to expect:
- Insights from our working groups and projects
- Highlights from our steering committee
- A focused discussion on our work with JupyterHub

👉 Register here: https://forms.gle/GapNn9Vx8aMz8o6A7

Let’s come together to share, learn, and shape what’s next 🚀

#openscience #openresearch #reproducible

📣 The Turing Way’s June Community Forum!

Join our second Community Forum of 2026:
🗓 25th June 2026
⏰ 5:00 PM (UK), 6:00 PM (Central Europe), 12:00 PM (Eastern US), 9:00 AM (Western US)

🔍 What to expect:
- Insights from our working groups and projects
- Highlights from our steering committee
- A focused discussion on our work with JupyterHub

👉 Register here: https://forms.gle/GapNn9Vx8aMz8o6A7

Let’s come together to share, learn, and shape what’s next 🚀

#openscience #openresearch #reproducible

Great to be in #Estonia again! I'm here for the #MobileTartu conference and will be teaching Data Science for Transport Planning. For anyone unable to make it in person but interested in the topic, you can follow the #openaccess materials here: https://tdscience.github.io/tartu26/ #reproducible #datascience

Great to be in #Estonia again! I'm here for the #MobileTartu conference and will be teaching Data Science for Transport Planning. For anyone unable to make it in person but interested in the topic, you can follow the #openaccess materials here: https://tdscience.github.io/tartu26/ #reproducible #datascience

Great to be in #Estonia again! I'm here for the #MobileTartu conference and will be teaching Data Science for Transport Planning. For anyone unable to make it in person but interested in the topic, you can follow the #openaccess materials here: https://tdscience.github.io/tartu26/ #reproducible #datascience

Great to be in #Estonia again! I'm here for the #MobileTartu conference and will be teaching Data Science for Transport Planning. For anyone unable to make it in person but interested in the topic, you can follow the #openaccess materials here: https://tdscience.github.io/tartu26/ #reproducible #datascience

Great to be in #Estonia again! I'm here for the #MobileTartu conference and will be teaching Data Science for Transport Planning. For anyone unable to make it in person but interested in the topic, you can follow the #openaccess materials here: https://tdscience.github.io/tartu26/ #reproducible #datascience

Learn how to use Go Modules for effective dependency management, version control, and reproducible builds in Go projects. Master best practices for initializing, managing, and securing Go modules in modern development workflows.

#Go Modules #dependency management #semantic versioning #Go 1.22 #reproducible builds

https://dasroot.net/posts/2026/02/go-modules-managing-dependencies/

Learn how to use Go Modules for effective dependency management, version control, and reproducible builds in Go projects. Master best practices for initializing, managing, and securing Go modules in modern development workflows.

#Go Modules #dependency management #semantic versioning #Go 1.22 #reproducible builds

https://dasroot.net/posts/2026/02/go-modules-managing-dependencies/

Learn how to use Go Modules for effective dependency management, version control, and reproducible builds in Go projects. Master best practices for initializing, managing, and securing Go modules in modern development workflows.

#Go Modules #dependency management #semantic versioning #Go 1.22 #reproducible builds

https://dasroot.net/posts/2026/02/go-modules-managing-dependencies/

Learn how to use Go Modules for effective dependency management, version control, and reproducible builds in Go projects. Master best practices for initializing, managing, and securing Go modules in modern development workflows.

#Go Modules #dependency management #semantic versioning #Go 1.22 #reproducible builds

https://dasroot.net/posts/2026/02/go-modules-managing-dependencies/

Learn how to use Go Modules for effective dependency management, version control, and reproducible builds in Go projects. Master best practices for initializing, managing, and securing Go modules in modern development workflows.

#Go Modules #dependency management #semantic versioning #Go 1.22 #reproducible builds

https://dasroot.net/posts/2026/02/go-modules-managing-dependencies/

Dear opensource developers,

I added an "adoption" list to the repro-env README, if you publish pre-compiled binaries and you successfully adopted it to allow anyone to reproduce them from source code to prove the absense of a build server compromise, you are very welcome to add yourself to the list. 😺

https://github.com/kpcyrd/repro-env#adoption

#reproducible #reproduciblebuilds #supplychainsecurity #rust

Dear opensource developers,

I added an "adoption" list to the repro-env README, if you publish pre-compiled binaries and you successfully adopted it to allow anyone to reproduce them from source code to prove the absense of a build server compromise, you are very welcome to add yourself to the list. 😺

https://github.com/kpcyrd/repro-env#adoption

#reproducible #reproduciblebuilds #supplychainsecurity #rust

Dear opensource developers,

I added an "adoption" list to the repro-env README, if you publish pre-compiled binaries and you successfully adopted it to allow anyone to reproduce them from source code to prove the absense of a build server compromise, you are very welcome to add yourself to the list. 😺

https://github.com/kpcyrd/repro-env#adoption

#reproducible #reproduciblebuilds #supplychainsecurity #rust

Dear opensource developers,

I added an "adoption" list to the repro-env README, if you publish pre-compiled binaries and you successfully adopted it to allow anyone to reproduce them from source code to prove the absense of a build server compromise, you are very welcome to add yourself to the list. 😺

https://github.com/kpcyrd/repro-env#adoption

#reproducible #reproduciblebuilds #supplychainsecurity #rust

Dear opensource developers,

I added an "adoption" list to the repro-env README, if you publish pre-compiled binaries and you successfully adopted it to allow anyone to reproduce them from source code to prove the absense of a build server compromise, you are very welcome to add yourself to the list. 😺

https://github.com/kpcyrd/repro-env#adoption

#reproducible #reproduciblebuilds #supplychainsecurity #rust

https://blog.gslin.org/archives/2026/05/11/13035/debian-%e4%b8%8b%e4%b8%80%e7%89%88-forky-%e5%b0%87%e6%9c%83%e5%bc%b7%e5%88%b6%e8%a6%81%e6%b1%82-reproducible-packaging/

Debian 下一版 (forky) 將會強制要求 reproducible packaging

#build #chain #debian #integrity #linux #package #packaging #reproducible #security #software #trust

https://blog.gslin.org/archives/2026/05/11/13035/debian-%e4%b8%8b%e4%b8%80%e7%89%88-forky-%e5%b0%87%e6%9c%83%e5%bc%b7%e5%88%b6%e8%a6%81%e6%b1%82-reproducible-packaging/

Debian 下一版 (forky) 將會強制要求 reproducible packaging

#build #chain #debian #integrity #linux #package #packaging #reproducible #security #software #trust

https://blog.gslin.org/archives/2026/05/11/13035/debian-%e4%b8%8b%e4%b8%80%e7%89%88-forky-%e5%b0%87%e6%9c%83%e5%bc%b7%e5%88%b6%e8%a6%81%e6%b1%82-reproducible-packaging/

Debian 下一版 (forky) 將會強制要求 reproducible packaging

#build #chain #debian #integrity #linux #package #packaging #reproducible #security #software #trust

https://blog.gslin.org/archives/2026/05/11/13035/debian-%e4%b8%8b%e4%b8%80%e7%89%88-forky-%e5%b0%87%e6%9c%83%e5%bc%b7%e5%88%b6%e8%a6%81%e6%b1%82-reproducible-packaging/

Debian 下一版 (forky) 將會強制要求 reproducible packaging

#build #chain #debian #integrity #linux #package #packaging #reproducible #security #software #trust

https://blog.gslin.org/archives/2026/05/11/13035/debian-%e4%b8%8b%e4%b8%80%e7%89%88-forky-%e5%b0%87%e6%9c%83%e5%bc%b7%e5%88%b6%e8%a6%81%e6%b1%82-reproducible-packaging/

Debian 下一版 (forky) 將會強制要求 reproducible packaging

#build #chain #debian #integrity #linux #package #packaging #reproducible #security #software #trust

Debian 14 will only contain reproducible packages

Reproducible builds are a set of rules that apply to software development, including applications and libraries, to create a verifiable path from the source code to the binary code. It allows you to build the library or the application bit-for-bit. Reproducible builds tend to have great features, including, but not limited to:

• Security and trust: Allows third-parties to make sure that the software hasn’t been altered or tampered with.
• Transparency in development: Makes sure that developers’ code always works the same way.
• Resilience against attacks: Allows third-parties to verify the developers’ software to prevent your projects from being compromised.

Half way through the development cycle of the upcoming Debian release expected in 2027, Debian 14 Forky, the Debian release team has made a decision regarding the reproducible builds effort. Over the years with the Reproducible Builds effort that makes sure that packages get built consistently bit-for-bit, the Debian release team has decided that reproducible builds must be satisfied for the Debian packages to be approved.

A new mandate for Debian 14 Forky states that the reproducible packages, which are packages that build consistently and with confidence bit-for-bit, must be shipped. The migration software will reject the package addition or update if said package no longer becomes reproducible.

The Debian release team has also provided a link that allows you to check the package reproducibility status for the upcoming version of Debian via https://reproduce.debian.net/.

Via: Phoronix

Debian 14 will only contain reproducible packages

Reproducible builds are a set of rules that apply to software development, including applications and libraries, to create a verifiable path from the source code to the binary code. It allows you to build the library or the application bit-for-bit. Reproducible builds tend to have great features, including, but not limited to:

• Security and trust: Allows third-parties to make sure that the software hasn’t been altered or tampered with.
• Transparency in development: Makes sure that developers’ code always works the same way.
• Resilience against attacks: Allows third-parties to verify the developers’ software to prevent your projects from being compromised.

Half way through the development cycle of the upcoming Debian release expected in 2027, Debian 14 Forky, the Debian release team has made a decision regarding the reproducible builds effort. Over the years with the Reproducible Builds effort that makes sure that packages get built consistently bit-for-bit, the Debian release team has decided that reproducible builds must be satisfied for the Debian packages to be approved.

A new mandate for Debian 14 Forky states that the reproducible packages, which are packages that build consistently and with confidence bit-for-bit, must be shipped. The migration software will reject the package addition or update if said package no longer becomes reproducible.

The Debian release team has also provided a link that allows you to check the package reproducibility status for the upcoming version of Debian via https://reproduce.debian.net/.

Via: Phoronix

Debian 14 will only contain reproducible packages

Reproducible builds are a set of rules that apply to software development, including applications and libraries, to create a verifiable path from the source code to the binary code. It allows you to build the library or the application bit-for-bit. Reproducible builds tend to have great features, including, but not limited to:

• Security and trust: Allows third-parties to make sure that the software hasn’t been altered or tampered with.
• Transparency in development: Makes sure that developers’ code always works the same way.
• Resilience against attacks: Allows third-parties to verify the developers’ software to prevent your projects from being compromised.

Half way through the development cycle of the upcoming Debian release expected in 2027, Debian 14 Forky, the Debian release team has made a decision regarding the reproducible builds effort. Over the years with the Reproducible Builds effort that makes sure that packages get built consistently bit-for-bit, the Debian release team has decided that reproducible builds must be satisfied for the Debian packages to be approved.

A new mandate for Debian 14 Forky states that the reproducible packages, which are packages that build consistently and with confidence bit-for-bit, must be shipped. The migration software will reject the package addition or update if said package no longer becomes reproducible.

The Debian release team has also provided a link that allows you to check the package reproducibility status for the upcoming version of Debian via https://reproduce.debian.net/.

Via: Phoronix

Debian 14 will only contain reproducible packages

Reproducible builds are a set of rules that apply to software development, including applications and libraries, to create a verifiable path from the source code to the binary code. It allows you to build the library or the application bit-for-bit. Reproducible builds tend to have great features, including, but not limited to:

• Security and trust: Allows third-parties to make sure that the software hasn’t been altered or tampered with.
• Transparency in development: Makes sure that developers’ code always works the same way.
• Resilience against attacks: Allows third-parties to verify the developers’ software to prevent your projects from being compromised.

Half way through the development cycle of the upcoming Debian release expected in 2027, Debian 14 Forky, the Debian release team has made a decision regarding the reproducible builds effort. Over the years with the Reproducible Builds effort that makes sure that packages get built consistently bit-for-bit, the Debian release team has decided that reproducible builds must be satisfied for the Debian packages to be approved.

A new mandate for Debian 14 Forky states that the reproducible packages, which are packages that build consistently and with confidence bit-for-bit, must be shipped. The migration software will reject the package addition or update if said package no longer becomes reproducible.

The Debian release team has also provided a link that allows you to check the package reproducibility status for the upcoming version of Debian via https://reproduce.debian.net/.

Via: Phoronix

Debian 14 will only contain reproducible packages

Reproducible builds are a set of rules that apply to software development, including applications and libraries, to create a verifiable path from the source code to the binary code. It allows you to build the library or the application bit-for-bit. Reproducible builds tend to have great features, including, but not limited to:

• Security and trust: Allows third-parties to make sure that the software hasn’t been altered or tampered with.
• Transparency in development: Makes sure that developers’ code always works the same way.
• Resilience against attacks: Allows third-parties to verify the developers’ software to prevent your projects from being compromised.

Half way through the development cycle of the upcoming Debian release expected in 2027, Debian 14 Forky, the Debian release team has made a decision regarding the reproducible builds effort. Over the years with the Reproducible Builds effort that makes sure that packages get built consistently bit-for-bit, the Debian release team has decided that reproducible builds must be satisfied for the Debian packages to be approved.

A new mandate for Debian 14 Forky states that the reproducible packages, which are packages that build consistently and with confidence bit-for-bit, must be shipped. The migration software will reject the package addition or update if said package no longer becomes reproducible.

The Debian release team has also provided a link that allows you to check the package reproducibility status for the upcoming version of Debian via https://reproduce.debian.net/.

Via: Phoronix