date:20210903

I will change to testing with all keyword switched to testing because my case 
is more often needing to use newer version software compared to stable, which 
also works fine w/t a problem for most of time. 

Thanks for all your help, and advice! Appreciate it!


Sep 4, 2021, 09:30 by riveravaldezm...@gmail.com:

> On 9/3/21, The Wanderer  wrote:
>
>> On 2021-09-03 at 15:16, Brian wrote:
>>
>>> On Fri 03 Sep 2021 at 13:40:52 -0400, Greg Wooledge wrote:
>>>
 On Fri, Sep 03, 2021 at 06:24:31PM +0100, Brian wrote:

 (...)
 In the absence of "pinning", using the two lines that The Wanderer
 posted would give you a testing system, with the option to pull in
 packages from stable if needed.  It's a viable setup.  Sensible.

>>> (...)
>>>
>>
>> Absence in testing is the specific reason why I still include that line:
>> in case I need to install a package because I need its functionality,
>> but it's been temporarily removed from testing for whatever reason.
>>
>> That scenario has actually arisen a handful of times over the years, and
>> the rest of the time, having the line included doesn't seem to have done
>> any harm.
>>
>> --
>>  The Wanderer
>>
>
> In fact, I'm just right now dealing with kinda situation.
>
> There's this `phwmon.py`[1] which I use with fluxbox to have a couple
> of system monitors at hand, and that depends on some python2 packages.
> I've just made it work, installing manually (# apt-get install packages.deb)
> this packages that I've downloaded from OldStable official archives:
>
> python-psutil
> python-is-python2 (this is in fact in Testing)
> python-numpy
> python-pkg-resources
> python-cairo
> libffi6
> python-gobject-2
> python-gtk2
>
> Therefore, my question:
>
> Is it better to install them as I did, or adding the line in sources.list as
> The Wanderer does?
>
> Thanks a lot in advance.
> Kind regards!
>
> [1] https://gitlab.com/o9000/phwmon
>

Proper way to add per-user profile under nix

2021-09-03 Thread Pankaj Jangid

I have installed ‘nix-setup-systemd’. And I was on the getting started
page of nix website. In the sample app, ‘nix-build’ gave me the
following error:

--8<---cut here---start->8---
warning: Nix search path entry 
'/nix/var/nix/profiles/per-user/pankaj/channels/nixpkgs' does not exist, 
ignoring
warning: Nix search path entry '/nix/var/nix/profiles/per-user/pankaj/channels' 
does not exist, ignoring
error: file 'nixpkgs' was not found in the Nix search path (add it using 
$NIX_PATH or -I), at /home/pankaj/work/personal/learn/nix/p1/default.nix:1:17
--8<---cut here---end--->8---

I have added myself to ‘nix-users’ group as specified in the
‘/usr/share/doc/nix-bin/README.Debian’.

Do I need to manually create profile directory? What is the proper
debian-way of creating per-user profile?

Re: Sound input source detected but not capturing

2021-09-03 Thread Pankaj Jangid

Marko Randjelovic  writes:

> Did you make sure:
>
> 1. correct device is set to record from 
> 2. recording is enabled
> 3. input volume is large enough

I guess I have only one device so there is nothing to set.

How is recording enabled? Do I need to add myself to some group? I am
member of followin groups: pankaj cdrom floppy sudo audio dip video
plugdev netdev bluetooth scanner.

I have tried to set input volume using various knobs in gnome settings
as well as alsamixer. It did not work.

>> If you are not sure send the output of command 'amixer' so we can check.
>
> In fact, unless you have only one sound device, the command should
> be 'amixer -cN' where N is the number of your sound card and can change
> after reboot. So first you have to type 'cat /proc/asound/cards' to
> find your card number.

Output of ‘amixer’

--8<---cut here---start->8---
$ amixer
Simple mixer control 'Master',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 65536
  Mono:
  Front Left: Playback 64880 [99%] [on]
  Front Right: Playback 64880 [99%] [on]
Simple mixer control 'Capture',0
  Capabilities: cvolume cswitch cswitch-joined
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 65536
  Front Left: Capture 65540 [100%] [on]
  Front Right: Capture 65540 [100%] [on]
--8<---cut here---end--->8---

Output of ‘amixer -c0’

--8<---cut here---start->8---
$ cat /proc/asound/cards
 0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xb1328000 irq 137

$ amixer -c0
Simple mixer control 'Master',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 87
  Mono: Playback 87 [100%] [0.00dB] [on]
Simple mixer control 'Headphone',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 87
  Mono:
  Front Left: Playback 0 [0%] [-65.25dB] [off]
  Front Right: Playback 0 [0%] [-65.25dB] [off]
Simple mixer control 'Speaker',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 87
  Mono:
  Front Left: Playback 87 [100%] [0.00dB] [on]
  Front Right: Playback 87 [100%] [0.00dB] [on]
Simple mixer control 'PCM',0
  Capabilities: pvolume
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 255
  Mono:
  Front Left: Playback 254 [100%] [-0.20dB]
  Front Right: Playback 254 [100%] [-0.20dB]
Simple mixer control 'Mic Boost',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 3
  Front Left: 3 [100%] [30.00dB]
  Front Right: 3 [100%] [30.00dB]
Simple mixer control 'IEC958',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]
Simple mixer control 'IEC958',1
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [on]
Simple mixer control 'IEC958',2
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [on]
Simple mixer control 'IEC958',3
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [on]
Simple mixer control 'IEC958',4
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [on]
Simple mixer control 'Capture',0
  Capabilities: cvolume cswitch
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 63
  Front Left: Capture 63 [100%] [30.00dB] [on]
  Front Right: Capture 63 [100%] [30.00dB] [on]
Simple mixer control 'Auto-Mute Mode',0
  Capabilities: enum
  Items: 'Disabled' 'Enabled'
  Item0: 'Enabled'
Simple mixer control 'Internal Mic Boost',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 3
  Front Left: 0 [0%] [0.00dB]
  Front Right: 0 [0%] [0.00dB]
--8<---cut here---end--->8---

Re: smart fans

2021-09-03 Thread Emanuel Berg

David Christensen wrote:

> Feeding the raw data into LibreOffice Calc was problematic
> -- header line field names do not have a one-to-one with
> data line field values. I reworked the header line as
> follows:
>
>   time, governor, processes, CPU_temperature, system_load,
>   CPU_fan_speed, core1_freq, core2_freq, core3_freq,
>   core4_freq

OK, changed.

> The system *must* be otherwise idle before and during the
> test. The data indicates it was not.

I didn't use the computer and there was no download or
anything explicit run by me in the background, so I don't know
what more to do in that regard?

> The "CPU_fan_speed" was 0 throughout. Your data collection
> code for that field value is broken.

That's what's reported by sensors(1), I don't know how else
one would retrieve that information?

> There is supposed to be a cool-down delay at the start of
> each governor sub-run. My WAG was 3 minutes. Your test did 2
> minutes (off by 1 error).

Weird, if you mean this part of the pseudocode

  loop 3 times
sleep 60 seconds
print statistics
  endloop

then that's this part of the zsh code

  repeat 3 {
sleep 60
cpu-stats
  }

so I don't know what that isn't 3 minutes ... ?

> After each loading cycle, the load processes must be killed.

OK.

> Incremental load period -- the output variables must have
> reached their steady-state values when each incremental load
> period ends (10 loops * 6 seconds). Adjust and/or
> code accordingly.

Again I don't understand why that isn't what

  repeat 10 {
sleep 6
cpu-stats
  }

does?

> Have you isolated and identified the primary noise
> source(s)? Have you quantified them (e.g.
> sound measurement)?

No?

> Can you get that data into your test script?

I don't know?

Anyway here is the new script with a URL to the output:

#! /bin/zsh
#
# this file:
#   https://dataswamp.org/~incal/conf/.zsh/cpu
#
# example output:
#   https://dataswamp.org/~incal/ebchw/cpu.txt

cpu-stats-print () {
local time=$1
local gov=$2
local pro=$3
local temp=$4
local load=$5
local fan=$6
shift 6
local freq=($@)
echo -n "${time}, ${gov}, ${pro}, ${temp}, ${load}, ${fan}"
for f in $freq; do
echo -n ", $f"
done
echo
}

cpu-stats () {
local time=$(date +%s)
local gov=$(cpufreq-info -p | awk '{print $3}')
local pro=$(ps -ea | wc -l) # 'jobs -l' DNC
local temp=$(sensors -j | jq -a '.["k10temp-pci-00c3"].Tdie.temp1_input')
local load=$(awk '{print $1}' /proc/loadavg)
local fan=$(sensors | awk '/cpu_fan/{print $2}') # always 0
local freq=("${(@f)$(awk '/cpu MHz/{print $4}' /proc/cpuinfo)}")
cpu-stats-print $time $gov $pro $temp $load $fan $freq
}

test-cpu () {
echo -n "time, governor, processes, CPU_temperature, system_load, 
CPU_fan_speed"
local cores=$(getconf _NPROCESSORS_ONLN)
for c in {1..$cores}; do
echo -n ", core${c}_freq"
done
echo

local ori=$(cpufreq-info -p | awk '{print $3}')
local pids
local g
local p
for g in $(cpufreq-info -g); do
pids=()
sudo cpufreq-set -g $g
repeat 3 {
sleep 60
cpu-stats
}
repeat $cores {
perl -e '1 while 1' &
pids+=($!)
repeat 10 {
sleep 6
cpu-stats
}
}
for p in $pids; do
  kill $p
done
done
sudo cpufreq-set -g $ori
}

-- 
underground experts united
https://dataswamp.org/~incal

Re: smart fans

2021-09-03 Thread David Christensen

On 9/3/21 3:05 PM, Emanuel Berg wrote:

David Christensen wrote:

Feeding the raw data into LibreOffice Calc was problematic

OK, changed.

Your data format still has issues. This is what LibreOffice Calc wants:

time,governor,processes,CPU_temperature,system_load,CPU_fan_speed,core1_freq,core2_freq,core3_freq,core4_freq
1630072652,conservative,157,33.25,0,0,1685.535,1416.164,3029.758,1415.421
1630072712,conservative,157,33.25,0,0,1537.245,1402.528,3118.173,1286.09
1630072772,conservative,157,33.25,0.06,0,1426.077,1356.078,1358.613,3049.18

Note:

1. No extraneous characters anywhere -- e.g. spaces.

2. No spaces in column names; use underscores and abbreviations.

3. One column name for each and every column.

4. Number of columns is same in every row.

5. Commas (field separator) between every row item.

5. Newlines (record separator) at the end of every row.

The system *must* be otherwise idle before and during the
test. The data indicates it was not.

I didn't use the computer and there was no download or
anything explicit run by me in the background, so I don't know
what more to do in that regard?

Then the "cpu-stats" function must be causing the spikes in the
"core*_freq" values, by the several child processes it creates in rapid
succession. Get rid of the useless CPU_fan_speed call. Insert a 1
second sleep ahead of each of the remaining data point collection calls.
Adjust the iteration counts and the sleep times in the calling loops
to compensate.

There is supposed to be a cool-down delay at the start of
each governor sub-run. My WAG was 3 minutes. Your test did 2
minutes (off by 1 error).

Weird, if you mean this part of the pseudocode

loop 3 times
sleep 60 seconds
print statistics
endloop

then that's this part of the zsh code

repeat 3 {
sleep 60
cpu-stats
}

so I don't know what that isn't 3 minutes ... ?

I was off-by-one -- there is no "print statistics" at the top of the
script, which means the first data row comes out after 60 seconds.
Please add a 10 second sleep and a call to "cpu-stats" prior to the
governor loop.

But, a fundamental reality is the Nyquist–Shannon sampling theorem:

https://en.wikipedia.org/wiki/Nyquist%E2%80%93Shannon_sampling_theorem

Each of the data points your script is collecting has some signal
processing behind it; notably a sampling period. Please RTFM and see if
you can determine the periods of the CPU temperature sensor readings and
the core frequency readings, and if you can adjust those periods so that
they are longer than your data collection period.

It might be best to rework the loops so that the data collection period
is constant throughout the entire test.

After each loading cycle, the load processes must be killed.

OK.

Looking at the "processes", "system_load", and "core*_freq" fields, the
overall test data indicates that the "conservative" sub-run loaded the
machine to 100% and that the loading processes never were killed. The
second and subsequent governor sub-runs just added more load. Debug the
code related to "pids" and kill.

Have you isolated and identified the primary noise
source(s)? Have you quantified them (e.g.
sound measurement)?

No?

If the loudest sound source is the PSU or GPU fan, then tuning the CPU
and/or chassis fans isn't going to help.

David

Question about DMARK and flood of mails...

2021-09-03 Thread Jean-François Bachelet


Hello ^^)


en ce moment je suis floodé de mails 'dmark aggregate reports' de la 
part de serveurs que j'ai pas contacté, pour un domaine (qui 
m'appartient) mais qui n'envoie pas de mails sauf si c'est moi qui le 
fait... et le dernier date de plus d'un mois.


c'est quoi ce binz ? une idée ?


Jeff

Re: How to update Debian 11 source.list to testing?

2021-09-03 Thread riveravaldez

On 9/3/21, The Wanderer  wrote:
> On 2021-09-03 at 15:16, Brian wrote:
>
>> On Fri 03 Sep 2021 at 13:40:52 -0400, Greg Wooledge wrote:
>>
>>> On Fri, Sep 03, 2021 at 06:24:31PM +0100, Brian wrote:
>
>>> (...)
>>> In the absence of "pinning", using the two lines that The Wanderer
>>> posted would give you a testing system, with the option to pull in
>>> packages from stable if needed.  It's a viable setup.  Sensible.
>> (...)
>
> Absence in testing is the specific reason why I still include that line:
> in case I need to install a package because I need its functionality,
> but it's been temporarily removed from testing for whatever reason.
>
> That scenario has actually arisen a handful of times over the years, and
> the rest of the time, having the line included doesn't seem to have done
> any harm.
>
> --
>The Wanderer

In fact, I'm just right now dealing with kinda situation.

There's this `phwmon.py`[1] which I use with fluxbox to have a couple
of system monitors at hand, and that depends on some python2 packages.
I've just made it work, installing manually (# apt-get install packages.deb)
this packages that I've downloaded from OldStable official archives:

python-psutil
python-is-python2 (this is in fact in Testing)
python-numpy
python-pkg-resources
python-cairo
libffi6
python-gobject-2
python-gtk2

Therefore, my question:

Is it better to install them as I did, or adding the line in sources.list as
The Wanderer does?

Thanks a lot in advance.
Kind regards!

[1] https://gitlab.com/o9000/phwmon

Re: Clamav question ^^)

2021-09-03 Thread Jean-François Bachelet


Hello ^^)


Le 03/09/2021 à 16:10, Luc Novales a écrit :


Bonjour,

Le 03/09/2021 à 13:42, Jean-François Bachelet a écrit :


...

#|ldd $(which freshclam)|
    linux-vdso.so.1 (0x7ffea9559000)
--> libclamav.so.9 => /lib/x86_64-linux-gnu/libclamav.so.9 
(0x7fc1a9a4e000)

    ...

Question : comment on s'en débarrasse de cette vieille lib ? le 'apt 
remove --auto-remove' ne fait rien ici.


Pourquoi penses tu que c’est une vieille lib ?

Parce ce que c'est que disent les auteurs du logiciel dans leur propre 
site, ce que je cite dans mon mel en vient directement.


je te le remet :


 "I upgraded to the latest stable version but I still get the
 message "/Your ClamAV installation is OUTDATED/", why?
 


Make sure there is really only one version of ClamAV installed on your 
system:


|whereis freshclam whereis clamscan |

--> Also make sure that you haven't got old libraries (|libclamav.so*|) 
lying around your filesystem. You can verify it using:


|ldd $(which freshclam)" |


si tu veux vérifier c'est la : https://docs.clamav.net/faq/faq-upgrade.html


libclamav9 (>= 0.103.2) 
 est une 
dépendance de clamav (0.103.2+dfsg-2) 
 pour debian11, et ce 
fichier fait bien partie de la dernière version 
.


Au passage un |dpkg -S /usr/lib/x86_64-linux-gnu/libclamav.so.9| 
t’aurait renseigné sur le paquet dont dépend ce fichier.


Tout semble dans l’ordre ;)


jeff ;)

Re: cups no puedo ingresar

2021-09-03 Thread Marcelo Eduardo Giordano




El 3/9/21 a las 03:28, Camaleón escribió:

El 2021-09-02 a las 18:49 -0300, Marcelo Eduardo Giordano escribió:


Tengo Debian bullseye kde y he cambiado unas configuraciones de cups por lo
cual me pidió mi usuario root y se reinició.

Ahora no puedo ingresar a localhost:631 me dice "localhost rechazó la
conexión"

No tengo firewall instalado

Comprueba que el servicio esté iniciado «service cups status» y manda
también la salida de la orden «lpstat -t».

Saludos,

Gracias por contestar. Esto me dicen los comandos. Puedo imprimir 
perfectamente desde la computadora, aunque por supuesto que no en red 
que es lo que quiero lograr


antonella@Antonella:~$ service cups status
● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor 
preset: enabled)

 Active: active (running) since Fri 2021-09-03 16:48:00 -03; 8min ago
TriggeredBy: ● cups.path
 ● cups.socket
   Docs: man:cupsd(8)
   Main PID: 3104 (cupsd)
 Status: "Scheduler is running..."
  Tasks: 5 (limit: 18432)
 Memory: 6.1M
    CPU: 114ms
 CGroup: /system.slice/cups.service
 ├─3104 /usr/sbin/cupsd -l
 ├─3106 /usr/lib/cups/notifier/dbus dbus://
 ├─3107 /usr/lib/cups/notifier/dbus dbus://
 ├─3108 /usr/lib/cups/notifier/dbus dbus://
 └─3112 /usr/lib/cups/notifier/dbus dbus://
antonella@Antonella:~$ lpstat -t
el planificador de tareas se está ejecutando
destino predeterminado del sistema: Xerox_B215_XRX9C934EAED2E8_
dispositivo para EPSON_L3110_Series: 
usb://EPSON/L3110%20Series?serial=583544503031343683=1
dispositivo para Xerox_B215_XRX9C934EAED2E8_: 
implicitclass://Xerox_B215_XRX9C934EAED2E8_/

EPSON_L3110_Series aceptando peticiones desde vie 03 sep 2021 10:47:48
Xerox_B215_XRX9C934EAED2E8_ aceptando peticiones desde vie 03 sep 2021 
16:48:02
la impresora EPSON_L3110_Series está inactiva.  activada desde vie 03 
sep 2021 10:47:48
la impresora Xerox_B215_XRX9C934EAED2E8_ está inactiva.  activada desde 
vie 03 sep 2021 16:48:02

Re: How to update Debian 11 source.list to testing?

On 2021-09-03 at 15:16, Brian wrote:

> On Fri 03 Sep 2021 at 13:40:52 -0400, Greg Wooledge wrote:
> 
>> On Fri, Sep 03, 2021 at 06:24:31PM +0100, Brian wrote:

>>> Surely - if you have a package installed from a previous release,
>>> it does not get removed simply because testing does not have it?
>> 
>> Correct.
>> 
>>> It looks to me that the first line in sources.list does not help
>>> in this situation.
>> 
>> Also correct, *but* it does help if you want to install something from
>> stable that has been removed from testing.
>> 
>> In the absence of "pinning", using the two lines that The Wanderer
>> posted would give you a testing system, with the option to pull in
>> packages from stable if needed.  It's a viable setup.  Sensible.
> 
> The bit that neeeds emphasising is 
> 
>   ...give you a testing system.
> 
> That is what the second entry in sources.list does.
> 
> It doesn't matter what the other line is, the user is working 
> with a testing system. That is where the packages come from.
> 
> Having said that, the option to pull in packages from stable
> as needed is moot, apart from security updates or absence on
> testing. It looks like cargo cult.

Absence in testing is the specific reason why I still include that line:
in case I need to install a package because I need its functionality,
but it's been temporarily removed from testing for whatever reason.

That scenario has actually arisen a handful of times over the years, and
the rest of the time, having the line included doesn't seem to have done
any harm.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw

signature.asc
Description: OpenPGP digital signature

Re: Why ``color_prompt`` is only set for ``xterm``?

2021-09-03 Thread Mark Neyhart

On 9/2/21 5:45 PM, piorunz wrote:
> On 03/09/2021 01:34, David Wright wrote:
>> (I use my own customisations for distinct colours on each host,
>> and inverse colours for root's prompt.)
> 
> Can you please share your root prompt invocation? Thanks!
> 

In /root/.bashrc I use this to give a red prompt including host and
full path followed by a new line.  This leaves more room for a long
command when the full path is long.

export PS1='\[\e[1;31m\]\h:\w\$\[\e[0m\]\n'

Re: How to update Debian 11 source.list to testing?

2021-09-03 Thread Brian

On Fri 03 Sep 2021 at 13:40:52 -0400, Greg Wooledge wrote:

> On Fri, Sep 03, 2021 at 06:24:31PM +0100, Brian wrote:
> > On Fri 03 Sep 2021 at 10:40:32 -0400, The Wanderer wrote:
> > > deb http://ftp.us.debian.org/debian/ stable main non-free contrib
> > > deb http://ftp.us.debian.org/debian/ testing main non-free contrib
> 
> > Surely - if you have a package installed from a previous release,
> > it does not get removed simply because testing does not have it?
> 
> Correct.
> 
> > It looks to me that the first line in sources.list does not help
> > in this situation.
> 
> Also correct, *but* it does help if you want to install something from
> stable that has been removed from testing.
> 
> In the absence of "pinning", using the two lines that The Wanderer
> posted would give you a testing system, with the option to pull in
> packages from stable if needed.  It's a viable setup.  Sensible.

The bit that neeeds emphasising is 

  ...give you a testing system.

That is what the second entry in sources.list does.

It doesn't matter what the other line is, the user is working 
with a testing system. That is where the packages come from.

Having said that, the option to pull in packages from stable
as needed is moot, apart from security updates or absence on
testing. It looks like cargo cult.

-- 
Brian.

Re: Sound input source detected but not capturing

2021-09-03 Thread Marko Randjelovic

On Fri, 3 Sep 2021 20:48:52 +0200
Marko Randjelovic  wrote:

> If you are not sure send the output of command 'amixer' so we can check.

In fact, unless you have only one sound device, the command should
be 'amixer -cN' where N is the number of your sound card and can change
after reboot. So first you have to type 'cat /proc/asound/cards' to
find your card number.

Re: How to update Debian 11 source.list to testing?

On 2021-09-03 at 13:40, Greg Wooledge wrote:

> On Fri, Sep 03, 2021 at 06:24:31PM +0100, Brian wrote:
> 
>> On Fri 03 Sep 2021 at 10:40:32 -0400, The Wanderer wrote:
>> 
>>> deb http://ftp.us.debian.org/debian/ stable main non-free
>>> contrib deb http://ftp.us.debian.org/debian/ testing main
>>> non-free contrib
> 
>> Surely - if you have a package installed from a previous release, 
>> it does not get removed simply because testing does not have it?
> 
> Correct.
> 
>> It looks to me that the first line in sources.list does not help in
>> this situation.
> 
> Also correct, *but* it does help if you want to install something
> from stable that has been removed from testing.

Yep - and that's the main reason why I keep this arrangement.

> In the absence of "pinning", using the two lines that The Wanderer 
> posted would give you a testing system, with the option to pull in 
> packages from stable if needed.  It's a viable setup.  Sensible.
> 
> The problem is, sometimes people think it's the opposite of that. 
> They think they can run a "mostly stable" system with the option to 
> cherry-pick packages from testing.  This is *NOT* the case.  And no 
> amount of "pinning" will make it so.

I hadn't even considered that angle, although now that it's been brought
up I recall having seen it discussed in the past.

No, indeed - that's not going to work, and it should not be anything
close to recommended. I would not want my description of my own setup to
be interpreted as an endorsement of trying to do that.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw

signature.asc
Description: OpenPGP digital signature

Re: gcc-10: options order important?

2021-09-03 Thread Sven Joachim

On 2021-09-03 12:24 +0200, Piotr A. Dybczyński wrote:

> Hi,
>
> in contrary to previous versions, now in Debian 11 with gcc-10:
>
> gcc aa.c -lm -o aa   works, but
>
> gcc -lm aa.c -o aa   does not work, saying: 
>
> /usr/bin/ld: /tmp/ccWyhudO.o: in function `main':
> aa.c:(.text+0x1f): undefined reference to `sqrt'
> collect2: error: ld returned 1 exit status
>
> It seems that an option -lm cannot be placed in an arbitrary place which I 
> used to
> do. Is this intentional ?

Yes, gcc now invokes ld with the --as-needed option.  This reduces
unnecessary linking and thereby Debian package dependencies, but it also
has the effect you are seeing, as mentioned in the binutils
documentation:

,
| Object files or libraries appearing on the command line _after_ the
| library in question do not affect whether the library is seen as needed.
| This is similar to the rules for extraction of object files from
| archives.  '--no-as-needed' restores the default behaviour.
`

Cheers,
   Sven

Re: How to update Debian 11 source.list to testing?

On 2021-09-03 at 13:06, Greg Wooledge wrote:

> On Fri, Sep 03, 2021 at 10:40:32AM -0400, The Wanderer wrote:
> 
>> I have been running with (e.g.)
>> 
>> deb http://ftp.us.debian.org/debian/ stable main non-free contrib 
>> deb http://ftp.us.debian.org/debian/ testing main non-free contrib
>> 
>> for over a decade, and [...] there have been some problems [...]
> 
> This is *precisely* why we advise against doing this.  A dedicated 
> expert in Debian may be equipped to handle the problems that arise. 
> If you think you're good enough, and you want to do this, we can't 
> stop you.  But we also can't help you when it breaks.

While I acknowledge the points raised thus far (that being why I haven't
responded, since I wouldn't have had much to say but "That's fair"), I
don't think this is entirely right. You snipped out the part where I
pointed out that as far as I can tell, the problems which I had are the
same ones which I'd have had from just tracking testing anyway. If
that's correct, then the fact of tracking both will have had nothing to
do with my having encountered those problems.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw

signature.asc
Description: OpenPGP digital signature

Re: APT testing and unstabe Firefox: can't find newest version from unstable

2021-09-03 Thread Sven Joachim

On 2021-09-03 19:05 +0200, Daniel M. wrote:

> I'm running debian testing ("bookworm" at the moment) and have firefox
> 88 installed from unstable. My sources.list contains testing and
> unstable main, contrib and non-free lines and I have pinning set up to
> 900 testing, 500 unstable. Default-Release is set to "testing".
>
> The debian package tracker (https://tracker.debian.org/pkg/firefox)
> states that version 91.0.1-1 of firefox should be available, but I can
> in no way install it. "apt -t unstable install firefox" doesn't work,
> neither does "apt install firefox/unstable". Both get me version 88
> again. "apt-cache policy firefox" also only lists this version. If I
> remove firefox and install it again with one of these ways I again get
> version88.
>
> What am I doing wrong? Shouldn't I be able to install version 91 via
> one of these ways?

Version 91 is only in experimental.

Cheers,
   Sven

Re: Sound input source detected but not capturing

2021-09-03 Thread Marko Randjelovic

On Fri, 03 Sep 2021 22:52:45 +0530
Pankaj Jangid  wrote:

> I have a fresh Bullseye installation on a laptop. Sound output is
> working. But the input is not working. The device is detected.
> 
> --8<---cut here---start->8---
> $ arecord -l
>  List of CAPTURE Hardware Devices 
> card 0: PCH [HDA Intel PCH], device 0: ALC236 Analog [ALC236 Analog]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> --8<---cut here---end--->8---
> 
> In the gnome settings, input is showing built-in microphone but there is
> not movement in the capturing indicator.
> 
> alsamixer is also showing the sound card (F6) - HDA Intel PCH.
> 

Did you make sure:

1. correct device is set to record from 
2. recording is enabled
3. input volume is large enough

If you are not sure send the output of command 'amixer' so we can check.

Re: gcc-10: options order important?

2021-09-03 Thread tomas

On Fri, Sep 03, 2021 at 12:59:27PM -0400, Greg Wooledge wrote:
> On Fri, Sep 03, 2021 at 02:12:46PM +0100, Tixy wrote:
> > > A man page a found online [1] says linking happens as Greg described, 
> > > and this is true looking at a 6 year old copy of that page on
> > > archive.org. So seems strange that for many years my Makefiles have
> > > worked with Libraries specified before inputs that use them.
> > 
> > Correction... 'for many years my Makefiles have worked with Libraries
> > specified _after_ inputs that use them'
> 
> You had it right the first time.  It's strange that it worked (in the
> past) with the library argument in front.  It's supposed to be behind.
> 
> The linker's argument processing must have been changed a few times.
> GNU utilities in general have a tendency to be overly lenient with
> command-line options.  Commands that *should* fail according to POSIX
> sometimes work in the GNU variants.

[...]

It /might/ be related to weak linking and the default for
the --as-needed option in the linker. Caveat: I haven't found
the time to research this more thoroughly.

But OP could try to pass --no-as-needed and see what happens :)

Cheers
 - t


signature.asc
Description: Digital signature

Re: How to update Debian 11 source.list to testing?

On Fri, Sep 03, 2021 at 06:24:31PM +0100, Brian wrote:
> On Fri 03 Sep 2021 at 10:40:32 -0400, The Wanderer wrote:
> > deb http://ftp.us.debian.org/debian/ stable main non-free contrib
> > deb http://ftp.us.debian.org/debian/ testing main non-free contrib

> Surely - if you have a package installed from a previous release,
> it does not get removed simply because testing does not have it?

Correct.

> It looks to me that the first line in sources.list does not help
> in this situation.

Also correct, *but* it does help if you want to install something from
stable that has been removed from testing.

In the absence of "pinning", using the two lines that The Wanderer
posted would give you a testing system, with the option to pull in
packages from stable if needed.  It's a viable setup.  Sensible.

The problem is, sometimes people think it's the opposite of that.
They think they can run a "mostly stable" system with the option to
cherry-pick packages from testing.  This is *NOT* the case.  And no
amount of "pinning" will make it so.

(If you actually want such a system, use stable-backports.  That's
what they're for.  Do not pull binary packages from testing.  I know,
we say this every 3 days, but that's because the issue *comes up*
every 3 days.  We can't stamp it out.)

Re: How to update Debian 11 source.list to testing?

2021-09-03 Thread Brian

On Fri 03 Sep 2021 at 10:40:32 -0400, The Wanderer wrote:

[...]

> Are you sure about that last part?
> 
> I have been running with (e.g.)
> 
> deb http://ftp.us.debian.org/debian/ stable main non-free contrib
> deb http://ftp.us.debian.org/debian/ testing main non-free contrib
> 
> for over a decade, and while there have been some problems, I think
> they've been basically the same ones I'd have seen from running testing
> alone; none of them have seemed terribly difficult to resolve, either.
> (At least not by my standards, although I'll admit that I may not be the
> best or most representative example.)
> 
> I don't particularly consider this mixing releases; it's more tracking
> testing, while still keeping available any packages which were in stable
> but have been removed from testing.
> 
> IMO, if you're going to track testing at all on a production computer
> (as opposed to, well, for the purpose of actually *testing the upcoming
> release*), it only makes sense to also include stable; there's too much
> chance of an important package being (temporarily or permanently)
> unavailable, otherwise.

Surely - if you have a package installed from a previous release,
it does not get removed simply because testing does not have it?
It looks to me that the first line in sources.list does not help
in this situation.

-- 
Brian.

Sound input source detected but not capturing

2021-09-03 Thread Pankaj Jangid

I have a fresh Bullseye installation on a laptop. Sound output is
working. But the input is not working. The device is detected.

--8<---cut here---start->8---
$ arecord -l
 List of CAPTURE Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC236 Analog [ALC236 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
--8<---cut here---end--->8---

In the gnome settings, input is showing built-in microphone but there is
not movement in the capturing indicator.

alsamixer is also showing the sound card (F6) - HDA Intel PCH.

APT testing and unstabe Firefox: can't find newest version from unstable

2021-09-03 Thread Daniel M.

Hi everyone,

I'm running debian testing ("bookworm" at the moment) and have firefox
88 installed from unstable. My sources.list contains testing and
unstable main, contrib and non-free lines and I have pinning set up to
900 testing, 500 unstable. Default-Release is set to "testing".

The debian package tracker (https://tracker.debian.org/pkg/firefox)
states that version 91.0.1-1 of firefox should be available, but I can
in no way install it. "apt -t unstable install firefox" doesn't work,
neither does "apt install firefox/unstable". Both get me version 88
again. "apt-cache policy firefox" also only lists this version. If I
remove firefox and install it again with one of these ways I again get
version88.

What am I doing wrong? Shouldn't I be able to install version 91 via
one of these ways?

Please spare me the talk about not mixing debian suites - I usually
know what I'm doing. I've been running debian for over 10 years now.
This is the first time apt/dpkg is too high for me. Can anyone please
help?

Cheers,
Daniel

Re: How to update Debian 11 source.list to testing?

On Fri, Sep 03, 2021 at 10:40:32AM -0400, The Wanderer wrote:
> I have been running with (e.g.)
> 
> deb http://ftp.us.debian.org/debian/ stable main non-free contrib
> deb http://ftp.us.debian.org/debian/ testing main non-free contrib
> 
> for over a decade, and [...] there have been some problems [...]

This is *precisely* why we advise against doing this.  A dedicated
expert in Debian may be equipped to handle the problems that arise.
If you think you're good enough, and you want to do this, we can't
stop you.  But we also can't help you when it breaks.

Re: gcc-10: options order important?

On Fri, Sep 03, 2021 at 02:12:46PM +0100, Tixy wrote:
> > A man page a found online [1] says linking happens as Greg described, 
> > and this is true looking at a 6 year old copy of that page on
> > archive.org. So seems strange that for many years my Makefiles have
> > worked with Libraries specified before inputs that use them.
> 
> Correction... 'for many years my Makefiles have worked with Libraries
> specified _after_ inputs that use them'

You had it right the first time.  It's strange that it worked (in the
past) with the library argument in front.  It's supposed to be behind.

The linker's argument processing must have been changed a few times.
GNU utilities in general have a tendency to be overly lenient with
command-line options.  Commands that *should* fail according to POSIX
sometimes work in the GNU variants.

For example:

unicorn:~$ ls .bashrc -l
-rwxr-xr-x 1 greg greg 2741 Sep  1 22:32 .bashrc*

That should *not* have worked, but GNU permits the option (-l) to be
handled even when it's in the wrong place.  (In standard POSIX ls,
that command should have tried to list a file named "-l", because
the non-option ".bashrc" terminates option processing.  All remaining
arguments are to be treated as files or directories.)

All I can speculate is that GNU ld (the linker that gcc uses) must have
had some tweaks done to it over the years, and now has settled back into
its original behavior.  An expert in GNU binutils (or even a changelog)
might have more details.

The way a gcc (or cc) command is supposed to be written is:

gcc [options] source/object files [-libraries]

The up-front [options] can include things like "-o foo" to specify an
output file other than a.out to the linker.  So, for example, the OP's
command should have been something like:

gcc -o foo foo.c -lm

That's the standard format, and is what you should be using in Makefiles
and similar files which call gcc.

Re: How to update Debian 11 source.list to testing?

2021-09-03 Thread Eduardo M KALINOWSKI


On 03/09/2021 11:40, The Wanderer wrote:

On 2021-09-03 at 10:17, Roberto C. Sánchez wrote:


On Fri, Sep 03, 2021 at 04:11:49PM +0200, Richard Forst wrote:

If you change all instances of bullseye -> testing, then you are not
mixing. Go ahead with that, modulo the standard caveats associated
with running testing. The problem would come if you tried to include
both bullseye *and* testing sources in your sources.list. Then you
might create very difficult to resolve problems.

Are you sure about that last part?

I have been running with (e.g.)

deb http://ftp.us.debian.org/debian/ stable main non-free contrib
deb http://ftp.us.debian.org/debian/ testing main non-free contrib

for over a decade, and while there have been some problems, I think
they've been basically the same ones I'd have seen from running testing
alone; none of them have seemed terribly difficult to resolve, either.
(At least not by my standards, although I'll admit that I may not be the
best or most representative example.)

I don't particularly consider this mixing releases; it's more tracking
testing, while still keeping available any packages which were in stable
but have been removed from testing.

IMO, if you're going to track testing at all on a production computer
(as opposed to, well, for the purpose of actually *testing the upcoming
release*), it only makes sense to also include stable; there's too much
chance of an important package being (temporarily or permanently)
unavailable, otherwise.


But there's a chance that the version in stable is not installable 
anymore because it depends on packages that have been upgraded on 
testing and are incompatible with stable.


That said, I agree with you that there's a bit of exaggeration about 
mixing releases. Sure, it's not something to be recommended to a 
beginner or someone who's used to just clicking "Next >" to 
install/upgrade software, but provided one knows what they are doing and 
are careful when running apt-get (or equivalents), it's certainly 
possible and won't lead to guaranteed breakage.



--
  Goes (Went) over like a lead balloon.

Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: How to update Debian 11 source.list to testing?

On Fri, Sep 03, 2021 at 04:25:39PM +0100, piorunz wrote:
> On 03/09/2021 15:17, Roberto C. Sánchez wrote:
> > If you change all instances of bullseye -> testing, then you are not
> > mixing.  Go ahead with that (...)
> 
> Yep, that's all there is to say. testing word instead of bullseye
> everywhere in sources.list will do the trick.
> 
> AFAIK, you may also disable "-security" entry, as testing doesn't have
> dedicated security team and testing-security repository will be empty.
> 
I actually would recommend leaving it.  In the last months prior to the
next release, particularly when the freeze goes into effect, there will
be uploads into bookwork-security (or testing-security).  It doesn't
hurt anything to leave it.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: How to update Debian 11 source.list to testing?

2021-09-03 Thread piorunz


On 03/09/2021 15:17, Roberto C. Sánchez wrote:

If you change all instances of bullseye -> testing, then you are not
mixing.  Go ahead with that (...)


Yep, that's all there is to say. testing word instead of bullseye
everywhere in sources.list will do the trick.

AFAIK, you may also disable "-security" entry, as testing doesn't have
dedicated security team and testing-security repository will be empty.

--

With kindest regards, piorunz.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: How to update Debian 11 source.list to testing?

On Fri, Sep 03, 2021 at 10:40:32AM -0400, The Wanderer wrote:
> On 2021-09-03 at 10:17, Roberto C. Sánchez wrote:
> 
> > On Fri, Sep 03, 2021 at 04:11:49PM +0200, Richard Forst wrote:
> > 
> >> I just installed Debian using netinstall image. I thought I install
> >> testing version, but apparently it's Debian 11. So now my
> >> source.list looks like below:
> >> 
> >> deb http://deb.debian.org/debian/ bullseye main non-free contrib
> >> deb-src http://deb.debian.org/debian/ bullseye main non-free contrib
> >> 
> >> deb http://security.debian.org/debian-security bullseye-security main 
> >> contrib non-free
> >> deb-src http://security.debian.org/debian-security bullseye-security 
> >> main contrib non-free
> >> 
> >> deb http://deb.debian.org/debian/ bullseye-updates main contrib 
> >> non-free
> >> deb-src http://deb.debian.org/debian/ bullseye-updates main contrib 
> >> non-free
> >> 
> >> I want to switch to testing version. In the past I just change the 
> >> keyword from e.g. bullseye to testing, and generally there is no
> >> weird problem. But I read on the internet saying that the
> >> source.list should not mix up with different version. For instance,
> >> Debian 11 with testing. So I am wondering if there is a better way
> >> to switch to testing? Or reinstalling is the only way to go?
> > 
> > If you change all instances of bullseye -> testing, then you are not 
> > mixing. Go ahead with that, modulo the standard caveats associated
> > with running testing. The problem would come if you tried to include
> > both bullseye *and* testing sources in your sources.list. Then you
> > might create very difficult to resolve problems.
> 
> Are you sure about that last part?
> 
Yes, I'm sure, that's why I used *might* :-)

> I have been running with (e.g.)
> 
> deb http://ftp.us.debian.org/debian/ stable main non-free contrib
> deb http://ftp.us.debian.org/debian/ testing main non-free contrib
> 
> for over a decade, and while there have been some problems, I think
> they've been basically the same ones I'd have seen from running testing
> alone; none of them have seemed terribly difficult to resolve, either.
> (At least not by my standards, although I'll admit that I may not be the
> best or most representative example.)
> 
I respect your experience as valid.  However, the anecdotal "I haven't
experienced this particular problem" does not automatically extend to
"therefore nobody else should either".  The people who have written the
documentation have provided a great deal of user support over the years.
It seems unlikely that they would invent phantom problems to try to
frighten users.  Having experienced problems precisely as those
described associated with mixing releases, I can testify to the fact
that it can happen.

> I don't particularly consider this mixing releases; it's more tracking
> testing, while still keeping available any packages which were in stable
> but have been removed from testing.
> 
Yet, the further way the stable release becomes from the present, the
greater the divergence of things like library dependencies.  It is, in
fact, mixing releases.  Depending on which particular set of packages
you have installed, you might see no problems, only minor problems, or
extraordinarily difficult problems.  Hence, the caution.

> IMO, if you're going to track testing at all on a production computer
> (as opposed to, well, for the purpose of actually *testing the upcoming
> release*), it only makes sense to also include stable; there's too much
> chance of an important package being (temporarily or permanently)
> unavailable, otherwise.
> 
Note that the OP's concern was "I want to switch a just-installed system
from bullseye to testing, but I'm concerned about mixing releases."  The
idea is that if everything is switched from bullseye to testing then it
isn't mixing releases.  However, I did feel the need to point out the
nature of potential problems to be encountered.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: Install Debian netinstall to HP Elitebook 840 G8 problem

2021-09-03 Thread Patrick Bartek

On Fri, 3 Sep 2021 09:46:24 +0200 (CEST)
Richard Forst  wrote:

> I purchased a new laptop HP Elitebook 840 G8, and am trying to
> install Debian to it. However I encounter a problem. 
> 
> I change the bios setting, but when booting from usb. What was shown
> on the screen is simply a grub env command line like

When in bios, did you disable Secureboot, Fastboot, and/or enable
Legacy option?

B

Re: Clamav question ^^)

2021-09-03 Thread Luc Novales


Bonjour,

Le 03/09/2021 à 13:42, Jean-François Bachelet a écrit :


...

#|ldd $(which freshclam)|
    linux-vdso.so.1 (0x7ffea9559000)
--> libclamav.so.9 => /lib/x86_64-linux-gnu/libclamav.so.9 
(0x7fc1a9a4e000)

    ...

Question : comment on s'en débarrasse de cette vieille lib ? le 'apt 
remove --auto-remove' ne fait rien ici.


Pourquoi penses tu que c’est une vieille lib ?

libclamav9 (>= 0.103.2) 
 est une dépendance 
de clamav (0.103.2+dfsg-2) 
 pour debian11, et ce 
fichier fait bien partie de la dernière version 
.


Au passage un |dpkg -S /usr/lib/x86_64-linux-gnu/libclamav.so.9| 
t’aurait renseigné sur le paquet dont dépend ce fichier.


Tout semble dans l’ordre ;)

Bonne journée,


--
*Luc Novalès*
Enseignant réseaux.
SINA/RCA
Tel : (33) (0)5 62 17 42 63
Mail : luc.nova...@enac.fr


Logo ENAC 7, ave. Édouard Belin
cedex 4
31055 Toulouse

Re: How to update Debian 11 source.list to testing?

On 2021-09-03 at 10:17, Roberto C. Sánchez wrote:

> On Fri, Sep 03, 2021 at 04:11:49PM +0200, Richard Forst wrote:
> 
>> I just installed Debian using netinstall image. I thought I install
>> testing version, but apparently it's Debian 11. So now my
>> source.list looks like below:
>> 
>> deb http://deb.debian.org/debian/ bullseye main non-free contrib
>> deb-src http://deb.debian.org/debian/ bullseye main non-free contrib
>> 
>> deb http://security.debian.org/debian-security bullseye-security main 
>> contrib non-free
>> deb-src http://security.debian.org/debian-security bullseye-security 
>> main contrib non-free
>> 
>> deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
>> deb-src http://deb.debian.org/debian/ bullseye-updates main contrib 
>> non-free
>> 
>> I want to switch to testing version. In the past I just change the 
>> keyword from e.g. bullseye to testing, and generally there is no
>> weird problem. But I read on the internet saying that the
>> source.list should not mix up with different version. For instance,
>> Debian 11 with testing. So I am wondering if there is a better way
>> to switch to testing? Or reinstalling is the only way to go?
> 
> If you change all instances of bullseye -> testing, then you are not 
> mixing. Go ahead with that, modulo the standard caveats associated
> with running testing. The problem would come if you tried to include
> both bullseye *and* testing sources in your sources.list. Then you
> might create very difficult to resolve problems.

Are you sure about that last part?

I have been running with (e.g.)

deb http://ftp.us.debian.org/debian/ stable main non-free contrib
deb http://ftp.us.debian.org/debian/ testing main non-free contrib

for over a decade, and while there have been some problems, I think
they've been basically the same ones I'd have seen from running testing
alone; none of them have seemed terribly difficult to resolve, either.
(At least not by my standards, although I'll admit that I may not be the
best or most representative example.)

I don't particularly consider this mixing releases; it's more tracking
testing, while still keeping available any packages which were in stable
but have been removed from testing.

IMO, if you're going to track testing at all on a production computer
(as opposed to, well, for the purpose of actually *testing the upcoming
release*), it only makes sense to also include stable; there's too much
chance of an important package being (temporarily or permanently)
unavailable, otherwise.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw

signature.asc
Description: OpenPGP digital signature

Re: How to update Debian 11 source.list to testing?

On Fri, Sep 03, 2021 at 04:11:49PM +0200, Richard Forst wrote:
> I just installed Debian using netinstall image. I thought I install testing 
> version, but apparently it's Debian 11. So now my source.list looks like 
> below:
> 
>     deb http://deb.debian.org/debian/ bullseye main non-free contrib
>     deb-src http://deb.debian.org/debian/ bullseye main non-free contrib
> 
>     deb http://security.debian.org/debian-security bullseye-security main 
> contrib non-free
>     deb-src http://security.debian.org/debian-security bullseye-security main 
> contrib non-free
> 
>     deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
>     deb-src http://deb.debian.org/debian/ bullseye-updates main contrib 
> non-free
> 
> I want to switch to testing version. In the past I just change the keyword 
> from e.g. bullseye to testing, and generally there is no weird problem. But I 
> read on the internet saying that the source.list should not mix up with 
> different version. For instance, Debian 11 with testing. So I am wondering if 
> there is a better way to switch to testing? Or reinstalling is the only way 
> to go?
> 
If you change all instances of bullseye -> testing, then you are not
mixing.  Go ahead with that, modulo the standard caveats associated with
running testing.  The problem would come if you tried to include both
bullseye *and* testing sources in your sources.list.  Then you might
create very difficult to resolve problems.

You might consider using bookwork rather than testing, however.  That is
the name of the testing release and unless you specifically want to
continue tracking testing even after bookwork is released, it is
probably better for most use cases to use the specific release code name
rather than stable or testing.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: how to forbid debhelper to modify /home ?

On Fri, Sep 03, 2021 at 03:41:00PM +0200, Harald Dunkel wrote:
> On 9/3/21 13:57, Roberto C. Sánchez wrote:
> > That sounds like potentially buggy behavior.  Can you give a specific
> > example?
> > 
> 
>   ntp (Debian)
>   sane (Debian)
>   gitlab-runner (not Debian)
>   zabbix-agent (not Debian)
> 
> Apparently the postinst scripts of ntp and sane have been fixed.
> I don't want to blame anybody, anyway.
> 

No worries.  It's not a question of blame.  Rather, maintainers
sometimes overlook what to them are trivial things but which impact
different use cases which they might not have considered.

As far as ntp, as Greg pointed out, it did at one time not specify a
directory in the postinst script's adduser command, which would have
resulted in the directory /home/ntp being specified.  However, as far
back as I was able to conveniently look, the --no-create-home option was
passed to adduser.  Based on that, it seems very unlikely that the
postinst script would ever create that directory.  Of course, in more
recent versions, the home directory is explicitly listed as
/nonexistent.  I can't find a good explanation for how you might have
ended up with /home/ntp being present on your system.

On the other hand, sane has logic from around version 1.0.24-6 (December
2014) that changes the saned user home directory from /home/saned to
/var/lib/saned.  It would seem, however, that if /home/saned was
present, that it does not actually get relocated, so that directory
might remain on a system that had saned installed long enough ago to
have been using the former home directory location.

As far as the others, I don't know about their scripts.

As to your initial question, is it possible to somehow prevent or
redirect dpkg from making modifications under /home?  The answer is,
probably not easily.

The maintainer scripts executed by dpkg are mostly shell scripts (though
I think some packages use Perl scripts).  They can execute arbitrary
commands and are run as root.  The ability to prevent modifications to
/home depends on the functioning of the commands invoked from the
maintainer scripts, which as you've noted, can include adduser, deluser,
rm, cp, mv, and any of a number of other commands along with
dpkg-specific helper commands.

If you have /home in a good state, and you want to at least be made
aware of future directory creation operations, I recommend a tool like
incron.  You can set it to specifically look for new directory creations
under /home, which you could either have logged or execute an arbitrary
command in response.  You can certainly get much fancier with it, but I
have found it to be rather of annoyance if I make it too sensitive or
have it monitoring too many things, just because of the noise in the
logs.

Regards,

-Roberto
-- 
Roberto C. Sánchez

How to update Debian 11 source.list to testing?

I just installed Debian using netinstall image. I thought I install testing 
version, but apparently it's Debian 11. So now my source.list looks like below:

    deb http://deb.debian.org/debian/ bullseye main non-free contrib
    deb-src http://deb.debian.org/debian/ bullseye main non-free contrib

    deb http://security.debian.org/debian-security bullseye-security main 
contrib non-free
    deb-src http://security.debian.org/debian-security bullseye-security main 
contrib non-free

    deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
    deb-src http://deb.debian.org/debian/ bullseye-updates main contrib non-free

I want to switch to testing version. In the past I just change the keyword from 
e.g. bullseye to testing, and generally there is no weird problem. But I read 
on the internet saying that the source.list should not mix up with different 
version. For instance, Debian 11 with testing. So I am wondering if there is a 
better way to switch to testing? Or reinstalling is the only way to go?

Thanks

Re: how to forbid debhelper to modify /home ?

2021-09-03 Thread Harald Dunkel


On 9/3/21 13:57, Roberto C. Sánchez wrote:

That sounds like potentially buggy behavior.  Can you give a specific
example?



ntp (Debian)
sane (Debian)
gitlab-runner (not Debian)
zabbix-agent (not Debian)

Apparently the postinst scripts of ntp and sane have been fixed.
I don't want to blame anybody, anyway.

Re: how to forbid debhelper to modify /home ?

2021-09-03 Thread Harald Dunkel


On 9/3/21 11:40, Erwan David wrote:


I would do this the other way (but not eay tpo migrate) : add your users
in another directory (/srv/home or something else) where you mpount your
remote home directory, and keep system using /home.



I agree, but unfortunately this is not an option.

Re: Réseau et route

2021-09-03 Thread David Martin

nickel merci


Le ven. 3 sept. 2021 à 14:49, Yahoo  a écrit :

> Bonjour,
>
> dans la configuration GUI de Network manager, dans le paramétrage de
> compte VPN,  il y a une option à cocher qui est : N'utiliser cette
> connexion que pour les ressources sur ce réseau.
>
> Cette option permet de laisser ta route par défaut de ta connexion local.
>
> Cdt.
> Le 03/09/2021 à 14:25, David Martin a écrit :
>
> Bonjour à tous,
>
> J'utilise une connexion VPN pour des accès distant sur des serveurs au
> boulot.
> J'ai donc configuré une connexion VPN dans network-manager, mais pour
> retrouver internet je dois le désactiver, et ainsi de suite.
>
> Mes collègues sous windows eux, le net fonctionne et ont accès au serveur
> via le vpn.
>
> la commande route -n avant d'activer le vpn
>
> Destination Passerelle  Genmask Indic Metric RefUse
> Iface
> 0.0.0.0 192.168.157.1   0.0.0.0 UG10000
> eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00
> eth0
> 192.168.157.0   0.0.0.0 255.255.255.0   U 10000
> eth0
>
> et après l'avoir activé
>
> Table de routage IP du noyau
> Destination Passerelle  Genmask Indic Metric RefUse
> Iface
> 0.0.0.0 0.0.0.0 0.0.0.0 U 50 00
> ppp0
> 0.0.0.0 192.168.157.1   0.0.0.0 UG10000
> eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00
> eth0
> 172.16.0.0  10.0.194.22 255.255.0.0 UG50 00
> ppp0
> 172.17.0.0  10.0.194.22 255.255.0.0 UG50 00
> ppp0
> 172.18.0.0  10.0.194.22 255.255.0.0 UG50 00
> ppp0
> 172.19.0.0  10.0.194.22 255.255.0.0 UG50 00
> ppp0
> 172.22.234.010.0.194.22 255.255.254.0   UG50 00
> ppp0
> 192.0.2.1   0.0.0.0 255.255.255.255 UH50 00
> ppp0
> 192.168.157.0   0.0.0.0 255.255.255.0   U 10000
> eth0
> 192.168.157.1   0.0.0.0 255.255.255.255 UH10000
> eth0
> 195.83.235.250  192.168.157.1   255.255.255.255 UGH   10000
> eth0
>
> Comment puis-je faire ? si sous linux c'est possible
>
> --
> david martin
>
>

-- 
david martin

Re: Réseau et route

2021-09-03 Thread David Martin

Salut,

Merci pour ta réponse. J'ai activé la fonction utiliser cette connexion
uniquement les ressources de son réseau.
Ca ma supprimé la route. et du coup j'ai ceci :

route -n
Table de routage IP du noyau
Destination Passerelle  Genmask Indic Metric RefUse
Iface
0.0.0.0 192.168.157.1   0.0.0.0 UG10000 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 eth0
172.16.0.0  10.0.194.19 255.255.0.0 UG50 00 ppp0
172.17.0.0  10.0.194.19 255.255.0.0 UG50 00 ppp0
172.18.0.0  10.0.194.19 255.255.0.0 UG50 00 ppp0
172.19.0.0  10.0.194.19 255.255.0.0 UG50 00 ppp0
172.22.234.010.0.194.19 255.255.254.0   UG50 00 ppp0
192.0.2.1   0.0.0.0 255.255.255.255 UH50 00 ppp0
192.168.157.0   0.0.0.0 255.255.255.0   U 10000 eth0
192.168.157.1   0.0.0.0 255.255.255.255 UH10000 eth0
195.83.235.250  192.168.157.1   255.255.255.255 UGH   10000 eth0

Ca fonctionne.
Merci beaucpou


-- 
david martin

Re: gcc-10: options order important?

2021-09-03 Thread Tixy

On Fri, 2021-09-03 at 14:10 +0100, Tixy wrote:
> On Fri, 2021-09-03 at 12:24 +0200, Piotr A. Dybczyński wrote:
> > Hi,
> > 
> > in contrary to previous versions, now in Debian 11 with gcc-10:
> > 
> > gcc aa.c -lm -o aa   works, but
> > 
> > gcc -lm aa.c -o aa   does not work, saying: 
> 
> [...]
> 
> > It seems that an option -lm cannot be placed in an arbitrary place which I 
> > used to
> > do. Is this intentional ?
> 
> I found this too, I just modified my Makefiles to have libraries after
> input files.
> 
> A man page a found online [1] says linking happens as Greg described, 
> and this is true looking at a 6 year old copy of that page on
> archive.org. So seems strange that for many years my Makefiles have
> worked with Libraries specified before inputs that use them.

Correction... 'for many years my Makefiles have worked with Libraries
specified _after_ inputs that use them'

-- 
Tixy

Re: how to forbid debhelper to modify /home ?

2021-09-03 Thread Sven Hartge

Roberto C. Sánchez  wrote:
> On Fri, Sep 03, 2021 at 08:03:23AM -0400, Greg Wooledge wrote:

>> Out of curiosity, I checked my system to see if there were any system
>> users with home directories under /home.  The only one I found is "ntp".
>> 
>> Then I looked at the ntp.postinst script, and it has this:
>> 
>> adduser --system --quiet --ingroup ntp --no-create-home --home /nonexistent 
>> ntp
>> 
>> So presumably my ntp user with /home/ntp as its home directory is from
>> an older Debian release, and if it had been created under bullseye, it
>> would look different.
 
> How old is your system?  I just checked a machine that I initially as a
> Woody (3.0) system in 2001 and there is no ntp user directory under
> /home.

I have a system that was installed as either Slink (2.1) or Potato (2.2)
and then kept on Unstable ever since.

I *do* have 

sshd:x:104:65534::/home/sshd:/usr/sbin/nologin
ntp:x:106:117::/home/ntp:/bin/false
cupsys:x:130:106::/home/cupsys:/bin/false

I don't have the directories, though. (Might have gotten lost over the
years, though.)

So there was a time in the past when system users home dirs were created in 
/home.

Grüße,
S°

-- 
Sigmentation fault. Core dumped.

Re: gcc-10: options order important?

2021-09-03 Thread Tixy

On Fri, 2021-09-03 at 12:24 +0200, Piotr A. Dybczyński wrote:
> Hi,
> 
> in contrary to previous versions, now in Debian 11 with gcc-10:
> 
> gcc aa.c -lm -o aa   works, but
> 
> gcc -lm aa.c -o aa   does not work, saying: 

[...]

> It seems that an option -lm cannot be placed in an arbitrary place which I 
> used to
> do. Is this intentional ?

I found this too, I just modified my Makefiles to have libraries after
input files.

A man page a found online [1] says linking happens as Greg described, 
and this is true looking at a 6 year old copy of that page on
archive.org. So seems strange that for many years my Makefiles have
worked with Libraries specified before inputs that use them.

-- 
Tixy

Re: Réseau et route

2021-09-03 Thread Yahoo


Bonjour,

dans la configuration GUI de Network manager, dans le paramétrage de 
compte VPN,  il y a une option à cocher qui est : N'utiliser cette 
connexion que pour les ressources sur ce réseau.


Cette option permet de laisser ta route par défaut de ta connexion local.

Cdt.

Le 03/09/2021 à 14:25, David Martin a écrit :

Bonjour à tous,

J'utilise une connexion VPN pour des accès distant sur des serveurs au 
boulot.
J'ai donc configuré une connexion VPN dans network-manager, mais pour 
retrouver internet je dois le désactiver, et ainsi de suite.


Mes collègues sous windows eux, le net fonctionne et ont accès au 
serveur via le vpn.


la commande route -n avant d'activer le vpn

Destination     Passerelle      Genmask         Indic Metric Ref   
 Use Iface

0.0.0.0         192.168.157.1   0.0.0.0         UG    100  0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1000 0        0 eth0
192.168.157.0   0.0.0.0         255.255.255.0   U     100  0        0 eth0

et après l'avoir activé

Table de routage IP du noyau
Destination     Passerelle      Genmask         Indic Metric Ref   
 Use Iface

0.0.0.0         0.0.0.0         0.0.0.0         U     50   0        0 ppp0
0.0.0.0         192.168.157.1   0.0.0.0         UG    100    0       
 0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0       
 0 eth0

172.16.0.0      10.0.194.22     255.255.0.0     UG    50   0        0 ppp0
172.17.0.0      10.0.194.22     255.255.0.0     UG    50   0        0 ppp0
172.18.0.0      10.0.194.22     255.255.0.0     UG    50   0        0 ppp0
172.19.0.0      10.0.194.22     255.255.0.0     UG    50   0        0 ppp0
172.22.234.0    10.0.194.22     255.255.254.0   UG    50   0        0 ppp0
192.0.2.1       0.0.0.0         255.255.255.255 UH    50   0        0 ppp0
192.168.157.0   0.0.0.0         255.255.255.0   U     100    0       
 0 eth0
192.168.157.1   0.0.0.0         255.255.255.255 UH    100    0       
 0 eth0
195.83.235.250  192.168.157.1   255.255.255.255 UGH   100    0       
 0 eth0


Comment puis-je faire ? si sous linux c'est possible

--
david martin

Re: how to forbid debhelper to modify /home ?

On Fri, Sep 03, 2021 at 08:39:09AM -0400, Roberto C. Sánchez wrote:
> So, the existence of /home/ntp on the OP's system, or any system
> installed from a Debian release prior to the last 4-ish years, could be
> attributed to some process or series of actions that decides, "hey, this
> ntp user's home directory is missing, I should create it".  Whether
> those actions be manual or the result of some script or service, that
> seems the most likely way for that directory to appear on a system.

We haven't heard back from the OP yet.  We don't know what packages
and/or directories they're talking about.

In my case, there *isn't* an actual /home/ntp directory.  It's just
specified in /etc/passwd as the user's home directory.

Re: how to forbid debhelper to modify /home ?

On Fri, Sep 03, 2021 at 08:33:25AM -0400, Greg Wooledge wrote:
> On Fri, Sep 03, 2021 at 08:23:07AM -0400, Roberto C. Sánchez wrote:
> > On Fri, Sep 03, 2021 at 08:03:23AM -0400, Greg Wooledge wrote:
> > > Out of curiosity, I checked my system to see if there were any system
> > > users with home directories under /home.  The only one I found is "ntp".
> 
> > How old is your system?  I just checked a machine that I initially as a
> > Woody (3.0) system in 2001 and there is no ntp user directory under
> > /home.
> 
> Well, you probably didn't install the ntp pacakge. ;-)
> 
> I *think* this system was installed as stretch, so I downloaded a stretch
> package of ntp:
> 
> unicorn:~/tmp/x$ dpkg-deb -R ../ntp_4.2.8p10+dfsg-3+deb9u2_amd64.deb .
> unicorn:~/tmp/x$ grep adduser DEBIAN/postinst 
>   adduser --system --quiet --ingroup ntp --no-create-home ntp
> 
> I'm not 100% sure, but I think that creates a user with a home directory
> under /home, even though it doesn't actually create that directory.
> 
> I also just fired up a fresh wheezy chroot and the ntp postinst
> > has this:
> > 
> > adduser --system --quiet --ingroup ntp --no-create-home ntp
> > 
> > Did you perhaps modify your ntp config at a time when you might have
> > been limited on space under /var?
> 
> ... uh, I don't think so?
> 
> Let's test this sucker and find out:
> 
> unicorn:~/tmp/x$ sudo adduser --system --quiet --ingroup ntp --no-create-home 
> zzntp
> unicorn:~/tmp/x$ grep zzntp /etc/passwd 
> zzntp:x:115:112::/home/zzntp:/usr/sbin/nologin
> 
> As I guessed.  That's what it did.

Quite right.  That explains the motivation a few years ago to begin
explicitly specifying the home directory as /nonexistent for system
users not meant to have an actual home directory.

So, the existence of /home/ntp on the OP's system, or any system
installed from a Debian release prior to the last 4-ish years, could be
attributed to some process or series of actions that decides, "hey, this
ntp user's home directory is missing, I should create it".  Whether
those actions be manual or the result of some script or service, that
seems the most likely way for that directory to appear on a system.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: how to forbid debhelper to modify /home ?

On Fri, Sep 03, 2021 at 08:23:07AM -0400, Roberto C. Sánchez wrote:
> On Fri, Sep 03, 2021 at 08:03:23AM -0400, Greg Wooledge wrote:
> > Out of curiosity, I checked my system to see if there were any system
> > users with home directories under /home.  The only one I found is "ntp".

> How old is your system?  I just checked a machine that I initially as a
> Woody (3.0) system in 2001 and there is no ntp user directory under
> /home.

Well, you probably didn't install the ntp pacakge. ;-)

I *think* this system was installed as stretch, so I downloaded a stretch
package of ntp:

unicorn:~/tmp/x$ dpkg-deb -R ../ntp_4.2.8p10+dfsg-3+deb9u2_amd64.deb .
unicorn:~/tmp/x$ grep adduser DEBIAN/postinst 
adduser --system --quiet --ingroup ntp --no-create-home ntp

I'm not 100% sure, but I think that creates a user with a home directory
under /home, even though it doesn't actually create that directory.

I also just fired up a fresh wheezy chroot and the ntp postinst
> has this:
> 
> adduser --system --quiet --ingroup ntp --no-create-home ntp
> 
> Did you perhaps modify your ntp config at a time when you might have
> been limited on space under /var?

... uh, I don't think so?

Let's test this sucker and find out:

unicorn:~/tmp/x$ sudo adduser --system --quiet --ingroup ntp --no-create-home 
zzntp
unicorn:~/tmp/x$ grep zzntp /etc/passwd 
zzntp:x:115:112::/home/zzntp:/usr/sbin/nologin

As I guessed.  That's what it did.

Re: Réseau et route

2021-09-03 Thread NoSpam


Bonjour

Le 03/09/2021 à 14:25, David Martin a écrit :

Bonjour à tous,

J'utilise une connexion VPN pour des accès distant sur des serveurs au 
boulot.
J'ai donc configuré une connexion VPN dans network-manager, mais pour 
retrouver internet je dois le désactiver, et ainsi de suite.


Mes collègues sous windows eux, le net fonctionne et ont accès au 
serveur via le vpn.


la commande route -n avant d'activer le vpn

Destination     Passerelle      Genmask         Indic Metric Ref   
 Use Iface

0.0.0.0         192.168.157.1   0.0.0.0         UG    100  0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1000 0        0 eth0
192.168.157.0   0.0.0.0         255.255.255.0   U     100  0        0 eth0

et après l'avoir activé

Table de routage IP du noyau
Destination     Passerelle      Genmask         Indic Metric Ref   
 Use Iface

0.0.0.0         0.0.0.0         0.0.0.0         U     50   0        0 ppp0


Supprimer cette route ip r del 0.0.0.0/0 dev ppp0

ou dire à NM de ne pas rajouter de route par défaut


0.0.0.0         192.168.157.1   0.0.0.0         UG  100    0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0       
 0 eth0

172.16.0.0      10.0.194.22     255.255.0.0     UG    50   0        0 ppp0
172.17.0.0      10.0.194.22     255.255.0.0     UG    50   0        0 ppp0
172.18.0.0      10.0.194.22     255.255.0.0     UG    50   0        0 ppp0
172.19.0.0      10.0.194.22     255.255.0.0     UG    50   0        0 ppp0
172.22.234.0    10.0.194.22     255.255.254.0   UG    50   0        0 ppp0
192.0.2.1       0.0.0.0         255.255.255.255 UH    50   0        0 ppp0
192.168.157.0   0.0.0.0         255.255.255.0   U     100    0       
 0 eth0
192.168.157.1   0.0.0.0         255.255.255.255 UH    100    0       
 0 eth0
195.83.235.250  192.168.157.1   255.255.255.255 UGH   100    0       
 0 eth0


Comment puis-je faire ? si sous linux c'est possible

--
david martin

Réseau et route

2021-09-03 Thread David Martin

Bonjour à tous,

J'utilise une connexion VPN pour des accès distant sur des serveurs au
boulot.
J'ai donc configuré une connexion VPN dans network-manager, mais pour
retrouver internet je dois le désactiver, et ainsi de suite.

Mes collègues sous windows eux, le net fonctionne et ont accès au serveur
via le vpn.

la commande route -n avant d'activer le vpn

Destination Passerelle  Genmask Indic Metric RefUse
Iface
0.0.0.0 192.168.157.1   0.0.0.0 UG10000 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 eth0
192.168.157.0   0.0.0.0 255.255.255.0   U 10000 eth0

et après l'avoir activé

Table de routage IP du noyau
Destination Passerelle  Genmask Indic Metric RefUse
Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 50 00 ppp0
0.0.0.0 192.168.157.1   0.0.0.0 UG10000 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 eth0
172.16.0.0  10.0.194.22 255.255.0.0 UG50 00 ppp0
172.17.0.0  10.0.194.22 255.255.0.0 UG50 00 ppp0
172.18.0.0  10.0.194.22 255.255.0.0 UG50 00 ppp0
172.19.0.0  10.0.194.22 255.255.0.0 UG50 00 ppp0
172.22.234.010.0.194.22 255.255.254.0   UG50 00 ppp0
192.0.2.1   0.0.0.0 255.255.255.255 UH50 00 ppp0
192.168.157.0   0.0.0.0 255.255.255.0   U 10000 eth0
192.168.157.1   0.0.0.0 255.255.255.255 UH10000 eth0
195.83.235.250  192.168.157.1   255.255.255.255 UGH   10000 eth0

Comment puis-je faire ? si sous linux c'est possible

-- 
david martin

Re: how to forbid debhelper to modify /home ?

On Fri, Sep 03, 2021 at 08:03:23AM -0400, Greg Wooledge wrote:
> On Fri, Sep 03, 2021 at 07:57:44AM -0400, Roberto C. Sánchez wrote:
> > On Fri, Sep 03, 2021 at 11:14:45AM +0200, Harald Dunkel wrote:
> > > Hi folks,
> > > 
> > > how can I tell the debhelper scripts to not install home directories
> > > for system services in /home (managed on a remote host in my environment),
> > > but to use /var/lib instead?
> > > 
> > That sounds like potentially buggy behavior.  Can you give a specific
> > example?
> 
> Out of curiosity, I checked my system to see if there were any system
> users with home directories under /home.  The only one I found is "ntp".
> 
> Then I looked at the ntp.postinst script, and it has this:
> 
> adduser --system --quiet --ingroup ntp --no-create-home --home /nonexistent 
> ntp
> 
> So presumably my ntp user with /home/ntp as its home directory is from
> an older Debian release, and if it had been created under bullseye, it
> would look different.
> 
How old is your system?  I just checked a machine that I initially as a
Woody (3.0) system in 2001 and there is no ntp user directory under
/home.  I also just fired up a fresh wheezy chroot and the ntp postinst
has this:

adduser --system --quiet --ingroup ntp --no-create-home ntp

Did you perhaps modify your ntp config at a time when you might have
been limited on space under /var?

> Granted, I have only my specific subset of Debian packages installed,
> and there could be others that still make system user home directories
> in /home.  We'll have to await further details from the OP.
> 

As a Debian Developer, I would consider it bad form to go creating
things under /home from a package's maintainer script, though that does
not appear to be a specific policy violation.  In my own case, I don't
locate user home directories under /home for most users, so this sort of
behavior would very likely have triggered jumped out at me.  I have
not in my recollection encountered a Debian package that has done this.

I too would be interested to know more details from the OP.

Regards,

-Roberto
-- 
Roberto C. Sánchez

Re: how to forbid debhelper to modify /home ?

2021-09-03 Thread Andrew M.A. Cater

On Fri, Sep 03, 2021 at 08:03:23AM -0400, Greg Wooledge wrote:
> On Fri, Sep 03, 2021 at 07:57:44AM -0400, Roberto C. Sánchez wrote:
> > On Fri, Sep 03, 2021 at 11:14:45AM +0200, Harald Dunkel wrote:
> > > Hi folks,
> > > 
> > > how can I tell the debhelper scripts to not install home directories
> > > for system services in /home (managed on a remote host in my environment),
> > > but to use /var/lib instead?
> > > 
> > That sounds like potentially buggy behavior.  Can you give a specific
> > example?
> 
> Out of curiosity, I checked my system to see if there were any system
> users with home directories under /home.  The only one I found is "ntp".
> 
> Then I looked at the ntp.postinst script, and it has this:
> 
> adduser --system --quiet --ingroup ntp --no-create-home --home /nonexistent 
> ntp
> 
> So presumably my ntp user with /home/ntp as its home directory is from
> an older Debian release, and if it had been created under bullseye, it
> would look different.
> 
> Granted, I have only my specific subset of Debian packages installed,
> and there could be others that still make system user home directories
> in /home.  We'll have to await further details from the OP.
> 

As another datum point, this is a fairly newly installed Debian 11 system,
the only user in /home is the single human user on this system. This is a
full GNOME desktop so has services running. I'd anticipate that everything
service related would now be under /etc or /etc/default/

All best, as ever,

Andy Cater

Re: how to forbid debhelper to modify /home ?

2021-09-03 Thread rhkramer

On Friday, September 03, 2021 05:40:18 AM Erwan David wrote:
> Le 03/09/2021 à 11:14, Harald Dunkel a écrit :
> > how can I tell the debhelper scripts to not install home directories
> > for system services in /home (managed on a remote host in my
> > environment), but to use /var/lib instead?

> I would do this the other way (but not eay tpo migrate) : add your users
> in another directory (/srv/home or something else) where you mpount your
> remote home directory, and keep system using /home.

Especially if you have only one user, I would mount your remote home directory 
(presumably containing your "real user data" documents, photos, etc) as a top 
level directory, /.

Re: how to forbid debhelper to modify /home ?

On Fri, Sep 03, 2021 at 07:57:44AM -0400, Roberto C. Sánchez wrote:
> On Fri, Sep 03, 2021 at 11:14:45AM +0200, Harald Dunkel wrote:
> > Hi folks,
> > 
> > how can I tell the debhelper scripts to not install home directories
> > for system services in /home (managed on a remote host in my environment),
> > but to use /var/lib instead?
> > 
> That sounds like potentially buggy behavior.  Can you give a specific
> example?

Out of curiosity, I checked my system to see if there were any system
users with home directories under /home.  The only one I found is "ntp".

Then I looked at the ntp.postinst script, and it has this:

adduser --system --quiet --ingroup ntp --no-create-home --home /nonexistent ntp

So presumably my ntp user with /home/ntp as its home directory is from
an older Debian release, and if it had been created under bullseye, it
would look different.

Granted, I have only my specific subset of Debian packages installed,
and there could be others that still make system user home directories
in /home.  We'll have to await further details from the OP.

Re: how to forbid debhelper to modify /home ?

On Fri, Sep 03, 2021 at 11:14:45AM +0200, Harald Dunkel wrote:
> Hi folks,
> 
> how can I tell the debhelper scripts to not install home directories
> for system services in /home (managed on a remote host in my environment),
> but to use /var/lib instead?
> 
That sounds like potentially buggy behavior.  Can you give a specific
example?

Regards,

-Roberto

-- 
Roberto C. Sánchez

Clamav question ^^)

2021-09-03 Thread Jean-François Bachelet


Hello ^^)


dans la doc de Clamav, section update, il est dit :


'Also make sure that you haven't got old libraries (|libclamav.so*|) 
lying around your filesystem. You can verify it using:


|ldd $(which freshclam)' trad : 'soyez sur de ne pas avoir de vieilles 
librairies (libclamav.so*) qui trainent sur votre disque dur, vous 
pouvez vérifier avec :|

|ldd $(which freshclam)'|

or :
 
#|ldd $(which freshclam)|

linux-vdso.so.1 (0x7ffea9559000)
--> libclamav.so.9 => /lib/x86_64-linux-gnu/libclamav.so.9 
(0x7fc1a9a4e000)
libfreshclam.so.2 => /lib/x86_64-linux-gnu/libfreshclam.so.2 
(0x7fc1a9a18000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fc1a99f6000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fc1a9831000)
libjson-c.so.5 => /lib/x86_64-linux-gnu/libjson-c.so.5 
(0x7fc1a981e000)
etc...


bin y en a une. méheu !
ce doit être un laissé pour compte de la version précédente de clamav après la 
mise à jour de debian 10 vers la 11...
clamav est installé en version 0.103.2 (dernière version dispo dans les 
paquets) et upgradable en version 0.103.3 (pas encore dispo dans les paquets).


Question : comment on s'en débarrasse de cette vieille lib ? le 'apt remove 
--auto-remove' ne fait rien ici.


Merci d'avance,
Jeff||

Re: gcc-10: options order important?

On Fri, Sep 03, 2021 at 12:24:39PM +0200, Piotr A. Dybczyński wrote:
> Hi,
> 
> in contrary to previous versions, now in Debian 11 with gcc-10:
> 
> gcc aa.c -lm -o aa   works, but
> 
> gcc -lm aa.c -o aa   does not work, saying: 
> 
> /usr/bin/ld: /tmp/ccWyhudO.o: in function `main':
> aa.c:(.text+0x1f): undefined reference to `sqrt'
> collect2: error: ld returned 1 exit status

If this *ever* worked in the past, it was dumb luck.  Libraries need
to be given after the objects that use them.  That's how the linker
operates.

You can think of it this way: the linker scans through the list of object
files and libraries in a single pass, left to right.  In your non-working
command, the first thing it encounters is -lm (math library).  So it
checks for any unresolved symbols that it currently has, and tries to
match them against the math library.  There aren't any unresolved symbols
at this point (because no object files have been linked in yet), so it
doesn't pull anything out of the math library.

Next it encounters aa.o (implicitly compiled from aa.c), and it links in
that object file, which may have some unresolved symbols.  If there are
any, the linker expects that it'll be given a library afterward, to look
them up.

But... there is no library given after that.  It doesn't go *back* to
look at the math library a second time.

Re: ping6 impossible/très lent depuis Debian sid et bullseye

2021-09-03 Thread NoSpam


Bonjour

Le 03/09/2021 à 13:06, Cédric Boutillier a écrit :

Bonjour Joël,


Y a-t-il une passerelle définie ? Quel est le retour de la commande
route -A inet6 ?

Déjà là, c'est un peu bizarre : quand je suis branché en ethernet

$ sudo route -A inet6
Table de routage IPv6 du noyau
DestinationNext Hop   Flag Met Ref Use If
localhost/128  [::]   U256 1 0 lo
[::]/0 [::]   !n   -1  1 0 lo
localhost/128  [::]   Un   0   10 0 lo
[::]/0 [::]   !n   -1  1 0 lo

mon interface ethernet n'apparait pas du tout.
Faut regarder du côté de la définition des interfaces si ipv6 est activé 
sur la carte ethernet

--
Daniel

Re: GLIBCXX_3.4.29

2021-09-03 Thread Paul van der Vlis


Op 03-09-2021 om 09:46 schreef Martijn van de Streek:

Paul van der Vlis schreef op do 02-09-2021 om 20:32 [+0200]:

Iemand vroeg me een computer te bouwen voor iets wat Pixinsight heet:
https://pixinsight.com/sysreq/

Punt is dat dit GLIBCXX_3.4.29 nodig heeft, en Debian 11 biedt 3.4.2


Deze ABIs veranderen/worden nieuw gemaakt als er nieuwe features worden
toegevoegd die niet 100% compatible zijn. GCC 11 heeft extra C++17 en
C++20 features, met bijbehordende nieuwe ABIs. Dit is toegevoegd in de
volgende commit:

https://github.com/gcc-mirror/gcc/commit/932fbc868ad429167a3d4d5625aa9d6dc0b4506b

Debian Bullseye heeft GCC 10, en heeft daarom die nieuwere ABI nog
niet.

De "sysreq" pagina van Pixinsight lijkt me dan ook niet helemaal te
kloppen want die zeggen:


  PixInsight 1.8.8-8 for Linux requires a 64-bit Linux distribution
with glibc version 2.27 (January 2018) or later and GLIBCXX_3.4.29 /
CXXABI_1.3.12 (GCC 9.3.0 or later).


CXXABI_1.3.12 is inderdaad toegevoegd in GCC 9:
https://github.com/gcc-mirror/gcc/commit/c124af936b6b225eb548ccdd7f01400511d784dc

Maar GLIBCXX_3.4.29 zit pas in GCC 11.


Mijn indruk is ook dat het niet helemaal klopt, wellicht moet ik maar 
eens contact opnemen met de makers.


Bedankt voor de hulp, hetzelfde voor Henk!

Groet,
Paul


--
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Re: ping6 impossible/très lent depuis Debian sid et bullseye

2021-09-03 Thread Cédric Boutillier

Bonjour Joël,

> 
>   Y a-t-il une passerelle définie ? Quel est le retour de la commande
> route -A inet6 ?

Déjà là, c'est un peu bizarre : quand je suis branché en ethernet

$ sudo route -A inet6
Table de routage IPv6 du noyau
DestinationNext Hop   Flag Met Ref Use If
localhost/128  [::]   U256 1 0 lo
[::]/0 [::]   !n   -1  1 0 lo
localhost/128  [::]   Un   0   10 0 lo
[::]/0 [::]   !n   -1  1 0 lo

mon interface ethernet n'apparait pas du tout.

En allumant le wifi:
$ sudo route -A inet6
Table de routage IPv6 du noyau
DestinationNext Hop   Flag Met Ref Use If
localhost/128  [::]   U256 2 0 lo
2a01:e0a:27a:ab50::/64 [::]   U600 1 0 wlo1
2a01:e35:1384:2d50::/64[::]   U600 2 0 wlo1
fe80::/64  [::]   U600 1 0 wlo1
[::]/0 fe80::de00:b0ff:fe3a:9e88  UG   600 5 0 wlo1
[::]/0 fe80::208:9bff:fed1:21dd   UG   600 6 0 wlo1
localhost/128  [::]   Un   0   11 0 lo
2a01:e0a:27a:ab50:3320:dcd7:4002:df4/128 [::]   Un   0   2  
   0 wlo1
2a01:e35:1384:2d50:242a:9d63:7221:7bbf/128 [::]   Un   0   
3 0 wlo1
fe80::de1f:f530:8c6c:4af1/128  [::]   Un   0   4 0 wlo1
ff00::/8   [::]   U256 5 0 wlo1
[::]/0 [::]   !n   -1  1 0 lo

Il semble donc que la freebox configure les interfaces wifi et ethernet
pour le routage différemment. Déjà bizarre. Quelquechose que je n'avais
pas envisagé. Cela pourrait expliquer partiellement la différence que
j'avais noté "Debian marche pas"/"mac marche", car le portable mac testé
était en wifi, et les machines Debian toutes en ethernet ?

Donc sans wifi, purement ethernet, il semble que je n'ai qu'une
connectivité ipv4. Pourtant que se passe-t-il quand j'essaie une
connection SSH ? si le MTU de la carte ethernet est de l'ordre de 1200,
c'est l'ipv4 du server qui est résolue, et la connexion aboutit
rapidement.

debug1: Connecting to master.debian.org [82.195.75.110] port 22.

Si le MTU est à 1500, alors c'est une connexion vers une adresse ipv6
qui est tentée, et 

debug1: Connecting to master.debian.org 
[2001:41b8:202:deb:216:36ff:fe40:4001] port 22.
elle timeout au bout de plusieurs minutes pour rebasculer sur l'ipv4,
qui finit par aboutir.

Il se passe exactement la même chose lorsque je tente une connexion ssh
avec wifi (sans ethernet) : ipv4 pour bas MTU, ipv6 qui timeout pour un
MTU par défaut à 1500.

>   Comment sont définies les adresses ? Statiques ou dynamiques ? Et si
> dynamiques, par quoi ? Le routage IPv6 est un truc délirant, certains
> outils se débrouillant avec des adresses locales, d'autres non (j'ai
> déjà vu des OS se débrouiller avec une passerelle en fe80:..., d'autres
> refusent catégoriquement.).

Les adresses sont dynamiques, données par la freebox qui sert de serveur
dhcp.

>   Je ne pencherai pas ici pour un problème de MTU, mais pour un problème
> de routage ou de configuration automatique IPv6.

Comment faire maintenant pour résoudre ces connexions ipv6 qui timeout
sans désactiver brutalement l'ipv6 ? J'ai un petit routeur qui traine.
Je peux essayer de le mettre derrière la freebox et passer celle-ci en
mode bridge. C'est raisonnable ?

Merci et bonne journée

Cédric

gcc-10: options order important?

2021-09-03 Thread Piotr A. Dybczyński

Hi,

in contrary to previous versions, now in Debian 11 with gcc-10:

gcc aa.c -lm -o aa   works, but

gcc -lm aa.c -o aa   does not work, saying: 

/usr/bin/ld: /tmp/ccWyhudO.o: in function `main':
aa.c:(.text+0x1f): undefined reference to `sqrt'
collect2: error: ld returned 1 exit status

My aa.c content:

---
#include
#include

int main(void)
{
  double x=4;

  printf("sqrt(4)=%f\n",sqrt(x));

  return 0;
}
---

It seems that an option -lm cannot be placed in an arbitrary place which I used 
to
do. Is this intentional ?

Regards,

Piotr A. Dybczyński
-- 
/**
  dr Piotr A. Dybczyński 
 homepage: https://www.dybczynski.pl/Piotr e-mail: pi...@dybczynski.pl
PAD***/

Re: ping6 impossible/très lent depuis Debian sid et bullseye

2021-09-03 Thread Cédric Boutillier

Bonjour Daniel

Le Thu, Sep 02, 2021 at 05:16:56PM +0200, NoSpam a écrit :
> 
> Joue avec la MTU, 1492 passe pour moi.
> 

Merci du tuyau. Ça permet de soigner au moins les symptomes.
J'ai dû descendre à 1250 pour avoir une connection ssh et un traceroute6
qui fonctionnent. Mais c'est extrêment bas, n'est-ce pas ?

Cordialement

Cédric

Re: how to forbid debhelper to modify /home ?

2021-09-03 Thread Erwan David


Le 03/09/2021 à 11:14, Harald Dunkel a écrit :

Hi folks,

how can I tell the debhelper scripts to not install home directories
for system services in /home (managed on a remote host in my environment),
but to use /var/lib instead?

I know I can block dpkg using apparmor, but this would break many
postinst scripts, at least for 3rd-party packages. Some kind of redirect
would be helpful.


Regards
Harri





I would do this the other way (but not eay tpo migrate) : add your users 
in another directory (/srv/home or something else) where you mpount your 
remote home directory, and keep system using /home.

how to forbid debhelper to modify /home ?

2021-09-03 Thread Harald Dunkel


Hi folks,

how can I tell the debhelper scripts to not install home directories
for system services in /home (managed on a remote host in my environment),
but to use /var/lib instead?

I know I can block dpkg using apparmor, but this would break many
postinst scripts, at least for 3rd-party packages. Some kind of redirect
would be helpful.


Regards
Harri

Re: calcul naval en mode "DMS" sur un tableur

2021-09-03 Thread Basile Starynkevitch




On 9/3/21 10:04 AM, Bernard Schoenacker wrote:

Bonjour,

Je recherche une solution facilitant le
calcul de trajectoire sur une feuille de
calcul d'un tableur ...

Pour l'instant je butte sur l'art et la manière
de déclarer les angles ...

Qui pourrais trouver une solution élégante à ce
genre de situation ?



Une possibilité peu élégante est de convertir un angle en radians.

L'avantage est que les fonctions trigonométriques usuelles s'utilisent 
alors facilement.



La conversion de radians en degré + minutes + secondes d'angle se fait 
facilement



--

Basile Starynkevitch  
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/

Re: Install Debian netinstall to HP Elitebook 840 G8 problem

Ok I am kind of getting what goes wrong. First configure boot options to usb in 
bios setting as usual. 

Then do rebooting. After the screen displays HP logo, pressing esc button, 
which will again enter the bios seting or that kind of screen but it will ask 
(the screen will display) with several options, such as

continuous boot
...
boot options
bios setup
...

Then this time, pressing continuous boot or something similar (sorry can't 
remember the name, but it's at the first option). Now it enters to normal boot 
process where lovely debian installer asks me to install or use gui blah blah

It also possible my iso did not burn correctly. I did rebrun iso to usb using 
etcher, which seemingly do validation step. 

Anyway, hopes  this trivial info may be of help to someone who also runs into 
some annoying issues (not debian side) similar like mine. 

Thanks

Sep 3, 2021, 15:46 by sterbl...@tutanota.com:

> I purchased a new laptop HP Elitebook 840 G8, and am trying to install Debian 
> to it. However I encounter a problem. 
>
> I change the bios setting, but when booting from usb. What was shown on the 
> screen is simply a grub env command line like
>
> grub>
>
> instead of a traditional debian install screen which may describe whether to 
> install with GUI or standard mode (non gui). I've repeated installing from 
> netinstall iso many times, but I had never run into such situation. So 
> actually I am stocked. I don't know that's because of UEFI or because the iso 
> burn to usb stick problem (but I check the usb I can see setup.exe, and those 
> bootable files as usual w/t a problem). 
>
> The netinstall iso is downloaded from [1]. Is it expected now to install 
> debian from grub? Or maybe because the iso I download is broken? 
>
> I am scratching my head. So I appreciate any comments or suggestions. Thanks!
>
> [1]. > 
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.0.0+nonfree/amd64/iso-cd/firmware-11.0.0-amd64-netinst.iso
>

Re: calcul naval en mode "DMS" sur un tableur

2021-09-03 Thread Bernard Schoenacker




- Mail original -
> De: "Fab" 
> À: debian-user-french@lists.debian.org
> Envoyé: Vendredi 3 Septembre 2021 10:28:41
> Objet: Re: calcul naval en mode "DMS" sur un tableur
> 
> yes, c'est plus pratique quand on navigue ;)
> 
> 
> J'ai l'impression qu'il n'y a pas de format de donnée °:':'' dans
> libreoffice :(
> 
> Peut-être en se basant la-dessus ?
> https://calculator.academy/dms-calculator-degrees-minutes-seconds/
> 
> Perso, je ferai un doc avec 5 colonnes:
> C1: degré en mode décimal
> C2: degrés
> C3: minutes
> C4: secondes
> C5: et enfin concaténation des colonnes C2°:C3':C4"
> 
> ça fait un peu bricolage mais je vois pas autre chose pour l'instant.
> 
> a+
> 
> f.
> 

Bonjour Fabrice,

Je viens de trouver la solution qui consiste à simplement convertir 
les angles en mode décimal et de réaliser les calculs intermédiaires 
désirés et seulement à la fin de rebasculer via la fonction de 
conversion en mode "DMS" mathématique ...

Merci pour ton aimable attention 

Bien à toi

Bernard

Re: calcul naval en mode "DMS" sur un tableur

2021-09-03 Thread Fab





Désolé, mais il faut aussi prendre en compte toutes les valeurs
en mode "DMS" :

359°:58':58"

yes, c'est plus pratique quand on navigue ;)


J'ai l'impression qu'il n'y a pas de format de donnée °:':'' dans 
libreoffice :(


Peut-être en se basant la-dessus ? 
https://calculator.academy/dms-calculator-degrees-minutes-seconds/


Perso, je ferai un doc avec 5 colonnes:
C1: degré en mode décimal
C2: degrés
C3: minutes
C4: secondes
C5: et enfin concaténation des colonnes C2°:C3':C4"

ça fait un peu bricolage mais je vois pas autre chose pour l'instant.

a+

f.

Re: calcul naval en mode "DMS" sur un tableur

2021-09-03 Thread Bernard Schoenacker




- Mail original -
> De: "Fab" 
> À: debian-user-french@lists.debian.org
> Envoyé: Vendredi 3 Septembre 2021 10:11:37
> Objet: Re: calcul naval en mode "DMS" sur un tableur
> 
> hello,
> 
> Tu considères la mesure des angles de 1° à 360°.
> Donc, si tu appliques un modulo de 360 à toutes tes cellules, ça
> devrait
> coller.
> En revanche, comment gérer les minutes et les secondes ? mais
> peut-être
> que tu n'en a pas besoin ?
> 
> Bonne journée ;)
> 
> f.

Bonjour,

Désolé, mais il faut aussi prendre en compte toutes les valeurs 
en mode "DMS" :

359°:58':58"


Merci

@+

Bernard

Re: calcul naval en mode "DMS" sur un tableur

2021-09-03 Thread Fab


hello,

Tu considères la mesure des angles de 1° à 360°.
Donc, si tu appliques un modulo de 360 à toutes tes cellules, ça devrait 
coller.
En revanche, comment gérer les minutes et les secondes ? mais peut-être 
que tu n'en a pas besoin ?


Bonne journée ;)

f.


Le 03/09/2021 à 10:04, Bernard Schoenacker a écrit :

Bonjour,

Je recherche une solution facilitant le
calcul de trajectoire sur une feuille de
calcul d'un tableur ...

Pour l'instant je butte sur l'art et la manière
de déclarer les angles ...

Qui pourrais trouver une solution élégante à ce
genre de situation ?

Merci pour votre aimable attention

Bien à vous

Bernard

calcul naval en mode "DMS" sur un tableur

2021-09-03 Thread Bernard Schoenacker

Bonjour,

Je recherche une solution facilitant le 
calcul de trajectoire sur une feuille de 
calcul d'un tableur ...

Pour l'instant je butte sur l'art et la manière
de déclarer les angles ...

Qui pourrais trouver une solution élégante à ce
genre de situation ?

Merci pour votre aimable attention

Bien à vous

Bernard

Re: GLIBCXX_3.4.29

2021-09-03 Thread Martijn van de Streek

Paul van der Vlis schreef op do 02-09-2021 om 20:32 [+0200]:
> Iemand vroeg me een computer te bouwen voor iets wat Pixinsight heet:
> https://pixinsight.com/sysreq/
> 
> Punt is dat dit GLIBCXX_3.4.29 nodig heeft, en Debian 11 biedt 3.4.2 

Deze ABIs veranderen/worden nieuw gemaakt als er nieuwe features worden
toegevoegd die niet 100% compatible zijn. GCC 11 heeft extra C++17 en
C++20 features, met bijbehordende nieuwe ABIs. Dit is toegevoegd in de
volgende commit:

https://github.com/gcc-mirror/gcc/commit/932fbc868ad429167a3d4d5625aa9d6dc0b4506b

Debian Bullseye heeft GCC 10, en heeft daarom die nieuwere ABI nog
niet.

De "sysreq" pagina van Pixinsight lijkt me dan ook niet helemaal te
kloppen want die zeggen:

>  PixInsight 1.8.8-8 for Linux requires a 64-bit Linux distribution
> with glibc version 2.27 (January 2018) or later and GLIBCXX_3.4.29 /
> CXXABI_1.3.12 (GCC 9.3.0 or later). 

CXXABI_1.3.12 is inderdaad toegevoegd in GCC 9:
https://github.com/gcc-mirror/gcc/commit/c124af936b6b225eb548ccdd7f01400511d784dc

Maar GLIBCXX_3.4.29 zit pas in GCC 11.

-Martijn

Re: icewm anomaly after bullseye upgrade

2021-09-03 Thread Michael Lange

Hi,

On Thu, 2 Sep 2021 16:02:08 -0400 (EDT)
Bob Bernstein  wrote:

> Thanks to those who chimed in!
> 
> My focus today is on those lines in ~/.icewm/preferences that 
> specify fonts for the task bar. I have in mind such statements 
> as:
> 
> NormalTaskBarFontNameXft="DejaVuSans-Bold,sans-serif:size=18"
> ActiveTaskBarFontNameXft="DejaVuSans-Bold,sans-serif:size=18"
> 
> I suspect the syntax of my lines does not represent actual fonts 
> that are available on this machine.
> 
> Can anyone provide a critique of that syntax?

according to https://ice-wm.org/man/icewm-preferences the syntax for
using a bold font should rather be:

ActiveTaskBarFontNameXft=”sans-serif:size=12:bold” .

That comma-separated font list thing does not seem to work (at least not
with the IceWM version from Buster); since I suspect that "DejaVuSans"
and "sans-serif" might be equivalent here, I tried with a different font
here:

NormalTaskBarFontNameXft="Akkadian,sans-serif:size=11:bold"

This gives me the Akkadian font with normal (or medium) weight.
Changing the first font name to one that does not exist, like

NormalTaskBarFontNameXft="Akadian,sans-serif:size=11:bold"

gives me a normal weight default/fallback font. Likewise

NormalTaskBarFontNameXft="Akkadian:size=11:bold,sans-serif:size=11:bold"
resp.
NormalTaskBarFontNameXft="Akadian:size=11:bold,sans-serif:size=11:bold"

gives me a bold Akkadian font resp. that same normal weight default
fallback font as above.

I have some doubt though, that this has anything to do with your original
problem.

Best regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

It is necessary to have purpose.
-- Alice #1, "I, Mudd", stardate 4513.3

Install Debian netinstall to HP Elitebook 840 G8 problem