There is 1 open security issue in trixie.
There are 3 open security issues in bookworm.
commit 600ecb0d2727a31bc0f080b7bb585797bc740914
Author: Jonas Smedegaard <dr@jones.dk>
Date: Mon Jan 19 13:05:55 2026 +0100
update changelog and copyright hints
commit 7466a066777225a10cf70fead7272a0958ac201e
Author: Jonas Smedegaard <dr@jones.dk>
Date: Mon Jan 19 13:03:43 2026 +0100
update copyright info: update coverage
commit 09cf4b1ea91858df9f7e81012febf1937f9f911a
Author: Jonas Smedegaard <dr@jones.dk>
Date: Mon Jan 19 12:48:26 2026 +0100
unfuzz patches
commit 94bf678e1d18c1579c094ce72bec84d37ec4da85
Merge: 2f37b19f 655b398e
Author: Jonas Smedegaard <dr@jones.dk>
Date: Mon Jan 19 12:46:29 2026 +0100
Update upstream source from tag 'upstream/22.8.0_rc1+dfsg+_cs6.15.60671435'
Update to upstream version '22.8.0~rc1+dfsg+~cs6.15.60671435'
with Debian dir efdea3b84435b3594a8cc83e9b999cf665e7725c
commit 655b398e477b49b070de03e0c46f88e6f75041a8
Author: Jonas Smedegaard <dr@jones.dk>
Date: Mon Jan 19 12:46:10 2026 +0100
New upstream version 22.8.0~rc1+dfsg+~cs6.15.60671435
commit 2f37b19ff27c4a0c3ecb97c27d56a25ac3d30984
Author: Jonas Smedegaard <dr@jones.dk>
Date: Mon Jan 19 12:42:54 2026 +0100
update watch file: use Uversion-Mangle: auto (not custom regex); use Dversion-Mangle: auto; use Repacksuffix: +dfsg (not ~dfsg)
commit eba5b11096d33211a76fc9d2c9370e9d31380f6c
Author: Jonas Smedegaard <dr@jones.dk>
Date: Mon Jan 19 12:32:10 2026 +0100
update copyright info: avoid any .git* files when repackaging source
commit 9decfc4daa7d71585a0f354a440bf41a029f40cd
Author: Jonas Smedegaard <dr@jones.dk>
Date: Mon Jan 19 12:28:50 2026 +0100
declare compliance with Debian Policy 4.7.3
commit 31bf7b6458baf443a950febeaaf4cbaf388b2cc0
Author: Jonas Smedegaard <dr@jones.dk>
Date: Mon Jan 19 12:28:42 2026 +0100
stop superfluously set fields Rules-Requires-Root Priority
Among the 15 debian patches available in version 1:22.7.0~dfsg+~cs6.15.60671435-1 of the package, we noticed the following issues:
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.