Dear maintainer, The reproducibility status of the package commons-exec changed during the continuous testing. See the following notes for more details:
2025-02-17 12:20 https://tests.reproducible-builds.org/debian/unstable/amd64/commons-exec changed from reproducible -> timeout 2025-03-14 15:48 https://tests.reproducible-builds.org/debian/unstable/amd64/commons-exec changed from timeout -> reproducible 2025-04-18 13:02 https://tests.reproducible-builds.org/debian/unstable/amd64/commons-exec changed from reproducible -> timeout 2025-06-09 18:07 https://tests.reproducible-builds.org/debian/unstable/amd64/commons-exec changed from reproducible -> timeout 2025-06-09 18:16 https://tests.reproducible-builds.org/debian/unstable/amd64/commons-exec changed from timeout -> reproducible 2025-06-24 02:30 https://tests.reproducible-builds.org/debian/unstable/amd64/commons-exec changed from reproducible -> timeout 2025-06-24 02:40 https://tests.reproducible-builds.org/debian/unstable/amd64/commons-exec changed from timeout -> reproducible 2025-08-16 15:18 https://tests.reproducible-builds.org/debian/unstable/amd64/commons-exec changed from reproducible -> timeout 2025-08-29 21:03 https://tests.reproducible-builds.org/debian/forky/amd64/commons-exec changed from reproducible -> timeout 2025-09-08 02:34 https://tests.reproducible-builds.org/debian/unstable/amd64/commons-exec changed from timeout -> reproducible 2025-10-14 21:06 https://tests.reproducible-builds.org/debian/forky/amd64/commons-exec changed from timeout -> reproducible 2026-02-05 15:34 https://tests.reproducible-builds.org/debian/unstable/amd64/commons-exec changed from reproducible -> timeout 2026-02-05 15:43 https://tests.reproducible-builds.org/debian/unstable/amd64/commons-exec changed from timeout -> reproducible Feel free to reply to this email if you have questions regarding this automatic notification. -- The Reproducible Builds folks __ This is the maintainer address of Debian's Java team <https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use [email protected] for discussions and questions.
