Hi,
On 19/11/2026 15:31, Sven Hartge wrote:
On 19.11.26 15:19, Sylvain Beucler wrote:
I referenced your upload in our work queue:
https://salsa.debian.org/security-tracker-team/security-tracker/-/
commit/84749e7
A member of the LTS Team should contact you, otherwise I'll try and
check this next week.
Any clear reason why piuparts is failing at:
https://salsa.debian.org/debian/radsecproxy/-/pipelines/1214681
?
That was an error on my part when branching off into bookworm, I still
had the unstable configuration for Salsa-CI. I fixed this in git now. Do
you want me to do another build with this? (The files don't do anything
for the DEB anyway.)
This looks good. I think we'll build the uploaded source package from
Salsa so no need to regen the debdiff just for this.
(also is there a reason to change the prior upload's changelog date in
your debdiff?)
I used the dsc from the archive to create the debdiff, that has a
different date from the sponsored upload than what is in git.
Is this a problem and do you want to change the date in git to match the
one in the archive?
Ideally what's in Salsa matches what's in the archive. But now I guess
it's too late to fix the commit for the 2023 unstable upload, so it
doesn't really matter. Let's just make sure this upcoming upload is in sync.
Cheers!
Sylvain Beucler
Debian LTS Team