Bug#958179: My setup

Not a solution to the issue you raised, but in case that helps, I've documented my own setup here: https://feeding.cloud.geek.nz/posts/home-music-server-with-mpd/ Francois -- https://fmarier.org/

Bug#969602: lptools: UnicodeDecodeError in lp-project-upload

Package: lptools Version: 0.2.0-7 Severity: normal I was unable to use lp-project-upload to upload a new release of safe-rm to Launchpad: $ gpg --armor --sign --detach-sig safe-rm-0.13.tar.gz gpg: using "8C470B2A0B31568E110D432516281F2E007C98D1" as default secret key for signing $

Bug#969356: safe-rm: Add support for csh/tcsh

Package: safe-rm Version: 0.12-11 Severity: wishlist Tags: help Right now safe-rm is enabled by default for interactive bash/dash shells due to the fact that it drops a configuration blurb in /etc/profile.d/ which overwrites the default PATH:

Bug#969306: Checking for interactive shells

According to https://stackoverflow.com/questions/945302/, one can check for the presence of an interactive KornShell using: [[ $- == *i* ]] && echo interactive || echo not interactive Francois -- https://fmarier.org/

Bug#969305: [Pkg-zsh-devel] Bug#969305: zsh: safe-rm needs to be added to the default path of interactive shells to work

On 2020-08-31 at 04:41:56, Daniel Shahaf wrote: > I guess it should be in the zprofile file, guarded by a [[ -o interactive ]] > check. >From the comment in /etc/zsh/zshrc: # This file is sourced only for interactive shells. It # should contain commands to set up aliases, functions, #

Bug#969306: safe-rm: Add support for ksh, the KornShell

Package: safe-rm Version: 0.12-10 Severity: wishlist Tags: help Right now safe-rm is enabled by default for interactive bash/dash shells due to the fact that it drops a configuration blurb in /etc/profile.d/ which overwrites the default PATH:

Bug#969307: safe-rm: Add support for Fish, the friendly interactive shell

Package: safe-rm Version: 0.12-10 Severity: wishlist Tags: help Right now safe-rm is enabled by default for interactive bash/dash shells due to the fact that it drops a configuration blurb in /etc/profile.d/ which overwrites the default PATH:

Bug#969305: zsh: safe-rm needs to be added to the default path of interactive shells to work

Package: zsh Version: 5.8-5 Severity: normal This isn't really a bug in zsh, but rather I'd like to figure out how to best enable the safe-rm package for zsh users. For bash, we ship a config file in /etc/profile.d/ which adds /usr/share/safe-rm/bin in front of /bin:

Bug#969303: tiger: diff for NMU version 1:3.2.4~rc1-2.1

2.4~rc1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add missing dependency on lsb-release (closes: #962975). + * Use mktemp instead of tempfile (closes: #961642). + * Teach tiger about nsfs (closes: #968713). + + -- Francois Marier Sun, 30 Aug 2020 16:58:11 -0700 + tiger (1:

Bug#968116: Logcheck rule?

If these messages are not an indication of anything wrong on the system or in these third-paty service files, then perhaps a logcheck rule filtering them out would be appropriate for the systemd package? Francois -- https://fmarier.org/

Bug#968169: lxc: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.

Package: lxc Version: 1:4.0.2-1 Severity: normal I see the following message in my logs once a day: Aug 9 06:43:56 hostname systemd[1]: /lib/systemd/system/lxc.service:18: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider

Bug#968168: smartmontools: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.

Package: smartmontools Version: 7.1-1 Severity: normal I see the following in my logs every day: Aug 9 06:43:56 hostname systemd[1]: /lib/systemd/system/smartmontools.service:10: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and

Bug#968167: gdm3: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.

Package: gdm3 Version: 3.36.2-1 Severity: normal I see the following message in my logs once a day: Aug 9 06:43:56 hostname systemd[1]: /lib/systemd/system/gdm.service:30: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider

Bug#968166: apt-listbugs: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.

Package: apt-listbugs Version: 0.1.32 Severity: normal I see the following in my logs once a day: Aug 9 06:43:56 hostname systemd[1]: /lib/systemd/system/apt-listbugs.service:30: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and

Bug#967917: blk-availability.service: Cannot add dependency job, ignoring: Unit blk-availability.service has a bad unit file setting.

Package: lvm2 Version: 2.03.09-2 Severity: normal I'm seeing these errors messages in my logs every hour: Aug 4 14:30:33 systemd[1]: blk-availability.service: Cannot add dependency job, ignoring: Unit blk-availability has a bad unit file setting. Aug 4 14:34:28 systemd[1]:

Bug#957244: Upstream issue

This upstream issue: https://github.com/mrash/fwknop/issues/305 suggests the following patch: https://github.com/Jakuje/fwknop/commit/a87325b0816a79329cf0b4d4f9ebf247ead117db Francois -- https://fmarier.org/

Bug#864795: Outdated upstream repository links

The upstream repository has moved. The latest one can be found here: https://brave-browser.readthedocs.io/en/latest/installing-brave.html#debian-9-ubuntu-14-04-and-mint-17 The repo itself is: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main and the signing key is

Bug#965162: RFP: semgrep -- lightweight static analysis for many languages

Package: wnpp Severity: wishlist * Package name: semgrep Version : 0.15.0 Upstream Author : r2c * URL : https://semgrep.live/ * License : LGPL-2.1 Programming Lang: Python, OCaml Description : lightweight static analysis for many

Bug#965160: hamradio-training: Please recommend the canadian-ham-exam package

Package: hamradio-training Version: 0.5 Severity: normal The current package only recommends training programs for US / FCC certifications. A training program for Canada / ISEC is now available in unstable: https://packages.debian.org/sid/canadian-ham-exam Francois -- https://fmarier.org/

Bug#964333: ITP: tmd710-tncsetup -- tool to configure the TNC on several Kenwood radios

Package: wnpp Severity: wishlist Owner: Francois Marier * Package name: tmd710-tncsetup Version : 1.13 Upstream Author : Francois Marier * URL : https://github.com/fmarier/tmd710_tncsetup * License : GPL-3.0-or-later Programming Lang: C Description

Bug#964332: ITP: canadian-ham-exam -- practice test for the Canadian Amateur Radio exam

Package: wnpp Severity: wishlist Owner: Francois Marier * Package name: canadian-ham-exam Version : 1.0.0 Upstream Author : Francois Marier * URL : https://launchpad.net/canadian-ham-exam * License : AGPL-3.0-or-later Programming Lang: Python Description

Bug#961642: Patch

I've applied the attached patch locally and it has silenced the warning. The first patch hunk (config) is the necessary one, but I've taken the liberty to remove all other uses of the "tempfile" command. Francois -- https://fmarier.org/ --- /home/francois/config 2020-05-26 19:17:16.192981188

Bug#961605: rkhunter: /bin/which moved to /usr/bin/which

On 2020-05-26 at 17:00:03, Christoph Anton Mitterer wrote: > The symlink /bin/which to /usr/bin/which was removed. > > Please adapt the template config to use /usr/bin/which . I think that it was already done in order to fix #931396:

Bug#961642: tigercron: WARNING: tempfile is deprecated; consider using mktemp instead.

Package: tiger Version: 1:3.2.4~rc1-2 Severity: normal Once an hour, tigercron generates the following WARNING in an email: WARNING: tempfile is deprecated; consider using mktemp instead. Francois -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500,

Bug#956759: libayatana-indicator3 in workrave 1.10.44

On 2020-05-15 at 20:45:38, Kentaro Hayashi wrote: > Thus, it should be ayatana-indicator3-0.4 instead of indicator3-0.4. Thanks Kentaro. I have applied your patch and uploaded the latest release. It has now also been fixed upstream:

Bug#956759: libayatana-indicator3 in workrave 1.10.44

Hi Kentaro, I have tried updating the workrave package to version 1.10.44 which includes your libayatana-indicator3 patch, however I can't get it to build since I run into this error: /bin/bash ../../../../libtool --tag=CC --mode=link gcc -pthread -I/usr/include/libayatana-indicator3-0.4

Bug#960127: Tk::Error: Can't locate object method "resolve_names" via package "App::ClusterSSH::Window"

Package: clusterssh Version: 4.14-1 Severity: grave Justification: renders package unusable It looks like cssh doesn't work anymore on my Debian unstable machine. When I add a host, I see the following on the console: Tk::Error: Can't locate object method "resolve_names" via package

Bug#951144: libpam-cap: PAM unable to dlopen(pam_cap.so): /lib/security/pam_cap.so: cannot open shared object file

On 2020-03-27 at 13:32:30, Christian Kastner wrote: > On 24.02.20 09:49, Timo van Roermund wrote: > > I see the same issue: > > > > Feb 23 16:22:06 hostname smbd[522826]: PAM unable to dlopen(pam_cap.so): > > /lib/security/pam_cap.so: cannot open shared object file: No such file > > or directory

Bug#955135: TypeError: '<' not supported between instances of 'NotImplementedType' and 'int'

Package: unattended-upgrades Version: 2.0 Severity: normal I've been seeing the following errors in my logs for a few days: Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: Traceback (most recent call last): Mar 27 06:38:16 hostname apt.systemd.daily[1664925]: File

Bug#953641: DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats

On 2020-03-12 at 12:29:54, Bálint Réczey wrote: > Do you still observe the messages? > This should have been fixed in python-apt in #944091 in version 1.9.1 I haven't seen the messages in a while now. I guess it's all fixed. Francois -- https://fmarier.org/

Bug#954734: mythtv-status: Error while starting the systemd service file

Package: mythtv-status Version: 1.0.1-1 Severity: normal Tags: patch I used to get the following errors when mythtv-status would start: Mar 19 20:35:16 keflavik sh[3364]: rm: impossible de supprimer '/var/lib/mythtv-status/motd_update_disabled': Aucun fichier ou dossier de ce type That

Bug#953641: DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats

On 2020-03-12 at 12:29:54, Bálint Réczey wrote: > Do you still observe the messages? I will need to remove the logcheck rule I added yesterday to confirm, but this morning I saw this new message: Mar 12 06:26:02 hostname apt.systemd.daily[1857505]: /usr/bin/unattended-upgrade:1047:

Bug#953641: DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats

Package: unattended-upgrades Version: 1.17 Severity: normal I noticed the following in my logs this morning: Mar 11 07:16:18 hostname apt.systemd.daily[715786]: /usr/bin/unattended-upgrade:1017: DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats Mar 11 07:16:18 hostname

Bug#951366: rkhunter: libkeyutils1/1.6.1-2 triggers a false positive

On 2020-02-15 at 16:12:16, Francesco Poli wrote: > thanks from a suggestion from keyutils Debian package maintainer, > I managed to work around the issue, by adding the following two > lines to my rkhunter configuration file: > > $ grep keyutils /etc/rkhunter.conf >

Bug#949331: marked as done (fwknop-server: consider building with nfq support)

I have reverted this in 2.6.10-7. Building with NFQ support disables PCAP support. I'm not sure it's possible to have both. Is there any advantage to migrating users to NFQ? Francois -- https://fmarier.org/ signature.asc Description: PGP signature

Bug#949332: fwknop-apparmor-profile: consider adding ipset to apparmor profile

In other words, the attached patch is what was needed to make this work on your machine? Francois -- https://fmarier.org/ --- a/extras/apparmor/usr.sbin.fwknopd +++ b/extras/apparmor/usr.sbin.fwknopd @@ -20,16 +20,23 @@ /bin/bash rix, /etc/fwknop/access.conf r, /etc/fwknop/fwknopd.conf

Bug#951144: libpam-cap: PAM unable to dlopen(pam_cap.so): /lib/security/pam_cap.so: cannot open shared object file

Package: libpam-cap Version: 1:2.31-1 Severity: normal I see the following in my logs: Feb 11 07:39:22 hostname systemd: PAM unable to dlopen(pam_cap.so): /lib/security/pam_cap.so: cannot open shared object file: No such file or directory Feb 11 07:39:22 hostname systemd: PAM adding faulty

Bug#933636: CVE-2019-14934

On 2020-02-07 at 10:14:24, Salvatore Bonaccorso wrote: > > It looks OK to me. Tagging moreinfo until there's a final diff. > > Friendly ping, any news? (It's too late now for the upcoming point > release though). It's still on my list, but not a very high priority. Definitely won't happen until

Bug#950812: pciutils: update-pciids fails because /usr/share/misc/pci.ids.old already exists

Package: pciutils Version: 1:3.6.4-1 Severity: normal If I run the `update-pciids` command, it fails: $ sudo /usr/sbin/update-pciids % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft

Bug#947208: youtube-dl 2019.11.28 is available

Package: youtube-dl Version: 2019.09.28-1 Severity: wishlist A new version of youtube-dl is available upstream. The one in Debian is a few months old and is missing a few new sites. Francois

Bug#941855: dunst: Daily systemd errors: "Failed to start Dunst notification daemon."

On 2019-10-15 at 11:36:30, Nikos Tsipinakis wrote: > > /usr/bin/systemctl status --user dunst > > Huh, why `status` and not `start`? Is that a typo? Yes, typo indeed! I've now fixed that. > Perhaps the import-environment fails, could you add `echo DISPLAY=$DISPLAY` > under that > and see if

Bug#941855: dunst: Daily systemd errors: "Failed to start Dunst notification daemon."

On 2019-10-12 at 09:25:20, Nikos Tsipinakis wrote: > This is usually caused by not having exported the DISPLAY variable into the > systemd environment, there has been extensive discussion about this in #347[1] > upstream. > > How are you starting X11, are you using a custom xinitrc? I've got this

Bug#941855: dunst: Daily systemd errors: "Failed to start Dunst notification daemon."

Package: dunst Version: 1.4.1-1 Severity: normal Once a day, at exactly the same time (+/- a couple of minutes), I get the following errors in my logs: Oct 6 07:39:49 akranes dunst[28243]: CRITICAL: Cannot open X11 display. Oct 6 07:39:49 akranes systemd[28227]: dunst.service: Main process

Bug#941360: fwupd: Failed to activate service: timed out

On 2019-09-30 at 19:53:03, mario.limoncie...@dell.com wrote: > Here is a fix for it. I believe it's because of a clash with fwupd-refresh > and fwupd specifically in systemd 242 and newer. > > https://github.com/fwupd/fwupd/commit/dc7e7c3808d564d5769b2845dbd66a3651f72e07 Looks like it worked. I

Bug#941360: fwupd: Failed to activate service: timed out

On 2019-09-29 at 23:57:02, mario.limoncie...@dell.com wrote: > What version did you upgrade from? And was that directory already existing or > did it get created with the package? I'm also affected by this problem. In my case, I also purged the package and reinstalled it. The problem persists

Bug#939563: My log

I also get this problem. Here's what I see everyday in my logs: Sep 11 07:39:09 akranes pulseaudio[2828]: E: [pulseaudio] core-util.c: Home directory not accessible: Permission non accordée Sep 11 07:39:09 akranes systemd[2814]: pulseaudio.service: Main process exited, code=exited,

Bug#941220: /lib/systemd/system/usbguard.service:7: PIDFile= references a path below legacy directory /var/run/

Package: usbguard Version: 0.7.4+ds-1+b1 Severity: minor Once a day I see the following in my system logs: Sep 12 06:03:32 hostname systemd[1]: /lib/systemd/system/usbguard.service:7: PIDFile= references a path below legacy directory /var/run/, updating /var/run/usbguard.pid →

Bug#941219: gajim.plugin_system.omemo: fmarier.org => Publishing bundle was NOT successful

Package: ejabberd Version: 18.12.1-2 Severity: normal Since upgrading to buster, my clients, running gajim (version are printing the following error at startup: 2019-09-26 08:48:14 (E) gajim.plugin_system.omemo franc...@fmarier.org => Publishing bundle was NOT successful It may very well be

Bug#864502: 'power' group

I was also curious about that 'power' group I've seen in the error log. According to https://github.com/intel/thermal_daemon/issues/162, it's for a user space GUI, which doesn't appear to be packaged for Debian. Francois -- https://fmarier.org/

Bug#940145: RFA: node-libravatar -- libravatar library for NodeJS

Package: wnpp Severity: normal I request an adopter for the node-libravatar package. The package description is: This library allows web application authors to make use of the free Libravatar service (https://www.libravatar.org). This service hosts avatar images for users and allows other

Bug#937469: rdepends will also be removed

While pylibravatar has a reverse dependency (python-txlibravatar), that package is also going to be removed in bug #938733. Francois -- https://fmarier.org/

Bug#928640: tiger: This makes the cronjob fail noisily every hour on my laptop

On 2019-08-16 at 13:27:38, Günter Frenz wrote: > On Tue, 13 Aug 2019 23:13:38 -0700 Francois Marier > wrote: > > /usr/sbin/tigercron: 127: /usr/lib/tiger/systems/default/config: > > expot: not found --ERROR-- [init001e] Don't have required command > > DIFF. > > o

Bug#933636: CVE-2019-14934

There is now an additional CVE that affects pdfresurrect in buster and stretch: https://security-tracker.debian.org/tracker/CVE-2019-14934 Neither this one or CVE-2019-14267 are deemed worthy of a DSA however. If you approve the first upload I have prepared for buster and stretch, I will

Bug#928640: tiger: This makes the cronjob fail noisily every hour on my laptop

n: * tiger/mail_rcpt: root * tiger/policy_adapt: >From 6ed09d5b458237c0cf43a06dec676e625c8e8059 Mon Sep 17 00:00:00 2001 From: Francois Marier Date: Tue, 13 Aug 2019 23:04:11 -0700 Subject: [PATCH] Fix tiger typos This resolves the following error message: /usr/sbin/tigercron: 127: /usr/lib

Bug#934003: RFP: rget -- download URLs and verify the contents against a publicly recorded cryptographic log

Package: wnpp Severity: wishlist * Package name: rget Version : 0.0.7 Upstream Author : Brandon Philips * URL : https://github.com/merklecounty/rget * License : Apache-2 Programming Lang: Go Description : download URLs and verify the contents against a

Bug#933637: buster-pu: package pdfresurrect/0.15-2

+ + * Fix buffer overflow (CVE-2019-14267). + + -- Francois Marier Tue, 30 Jul 2019 08:41:35 -0700 + pdfresurrect (0.15-2) unstable; urgency=medium * Bump Standars-Version up to 4.3.0 diff -Nru pdfresurrect-0.15/debian/patches/CVE-2019-14267.patch pdfresurrect-0.15/debian/patches/CVE-2019

Bug#933636: stretch-pu: package pdfresurrect/0.12-6

+ + * Fix buffer overflow (CVE-2019-14267). + + -- Francois Marier Tue, 30 Jul 2019 08:54:01 -0700 + pdfresurrect (0.12-6) unstable; urgency=medium * Run wrap-and-sort diff -Nru pdfresurrect-0.12/debian/patches/CVE-2019-14267.patch pdfresurrect-0.12/debian/patches/CVE-2019-14267.patch

Bug#932594: rkhunter: SCRIPTWHITELIST change to /usr/bin/egrep causes failure if usrmerge has not been run

On 2019-07-21 at 02:00:30, Julian Gilbey wrote: > I don't know whether there is a way of saying "whitelist this script > if it is found, otherwise ignore it". If there is, then this should > be applied to both /usr/bin/egrep and /bin/egrep, and likewise for > fgrep and any other /bin/... scripts.

Bug#932089: openssh-server: Cannot log into openssh-server on buster/mipsel

On 2019-07-15 at 10:33:26, Colin Watson wrote: > However, openssh should just fall back to not using seccomp sandboxing > in that case. It should make it easier to debug though! Perhaps you > could run sshd under strace and we might be able to see where it goes > wrong there? (Be careful with

Bug#932089: openssh-server: Cannot log into openssh-server on buster/mipsel

On 2019-07-14 at 23:23:35, Colin Watson wrote: > Judging from this, the crash (or is it a hang? I'm assuming a crash) is > near the start of ensure_minimum_time_since, probably inside > monotime_ts. I suspect there's something wrong with the seccomp > sandboxing of the privileged monitor process

Bug#932089: openssh-server: Cannot log into openssh-server on buster/mipsel

Package: openssh-server Version: 1:7.9p1-10 Severity: important In a fairly minimal buster installation on mipsel, I am unable to log into openssh-server from a Debian unstable client. Here's the debug log when I start sshd manually: $ systemctl stop sshd $ mkdir /run/sshd $ /usr/sbin/sshd -ddd

Bug#930340: tiger: [init001e] Don't have required command DIFF (Linux 5)

Package: tiger Version: 1:3.2.4~rc1-1 Severity: normal Every hour cron spits out: --ERROR-- [init001e] Don't have required command DIFF. This is the same bug as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785589 but for Linux 5 instead of Linux 4. The fix is the same: cd

Bug#759410: Should not install /usr/bin/rm conflicting with /bin/rm (blocks /bin -> /usr/bin)

On 2019-05-28 at 18:26:31, Andreas Beckmann wrote: > safe-rm also breaks a stretch --merged-usr chroot, found while testing > with piuparts stretch->buster upgrades with --merged-usr enabled. > And it seems to be the only package causing outright havoc in such a > scenario. So if I understand

Bug#929456: Patch up on Salsa

https://salsa.debian.org/debian/dunst/merge_requests/1

Bug#929456: dunst ignores the default web browser set by the user

Package: dunst Version: 1.3.2-1 Severity: normal Tags: patch Upstream dunst comes with the following in /etc/xdg/dunst/dunstrc: browser = /usr/bin/firefox -new-tab If a user sets another web browser as the default, opening a notification from dunst (Ctrl+Shift+. by default) will lead to

Bug#928955: RFP: yubikey-manager -- configuration of FIDO2, OTP and PIV functionality for YubiKey devices

Package: wnpp Severity: wishlist * Package name: yubikey-manager Version : 2.1.0 Upstream Author : YubiKey * URL : https://www.yubico.com/products/services-software/download/yubikey-manager/ * License : Simplified BSD Programming Lang: Python Description

Bug#928725: muttprint: Missing cups-bsd dependency

Package: muttprint Version: 0.73-8 Severity: important I was unable to print using CUPS before installing cups-bsd. Since muttprint requires lpr to print emails, it should depend on: cups-bsd | lpr | lprng Francois -- System Information: Debian Release: 10.0 APT prefers unstable APT

Bug#927392: Bug in previous script

/ #!/bin/sh # Copyright (c) 2019 Thomas Koch , Francois Marier and others. # This software is licensed under the GPL v2 or later. read_sysf () { # read and echo contents of sysfile # return 1 and echo default if read fails # $1: sysfile, $2: default; rc: 0=ok/1=error if ! cat "$1&quo

Bug#927392: fwknop-server: fwknop service dies when an interface goes down

nformation #!/bin/sh # Copyright (c) 2019 Thomas Koch , Francois Marier and others. # This software is licensed under the GPL v2 or later. save_iface_type () { # save interface type -- $1: interface; $2: type # rc: 0=saved/1=error [ -d $NETD/$1 ] && { printf '%s\n' "$2"

Bug#926331: Source of that warning

It looks like that warning comes from a Debian-specific patch: https://salsa.debian.org/postfix-team/postfix-dev/blob/7fd2e6facc18bbe22829735fc94d6eee7e58fc0f/debian/patches/70_postfix-check.diff#L15 introduced two years ago:

Bug#926331: warning: symlink leaves directory: /etc/postfix/./makedefs.out

Package: postfix Version: 3.4.5-1 Severity: normal I seem to be getting the following in my logs once a day: Apr 3 06:47:05 hostname postfix/postfix-script[8633]: warning: symlink leaves directory: /etc/postfix/./makedefs.out Apr 3 06:47:05 hostname postfix/postfix-script[8633]: warning:

Bug#925984: john: Considering switching upstream to John The Ripper Jumbo

Source: john Severity: wishlist The version of John The Ripper that's in Debian is very old and looks pretty much abandoned in favour of the proprietary version. However, a community project has come out of this under the banner of John The Ripper Jumbo:

Bug#924583: razor.cloudmark.com service no longer available?

I tried to re-initialize my razor config and found that there are no available servers anymore: # sudo -u debian-spamd razor-admin -d -register Razor-Log: Computed razorhome from env: /var/lib/spamassassin/.razor Razor-Log: Found razorhome: /var/lib/spamassassin/.razor Razor-Log: No

Bug#924583: spamassassin: razor2 had unknown error during get_server_info at /usr/share/perl5/Mail/SpamAssassin/Plugin/Razor2.pm line 186

Package: spamassassin Version: 3.4.2-1 Severity: normal Since yesterday, I've started seeing these errors messages from spamd in my logs: Mar 14 01:00:53 hostname spamd[12724]: razor2: razor2 check failed: razor2: razor2 had unknown error during get_server_info at

Bug#924178: python-paramiko: DeprecationWarning about EllipticCurvePublicNumbers when using duplicity

Package: python-paramiko Version: 2.4.2-0.1 Severity: normal Forwarded: https://github.com/paramiko/paramiko/issues/1369 I see the following in my duplicity cronjob logs: /usr/lib/python2.7/dist-packages/paramiko/kex_ecdh_nist.py:39: CryptographyDeprecationWarning: encode_point has been

Bug#923404: Patch

The attached patch seems to fix the problem for me. Francois -- https://fmarier.org/ diff -u /usr/bin/ssl-cert-check ssl-cert-check --- /usr/bin/ssl-cert-check 2019-02-26 21:24:00.0 -0800 +++ ssl-cert-check 2019-02-27 10:04:34.331729364 -0800 @@ -658,9 +658,9 @@ fi if [

Bug#923404: ssl-cert-check cannot monitor TLS1.2-only servers

Package: ssl-cert-check Version: 4.10-1 Severity: important Tags: upstream It appears that version 4.10 no longer supports checking the certificates of servers that only support TLS 1.2, as recommended by Mozilla: https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility Here's

Bug#831273: Updated package on Salsa

The updated package I am working on is here: https://salsa.debian.org/debian/fwknop Francois -- https://fmarier.org/

Bug#923086: fwknop 2.6.10 is available

Source: fwknop Version: 2.6.9-2 Severity: wishlist A new upstream version is available: https://github.com/mrash/fwknop/releases/tag/2.6.10 Francois -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture:

Bug#922988: New upstream version fixes #922989

As mentioned in bug #922989, the new upstream version avoids setting the SENDER value to an invalid one and so this bug will be fixed once the package is updated. Francois -- https://fmarier.org/

Bug#922989: ssl-cert-check: Default SENDER email address leads to undeliverable mails

Package: ssl-cert-check Version: 3.30-2 Severity: normal The default sender address is set "postmaster@localhost.localdomain" and when the destination emails are external to the local machine, that usually gets flagged as spam. This can be overriden with the `-E` flag, but ideally the default in

Bug#922988: ssl-cert-check: New upstream version available (4.10)

Package: ssl-cert-check Version: 3.30-2 Severity: normal A new upstream version of ssl-cert-check is available: 4.10 https://github.com/Matty9191/ssl-cert-check/blob/master/ssl-cert-check In particular, it includes mail client fixes. Francois -- https://fmarier.org/

Bug#912879: email-reminder: Depends on libgtk2-perl, that won't be part of Bullseye

On 2018-11-04 at 18:55:55, intrig...@debian.org wrote: > This package depends on libgtk2-perl, that I intend to remove > from testing soon after the Buster release, and then from sid at > some later point during the Bullseye development cycle: > >https://bugs.debian.org/912860 > > I notice

Bug#918085: Still an issue?

It looks like the experimental version of kmymoney is no longer installable in sid: $ LANG=C sudo apt install libkf5newstuffcore5 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer

Bug#919966: akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant

Package: akregator Version: 4:18.08.1-1 Severity: grave Justification: renders package unusable akregator doesn't start anymore. It exits with the following error message: akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol:

Bug#919312: ITP: git-secrets -- Prevents you from committing passwords and other sensitive information to a git repository.

Package: wnpp Severity: wishlist Owner: Francois Marier * Package name: git-secrets Version : 1.2.1 Upstream Author : Michael Dowling * URL : https://github.com/awslabs/git-secrets * License : Apache 2.0 Programming Lang: Bash Description : Prevents

Bug#919254: chkrootkit: Fix for incorrectly initialized variable in chk_tcpd()

+git20180626.aebd88e-1 ii openssh-client 1:7.9p1-4 ii procps 2:3.3.15-2 chkrootkit recommends no packages. chkrootkit suggests no packages. -- debconf information: chkrootkit/diff_mode: false chkrootkit/run_daily_opts: -q * chkrootkit/run_daily: false Author: Francois Marier

Bug#891858: More information on the libinput FAQ

Quoting the libinput FAQ [0], this is generally due to a slow/overloaded Xorg/Wayland client: "What causes the “timer offset negative” warning? libinput relies on the caller to call libinput_dispatch() whenever data is available on the epoll-fd. Doing so will process the state of all devices and

Bug#913008: devscripts: Useless use of concatenation (.) or string in void context at /usr/share/perl5/Devscripts/Uscan/Downloader.pm line 106.

Package: devscripts Version: 2.18.7 Severity: normal Tags: patch When running uscan, I get the following warning message: $ mkdir test $ cd test $ uscan --report Useless use of concatenation (.) or string in void context at /usr/share/perl5/Devscripts/Uscan/Downloader.pm line 106.

Bug#911054: workrave: desktop instability in multimonitor (3) setup

On 2018-10-15 at 09:03:54, wim wrote: > in about 80% of the cases, whenever workrave tries to "intervene" with a > break or other notice, > the desktop flickers and needs reloading, > sometimes the desktop needs to be restarted > > this could be related to #503684 ? I just closed that old bug.

Bug#910743: etbemon: Sample config in README.monitors is outdated and invalid

Source: etbemon Version: 1.3.3-3 Severity: normal Tags: patch The sample config in README.monitors under the "freespace.monitor" section is invalid and I suspect now outdated. Here's a fix for it: --- README.monitors 2018-10-10 08:28:58.426445460 -0700 +++ README.monitors.fixed

Bug#910741: etbemon: By default mon listens on port 2583 (UDP) on all network interfaces

Source: etbemon Version: 1.3.3-3 Severity: important After installing mon, I got the following tiger warning email: # Checking listening processes NEW: --WARN-- [lin003w] The process `mon' is listening on socket 2583 (UDP on every interface) is run by mon. I realized that the fix for

Bug#907399: Logs with systemd-coredump

On 2018-09-01 at 14:44:16, Till Kamppeter wrote: > Bernhard, thank for the patch. I have applied it now (and also done an > additional fix for DomainSocket) and committed it to the upstream GIT repo. > > Please test. Happy to test things. Just to be clear, do you want me to clone the repo, build

Bug#907399: Logs with systemd-coredump

I installed systemd-coredump and this is what I see in my logs now: Aug 27 23:04:37 hostname systemd[1]: Listening on Process Core Dump Socket. Aug 27 23:05:34 hostname cups-browsed[29428]: munmap_chunk(): invalid pointer Aug 27 23:05:34 hostname systemd[1]: Created slice

Bug#907399: cups-browsed: munmap_chunk(): invalid pointer

Package: cups Version: 2.2.8-5 Severity: normal Once a day, I get a message like this in my logs: Aug 27 00:00:02 hostname cups-browsed[6122]: munmap_chunk(): invalid pointer Aug 27 00:00:02 hostname systemd[1]: cups-browsed.service: Main process exited, code=dumped, status=6/ABRT Aug 27

Bug#907351: tor: TLS error while constructing a TLS context: dh key too small (in SSL routines:ssl3_ctx_ctrl:---)

Package: tor Version: 0.3.3.9-1 Severity: normal I get the following error in my logs approximately every 2 hours: Aug 26 05:05:01 hostname Tor[25963]: TLS error while constructing a TLS context: dh key too small (in SSL routines:ssl3_ctx_ctrl:---) I tried upgrading to the version in

Bug#902875: Patch

tags 902875 +patch thanks According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902413#12, all that's needed is to change `/var/run/` to `/run/` in /usr/lib/tmpfiles.d/postgresql.conf. I've attached a patch. Francois -- https://fmarier.org/ diff --git

Bug#759410: Different approach for safe-rm

I took a look at the details of the diversion that the latest version of dash sets up and it's really quite complicated. It's not clear that I could easily get it right, even copying that code, and the consequences of getting it wrong could be disastrous. So instead I went for an easier approach:

Bug#902929: units: /var/lib/units/currency.units should be installed in a maintainer script

Package: units Version: 2.17-1 Severity: normal It looks like /var/lib/units/currency.units is updated on cron once a day. This means that this file no longer matches the checksum that was generated at package creation time and so tools like reportbug and debsums will warn about it: System

Bug#902875: postgresql-common: systemd warning message: Line references path below legacy directory /var/run/

Package: postgresql-common Version: 191 Severity: normal Once a day, I get the following systemd warning message in my logs: Jul 1 20:50:01 hostname systemd-tmpfiles[21472]: [/usr/lib/tmpfiles.d/postgresql.conf:2] Line references path below legacy directory /var/run/, updating

<    1   2   3   4   5   6   7   8   9   10   >