There is 1 open security issue in sid.
There is 1 open security issue in forky.
commit 81dc135e5231cbbdfc7deb55e603a33e5acd43a5
Author: Yadd <yadd@debian.org>
Date: Wed Feb 11 07:57:00 2026 +0100
Add SINGLE_USCAN_TEST env var to be able to test only one test/t/uscan/* test
commit 9804fdcb7b7fd47430d0d88d622b5a67b979bac0
Author: Yadd <yadd@debian.org>
Date: Wed Feb 11 07:47:58 2026 +0100
autopkgtest: skip metacpan test if test version mismatch upstream version
commit f8d9297cc313c4a15bab432287f1f52433e68a7f
Author: Yadd <yadd@debian.org>
Date: Wed Feb 11 07:03:41 2026 +0100
Udpate metacpan version to fix autopkgtest
commit 990794d68d3979da194bdb2f6a6dc692d2327c55
Author: Daniel Gröber <dxld@darkboxed.org>
Date: Mon Feb 2 15:54:48 2026 +0100
bts: Fix Message-ID header missing "@" (Closes: #1126848)
See https://datatracker.ietf.org/doc/html/rfc2822#section-3.6.4
commit b15e7e96ea9fa71ac42736edfcde86207367ae3d
Author: Yadd <yadd@debian.org>
Date: Tue Feb 3 21:32:00 2026 +0100
Update French translation
commit 804a6339d4c404267520ba5f338a28c87ead4d1b
Author: Holger Levsen <holger@layer-acht.org>
Date: Thu Jan 29 13:00:22 2026 +0100
Update Portuguese translation, thanks to Américo Monteiro. Closes: #1126583
commit 121faff28d3919b73b885cdc2e9034bf7de847af
Merge: dda4f69a2 6f7296856
Author: Yadd <yadd@debian.org>
Date: Tue Jan 27 08:05:46 2026 +0100
Merge remote-tracking branch 'tmp1/salsa-token-dot'
commit dda4f69a29ca91565d3fcad49f479ceacd73c47d
Author: Yadd <yadd@debian.org>
Date: Tue Jan 27 08:05:09 2026 +0100
Partial Fr translation
Gbp-Dch: ignore
commit 167a2f96d8634c724d86c031c874b6e044677a27
Merge: 8f2685c85 83f0bff88
Author: Yadd <yadd@debian.org>
Date: Tue Jan 27 07:45:28 2026 +0100
Merge remote-tracking branch 'origin/salsaforksalsafork'
commit 83f0bff887ee14ea9ac4df6759c821a256bf87c7
Author: Jérémy Lal <kapouer@melix.org>
Date: Mon Dec 8 00:00:13 2025 +0100
Update devscripts.pot
commit 8446c22a5d4f970151980937ce14d61fcdfcf1e8
Author: Jérémy Lal <kapouer@melix.org>
Date: Sun Dec 7 23:59:50 2025 +0100
Fix stuttering in salsa fork doc
commit 6f7296856e04e6e6456320883477c50807d54298
Author: Nicolas Schodet <nico@ni.fr.eu.org>
Date: Sat Dec 27 00:38:06 2025 +0100
salsa: accept dots in token when using a token file
commit 8f2685c8566f6c78193520b4fda87c831f33565c
Author: Dmitry Shachnev <mitya57@debian.org>
Date: Sun Jan 4 21:52:42 2026 +0300
uscan: Add ~ to the version for PyPI pre-releases
commit 89871ab623b4c8cc33ee471c7a59599b89fb57e6
Author: Dmitry Shachnev <mitya57@debian.org>
Date: Sun Jan 4 21:50:49 2026 +0300
uscan: Remove unused test file
Gbp-Dch: ignore
commit 892e72b27db0056c6a9bc6046039489c7ff32625
Author: Arnaud Rebillout <arnaudr@debian.org>
Date: Tue Dec 30 11:16:40 2025 +0700
uscan: Prefer Dist keyword when updating d/watch to v5 (GitHub template)
Before this commit, a watch file for a GitHub project was updated to:
Version: 5
Template: GitHub
Owner: foo
Project: bar
After this commit:
Version: 5
Template: GitHub
Dist: https://github.com/foo/bar
It's surely a matter of taste, so let me argue in favor of the second
form:
* it is more concise
* it shows the URL of the repo: one can just copy/paste it, grep for it,
click on it, etc... It is more useful than having Owner and Project
listed on two separate fields.
commit 4bd0c7f008640030cd2b231146585d542fff591e
Author: Arnaud Rebillout <arnaudr@debian.org>
Date: Wed Dec 17 14:32:07 2025 +0700
uscan: Formatting nitpicks in Version4.pm
It seems more readable to have one assignment per line, and it's how
it's done for other templates.
commit 525012025750beb8be74b5cf35dd32776352baae
Author: Holger Levsen <holger@layer-acht.org>
Date: Sun Jan 18 12:54:35 2026 +0100
Start 2.26.6 development.
d/changelog entries will be written on release
using the git commit messages.
Use 'gbp dch --since v2.26.5 --multimaint-merge'
to write d/changelog entries since that last release.
Gbp-Dch: ignore
Signed-off-by: Holger Levsen <holger@layer-acht.org>
There is 1 open security issue in trixie.
You can find information about how to handle this issue in the security team's documentation.
There is 1 open security issue in bookworm.
You can find information about how to handle this issue in the security team's documentation.
Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.
Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/d/devscripts.png){kind=link}