Bug#1005775: ksmbd-tools: backport package for bullseye
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: ksmbd-tools Severity: wishlist Dear Maintainer, Linux kernel 5.15 is already available for bullseye backports, and is also the default kernel for Raspberry Pi OS, which brings ksmbd kernel module for bullseye users. Is there any chance someone might be interested in providing a backport of ksmbd-tools to bullseye users as well? Best regards, Reka -BEGIN PGP SIGNATURE- Version: BCPG C# v1.8.10.0 iQE4BAEBCAAiBQJiCqKtGxxTb2x5YSBSZWthIDxyZWthQGJ1dGEubW9lPgAKCRDX S8NKJK0NOpTQB/0auYkLY4XG0oTnKZcntAtX2swnKppCS8UXQK+daXQ2R5TyC0vz tR40npLEN9uLNBcQS+F3m+IUpem2Al+0z9s6chcMaXGiiwnAX9W8+6IxSC8Eums6 VXIxgaO0jhpujWOkL8SDtOOkv9pvHCPTi/CsXvr0E0aOoYOtxPcTdQk2/WlMzxsz ZJsbFCVXsPobMXWf0gKlyUXhu6GFi+G0LJrtXAWEOecHKUkZjGHDLdyMSl680J6Q 8ENrUlcQW3S/7L1bd0NXsN9cmqDTcTvQLnItTzUf89MQhCzRlOiOoUpv/hHVWtcZ g7wCXUT9HAEcD9Zh2B3mIKWwBPxS6ppon39N =bKl3 -END PGP SIGNATURE-
Bug#1005768: wsdd2: Please allow dependency on either samba or ksmbd-tools
Also it would be nice if someone can package it in Backports for Debian 11 (bullseye-backports / stable-backports).
Bug#1005768: wsdd2: Please allow dependency on either samba or ksmbd-tools
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: wsdd2 Severity: wishlist X-Debbugs-Cc: r...@buta.moe Dear Maintainer, KSMBD is a Linux kernel server which implements SMB3 protocol in kernel space for sharing files over network, it's part of Linux kernel since 5.15. ksmbd-tools are the user space utilities for ksmbd kernel server, and its Debian package has been accepted since December 2021. Right now, wsdd2 depends on samba, which conflicts with ksmbd-tools. Would you consider allow wsdd2 to be dependent on either samba or ksmbd-tools, so that users may install them together? - -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-3-amd64 (SMP w/4 CPU threads) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wsdd2 depends on: ii libc6 2.33-5 pn samba wsdd2 recommends no packages. wsdd2 suggests no packages. -BEGIN PGP SIGNATURE- Version: BCPG C# v1.8.10.0 iQE4BAEBCAAiBQJiCoEcGxxTb2x5YSBSZWthIDxyZWthQGJ1dGEubW9lPgAKCRDX S8NKJK0NOk+7B/9ITkTqzJNDK0loS7sGofxCPHS9j2TKI3vbVYjhifLMbhe4w/Ys kKHf1rZZELBPgJd7/wWBM6dvjZXs96cptCg05QIV6FspSCiK7BAQ3395AKu4TYx7 Af4/Ytb2OgEaElUgei96p6LEjQ9QCldYQym2mekr7HkrAakhZlBju9PSZsO+WP8X YVC81rF2AcpNWHYx6BHLn8aJ3TMF36GyVmF+draT2adqEdgrVY7NA6fLM/p4krQo YOTAlqjhtAbIbyum99hENr4qW4CS9NC+GrarmC6QBYJoWyLfQDttiT9UUCwzBcjS cPRWs9fGIVFID+Scndiv8+f8EODE0Jm82O6s =Z0aY -END PGP SIGNATURE- reka@buta.moe.asc Description: application/pgp-keys
Bug#995117: msmtpd: Does not work with qBittorrent in Debian Buster
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: msmtp Version: 1.8.11-2~bpo10+1 Severity: important Dear Maintainer, I am trying to use msmtpd as my local smtp server. So far, I cannot get qBittorrent to work with it. When setup individually, qBittorrent can send mail through both exim4 and opensmtpd, and msmtp are able to work together with apt-listchanges, or test emails via sendmail command. However, when configure qBittorrent to send via msmtpd, it doesn't produce any results. qBittorrent's log didn't record anything, dispite it should log errors if something goes wrong during the SMTP session. ``` (N) TIMESTAMP - 'Totally legit torrent' added to download list. (N) TIMESTAMP - Torrent: Totally legit torrent, sending mail notification ``` And there is no new entry in smtp's log. When attempt to produce a mail dump using `--command`, it appears that msmtpd didn't receive anything, as there is no contents piped to command line. I cannot reproduce this problem a Debian 11 Bullseye VM (amd64), with msmtp version 1.8.11 it just works as expected. I can get mail dumped as following: ``` $ cat maildump m...@example.com Date: Sun, 26 Sep 2021 From: qbittorrent_notificat...@service.example.com Subject: [qBittorrent] 'Totally legit torrent' has finished downloading To: m...@example.com MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 VG9ycmVudCBuYW1lOiBUb3RhbGx5IGxlZ2l0IHRvcnJlbnQKVG9ycmVudCBzaXplOiA4LjYgTWlCClNhdmUgcGF0aDogL2hvbWUvdXNlci9Eb3dubG9hZHMvCgpUaGUgdG9ycmVudCB3YXMgZG93bmxvYWRlZCBpbiA8IDFtLgoKClRoYW5rIHlvdSBmb3IgdXNpbmcgcUJpdHRvcnJlbnQuCg== ``` However, this problem will occur in a Debian 10 Buster VM, with qBittorrent 4.1.5-1+deb10u1 from official repo (though qBittorrent version doesn't matter here, as it all failed including unofficial builds). Upgrade msmtp to Version 1.8.11-2~bpo10+1 from buster-backports WILL NOT fix this issue. I have also raised this issue in upstream, more details and discussions are available here: https://github.com/marlam/msmtp-mirror/issues/59 Regards Reka - -- System Information: Debian Release: 10.10 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: arm64 (aarch64) Foreign Architectures: armhf Kernel: Linux 5.10.60-v8+ (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_CRAP Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages msmtp depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.71 ii libc6 2.28-10+rpt2+rpi1 ii libglib2.0-0 2.58.3-2+deb10u3 ii libgnutls303.6.7-4+deb10u7 ii libgsasl7 1.8.0-8+b2 ii libsecret-1-0 0.18.7-1 ii ucf3.0038+nmu1 Versions of packages msmtp recommends: ii ca-certificates 20200601~deb10u2 Versions of packages msmtp suggests: ii msmtp-mta 1.8.11-2~bpo10+1 - -- debconf information: * msmtp/host: smtp.sendgrid.net msmtp/tls: on /etc/ssl/certs/ca-certificates.crt msmtp/sysconfig: true msmtp/port: 465 -BEGIN PGP SIGNATURE- Version: BCPG C# v1.8.8.0 iQE4BAEBCAAiBQJhUH03GxxTb2x5YSBSZWthIDxyZWthQGJ1dGEubW9lPgAKCRDX S8NKJK0NOr+FB/4iYW/kpRECEOKRYxKGZO5eRjuNHoggDFIMkmggxKYgUu6xKKe6 HwP77kWCrMt1bewn5BmFMmDkUR/b6jkdZRMbhWKdfZzpgPNGhlnL7KLXBe9Wle4f UZSosWcHFaOm2CsHkGrDAgWj6AmI6MdxrFK/wvxx2vmrRCL9SWdiheAYLdU+Afx9 HR0hOjj64zp5F5zLBp98c2GQ0QIqXKzJPcaifDsgUkdCqzUZcMU5l15V3dqAWx15 Fb1EleQ/hHsh85ZYinby7U3MKYGc1GCkESShOzfCBcIdgx5piWgPDMGuxJejspUx EBKEJCYi1WlZWi/s0Wx3TKt9FRYFa7phc1eE =lNte -END PGP SIGNATURE- reka@buta.moe.asc Description: application/pgp-keys
Bug#981066: aerc: Cannot Render HTML Emails After Latest w3m Update in bullseye
Package: aerc Version: 0.3.0-2+b1 Severity: important Dear Maintainer, After I did a apt upgrade today (which upgraded w3m from 0.5.3+git20210102-1 to 0.5.3+git20210102-2), I am no longer able to display either plaintext or HTML emails. The message viewer simply display a empty screen instead of email content. Yours sincerely Solya. Reka -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.4.72-microsoft-standard-WSL2 (SMP w/8 CPU threads) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages aerc depends on: ii libc62.31-9 ii libnotmuch5 0.31.3-2 Versions of packages aerc recommends: ii dante-client 1.4.2+dfsg-7 ii w3m 0.5.3+git20210102-2 Versions of packages aerc suggests: ii notmuch 0.31.3-2 -- no debconf information
