Bug#1071586: kicad: bookworm-backports requires update to 8.x

2024-05-21 Thread Charlemagne Lasse
Package: kicad Version: 7.0.11+dfsg-1~bpo12+1 Severity: wishlist Backports is expected to track the version in testing. But at the moment, it is unfortunately from an older version. It would be nice to have an upload to bookworm-backports which updates it to the "same" version. If there are any bl

Bug#1069191: glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence

2024-04-22 Thread Charlemagne Lasse
Hi, Can this be backported to older Debian versions via the security repo? This bug can be used to execute code when using the PHP engine: * https://www.offensivecon.org/speakers/2024/charles-fol.html * https://www.openwall.com/lists/oss-security/2024/04/18/4

Bug#1064476: dpkg-buildflags: add support for building with frame pointers enabled

2024-03-17 Thread Charlemagne Lasse
Control: merge 1064476 1058665 1058664 I would even love to have finally a debian again which can be used to debug and profile production ready binaries (at least on amd64). See also * https://www.brendangregg.com/blog/2024-03-17/the-return-of-the-frame-pointers.html * https://ubuntu.com/blog/u

Bug#1037363: libkf5mimetreeparser5abi1: does not find the key used to sign a message if a signing subkey was used

2023-06-12 Thread Charlemagne Lasse
Package: libkf5mimetreeparser5abi1 Version: 4:22.12.3-1 Tags: bookworm sid patch upstream Forwarded: https://bugs.kde.org/show_bug.cgi?id=469304 Control: affects -1 kmail SUMMARY KMail claims that messages signed with a subkey of my own key are signed with an unknown key. STEPS TO REPRODUCE 1. Yo

Bug#1031616: kmail: E-Mail signed with gnupg subkey not properly shown as valid

2023-02-19 Thread Charlemagne Lasse
Package: kmail Version: 22.12.2-1 Severity: normal Tags: bookworm sid upstream Forwarded: https://bugs.kde.org/show_bug.cgi?id=465551 SUMMARY I'm using gnupg with an subkey to sign my e-mails. KMail shows following message when a e-mail was signed with the gnugp subkey: "Not enough information to

Bug#1003242: python3-mailman-hyperkitty: Need a newer version to match mailman core

2022-12-11 Thread Charlemagne Lasse
Control: tags -1 + fixed-upstream patch security Justification: CVE-2021-35058 https://gitlab.com/mailman/mailman-hyperkitty/-/commit/18816fbd4130a9f08b0885e0421c963879808921 https://gitlab.com/mailman/mailman-hyperkitty/-/commit/df9cdc44dc59c7ed78097ef8f5ba3db46e7a92e9 But it might be better to

Bug#1025019: python-aiosmtpd: (autopkgtest) needs update for python3.11: Can't decode base64

2022-12-11 Thread Charlemagne Lasse
Control: tags -1 + fixed-upstream patch Patch can be found at https://github.com/aio-libs/aiosmtpd/commit/827f2321b7a926f3e8ba2aad6387b36c7c2e0b9a.patch

Bug#1013480: hyperkitty: FTBFS: TypeError: __init__() got an unexpected keyword argument 'providing_args'

2022-11-14 Thread Charlemagne Lasse
Am Mo., 14. Nov. 2022 um 10:53 Uhr schrieb Pierre-Elliott Bécue : > I really don't need reminders about the bugs on my packages. This is not a reminder. I was just going through the mailman3 packages to understand what is currently blocking the migration of packages. And when I found out what is b

Bug#1013480: hyperkitty: FTBFS: TypeError: __init__() got an unexpected keyword argument 'providing_args'

2022-11-14 Thread Charlemagne Lasse
Control: tags -1 + fixed-upstream patch This problem currently blocks various mailman3 related packages from migrating to Debian bookwoom. But it seems like this is fixed by 1.3.6: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6

Bug#1013500: django-mailman3: FTBFS: TypeError: __init__() got an unexpected keyword argument 'providing_args'

2022-11-14 Thread Charlemagne Lasse
Control: tags -1 + fixed-upstream patch This problem currently blocks various mailman3 related packages from migrating to Debian bookwoom. But it seems like this is fixed by 1.3.8: https://pypi.org/project/django-mailman3/ (btw. thanks for the mailman 3.3.7 upload)

Bug#998223: Contributors for Mailman 3 in Debian / your RFH

2022-11-13 Thread Charlemagne Lasse
> Mailman3 has been part of buster and bullseye, but the release of sqlalchemy > 1.4 is not compatible with it and therefore there is a chance that it will > not make it in bookworm. There is nothing that any contributor can do except > taking the time to help mailman upstream to be fixed and wo

Bug#1023976: mailman3: Package version 3.3.7

2022-11-13 Thread Charlemagne Lasse
Package: mailman3 Version: 3.3.3-1 Severity: wishlist Control: block 996806 by -1 Control: tags 996806 + patch fixed-upstream Control: block 995779 by -1 Control: tags 995779 + patch fixed-upstream Control: block 1004934 by -1 Control: tags 1004934 + patch fixed-upstream Control: block 1015989 by -

Bug#995779: autopkgtest fails with sqlalchemy 1.4.23+ds1

2022-11-06 Thread Charlemagne Lasse
Control: tags 995779 + patch This is the upstream merged fix for sqlalchemy 1.4: https://gitlab.com/mailman/mailman/-/commit/c926e3d54680d4fac0648cde036368c699976038

Bug#998223: Contributors for Mailman 3 in Debian / your RFH

2022-11-04 Thread Charlemagne Lasse
Am Sa., 15. Okt. 2022 um 09:39 Uhr schrieb Pierre-Elliott Bécue : > Mailman3 has been part of buster and bullseye, but the release of sqlalchemy > 1.4 is not compatible with it and therefore there is a chance that it will > not make it in bookworm. There is nothing that any contributor can do exc

Bug#998223: Contributors for Mailman 3 in Debian / your RFH

2022-10-15 Thread Charlemagne Lasse
Hi, Where can we find results from the new contributors? Because it looks at the moment like Debian bookworm might become the third Debian release (after buster + bullseye) which is unsuitable as a base system for software project servers (redmine + mailman3 + gitolite). At least, for the last two

Bug#960454: chromium: Make Chromium ask before downloading and enabling DRM

2021-01-25 Thread Charlemagne Lasse
Completely disabling the autoupdater was an extremely bad idea. Now even various autoupdater scripts to update the global version in /usr/lib/chromium/WidevineCdm don't work anymore - so leaving users in a broken state. See also #981069

Bug#981069: chromium: Doesn't load widevine from /usr/lib/chromium/WidevineCdm/

2021-01-25 Thread Charlemagne Lasse
Package: chromium Version: 88.0.4324.96-0.1 X-Debbugs-CC: Olivier Tilloy X-Debbugs-CC: mimi8 The changes for ticket #960454 removed the autoupdater for widevine. And then mentions in the README.debian that /usr/lib/chromium/WidevineCdm/ is the place to put the widevine binaries. But this is

Bug#979970: libselinux1: dependency to newer libc6 ignored by/missing for aptitude

2021-01-12 Thread Charlemagne Lasse
Package: libselinux1 Version: 2.8-1+b1 Severity: grave Right now, an update from buster to bullseye on amd64 completely bricks the system because libselinux1 is requiring a libc6 which is not yet installed on the system: Preparing to unpack .../0-libselinux1_3.1-2+b2_amd64.deb ... De-conf

Bug#977510: [gajim] File/Link actions cause g-io-error-quark exception

2020-12-15 Thread Charlemagne Lasse
Package: gajim Version: 1.2.2-1 Severity: important Tags: patch X-Debbugs-Cc: pkg-gnome-maintain...@lists.alioth.debian.org X-Debbugs-Cc: pkg-xmpp-de...@lists.alioth.debian.org X-Debbugs-Cc: pkg-freedesktop-maintain...@lists.alioth.debian.org It was noticed that there is a regression when switchin

Bug#950500: aqbanking-tools: aqpaypal-tool unable to call any control function

2020-02-02 Thread Charlemagne Lasse
Package: aqbanking-tools Version: 6.0.1-2 Tags: patch The libaqbanking44 or the aqbanking-tools are currently incompatible with each other when calling the aqpaypal backend aqpaypal-tool fff 3:2020/02/02 17-39-18:aqpaypal-tool(16869):aqpaypal-tool.c: 246: Error calling control function (-51) I

Bug#947080: [getmail] Crashes when not being able to decode encoding of Cc line

2019-12-20 Thread Charlemagne Lasse
Package: getmail Version: 5.13-1 Severity: normal Tags: buster X-Debbugs-CC: getm...@lists.pyropus.ca X-Debbugs-CC: charlesc-getmail-supp...@pyropus.ca I now have to soothe a lot of angry people because I didn't receive some important mails from one of my accounts (and thus didn't act correctly).

Bug#945406: chromium: Widevine content decrytion module no longer working

2019-11-24 Thread Charlemagne Lasse
Package: chromium Version: 78.0.3904.97-1~deb10u1 Tags: buster The update in Debian Buster amd64 broke the support for the Widevine content decryption module. It was working fine before with 76.0.3809.100-1~deb10u1. The component is also no longer shown under chrome://components/ and this problem

Bug#931496: redmine: Missing in Debian Buster

2019-07-06 Thread Charlemagne Lasse
Source: redmine Severity: normal Tags: buster I've just updated my server to Debian buster and then noticed that my redmine was gone. Problem is that it was removed from Debian testing https://tracker.debian.org/news/1027921/redmine-removed-from-testing/ (when Buster was still equal to testing) P

Bug#929492: iwyu: Requests to add forward declaration which is in file

2019-05-24 Thread Charlemagne Lasse
Package: iwyu Version: 7.0-3 Forwarded: https://github.com/include-what-you-use/include-what-you-use/issues/682 Tags: buster sid X-Debbugs-CC: Kim Grasman Problem can reproduced via (please check the first line): struct foobar; struct foobar *test(struct foobar *asd) { retu

Bug#925528: kwin-x11: High CPU load and extreme screen tearing with nvidia driver

2019-03-26 Thread Charlemagne Lasse
Here is a patch which can be applied on top of the kwin package to include the two patches which modify GlxBackend::GlxBackend. From ad5f05d207edd32fc8571c9ae6bb916e61b291d4 Mon Sep 17 00:00:00 2001 From: Charlemagne Lasse Date: Tue, 26 Mar 2019 15:30:19 +0100 Subject: [PATCH] Fix missing vsync

Bug#925528: kwin-x11: High CPU load and extreme screen tearing with nvidia driver

2019-03-26 Thread Charlemagne Lasse
Package: kwin-x11 Version: 4:5.14.5-1 Severity: important Tags: buster sid patch upstream fixed-upstream Forwarded: https://bugs.kde.org/show_bug.cgi?id=322060 kwin-x11 with the current nvidia driver causes extreme high CPU load and tearing. The graphics performance is also reduced to an unaccepta

Bug#922502: plasma-desktop: regional settings allow do select system incompatible locales

2019-02-18 Thread Charlemagne Lasse
> Control: reassign -1 libqt5core5a/5.11.3+dfsg-2 > Control: affects -1 plasma-desktop > > Control: severity -1 important > > Please, don't abuse the bugs severity just to get more attention. I didn't abuse the severity. The https://www.debian.org/Bugs/Developer#severities has an entry "makes unr

Bug#922213: Bug#922500: tex-common: Fails to install with LC_TIME=en_DE.UTF-8

2019-02-17 Thread Charlemagne Lasse
> On Sun, 17 Feb 2019, Charlemagne Lasse wrote: > > perl: warning: Setting locale failed. > > perl: warning: Please check that your locale settings: > > LANGUAGE = "en_US:en", > > LC_ALL = (unset), > > LC_TIME = "en_DE.UTF-8", > >

Bug#922502: plasma-desktop: regional settings allow do select system incompatible locales

2019-02-17 Thread Charlemagne Lasse
See also https://bugs.debian.org/922500

Bug#922502: plasma-desktop: regional settings allow do select system incompatible locales

2019-02-17 Thread Charlemagne Lasse
Package: plasma-desktop Version: 4:5.14.5-1 Severity: critical Justification: makes unrelated software break on the system The "regional settings" allow to select various regions which are not available on the system (even with locales-all). An example here is en_DE (Germany) for "Time". This is t

Bug#922500: tex-common: Fails to install with LC_TIME=en_DE.UTF-8

2019-02-17 Thread Charlemagne Lasse
Package: tex-common Version: 6.10 Severity: serious Justification: Fails to install on a normal KDE installation with "Germany" setting as Time localization The installation works fine with LC_TIME=C but not with the setting generated by KDE LC_TIME=en_DE.UTF-8. The aptitude output follows and at

Bug#922213: locales-all: Doesn't provide en_DE.UTF-8

2019-02-13 Thread Charlemagne Lasse
Package: locales-all Version: 2.28-6 Severity: normal X-Debbugs-CC: debian-qt-...@lists.debian.org, debian-tex-ma...@lists.debian.org It is possible under KDE to change the locale to en_DE.UTF-8/German for some specific parts (e.g. time) but it seems to be missing on the system even when locales

Bug#921381: [firefox-esr] Fails to use the correct esr update channel + gmp-components

2019-02-11 Thread Charlemagne Lasse
> The attached patch can be used to switch firefox-esr to the correct > MOZ_UPDATE_CHANNEL "esr" instead of "default" (which provided the > incompatible Gecko Media Plugins widevine and openh264) The same problem was observed on Gentoo. The gentoo reporter basically ported the bugfix from this tic

Bug#921832: [firefox-esr] FTBFS of security/certverifier/Buffer.cpp

2019-02-09 Thread Charlemagne Lasse
Source: firefox-esr Version: 60.5.0esr-1 Severity: grave Tags: patch Forwarded: https://bugzilla.mozilla.org/show_bug.cgi?id=1526648 Noticed while trying to prepare the mini fix for https://bugs.debian.org/921381 /usr/bin/g++ -o Unified_cpp_certverifier0.o -c -Ibuster/stl_wrappers -Ibuster/system

Bug#921381: [firefox-esr] Fails to use the correct esr update channel + gmp-components

2019-02-09 Thread Charlemagne Lasse
tions --with-unsigned-addon-scopes=app,system ac_add_options --enable-alsa +ac_add_options --enable-update-channel=esr --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +firefox-esr (60.5.0esr-2) UNRELEASED; urgency=medium + + [ Charlemagne Lasse ] + + * Fix download of esr compatibl

Bug#921823: chromium: FTBFS of vaapi_wrapper.cc in i386/armhf (pointer casting)

2019-02-09 Thread Charlemagne Lasse
Source: chromium Version: 72.0.3626.81-1 Severity: grave X-Debbugs-CC: 856...@bugs.debian.org FAILED: obj/media/gpu/vaapi/vaapi/vaapi_wrapper.o g++ -MMD -MF obj/media/gpu/vaapi/vaapi/vaapi_wrapper.o.d -DMEDIA_GPU_IMPLEMENTATION -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_N

Bug#921738: chromium-widevine: Widevine does not work with Netflix

2019-02-08 Thread Charlemagne Lasse
tags 921738 + wontfix bye This package is *not* widevine. It is the *support* for the legacy widevine cdm. You still have to download the widevine cdm from widevine.com/google. Google prohibits its distribution without a license: > "Google Inc. and its affiliates ("Google") own all legal right, t

Bug#921646: kdepim-runtime: akonadi_imap_resource fails to download gmail content

2019-02-07 Thread Charlemagne Lasse
Package: kdepim-runtime Version: 4:18.08.3-1 Severity: important I've spend now a week trying to get may my gmail imap downloaded. I am using the standard settings from imap with imap server set to imap.gmail.com. It downloads the mails of a single year (2015) and then shows it stops suddenly Af

Bug#921521: chromium-browser: CVE/Security fixes missing in stable-sec

2019-02-06 Thread Charlemagne Lasse
Package: chromium Version: 71.0.3578.80-1~deb9u1 Severity: serious The stable-sec package is stuck with version 71.0.3578.80 and is missing security updates for several CVEs. Take for example the list from 72.0.3626.81 - Stack buffer overflow in Skia. Reported by Ivan Fratric - Use after free in

Bug#921381: [firefox-esr] Fails to use the correct esr update channel + gmp-components

2019-02-04 Thread Charlemagne Lasse
Package: firefox-esr Version: 60.5.0esr-1~deb9u1 Severity: important X-Debbugs-CC: bvan...@mozilla.com It was noticed that the Debian stretch version (and most likely also the Debian buster) of firefox-esr uses the wrong channel to search for components. As result, the downloaded components don't

Bug#911433: [nvidia-driver] Update to 410.66

2018-10-19 Thread Charlemagne Lasse
Source: nvidia-driver Severity: wishlist The new driver version is required to support the current generation of nvidia GPUs: Added support for the following GPUs: GeForce RTX 2070 GeForce RTX 2080 Ti GeForce RTX 2080 Quadro P5200 with Max-Q Design Quadro P4200 with Max-Q Design Quadro P2000 wit

Bug#904652: pulseaudio: looses device and replace it with dummy package so no sound possible

2018-07-28 Thread Charlemagne Lasse
found 904652 11.1-5 thanks > i didn't do anything. > Upgrading the system like always. > Suddenly there was no sound available. Change /etc/pulse/default.pa to automatically load module-alsa-sink on boot (module-udev-detect is broken and will not load the alsa-sink anymore) This is also a proble

Bug#898643: [python-keyring] update to keyring 12.x

2018-05-14 Thread Charlemagne Lasse
Source: python-keyring Version: 10.1-1 Severity: normal The gajim developers asked me to test 12.x of python keyring. These seems to fix a problem with their login system. See https://dev.gajim.org/gajim/gajim/issues/9126#note_186025

Bug#888605: [gajim] Regression: kwallet integration missing

2018-02-09 Thread Charlemagne Lasse
Source: gajim Source-Version: 1.0.0~beta1-1 Seems to work here. Thanks

Bug#889809: [linux] Fails to compile external modules

2018-02-07 Thread Charlemagne Lasse
Source: linux Version: 4.14.13-1~bpo9+1 Severity: normal X-Debbugs-CC: backpo...@vger.kernel.org It seems like the current kernel in stretch backporst and in buster has problems when compiling external modules against it. This worked fine in the past. Also works fine when compiling against a manua

Bug#888605: [gajim] Regression: kwallet integration missing

2018-02-03 Thread Charlemagne Lasse
forwarded 888605 https://dev.gajim.org/gajim/gajim/issues/8875 tags 888605 + patch thanks The problem is fixed in https://dev.gajim.org/gajim/gajim/merge_requests/206. The kwalletcli dependency has to be dropped in debian (it is wrong at the moment anyway) and instead it now has to depend on pytho

Bug#888611: [gajim] Fails to keep connection against prosody 0.9.12-2 (Debian Stretch)

2018-01-27 Thread Charlemagne Lasse
Package: gajim Version: 1.0.0~alpha2-1 Severity: normal The gajim version from Debian Stretch worked fine but now with gajim 1.0.0~alpha2-1 (0.98.2 according to the about page), the connection drops all the time against a prosody 0.9.12-2 server (Debian Stretch). I see following in the XML log:

Bug#888609: [smb4k] Retrieving the list of available domains failed

2018-01-27 Thread Charlemagne Lasse
Package: smb4k Version: 2.0.2-1 Severity: normal smb4k shows me following when it gets started under Debian buster: Retrieving the list of available domains failed: Usage: [-?fMRSTrAV] [-?|--help] [--usage] [-B|--broadcast=BROADCAST-ADDRESS] [-f|--flags] [-U|--unicast=STRING] [-M|--master-browser

Bug#888605: [gajim] Regression: kwallet integration missing

2018-01-27 Thread Charlemagne Lasse
Package: gajim Version: 1.0.0~alpha2-1 Severity: important The kwallet integration was done in the gajim stretch version using kwalletcli. But upstream removed it in 13a61d76187c ("Remove support for GNOME Keyring and KWalletCLI, instead always use libsecret.") without a replacement for KDE. The k

Bug#888442: [nftables] Crash when list(ing) ip6tables-compat CT rules

2018-01-25 Thread Charlemagne Lasse
Package: nftables Version: 0.7-1 Severity: important The nft list crashes when an ip6tables-compat CT rule is found also in iptables-compat. This is either an assert with 0.7-1 or a segfault with 0.8-2~bpo9+1. # nft flush ruleset # nft list ruleset # iptables-compat -A INPUT -m state --state ESTA

Bug#863475: [prosody] Fails to initiate s2s when lua-event 0.4.3 is installed

2017-05-27 Thread Charlemagne Lasse
Package: prosody Version: 0.9.12-1 Severity: serious Tags: patch stretch Prosody fails to intiate S2S connections when lua-event 0.4.3 is installed. This bug was already fixed in the 0.10 branch of prosody but is still present on Debian stretch (which is shipped with lua-event 0.4.3) The fix can

Bug#842710: [gcc-6] Fails to compile OpenWrt/LEDE prereq-build

2016-10-31 Thread Charlemagne Lasse
Package: gcc-6 Version: 6.2.0-10 Severity: serious X-Debbugs-CC: lede-...@lists.infradead.org There is a regression after gcc-6 6.2.0-6. I get following output when trying to compile LEDE/OpenWrt "Please install a static zlib" This is wrong $ ls -ltr /usr/lib/x86_64-linux-gnu/libz.a -rw-r--r-- 1

Bug#831525: [libretro-mupen64plus] Remove copies of mupen64plus-*

2016-08-21 Thread Charlemagne Lasse
severity 831525 serious bye Then please integrate your changes in upstream mupen64plus. Many "forks" are now removed from debian (I think mutt-patched is one of the recent ones) and now you start to introduce new ones - against the Debian policy

Bug#831525: [libretro-mupen64plus] Remove copies of mupen64plus-*

2016-07-16 Thread Charlemagne Lasse
Source: libretro-mupen64plus Version: 2.0+git20160207+dfsg2-1 Severity: serious Marked as serious because it is a violation of paragraph 4.13 from the Debian Policy. Debian should not ship the same things twice. So the Debian Games Team should decide whether it wants to ship mupen64plus-* or libr