Processed (with 4 errors): unarchive

2023-04-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> unarchive 875200
Bug #875200 {Done: Debian FTP Masters } 
[src:tagainijisho] [tagainijisho] Future Qt4 removal from Buster
Unarchived Bug 875200
> notfixed 875200
Unknown command or malformed arguments to command.
> unarchive 673118
Bug #673118 {Done: Debian FTP Masters } 
[tagainijisho] tagainijisho: should not check for new version by default
Unarchived Bug 673118
> notfixed 673118
Unknown command or malformed arguments to command.
> unarchive 672728
Bug #672728 {Done: Debian FTP Masters } 
[tagainijisho] tagainijisho: tagaini jisho doesn't warn when preferred 
dictionary language isn't installed
Unarchived Bug 672728
> notfixed 672728
Unknown command or malformed arguments to command.
> unarchive 672718
Bug #672718 {Done: Debian FTP Masters } 
[tagainijisho] tagainijisho: some part of GUI is too small to display its 
content
Unarchived Bug 672718
> notfixed 672718
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
672718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672718
672728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672728
673118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673118
875200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1032234: cryptsetup-initramfs: libargon2 0~20190702-0.1 no longer links against libpthread which breaks cryptsetup-initramfs

2023-04-04 Thread Bastian Germann

Hi Ondřej,

Please use the original bug. I have changed the BTS address.

Am 04.04.23 um 22:25 schrieb Ondřej Surý:

I went through the upstream changes between 20171227..20190702
and as far as I can tell, there's nothing important in there:

...
Out of these, there are only two commits that might be of interest:

cfa4385e728116989ad88b4be7c23b4868422778 Wait for already running threads if a 
thread creation failed.
fea3943adadf6527d1e839a2953e9591896e628d Use explicit_bzero() on recent glibc 
versions

But it's not like the world will be on fire if those were not backported to 
2017 version.


I do not think you need any upstream changes to fix #1032234 in the 2017 
version. Just apply this commit to it:
https://salsa.debian.org/debian/argon2/-/commit/c2152a2766fc73dd88a7d9e88bb9887cf31f1b1b

Cheers,
Bastian



golang-github-go-macaron-csrf is marked for autoremoval from testing

2023-04-04 Thread Debian testing autoremoval watch
golang-github-go-macaron-csrf 0.0~git20170207.0.428b7c6-6 is marked for 
autoremoval from testing on 2023-04-18

It is affected by these RC bugs:
1033865: golang-github-go-macaron-csrf: Don't release with bookworm
 https://bugs.debian.org/1033865



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl