Bug#982944: rename.ul was arbitrarily removed from util-linux citing non-existent policy

2021-02-18 Thread Scott Mcdermott
Incidentally, RedHat has long had rename from util-linux as /usr/bin/rename. So that's yet another reason to use an Alternative: so people with heterogeneous farms can expect the same binary path to behave the same way regardless of which system they're logged into. This should be an administrato

Bug#982944: rename.ul was arbitrarily removed from util-linux citing non-existent policy

2021-02-16 Thread Scott Mcdermott
Package: util-linux Version: 2.36.1-7 In bug #926637 rename.ul was removed as an alternative for /usr/bin/rename, citing "debian-policy" and because the implementations "cannot be used interchangeably." After using the util-linux 'rename' for at least a decade, maybe even two, I find this extreme

Bug#968584: vim-nox requires sound libraries and freedesktop stuff that doesn't belong in -nox

2020-08-17 Thread Scott Mcdermott
Package: vim-nox Version: 2:8.2.0716-3 The package named "vim-nox" now requires an abstract sound library that uses XDG specification for sound, is packaged by GNOME maintainers, and pulls in audio libraries and freedesktop sound theme? What does this have to do with editing files, and how is that

Bug#943337: linux-image-5.3.0-1-amd64: Keyboard driver for SPI connected MacBooks not included

2019-12-01 Thread Scott Mcdermott
yes please, this is required for macbook pro 2016 and 2017 and later keyboard to work, I am using the out-of tree dkms for this now, which is kind of silly to use since this is actually in the kernel 5.3 already dkms version (presumably same code) works fine on my laptop with debian vendor kernel

Bug#849077: new version of wpa-supplicant uploaded -- please test

2017-02-23 Thread Scott Mcdermott
On Thu, 26 Jan 2017 18:36:08 +0100 Andrew Shadura wrote: > I have cherry-picked a few patches from the upstream Git repository. I tried this on my mbpr 11,1 with wl.ko and still same result. Scan failure in endless loop return -22 just like in my previously attached log dump. > Please test this

Bug#849077: [pkg-wpa-devel] Bug#849077: wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi

2017-01-10 Thread Scott Mcdermott
I will again reference my comment https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849077#45 I'm encountering this bug without NetworkManager, wicd or anything else, just a simple wpa_supplicant config file which has worked fine until wpa_supplicant update and then stopped working, no other chang

Bug#849077: [pkg-wpa-devel] Bug#849077: wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi

2016-12-23 Thread Scott Mcdermott
my machine is having an identical looping scan failure messages as did the submitter after recent update. worked: 2.5-2+v2.4-3+b1 broken: 2.6-2 device: 03:00.0 Network controller: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter (rev 03) driver: Broadcom BCM43a0 802.11 Hybrid Wi

Bug#800835: firmware-linux-free: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1.bin for module i915

2016-10-29 Thread Scott Mcdermott
these appear to be at https://01.org/sites/default/files/downloads/intelr-graphics-linux/sklgucver61.tar.bz2 https://01.org/sites/default/files/downloads/intelr-graphics-linux/kbldmcver101.tar.bz2 what package do they properly belong in?

Bug#838312: ifupdown: Missing required variable: vlan_id1

2016-09-21 Thread Scott Mcdermott
It's the infiniband patch; reverting edb181c fixes the bug for me. It seems to make this noise on ifdown, but not ifup. It's not clear why this happens, since it looks like the reference to %vlan_id1% is protected by test -d /sys/class/net/%link%/device/infiniband which certainly is not tru

Bug#832576: postfix: Messages postfix-script: warning: group or other writable: in the logs

2016-08-04 Thread Scott Mcdermott
> The solution is to use "find -L", although Wietse seems to > have reservations about that (see his replies in the thread on > postfix-users). reference is http://marc.info/?l=postfix-users&m=145687936712995&q=raw msgid 3qfgk11pspzj...@spike.porcupine.org that patch should be ok right? if symlin

Bug#824853: tex-common: package installation fails

2016-05-20 Thread Scott Mcdermott
Installing the package 'context' (which also provides "syst-tex.mkii" albeit in a different location) seems to fix this also; tex packages upgrade and can finish install without issues afterwards.

Bug#814394: xserver-xorg-legacy: Fails to start xserver after upgrade to 1.18.1

2016-02-13 Thread Scott Mcdermott
Julien Cristau on 2016/02/13 +0100 @11:30:30: > > startx does not longer work after upgrade; `grep EE > > Xorg.log' shows: > > > >[ 1463.840] (EE) systemd-logind: failed to get > >session: The name org.freedesktop.login1 was not > >provided by any .service files > > X requires logind

Bug#802544: Xorg.wrap move to xorg-legacy broke X startup (permissions)

2015-10-22 Thread Scott Mcdermott
Julien Cristau on 2015/10/22 +0200 @07:47:28: > > That would surely be a regression. Debian went > > from a working X that dropped privileges, to a > > non-working X that can only be run as root. Huh?? > > No, Debian is going from an X server that always runs > as root to one that can run as unpr

Bug#802544: Xorg.wrap move to xorg-legacy broke X startup (permissions)

2015-10-21 Thread Scott Mcdermott
Julien Cristau on 2015/10/21 +0200 @20:48:56: > > xserver-xorg-core:amd64 (1.17.2-1.1, 1.17.2-3) > > > > This upgrade has broken X startup for me. Here is how > > I start X (as ordinary user): > > > > exec setsid env -i \ > > ... > > X :0 vt63 \ > > So one solution is to ins

Bug#802544: Xorg.wrap move to xorg-legacy broke X startup (permissions)

2015-10-20 Thread Scott Mcdermott
Package: xserver-xorg-legacy Version: 2:1.17.2-3 Severity: grave I recently did an upgrade of X, which broke it on my machine. Here are old (working) and new (broken) versions that apt-get installed, as shown in /var/log/apt/history.log: xserver-xorg-core:amd64 (1.17.2-1.1, 1.17.2-3) This up