From noreply at release.debian.org Fri Oct 2 05:40:14 2026 From: noreply at release.debian.org (Debian testing autoremoval watch) Date: Fri, 02 Oct 2026 04:40:14 +0000 Subject: [Pkg-mailman-hackers] mailmanclient is marked for autoremoval from testing Message-ID: mailmanclient 3.3.5-1 is marked for autoremoval from testing on 2026-11-03 It (build-)depends on packages with these RC bugs: 1148561: python-anyio: CVE-2026-64847 CVE-2026-63349 CVE-2026-63374 https://bugs.debian.org/1148561 For more information on the autoremoval process, including hints to prevent autoremoval can be found on the wiki: https://wiki.debian.org/Autoremoval 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 From sanvila at debian.org Fri Oct 2 20:09:23 2026 From: sanvila at debian.org (Santiago Vila) Date: Fri, 02 Oct 2026 19:09:23 +0000 Subject: [Pkg-mailman-hackers] Bug#1149746: hyperkitty: FTBFS: TypeError: MyRenderer.emphasis() missing 1 required positional argument: 'marker' Message-ID: Package: src:hyperkitty Version: 1.3.12-7 Severity: serious Tags: ftbfs forky sid Dear maintainer: During a rebuild of all packages in unstable, this package failed to build. Below you will find the last part of the build log (probably the most relevant part, but not necessarily). If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202610/ About the archive rebuild: The build was made on virtual machines from AWS, using sbuild and a reduced chroot with only build-essential packages. If you cannot reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and add an affects on src:hyperkitty, so that this is still visible in the BTS web page for this package. Thanks. -------------------------------------------------------------------------------- [...] File "/usr/lib/python3/dist-packages/mistune/core.py", line 271, in iter_tokens yield self.render_token(tok, state) ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mistune/renderers/html.py", line 57, in render_token return func(text) TypeError: MyRenderer.emphasis() missing 1 required positional argument: 'marker' ====================================================================== FAIL: test_email_rendered_using_rendering_mode (hyperkitty.tests.views.test_message.MessageViewsTestCase.test_email_rendered_using_rendering_mode) ---------------------------------------------------------------------- Traceback (most recent call last): File "/<>/hyperkitty/tests/views/test_message.py", line 398, in test_email_rendered_using_rendering_mode self.assertContains(response, ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^ "**Dummy content**", ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ status_code=200) ^^^^^^^^^^^^^^^^ AssertionError: False is not true : Couldn't find '**Dummy content**' in the following response b'\n\n\n\n\n\n\n \n \n\n' ---------------------------------------------------------------------- Ran 366 tests in 97.958s FAILED (failures=1, errors=1, skipped=4, expected failures=2) Destroying test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... OK (0.011s) Running post-migrate handlers for application hyperkitty Adding content type 'hyperkitty | attachment' Adding content type 'hyperkitty | email' Adding content type 'hyperkitty | favorite' Adding content type 'hyperkitty | lastview' Adding content type 'hyperkitty | mailinglist' Adding content type 'hyperkitty | profile' Adding content type 'hyperkitty | sender' Adding content type 'hyperkitty | tag' Adding content type 'hyperkitty | tagging' Adding content type 'hyperkitty | thread' Adding content type 'hyperkitty | threadcategory' Adding content type 'hyperkitty | vote' Adding permission 'Permission object (1)' Adding permission 'Permission object (2)' Adding permission 'Permission object (3)' Adding permission 'Permission object (4)' Adding permission 'Permission object (5)' Adding permission 'Permission object (6)' Adding permission 'Permission object (7)' Adding permission 'Permission object (8)' Adding permission 'Permission object (9)' Adding permission 'Permission object (10)' Adding permission 'Permission object (11)' Adding permission 'Permission object (12)' Adding permission 'Permission object (13)' Adding permission 'Permission object (14)' Adding permission 'Permission object (15)' Adding permission 'Permission object (16)' Adding permission 'Permission object (17)' Adding permission 'Permission object (18)' Adding permission 'Permission object (19)' Adding permission 'Permission object (20)' Adding permission 'Permission object (21)' Adding permission 'Permission object (22)' Adding permission 'Permission object (23)' Adding permission 'Permission object (24)' Adding permission 'Permission object (25)' Adding permission 'Permission object (26)' Adding permission 'Permission object (27)' Adding permission 'Permission object (28)' Adding permission 'Permission object (29)' Adding permission 'Permission object (30)' Adding permission 'Permission object (31)' Adding permission 'Permission object (32)' Adding permission 'Permission object (33)' Adding permission 'Permission object (34)' Adding permission 'Permission object (35)' Adding permission 'Permission object (36)' Adding permission 'Permission object (37)' Adding permission 'Permission object (38)' Adding permission 'Permission object (39)' Adding permission 'Permission object (40)' Adding permission 'Permission object (41)' Adding permission 'Permission object (42)' Adding permission 'Permission object (43)' Adding permission 'Permission object (44)' Adding permission 'Permission object (45)' Adding permission 'Permission object (46)' Adding permission 'Permission object (47)' Adding permission 'Permission object (48)' Running post-migrate handlers for application django_mailman3 Adding content type 'django_mailman3 | profile' Adding content type 'django_mailman3 | maildomain' Adding permission 'Permission object (49)' Adding permission 'Permission object (50)' Adding permission 'Permission object (51)' Adding permission 'Permission object (52)' Adding permission 'Permission object (53)' Adding permission 'Permission object (54)' Adding permission 'Permission object (55)' Adding permission 'Permission object (56)' Running post-migrate handlers for application admin Adding content type 'admin | logentry' Adding permission 'Permission object (57)' Adding permission 'Permission object (58)' Adding permission 'Permission object (59)' Adding permission 'Permission object (60)' Running post-migrate handlers for application auth Adding content type 'auth | permission' Adding content type 'auth | group' Adding content type 'auth | user' Adding permission 'Permission object (61)' Adding permission 'Permission object (62)' Adding permission 'Permission object (63)' Adding permission 'Permission object (64)' Adding permission 'Permission object (65)' Adding permission 'Permission object (66)' Adding permission 'Permission object (67)' Adding permission 'Permission object (68)' Adding permission 'Permission object (69)' Adding permission 'Permission object (70)' Adding permission 'Permission object (71)' Adding permission 'Permission object (72)' Running post-migrate handlers for application contenttypes Adding content type 'contenttypes | contenttype' Adding permission 'Permission object (73)' Adding permission 'Permission object (74)' Adding permission 'Permission object (75)' Adding permission 'Permission object (76)' Running post-migrate handlers for application sessions Adding content type 'sessions | session' Adding permission 'Permission object (77)' Adding permission 'Permission object (78)' Adding permission 'Permission object (79)' Adding permission 'Permission object (80)' Running post-migrate handlers for application sites Adding content type 'sites | site' Adding permission 'Permission object (81)' Adding permission 'Permission object (82)' Adding permission 'Permission object (83)' Adding permission 'Permission object (84)' Creating example.com Site object Running post-migrate handlers for application django_gravatar Running post-migrate handlers for application compressor Running post-migrate handlers for application haystack Running post-migrate handlers for application django_extensions Running post-migrate handlers for application django_q Adding content type 'django_q | schedule' Adding content type 'django_q | task' Adding content type 'django_q | failure' Adding content type 'django_q | success' Adding content type 'django_q | ormq' Adding permission 'Permission object (85)' Adding permission 'Permission object (86)' Adding permission 'Permission object (87)' Adding permission 'Permission object (88)' Adding permission 'Permission object (89)' Adding permission 'Permission object (90)' Adding permission 'Permission object (91)' Adding permission 'Permission object (92)' Adding permission 'Permission object (93)' Adding permission 'Permission object (94)' Adding permission 'Permission object (95)' Adding permission 'Permission object (96)' Adding permission 'Permission object (97)' Adding permission 'Permission object (98)' Adding permission 'Permission object (99)' Adding permission 'Permission object (100)' Adding permission 'Permission object (101)' Adding permission 'Permission object (102)' Adding permission 'Permission object (103)' Adding permission 'Permission object (104)' Running post-migrate handlers for application allauth Running post-migrate handlers for application account Adding content type 'account | emailaddress' Adding content type 'account | emailconfirmation' Adding permission 'Permission object (105)' Adding permission 'Permission object (106)' Adding permission 'Permission object (107)' Adding permission 'Permission object (108)' Adding permission 'Permission object (109)' Adding permission 'Permission object (110)' Adding permission 'Permission object (111)' Adding permission 'Permission object (112)' Running post-migrate handlers for application socialaccount Adding content type 'socialaccount | socialaccount' Adding content type 'socialaccount | socialapp' Adding content type 'socialaccount | socialtoken' Adding permission 'Permission object (113)' Adding permission 'Permission object (114)' Adding permission 'Permission object (115)' Adding permission 'Permission object (116)' Adding permission 'Permission object (117)' Adding permission 'Permission object (118)' Adding permission 'Permission object (119)' Adding permission 'Permission object (120)' Adding permission 'Permission object (121)' Adding permission 'Permission object (122)' Adding permission 'Permission object (123)' Adding permission 'Permission object (124)' Running post-migrate handlers for application openid Adding content type 'openid | openidnonce' Adding content type 'openid | openidstore' Adding permission 'Permission object (125)' Adding permission 'Permission object (126)' Adding permission 'Permission object (127)' Adding permission 'Permission object (128)' Adding permission 'Permission object (129)' Adding permission 'Permission object (130)' Adding permission 'Permission object (131)' Adding permission 'Permission object (132)' 2 attachments moved. make[1]: *** [debian/rules:15: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess failed with exit status 2 -------------------------------------------------------------------------------- From carles at pina.cat Sat Oct 3 21:25:32 2026 From: carles at pina.cat (Carles Pina i Estany) Date: Sat, 3 Oct 2026 20:25:32 +0000 Subject: [Pkg-mailman-hackers] Bug#1149868: mailman3-web: recommends libapache2-mod-proxy-uwsgi which is not in unstable Message-ID: Subject: mailman3-web: recommends libapache2-mod-proxy-uwsgi which is not in unstable Package: mailman3-web Version: 0+20240312-3 Usertags: package-relations package-relations-recommends Severity: wishlist Dear maintainer(s), I noticed that package mailman3-web recommends libapache2-mod-proxy-uwsgi, which is currently not available in unstable. The package libapache2-mod-proxy-uwsgi was removed in 2024 from the apache2 source package: https://salsa.debian.org/apache-team/apache2/-/blob/master/debian/changelog?ref_type=heads#L310 I have recently used mailman3-web and documented the usage and I didn't need to do anything special to get it running in a Debian trixie, so I guess that can be just dropped (in my limited experience). Thank you for your time, PS[0]: I am developing a tool to detect such issues: https://salsa.debian.org/carlespina/check-relations . Reports are manually reviewed before submission. If you would prefer not to receive such reports (for specific packages, all of your maintained packages, etc.), please let me know. Any other feedback is welcomed as well. No more bugreports for this missing relation will be sent. PS[1]: more information available in https://salsa.debian.org/carlespina/check-relations/-/blob/main/README.md and https://salsa.debian.org/carlespina/check-relations/-/blob/main/docs/bug-report-extra-info.md -- Carles Pina i Estany https://carles.pina.cat | carles at pina.cat | cpina at debian.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From noreply at release.debian.org Sun Oct 4 05:39:38 2026 From: noreply at release.debian.org (Debian testing autoremoval watch) Date: Sun, 04 Oct 2026 04:39:38 +0000 Subject: [Pkg-mailman-hackers] mailman-hyperkitty is marked for autoremoval from testing Message-ID: mailman-hyperkitty 1.2.1-4 is marked for autoremoval from testing on 2026-11-03 It (build-)depends on packages with these RC bugs: 1148561: python-anyio: CVE-2026-64847 CVE-2026-63349 CVE-2026-63374 https://bugs.debian.org/1148561 For more information on the autoremoval process, including hints to prevent autoremoval can be found on the wiki: https://wiki.debian.org/Autoremoval 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 From noreply at release.debian.org Sun Oct 4 05:39:38 2026 From: noreply at release.debian.org (Debian testing autoremoval watch) Date: Sun, 04 Oct 2026 04:39:38 +0000 Subject: [Pkg-mailman-hackers] mailman-suite is marked for autoremoval from testing Message-ID: mailman-suite 0+20240312-3 is marked for autoremoval from testing on 2026-11-03 It (build-)depends on packages with these RC bugs: 1148561: python-anyio: CVE-2026-64847 CVE-2026-63349 CVE-2026-63374 https://bugs.debian.org/1148561 For more information on the autoremoval process, including hints to prevent autoremoval can be found on the wiki: https://wiki.debian.org/Autoremoval 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