Bug#949387: nagivs: New upstream release 1.19.17
Control: reassign -1 nagvis 1:1.9.11-1 On Lu, 20 ian 20, 16:08:50, Adam Cecile wrote: > Package: nagivs > Version: 1:1.9.11-1 > Severity: wishlist > Tags: patch > > Dear Maintainer, > > Several upstream versions have been released and the latest one is 1.9.17. > > Between current Debian's version and latest upstream there are several changes > but the following are important to me: > * Performance improvments > * Ability to pass a custom Openstreetmap WMS server > > I'll provided a PR on Salsa in a few minutes. > > Best regards, Adam. > > > > -- System Information: > Debian Release: 10.2 > APT prefers stable > APT policy: (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#949233: Kernel Failing To Load Wifi Firmware
Control: reassign -1 src:linux 4.19.67-2+deb10u2 On Sb, 18 ian 20, 16:20:53, Jesse57901 wrote: > Package: kernel > Version: Linux debian 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 > (2019-11-11) x86_64 GNU/Linux > > I'm having the same problem on 2 different computers when I install Debian > 10. The problem is that the system is not detecting any wifi hardware. I have > downloaded the correct firmware files (firmware-b43-installer and > firmware-iwlwifi) and they are located in the /lib/firmware directory. When I > run command 'ip link show' it does not detect any wifi hardware and only > shows lo and enp9s0(ethernet) . When I use various network managers like > connman and wicd they are not detecting any wifi hardware. I ran a dmesg > command and it says it cannot load the firmware and indicates it is missing > but everything appears to be installed correctly. Here is the terminal output > for dmesg: > >9.161602] b43-phy0: Broadcom 4312 WLAN found (core revision 15) > [9.207735] b43-phy0: Found PHY: Analog 6, Type 5 (LP), Revision 1 > [9.207750] b43-phy0: Found Radio: Manuf 0x17F, ID 0x2062, Revision 2, > Version 0 > [9.224592] Broadcom 43xx driver loaded [ Features: PNLS ] > [9.227035] Adding 2685948k swap on /dev/sdb5. Priority:-2 extents:1 > across:2685948k FS > [9.231785] b43 ssb0:0: firmware: failed to load b43/ucode15.fw (-2) > [9.231841] firmware_class: See https://wiki.debian.org/Firmware for > information about missing firmware > [9.231889] b43 ssb0:0: Direct firmware load for b43/ucode15.fw failed > with error -2 > [9.232354] b43 ssb0:0: firmware: failed to load b43/ucode15.fw (-2) > [9.232401] b43 ssb0:0: Direct firmware load for b43/ucode15.fw failed > with error -2 > [9.232441] b43 ssb0:0: firmware: failed to load b43-open/ucode15.fw (-2) > [9.232478] b43 ssb0:0: Direct firmware load for b43-open/ucode15.fw > failed with error -2 > [9.232492] b43 ssb0:0: firmware: failed to load b43-open/ucode15.fw (-2) > [9.232527] b43 ssb0:0: Direct firmware load for b43-open/ucode15.fw > failed with error -2 > [9.232531] b43-phy0 ERROR: You must go to > http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download > the correct firmware for this driver version. Please carefully read all > instructions on this website. > > Now here are the files located in /lib/firmware/b43: > a0g0bsinitvals5.fw n0bsinitvals22.fw > a0g0bsinitvals9.fw n0bsinitvals24.fw > a0g0initvals5.fwn0bsinitvals25.fw > a0g0initvals9.fwn0initvals11.fw > a0g1bsinitvals13.fw n0initvals16.fw > a0g1bsinitvals5.fw n0initvals17.fw > a0g1bsinitvals9.fw n0initvals22.fw > a0g1initvals13.fw n0initvals24.fw > a0g1initvals5.fwn0initvals25.fw > a0g1initvals9.fwn16bsinitvals30.fw > b0g0bsinitvals13.fw n16initvals30.fw > b0g0bsinitvals5.fw n18bsinitvals32.fw > b0g0bsinitvals9.fw n18initvals32.fw > b0g0initvals13.fw n1bsinitvals20.fw > b0g0initvals5.fwn1initvals20.fw > b0g0initvals9.fwn2bsinitvals19.fw > firmware-b43-installer.catalog n2initvals19.fw > ht0bsinitvals26.fw pcm5.fw > ht0bsinitvals29.fw sslpn0bsinitvals16.fw > ht0initvals26.fwsslpn0initvals16.fw > ht0initvals29.fwsslpn1bsinitvals20.fw > lcn0bsinitvals24.fw sslpn1bsinitvals27.fw > lcn0bsinitvals25.fw sslpn1initvals20.fw > lcn0bsinitvals26.fw sslpn1initvals27.fw > lcn0initvals24.fw sslpn2bsinitvals19.fw > lcn0initvals25.fw sslpn2initvals19.fw > lcn0initvals26.fw sslpn3bsinitvals21.fw > lcn1bsinitvals24.fw sslpn3initvals21.fw > lcn1bsinitvals25.fw sslpn4bsinitvals22.fw > lcn1bsinitvals26.fw sslpn4initvals22.fw > lcn1initvals24.fw ucode11.fw > lcn1initvals25.fw ucode13.fw > lcn1initvals26.fw ucode14.fw > lcn2bsinitvals24.fw ucode15.fw > lcn2bsinitvals25.fw ucode16_lp.fw > lcn2bsinitvals26.fw ucode16_mimo.fw > lcn2initvals24.fw ucode16_sslpn.fw > lcn2initvals25.fw ucode16_sslpn_nobt.fw > lcn2initvals26.fw ucode17_mimo.fw > lcn400bsinitvals33.fw ucode19_sslpn.fw > lcn400initvals33.fw ucode19_sslpn_nobt.fw > lp0bsinitvals13.fw ucode20_sslpn.fw > lp0bsinitvals14.fw ucode20_sslpn_nobt.fw > lp0bsinitvals15.fw ucode21_sslpn.fw > lp0bsinitvals16.fw ucode21_sslpn_nobt.fw > lp0initvals13.fwucode22_mimo.fw > lp0initvals14.fwucode22_sslpn.fw > lp0initvals15.fwucode24_lcn.fw > lp0initvals16.fwucode24_mimo.fw > lp1bsinitvals20.fw ucode25_lcn.fw >
Bug#947661: optirun fails
Control: reassign -1 bumblebee On Sb, 28 dec 19, 22:07:12, Marcin Szamotulski wrote: > Package: optirun > Version: bumblebee > Severity: normal > Tags: patch > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > I upgraded from debian-stable to sid. > >* What exactly did you do (or not do) that was effective (or > ineffective)? > > I run `optirun glxinfo` > > >* What was the outcome of this action? > > The outcome is: > ``` > optirun glxinfo > primus: fatal: failed to load any of the libraries: /usr/lib/x86_64-linux- > gnu/nvidia/libGL.so.1:/usr/lib/i386-linux- > gnu/nvidia/libGL.so.1:/usr/lib/nvidia/libGL.so.1 > /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1: cannot open shared object file: > No > such file or directory > /usr/lib/i386-linux-gnu/nvidia/libGL.so.1: cannot open shared object file: No > such file or directory > /usr/lib/nvidia/libGL.so.1: cannot open shared object file: No such file or > directory > > ``` > > > *** End of the template - remove these template lines *** > > > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.3.15 (SMP w/12 CPU cores; PREEMPT) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), > LANGUAGE=en_GB:en (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#947693: installation script changes swap UUID
Control: reassign -1 debian-installer Control: severity -1 wishlist On Du, 29 dec 19, 12:22:11, Peter Schmitt wrote: > > Package: Installation script for network install > > During the installation of debian on a new partition > (text, expert mode) I used the existing swap partition > (used also bei ubuntu). The script insisted on newly > formatting the partition, and (as I later found out) > also changed the partition's UUID. > As a result, booting ubuntu was very slow. > Searching the net for help I finally found this article > https://www.dedoimedo.com/computers/ubuntu-beaver-slow-boot.html > that pointed me to fstab (on ubuntu) using the original UUID. > > I suggest to not reformat an existing formatted swap partition. > > I used: firmware-10.2.0-amd64-netinst.iso > > Peter Schmittpeter.schm...@univie.ac.at >Adolf Gstöttner-Gasse 6/37, 1200 Wien -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#947108: Xorg problem preventing bootup
Control: reassign -1 xserver-xorg On Vi, 20 dec 19, 23:47:46, Casey Cullen wrote: > Package: X.org > Version: 1.20.6 > Architecture: PPC64 > > When trying to boot into Debian PPC64 on a "cyrus plus" board (Freescale > P5020 e5500 core based PPC64 system), an error is displayed. Below is the > log. This only occurs on PPC64 (does not occur on PowerPC). > Thank you for your assistance. > > [ 922.574] > X.Org X Server 1.20.6 > X Protocol Version 11, Revision 0 > [ 922.592] Build Operating System: Linux 4.19.0-5-powerpc64 ppc64 Debian > [ 922.598] Current Operating System: Linux Fienix > 5.5-a2_A-EON_X5000-05280-g89d577d3-dirty #1 SMP PREEMPT Wed Nov 27 > 12:53:57 CET 2019 ppc64 > [ 922.598] Kernel command line: root=/dev/sdb2 rootdelay=5 > [ 922.612] Build Date: 25 November 2019 09:49:09AM > [ 922.618] xorg-server 2:1.20.6-1 (https://www.debian.org/support) > [ 922.625] Current version of pixman: 0.36.0 > [ 922.638] Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [ 922.638] Markers: (--) probed, (**) from config file, (==) default > setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [ 922.666] (==) Log file: "/home/fienix/.local/share/xorg/Xorg.0.log", > Time: Sat Dec 21 00:37:38 2019 > [ 922.673] (==) Using system config directory "/usr/share/X11/xorg.conf.d" > [ 922.674] (==) No Layout section. Using the first Screen section. > [ 922.674] (==) No screen section available. Using defaults. > [ 922.674] (**) |-->Screen "Default Screen Section" (0) > [ 922.674] (**) | |-->Monitor "" > [ 922.675] (==) No monitor specified for screen "Default Screen Section". > Using a default monitor configuration. > [ 922.675] (==) Automatically adding devices > [ 922.675] (==) Automatically enabling devices > [ 922.675] (==) Automatically adding GPU devices > [ 922.675] (==) Max clients allowed: 256, resource mask: 0x1f > [ 922.675] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not > exist. > [ 922.675] Entry deleted from font path. > [ 922.675] (==) FontPath set to: > /usr/share/fonts/X11/misc, > /usr/share/fonts/X11/100dpi/:unscaled, > /usr/share/fonts/X11/75dpi/:unscaled, > /usr/share/fonts/X11/Type1, > /usr/share/fonts/X11/100dpi, > /usr/share/fonts/X11/75dpi, > built-ins > [ 922.675] (==) ModulePath set to "/usr/lib/xorg/modules" > [ 922.675] (II) The server relies on udev to provide the list of input > devices. > If no devices become available, reconfigure udev or disable > AutoAddDevices. > [ 922.675] (II) Loader magic: 0x1279f6ad0 > [ 922.675] (II) Module ABI versions: > [ 922.675] X.Org ANSI C Emulation: 0.4 > [ 922.675] X.Org Video Driver: 24.0 > [ 922.675] X.Org XInput driver : 24.1 > [ 922.675] X.Org Server Extension : 10.0 > [ 922.677] (++) using VT number 1 > > [ 922.680] (II) systemd-logind: took control of session > /org/freedesktop/login1/session/c1 > [ 922.683] (II) xfree86: Adding drm device (/dev/dri/card0) > [ 922.684] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 > paused 0 > [ 922.690] (--) PCI:*(1@0:0:0) 1002:6738:174b:e177 rev 0, Mem @ > 0xc/268435456, 0xc1000/131072, I/O @ 0x1000/256, BIOS @ > 0x/131072 > [ 922.690] (II) LoadModule: "glx" > [ 922.691] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so > [ 922.695] (II) Module glx: vendor="X.Org Foundation" > [ 922.695] compiled for 1.20.6, module version = 1.0.0 > [ 922.695] ABI class: X.Org Server Extension, version 10.0 > [ 922.695] (II) Applying OutputClass "Radeon" to /dev/dri/card0 > [ 922.695] loading driver: radeon > [ 922.695] (==) Matched radeon as autoconfigured driver 0 > [ 922.696] (==) Matched ati as autoconfigured driver 1 > [ 922.696] (==) Matched modesetting as autoconfigured driver 2 > [ 922.696] (==) Matched fbdev as autoconfigured driver 3 > [ 922.696] (==) Assigned the driver to the xf86ConfigLayout > [ 922.696] (II) LoadModule: "radeon" > [ 922.696] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so > [ 922.697] (II) Module radeon: vendor="X.Org Foundation" > [ 922.697] compiled for 1.20.4, module version = 19.1.0 > [ 922.697] Module class: X.Org Video Driver > [ 922.697] ABI class: X.Org Video Driver, version 24.0 > [ 922.697] (II) LoadModule: "ati" > [ 922.698] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so > [ 922.698] (II) Module ati: vendor="X.Org Foundation" > [ 922.698] compiled for 1.20.4, module version = 19.1.0 > [ 922.698] Module class: X.Org Video Driver > [ 922.698] ABI class: X.Org Video Driver, version 24.0 > [ 922.698] (II) LoadModule: "modesetting" > [ 922.698] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so > [ 922.699] (II) Module modesetting:
Bug#946268: Please add support for custom entries
On Lu, 16 dec 19, 11:01:09, Jonas Smedegaard wrote:
> Quoting andreimpope...@gmail.com (2019-12-16 09:42:46)
> >
> > I'll rework the patch accordingly, probably sometimes this week.
>
> Really, the only change I would want compared to your current proposed
> patch would be to have the newly line in the conffile uncommented.
That wouldn't be in line with the other variables that are commented out
by default.
Additionally, if the variable is always set the checks must be changed
slightly, otherwise the script would always error out.
> I am looking forward to see what changes you come up with.
Attached. Comments welcome :)
> > [1] Not sure how common it is, but my motivation for this was to
> > have an entry with a different root file system that is not
> > overwritten on every update, hence my example above. I might come up
> > with a patch implementing U_BOOT_ALT_ROOT as well, if I don't have
> > anything better to do ;)
>
> Please make that a separate patch files as a separate bug from this one.
> What I can imagine, such feature would be more involving and I suspect
> the usecase is more narrow. On the other hand, I am really pleased with
> your proposed patch so it might simply be my imagination being too
> limited: Please do make a patch and try argue the case for its adoption!
Will do so in a separate bug, if I do ever get around to it.
BTW, U_BOOT_FDT_DIR is not documented in the manpage (there is a pull
request in the upstream github repo that appears to address this) and
shellcheck has some recommendations.
Would you take patches for these as well?
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
From d24f8dd89f73ff5abdfb147a85f339413661f57e Mon Sep 17 00:00:00 2001
From: Andrei POPESCU
Date: Sun, 8 Dec 2019 11:53:36 +0200
Subject: [PATCH] Add option to append one or more custom entries from an
external file
This patch adds a new option U_BOOT_CUSTOM_ENTRIES to specify an
external file to be appended to extlinux.conf.
default:
Add the new option commented out, with the default value.
u-boot-update:
Do some basic checks on the file (exists, regular file, readable,
non-zero length).
Issue a warning in case the file is not owned by root, but don't
error out (the sysadmin may have good reasons for that).
u-boot-update.8:
Document the new option in the manpage, including some safety/security
warnings.
U_BOOT_CUSTOM_ENTRIES is always set
---
default | 1 +
u-boot-update | 30 ++
u-boot-update.8 | 2 ++
3 files changed, 33 insertions(+)
diff --git a/default b/default
index 4389a87..7e6804d 100644
--- a/default
+++ b/default
@@ -11,4 +11,5 @@
#U_BOOT_TIMEOUT="50"
#U_BOOT_FDT=""
#U_BOOT_FDT_DIR="/usr/lib/linux-image-"
+#U_BOOT_CUSTOM_ENTRIES="/etc/default/u-boot-custom"
diff --git a/u-boot-update b/u-boot-update
index 2bf151b..2cfe3ca 100755
--- a/u-boot-update
+++ b/u-boot-update
@@ -82,6 +82,7 @@ U_BOOT_TIMEOUT="${U_BOOT_TIMEOUT:-50}"
U_BOOT_MENU_LABEL="Debian GNU/Linux kernel"
U_BOOT_PARAMETERS="${U_BOOT_PARAMETERS:-ro quiet}"
U_BOOT_FDT_DIR="${U_BOOT_FDT_DIR:-/usr/lib/linux-image-}"
+U_BOOT_CUSTOM_ENTRIES="${U_BOOT_CUSTOM:-/etc/default/u-boot-custom}"
# Find parameter for root from fstab
if [ -z "${U_BOOT_ROOT}" ]
@@ -216,5 +217,34 @@ done
_NUMBER=""
+# Append custom entries if any
+if [ -f "${U_BOOT_CUSTOM_ENTRIES}" ]
+then
+if [ ! -r "${U_BOOT_CUSTOM_ENTRIES}" ]
+then
+echo 'E: The file '"${U_BOOT_CUSTOM_ENTRIES}"' is unreadable'
+exit 1
+fi
+
+if [ ! -s "${U_BOOT_CUSTOM_ENTRIES}" ]
+then
+echo 'E: The file '"${U_BOOT_CUSTOM_ENTRIES}"' is empty'
+exit 1
+fi
+
+if [ ! -O "${U_BOOT_CUSTOM_ENTRIES}" ]
+then
+echo 'W: The file '"${U_BOOT_CUSTOM_ENTRIES}"' is NOT owned by root'
+fi
+
+echo 'P: Appending custom entries from '"${U_BOOT_CUSTOM_ENTRIES}"'...'
+
+# Writing custom entries
+_CONFIG="${_CONFIG}
+
+$(< "${U_BOOT_CUSTOM_ENTRIES}")
+"
+fi
+
Update "${_U_BOOT_DIRECTORY}/extlinux.conf" "${_CONFIG}"
diff --git a/u-boot-update.8 b/u-boot-update.8
index 3397bc8..7e88000 100644
--- a/u-boot-update.8
+++ b/u-boot-update.8
@@ -26,6 +26,8 @@ This variable specifies additional boot parameters that are appended to each ker
This variable specifies the root partition. It is automatically extracted from /etc/fstab. U\-BOOT supports both devices and UUIDs.
.IP "U_BOOT_TIMEOUT=""\fB50\fR""" 4
This variable specifies the time that U\-BOOT should wait for user input during boot. Values are in decisecond greater than 0 (e.g. '10' for a 1 second timeout), 0 specifies to wait forever. The default is 50.
+.IP "U_BOOT_CUSTOM_ENTRIES=""/path/to/file""" 4
+This variable specifies the name of a file containing one or more custom entries. The file is appended \fBas is\fR, without any checks for validity or safety. For security reasons the file should not be writable to untrusted users as it can be used to gain root access to the system
Bug#946268: Please add support for custom entries
On Du, 15 dec 19, 18:50:23, Jonas Smedegaard wrote: > > I don't understand what you mean gets "activated by default": By default > no custom file exists, and therefore none is "activated". Right. > Reason I prefer having that entry uncommented by default is to not need > editing main file when adding a custom file. Main file is a conffile so > the fewer situations it needs editing the better. Oh, didn't think about it being a conffile, so yes, I agree. > > For me it would make more sense to add some more variables to generate > > different entries, e.g. something like U_BOOT_ALT_ROOT (alternative > > root file system for which to generate entries). > > Sorry, I don't understand what you are saying here. Seems to you are > switching topic to discuss something else, is that correct? Let me rephrase that. As I see it, the custom entries are potentially dangerous (unbootable system, security, etc.) so it made sense for me to have them under several "layers" of "protection". I was suggesting that instead of having it enabled by default in the configuration to provide the admin with additional switches for "common" customizations[1], that might make it unnecessary to use this bigger hammer at all. Of course, as you mentioned above, with /etc/default/u-boot being a conffile this tends to make the admin's life harder than it should. I'll rework the patch accordingly, probably sometimes this week. [1] Not sure how common it is, but my motivation for this was to have an entry with a different root file system that is not overwritten on every update, hence my example above. I might come up with a patch implementing U_BOOT_ALT_ROOT as well, if I don't have anything better to do ;) Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#946510: Support for accelerated graphics and video decoding on PINE A64+ in bullseye
On Du, 15 dec 19, 12:17:07, Vagrant Cascadian wrote: > Control: tags 946510 pending > > On 2019-12-14, Andrei POPESCU wrote: > > > > For the Allwinner A64 the sun8i-mixer module is missing, see #946510. > > Thanks for looking into this! > > Did some basic compile testing and pushed to the git kernel repository, > should land in the next linux 5.3.x and 5.4.x uploads. Great :) Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#946268: Please add support for custom entries
On Mi, 11 dec 19, 03:19:16, Jonas Smedegaard wrote: > > Thanks¹ for the attached patch. > > Looks great! Thanks :) > One detail: Seems more sensible to me to by default check for and > include addon config if it exists - i.e. not only if uncommented in main > config as in your proposed patch. > > Do you have some opinion on that? After thinking about this for a while it seems to me like the custom entries are a solution of last resort and should not be activated by default. For me it would make more sense to add some more variables to generate different entries, e.g. something like U_BOOT_ALT_ROOT (alternative root file system for which to generate entries). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#944479: EDAC amd64 regression
Control: fixed -1 5.4.2-1~exp1 On Sb, 14 dec 19, 18:05:19, andreimpope...@gmail.com wrote: > Control: fixed 5.4.2-1~exp1 > > On Sb, 14 dec 19, 08:43:10, Antonio Russo wrote: > > Thanks for checking in on this. > > > > On 12/14/19 3:59 AM, andreimpope...@gmail.com wrote: > > > In the meantime unstable has 5.3.17, you should check if maybe this was > > > fixed. > > > > I moved to Linux 5.4 (trunk, 5.4.2), and the problem is resolved > > there. > > Thank you for confirming. > > > I'm not sure the correct way to close this bug report given that > > version is still in experimental. > > Doing so with this message, assuming you meant the current version in > experimental. Ugh, messed up the syntax, should be correct now. Kind regards, Andrei -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Bug#946393: Fwd: vagrant virtualbox kernel is behind
Control: reassign -1 cloud.debian.org On Du, 08 dec 19, 08:08:09, Drew Mullen wrote: > package: debian0cloud virtual > X-Debuggs-CC: emman...@libera.cc > image source: vagrant cloud: > image version: debian/buster64 > vagrant provider: virtualbox > package: kernel > kernel: 4.19.0-5 > > @emmanuel, i cc'd you directly. I haven't submitted a bug to debian before > and I wasnt sure if i got the headers correctly. I apologize if this double > contacts you. For submitting bugs you should use submit@ instead of quiet@, unless you have good reasons to do so. > While attempting to enable ZFS on the debian/buster64 vagrant box > (provider: virtualbox), ZFS modprobe is incompatible with 4.19.0-5 kernel, > works with updated 4.19.0-6. If possible, can you please update the > published virtualbox image to vagrant cloud. > > $ apt update && apt install -y vim > > $ cat << EOF >> /etc/apt/sources.list > deb http://deb.debian.org/debian buster-backports main contrib > deb-src http://deb.debian.org/debian buster-backports main contrib > EOF > > $ cat << EOF >> /etc/apt/preferences.d/90_zfs > Package: libnvpair1linux libuutil1linux libzfs2linux libzpool2linux > spl-dkms zfs-dkms zfs-test zfsutils-linux zfsutils-linux-dev zfs-zed > Pin: release n=buster-backports > Pin-Priority: 990 > EOF > > $ apt update > > $ apt install --yes debootstrap gdisk dkms dpkg-dev linux-headers-$(uname > -r) > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: Unable to locate package linux-headers-4.19.0-5-amd64 > E: Couldn't find any package by glob 'linux-headers-4.19.0-5-amd64' > E: Couldn't find any package by regex 'linux-headers-4.19.0-5-amd64' > > $ apt install --yes -t buster-backports zfs-dkms --no-install-recommends > ... > > $ modprobe zfs > modprobe: FATAL: Module zfs not found in directory > /lib/modules/4.19.0-5-amd64 > > more info: > https://github.com/zfsonlinux/zfs/issues/9599#issuecomment-562943133 Kind regards, Andrei -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Bug#944479: EDAC amd64 regression
Control: reassign -1 src:linux On Du, 10 nov 19, 10:00:54, Antonio Russo wrote: > Package: linux-image-5.3.0-2-amd64 > Version: 5.3.9-1 > Severity: normal > > --- Please enter the report below this line. --- > > Upgraded from kernel 5.2.17, and started getting lines like > > Nov 10 09:13:08 REDACTED kernel: EDAC amd64: Node 0: DRAM ECC enabled. > Nov 10 09:13:08 REDACTED kernel: EDAC amd64: F17h detected (node 0). > Nov 10 09:13:08 REDACTED kernel: EDAC amd64: Error: F0 not found, device > 0x1460 (broken BIOS?) > Nov 10 09:13:08 REDACTED kernel: EDAC amd64: Error: Error probing instance: 0 > > I do have ECC ram, and it claims to be supported, lshw shows > "errordetection=multi-bit-ecc", > on both 5.2.17 and 5.3.9. > > This would seem to be a regression, since I didn't have this error on 5.2.17. In the meantime unstable has 5.3.17, you should check if maybe this was fixed. > --- System information. --- > Motherboard: X470 Taichi Ultimate > Processor: AMD Ryzen 7 3700X > > Architecture: > Kernel: Linux 5.3.0-2-amd64 > > Debian Release: bullseye/sid Kind regards, Andrei -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Bug#946268: Please add support for custom entries
On Du, 08 dec 19, 14:38:49, Jonas Smedegaard wrote:
> Quoting andreimpope...@gmail.com (2019-12-08 11:10:25)
> >
> > Ok, attached a patch against u-boot-menu on Salsa/debian implementing
> > this.
> >
> > Comments welcome :)
>
> Please share the patch as attachment here instead.
I did, see my other message (forgot to attach it the first time).
Attached again for your convenience.
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
From c36cbdd65e3bc9c4c6dc41fceda5463d52dcf5d7 Mon Sep 17 00:00:00 2001
From: Andrei POPESCU
Date: Sun, 8 Dec 2019 11:53:36 +0200
Subject: [PATCH] Add option to append one or more custom entries from an
external file
This patch adds a new option U_BOOT_CUSTOM_ENTRIES to specify an
external file to be appended to extlinux.conf.
default:
Add the new option commented out, with a suggested filename.
u-boot-update:
Do some basic checks on the file (exists, regular file, readable,
non-zero length).
Issue a warning in case the file is not owned by root, but don't
error out (the sysadmin may have good reasons for that).
u-boot-update.8:
Document the new option in the manpage, including some safety/security
warnings.
---
default | 1 +
u-boot-update | 35 +++
u-boot-update.8 | 2 ++
3 files changed, 38 insertions(+)
diff --git a/default b/default
index 4389a87..7e6804d 100644
--- a/default
+++ b/default
@@ -11,4 +11,5 @@
#U_BOOT_TIMEOUT="50"
#U_BOOT_FDT=""
#U_BOOT_FDT_DIR="/usr/lib/linux-image-"
+#U_BOOT_CUSTOM_ENTRIES="/etc/default/u-boot-custom"
diff --git a/u-boot-update b/u-boot-update
index 2bf151b..9302f7a 100755
--- a/u-boot-update
+++ b/u-boot-update
@@ -216,5 +216,40 @@ done
_NUMBER=""
+# Append custom entries if any
+if [ -n "${U_BOOT_CUSTOM_ENTRIES}" ]
+then
+if [ ! -f "${U_BOOT_CUSTOM_ENTRIES}" ]
+then
+echo 'E: The file '"${U_BOOT_CUSTOM_ENTRIES}"' does not exist or is not a regular file'
+exit 1
+fi
+
+if [ ! -r "${U_BOOT_CUSTOM_ENTRIES}" ]
+then
+echo 'E: The file '"${U_BOOT_CUSTOM_ENTRIES}"' is unreadable'
+exit 1
+fi
+
+if [ ! -s "${U_BOOT_CUSTOM_ENTRIES}" ]
+then
+echo 'E: The file '"${U_BOOT_CUSTOM_ENTRIES}"' is empty'
+exit 1
+fi
+
+if [ ! -O "${U_BOOT_CUSTOM_ENTRIES}" ]
+then
+echo 'W: The file '"${U_BOOT_CUSTOM_ENTRIES}"' is NOT owned by root'
+fi
+
+echo 'P: Appending custom entries from '"${U_BOOT_CUSTOM_ENTRIES}"'...'
+
+# Writing custom entries
+_CONFIG="${_CONFIG}
+
+$(< "${U_BOOT_CUSTOM_ENTRIES}")
+"
+fi
+
Update "${_U_BOOT_DIRECTORY}/extlinux.conf" "${_CONFIG}"
diff --git a/u-boot-update.8 b/u-boot-update.8
index 3397bc8..7c209b4 100644
--- a/u-boot-update.8
+++ b/u-boot-update.8
@@ -26,6 +26,8 @@ This variable specifies additional boot parameters that are appended to each ker
This variable specifies the root partition. It is automatically extracted from /etc/fstab. U\-BOOT supports both devices and UUIDs.
.IP "U_BOOT_TIMEOUT=""\fB50\fR""" 4
This variable specifies the time that U\-BOOT should wait for user input during boot. Values are in decisecond greater than 0 (e.g. '10' for a 1 second timeout), 0 specifies to wait forever. The default is 50.
+.IP "U_BOOT_CUSTOM_ENTRIES=""/path/to/file""" 4
+This variable specifies the name of a file containing one or more custom entries. The file is appended \fBas is\fR, without any checks for validity or safety. For security reasons the file should not be writable to untrusted users as it can be used to gain root access to the system (e.g. by adding a boot entry with "init=/bin/sh" as kernel parameter). u\-boot\-update will issue a warning if the file is not owned by root.
.SH FILES
/etc/default/u-boot
--
2.20.1
signature.asc
Description: PGP signature
Bug#946268: Please add support for custom entries
On Vi, 06 dec 19, 15:17:37, Jonas Smedegaard wrote: > Hi Andrei, > > Quoting Andrei POPESCU (2019-12-06 14:45:11) > > Currently any changes done to /boot/extlinux/extlinux.conf will be > > overwritten on the next kernel update. > > > > It would be nice to have some mechanism to include custom entries. In > > my case I need an entry with a different root partition (to boot a > > different install). > > > > One idea would be to have a U_BOOT_CUSTOM configuration variable to > > specify a file to be included as is. > > > > If you think the idea is good I might be able to come up with a patch > > for it. > > I like the idea, and welcome a draft patch! Ok, attached a patch against u-boot-menu on Salsa/debian implementing this. Comments welcome :) Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#946268: Please add support for custom entries
[now with the patch attached :) ]
On Vi, 06 dec 19, 15:17:37, Jonas Smedegaard wrote:
> Hi Andrei,
>
> Quoting Andrei POPESCU (2019-12-06 14:45:11)
> > Currently any changes done to /boot/extlinux/extlinux.conf will be
> > overwritten on the next kernel update.
> >
> > It would be nice to have some mechanism to include custom entries. In
> > my case I need an entry with a different root partition (to boot a
> > different install).
> >
> > One idea would be to have a U_BOOT_CUSTOM configuration variable to
> > specify a file to be included as is.
> >
> > If you think the idea is good I might be able to come up with a patch
> > for it.
>
> I like the idea, and welcome a draft patch!
Ok, attached a patch against u-boot-menu on Salsa/debian implementing
this.
Comments welcome :)
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
From c36cbdd65e3bc9c4c6dc41fceda5463d52dcf5d7 Mon Sep 17 00:00:00 2001
From: Andrei POPESCU
Date: Sun, 8 Dec 2019 11:53:36 +0200
Subject: [PATCH] Add option to append one or more custom entries from an
external file
This patch adds a new option U_BOOT_CUSTOM_ENTRIES to specify an
external file to be appended to extlinux.conf.
default:
Add the new option commented out, with a suggested filename.
u-boot-update:
Do some basic checks on the file (exists, regular file, readable,
non-zero length).
Issue a warning in case the file is not owned by root, but don't
error out (the sysadmin may have good reasons for that).
u-boot-update.8:
Document the new option in the manpage, including some safety/security
warnings.
---
default | 1 +
u-boot-update | 35 +++
u-boot-update.8 | 2 ++
3 files changed, 38 insertions(+)
diff --git a/default b/default
index 4389a87..7e6804d 100644
--- a/default
+++ b/default
@@ -11,4 +11,5 @@
#U_BOOT_TIMEOUT="50"
#U_BOOT_FDT=""
#U_BOOT_FDT_DIR="/usr/lib/linux-image-"
+#U_BOOT_CUSTOM_ENTRIES="/etc/default/u-boot-custom"
diff --git a/u-boot-update b/u-boot-update
index 2bf151b..9302f7a 100755
--- a/u-boot-update
+++ b/u-boot-update
@@ -216,5 +216,40 @@ done
_NUMBER=""
+# Append custom entries if any
+if [ -n "${U_BOOT_CUSTOM_ENTRIES}" ]
+then
+if [ ! -f "${U_BOOT_CUSTOM_ENTRIES}" ]
+then
+echo 'E: The file '"${U_BOOT_CUSTOM_ENTRIES}"' does not exist or is not a regular file'
+exit 1
+fi
+
+if [ ! -r "${U_BOOT_CUSTOM_ENTRIES}" ]
+then
+echo 'E: The file '"${U_BOOT_CUSTOM_ENTRIES}"' is unreadable'
+exit 1
+fi
+
+if [ ! -s "${U_BOOT_CUSTOM_ENTRIES}" ]
+then
+echo 'E: The file '"${U_BOOT_CUSTOM_ENTRIES}"' is empty'
+exit 1
+fi
+
+if [ ! -O "${U_BOOT_CUSTOM_ENTRIES}" ]
+then
+echo 'W: The file '"${U_BOOT_CUSTOM_ENTRIES}"' is NOT owned by root'
+fi
+
+echo 'P: Appending custom entries from '"${U_BOOT_CUSTOM_ENTRIES}"'...'
+
+# Writing custom entries
+_CONFIG="${_CONFIG}
+
+$(< "${U_BOOT_CUSTOM_ENTRIES}")
+"
+fi
+
Update "${_U_BOOT_DIRECTORY}/extlinux.conf" "${_CONFIG}"
diff --git a/u-boot-update.8 b/u-boot-update.8
index 3397bc8..7c209b4 100644
--- a/u-boot-update.8
+++ b/u-boot-update.8
@@ -26,6 +26,8 @@ This variable specifies additional boot parameters that are appended to each ker
This variable specifies the root partition. It is automatically extracted from /etc/fstab. U\-BOOT supports both devices and UUIDs.
.IP "U_BOOT_TIMEOUT=""\fB50\fR""" 4
This variable specifies the time that U\-BOOT should wait for user input during boot. Values are in decisecond greater than 0 (e.g. '10' for a 1 second timeout), 0 specifies to wait forever. The default is 50.
+.IP "U_BOOT_CUSTOM_ENTRIES=""/path/to/file""" 4
+This variable specifies the name of a file containing one or more custom entries. The file is appended \fBas is\fR, without any checks for validity or safety. For security reasons the file should not be writable to untrusted users as it can be used to gain root access to the system (e.g. by adding a boot entry with "init=/bin/sh" as kernel parameter). u\-boot\-update will issue a warning if the file is not owned by root.
.SH FILES
/etc/default/u-boot
--
2.20.1
signature.asc
Description: PGP signature
Bug#946260: Please enable SPDIF support for Allwinner based systems
Source: linux Severity: wishlist X-Debbugs-CC: har...@ccbib.org Cloning doesn't work for archived bugs, submitting a new one, sorry for duplicates. On Jo, 02 mai 19, 17:31:00, Harald Geyer wrote: > Andrei POPESCU writes: > > On Jo, 31 ian 19, 17:21:54, Harald Geyer wrote: > > > > > Please enable the following Kconfig symbols as modules: > > > > > > CONFIG_SND_SUN50I_CODEC_ANALOG > > > CONFIG_SND_SUN8I_CODEC > > > CONFIG_SND_SUN4I_I2S > > > CONFIG_SND_SOC_SIMPLE_AMPLIFIER > > > CONFIG_SND_SIMPLE_CARD > > > > > > These are necessary for sound support on pinebook, Olimex TERES-I, etc. > > > The drivers are available upstream since 4.20. > > > Pinebook has sound enabled in devicetree starting with 5.0 This is done and working, thanks! > > Would this enable also the S/PDIF or is something else needed > > (CONFIG_SND_SUN4I_SPDIF maybe?)? > > Indeed, for S/PDIF on A64 CONFIG_SND_SUN4I_SPDIF is needed. Based on the name I'm guessing this is not A64 specific, so retitling the bug accordingly. > However AFAICS debian ships no sun50i-a64 devicetrees where S/PDIF is > enabled. You would need a custom DT or an overlay, to make the > debian kernel actually load the module. Is this still needed or do recent kernels have this already enabled? Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#934383: Debian bug # 934383
On Vi, 06 sep 19, 08:47:10, William Melgaard wrote: > If you will forward to me or give me a link to the source code for the install > package, I will take a crack at debugging it. > While I am at it, include a list of other bugs applicable to that package. > > William Melgaard Hi William, Please note I'm not a maintainer, but just someone looking after bugs filed against inexistent packages (in this case just a typo). You might want to write to @bugs.debian.org instead. Kind regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: PGP signature
Bug#938928: installer: Cannot install Debian Buster on a Samsung SSD 970 Evo Plus SSD
Control: reassign -1 src:linux On Vi, 30 aug 19, 10:24:26, Alexander Veit wrote: > Package: installer There is no such package, let's reassign to the kernel instead. @debian-kernel: Alexander wrote in a follow-up message that installation fails also with the testing installer (using 5.2.0-2-amd64). Full quote below for context. Kind regards, Andrei > Version: Debian 10 (Buster) > Severity: important > Tags: d-i > > Dear Maintainer, > > > Mainboard: MSI Z390 A-Pro > CPUI7 9700K > RAM: Corsair Vengeance LPX 32GB CMK32GX4M2D3000C16 > SSD: Samsung SSD 970 Evo Plus > > System:Host: helium Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc > v: 8.3.0 Console: tty 1 >Distro: Debian GNU/Linux 10 (buster) > Machine: Type: Desktop Mobo: Micro-Star model: Z390-A PRO (MS-7B98) v: 1.0 > serial: J516583286 >UEFI [Legacy]: American Megatrends v: 1.60 date: 03/21/2019 > CPU: Topology: 8-Core model: Intel Core i7-9700K bits: 64 type: MCP > arch: Kaby Lake rev: D L2 cache: 12.0 MiB >flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: > 57600 >Speed: 800 MHz min/max: 800/4900 MHz Core speeds (MHz): 1: 800 2: > 801 3: 800 4: 800 5: 800 6: 800 7: 800 8: 801 > Graphics: Device-1: Intel vendor: Micro-Star MSI driver: N/A bus ID: 00:02.0 >Display: tty server: X.org 1.20.4 driver: vesa unloaded: > fbdev,modesetting tty: 174x59 >Message: Advanced graphics data unavailable in console for root. > Audio: Device-1: Intel Cannon Lake PCH cAVS vendor: Micro-Star MSI > driver: snd_hda_intel v: kernel bus ID: 00:1f.3 >Sound Server: ALSA v: k4.19.0-5-amd64 > Network: Device-1: Intel Ethernet I219-V vendor: Micro-Star MSI driver: > e1000e v: 3.2.6-k port: efa0 bus ID: 00:1f.6 >IF: eno1 state: up speed: 1000 Mbps duplex: full mac: > 00:d8:61:74:81:5b > > The Samsung SSD 970 Evo Plus SSD is attached to the mainboard's M.2 connector. > > 1.) Install Debian Buster using the graphical expert installer. > 2.) Partitioning of the SSD seemed to work > 3.) The step where the base system packages are installed failed. > > => Installation failed. > > Debian Buster does not seem to support Samsung SSD 970 Evo Plus SSD, at least > not with the MSI Z390 A-Pro and I7 9700K processor. I had to replace the SSD > with an older model attached to a SATA connector. > > > -- System Information: > Debian Release: 10.0 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#934690: networkmanager does not parse interface config file correctly
On Mi, 14 aug 19, 15:18:15, Hans-Cees Speel wrote: > On 13-08-19 21:15, andreimpope...@gmail.com wrote: > > > > Raspbian is making several changes compared to a pristine Debian system. > > Combine this with images being produced by third parties, with possible > > additional customizations and it becomes impossible to diagnoze an issue > > from Debian perspective. > > > > Please kindly report bugs in Debian only if you can reproduce the > > behaviour with a pure Debian install. > > > > I would suggest you contact Raspbian support channels to find a solution > > to your problem and if this is indeed a bug report it to Raspbian. > > While I respect your difficulties from the debian perspective: Please note I'm only triaging bugs filed against unknown packages. > * some more info would be welcome. Is my assertion correct that given >my configuration file form netwerokmanager resolv.conf should only >have one dns-address. If this is not the case my and your time is >wasted to find out more The file /etc/resolvconf/resolv.conf.d/head in Debian stretch looks like this: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN You can verify that yourself by downloading the package from a Debian mirror and inspecting it, e.g. with mc. It seems like your issue is due to a Raspbian and/or image specific customization. Hope this helps, Andrei -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Bug#934626: linux-image-5.2.0-2-powerpc64: Fail to boot G5
On Lu, 12 aug 19, 16:55:22, Christian Marillat wrote: > Package: linux-image-5.2.0-2-powerpc64 > Version: 5.2.7-1 > Severity: normal Hello, That package is only available from debports, did you mean linux-image-5.2.0-2-powerpc64le ? Kind regards, Andrei -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Bug#760035: retitle 760025 to ITP: xserver-xorg-video-fbturbo -- X.Org X server -- fbturbo display driver ...
On Jo, 13 oct 16, 14:45:27, Dominik George wrote: > retitle 760025 ITP: xserver-xorg-video-fbturbo -- X.Org X server -- fbturbo > display driver > owner 760025 ! > thanks Any progress on this? I would be willing to test binary packages, preferably installable on buster/stable, but could also install bullseye/testing or sid if needed. I'm already running linux 5.2 from sid. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#934383: debian-install: Package fails attempting to access USB WiFi
Control: reassign -1 debian-installer On Sb, 10 aug 19, 09:50:50, William Melgaard wrote: > Package: debian-install > Version: debian-10.0.0-amd64-netinst.iso > Severity: serious > Tags: ipv6 > Justification: 2 > > Dear Maintainer, > > > >* What led up to the situation? > Attemting to install Buster with an USB WiFi dongle >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? > When the installer reached the "Detect Network Hardware", it entered a loop > of alternating white & black screen >* What outcome did you expect instead? > Identify the presence of a Panda PAU06 Wifi dongle, RT5372, requiring Debian > package rt2800us > > > > -- System Information: > Debian Release: 10.0 > APT prefers stable > APT policy: (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= > (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Bug#934030: xscreensaver-data-extra: glitchpeg.desktop contains split comment section
Control: reassign -1 xscreensaver-data-extra Control: forcemerge 920753 -1 On Mi, 07 aug 19, 16:06:04, Patrice Duroux wrote: > > Hi, > There is a trouble with the package name of your bug report (a trailing :) > which I think is also a duplicate of > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920753 So let's fix it ;) Kind regards, Andrei -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Bug#934184: ITP: nghttp3 -- C library for HTTP/3 functions
Control: reassign -1 wnpp On Mi, 07 aug 19, 22:11:42, Sakirnth Nagarasa wrote: > Package: nghttp3 > Owner: sakir...@gmail.com > > * Package name: nghttp3 > Upstream Author : nghttp3 contributors > * License : MIT License > Description : Implementation of HTTP/3 mapping over QUIC and QPACK > in C. > > Provides library for HTTP/3 fuctions. > > Greetings, > Sakirnth (Saki) -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Bug#933885: ITP: GNU Health - a hospital information system
Control: reassign -1 wnpp On Du, 04 aug 19, 22:44:51, Sakirnth Nagarasa wrote: > Package: gnuhealth > Owner: sakir...@gmail.com > > * Package name: gnuhealth > Upstream Author : GNU Health contributors > * License : GPL-3+ > Description : GNU Health is a Free/Libre project for health > practitioners, health institutions and governments. It provides the > functionality of Electronic Medical Record (EMR), Hospital Management > (HMIS) and Health Information System (HIS). > > Its modular design allows to be deployed in many different scenarios: > from small private offices, to large, national public health systems. > > Greetings, > > Sakirnth (Saki) -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Bug#933765: querybts: edit retrieves original submitter message
On Sb, 03 aug 19, 08:17:32, Andrei POPESCU wrote: > > Retrieving the message processed by the BTS (as 'bts --mbox show' does) > would be much more useful. Hello, I've just submitted Merge Request 25 in Salsa implementing this. If you prefer the patch in any other form don't hesitate to ask. This is my first attempt at python, beware of the dragons, ahem snakes ;) Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#517756: libxine1: No longer disables idle screen blanking
Control: reassign -1 xine-ui Control: retitle -1 xine-ui: No longer disables idle screen blanking On Jo, 05 mar 09, 00:55:58, Darren Salt wrote: > I demand that Sean Kellogg may or may not have written... > > > On Sunday 01 March 2009 06:17:09 pm Darren Salt wrote: > [snip] > >> But xine-lib doesn't know anything about screen blanking; that's left to > >> the front ends. Though now that you've said which front end, I suspect > >> that the bug is actually elsewhere. Probably xdg-screensaver, which is in > >> xdg-utils. You can test this by installing & using 0.99.5+cvs20070914-2. > > > I do have xdg-utils installed, wasn't aware there was yet ANOTHER > > screensaver provider after ditching xscreensaver AND kscreensaver. If I'm > > understanding what you are suggesting, I need to wait until there is a an > > updated xine-ui package in unstable? Sounds simple enough. > > Actually, no. An *older* version. Reverting the patch at > http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=58;bug=374644 will > effectively get you that version. > > See also bug 511248. Apparently this bug was left behind when libxine1 (src:xine-lib) was removed, however, my understanding of the bug log is that it belonged to xine-ui anyway (or possibly xdg-screensaver). Reassigning accordingly. Considering its age it would make sense to test if still applicable and deal with it accordingly. Kind regards, Andrei -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Bug#827611: No automatic log-out of ssh connected users when switching from ISC dhcp client to dhcpcd
Control: reopen -1 Control: reassign -1 dhcpcd5 On Sb, 03 aug 19, 09:47:05, andreimpope...@gmail.com wrote: > On Sb, 18 iun 16, 17:34:58, Comer352L wrote: > > Package: dhcpcd > > Version: 6.0.5-2 > > > > When switching from the ISC dhcp client to dhcpcd (uninstalling packages > > isc-dhcp-client, isc-dhcp-common, installing package dhcpcd5) > > users which are logged in via SSH are no longer logged out automatically > > when the system is shut down. > > Switching back to isc-dhcp-client restores the correct behavior. > > This package was removed from Debian (see #743218) as it was superseded > by a newer version. Never mind, the version suggests this was intended for dhcpd5 in jessie. > In case you can reproduce this behaviour with the current version of > dhcpcd please feel free to reopen and reassign as needed. Reproducing this with newer version of dhcpcd5 would still be useful though. Kind regards, Andrei -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Bug#627357: gnome-desktop-environment: I would like to remove avahi-daemon because mdns slows down PTR lookup
Control: reassign -1 libnss-mdns On Lu, 01 oct 12, 11:20:43, Karl O. Pinc wrote: > On 10/01/2012 02:26:25 AM, Simon McVittie wrote: > > On Thu, 19 May 2011 at 16:11:07 -0500, Karl O. Pinc wrote: > > > gnome-desktop-environment depends on gnome-user-share which, > > > eventually, depends on avahi-daemon. MDNS greatly slows down > > reverse > > > dns (PTR) lookups > > > > You should be able to address this without changes to the metapackage > > by removing libnss-mdns, which is recommended by avahi-daemon, but > > leaving avahi-daemon installed and running. Result: Avahi continues > > to work if applications like gnome-user-share explicitly use it > > (via libavahi-* or direct use of its D-Bus API), but you can no > > longer > > resolve through Avahi via the glibc name service switch API (so > > "ping foo.local" will no longer work). > > > > Removing mdns from nsswitch.conf but leaving mdns4_minimal might also > > be worth considering for your situation: mdns4_minimal will only > > resolve hostnames that match *.local or 169.254.*.*, and only with > > IPv4. > > Thanks for the response. > > Perhaps a note in README.Debian is called for? The gnome-desktop-environment meta-package doesn't exist anymore, so this bug is currently not assigned to any package. If my understanding is correct your suggestion for a note in README.Debian applies to libnss-mdns, so I'm reassigning accordingly. Kind regards, Andrei -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Bug#931546: RFP: TTG -- SNMP Text Traffic Grapher
Control: reassign -1 wnpp
On Du, 07 iul 19, 14:55:59, Apachez wrote:
> Subject: RFP: TTG -- SNMP Text Traffic Grapher
> Package: TTG
> Severity: wishlist
>
> * Package name : TTG
> Version : 2.2
> Upstream Author : Antoni Sawicki
> * URL : https://github.com/tenox7/ttg
> * License : Apache License 2.0
> Description :
>
> TTG is a small command line utility that displays current throughput
> (bandwidth usage) on an interface of a remote device such as router,
> switch, firewall, etc., over SNMP. You can think of TTG as command line
> version of STG or a high-interval/ad-hoc query/test tool for MRTG, etc. The
> output is very similar to ping(1) command. You can use it to quickly
> check/measure traffic before waiting 5 minute cycle when configuring MRTG,
> as a means of using the data in text form (eg. copy in to an email or
> spreadsheet) or just a general purpose command line network administration
> aid.
>
> TTG allows you to specify: SI prefix k/M/G (default is auto), units
> bits/bytes (b/B), size of "kilo" which can be either 1000 or 1024 depending
> on a personal opinion (default is 1000), interval in seconds and count
> limit. Finally the utility also allows you to list all interfaces of the
> device and can take interface name, such as "FastEthernet1/1" or it's
> abbreviation ("fa1/1") instead of OID name/number as the parameter.
--
http://wiki.debian.org/FAQsFromDebianUser
signature.asc
Description: PGP signature
Bug#931443: menu: corrected Romanian translation for su-to-root
Package: menu Version: 2.1.47 Severity: wishlist Tags: l10n patch X-Debbugs-CC: debian-l10n-roman...@lists.debian.org Dear Maintainer, Attached a corrected Romanian translation for su-to-root. Please kindly include on your next update. Best regards, Andrei - Forwarded message from Cristian Secară - Date: Thu, 4 Jul 2019 18:44:46 +0300 From: Cristian Secară To: debian-l10n-roman...@lists.debian.org Subject: fișierul .po de la menu_2.1.47_ro X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-w64-mingw32) În data de Tue, 2 Jul 2019 09:07:39 +0300, andreimpope...@gmail.com a scris: > Vă rog trimiteți un .po actualizat la > debian-l10n-roman...@lists.debian.org și mă ocup eu de actualizare. Atașat. Cristi -- Cristian Secară http://www.secarica.ro - End forwarded message - -- http://wiki.debian.org/FAQsFromDebianUser menu_2.1.47_ro.po.gz Description: Binary data signature.asc Description: PGP signature
Bug#931130: Document that local configuration for dummy and bonding modules are getting overwritten by systemd
On Vi, 28 iun 19, 14:46:15, Baptiste BEAUPLAT wrote: > On 6/28/19 2:39 PM, Michael Biebl wrote: > > > Would be good to know how Baptiste is setting up those devices. If he is > > doing it manually via some scripting of low level tool or uses a higher > > level network management tool > > Fwiw, with "ip link add dummy0 type dummy" (or "ip link add bond0 type > > bond") I was e.g. able to create such a device manually as well. > > I wonder whether such an approach isn't better then statically setting > > the number of devices via a kernel module option. > > My original setup was: > > echo "dummy" > /etc/modules > > cat << EOF >> /etc/network/interfaces > auto dummy0 > iface dummy0 inet static > address 192.168.64.1 > netmask 24 > EOF > > The interface would pop up configured at boot time (by ifup). Then, I > had services binding on 192.168.64.1. A (quick) look at interfaces(5) doesn't reveal any specific method to create dummy or bond interfaces. In order to keep things within one configuration file it would make sense to use a pre-up with ip commands as suggested above. Would this work *without* overriding the systemd.conf file? Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#930666: Please document consensus on use of dh sequencer
On Vi, 21 iun 19, 13:09:29, Sean Whitton wrote: > > There are sometimes good reasons to use a different approach. For > example, the standard tools for packaging software written in some > languages may use another tool; some rarer packaging patterns, such > as multiple builds of the same software with different options, are > easier to express with other tools; and a packager working on a new ^ > packaging helper might want to use their new tool. ^ Dropping "new" would cover both the case of existing (Jonas and cdbs) and new packaging helpers ;) Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#931130: Document that local configuration for dummy and bonding modules are getting overwritten by systemd
On Jo, 27 iun 19, 00:37:01, Justin B Rye wrote: > > Okay, so here's a first rough idea of what the release-notes might > say. It would make sense to put the new section after the existing > one on deprecating old-style interface names. Something like: > > > _Module configuration for bonding and dummy interfaces_ > > Administrators who are using channel bonding and/or dummy interfaces > (for instance to configure a machine as a router), and who have set > up module parameters in a file under /etc/modprobe.d, may need to > change the name of the local configuration file used, to avoid these > parameters being ignored after the upgrade to buster. > > In buster, udev ships a file /lib/modprobe.d/systemd.conf designed to > make it easier to configure such interfaces using systemd-networkd.[?] > This contains the lines > > options bonding max_bonds=0 > options dummy numdummies=0 > > A file in /lib/modprobe.d can be overridden by one with the same name > under /etc/modprobe.d, but the names are processed in alphabetical > order, so /lib/modprobe.d/systemd.conf follows and overrides (for > instance) /etc/modprobe.d/dummy.conf. Make sure that any local > configuration file has a name that sorts after "systemd.conf", such > as "/etc/modprobe.d/zz-local.conf". LGTM FWIW :) Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#931130: Document that local configuration for dummy and bonding modules are getting overwritten by systemd
Control: tags -1 moreinfo On Mi, 26 iun 19, 20:23:59, Baptiste BEAUPLAT wrote: > Package: release-notes > > Dear maintainers, > > Systemd, in buster, will ship the file /lib/modprobe.d/systemd.conf, > which contains the following: > > options bonding max_bonds=0 > > # Do the same for dummy0. > > options dummy numdummies=0 > > This breaks any configuration that an administrator could have added to > /etc/modprobe.d regarding the dummy and bonding modules. Would you have background information on why this is done? What would be the impact on local configuration (networking unusable, degraded, etc.)? > For instance, a file in /etc/modprobe.d/dummy.conf containing: > > options dummy numdummies=1 > > Will result in the following being executed by modprobe: > > insmod /lib/modules/4.19.0-5-amd64/kernel/drivers/net/dummy.ko > numdummies=1 numdummies=0 > > And the original configuration will be overridden. > > The only way to force modprobe to use local configuration is to rename > the /etc/modprobe.d/dummy.conf file to /etc/modprobe.d/systemd.conf. Is this documented anywhere else? > I thinks this should be documented in the release notes as admins would > need to be aware of that. Thanks, Andrei - not a Release Notes Maintainer, just anticipating what information might be necessary to write a useful entry. -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#922604: Re-assign and merge
control: reassign -1 keyboard-configuration control: forcemerge 924657 922604 These appear to be the same issue, so merging accordingly. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
