Re: Pilote carte vidéo Nvidia 340 210 obsolète.

[Basile Starynkevitch]

On 28/02/2023 07:32, Basile Starynkevitch wrote:


On 27/02/2023 19:50, ajh-valmer wrote:

Bonsoir à tous,

Depuis la version Bullseye, le pilote de ma carte vidéo Nvidia 340 
modèle 210

ne peut plus fonctionner, il est abandonné.
J'avais donc choisi le pilote (nvidia) "nouveau" qui donnait 
satisfaction.


Ce matin, j'ai upgradé le système, mon noyau est devenu 5.10.0-21,
du coup le pilote "nouveau" ne fonctionne plus.
Hélas, j'ai oublié la manip pour recréer le pilote, malgré vaines 
recherches,

je n'ai rien trouvé de fonctionnel



Que donnent les commandes (sous root)

/usr/bin/aptitude install xserver-xorg-video-nouveau nouveau-firmware 
libdrm-nouveau2


/usr/bin/startx

/usr/bin/dmesg

/usr/bin/lspci

/usr/bin/lscpu



Et j'ai oublié le plus important: quel est le fichier 
/var/log/Xorg.0.log après lancement de /usr/bin/startx ou de /usr/bin/Xorg


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

Re: Pilote carte vidéo Nvidia 340 210 obsolète.

[Basile Starynkevitch]

On 27/02/2023 19:50, ajh-valmer wrote:

Bonsoir à tous,

Depuis la version Bullseye, le pilote de ma carte vidéo Nvidia 340 modèle 210
ne peut plus fonctionner, il est abandonné.
J'avais donc choisi le pilote (nvidia) "nouveau" qui donnait satisfaction.

Ce matin, j'ai upgradé le système, mon noyau est devenu 5.10.0-21,
du coup le pilote "nouveau" ne fonctionne plus.
Hélas, j'ai oublié la manip pour recréer le pilote, malgré vaines recherches,
je n'ai rien trouvé de fonctionnel



Que donnent les commandes (sous root)

/usr/bin/aptitude install xserver-xorg-video-nouveau nouveau-firmware 
libdrm-nouveau2


/usr/bin/startx

/usr/bin/dmesg

/usr/bin/lspci

/usr/bin/lscpu

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

Re: Remove route '169.254.0.0/16 dev ovs-system'

[Reco]

Hi.

On Mon, Feb 27, 2023 at 10:53:24PM +0100, Geert Stappers wrote:
> (Meanwhile solved with denyinterface in /etc/dhcpcd.conf)
> 
>  
> > Long story short, consider running "systemctl mask dhcpcd" unless you
> > need dhcpcd to work in a way described above.
> 
> The laptop does need to have DHCP client.

I see. Adding appropriate amount of "allowinterfaces" and
"denyinterfaces" stanzas into dhcpcd.conf should solve it for you.


> > Another possible workaround is to add "noipv4ll" to dhcpcd.conf,
> 
> Not tried.

It disallows dhcpcd to add IPv4LL address on any network interface.

Reco

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[David Wright]

On Thu 23 Feb 2023 at 11:23:30 (+0100), daven...@tuxfamily.org wrote:
> On 2023-02-23 02:59, cono...@panix.com wrote:
> > On 2/22/23, daven...@tuxfamily.org  wrote:
> > > 
> > > There is an unidentified process that decides it's ok to delete and
> > > recreate /etc/resolv.conf without asking user/admin,
> > > The problem is, the problematic process is not work's VPN related and
> > > creates the file with wrong resolver's IP. The IP corresponds
> > > to my home
> > > router IP, which does has a DNS resolver and it works as it
> > > should. BUT
> > > my home's router DNS obviously don't know jack about work internal
> > > servers, on which I work… and work's proxy as well, which
> > > when it cannot
> > > be resolved… breaks everything using HTTP.
> > 
> > Might look at:
> > 
> > /etc/network/interfaces.d/setup
> > 
> > as explained in "man interfaces". (That file can/might be changed via
> > the network symbol in the window manager's configuration bar/menu
> > system, usually required with root/sudo privileges.)
> 
> There's nothing relevant to change in that file. I don't want to have
> static IP. And the right interface name is not in it.
> 
> I'm not sure whether that file became totally obsoleled, or if it's
> not normal that it doesn't contain the expected interface name? has it
> been deprecated since debian switched to systemd so-called
> "predictable" iface names?
> 
> For some reasons, since debian 9 or 10 (id nor 8?), including debian
> 11 new installs (work laptop has been install slightly more than a
> year ago),
> that files only contains the eth0 and local interfaces name, while
> debian switched to systemd style interfaces names.
> I remembrer having slowed down boots because of the that, on my
> personal laptop, when debian switched to systemd style names and that
> file still referred to eth0 which doesn't exist
> So boot process was waiting for eth0 interface until I commented out
> that part (eth0 block) of interfaces files.
> 
> On the newer work laptop on the other hand, there is that eth0 block,
> there's is no eth0 interface on my system (there's enp.* and enx.*
> systemd names, instead)
> BUT I never had the slow/timeout-waiting boot process unlike the
> personal was reinstall from zero instead of upgraded years ago only to
> change HDD to SSD, and to change partitioning to encrypted LVM.

What are these enp… (waste of time hiding that name) and enx…
interfaces (and any others), and what are they used for.

> So my guess is /etc/network/interface.* has been replaced with
> something also. Since it refers to non-exitent interfaces names
> without breaking the network or slowing down the boot process.
> 
> Also, the switching to systemd styles interfaces names has been
> following by a weird behaviour on my personal computer. It has a
> "failed" error message at startup, for the network (or is networking?
> it never remember the correct name) service, without breaking the
> network… it weirdly just works. I never figured out what replaces that
> service. If anyone has any idea?

Different installation scripts and/or individual sysadmins can place
files with a variety of names in /etc/network/interface.d/. So their
removal can be rather sporadic: Debian won't know their names, and
deinstallation scripts might leave them, if they get run at all.

It's worrying that such files are there if they have the wrong
interface names in them. It might suggest ancient cruft or, just
as easily, network installation scripts that are broken, or designed
for a different system/distribution.

What's the output from   ls -lR /etc/network* /etc/systemd/network*

Cheers,
David.

Re: Debian bug report etiquette

[John Crawley]

On 27/02/2023 19:58, Jonathan Dowland wrote:

I see the maintainer has
uploaded a new version with a fix for your issue (--execute), but
they have pointed out that the original bug was complaining about
something different (-c): I hadn't noticed the difference, and it
seems only the former is a policy violation in their eyes. I hope
the action properly addresses *your* issue.

Indeed it does.

I guess the issue of how to handle the arguments following -e is a bit tricky, 
and this *ought not to work*:
x-terminal-emulator -e 'if true; then { echo "true"; bash;}; fi'
although it does with some terminals.
'if true; then { echo "true"; bash;}; fi' doesn't work in an actual terminal 
interface though, because the whole quoted string is treated as a single command, and 
rejected.

This works:
x-terminal-emulator -e sh -c 'if true; then { echo "true"; bash;}; fi'

Anyway the issue is fixed. :)

--
John

Re: Debian bug report etiquette

[John Crawley]

On 28/02/2023 09:00, John Crawley wrote:

On 27/02/2023 19:58, Jonathan Dowland wrote:

I see the maintainer has
uploaded a new version with a fix for your issue (--execute), but
they have pointed out that the original bug was complaining about
something different (-c): I hadn't noticed the difference, and it
seems only the former is a policy violation in their eyes. I hope
the action properly addresses *your* issue.

I'll have to have another careful look at this. I was pretty sure that -e 
handling was broken, as described in Debian Policy - the part about accepting 
all following arguments as belonging to the invoked executable.

There is no mention of the -c option in Debian Policy for x-terminal-emulator.



PS I forgot to mention, Debian Policy does not refer to an --execute option 
either, only -e.

--
John

Re: Debian bug report etiquette

[John Crawley]

On 27/02/2023 19:58, Jonathan Dowland wrote:

I see the maintainer has
uploaded a new version with a fix for your issue (--execute), but
they have pointed out that the original bug was complaining about
something different (-c): I hadn't noticed the difference, and it
seems only the former is a policy violation in their eyes. I hope
the action properly addresses *your* issue.

I'll have to have another careful look at this. I was pretty sure that -e 
handling was broken, as described in Debian Policy - the part about accepting 
all following arguments as belonging to the invoked executable.

There is no mention of the -c option in Debian Policy for x-terminal-emulator.

--
John

Re: No keyboard on ttyS0

[David Wright]

On Mon 27 Feb 2023 at 14:06:08 (+0100), basti wrote:
> 
> we have a PC Engines APU. This PC has only a Serial-Console.
> 
> After the upgrade from buster to bullseye I see the kernel output on
> ttyS0 but there is no keyboard input available, neither in Grub.
> 
> Getty is startet on ttyS0, I see a login prompt.
> 
> Did anyone has had a similar problem?

Yourself, perhaps. Is this the machine that required
usbserial_pl2303.mod in Grub's core image? How did
you upgrade? Did you preserve /etc/default/grub or
has it been overwritten?

Cheers,
David.

Re: No keyboard on ttyS0

[Juri Grabowski]

Hello,

please check RX-Line on RS-232.

Best Regards,
Juri Grabowski

Re: Us animeu a traduir debian-history al català?

[Antoni Villalonga]

Hola,

Ara he fet una petita part.
La deixo aquí per si algú s'anima a revisar o continuar la tasca.

  https://salsa.debian.org/friki/debian-history/-/blob/wip-ca/po4a/po/ca.po

Gràcies!

On Mon, Feb 27, 2023 at 03:58:07PM +0100, Alex Muntada wrote:
> Hola debianites, fa poc he descobert que hi ha un paquet anomenat
> debian-history que conté un recull de la història del projecte:
> 
> https://tracker.debian.org/pkg/debian-history
> 
> Crec que estaria bé tenir-lo en català i pot ser una bonica
> contribució per qui vulgui engrescar-s'hi.
> 
> Salut,
> Alex
> 
> --
>   ⢀⣴⠾⠻⢶⣦⠀
>   ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
>   ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
>   ⠈⠳⣄
> 



-- 
Antoni Villalonga
https://friki.cat/

Re: Remove route '169.254.0.0/16 dev ovs-system'

[Geert Stappers]

Hi.

On Sun, Feb 26, 2023 at 05:25:09PM +0300, Reco wrote:
> On Sun, Feb 26, 2023 at 03:14:22PM +0100, Geert Stappers wrote:
> > On Sun, Feb 26, 2023 at 04:01:06PM +0300, Reco wrote:
> > > On Sun, Feb 26, 2023 at 12:18:52PM +0100, Geert Stappers wrote:
} } } } }  Have you tried `journalctl --boot`?
> > > > Feb 24 22:24:21 trancilo dhcpcd[1175]: ovs-system: probing for an 
> > > > IPv4LL address
> > > > Feb 24 22:24:26 trancilo dhcpcd[1175]: ovs-system: using IPv4LL address 
> > > > 169.254.201.7
> > > > Feb 24 22:24:26 trancilo dhcpcd[1175]: ovs-system: adding route to 
> > > > 169.254.0.0/16
> > > 
> > > Let's try a straightforward approach for starters:
> > > 
> > >   echo denyinterfaces ovs-system >> /etc/dhcpcd.conf
> > 
> > 
> > Yes, now no more route 169.254.0.0/16 for device ovs-system.
> > 
> > And for the record:
> > * Package avahi-autoipd left removed
> > * Service avahi-daemon left disabled
> > * Socket avahi-daemon left disabled

As done / adviced earlier in this thread.


> These have nothing to do with your problem.
> dhcpcd is the source of your problem, in a way.

OK, so I checked.  And yes, it is true that adding
'denyinterfaces ovs-system ovsbr0' to /etc/dhcpcd.conf
does prevent "route 169.254.0.0/16 dev ovs-system"
and "route 169.254.0.0/16 dev ovsbr0"
 
> dhcpcd can run as a systemwide daemon, which tries to obtain DHCP lease
> on any network interface barring "lo".
> In stock configuration, dhcpcd will add IPv4LL (169.254/16) IP on a
> interface if it fails to obtain a lease after 60 second timeout (IIRC).
> And obviously you have no DHCP server on "ovs-system" :)
> Debian's packaging of dhcpcd should prevent the daemon to obtain DHCP
> lease on any interface that's listed in /etc/network/interfaces, but:
> 
> 1) OVS bridge should not be listed there, it's dynamic by nature.
> 2) You're using Network Manager, so it's totally possible that you have
> an empty /etc/network/interfaces, or no such file at all.
> 

I have no /etc/network/interfaces.d/ovs-system,
my /etc/network/interfaces.d/ovsbr0 has
  auto ovsbr0
  iface ovsbr0 inet static
 address 172.24.6.2/24

And there was "route 169.254.0.0/16 dev ovsbr0".

I only reported, until now, only about dev ovs-system.


Thing I trying to say:
  Having device in /etc/network/interfaces did
  not prevent the unwanted route.

(Meanwhile solved with denyinterface in /etc/dhcpcd.conf)

 
> Long story short, consider running "systemctl mask dhcpcd" unless you
> need dhcpcd to work in a way described above.

The laptop does need to have DHCP client.
 
 
> Another possible workaround is to add "noipv4ll" to dhcpcd.conf,

Not tried.


> but this could break something else in your setup.

Yes "could break",  but I don't know what ...
(I'm mostly on computer networks that do have
DHCP and DNServers (I can't tell first hand
the benefits of IPv4LL addresses))

 
> Reco

Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: where are the actual ".deb" packages? all I see are "pkgcache.bin" and "srcpkgcache.bin" . . .

[Tim Woodall]

On Sun, 26 Feb 2023, Greg Wooledge wrote:


On Sun, Feb 26, 2023 at 05:28:44PM +, Albretch Mueller wrote:

 Basically, I am trying to download all packages that are part of the
installation dependencies of a given one into a directory of my
choosing to then install packages on an unexposed machine.


The tricky part here is that the packages on machine A are not necessarily
the same as on machine B.  So, installing package P1 on machine A may
need dependencies P2, P3 and P4.  But on machine B, it may need dependencies
P3, P4 and P5 instead.

If you ignore that, then the obvious answer is:

A# apt-get --download-only --reinstall install P1
A# cd /var/cache/apt/archives
A# scp *.deb B:/var/cache/apt/archives/
A# ssh root@B

B# cd /var/cache/apt/archives
B# apt-get install ./P1.deb

That should utilize the cached dependent packages P2, P3, P4 which are
located in /v/c/a/a on machine B.

If additional dependencies are needed, you'll have to fetch those by
hand.




If you want to download all the dependencies (except essential packages)
then you can point to an empty dir.

I do something like:

  rm -f ${APT_WORK}/archives/*.deb
  APT_CONFIG=${APT_CONFIG} \
  DEBIAN_FRONTEND=noninteractive \
apt-get -q -y install -d \
-o APT::Install-Recommends=false \
  $@

where APT_CONFIG looks something like:
  cat <${APT_CONFIG}
APT::Architecture "${ARCH}";
APT::Install-Recommends "false";

Dir::Etc::PreferencesParts "${APT_WORK}/preferences.d";
Dir::Etc::SourceParts "${APT_WORK}/sources.list.d";
Dir::Etc::TrustedParts "${aptdir}/trusted.d";
Dir::Etc::Parts "${aptdir}/conf.d";

Dir::State::Lists "${APT_WORK}/lists";
Dir::State::Status "${APT_WORK}/status";
Dir::Cache::Archives "${APT_WORK}/archives";
Dir::Cache::srcpkgcache "${APT_WORK}/srcpkgcache";
Dir::Cache::pkgcache "${APT_WORK}/pkgcache";
EOF

Pilote carte vidéo Nvidia 340 210 obsolète.

[ajh-valmer]

Bonsoir à tous,

Depuis la version Bullseye, le pilote de ma carte vidéo Nvidia 340 modèle 210
ne peut plus fonctionner, il est abandonné.
J'avais donc choisi le pilote (nvidia) "nouveau" qui donnait satisfaction.

Ce matin, j'ai upgradé le système, mon noyau est devenu 5.10.0-21,
du coup le pilote "nouveau" ne fonctionne plus.
Hélas, j'ai oublié la manip pour recréer le pilote, malgré vaines recherches,
je n'ai rien trouvé de fonctionnel.
Merci d'avance de m'indiquer le mode opératoire.

Bonne soirée,
A. Valmer

Re: [1/2 HS] Part du marché professionnel GNU/Linux

[Jérémy Prego]

Le 26/02/2023 à 19:36, Basile Starynkevitch a écrit :





(Voyez aussi le logiciel libre http://refpersys.org/ et contactez moi 
par courriel si intéressés, même au bureau -CEA LIST 
- en basile.starynkevi...@cea.fr )




On peut se dire que depuis le temps, personne n'est intéressé ? je pense 
qu'il serait  bien de stopper cette pub / ce spam à chaque message ...


Jerem



Cordialement

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

Re: Generar ruido inaudible

[Roberto C . Sánchez]

On Mon, Feb 27, 2023 at 10:06:09AM -0600, Paynalton wrote:
>Hola a todos.
>Alguien sabe como puedo poner un sonido inaudible para el ser humano a
>reproducir de forma infinita??
>Tengo un problema con una bocina bluethoot que se apaga por una funcion de
>ahorro de energia que no se puede desactivar y al retornar corta parte del
>audio, lo que hace que las llamadas se escuchen entrecortadas.
>Quiero colocar un sonido a reproducir de forma permanente en el fondo para
>que no se active el modo de ahorro y pueda tener conversaciones
>mas claras.

¿Cuál applicación usas para configurar/manejar la bocina?  ¿Te permite
cambiar los parámetros de energía?

¿Has mirado a ver si el vendedor ofrece un firmware actualizado que
posiblemente arregla este defecto?

Saludos,

-Roberto

-- 
Roberto C. Sánchez

Re: Generar ruido inaudible

[estebanmonge]

Compra otra bocina...Get Outlook for AndroidFrom: Camaleón Sent: Monday, February 27, 2023, 10:12 AMTo: debian-user-spanish@lists.debian.org Subject: Re: Generar ruido inaudibleEl 2023-02-27 a las 10:06 -0600, Paynalton escribió:

> Hola a todos.
> 
> Alguien sabe como puedo poner un sonido inaudible para el ser humano a
> reproducir de forma infinita??

Si ffmpeg no puede, nada puede.
Bueno, quizá sox :-)

> Tengo un problema con una bocina bluethoot que se apaga por una funcion de
> ahorro de energia que no se puede desactivar y al retornar corta parte del
> audio, lo que hace que las llamadas se escuchen entrecortadas.
> 
> Quiero colocar un sonido a reproducir de forma permanente en el fondo para
> que no se active el modo de ahorro y pueda tener conversaciones mas claras.

Curiosa causística, pero eso de «reproducir contínuamente algo» no me 
termina de convencer.

Saludos,

-- 
Camaleón 

Re: Generar ruido inaudible

[Camaleón]

El 2023-02-27 a las 10:06 -0600, Paynalton escribió:

> Hola a todos.
> 
> Alguien sabe como puedo poner un sonido inaudible para el ser humano a
> reproducir de forma infinita??

Si ffmpeg no puede, nada puede.
Bueno, quizá sox :-)

> Tengo un problema con una bocina bluethoot que se apaga por una funcion de
> ahorro de energia que no se puede desactivar y al retornar corta parte del
> audio, lo que hace que las llamadas se escuchen entrecortadas.
> 
> Quiero colocar un sonido a reproducir de forma permanente en el fondo para
> que no se active el modo de ahorro y pueda tener conversaciones mas claras.

Curiosa causística, pero eso de «reproducir contínuamente algo» no me 
termina de convencer.

Saludos,

-- 
Camaleón 

Generar ruido inaudible

[Paynalton]

Hola a todos.

Alguien sabe como puedo poner un sonido inaudible para el ser humano a
reproducir de forma infinita??

Tengo un problema con una bocina bluethoot que se apaga por una funcion de
ahorro de energia que no se puede desactivar y al retornar corta parte del
audio, lo que hace que las llamadas se escuchen entrecortadas.

Quiero colocar un sonido a reproducir de forma permanente en el fondo para
que no se active el modo de ahorro y pueda tener conversaciones mas claras.

Us animeu a traduir debian-history al català?

[Alex Muntada]

Hola debianites, fa poc he descobert que hi ha un paquet anomenat
debian-history que conté un recull de la història del projecte:

https://tracker.debian.org/pkg/debian-history

Crec que estaria bé tenir-lo en català i pot ser una bonica
contribució per qui vulgui engrescar-s'hi.

Salut,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[Greg Wooledge]

On Mon, Feb 27, 2023 at 03:14:40PM +0100, daven...@tuxfamily.org wrote:
> I did
> 
> - chattr +i /etc/revolv.conf
> 
> And when auditd showed a (failed) delete event on /etc/resolv.conf
> 
> I grepped "resolv.conf" recursively on /var/log/, and All I've found are
> entries in
> 
> - /var/log/installer from more than 1 year ago, since the log file is small,
> I guess it has never been rotated
> - audit.log, since write and append  to "/etc/resolv.conf" are audited
> - auth.log : authentication related to commands I've used this morning,
> which are "auditctl -w /etc/resolv.conf -p wa" and "chattr +i
> /etc/revolv.conf"
> 
> But whatever process tried to delete "/etc/resolv.conf" whidle it was
> immutable, didn't leave traces.
> Not even a log for permission error because of the immutable flag. At least
> not in /var/log anyway.

I can't say I'm shocked.  But you *did* find an entry from auditd, which
presumably has a timestamp.  Check to see what was happening right at
that moment in other log files.

In particular, check whether a DHCP client daemon renewed its DHCP lease
at that time.

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[davenull]

Hello

On 2023-02-24 11:27, daven...@tuxfamily.org wrote:

On 2023-02-24 10:27, to...@tuxteam.de wrote:
On Fri, Feb 24, 2023 at 10:19:38AM +0100, daven...@tuxfamily.org 
wrote:


[...]

BUT I will make sure to take some time to dig into the logs monday.
Now that I have an idea what I'm looking for, totally agree logs are
better than suspicion


I did

- chattr +i /etc/revolv.conf

And when auditd showed a (failed) delete event on /etc/resolv.conf

I grepped "resolv.conf" recursively on /var/log/, and All I've found are 
entries in


- /var/log/installer from more than 1 year ago, since the log file is 
small, I guess it has never been rotated

- audit.log, since write and append  to "/etc/resolv.conf" are audited
- auth.log : authentication related to commands I've used this morning, 
which are "auditctl -w /etc/resolv.conf -p wa" and "chattr +i 
/etc/revolv.conf"


But whatever process tried to delete "/etc/resolv.conf" whidle it was 
immutable, didn't leave traces.
Not even a log for permission error because of the immutable flag. At 
least not in /var/log anyway.

No keyboard on ttyS0

[basti]

Hello,

we have a PC Engines APU. This PC has only a Serial-Console.

After the upgrade from buster to bullseye I see the kernel output on 
ttyS0 but there is no keyboard input available, neither in Grub.


Getty is startet on ttyS0, I see a login prompt.

Did anyone has had a similar problem?

Best regards,

Re: dmesg ... XFS (sdb1): log I/O error ...

[tomas]

On Mon, Feb 27, 2023 at 09:23:06AM -0300, Eduardo M KALINOWSKI wrote:

[...]

> Maybe putting a tiny tinfoil hat on the power cable?

tiny tinfoil ♥

Cheers
- 
t


signature.asc
Description: PGP signature

Re: MPV Player...

[David]

On Mon, 27 Feb 2023 at 23:14, Greg Wooledge  wrote:

> unicorn:~$ apt-cache show yt-dlp
> N: Unable to locate package yt-dlp
> E: No packages found
> unicorn:~$ cat /etc/debian_version
> 11.6

$ aptitude --disable-columns -F '%p %O' search yt-dl
yt-dlp Debian Backports:bullseye-backports [all]
$ cat /etc/debian_version
11.6

It's also in Bookworm:
  
https://packages.debian.org/search?keywords=yt-dlp=names=testing=all

I wouldn't install it anyway, because this kind of tool has
frequent updates. I just 'git pull', 'make', and run, that works
for me on Bullseye.

Re: MPV Player...

[Reco]

On Mon, Feb 27, 2023 at 07:14:25AM -0500, Greg Wooledge wrote:
> On Mon, Feb 27, 2023 at 12:05:27PM +0300, Reco wrote:
> > Hi.
> > 
> > On Mon, Feb 27, 2023 at 12:40:39AM -0600, Lester Rees wrote:
> > > I would like for MPV Player to be updated/upgraded because the newest
> > > version uses yt-dlp instead of youtube-dl(more or less abandoned).
> > 
> > apt install yt-dlp youtube-dl-
> > ln -sf /usr/bin/yt-dlp /usr/local/bin/youtube-dl
> > 
> > 
> 
> unicorn:~$ apt-cache show yt-dlp
> N: Unable to locate package yt-dlp
> E: No packages found
> unicorn:~$ cat /etc/debian_version 
> 11.6

A valid point.

$ apt policy yt-dlp
yt-dlp:
  Installed: 2023.01.06-1~bpo11+1
  Candidate: 2023.01.06-1~bpo11+1
  Version table:
 *** 2023.01.06-1~bpo11+1 100
100 http://ftp.debian.org/debian bullseye-backports/main amd64 Packages

Reco

Re: dmesg ... XFS (sdb1): log I/O error ...

[Eduardo M KALINOWSKI]

On 26/02/2023 18:56, Albretch Mueller wrote:

  I started using another power cable and so far so good, but I would
not be too happy too soon. It may sound more than half way off to you,
but it is physically possible and it has been actually demonstrated
that "they" have been hacking into computers through the power supply
lines . . .
  What physical means do we have to avoid that? Would some sort of
"denoising"/"gray noIsing" power surge protector help?


Maybe putting a tiny tinfoil hat on the power cable?

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

Re: MPV Player...

[Greg Wooledge]

On Mon, Feb 27, 2023 at 12:05:27PM +0300, Reco wrote:
>   Hi.
> 
> On Mon, Feb 27, 2023 at 12:40:39AM -0600, Lester Rees wrote:
> > I would like for MPV Player to be updated/upgraded because the newest
> > version uses yt-dlp instead of youtube-dl(more or less abandoned).
> 
> apt install yt-dlp youtube-dl-
> ln -sf /usr/bin/yt-dlp /usr/local/bin/youtube-dl
> 
> 

unicorn:~$ apt-cache show yt-dlp
N: Unable to locate package yt-dlp
E: No packages found
unicorn:~$ cat /etc/debian_version 
11.6

Re: Debian bug report etiquette

[Jonathan Dowland]

On Sat, Feb 25, 2023 at 03:40:19PM +0900, John Crawley wrote:

I've done this. [1]


Great!


I've sent a mail to cont...@bugs.debian.org to bump the severity to
serious.


Good. That seems to have done the trick: I see the maintainer has
uploaded a new version with a fix for your issue (--execute), but
they have pointed out that the original bug was complaining about
something different (-c): I hadn't noticed the difference, and it
seems only the former is a policy violation in their eyes. I hope
the action properly addresses *your* issue.

(They didn't merge your MR as part of the upload, it seems. You
can probably close it if you are satisfied the issue is done.)


I help to manage a small Debian derivative. [2] Our default terminal
emulator used to be Terminator, and some of our users still like it.
The recent issue has broken one of our utilities, if run with
x-terminal-emulator set to terminator.


I see, thank you for explaining!


Thanks again!


You're welcome,

--
Please do not CC me for listmail.

  Jonathan Dowland
✎j...@debian.org
   https://jmtd.net

Re: MPV Player...

[Reco]

Hi.

On Mon, Feb 27, 2023 at 12:40:39AM -0600, Lester Rees wrote:
> I would like for MPV Player to be updated/upgraded because the newest
> version uses yt-dlp instead of youtube-dl(more or less abandoned).

apt install yt-dlp youtube-dl-
ln -sf /usr/bin/yt-dlp /usr/local/bin/youtube-dl



Reco

Re: MPV Player...

[Luna Jernberg]

oh alright, well its in regular Debian testing too:
https://packages.debian.org/bookworm/mpv

On 2/27/23, Tixy  wrote:
> On Mon, 2023-02-27 at 08:04 +0100, Luna Jernberg wrote:
>> There is newer mpv in the http://deb-multimedia.org/ testing repos (if
>> you feel like running testing)
>
> Two reason's not to recommend that: deb-multimedia isn't run by the
> Debian project and mixing in stuff from another release it fraught with
> problems. As is oft pointed out here, see...
> https://wiki.debian.org/DontBreakDebian
>
> --
> Tixy
>
>

Re: MPV Player...

[Tixy]

On Mon, 2023-02-27 at 08:04 +0100, Luna Jernberg wrote:
> There is newer mpv in the http://deb-multimedia.org/ testing repos (if
> you feel like running testing)

Two reason's not to recommend that: deb-multimedia isn't run by the
Debian project and mixing in stuff from another release it fraught with
problems. As is oft pointed out here, see...
https://wiki.debian.org/DontBreakDebian

-- 
Tixy