Re: copy directory tree, mapping to new owners

[Richard Hector]

On 12/09/21 7:46 pm, Teemu Likonen wrote:

* 2021-09-12 12:43:29+1200, Richard Hector wrote:


The context of my question is that I'm creating (or updating) a test
copy of a website. The files are owned by one of two owners, depending
on whether they were written by the server (actually php-fpm).

To do that, I want all the permissions to remain the same, but the
ownership should be changed according to a provided map.


Looks exactly like what "rsync --usermap=FROM:TO" can do. There is also
"--groupmap" option for mapping groups.


Aha - thanks a lot :-) I guess I've been caught not reading the man page 
thoroughly enough. The pitfalls of thinking that you know everything 
that a tool does, just because you use it often ...


The way the docs are written seems to imply a sender and receiver; I'll 
have to check it works for a local copy ... it does.


Now I need to rewrite my script somewhat, since to do this it's going to 
have to run as root ...


Thanks,
Richard

Re: copy directory tree, mapping to new owners

[Richard Hector]

On 12/09/21 6:53 pm, l0f...@tuta.io wrote:


# actually not necessary? rsync will create it
mkdir -p mysite_test/doc_root


You can make a simple test to know that but I would say that rsync doesn't create your 
destination "root" directory (the one you specify on the command line) unless 
`--mkpath` is used.


I was fairly confident of that, from my regular usage.


# The trailing / matters. Does it matter on the source as well?
# I generally include it.
rsync -a mysite/doc_root/ mysite_test/doc_root/  # The trailing / matters.


Actually, I'm not sure to understand Greg's remark here.

In my opinion, trailing slash doesn't matter for destination folder on the 
contrary of *source* folder.

In other words, for me, the following are equal:
rsync -a mysite/doc_root/ mysite_test/doc_root/
rsync -a mysite/doc_root/ mysite_test/doc_root

But not the following:
rsync -a mysite/doc_root mysite_test/doc_root => you will get an extra 
"doc_root" folder (the source one) in your dest, i.e. : 
mysite_test/doc_root/doc_root and then the content of doc_root source
rsync -a mysite/doc_root/ mysite_test/doc_root => your doc_root (destination) 
folder will get doc_root content (source) directly


Yep. As I've mentioned elsewhere, I habitually include trailing slashes 
for both source and destination when I'm replicating a whole tree. I 
couldn't remember the details of what happens when you don't, but I know 
what happens when I do :-)


Cheers,
Richard

Re: copy directory tree, mapping to new owners

[Richard Hector]

On 12/09/21 6:52 pm, john doe wrote:

On 9/12/2021 3:45 AM, Richard Hector wrote:




Thanks, that looks reasonable. It does mean, though, that the files
exist for a while with the wrong ownership. That probably doesn't
matter, but somehow 'feels wrong' to me.



If you are doing this in a script, I would use a temporary directory.
That way, in case of failure the destination directory is not rongly
modified.

EG:

$ rsync  

Make  the way you want it to be.

$ rsync  


That is true, but firstly it would require more available space, and 
secondly, as long as I know about the failure, it doesn't worry me too 
much. This is a script I will call manually.



Given that you want to change the ownership, you may want to emulate the
options implied by '-a' but without the ownership option ('-o').


I do that in my existing script (also not -g (group) or -D 
(specials/devices (which don't exist there anyway)) - and sometimes -p 
(permissions), if I've pre-created the tree with the permissions I want. 
The last one is a slightly different use case, but I should make sure I 
know which use case I'm trying for ...



My habits would also lead me to do all of the above from above the two
directories in question (in my case, /srv - for /srv/mysite/doc_root and
/srv/mysite_test/doc_root) So:

cd /srv

# actually not necessary? rsync will create it
mkdir -p mysite_test/doc_root

# The trailing / matters. Does it matter on the source as well?


According to the man page it does (1):

"CWrsync -avz foo:src/bar/ /data/tmp
A trailing slash on the source changes this behavior to avoid creating
an additional directory level at the destination. You can think of a
trailing / on a source as meaning lqcopy the contents"


# I generally include it.


In a script, you need to be sure what the cmd does do or not do!!! :)


True. But many options I've learned from my everyday usage, and 
sometimes forgotten the rationale - I just know it does what I want :-)




rsync -a mysite/doc_root/ mysite_test/doc_root/  # The trailing /
matters.

find mysite_dest -user mysite -exec chown mysite_test {} +

# I prefer mysite_test-run; it keeps consistency with
# the ${sitename}-run pattern used elsewhere
find mysite_dest -user mysite-run -exec chown mysite_test-run {} +

Have I broken anything there?



Not that I can see but testing will tell!


This is what I would do.  And I would do it *interactively*.

If you insist on making a script, then it will be slightly more
complicated, because you'll need to add error checking.


The trouble with doing it interactively, when it needs to be done many
times (and on several sites), is that each time there's opportunity to
make a mistake. And it means the process needs to be documented
separately from the script.

In fact, I'd incorporate the above in a larger script, which does things
like copying the database (and changing the db name in the site config).

Error checking in shell scripts is something I certainly need to learn


At the very least, ' ['&&'|'||'] handle the error>.

If you use Bash and don't need to be POSIX compliant and /or portable
you can be a bit more creative.


Heh - you've cut my sentence in two, which appears to change the meaning 
slightly :-)


" ... is something I need to learn and practice more".

You make it look like I need to learn error checking from scratch :-)

I am using bash. And I am currently using 'set -e' to handle that kind 
of error globally. As I say, as long as I can see that it broke, it 
doesn't matter too much.



and practice more - I tend to rely somewhat on 'knowing' what I'm
working with, which is probably not a good idea.

 >

Yes in a script it is like shooting yourself in the foot.


I do test it.

Cheers,
Richard

Re: debian-installer RAID question

[Darac Marjal]

On 11/09/2021 17:55, Felix Natter wrote:
> hello fellow Debian users,
>
> I have an SSD for the root filesystem, and two HDDs using RAID1 for
> /storage running Debian10. Now I need a plan B in case the upgrade
> fails.

Just want to check that you've not missed something obvious here. You
don't *need* to involve Debian-Installer in an upgrade. Debian fully
supports in-place upgrades. The process is documented here:
https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html


>
> So I made an experiment with a VM and rougly the same setup (disk-wise),
> and found out that when reinstalling Debian11, the d-i does recognize
> the RAID1 (/storage) and can reuse it while keeping the data.
>
> My question is: How does d-i know how the individual HDDs were combined
> into a RAID1? For all that "sudo fdisk -l" shows, the disks are
> "Linux raid autodetect". For all I see, it could be a RAIDX, X!=1 or
> two different RAIDs  Are there RAID headers on the partitions?
>
> The same thing applies when I boot a GNU/Linux rescue system: I think I
> can mount the RAID1 if I know the member partitions and type of RAID
> using mdadm?
>
> Many Thanks and Best Regards,



OpenPGP_signature
Description: OpenPGP digital signature

Re: debian-installer RAID question

[David Christensen]

On 9/11/21 9:55 AM, Felix Natter wrote:

hello fellow Debian users,

I have an SSD for the root filesystem, and two HDDs using RAID1 for
/storage running Debian10. Now I need a plan B in case the upgrade
fails.

So I made an experiment with a VM and rougly the same setup (disk-wise),
and found out that when reinstalling Debian11, the d-i does recognize
the RAID1 (/storage) and can reuse it while keeping the data.

My question is: How does d-i know how the individual HDDs were combined
into a RAID1? For all that "sudo fdisk -l" shows, the disks are
"Linux raid autodetect". For all I see, it could be a RAIDX, X!=1 or
two different RAIDs  Are there RAID headers on the partitions?

The same thing applies when I boot a GNU/Linux rescue system: I think I
can mount the RAID1 if I know the member partitions and type of RAID
using mdadm?

Many Thanks and Best Regards,



I would backup everything, unmount the RAID, shutdown, disconnect the 
RAID devices, remove the SSD, insert a blank SSD, boot the Debian 11 
installer, do a fresh install, configure, do some basic testing, 
shutdown, connect the RAID devices, boot, mount the RAID, and finish 
configuring/ testing.



If Debian 11 turns out to be bad, revert to the Debian 10 SSD.


If the RAID gets trashed, restore from backup.


David

Re: Debian 11 estable en poques hores

[Eduard Selma]

El 12/9/21 a les 15:38, Ernest Adrogué ha escrit:

Hola,

2021-08-22, 11:34 (+0200); Joan Montané escriu:

1.- bullseye soluciona el problema que tenia «ls» en l'ordre de dates,


>> .
>>> En segon lloc, no vull semblar negatiu, però jo segueixo pensant que la

preposició sobra en els llistats de directori.

I, desafortunadament, ls no és l'únic programa afectat.

systemd mostra les dates d'aquesta manera

d’ag. 22 11:56:16 doriath offlineimap[1492]: Syncing Trash: IMAP -> MappedIMAP
d’ag. 22 11:56:17 doriath offlineimap[1492]: *** Finished account 'Posteo.…:03
Hint: Some lines were ellipsized, use -l to show in full.

El dmesg igual:

[dg. d’ag. 22 10:37:23 2021] usb 1-8: device descriptor read/64, error -71
[dg. d’ag. 22 10:37:23 2021] usb 1-8: device descriptor read/64, error -71
[dg. d’ag. 22 10:37:23 2021] usb usb1-port8: attempt power cycle

>
- M'encanten els apòstrofs, és un tret que la nostra llengua comparteix
  amb algunes altres, però que la fan especial.


En definitiva, han passat 4 anys des de que es va "modernitzar" el local
ca_ES, i després de 4 anys jo penso que ja podem afirmar que la
experiència de l'usuari amb el local nou és pitjor que amb el local
anterior.


- Per part meva, em sembla MOLT pitjor, especialment ara amb el 
no-alineament
  de la sortida de ls -la. Fins al punt d'haver-me fet continuar amb 
Buster,

  tot esperant que es pugui solucionar.


Crec que la comunitat d'usuaris de GNU/Linux catalano-parlants ens hem
de plantejar si volem mantenir el local "modernitzat" que no funciona, o
si preferim tornar al local anterior.  Evidentment hi ha arguments a
favor i en contra de les dues alternatives.  Personalment, m'inclino per
la segona.  En fi, jo crec que hi hauria d'haver un debat i una votació
sobre aquest tema.

Què en penseu vosaltres?


- Si hi ha votació, ja podeu afegir el meu +1

  Sempre amb esperit positiu i cordial.

  Salut i codi lliure,  Eduard Selma i Bargalló.

Re: Debian bug report closed or open?

[Brian]

On Sun 12 Sep 2021 at 18:26:57 +0200, l0f...@tuta.io wrote:

> Hi,
> 
> 12 sept. 2021, 12:45 de bouncingc...@gmail.com:
> 
> > Also, as an additional confirmation ...
> > On the above bug page:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
> > the second link is the package name "sudo", which goes to
> > https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo
> > where under the heading
> > "Resolved bugs -- Normal bugs"
> > the bug number 958402 is shown with a strikethrough font
> > (ie it has a horizontal line through the digits).
> >
> Yes, thank you David.
> 
> 12 sept. 2021, 13:42 de a...@cityscape.co.uk:
> 
> > A good tip. However, a point to bear in mind is that Resolved bugs are
> > only visible for a few months (3?, 6?) after being closed.
> >
> Actually, it appears they get archived after some time.
> 
> You can access them by appending "=yes" to the URL of the package on 
> the BTS.
> 
> For example regarding sudo package:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo=yes

Tha's another excellent tip!

-- 
Brian.

Re: copy directory tree, mapping to new owners

[l0f4r0]

Hi Curt,

12 sept. 2021, 16:23 de cu...@free.fr:

> On 2021-09-12, l0f...@tuta.io  wrote:
>
>> In my opinion, trailing slash doesn't matter for destination folder on
>> the contrary of *source* folder.
>>
> It makes a difference when the source is a file and the destination
> directory is inexistant, because in that case a copy of $file named
> $destination will be created, which is not what you want here.
>
I think it is probably not applicable here for the OP (it's a directory) but 
thanks for this special use case :)

This explanation is given in the aforementioned `--mkpath` switch by the way.

The moral is: Pay attention to the single one character you type on the command 
line!
Best regards,
l0f4r0

SOLUCIONADO Re: cups no puedo ingresar

[Marcelo Eduardo Giordano]

grep -i listen /etc/cups/cupsd.conf

Listen localhost *:631

  ^^^

(...)

Hum... ese valor (el formato) no me parece correcto.

Prueba con:

Listen localhost:631

Guarda el archivo de configuración, reinicia el servicio de impresión
(systemctl restart cups.service) y prueba el acceso a la interfaz de
gestión web.


Solucionado!!!

Muchísimas gracias

Re: Debian bug report closed or open?

[l0f4r0]

Hi,

12 sept. 2021, 12:45 de bouncingc...@gmail.com:

> Also, as an additional confirmation ...
> On the above bug page:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
> the second link is the package name "sudo", which goes to
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo
> where under the heading
> "Resolved bugs -- Normal bugs"
> the bug number 958402 is shown with a strikethrough font
> (ie it has a horizontal line through the digits).
>
Yes, thank you David.

12 sept. 2021, 13:42 de a...@cityscape.co.uk:

> A good tip. However, a point to bear in mind is that Resolved bugs are
> only visible for a few months (3?, 6?) after being closed.
>
Actually, it appears they get archived after some time.

You can access them by appending "=yes" to the URL of the package on 
the BTS.

For example regarding sudo package:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo=yes
Best regards,
l0f4r0

Re: Help to let not disappear menu bar on Debian Buster

[Charles Curley]

On Sun, 12 Sep 2021 12:00:22 +0200 (CEST)
fran...@libero.it wrote:

> A friend has installed Debian Buster with XFCE on his pc and each
> time the menu bar at the bottom center and top disappears. Is there a
> way to ensure that it never disappears?
> 
> Since every time I have to go to his house to restart XFCE.

I'm not sure what you mean by "disappears".

XFCE refers to the bars at top and bottom as "panels", so that's what
I'll call them. If you go to panel settings (right click on desktop ->
settings -> panel), you will see for each panel the Display tab. In
that tab is the option to automatically hide the panel always,
intelligently, or never. If that is set to always, the panel will
disappear when you aren't using it.

Hiding means that the panel is reduced to a few pixels at the edge of
the screen. To recover the panel temporarily, hover the mouse pointer
over those few pixels, i.e. very close to the edge of the screen.

Or go to the setting, and change it to never or intelligently.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: copy directory tree, mapping to new owners

[Curt]

On 2021-09-12, l0f...@tuta.io  wrote:

>> # The trailing / matters. Does it matter on the source as well?
>> # I generally include it.
>> rsync -a mysite/doc_root/ mysite_test/doc_root/  # The trailing / 
>> matters.
>>
> Actually, I'm not sure to understand Greg's remark here.
>
> In my opinion, trailing slash doesn't matter for destination folder on
> the contrary of *source* folder.
>

It makes a difference when the source is a file and the destination
directory is inexistant, because in that case a copy of $file named
$destination will be created, which is not what you want here.

Re: Help to let not disappear menu bar on Debian Buster

[Dan Ritter]

fran...@libero.it wrote: 
> Hello,
> 
> A friend has installed Debian Buster with XFCE on his pc and each time the 
> menu bar at the bottom center and top disappears. Is there a way to ensure 
> that it never disappears?
> 
> Since every time I have to go to his house to restart XFCE.

This sounds like either:

- the panel is set to autohide, in which case moving the mouse
  cursor to the bottom and top of the screen should make them
  re-appear

or

- the xfce4-session-manager is not running or has been told not
  to save the running session, so xfce4-panel is not being
  started

-dsr-

Re: Looking for guidance on reporting a bug on the roundcube package

[Andrei POPESCU]

On Du, 12 sep 21, 07:54:32, Steve Dondley wrote:
> 
> > Using free(dom) software sometimes require you invest resources in some
> > other way, depending on the particular issue and how important it is to
> > you ;)
> 
> Agreed. But the package manager will have a much easier time than me at
> nailing down the problem and do it in much less time. I've already spent
> time investigating and isolating the problem so I consider that to be my
> contribution to the issue.

Every contribution is (or at least should be) appreciated.

Even if it takes you longer, the Maintainer could be doing other stuff 
in that time, that might benefit you as well, e.g. provide a backport of 
a newer version (which might also incidentally fix issues like yours, 
that do not qualify for a stable update).

Time is limited for everybody ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Debian 11 estable en poques hores

[Ernest Adrogué]

Hola,

2021-08-22, 11:34 (+0200); Joan Montané escriu:
> 1.- bullseye soluciona el problema que tenia «ls» en l'ordre de dates,
> ara pot mostrar «dia mes» [1] si el fitxer de traducció ho indica.
> 2. Amb això [1], ara sí que s'aplica la línia de format de la
> traducció (en el cas català indica mes dia), però la traducció de
> coretutils de bullseye usa %Ob (mes abreujat sense preposició, p. ex.
> «ag.»), però «ls» no ho parseja internament i per això queden les
> columnes desquadrades.
> 3. Per a evitar el desquadrament del punt anterior es va optar per una
> solució de compromís, i canviar la traducció perquè uses %b (mes
> abreujat amb preposició, p. ex. «d'ag.»), però que «ls» parseja
> internament per a quadrar les columnes).
> 4. Què ha passat, doncs? Que el canvi en la traducció es va fer per a
> coreutils 8.31.90 [2], última versió que consta al Translation
> Project, però bullseye usa 8.32 [3], que no apareix a TP. I la 8.32
> encara té %Ob a la traducció.

Primer de tot vull agrair la feina que fa tota la gent que contribueix a
la localització de programari GNU a la llengua catalana.

En segon lloc, no vull semblar negatiu, però jo segueixo pensant que la
preposició sobra en els llistats de directori.

I, desafortunadament, ls no és l'únic programa afectat.

systemd mostra les dates d'aquesta manera

d’ag. 22 11:56:16 doriath offlineimap[1492]: Syncing Trash: IMAP -> MappedIMAP
d’ag. 22 11:56:17 doriath offlineimap[1492]: *** Finished account 'Posteo.…:03
Hint: Some lines were ellipsized, use -l to show in full.

El dmesg igual:

[dg. d’ag. 22 10:37:23 2021] usb 1-8: device descriptor read/64, error -71
[dg. d’ag. 22 10:37:23 2021] usb 1-8: device descriptor read/64, error -71
[dg. d’ag. 22 10:37:23 2021] usb usb1-port8: attempt power cycle

En definitiva, han passat 4 anys des de que es va "modernitzar" el local
ca_ES, i després de 4 anys jo penso que ja podem afirmar que la
experiència de l'usuari amb el local nou és pitjor que amb el local
anterior.

Crec que la comunitat d'usuaris de GNU/Linux catalano-parlants ens hem
de plantejar si volem mantenir el local "modernitzat" que no funciona, o
si preferim tornar al local anterior.  Evidentment hi ha arguments a
favor i en contra de les dues alternatives.  Personalment, m'inclino per
la segona.  En fi, jo crec que hi hauria d'haver un debat i una votació
sobre aquest tema.

Què en penseu vosaltres?


Salutacions.

Re: html only email

[Gene Heskett]

On Sunday 12 September 2021 07:59:49 to...@tuxteam.de wrote:

> On Sun, Sep 12, 2021 at 06:59:35AM -0400, Gene Heskett wrote:
> > Had better have a very interesting subjct line or it does not get
> > read here. I have, for security reasons, told kmail to not show
> > html, and to override that takes up to 5 mouse clicks.
>
> And...
>
> instant black background for free!

Actually, Tomas, I think that is a configuration choice I made years ago 
and havn't touched since as these old eyes like black text on white.  
Plus my kmail is 1.9 since its tde's r14.0.10 version. 99.9% of kde 
3.5's bugs fixed. Stable.  :-)

>
> ;-)
>
> Cheers
>  - t


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Looking for guidance on reporting a bug on the roundcube package

[Steve Dondley]

Debian is interested in *all* issues affecting a user. The triager will
help sort it out.

If it is a Debian bug, the fix woudld be applied in unstable and work
its way through the system. The same happens with an upstream fix.

So would I just be wasting my time and everyone else's by reporting 
this?


No! Please submit the report.


OK, thanks for the clarification and assurance on this. I didn't want to 
irritate anybody with reports they might consider useless. I'll submit 
the report.

Re: photo opensource

[Polyna-Maude Racicot-Summerside]

Bonjour,

On 2021-09-12 12:38 a.m., ptilou wrote:
> Slt,
> 
> Le vendredi 4 juin 2021 à 20:20:05 UTC+2, Kohler Gerard a écrit :
>> Le 04/06/2021 à 14:41, Polyna-Maude Racicot-Summerside a écrit : 
>>> Bonjour, 
>>>
>>> On 2021-06-04 2:47 a.m., Kohler Gerard wrote: 
 bonjour, 

 merci pour votre implication dans le LL et la photo, 

 je suis sous Debian, et je n'utilise que des LL pour travailler mes 
 photos en dehors de quelques programmes qui sont des goulots 
 d’étranglements comme 

 Vuescan et Turboprint . 

 bon courage et tous mes voeux 

 G. Kohler 

>>> Que voulez-vous dire par "goulot d'étranglement" ?
>> en fait c'est la gestion de certain matériel bien spécifique : 
>>
>> imprimantes photo professionnelle, 
>>
>> scanners (surtout pour la retouche des négatifs ) 
>>
>> ou il n'existe pas encore de solution open source, surtout du fait que 
>> les fabricants ne communiquent pas sur leurs firmware. 
> 
> Voilà de quoi peut-être régler ton histoire de firmwaire :
> https://www.oreilly.com/library/view/linux-device-drivers/0596005903/
> 
Je suis pas trop certaine de comprendre pourquoi partager un livre sur
l'écriture de gestionnaire de périphériques ??

Le problème n'est pas le manque de connaissance dans la communauté.
C'est le manque de volonté des constructeurs de partager les
spécifications matériel de leurs produits.

Il y a amplement de gens capable écrire des gestionnaires de
périphériques. Mais ça ne change rien à la situation...

Comment tu fais pour écrire un gestionnaire de périphérique qui va
communiquer avec un numériseur (scanner) qui te renvoie des données dans
un format impossible à lire ? Qui n'a pas une méthode connu et publique
pour recevoir les commandes ?

Ce n'est pas parce qu'un périphérique est compatible avec la norme USB
1.1/2/3 que ça le rend ouvert pour autant.

4865478936436564655237866112344866542213

Ça signifie page entière, 600 DPI, noir et blanc, +2 pour le contraste

48654789464365646545337466112344866542213
Et ça c'est la même chose sauf que ça dit d'allumer la table lumineuse
pour faire des négatifs.

C'est pas la norme USB qui décrit les commandes à envoyer aux
périphériques. Certe elle décrit les grandes lignes mais pas l'opération
de certaines spécificités.

De la même façon que la norme USB sur les périphériques d'interface
d'entrée (HID) que sont clavier, souris et manette va décrire assez bien
comment interagir avec n'importe quel périphérique de cette classe.
Par contre, les boutons sur une manette de jeu n'auront pas
nécessairement d'ordre spécifique, un sera à un endroit sur un produit
et sera ailleur sur un autre produit.

Il faudra donc configurer la manette de jeu pour redéfinir les boutons.

C'est pareil avec les appareils photos, les numériseurs, etc.

Rien dans la norme USB PTP dicte comment changer la longueur focale sur
un compact expert, comment aller la lumière d'aide au focus, etc. Ce
sont tous des notions qui ont été découverte par rétro-ingénerie.

Si la solution était aussi simple que lire un bouquin de 300 pages, je
crois que ça ferait longtemps que ça aurait été fait. Surtout que ce
livre est présent dans la bibliothèque d'une majorité d'informaticien
développeur et se trouve facilement sur Google gratuitement.
>>
>> sinon comme logiciels j'utilise darktable, Krita, Mypaint, Inkscape, 
>> Blender, Luminance HDR. 
>>
>> Je n'utilise pas ou peu Gimp, trouvant Krita largement supérieur 
>>
>> G. Kohler
> 
> — 
> Ptilou 
> 

-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development



OpenPGP_signature
Description: OpenPGP digital signature

Re: html only email

[tomas]

On Sun, Sep 12, 2021 at 06:59:35AM -0400, Gene Heskett wrote:
> Had better have a very interesting subjct line or it does not get read 
> here. I have, for security reasons, told kmail to not show html, and to 
> override that takes up to 5 mouse clicks.

And...

instant black background for free!

;-)

Cheers
 - t


signature.asc
Description: Digital signature

Re: Looking for guidance on reporting a bug on the roundcube package

[Steve Dondley]

Using free(dom) software sometimes require you invest resources in some
other way, depending on the particular issue and how important it is to
you ;)


Agreed. But the package manager will have a much easier time than me at 
nailing down the problem and do it in much less time. I've already spent 
time investigating and isolating the problem so I consider that to be my 
contribution to the issue.




Just documenting an issues is still helpful, as it might help other
Roundcube users (on Debian) save time, e.g. by not redoing your
investigation.


Yes, good point. I'll submit the report. Thanks.

Re: Debian bug report closed or open?

[Brian]

On Sun 12 Sep 2021 at 20:45:13 +1000, David wrote:

> On Sun, 12 Sept 2021 at 20:20,  wrote:
> > 12 sept. 2021, 10:00 de scdbac...@gmx.net:
> > > l0f...@tuta.io wrote:
> > >
> > >> By the way, how can one see that a bug is closed and not open please?
> > >> [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
> > >>
> > > I think you can recognize it by the "Done:" header on the web page:
> > >
> > >  Done: Marc Haber <> mh+debian-packa...@zugschlus.de> >
> 
> Also, as an additional confirmation ...
> On the above bug page:
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
> the second link is the package name "sudo", which goes to
>   https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo
> where under the heading
>   "Resolved bugs -- Normal bugs"
> the bug number 958402 is shown with a strikethrough font
> (ie it has a horizontal line through the digits).

A good tip. However, a point to bear in mind is that Resolved bugs are
only visible for a few months (3?, 6?) after being closed.

-- 
Brian.

Re: HP Elitebook with external display and color issue [SOLVED]

[deloptes]

deloptes wrote:

>> That link mentions using a D-SUB (you didn't specify what you are using,
>> please do so), in which case take particular care to ensure it is
>> properly inserted, at *both* ends.
>> 
>> Even so, you should try using HDMI/DVI/DisplayPort instead (whichever is
>> available).
> 
> Thank you Andrei!
> 
> I give a try to the relevant part of the posting and

(sorry pressed ENTER)

TearFree option did the trick

Section "Device"
Identifier  "Card0"
Driver  "intel"
...
Option "TearFree"   "off" # []
EndSection


-- 
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0

Re: HP Elitebook with external display and color issue

[deloptes]

Andrei POPESCU wrote:

> That link mentions using a D-SUB (you didn't specify what you are using,
> please do so), in which case take particular care to ensure it is
> properly inserted, at *both* ends.
> 
> Even so, you should try using HDMI/DVI/DisplayPort instead (whichever is
> available).

Thank you Andrei!

I give a try to the relevant part of the posting and 


-- 
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0

html only email

[Gene Heskett]

Had better have a very interesting subjct line or it does not get read 
here. I have, for security reasons, told kmail to not show html, and to 
override that takes up to 5 mouse clicks.

Plain text that gets past spamassassin and clamav, does get read 100%. So 
the choice as to whether or not your message is read, is up to you. If 
you choose to use a broken email agent, expect to be ignored.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Looking for guidance on reporting a bug on the roundcube package

[Brian]

On Sat 11 Sep 2021 at 22:40:32 -0400, Steve Dondley wrote:

> First, thanks to everyone here and the Debian community, an amazing project.
> 
> Running bullseye with package roundcube. I believe I have found a bug that
> I'd like to report.
> 
> I am using reportbug to report it. When doing so, I got this message:
> 
> Your version (1.4.11+dfsg.1-4) of roundcube appears to be out of date.
> The following newer release(s) are available in the Debian archive:
>   experimental: 1.5~rc+dfsg.1-1
> Please try to verify if the bug you are about to report is already addressed
> by these releases.  Do you still want to file a report [y|N|q|?]? n
> Newer released version; stopping.

Technically, the first part of the message is correct. However, your
version of roundcube and unstable's version are the same. Submit the
report.

Even if unstable's version was higher, I would still send the report.
The Project needs users to participate.
 
> I don't want to install an experimental package on a production machine to
> verify the bug and I really don't have the time to set up a debian
> installation and install roundcube to test this.

Not unreasonable. I expect the scary notice on this archive's webpage
is also demotivating.

> So it's unclear to me if I should bother reporting this bug or if they are
> only interested in hearing about bugs from the upcoming release candidate. I
> have reported the bug to roundcube's github page already. I'm not even
> entirely sure if this is a bug with the package or roundcube itself. I'm
> going to assume it's a debian package issue because my issue on github was
> closed without comment:
> https://github.com/roundcube/roundcubemail/issues/8198

Debian is interested in *all* issues affecting a user. The triager will
help sort it out.

> I've always been confused by whether and how debian patches relatively bugs
> like this. I think only security patches were issued and minor usability
> fixes don't get release until the next version of debian. But I may be
> totally wrong on this.

If it is a Debian bug, the fix woudld be applied in unstable and work
its way through the system. The same happens with an upstream fix.

> So would I just be wasting my time and everyone else's by reporting this?

No! Please submit the report.

-- 
Brian.

Re: Looking for guidance on reporting a bug on the roundcube package

[Andrei POPESCU]

On Sb, 11 sep 21, 22:40:32, Steve Dondley wrote:
> First, thanks to everyone here and the Debian community, an amazing project.
> 
> Running bullseye with package roundcube. I believe I have found a bug that
> I'd like to report.
> 
> I am using reportbug to report it. When doing so, I got this message:
> 
> Your version (1.4.11+dfsg.1-4) of roundcube appears to be out of date.
> The following newer release(s) are available in the Debian archive:
>   experimental: 1.5~rc+dfsg.1-1
> Please try to verify if the bug you are about to report is already addressed
> by these releases.  Do you still want to file a report [y|N|q|?]? n
> Newer released version; stopping.
> 
> I don't want to install an experimental package on a production machine to
> verify the bug and I really don't have the time to set up a debian
> installation and install roundcube to test this.

Using free(dom) software sometimes require you invest resources in some 
other way, depending on the particular issue and how important it is to 
you ;)
 
> So it's unclear to me if I should bother reporting this bug or if they are
> only interested in hearing about bugs from the upcoming release 
> candidate.

In general a report is better than no report. The Maintainer might be 
able to easily do the test instead.

Alternatively, it seems you know your way around the source code, so 
maybe you can confirm it is still unchanged.

> I have reported the bug to roundcube's github page already. I'm not 
> even entirely sure if this is a bug with the package or roundcube 
> itself. I'm going to assume it's a debian package issue because my 
> issue on github was closed without comment:
> https://github.com/roundcube/roundcubemail/issues/8198

If you're unsure it is best to report the issue to Debian first.

If the problem is upstream the Debian Maintainer might ask you to open 
an issue upstream (or do that themselves).

Depending on the relation with Debian some upstreams will just close 
bugs instantly at just a mention of Debian. Sometimes this is even 
justified (e.g. in case Debian patches the software heavily and/or is 
using ancient versions that are not supported anymore).

Closing bugs without *any* kind of explanation is still annoying (to say 
the least) :(

> I've always been confused by whether and how debian patches relatively bugs
> like this. I think only security patches were issued and minor usability
> fixes don't get release until the next version of debian. But I may be
> totally wrong on this.

As a general rule stable (and oldstable for one year after the stable 
release) only receive fixes for security and major issues. The next 
stable release should get new upstream versions instead (that may or may 
not fix your issue).

> So would I just be wasting my time and everyone else's by reporting this?

Just documenting an issues is still helpful, as it might help other 
Roundcube users (on Debian) save time, e.g. by not redoing your 
investigation.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Debian bug report closed or open?

[David]

On Sun, 12 Sept 2021 at 20:20,  wrote:
> 12 sept. 2021, 10:00 de scdbac...@gmx.net:
> > l0f...@tuta.io wrote:
> >
> >> By the way, how can one see that a bug is closed and not open please?
> >> [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
> >>
> > I think you can recognize it by the "Done:" header on the web page:
> >
> >  Done: Marc Haber <> mh+debian-packa...@zugschlus.de> >

Also, as an additional confirmation ...
On the above bug page:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
the second link is the package name "sudo", which goes to
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo
where under the heading
  "Resolved bugs -- Normal bugs"
the bug number 958402 is shown with a strikethrough font
(ie it has a horizontal line through the digits).

Re: HP Elitebook with external display and color issue

[Andrei POPESCU]

On Du, 12 sep 21, 02:58:13, deloptes wrote:
> Hi,
> I don't know how to explain my problem, but I try hoping that someone would
> understand and help me fix it.
> 
> So I have one HP Elitebook (I think it is 820 G2) with 16GB RAM and Intel(R)
> Core(TM) i5-7200U CPU @ 2.50GHz.
> 
> The issue is that when it starts with its own display the colors are OK, but
> as soon as I activate an additional display the colors get messed and it is
> looking ugly like described
> https://h30434.www3.hp.com/t5/Notebook-Video-Display-and-Touch/820-g1-Ubuntu-Screen-artifacts/m-p/7029819/highlight/true#M188601)

Hardware


That link mentions using a D-SUB (you didn't specify what you are using, 
please do so), in which case take particular care to ensure it is 
properly inserted, at *both* ends.

Even so, you should try using HDMI/DVI/DisplayPort instead (whichever is 
available).

If the cable is (very) long try using a shorter, known good one, 
regardless of type.

If you are using any kind adapters try connecting directly with the 
correct cable instead.

Is there any difference if the laptop is connected to AC (or not)?


Software


What Debian release is this (and kernel version if not default)? Try a 
newer kernel, e.g. from -backports.

What driver is in use, device specific or modesetting? Try the other one 
instead (or the proprietary one, if applicable).

Your Xorg.0.log would be useful to get more information about your 
hardware and software, and/or check for possible issues.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: copy directory tree, mapping to new owners

[Andrei POPESCU]

On Du, 12 sep 21, 08:52:55, john doe wrote:
> On 9/12/2021 3:45 AM, Richard Hector wrote:
> > On 12/09/21 12:52 pm, Greg Wooledge wrote:
> > > 
> > > cd /src
> > > mkdir -p /dest
> > > rsync -a . /dest/  # The trailing / matters.
> > > cd /dest
> > > find . -user mysite -exec chown mysite_test {} +
> > > find . -user mysite-run -exec chown mysite-run_test {} +
> 
> Given that you want to change the ownership, you may want to emulate the
> options implied by '-a' but without the ownership option ('-o').

It might not matter for a site[1], but do note that -a doesn't include 
-H (preserve hardlinks), -A (preserve ACLs) and -X (preserve extended 
attributes).

[1] It definitely matters for system installations, as I found out the 
hard way.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Debian bug report closed or open?

[l0f4r0]

Hi,

12 sept. 2021, 10:00 de scdbac...@gmx.net:

> l0f...@tuta.io wrote:
>
>> By the way, how can one see that a bug is closed and not open please?
>> [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
>>
> I think you can recognize it by the "Done:" header on the web page:
>
>  Done: Marc Haber <> mh+debian-packa...@zugschlus.de> >
>
Well spotted Thomas!

It makes sense indeed with the email address  used to 
close a bug.

Thanks & have a great week-end!
l0f4r0

Re: debian-installer RAID question

[Andrei POPESCU]

On Sb, 11 sep 21, 18:55:56, Felix Natter wrote:
> hello fellow Debian users,
> 
> I have an SSD for the root filesystem, and two HDDs using RAID1 for
> /storage running Debian10. Now I need a plan B in case the upgrade
> fails.
> 
> So I made an experiment with a VM and rougly the same setup (disk-wise),
> and found out that when reinstalling Debian11, the d-i does recognize
> the RAID1 (/storage) and can reuse it while keeping the data.

Careful here! You can tell d-i to not format an existing partition, but 
if you want to use it as the root partition the new system will probably 
be installed in the same file structure as your other data.

Is this what you're considering?

Provided you have sufficient space on the RAID you should rather create 
a dedicated partition for the backup install, even if you need to shrink 
another partition (or several). The installer should be able to do that 
as well, though backing up your data is recommended[1].

On the other hand, as plan B in case of upgrade failures you can also 
use the rescue mode of the Debian Installer or, if you need a full 
system, install Debian to a USB stick. The speed might not be great[2], 
but it should be sufficient to get you out of trouble.

If you go this route make sure the stick still boots and works as 
expected even if you disconnect all other storage from the system.

[1] Just in case it's not obvious, the RAID won't help in case the 
resizing goes wrong (it shouldn't, but...).

[2] The speed will depend on the particular stick (look for one with 
consistent good write speed) and ports (USB 3 or better if possible, but 
USB 2 will also work). Avoid Desktop Environments if possible, or at 
least choose a light one like LXDE. 

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Help to let not disappear menu bar on Debian Buster

[frantal]

Hello,

A friend has installed Debian Buster with XFCE on his pc and each time the menu 
bar at the bottom center and top disappears. Is there a way to ensure that it 
never disappears?

Since every time I have to go to his house to restart XFCE.

Thanks for help

Francesco

Re: Will my reportbug report be seen?

[Andrei POPESCU]

On Vi, 10 sep 21, 20:22:43, Steve Dondley wrote:
> 
> Yeah, had I known my bug report would be thrown in the subject, I would have
> changed things up a bit.

The report should still go in the message body, the subject (and bug 
title) is supposed to represent a concise summary.

For reference, the text in reportbug is:

Briefly describe the problem (max. 100 characters allowed). This 
will be the bug email subject, so keep the summary as concise as 
possible, for example: "fails to send email" or "does not start with 
-q option specified" (enter Ctrl+c to exit reportbug without 
reporting a bug).


How would you reword it to make it clearer?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: is it possible to send e-mail via Yahoo's smtp servers using Thunderbird (78.13.0)?

[Andrei POPESCU]

On Vi, 10 sep 21, 20:55:43, Gary Dale wrote:
> On 2021-09-10 18:11, Alexander V. Makartsev wrote:
> > 
> > Pretty sure, it's the issue with Yahoo¹ ², nothing to do with Thunderbird.
> > Yahoo is following the same path as GMail, forcing their users to use
> > web browsers as mail clients.
> > In case of GMail you have to use same generated "app-password" for both
> > IMAP and SMTP services.
> > I guess the same principle will be for Yahoo.
> > 
> > 
> > [1]
> > https://help.yahoo.com/kb/account/temporary-access-insecure-sln27791.html
> > [2] 
> > https://help.yahoo.com/kb/account/generate-manage-third-party-passwords-sln15241.html
> > -- 
> Yes, I've tried the app passwords without success. As near as I can tell,
> they are just a randomly generated secure password that is linked to a
> particular application as well as the account.
 
On the other hand, at least in my opinion, they are preferable for 
situations where it's necessary to write the password in some 
configuration file (e.g. MTA configured to forward via smarthost, for 
interactive use it's possible to use a password manager instead).

The application password can only be used for SMTP/POP/IMAP (but not for 
logging in to the web interface) and in case you have reason to suspect 
it was compromised it can be easily revoked from the web interface.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Installing old/deprecated packages

[Andrei POPESCU]

On Lu, 06 sep 21, 16:04:29, Linux-Fan wrote:
> riveravaldez writes:
> 
> > On 9/5/21, Linux-Fan  wrote:
> > >
> > > My personal choice would be to install the packages without adding the
> > > oldstable repositories as to be reminded that they are obsolete and are
> > > likely to stop working in the future.
> > 
> > Thanks again. Very informative and educational.
> > When you say 'as to be reminded that they are obsolete', how/when/where
> > the system will remind me this?, will it be?
> 
> There is no automatism for this that I am aware of. There are tools like
> `deborphan` and `aptitude search ~o` that may tell you about them.

In aptitude's interactive mode there is a special section for them, that 
only shows up if there are any. Does this count as "automatism"? :)

For completeness, obsolete packages can also happen within the same 
release, e.g. old linux-image packages. APT is configured to keep one 
older version by default, the others are fair game for 'autoremove'.

> The release notes recommend proactively removing obsolete packages:
> 
> https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html#for-next

Yes, though some care might be needed, depending on the situation[1].

E.g. leafpad was replaced by mousepad in buster. If you just execute the 
'aptitude purge ~o' aptitude might want to remove the entire LXDE 
environment, because the lxde metapackage in buster has
'Depends: leafpad | mousepad'.

The solution in this particular case is to tell aptitude to install (and 
set as 'automatic') mousepad in the same run[2].

[1] Always inspect the list of proposed removals by apt/itude carefully 
before confirming. In case it looks wrong just ask on the list with the 
copy-paste of the full output.
[2] There are several methods to do that, depending on your familiarity 
with aptitude.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: copy directory tree, mapping to new owners

[tomas]

On Sun, Sep 12, 2021 at 10:46:01AM +0300, Teemu Likonen wrote:

[...]

> Looks exactly like what "rsync --usermap=FROM:TO" can do. There is also
> "--groupmap" option for mapping groups.

Never underestimate rsync :-)

Actually, I do read its manpage from time to time. Should do it more
often, perhaps as (yet another) after-breakfast routine.

Thanks, Teemu, this one wasn't aware to me!

Cheers
 - t


signature.asc
Description: Digital signature

Re: Debian bug report closed or open?

[Thomas Schmitt]

Hi,

l0f...@tuta.io wrote:
> By the way, how can one see that a bug is closed and not open please?
> [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402

I think you can recognize it by the "Done:" header on the web page:

  Done: Marc Haber 

I see it in an old bug that was closed by a package release
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731023
but not in a still open bug which is awaiting closure by package release
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993646


(The release close mechanism can be seen in the debian/changelog
of the affected package:
  * Introduced debian/xorriso.info list. (Closes: #731023)
This way the maintainer does not have to remember solved bugs when the
fixed release gets out.)


Have a nice day :)

Thomas

Re: (HTML) Re: Trouble upgrading Debian (reply to David Wright)

[Andrei POPESCU]

On Lu, 06 sep 21, 16:46:24, Dedeco Balaco wrote:
> 
> 
> Em 06/09/2021 14:25, John Hasler escreveu:
> > Curt writes:
> >> I suggest you follow the earlier advice, and set Thunderbird 
> >> to compose your email as plain text
> > Or even as "normal" HTML.
> 
> If it is trivial to me setting my mail manager to use the dark
> background i need, and to make it ignore the (usually default)
> background of color of all HTML messages, why the people in Debian User
> list cannot do it?

If your mail client is sending both html and plain text most subscribers 
will only see the plain text version (unless they go out of their way to 
look at the html version).

> I will not change my setting! I need it. Learn to
> deal with it. Things evolve. Being able to use *bold*, /italic/,
> _underscore_ is a minimum of "new" things that help a lot to compose
> good messages.

You mean like the markup in the text above? :)

(probably added by Thunderbird for the text version)

While I do agree with you somewhat, as far as I'm aware there is no 
agreed upon standard for HTML mail. How the receiving end will display 
your message is very much open to interpretation.

Some mail clients might even "lie" to you and show e.g. a sans font when 
composing, but the receiving end will display that message with a serif 
font (didn't bother to check the source to see which one of them is 
"wrong").

> If Thunderbird has a problem when writing the automatic
> text messages, together with the composed HTML ones, this is a reason to
> _**fix**_ it, not to never use anymore.

There should be a setting in Thunderbird to *not* remove "extra" line 
breaks (or similar) for the text version, please enable it.

> I have installed another mail
> manager in my computer: but it is bad, pretty horrible. It does not show
> HTML messages. It does not compose HTML messages. And it is pretty
> counter intuitive to configure, in several parts. It seems handy, have
> nice things. But if you do not know them, or are not familiar enough
> with "something", to be able to understand it, you cannot use them. Its
> name is Claws Mail. 

Last time I tried it Claws Mail could display (but not compose) HTML 
messages, you might need to enable it and/or install some plugin.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: /usr/sbin/reboot: disabled in systemd-nspawn container SOLVED

[Andrei POPESCU]

On Sb, 04 sep 21, 17:35:49, sp...@caiway.net wrote:
> SOLVED
> 
> /usr/share/open-infrastructure/container/shutdown.txt
> is from package progress-linux-container:
> 
> Progress Linux is a Debian derivative distribution focused on system
> integration.
> 
> This package is a metapackage to be installed in a container
> (systemd-nspawn).
> 
> # apt remove progress-linux-container

You should probably `purge` it, `remove` can leave stuff behind.

(didn't bother to check for this particular package, but anyway, I like 
my `dpkg -l` "clean")

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: copy directory tree, mapping to new owners

[Teemu Likonen]

* 2021-09-12 12:43:29+1200, Richard Hector wrote:

> The context of my question is that I'm creating (or updating) a test
> copy of a website. The files are owned by one of two owners, depending
> on whether they were written by the server (actually php-fpm).
>
> To do that, I want all the permissions to remain the same, but the
> ownership should be changed according to a provided map.

Looks exactly like what "rsync --usermap=FROM:TO" can do. There is also
"--groupmap" option for mapping groups.

-- 
/// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/
// OpenPGP: 4E1055DC84E9DFF613D78557719D69D324539450


signature.asc
Description: PGP signature

Re: Sound input source detected but not capturing

[Andrei POPESCU]

On Sb, 04 sep 21, 12:58:14, Marko Randjelovic wrote:
> On Sat, 04 Sep 2021 07:47:02 +0530
> Pankaj Jangid  wrote:
> > 
> > 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---
> > 
> 
> Your control 'Capture',0 is turned on and volume is at maximum, so
> that's fine, but you don't have 'input source' control. On my machine
> output of 'amixer -c0' gives among other controls the following:
> 
> Simple mixer control 'Input Source',0
>   Capabilities: cenum
>   Items: 'Rear Mic' 'Front Mic' 'Line' 'CD'
>   Item0: 'Rear Mic'
> 
> I suppose this is the reason why your capture is not working, but don't
> know how to fix it.

Well, there's no "Internal Mic" and "Mic" to choose from, so maybe 
that's the problem.

@Pankaj, do you have a microphone connected to the audio (combo) jack 
and/or maybe the internal microphone is disabled in EFI and/or from 
hotkeys?

> You might try to install kernel 5.13 from
> experimental or newest vanilla stable which is currently 5.14.1 (take
> care not to make your system unbootable). Also you might try with newer
> alsa userland software.

Or this...

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Debian bug report closed or open? (was: Will my reportbug report be seen?)

[l0f4r0]

Hi,

11 sept. 2021, 18:52 de a...@cityscape.co.uk:

> It's your submission; you can close it, In fact, any user can clos
>  it.
>
By the way, how can one see that a bug is closed and not open please?

For example, I know that the bug #958402 [1] has been closed because I received 
an email notification for that (I'm the submitter) but it's written nowhere in 
the webpage itself (at least I can't find it...).
[1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402

l0f4r0

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

[Andrei POPESCU]

On Vi, 03 sep 21, 19:05:23, Daniel M. wrote:
> 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".

You might as well just get rid of your pinning, 500 is the default 
priority and setting Default-Release is raising the priority of testing 
to 990 anyway (`apt policy` should reflect that, otherwise something is 
wrong).

apt_preferences(5) suggests APT treats Default-Release special compared 
to some release with priority 990, so it's still worth using that 
instead of pinning to 990.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: copy directory tree, mapping to new owners

[l0f4r0]

12 sept. 2021, 08:53 de l0f...@tuta.io:

> 12 sept. 2021, 03:45 de rich...@walnut.gen.nz:
>
>> # actually not necessary? rsync will create it
>> mkdir -p mysite_test/doc_root
>>
> You can make a simple test to know that but I would say that rsync doesn't 
> create your destination "root" directory (the one you specify on the command 
> line) unless `--mkpath` is used.
>
Actually, I've just did some tests and it appears that rsync creates the 
destination folder if its parent already exists and if you have the right 
permissions.

For example ("my" and "dest" don't exist yet):

rsync -a src/ dest => "dest" is created

rsync -a src/ my/dest => error, "my" and "dest" don't exist (and are not 
created then)

rsync --mkpath -a src/ my/dest => "my" and "dest" are created

l0f4r0

Re: Install Debian netinstall to HP Elitebook 840 G8 problem

[Andrei POPESCU]

On Vi, 03 sep 21, 08:09:25, Patrick Bartek wrote:
> 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?

The Debian Installer works for me on EFI with SecureBoot enabled.

If you encounter any issues with it the Debian Installer Team will 
likely want to know about it (`reportbug installation-report` would be a 
good start).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: copy directory tree, mapping to new owners

[l0f4r0]

Hi,

12 sept. 2021, 03:45 de rich...@walnut.gen.nz:

> On 12/09/21 12:52 pm, Greg Wooledge wrote:
>
>> cd /src
>> mkdir -p /dest
>> rsync -a . /dest/  # The trailing / matters.
>> cd /dest
>> find . -user mysite -exec chown mysite_test {} +
>> find . -user mysite-run -exec chown mysite-run_test {} +
>>
>
> [...]
> # actually not necessary? rsync will create it
> mkdir -p mysite_test/doc_root
>
You can make a simple test to know that but I would say that rsync doesn't 
create your destination "root" directory (the one you specify on the command 
line) unless `--mkpath` is used.

> # The trailing / matters. Does it matter on the source as well?
> # I generally include it.
> rsync -a mysite/doc_root/ mysite_test/doc_root/  # The trailing / matters.
>
Actually, I'm not sure to understand Greg's remark here.

In my opinion, trailing slash doesn't matter for destination folder on the 
contrary of *source* folder.

In other words, for me, the following are equal:
rsync -a mysite/doc_root/ mysite_test/doc_root/
rsync -a mysite/doc_root/ mysite_test/doc_root

But not the following:
rsync -a mysite/doc_root mysite_test/doc_root => you will get an extra 
"doc_root" folder (the source one) in your dest, i.e. : 
mysite_test/doc_root/doc_root and then the content of doc_root source
rsync -a mysite/doc_root/ mysite_test/doc_root => your doc_root (destination) 
folder will get doc_root content (source) directly

Best regards,
l0f4r0

Re: copy directory tree, mapping to new owners

[john doe]

On 9/12/2021 3:45 AM, Richard Hector wrote:

On 12/09/21 12:52 pm, Greg Wooledge wrote:

On Sun, Sep 12, 2021 at 12:43:29PM +1200, Richard Hector wrote:

The context of my question is that I'm creating (or updating) a test
copy of
a website. The files are owned by one of two owners, depending on
whether
they were written by the server (actually php-fpm).

To do that, I want all the permissions to remain the same, but the
ownership
should be changed according to a provided map. For example, if the
old file
was owned by 'mysite', the copy should be owned by 'mysite_test'. If
the old
file was owned by 'mysite-run' (the user php runs as), the copy
should be
owned by 'mysite_test-run' (if that has to be 'mysite-run_test' to make
things easier, I can live with that).


cd /src
mkdir -p /dest
rsync -a . /dest/  # The trailing / matters.
cd /dest
find . -user mysite -exec chown mysite_test {} +
find . -user mysite-run -exec chown mysite-run_test {} +


Thanks, that looks reasonable. It does mean, though, that the files
exist for a while with the wrong ownership. That probably doesn't
matter, but somehow 'feels wrong' to me.



If you are doing this in a script, I would use a temporary directory.
That way, in case of failure the destination directory is not rongly
modified.

EG:

$ rsync  

Make  the way you want it to be.

$ rsync  


Given that you want to change the ownership, you may want to emulate the
options implied by '-a' but without the ownership option ('-o').


My habits would also lead me to do all of the above from above the two
directories in question (in my case, /srv - for /srv/mysite/doc_root and
/srv/mysite_test/doc_root) So:

cd /srv

# actually not necessary? rsync will create it
mkdir -p mysite_test/doc_root

# The trailing / matters. Does it matter on the source as well?


According to the man page it does (1):

"CWrsync -avz foo:src/bar/ /data/tmp
A trailing slash on the source changes this behavior to avoid creating
an additional directory level at the destination. You can think of a
trailing / on a source as meaning lqcopy the contents"


# I generally include it.


In a script, you need to be sure what the cmd does do or not do!!! :)


rsync -a mysite/doc_root/ mysite_test/doc_root/  # The trailing /
matters.

find mysite_dest -user mysite -exec chown mysite_test {} +

# I prefer mysite_test-run; it keeps consistency with
# the ${sitename}-run pattern used elsewhere
find mysite_dest -user mysite-run -exec chown mysite_test-run {} +

Have I broken anything there?



Not that I can see but testing will tell!


This is what I would do.  And I would do it *interactively*.

If you insist on making a script, then it will be slightly more
complicated, because you'll need to add error checking.


The trouble with doing it interactively, when it needs to be done many
times (and on several sites), is that each time there's opportunity to
make a mistake. And it means the process needs to be documented
separately from the script.

In fact, I'd incorporate the above in a larger script, which does things
like copying the database (and changing the db name in the site config).

Error checking in shell scripts is something I certainly need to learn


At the very least, ' ['&&'|'||'] handle the error>.

If you use Bash and don't need to be POSIX compliant and /or portable
you can be a bit more creative.


and practice more - I tend to rely somewhat on 'knowing' what I'm
working with, which is probably not a good idea.

>

Yes in a script it is like shooting yourself in the foot.


1)  https://linux.die.net/man/1/rsync

--
John Doe

Re: HTML mail [was: How to improve my question in stackoverflow?]

[Joe]

On Fri, 10 Sep 2021 15:22:30 -0400
rhkra...@gmail.com wrote:

> On Friday, September 10, 2021 08:45:19 AM Joe wrote:
> > Sadly, much html comes of of MS software, and takes about ten pages
> > of markup to include three text lines.  
> 
> That may be (or may be a slight exxageration ;-), but in my email
> client, if I get a multipart message, the plain text part is
> displayed and I see the 3 lines of text -- I don't see the 10 pages
> of markup.
> 
> Do you see the ~10 pages of markup?

If I need to pick through the html to find something missing from the
text, but very often those who use Word as an html email client have
never heard of the concept of alternate text.

-- 
Joe