Bug#978931: gssproxy: CVE-2020-12658

2021-01-05 Thread rharwood
Package: gssproxy Followup-For: Bug #978931 Control: tags -1 - security

Bug#968060: axi-cache: string/bytes confusion in display

2020-08-07 Thread rharwood
Package: apt-xapian-index Version: 0.51 Severity: minor Tags: patch Dear Maintainer, In rdepends output: rharwood@eesha:~$ axi-cache rdepends apt-xapian-index apt-xapian-index Reverse Depends: b'muon' b'packagesearch' b'synaptic'

Bug#920555: xmobar: compile flag with_alsa to support Volume command

2020-08-06 Thread rharwood
Package: xmobar Version: 0.33-1 Followup-For: Bug #920555 Users looking for a non-polling solution to ALSA volume may be able to adapt my script for it: #!/usr/bin/python3 import re import subprocess import sys r = re.compile(r"\[(\d+)%\].*\[(on|off)\]$") args = "stdbuf

Bug#966640: build-depends: debhelper-compat (= 13) cannot be satisfied

2020-08-03 Thread rharwood
ble backports to get a current debhelper if you want to build the > unstable version of krb5. Hi, no, my system information is as reportbug put it in the footer - testing with unstable and experimental available. Some more information: rharwood@eesha:~$ aptitude versions debhelper i A

Bug#932298: krb5-admin-server: Confusing error if DES encryption types are enabled

2020-07-31 Thread rharwood
Package: krb5-admin-server Version: 1.17-10 Followup-For: Bug #932298 Control: tags -1 + patch Hi, I believe I fixed this upstream in https://github.com/krb5/krb5/pull/1094 Thanks, --Robbie

Bug#966640: build-depends: debhelper-compat (= 13) cannot be satisfied

2020-07-31 Thread rharwood
Source: krb5 Severity: normal Hi Sam, Ben, Russ, I think the debhelper-compat version is out of date: rharwood@eesha:~$ sudo aptitude build-dep krb5 [sudo] password for rharwood: Unable to satisfy the build-depends: Build-Depends: debhelper-compat (= 13) Unable to apply some

Bug#966093: Error: default OCI runtime "runc" not found: invalid argument

2020-07-23 Thread rharwood
Package: podman Followup-For: Bug #966093 Dear Maintainer, Nothing in that file is related to the issue. I have reviewed policy.json, and swapaccount has nothing to do with runc/crun nor user namespaces. If this is working as intended, then "Docker-compatible CLI" and "daemon-less alternative t

Bug#966093: Error: default OCI runtime "runc" not found: invalid argument

2020-07-22 Thread rharwood
Package: podman Version: 2.0.2+dfsg1-3 Severity: grave Justification: renders package unusable Dear Maintainer, After installing podman, I get: $ podman run -it debian:sid Error: default OCI runtime "runc" not found: invalid argument $ Inspecting the dependencies, I see a dependenc

Bug#959186: gssproxy: kerberos credentials not looked into the classical file

2020-05-12 Thread rharwood
Package: gssproxy Followup-For: Bug #959186 Control: Close -1

Bug#958492: xfonts-terminus: Provide gtk-compatible fonts

2020-04-22 Thread rharwood
Package: xfonts-terminus Version: 4.40-2 Severity: grave Justification: renders package unusable Dear Maintainer, With pango 1.44, bitmap fonts are no longer supported: https://gitlab.gnome.org/GNOME/pango/issues/386 This means that trying to render Terminus in gtk applications looks like... wel

Bug#952757: mypy(1): build errors in man page

2020-02-28 Thread rharwood
Package: mypy Version: 0.761-1 Severity: minor Dear Maintainer, The mypy man page (mypy(1)) has a lot of what appar to be build errors from tranlation from rst to nroff. Here's the first one: ``` The directories are checked recursively to find Python source files. System Message:

Bug#942399: rxvt-unicode: server lockup making all clients unresponsive

2019-10-25 Thread rharwood
Package: rxvt-unicode Version: 9.22-6+b2 Followup-For: Bug #942399 Dear Maintainer, I've gotten a few more of these lockups (two today). They all look about the same. Here's one of the tracebacks: (gdb) thread apply all bt Thread 1 (Thread 0x7f7a8ee7f880 (LWP 11279)): #0 0x7f7a8fd6328e i

Bug#942399: rxvt-unicode: server lockup making all clients unresponsive

2019-10-15 Thread rharwood
Package: rxvt-unicode Version: 9.22-6+b2 Severity: important Dear Maintainer, Occasionally, I will see urxvtc process become unresponsive to keyboard input. It seems like processes may still be able to update their panes - my mosh session keeps updating the screen, for instance. Here's a backgr

Bug#941751: mlterm requires additional keypress to exit

2019-10-04 Thread rharwood
Package: mlterm Version: 3.8.8-3 Severity: normal Dear Maintainer, When mlterm is running a shell (e.g., mlterm -e /bin/bash), and the shell terminates (e.g., exit, C-d), mlterm requires another keypress before it exits. (Any keypress, as far as I can tell.) This is true for both bash and zsh,

Bug#932854: initramfs-tools-core: Please depend on logsave

2019-07-25 Thread rharwood
Package: initramfs-tools Version: 0.133 Followup-For: Bug #932854 Control: severity -1 critical Raising severity of this since it renders the machine unbootable. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 45M Jul 24 12:59 /boot/initrd.img-4.19.0-5-amd64 -rw-r--r-- 1 root

Bug#932132: libkrb5-3: Don't require all enctypes in a keytab to be valid

2019-07-15 Thread rharwood
Package: libkrb5-3 Version: 1.17-4 Severity: normal Tags: patch upstream Hi Sam, Ben, Russ, I really appreciate your assistance in backporting the 1DES-removal patchset. I wanted to make sure you were aware of [1]: this fixes a bug where having an invalid enctype in a keytab would cause credentia