Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
On 20/05/24 at 14:35, Marc SCHAEFER wrote: Any idea what could be the problem? Any way to just make grub2 ignore the rimage (sub)volumes at setup and boot time? (I could live with / aka vg1/root not using dm-integrity, as long as the data/docker/etc volumes are integrity-protected) ? Or how to make grub 100% compatible with a vg1/root using dm-integrity (that would be obviously the final goal!) Thank you for any pointers! I can only recommend you to read carefully the Wiki: https://raid.wiki.kernel.org/index.php/Dm-integrity HTH kind regards -- Franco Martelli
Re: Sonido en Debian instalado en una Rpi4
El día 20/05/2024, a las 15:50, Camaleón escribió: > Parece un problema conocido relacionado con los controladores de audio > y/o el subsistema de gestión de sonido (PulseAudio/Jackd/ALSA, etc...). > > Mira a ver qué driver o stack de sonido instala/usa Raspberry Pi OS¹, > donde seguramente todo el hardware funcione sin problemas, y trata de > «emularlo» en Debian. > > ¹https://www.raspberrypi.com/software/operating-systems/ > > Gracias. Sí, creo que no me queda otro remedio. Me huelo que deberé recompilar el núcleo para añadir el módulo correspondiente.
Re: Sonido en Debian instalado en una Rpi4
El 2024-05-20 a las 11:49 +0200, Alfon escribió: > He seguido los pasos para instalar Debian descritos en: > https://wiki.debian.org/RaspberryPi4#Using_EFI_Firmware_and_the_regular_Debian_Installer > > Y todo ha ido bien, excepto que no tengo puedo usar la GPU para ver > vídeos con mpv y tampoco tengo sonido. Me interesa esto último, > ¿alguien lo ha conseguido? Parece un problema conocido relacionado con los controladores de audio y/o el subsistema de gestión de sonido (PulseAudio/Jackd/ALSA, etc...). Mira a ver qué driver o stack de sonido instala/usa Raspberry Pi OS¹, donde seguramente todo el hardware funcione sin problemas, y trata de «emularlo» en Debian. ¹https://www.raspberrypi.com/software/operating-systems/ Saludos, -- Camaleón
Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, 1. INITIAL SITUATION: WORKS (no dm-integrity at all) I have a Debian bookwork uptodate system that boots correctly with kernel 6.1.0-21-amd64. It is setup like this: - /dev/nvme1n1p1 is /boot/efi - /dev/nvme0n1p2 and /dev/nvme1n1p2 are the two LVM physical volumes - a volume group, vg1 is built with those PVs vg1 has a few LVs that have been created in RAID1 LVM mode: lvdisplay | egrep 'Path|Mirrored' LV Path/dev/vg1/root <-- this is / Mirrored volumes 2 LV Path/dev/vg1/swap Mirrored volumes 2 LV Path/dev/vg1/scratch Mirrored volumes 2 LV Path/dev/vg1/docker Mirrored volumes 2 As said, this boots without any issue. 2. ADDING dm-integrity WHILE BOOTED: works! Now, while booted, I can add dm-integrity to one of the volumes, let's say /dev/vg1/docker (this LV has absolutely no link with the boot process, except obviously it is listed in /etc/fstab -- it also fails the same way if even the swap is dm-integrit enabled, or /): lvconvert --raidintegrity y --raidintegritymode bitmap vg1/docker and wait a bit til the integrity is setup with lvs -a (100%) Obviously, this creates and uses a few rimage/rmeta sub LVs. Then I did this (after having boot issues): echo dm_integrity >> /etc/initramfs-tools/modules update-initramfs -u This did not change the below issue: 3. grub BOOT FAILS IF ANY LV HAS dm-integrity, EVEN IF NOT LINKED TO / if I reboot now, grub2 complains about rimage issues, clear the screen and then I am at the grub2 prompt. Booting is only possible with Debian rescue, disabling the dm-integrity on the above volume and rebooting. Note that you still can see the rimage/rmeta sub LVs (lvs -a), they are not deleted! (but no dm-integrity is activated). 4. update-grub GIVES WARNINGS Now, if I try to start update-grub while booted AND having enabled dm-integrity on the vg1/docker volume, I get: # update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.1.0-21-amd64 Found initrd image: /boot/initrd.img-6.1.0-21-amd64 error: unknown node 'docker_rimage_0'. [ ... many ... ] /usr/sbin/grub-probe: error: disk `lvmid/xLE0OV-wQy7-88H9-yKCz-4DUQ-Toce-h9rQvk/FzCf1C-95eB-7B0f-DSrF-t1pg-66qp-hmP3nZ' not found. error: unknown node 'docker_rimage_0'. [ ... many ... ] [ this repeats a few times ] Found linux image: /boot/vmlinuz-6.1.0-10-amd64 Found initrd image: /boot/initrd.img-6.1.0-10-amd64 Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi Warning: os-prober will not be executed to detect other bootable partitions. [ there are none ] Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Adding boot menu entry for UEFI Firmware Settings ... done Any idea what could be the problem? Any way to just make grub2 ignore the rimage (sub)volumes at setup and boot time? (I could live with / aka vg1/root not using dm-integrity, as long as the data/docker/etc volumes are integrity-protected) ? Or how to make grub 100% compatible with a vg1/root using dm-integrity (that would be obviously the final goal!) Thank you for any pointers!
Re: Debian, fail2ban, Version?
On 20 May 2024 07:00 -0400, from d...@randomstring.org (Dan Ritter): >> # fail2ban-server -V >> >> 0.11.2 > > Bullseye became stable in August of 2021. It's also perhaps worth noting that there seem to have been only two interim releases. https://github.com/fail2ban/fail2ban/releases lists 0.11.2 (Nov 2020), 1.0.1 (Sep 2022), 1.0.2 (Nov 2022) and 1.1.0 (April 2024). The release notes for 1.1.0 says 0.11 or 1.0 can be used if you have Python < 3.5; and 1.0.1 says 0.11 can be used if you have Python < 2.7. -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Re: Debian, fail2ban, Version?
Maurizio Caloro wrote: > Hello > > Please why on Debian Bullseye, 11.9 is a pretty old version available in the > repository? > > # fail2ban-server -V > > 0.11.2 Bullseye became stable in August of 2021. "Stable" means that packages don't change except to fix serious bugs, especially security-related bugs. Bookworm became stable in June of 2023. The fail2ban version there is 1.0.2-2. -dsr-
Debian, fail2ban, Version?
Hello Please why on Debian Bullseye, 11.9 is a pretty old version available in the repository? # fail2ban-server -V 0.11.2 I think this application arnt a big thing? Available on github, Version 1.1.0
Sonido en Debian instalado en una Rpi4
Hola lista, He seguido los pasos para instalar Debian descritos en: https://wiki.debian.org/RaspberryPi4#Using_EFI_Firmware_and_the_regular_Debian_Installer Y todo ha ido bien, excepto que no tengo puedo usar la GPU para ver vídeos con mpv y tampoco tengo sonido. Me interesa esto último, ¿alguien lo ha conseguido? Saludos.
Re: Regression in Radeon driver in latest Debian Stable kernel
On 17 May 2024 00:12 +0700, from maniku...@gmail.com (Max Nikulin): > Be realistic, to get the bug fixed, there should be affected persons > motivated enough to try vanilla kernel or even to build custom kernels with > provided patches. Developers time is limited and expensive resource. It may > be directed to fixing other bugs. If you can compare Debian and upstream > kernels you may get the issue fixed quicker. Direct communication with > driver developers may be more effective. Indeed; that's why I suggested trying the vanilla kernels of the same versions, compiled with the same options, and seeing if the behavior can be reproduced with those. If the same behavior as seen with the Debian-packaged kernels can be reproduced with the vanilla kernel, that would very strongly suggest that whatever this is is either (a) an upstream issue in the kernel, or (b) not a kernel issue at all. There's a reason why many upstream maintainers, when faced with a bug report for a downstream potentially modified version of their code, will start by saying "try our version". Adding to the "be realistic", if the issue was an obvious one, it likely never would have made it into a released kernel at all. So whatever this is about is unlikely to be obvious. Thus some detective work is most likely going to be needed; and unless a kernel developer can reproduce the problem on their own hardware, they'll probably have to ask you to try things out and report back; whether with debug logs, more detailed system information, or as Max mentioned building a kernel with a proposed fix to see what effect, if any, a proposed fix has on the problem. Also, especially if you start installing backports kernels as well, you may want to add a version pin to the kernel you currently have installed and which does not exhibit the problem to the same degree, to reduce the risk that it gets purged for being among the older ones you have installed. -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Re: Regression in Radeon driver in latest Debian Stable kernel
On 16/05/2024 22:53, piorunz wrote: https://bugzilla.kernel.org/ will they be interested in Debian specific error? I don't use vanilla kernel so maybe it's Debian only problem. If you *find* a similar report there then it is likely an upstream issue. (Developers of specific driver may use another bug tracker.) Do you have a recipe how to trigger the bug? Otherwise it may be much harder to fix it. Be realistic, to get the bug fixed, there should be affected persons motivated enough to try vanilla kernel or even to build custom kernels with provided patches. Developers time is limited and expensive resource. It may be directed to fixing other bugs. If you can compare Debian and upstream kernels you may get the issue fixed quicker. Direct communication with driver developers may be more effective.
Re: How to create a custom Debian ISO
Hi, Aditya Garg wrote: > This one is gonna be interesting. > Wish me luck. Fingers are crossed ... (But everything in the procedure is supposed to be deterministic. So there is few room for luck, good or bad. We rather have to navigate the chaos.) Have a nice day :) Thomas
Re: How to create a custom Debian ISO
Well I'm used to unsquashfs, chroot, squashfs and repack the iso. This one is gonna be interesting. Wish me luck. > On 16 May 2024, at 9:42 PM, Thomas Schmitt wrote: > > Hi, > > to...@tuxteam.de wrote: >> Not the OP, but thanks, Thomas. > > Well, ISO 9660 is known to be my hobby. So i can hardly resist trying > to acquire new users for xorriso. > > > Have a nice day :) > > Thomas >
Re: How to create a custom Debian ISO
Hi, to...@tuxteam.de wrote: > Not the OP, but thanks, Thomas. Well, ISO 9660 is known to be my hobby. So i can hardly resist trying to acquire new users for xorriso. Have a nice day :) Thomas
Re: Regression in Radeon driver in latest Debian Stable kernel
On 16/05/2024 12:35, Max Nikulin wrote: On 16/05/2024 17:35, piorunz wrote: As much as I would like to try vanilla kernel, I don't want to break my system. I use Debian Stable, don't know if things would just work with vanilla kernel. You may try bookworm-backports kernel 6.6.13+bpo-amd64 You may check https://bugzilla.kernel.org/ for reports similar to your one. Oh that's great solution, I will try that without risk of breaking my system, as I always can select previous kernel in the menu, thank you. https://bugzilla.kernel.org/ will they be interested in Debian specific error? I don't use vanilla kernel so maybe it's Debian only problem. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: How to create a custom Debian ISO
On Thu, May 16, 2024 at 05:20:40PM +0200, Thomas Schmitt wrote: > Hi, > > Aditya Garg wrote: > > I would prefer making the ISO as similar to the official Debian ISO and just > > replace the Debian kernel with the customised kernel. > > In that case, i'd go along [...] Not the OP, but thanks, Thomas. Your posts are always a trove. And pleasant, on top! Cheers -- t signature.asc Description: PGP signature
Re: How to create a custom Debian ISO
Hi, Aditya Garg wrote: > I would prefer making the ISO as similar to the official Debian ISO and just > replace the Debian kernel with the customised kernel. In that case, i'd go along https://wiki.debian.org/RepackBootableISO Either by using the xorrisofs options in /.disk/mkisofs of the ISO : https://wiki.debian.org/RepackBootableISO#Learn_about_the_actually_used_ISO_production_command or by relying on the capability of xorriso to determine the commands which will reproduce the boot equipmemt of the loaded ISO : https://wiki.debian.org/RepackBootableISO#In_xorriso_load_ISO_tree_and_write_modified_new_ISO If you need help with finding the appropriate xorriso commands, ask me in private or in public at bug-xorr...@gnu.org . What remains is to find out whether this works out of the box or whether the kernel has to be announced in some files of the ISO or even cryptographically signed in some way. -- Just in case your adventure goes beyond replacing the kernel and possibly the boot loader menu files, i warn of a bug in xorriso-1.5.6 and older: Don't overwrite the El Torito boot image files in a xorriso run that uses -boot_image "any" "replay" The boot image files in Debian amd64 ISOs are /isolinux/isolinux.bin and /boot/grub/efi.img . If you need to replace them, then we have to talk. Have a nice day :) Thomas
Re: How to create a custom Debian ISO
Well it's indeed not as easy as I thought as far as Debian ISOs are concerned. I'll try to be more precise. I am a maintainer for Ubuntu on Linux on T2 Macs project: https://t2linux.org/. We work to modify ISOs of commonly used distros by adding a custom kernel with drivers for T2 Macs and provide to the users. There has been a demand for Debian for a long time and I wish to provide the ISOs for the same. I would prefer making the ISO as similar to the official Debian ISO and just replace the Debian kernel with the customised kernel. I've already set up an apt repo which hosts the kernels over here: https://github.com/AdityaGarg8/t2-ubuntu-repo I'll be thankful if I get the best possible option. On 11 May 2024, at 8:33 PM, Thomas Schmitt wrote: Hi, Aditya Garg wrote to debian-devel: I wanted to create a custom ISO of Debian, with the following customisations: 1. I want to add a custom kernel that supports my Hardware. 2. I want to add my own Apt repo which hosts various software packages to support my hardware. I am not able to get any good documentation for the same. Please help. Marvin Renich wrote: The package live-build from the Debian Live project might help you do what you want. Indeed the live-build package seems to be in use outside Debian's own ISO production. Mailing list is debian-l...@lists.debian.org There exists a manual https://live-team.pages.debian.net/live-manual/html/live-manual/index.en.html Installation ISOs are made by package debian-cd, of which i am not aware that it would have have users outside the official ISO production.i Mailing list is debian...@lists.debian.org Your impression about lack of documentation is not wrong as far as this project is concerned. :)) Nevertheless the production step of packing up the ISO from a prepared file tree is documented together with methods to use a Debian installation ISO as base for the preparation: https://wiki.debian.org/RepackBootableISO Packages may probably be added at the appropriate place in the directory tree under /pool. (Managing a Debian repo is not my turf. Sorry for being vague here.) Changing the content of a Debian ISO might need some follow-up work in administrative files of the ISO. When merging Debian ISOs, my script https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos manipulates: /README.txt /dists/*/Release and merges the files listed in /dists/*/Release. You would have to explore whether these files are affected by your changes. Have a nice day :) Thomas
Re: Regression in Radeon driver in latest Debian Stable kernel
On 16/05/2024 17:35, piorunz wrote: As much as I would like to try vanilla kernel, I don't want to break my system. I use Debian Stable, don't know if things would just work with vanilla kernel. You may try bookworm-backports kernel 6.6.13+bpo-amd64 You may check https://bugzilla.kernel.org/ for reports similar to your one.
Re: Regression in Radeon driver in latest Debian Stable kernel
On 15/05/2024 20:55, Michael Kjörling wrote: You made this bug report less than 48 hours ago. While I can certainly understand that you would like to see it fixed, that's not an inordinate amount of time to wait. What probably _would_ be helpful is to see whether you can recreate the same scenario with the vanilla kernel.org kernels of the same versions; confirming that the issue exists with the vanilla 6.1.90 kernel _and_ that the issue goes away when booting the vanilla kernel of whatever exact version your earlier package is (I'm guessing 6.1.85), both when built with the same configuration options as the kernels shipped by Debian. That would confirm whether what you are seeing is something somehow introduced by Debian, or an upstream bug. Thank you for your reply, I appreciate it. I found out that this error happened on previous version of the kernel as well, just found it in the logs. So, it's not an immediate regression in the latest version of the kernel in Debian. Maybe it's deeper than that. That lowers the possibility that this is the most recent update which brought this problem. I sent latest update to the bug report, I will wait for any reply from developer but no rush, of course. As much as I would like to try vanilla kernel, I don't want to break my system. I use Debian Stable, don't know if things would just work with vanilla kernel. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: DNI electrónico en Debian
Estoy usando el típico Sveon que se muestra en la lista. Yo también lo uso como método de autenticación al sistema mediante pam_pkcs11. El Fri, 3 May 2024 19:56:51 +0200 Camaleón va escriure el següent: > El 2024-05-03 a las 09:57 -0600, Alejandro G. Sanchez Martinez > escribió: > > > En 02/05/24 01:41, Listas escribió: > > > El jue, 02-05-2024 a las 09:10 +0200, Camaleón escribió: > > > > > > > > Quienes usáis un lector autónomo y os funciona bien, mejor si > > > > decís marca, modelo (chipset) y tipo de conexión, seguro que > > > > resulta de utilidad para quien pregunta y para futuros lectores > > > > de este hilo :-) > > > En concreto en mi caso es > > > > > > lector USB Alcor Micro AU9540. > > > > > > Pero cualquier lector que cumpla con la especificación CCID > > > debería valer, básicamente todos los que se venden a día de hoy. > > > > > > Una lista de equipos soportados: > > > https://ccid.apdu.fr/ccid/section.html > > > > > > Info de opensc: > > > https://github.com/OpenSC/OpenSC/wiki/Smart-card-readers-%28Linux-and-Mac-OS-X%29 > > > > > > La especificación CCID: > > > https://www.usb.org/sites/default/files/DWG_Smart-Card_CCID_Rev110.pdf > > > > > > Un saludo > > > > > > > > Para lso que estasmo fuera de España si nos pudieran dar > > informaci+on de para que lo utilizan o cuales serían su > > funcuionalidad se lo agradeceriamos > > En España concretamente¹ es equivalente a la firma manuscrita, con lo > que ello conlleva a efectos legales, jurídicos, administrativos y de > todo tipo. > > Tanto el DNI electrónico (en soporte material de tarjeta física que > integra un certificado digital) como el certificado electrónico > cualificado (certificado en soporte software, es un archivo > informático) se usan para identificarte/acreditarte ante cualquier > instancia o entidad público y/o privada (gobierno, administraciones > locales, empresas, contratos privados, etc...). > > Realmente útil tanto para personas físicas como para personas > jurídicas (empresas o sus representantes). > > ¹Su uso es bastante desigual en otros países de la UE/EEE/Suiza, > siendo Reino Unido caso aparte donde apenas se usa, al menos según mi > experiencia personal. > > Saludos, >
Re: Regression in Radeon driver in latest Debian Stable kernel
On 15 May 2024 20:40 +0100, from pior...@gmx.com (piorunz): > I have reported a regression in latest Linux kernel in Debian Stable: > > segfault at amdgpu_dm_atomic_commit_tail > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071080 You made this bug report less than 48 hours ago. While I can certainly understand that you would like to see it fixed, that's not an inordinate amount of time to wait. What probably _would_ be helpful is to see whether you can recreate the same scenario with the vanilla kernel.org kernels of the same versions; confirming that the issue exists with the vanilla 6.1.90 kernel _and_ that the issue goes away when booting the vanilla kernel of whatever exact version your earlier package is (I'm guessing 6.1.85), both when built with the same configuration options as the kernels shipped by Debian. That would confirm whether what you are seeing is something somehow introduced by Debian, or an upstream bug. -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Regression in Radeon driver in latest Debian Stable kernel
Hello, I have reported a regression in latest Linux kernel in Debian Stable: segfault at amdgpu_dm_atomic_commit_tail https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071080 It throws a lot of errors related to AMD GPU every day. I also experienced full desktop hang, where I had to restart my computer: https://bugs.kde.org/show_bug.cgi?id=486970 This happens on 6.1.0-21-amd64. Booting previous version 6.1.0-20-amd64 solves all problems. Can anyone help me with getting attention from some developers? KDE dev said this is downstream, not KDE problem. Debian bug reported, but no reply from anyone yet. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Serial Connection in Debian 9 Moxa Device
Hello Debian Team, We are using Linux Debain 9 in our moxa devices. we are connected in a network where we connect with our moxa device via ssh and run the commands with Gauge ip and port and get Data. Now I'm Facing issue from 2, 3 weeks to connect the moxa using ssh and then connect to the serial port and get data as i getting in Telnet. I need Your Help in this Scenario to get the data when i connect through serial cable. please Let me know ASAP. Thanks Faisal
Re: Probléme de clés et dépôts Debian
Le dimanche 12 mai 2024 à 15:23 +0200, didier gaumet a écrit : > > donc en gros je pense que tu n'as rien à faire, qu'avec le temps, les > paquets Debian le nécessitant seront modifiés et que les dépôts le > nécessitant seront signés par des clés plus robustes (algo' plus > fiable) > > Bon, je vais patienter un peu, car pour l'heure ça me donne un accès aux dépôts. Nous verrons par la suite. Merci de vos réponses en tous cas. Krystof26
Re: Probléme de clés et dépôts Debian
Bonjour, - ce sont seulement des avertissements (W) pas des erreurs (E) - tu es dans un mélange stable et testing - par définition testing c'est fait pour tester donc tu te retrouves avec des trucs pas encore bien finalisés (on peut utiliser testing, unstable et experimental, faut juste accepter qu'on doit pouvoir se débrouiller seul: Debian ne met pas ça à disposition pour utiliser mais pour tester dans le but que Debian stable soit... stable) mon impression (je peux me tromper...) est que tout ça provient d'un travail de sécurisation en cours pour s'assurer que les dépôts lors des mises-à-jour sont bien ceux qu'ils prétendent être. Cela semble nécessiter qu'ils soient signés par des algorithmes sûrs, et que apt comme gpg permettent de s'assurer que l'algorithme utilisé est sûr. Et là on dirait que apt a déjà été modifié pour verifier ça mais que gpg ne sait pas quoi en faire (soit gpg devra être modifié soit il sait déjà traiter ça mais il reçoit des options erronées de apt qui devra être modifié (peut-être seulement les valeurs par défaut)) Ubuntu a un petit topo là-dessus et il est probable que c'est la même chose ici (particulièrement en bas de page, les trucs sur l'algo' dans apt.conf): https://discourse.ubuntu.com/t/new-requirements-for-apt-repository-signing-in-24-04/42854 donc en gros je pense que tu n'as rien à faire, qu'avec le temps, les paquets Debian le nécessitant seront modifiés et que les dépôts le nécessitant seront signés par des clés plus robustes (algo' plus fiable)
Re: Probléme de clés et dépôts Debian
Bonjour, As-tu essayé de nettoyer la bibliothèque et les caches APT ? Cel force APT à reconstituer sa base. # \rm -Rf /var/lib/apt* /var/cache/apt* Recréer la racine « aptitude : # mkdir /var/lib/aptitude et relancer une mise à jour : # aptitude update > Le 12 mai 2024 à 12:52, Christophe Musseau a écrit : > > Bonjour la liste, > > Ces derniers temps pas mal de mise à jour, et notamment avec Testing. > Consécutivement à une de ces récentes mise à jour, quand je lance # > aptitude update, j'ai droit aux messages suivants. Cela ne m'empêche > pas d'effectuer les mises à jour, mais je ne comprends pas et n'arrive > pas à résoudre ce problème avec les clés. > > Messages : > W: > http://debug.mirrors.debian.org/debian-debug/dists/testing-debug/InRelease > : Unknown response from gpgv to --assert-pubkey-algo check: gpgv: > error: Error parsing command-line arguments > W: > http://security.debian.org/debian-security/dists/bookworm-security/InRelease > : Unknown response from gpgv to --assert-pubkey-algo check: gpgv: > error: Error parsing command-line arguments > W: https://dl.google.com/linux/chrome/deb/dists/stable/InRelease: > Unknown response from gpgv to --assert-pubkey-algo check: gpgv: > error: Error parsing command-line arguments > W: http://deb.debian.org/debian/dists/bookworm/InRelease: Unknown > response from gpgv to --assert-pubkey-algo check: gpgv: error: Error > parsing command-line arguments > W: http://deb.debian.org/debian/dists/bookworm-updates/InRelease: > Unknown response from gpgv to --assert-pubkey-algo check: gpgv: > error: Error parsing command-line arguments > W: http://deb.debian.org/debian/dists/testing/InRelease: Unknown > response from gpgv to --assert-pubkey-algo check: gpgv: error: Error > parsing command-line arguments > W: > http://deb.debian.org/debian-security/dists/testing-security/updates/InRelease > : Unknown response from gpgv to --assert-pubkey-algo check: gpgv: > error: Error parsing command-line arguments > W: http://deb.debian.org/debian/dists/testing-updates/InRelease: > Unknown response from gpgv to --assert-pubkey-algo check: gpgv: > error: Error parsing command-line arguments > > Si quelqu'un a une solution à me proposer. > Merci par avance > > Krystof26 > -- Pierre Malard Responsable architectures système CDS DINAMIS/THEIA Montpellier IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France Tél : +33 626 89 22 68 «Il vaut mieux passer à La Poste qu’à la postérité» Alphonse Allais |\ _,,,---,,_ /,`.-'`'-. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- signature.asc Description: Message signed with OpenPGP
Probléme de clés et dépôts Debian
Bonjour la liste, Ces derniers temps pas mal de mise à jour, et notamment avec Testing. Consécutivement à une de ces récentes mise à jour, quand je lance # aptitude update, j'ai droit aux messages suivants. Cela ne m'empêche pas d'effectuer les mises à jour, mais je ne comprends pas et n'arrive pas à résoudre ce problème avec les clés. Messages : W: http://debug.mirrors.debian.org/debian-debug/dists/testing-debug/InRelease : Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments W: http://security.debian.org/debian-security/dists/bookworm-security/InRelease : Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments W: https://dl.google.com/linux/chrome/deb/dists/stable/InRelease: Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments W: http://deb.debian.org/debian/dists/bookworm/InRelease: Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments W: http://deb.debian.org/debian/dists/bookworm-updates/InRelease: Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments W: http://deb.debian.org/debian/dists/testing/InRelease: Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments W: http://deb.debian.org/debian-security/dists/testing-security/updates/InRelease : Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments W: http://deb.debian.org/debian/dists/testing-updates/InRelease: Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments Si quelqu'un a une solution à me proposer. Merci par avance Krystof26
Re: How to create a custom Debian ISO
Hi, Aditya Garg wrote to debian-devel: > > I wanted to create a custom ISO of Debian, with the following > > customisations: > > 1. I want to add a custom kernel that supports my Hardware. > > 2. I want to add my own Apt repo which hosts various software packages to support my hardware. > > I am not able to get any good documentation for the same. Please help. Marvin Renich wrote: > The package live-build from the Debian Live project might help you do > what you want. Indeed the live-build package seems to be in use outside Debian's own ISO production. Mailing list is debian-l...@lists.debian.org There exists a manual https://live-team.pages.debian.net/live-manual/html/live-manual/index.en.html Installation ISOs are made by package debian-cd, of which i am not aware that it would have have users outside the official ISO production.i Mailing list is debian...@lists.debian.org Your impression about lack of documentation is not wrong as far as this project is concerned. :)) Nevertheless the production step of packing up the ISO from a prepared file tree is documented together with methods to use a Debian installation ISO as base for the preparation: https://wiki.debian.org/RepackBootableISO Packages may probably be added at the appropriate place in the directory tree under /pool. (Managing a Debian repo is not my turf. Sorry for being vague here.) Changing the content of a Debian ISO might need some follow-up work in administrative files of the ISO. When merging Debian ISOs, my script https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos manipulates: /README.txt /dists/*/Release and merges the files listed in /dists/*/Release. You would have to explore whether these files are affected by your changes. Have a nice day :) Thomas
Re: How to create a custom Debian ISO
* Aditya Garg [240511 05:15]: > Hello > > I wanted to create a custom ISO of Debian, with the following customisations: > > 1. I want to add a custom kernel that supports my Hardware. > 2. I want to add my own Apt repo which hosts various software packages to > support my hardware. > > I am not able to get any good documentation for the same. Please help. [Redirecting to debian-user, dropping -project, M-F-T set to debian-user only] First, please don't double-post the same message within a few minutes. Give your message at least a half hour to show up before you decide it wasn't received. Second, neither debian-devel nor debian-project are appropriate lists for this question. You should use debian-user@lists.debian.org or some other user-oriented forum. Also, posting a question to multiple lists at once (called cross-posting) is considered rude in most situations. To give a possible answer to your question, look at the Debian Live project: https://www.debian.org/devel/debian-live/ The package live-build from the Debian Live project might help you do what you want. ...Marvin
Re: debian bookworm japanese kana input disabled
Hi Updated and upgraded,autoremoved. This matter has been fixed. The problem is currently resolved. Nice follow up! I appreciate it. Best wishes -- Moliharu Tomizawa
Re: Debian no es tan fácil como dicen
On Fri, May 10, 2024 at 11:45:25AM -0400, Carlos Garcia Elmis wrote: > Hola equipo Debian, soy nuevo en Linux/GNU y en si no es una correo de > queja si no de ampliar Debian, no solo instale Debian si no también un > montón de sus derivados, y en todos menos en una fue que me facilito la > vida y estoy hablando de deepin: > ¿cuales son las ventajas de deepin sobre Debian? > R: en deepin pude desinstalar programas desde su menu inicio, también pude > restaurar el sistema por último y que es lo primero que se hace es que la > instalación del SO de deepin es súper Fasil, mucho mas que calamares > Disculpe: debo decirte que se suele hablar ingles in esta lista. Puede ser que debian-user-spanish seria mejor. Como dice el FAQ mensual - Otras distribuciones de Linux son "off-topic" por aqui asi tu mensaje no valga mucho. Apologies: I have to tell you that we normally speak English in this list It might be that debian-user-spanish would be better. As it says in the monthly FAQ: Other Linux distributions are off topic here: your message is not worth as much here. Saludos / with every good wish, Andy Cater [amaca...@debian.org] > Pero en este caso vengo a hablarles de los dos primeros puntos de deepin > sobre Debian > 1) Un usuario nuevo como yo al pasarse a Debian necesita probar nuevas > aplicaciones para dejar atrás las que ya uso, en deepin instalaba y > desinstala las app sin problema, en Debian no, LibreOffice (sudo apt > remover install), GIMP (sudo apt remover GIMP), etc, en deepin clic en menú > inicio, clic derecho sobre la app y desinstalar, yo me pregunto cómo > quieren que alguien nuevo se quede en Debian si al mismo tiempo que tenemos > que probar aplicaciones por qué es un SO diferente no podemos desinstalar > aplicaciones tan fácil como la instalamos con gdebi > Nota:para esta parte solo incluye paquetes nativos ya que si hablamos de > flatpak, snapd y appimage es diferente sin embargo todos terminamos > evitando estas alternativa por que aumenta el consumo de las aplicaciones > además de ser contenedores y no ajustarse a la configuración del sistema > por tal motivo > > 2)Deepin tiene la posibilidad de restaurar el sistema dando una clara > ventaja de que un nuevo usuario que hizo y deshizo en deepin las veces que > quiso le da la oportunidad de volver a configurar de nuevo una nueva > cuenta, colocar el idioma, sin estar particionado otra vez el disco o > reinstalando el sistema desde cero, la gran desventaja de deepin aquí es > que si hago una partición manual pierdo esta excelente configuración de > deepin, por tal motivo estuve un buen tiempo en deepin > > Sin embargo no todo es bello en deepin, siendo que ellos no tienen una > interfaz única y bella gracias a deepin deskop, no por eso la instale y me > quedé bastante tiempo con ella si no por esa tres características que > mencioné atrás, pero vamos a la desventaja en deepin > > Como ya sabemos ya hablamos de los contenedores que habitualmente todos > evitamos por el uso mayor de recursos a comparación de un app nativo, pero > no siempre podemos evitarlos sobre todo con app que no podemos encontrar > nativas para Debian por tal motivo he aquí la única ventaja y por su puesto > gran ventaja de Debian sobre deepin, ya se dije que no era buena idea pero > también es inevitable sus usos, y claro hablo de flatpak, snap y appimage > que si bien cualquiera podemos utilizar en deepin pero perdiendo la > facilidad de uso desde la tienda como Debian nos proporciona estos paquetes > > Otro punto es que los repositorios Debian están disponibles para todo el > mundo y son veloces en cambio deepin no tienen esa gran ventaja > > Resumiendo > 1) desinstalar software > 2)restablecer sistema > 3)instalar sistema > > Son puntos que para todo usuario nuevo es importante, deepin ha demostrado > que es posible tener un SO completo y es muy importante saber que deepin > busca independizarse de Debian así creando un deepin independiente > > Espero no haber molestado un saludo cordial a el gran equipo Debian, > bendiciones
Re: Debian no es tan fácil como dicen
On Fri, May 10, 2024 at 11:45:25AM -0400, Carlos Garcia Elmis wrote: > Hola equipo Debian, soy nuevo en Linux/GNU y en si no es una correo de > queja si no de ampliar Debian, no solo instale Debian si no también un > montón de sus derivados, y en todos menos en una fue que me facilito la > vida y estoy hablando de deepin: [...] ¡Hola, Carlos! - No hay equipo aquí: esta es la lista de los usuarios - Si quieres hablar con usuarios en castellano, por aquí hay una lista en este lenguaje: https://en.wikipedia.org/wiki/Variant_Call_Format Quizás sea más apropiada para ti (la mayoría de la gente aquí no entiende castellano) - Me alegro mucho que te guste Deepin; sin embargo, aquì encontrarás gente que usa Debian y lo prefiere así (yo soy uno de esos). Tengo dudas de que una misiva como la tuya sea ùtil en este caso. Saludos -- tomás signature.asc Description: PGP signature
Debian no es tan fácil como dicen
Hola equipo Debian, soy nuevo en Linux/GNU y en si no es una correo de queja si no de ampliar Debian, no solo instale Debian si no también un montón de sus derivados, y en todos menos en una fue que me facilito la vida y estoy hablando de deepin: ¿cuales son las ventajas de deepin sobre Debian? R: en deepin pude desinstalar programas desde su menu inicio, también pude restaurar el sistema por último y que es lo primero que se hace es que la instalación del SO de deepin es súper Fasil, mucho mas que calamares Pero en este caso vengo a hablarles de los dos primeros puntos de deepin sobre Debian 1) Un usuario nuevo como yo al pasarse a Debian necesita probar nuevas aplicaciones para dejar atrás las que ya uso, en deepin instalaba y desinstala las app sin problema, en Debian no, LibreOffice (sudo apt remover install), GIMP (sudo apt remover GIMP), etc, en deepin clic en menú inicio, clic derecho sobre la app y desinstalar, yo me pregunto cómo quieren que alguien nuevo se quede en Debian si al mismo tiempo que tenemos que probar aplicaciones por qué es un SO diferente no podemos desinstalar aplicaciones tan fácil como la instalamos con gdebi Nota:para esta parte solo incluye paquetes nativos ya que si hablamos de flatpak, snapd y appimage es diferente sin embargo todos terminamos evitando estas alternativa por que aumenta el consumo de las aplicaciones además de ser contenedores y no ajustarse a la configuración del sistema por tal motivo 2)Deepin tiene la posibilidad de restaurar el sistema dando una clara ventaja de que un nuevo usuario que hizo y deshizo en deepin las veces que quiso le da la oportunidad de volver a configurar de nuevo una nueva cuenta, colocar el idioma, sin estar particionado otra vez el disco o reinstalando el sistema desde cero, la gran desventaja de deepin aquí es que si hago una partición manual pierdo esta excelente configuración de deepin, por tal motivo estuve un buen tiempo en deepin Sin embargo no todo es bello en deepin, siendo que ellos no tienen una interfaz única y bella gracias a deepin deskop, no por eso la instale y me quedé bastante tiempo con ella si no por esa tres características que mencioné atrás, pero vamos a la desventaja en deepin Como ya sabemos ya hablamos de los contenedores que habitualmente todos evitamos por el uso mayor de recursos a comparación de un app nativo, pero no siempre podemos evitarlos sobre todo con app que no podemos encontrar nativas para Debian por tal motivo he aquí la única ventaja y por su puesto gran ventaja de Debian sobre deepin, ya se dije que no era buena idea pero también es inevitable sus usos, y claro hablo de flatpak, snap y appimage que si bien cualquiera podemos utilizar en deepin pero perdiendo la facilidad de uso desde la tienda como Debian nos proporciona estos paquetes Otro punto es que los repositorios Debian están disponibles para todo el mundo y son veloces en cambio deepin no tienen esa gran ventaja Resumiendo 1) desinstalar software 2)restablecer sistema 3)instalar sistema Son puntos que para todo usuario nuevo es importante, deepin ha demostrado que es posible tener un SO completo y es muy importante saber que deepin busca independizarse de Debian así creando un deepin independiente Espero no haber molestado un saludo cordial a el gran equipo Debian, bendiciones
Re: Adding package to Debian Distro
On Thu 09 May 2024 at 16:24:55 (-), Curt wrote:
> On 2024-05-09, Charles Curley wrote:
> > On Thu, 9 May 2024 14:09:52 - (UTC) Curt wrote:
> >
> >> I don't think there is a process by which you could add closed-source
> >> IBM software to a bona fide Debian depository, even the non-free one,
> >> which only seems to contain firmware and drivers for closed-sourced
> >> *hardware*.
> >
> > Isn't that what the non-free archive is for?
> > https://www.debian.org/doc/debian-policy/ch-archive#s-non-free
>
> Maybe you're right. I can't seem to find a comprehensive list of
> non-free packages,
Would APT's lists do, assuming you have non-free in your sources.list?
/var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_non-free_{binary-amd64_Packages,i18n_Translation-en}
(Adjust for source address, distribution, architecture, language, etc.)
> nor anything equivalent to this intricate IBM
> software.
No idea. Cluster Technology is beyond my pay-grade.
> I mean, if non-free means: "anything at all that can be
> reverse-engineered by our software teams," then I've misunderstood its
> meaning and purpose (which is perfectly possible).
Well, no; you could have software that's gratis, open-source,
and redistributable, but if it couldn't be used, say, for
commercial purposes, that would have to go into Debian's
non-free archive rather than the main distribution.
It has nothing to do with reverse engineering per se.
Cheers,
David.
Re: Adding package to Debian Distro
On 2024-05-09, Charles Curley wrote: > On Thu, 9 May 2024 14:09:52 - (UTC) > Curt wrote: > >> I don't think there is a process by which you could add closed-source >> IBM software to a bona fide Debian depository, even the non-free one, >> which only seems to contain firmware and drivers for closed-sourced >> *hardware*. > > Isn't that what the non-free archive is for? > https://www.debian.org/doc/debian-policy/ch-archive#s-non-free > Maybe you're right. I can't seem to find a comprehensive list of non-free packages, nor anything equivalent to this intricate IBM software. I mean, if non-free means: "anything at all that can be reverse-engineered by our software teams," then I've misunderstood its meaning and purpose (which is perfectly possible).
Re: Adding package to Debian Distro
On Thu, 9 May 2024 14:09:52 - (UTC) Curt wrote: > I don't think there is a process by which you could add closed-source > IBM software to a bona fide Debian depository, even the non-free one, > which only seems to contain firmware and drivers for closed-sourced > *hardware*. Isn't that what the non-free archive is for? https://www.debian.org/doc/debian-policy/ch-archive#s-non-free -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Adding package to Debian Distro
On 2024-05-09, kiruthikaanbusuresh wrote: > > Hi Debian Team, > There is a package by name rsct which is specific to IBM. I would like to > know the process to get this added to the Debian Distro. Should I have > to get sponsorship for getting it added to Debian ? Seems IBM only provides a Ubuntu package. https://www.ibm.com/docs/en/rsct/3.2?topic=installation-verifying-linux-nodes Whether that package would work on your current Debian installation is anybody's guess (I am completely ignorant in these matters). I don't think there is a process by which you could add closed-source IBM software to a bona fide Debian depository, even the non-free one, which only seems to contain firmware and drivers for closed-sourced *hardware*. I could be wrong, though.
Re: Adding package to Debian Distro
On Thu, May 09, 2024 at 06:12:35PM +0530, kiruthikaanbusuresh wrote: > Hi Debian Team, > There is a package by name rsct which is specific to IBM. I would like to > know the process to get this added to the Debian Distro. Start with sharing more information about it. * Tell what "rsct" does (to get more stakeholders) * Where to find the source > Should I have to get sponsorship for getting it added to Debian ? You haven't told what the author[1] of rsct feels about that wish. > Thanks and Regards, > Kiruthika. NV Groeten Geert Stappers Footnote [1]: Copyrightholder -- Silence is hard to parse
Re: Adding package to Debian Distro
Hi, kiruthikaanbusuresh wrote: > Hi Debian Team, Standard disclaimer: We are the users. A team only by coincidence. (And you seem not to be subscribed to the mailing list. Thus i CC: your mail address.) > There is a package by name rsct which is specific to IBM. I > would like to know the process to get this added to the Debian Distro. If it complies to https://wiki.debian.org/DebianFreeSoftwareGuidelines and is of some general use, then have a look at https://wiki.debian.org/RFP > Should I have to get sponsorship for getting it added to Debian ? If you want to contribute own work to this packaging endeavor: Yes. It will probably increase your chances for success. See https://mentors.debian.net/ https://wiki.debian.org/ITP Have a nice day :) Thomas
Re: debian bookworm japanese kana input disabled
On Donnerstag, 9. Mai 2024 08:48:03 -04 Brad Rogers wrote: > On Thu, 9 May 2024 10:06:29 + > Michael Kjörling <2695bd53d...@ewoof.net> wrote: > > Hello Michael, > > >However, I seem to have had a similar issue even after upgrading to > >the first regression-fixed glib2.0 packages on Bookworm. > >Specifically, dead keys no longer working with the Swedish keyboard > >layout, and instead acting as though I didn't press any key at all. > > Is it possible that, without at least logging out and back in, the > broken version of the library is still in use? Hi Michael and hello 冨澤守治[1] I don't know if it was related but with the same Debian Sid upgrade Firefox (and only Firefox) lost the ability to enter äöüáéí€ß ... that is it ignored anything which was not pure ASCII, however entering the accented characters in a terminal or other applications (here KDE) still worked. After today's upgrade everything was back to normal but I *had* to reboot. So logging out and back in again might work although I suspect that at least restarting the X server will be necessary. I didn't try it because I had to reboot anyway. All the best to you all -- Eike Lantzsch KY4PZ / ZP5CGE [1] mailto: %3D%3Futf-8%3FB%3F5Yao5r6k5a6I5rK7%3F%3D%20%3Cmolitz%40coffee.ocn.ne.jp%3E
Adding package to Debian Distro
Hi Debian Team, There is a package by name rsct which is specific to IBM. I would like to know the process to get this added to the Debian Distro. Should I have to get sponsorship for getting it added to Debian ? Thanks and Regards, Kiruthika. NV
Re: debian bookworm japanese kana input disabled
On Thu, 9 May 2024 10:06:29 +
Michael Kjörling <2695bd53d...@ewoof.net> wrote:
Hello Michael,
>However, I seem to have had a similar issue even after upgrading to
>the first regression-fixed glib2.0 packages on Bookworm. Specifically,
>dead keys no longer working with the Swedish keyboard layout, and
>instead acting as though I didn't press any key at all.
Is it possible that, without at least logging out and back in, the
broken version of the library is still in use?
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
Words as weapons, sharper than knives
Devil Inside - INXS
pgpLB3jEQkwp1.pgp
Description: OpenPGP digital signature
Re: DNI electrónico en Debian
No tuve que tocar ni configurar nada, que yo recuerde. Un saludo. El jue, 9 may 2024, 12:36, Borja Gutiérrez Fernández escribió: > Hola, > > Perdón por el cambio de tema, actualizaste de 11 a 12 sin ningún problema? > > > Gracias. > Borja Gutiérrez Fernández. > El 1/5/24 a las 20:22, Raúl Armenta escribió: > > Yo lo hago. Instalé en Debian 11 y se mantiene todo correcto después de > que actualicé al 12. > > Configurado sobre Firefox. > > Único inconveniente que no he sabido configurar, firmar externamente con > aplicaciones de cada organismo. No encuentra el almacén de certificados de > Firefox. Tengo que guardar mi certificado en disco. > > También utilizo con lector de DNI electrónico. > > Un saludete > > El mié, 1 may 2024, 20:16, Luis Muñoz Fuente < > luis.munoz@juntadeandalucia.es> escribió: > >> Hola a todos/as: >> >> ¿Alguien se identifica o firma con el DNI electrónico en Debian? >> Habitualmente uso el certificado digital de la FNMT pero estoy pensando >> comprar un lector de DNI por si me falla la firma con el certificado de la >> FNMT. >> >> Saludos >> >
Re: DNI electrónico en Debian
Hola, Perdón por el cambio de tema, actualizaste de 11 a 12 sin ningún problema? Gracias. Borja Gutiérrez Fernández. El 1/5/24 a las 20:22, Raúl Armenta escribió: Yo lo hago. Instalé en Debian 11 y se mantiene todo correcto después de que actualicé al 12. Configurado sobre Firefox. Único inconveniente que no he sabido configurar, firmar externamente con aplicaciones de cada organismo. No encuentra el almacén de certificados de Firefox. Tengo que guardar mi certificado en disco. También utilizo con lector de DNI electrónico. Un saludete El mié, 1 may 2024, 20:16, Luis Muñoz Fuente escribió: Hola a todos/as: ¿Alguien se identifica o firma con el DNI electrónico en Debian? Habitualmente uso el certificado digital de la FNMT pero estoy pensando comprar un lector de DNI por si me falla la firma con el certificado de la FNMT. Saludos
Re: debian bookworm japanese kana input disabled
On 9 May 2024 09:14 +0200, from f.rou...@free.fr (Florent Rougon): >> Last night (JST) I did some apt update && apt upgade. >> But all of sudden I can't input kana and even print any editer or calc cell. >> (Roman alphabet has no problem on printing.) > > This may be due to a recent glib2.0 update: > > https://lists.debian.org/debian-security-announce/2024/msg00094.html That was my thought as well. > “The update for glib2.0 released as DSA 5682-1 caused a regression in > ibus affecting text entry with non-trivial input methods. Updated > glib2.0 packages are available to correct this issue.” > > Hopefully, you just need to update again. However, I seem to have had a similar issue even after upgrading to the first regression-fixed glib2.0 packages on Bookworm. Specifically, dead keys no longer working with the Swedish keyboard layout, and instead acting as though I didn't press any key at all. The key press did show up in xev: KeyPress event, serial 33, synthetic NO, window 0x2a1, root 0x6aa, subw 0x0, time 1153798, (397,298), root:(1268,818), state 0x10, keycode 35 (keysym 0xfe57, dead_diaeresis), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 33, synthetic NO, window 0x2a1, root 0x6aa, subw 0x0, time 1153862, (397,298), root:(1268,818), state 0x10, keycode 35 (keysym 0xfe57, dead_diaeresis), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False but despite my attempts nothing showed up in any input field; trying with both Xfce's Mousepad text editor, KeepassXC and gnome-terminal to cover various UI toolkits, with the same result everywhere. The combination of the key press showing up in xev and nothing showing up in any application I tried with running under X pointed strongly toward the input translation layer. However, another physical computer also running Bookworm which I upgraded to latest at around 09:40 May 9 UTC _didn't_ seem to have the same issue, despite being set up similarly. Turned out that there is _another_ upgrade to libglib2.0-0 and friends taking those packages to package version 2.74.6-2+deb12u2; after installing _that_ upgrade and rebooting, dead keys again seem to work normally. (It's entirely possible that the reboot wasn't needed, but as I had only just rebooted the system and so didn't have much of anything already open, it seemed an easy enough way to actually ensure that everything was running at the newly upgraded version.) So if you're still having the same issue, _try once more_ apt-get update && apt-get -u dist-upgrade; double-check that you get the +deb12u2 or newer glib package versions; and see if that fixes the problem before you poke around too much with the configuration (and risk breaking something else in the process). Then let us know whether you're still having the same issue or whether that resolved it. -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Re: debian bookworm japanese kana input disabled
Hi, Le 09/05/2024, 冨澤守治 a écrit: > Hellow! > > Thanks you for your supprting everyday. > > Last night (JST) I did some apt update && apt upgade. > But all of sudden I can't input kana and even print any editer or calc cell. > (Roman alphabet has no problem on printing.) This may be due to a recent glib2.0 update: https://lists.debian.org/debian-security-announce/2024/msg00094.html “The update for glib2.0 released as DSA 5682-1 caused a regression in ibus affecting text entry with non-trivial input methods. Updated glib2.0 packages are available to correct this issue.” Hopefully, you just need to update again. Regards -- Florent
Re: debian bookworm japanese kana input disabled
/var/log/apt/history will tell you what apt also has been showing you during that process. Never just mindlessly agree to what apt tells you it's about to do, especially pay attention to the app list for "remove" and "auto-remove". Things can always go wrong. So if apt told you it will remove some package for whatever reason that's needed for kana, it will have done so. So check the history and have a look at any packages from that timestamp that where set to be removed. Best Richard Am Do., 9. Mai 2024 um 03:45 Uhr schrieb 冨澤守治 : > Hellow! > > Thanks you for your supprting everyday. > > Last night (JST) I did some apt update && apt upgade. > But all of sudden I can't input kana and even print any editer or calc > cell. > (Roman alphabet has no problem on printing.) > > yours sincerely > > -- > Moriharu Tomizawa > >
Monthly FAQ for Debian-user mailing list [Modified 20240408]
Debian-user is a mailing list provided for support for Debian users, and to facilitate discussion on relevant topics. Codes of Conduct * The list is a Debian communication forum. As such, it is subject to both the Debian mailing list Code of Conduct and the main Debian Code of Conduct https://www.debian.org/MailingLists/#codeofconduct https://www.debian.org/code_of_conduct Guidelines for this list Some guidelines which may help explain how the list should work: Language * The language on this mailing list is English. There may be other mailing lists that are language-specific, for example, debian-user-french or debian-user-catalan * It is common for users to be redirected here from other lists, for example, from debian-project. It is also common for people to be posting here when English is not their primary language. Please be considerate. Answering questions and contributing to discussions constructively == * This is a fairly busy mailing list but even so you may have to wait some time for an answer - please be patient. * Help and advice on this list is provided by volunteers in their own time. It is common for there to be different opinions or answers provided. * It is not necessary to answer every post on the mailing list. * Be constructive in your responses. It may be that somebody else answers a question before you - if so, you should not reply simply in order to get the last word in, only reply if you can add useful information. Off-topic posts === * Please try to stay on topic. * Off-topic posts will happen occasionally as threads wander. Don't reply to them to make them carry on. * If you wish to introduce an off-topic subject that might be of interest to the wider list, start a new thread and preface the title with [OT]. * There is no debian-offtopic mailing list: please don't try to start one. Partisan topics and political arguments === * Arguments for the sake of it are not welcome here. * Partisan political / religious / cultural arguments do not belong here either. Debian's community is world wide; do not assume others will agree with your views or need to read them on a Debian list. Editing and answering mailing list posts * It is helpful to write meaningful subject lines. If you change subject or emphasis in mid-thread, please change the subject line on your email accordingly so that this can be clearly seen. For example: New question [WAS Old topic] * It may also be useful for someone to post a summary email from time to time to explain long threads. * Before posting, it may be useful to check your post for spelling mistakes and scan it for redundancy, duplicate words and redundancy. * Clear replies and a short mailing list thread are much easier to read and follow than long threads. * If you are replying to a post, please reply in-line if possible and cut out extra text that is not relevant to your point. Private replies and responding to posts off-list * Please post answers back to the list so others can benefit: private conversations don't benefit people who may only be following along on the list or reading the archives later. * We're only human: you may want to respond to someone off-list to make a point (or to wish them Happy Birthday / comment that you haven't seen them for a long time). We're also a community and the people you find on the list may become familiar friends BUT * Posting outside the list can be unhelpful: bad behaviour outside the lists can't easily be dealt with and will be invisible. You may inadvertently leak personal information by posting a private reply back to the list. If you *do* want to post outside the list - make it clear that you have done so at the top of the message. If someone replies to you privately and you think that this should go back to the list - ask them to post it to the list - do not just do so on their behalf without checking. I can't see what I want here - help me! === * It is often useful to look through the archives to see whether the issue you wish to raise or a similar issue has been raised before by someone else. The top level link to the archives of this list is at https://lists.debian.org/debian-user/ organised by year, then month. * Although there are only 20 or 30 regular contributors, there may be a couple of thousand readers in the background. Nobody is a mind reader, nobody can sit beside you. Please help by providing useful details if asked, especially which version of Debian you are running. I'm not using Debian but ... * Strictly, discussions of other distributions
debian bookworm japanese kana input disabled
Hellow! Thanks you for your supprting everyday. Last night (JST) I did some apt update && apt upgade. But all of sudden I can't input kana and even print any editer or calc cell. (Roman alphabet has no problem on printing.) yours sincerely -- Moriharu Tomizawa
Re: Problema de Thunderbird debian 11 con Zimbra
On Fri, Feb 17, 2023 at 1:36 AM Camaleón wrote: > > El 2023-02-16 a las 21:40 -0600, Roberto J. Blandino Cisneros escribió: > > > El 12/2/23 a las 13:04, Camaleón escribió: > > > El 2023-02-12 a las 12:05 -0600, Roberto J. Blandino Cisneros escribió: > > > > > > > El 12/2/23 a las 04:40, Camaleón escribió: > > > > > > Por mera curiosidad consulte las versiones de ambos clientes y vi > > > > > > que mi > > > > > > cliente de thunderbird tenía la version "102" proveída del > > > > > > repositorio de > > > > > > seguridad, y la otra aún tenía la versión "91" proveída del > > > > > > repositorio > > > > > > principal. > > > > > > > > > > > > Por lo tanto respalde la carpeta, desinstalé el paquete e instalé > > > > > > manualmente la versión "91" desde el repositorio excluyendo para > > > > > > thunderbird > > > > > > los demás repositorios, por medio de de una maquina virtual instalé > > > > > > la > > > > > > ultima versión de thunderbird para lograr abrir el backup y guardar > > > > > > todos a > > > > > > una carpeta local compartida en red, luego pase los correos al > > > > > > thunderbird > > > > > > con version "91" y listo. > > > > > > > > > > > > Para mi sorpresa con esta versión no me ha dado inconvenientes, he > > > > > > habilitado el debug en thunderbird y no he visto nada extraño en > > > > > > los logs > > > > > > más que errores de autenticación. > > > > > > > > > > > > ¿Alguien ha presentado ese problema? > > > > > (...) > > > > > > > > > > No uso Zimbra y tampoco sé qué servidor pop3/imap incluye pero si > > > > > tienes > > > > > acceso a los registros del servidor (Zimbra) y te dice que falla en la > > > > > autenticación del cliente, tanto en Outlook como en Thunderbird, quizá > > > > > se deba a algún problema de incompatibilidad con estos clientes. > > > > Zimbra hace uso de postfix es un set completo que combina, > > > > mysql+postfix+amavisd+clamav+ldap+dkim+dnscache+proxy+nginx y todo el > > > > set es > > > > completo para administrar el servicio, lógico que no es solo de > > > > instalar y > > > > listo, aunque funciona pero requiere algunos detalles para asegurarlo y > > > > protegerlo. > > > Sigo sin ver quién se encarga de la parte receptora (buzones) de los > > > correos > > > electrónicos... es decir, no veo un Dovecot, Cyrus, Courier-Imapd, por > > > poner > > > algunos ejemplos. > > > > Puedes leer el siguiente url: > > > > https://zimbra.github.io/zimbra-9/adminguide.html > > > > En la parte de "Produc Overview" > > > > El postfix es el que se encarga de administrar tanto el SMTP como el Popd y > > el imapd, > > (...) > > Postfix no puede encargarse de conexiones IMAP4/POP3, es un MTA. > > > Luego si sigues leyendo encontraras el flujo del correo. > > Ya lo veo... tienen algún servicio IMPAD integrado en la suite: Así es > > > https://zimbra.github.io/zimbra-9/adminguide.html#_imap > > IMAP > > Zimbra Collaboration has a built-in IMAP server which is installed by > default and is part of zimbra-mailboxd process (Zimbra Mailbox Server). > > > Pero no dice de qué servicio de trata. Qué poco me gustan estas > herramientas que pretenden encargarse de todo y a la vez, le ocultan > todo al administrador (todo para el pueblo pero sin el pueblo) :-/ Es bien complejo, se requiere mucho tiempo desenmarañar todo y como está todo entrelazado. Y cuando hacen cambios es por el bien de ellos, ahora la instalación tiene que ser por compilación para obtener la nueva suite, por ejemplo. Los que solo lo consumen sin saber nada de compilación han corrido la voz de que ya está muerto y que no hay actualizaciones sin embargo zimbra lo que ha dicho es que ya no se va a encargar de ofrecer los compilados para la rama opensource, pero seguirán disponibles. Los resultados que hice es que al final actualizar el thunderbird resolvió algunos problemas, puede ayudar crear varios zimbra proxy dependiendo de la geolocalizacion y esto mejora los problemas de conexión. > > Saludos, > > -- > Camaleón Saludos > (...) --
Re: Om debian på desktoppen
On Tue, 7 May 2024, Flemming Bjerke wrote:
Den 06.05.2024 kl. 15.18 skrev Povl Ole Haarlev Olsen:
Har du prøvet Debian backports?
Fordi jeg ikke orker at styre det:
It is recommended to pick out single backports which fit your needs, and
not to use all backports available.
https://wiki.debian.org/Backports
Jeg er ikke sikker på, at jeg ved hvorfor du mener det er besværligt at
styre.
Du installer en pakke som normalt. ("dia" er, som sagt, ikke i backports,
men da du ikke har nævnt andre pakker, bruger jeg alligevel den som
eksempel.)
Du opdager, at "dia" fra stable af den ene eller anden grund ikke er "god
nok".
Din løsning har været noget med at køre dia fra en Kubuntu chroot.
Med backports beder du i stedet pakkesystemet om at installere dia fra
backports. Enten vha.
apt install dia/bookworm-backports
(hvor du kun får "dia" fra backports, men ikke eventuelle dependencies)
eller vha.
apt -t bookworm-backports install dia
(hvor både "dia" og eventuelle dependencies bliver installeret fra
backports)
Og... Det er vist det.
Nyeste Q2OS er baseret på bookworm med nogle systemændringer.
ls /etc/apt/sources.list.d/
10_q4os.list 20_debian.list 30_debian_backports.list
(backports er ikke aktiveret)
Hint: Hvis man vil disable en fil i /etc/apt/sources.list.d/ uden at pille
i selve filen, kan man nøjes med at rename filen, så den ikke hedder
*.list, f.eks. hedder nogle af mine *.list.disabled
chroot /a2 mount /dev/sda4 /home
Hvad er grunden til, at du ikke bind-mounter /home?
Det er vel også det rigtigste at bruge bind. Men gør det nogen forskel?
Med bind-mount burde der kun være een version af filesystem koden i brug
og derfor også kun een ting, der snakker med /dev/sda4. Mens der med et
"rigtigt" mount kunne være to versioner filesystem koden i brug, en for
/home og en for /a2/home, og derfor to ting, der prøver at snakke med
/dev/sda4 samtidig.
Jeg har ikke checket, om det kunne give problemer. Det var lettere bare at
bruge et bind-mount og slippe for at tænke over den slags ting.
chroot /a2 #Her kan man udføre alle mulige kommandoer. Skriptet venter
til man kører: exit.
#chroot --userspec=flem:flem /a2 (fungerer ikke - forstår ikke hvorfor)
Hmm, hvorfor har jeg ikke hørt om --userspec før?!
man chroot
Ja, jeg er godt klar over, at det selvfølgelig står i man siden. Men hvem
læser man sider, når ens script virker "fint"? :-)
Og nu kan mit skript forenkles ganske meget:
#!/bin/bash
mount --bind /home /a2/home
bash -c "HOME=/home/flem chroot --userspec=flem:flem /a2 $1"
Med "$@" i stedet for "$1" burde du også kunne give din kommando
argumenter, f.eks. bede dia om at åbne en specifik fil.
Det virker ikke som om man behøver mount --bind /sys osv. Faktisk fik jeg
lidt problemer når jeg gjorde det fordi alt i /dev/pts/ forsvandt. Hvorfor
fatter jeg ikke, men det har nok noget at gøre med:
While ‘chroot’ is a powerful tool, it’s not a security measure by itself.
Processes that are running as root can break out of the chroot jail.
https://hopeness.medium.com/master-the-linux-chroot-command-a-comprehensive-guide-f2026f913726
Ok, det er ikke noget, jeg selv har oplevet, men det er efterhånden også
et godt stykke tid siden jeg sidst brugte chroot, så måske er noget blev
ændret.
Men jeg skal nok ikke opdatere kubuntu via chroot ... Risikerer jeg ikke at
der kommer ged i kernen og boot ... osv.?
Jeg har ikke haft /boot mountet i mine chroots, så den slags har jeg
aldrig tænkt nærmere over. Hvis et chroot ville ændrer i hvad det troede
var /boot, så var det i virkelighed f.eks. /opt/wheezy/boot og ikke det
rigtige /boot.
--
Povl Ole
Re: Om debian på desktoppen
Den 06.05.2024 kl. 15.18 skrev Povl Ole Haarlev Olsen: On Mon, 6 May 2024, Flemming Bjerke wrote: Jeg har adskillige gange opgivet debian på desktoppen fordi jeg ustandselig fik problemer med alt muligt der ikke rigtig virkede, bl.a. programmer som ikke fungerede og ikke kunne opdateres pga. debians restriktioner på hvornår programmer kunne blive stable. (Jeg har dog ikke prøvet bookworm af.) Jeg har så valgt at køre med kubuntu i årevis. Har du prøvet Debian backports? Fordi jeg ikke orker at styre det: It is recommended to pick out single backports which fit your needs, and not to use all backports available. https://wiki.debian.org/Backports "dia" er, så vidt jeg kan se, ikke i backports, men måske kunne det bruges med nogle af de andre programmer, hvor du ønsker en nyere version. Jeg er meget tilfreds med at køre et debian system (sources er primært debian stable), for jeg har normalt ikke brug for de nyeste versioner af forskelligt software. Derimod er stabiliteten vigtig for mig. Men ind i mellem får man brug for en nyere version af et program. F.eks. er bookworm's version af dia håbløst buggy. Så fandt jeg på at chroot til min kubuntu som ligger (passivt) Hvordan ved du, at bookworms dia er buggy, hvis du ikke har prøvet bookworm? Nyeste Q2OS er baseret på bookworm med nogle systemændringer. ls /etc/apt/sources.list.d/ 10_q4os.list 20_debian.list 30_debian_backports.list (backports er ikke aktiveret) chroot /a2 mount /dev/sda4 /home Hvad er grunden til, at du ikke bind-mounter /home? Det er vel også det rigtigste at bruge bind. Men gør det nogen forskel? chroot /a2 #Her kan man udføre alle mulige kommandoer. Skriptet venter til man kører: exit. #chroot --userspec=flem:flem /a2 (fungerer ikke - forstår ikke hvorfor) Hmm, hvorfor har jeg ikke hørt om --userspec før?! man chroot Hvilken fejlbesked får du? chroot --userspec=flem:flem /a2 To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. bash: /root/.bashrc: Adgang nægtet Som det fremgår, virker det ikke som at bruge: "su bruger" idet man ikke får adgang til det brugeren normalt har adgang til. Så uanset man er bruger (og altså ikke root), kan man f.eks. ikke køre dia: flem@baren:/$ whoami flem flem@baren:/$ dia ** (dia:102168): CRITICAL **: 08:48:13.495: Could not create per-user Dia configuration directory -- På nettet fandt Jeg en måde at omgå dette på: bash -c "HOME= chroot --userspec=: /bin/bash -i" Og nu kan mit skript forenkles ganske meget: #!/bin/bash mount --bind /home /a2/home bash -c "HOME=/home/flem chroot --userspec=flem:flem /a2 $1" umount /a2/home Med dette skript kan jeg afvikle et program på min ubuntu-partition. F.eks. ./chroot-program.sh dia Og hvis man ikke angiver et program, startes en kommandoprompt. Overordentlig nyttigt. Det virker ikke som om man behøver mount --bind /sys osv. Faktisk fik jeg lidt problemer når jeg gjorde det fordi alt i /dev/pts/ forsvandt. Hvorfor fatter jeg ikke, men det har nok noget at gøre med: While ‘chroot’ is a powerful tool, it’s not a security measure by itself. Processes that are running as root can break out of the chroot jail. https://hopeness.medium.com/master-the-linux-chroot-command-a-comprehensive-guide-f2026f913726 Men jeg skal nok ikke opdatere kubuntu via chroot ... Risikerer jeg ikke at der kommer ged i kernen og boot ... osv.? Nu kan jeg starte f.eks. kubuntus dia (og libreoffice) fra en terminal, og hvis jeg gør det med et & efter, fungerer fungerer programmet videre selv efter exit fra chroot. Hvad synes I om min løsning? Jeg har haft noget i samme stil (med /home bind-mounted) for at kunne bruge en ældre version af bl.a. xpra. Jeg havde alle mine bind-mounts i /etc/fstab og en desktop launcher, der "run in terminal" kørte su -c "chroot /opt/wheezy /bin/su - stderr -c /usr/bin/xfce4-terminal & bg" (Med --userspec ville den linie sikkert kunne skæres kraftigt ned.) Launcher'en startede en terminal og alt startet i den terminal blev kørte fra en wheezy installation, jeg havde debootstrap'et i /opt/wheezy. Det virkede fint til mit formål. Sejt! Det er selvfølgelig ikke uproblematisk at køre to forskellige systemer på samme home-partition, men hvis man ikke bruger samme programmer på dem, burde det vel ikke skabe de store problemer? Hvis programmer opførte sig nogenlunde pænt, ville det heller ikke være noget problem, at køre de samme programmer på samme homedir. Da jeg var studerende var vores homedirs mountet på Linux, HP-UX, IRIX, Solaris, ... og jeg tænkte ikke ret meget over, om jeg kunne tillade mig, at starte et program på en given platform eller ej. Men jeg ved godt, at der er nogle programmer, der meget gerne vil lave en "upgrade" af deres config i ~/.config
Re: Om debian på desktoppen
On Mon, 6 May 2024, Flemming Bjerke wrote: Jeg har adskillige gange opgivet debian på desktoppen fordi jeg ustandselig fik problemer med alt muligt der ikke rigtig virkede, bl.a. programmer som ikke fungerede og ikke kunne opdateres pga. debians restriktioner på hvornår programmer kunne blive stable. (Jeg har dog ikke prøvet bookworm af.) Jeg har så valgt at køre med kubuntu i årevis. Har du prøvet Debian backports? "dia" er, så vidt jeg kan se, ikke i backports, men måske kunne det bruges med nogle af de andre programmer, hvor du ønsker en nyere version. Jeg er meget tilfreds med at køre et debian system (sources er primært debian stable), for jeg har normalt ikke brug for de nyeste versioner af forskelligt software. Derimod er stabiliteten vigtig for mig. Men ind i mellem får man brug for en nyere version af et program. F.eks. er bookworm's version af dia håbløst buggy. Så fandt jeg på at chroot til min kubuntu som ligger (passivt) Hvordan ved du, at bookworms dia er buggy, hvis du ikke har prøvet bookworm? på den anden partion. Og vupti fungerede dia igen. Jeg lavede følgende skript: --- #!/bin/bash mount --bind /dev /a2/dev mount --bind /dev/pts /a2/dev/pts mount --bind /proc /a2/proc mount --bind /sys /a2/sys chroot /a2 mount /dev/sda4 /home Hvad er grunden til, at du ikke bind-mounter /home? chroot /a2 #Her kan man udføre alle mulige kommandoer. Skriptet venter til man kører: exit. #chroot --userspec=flem:flem /a2 (fungerer ikke - forstår ikke hvorfor) Hmm, hvorfor har jeg ikke hørt om --userspec før?! Hvilken fejlbesked får du? chroot /a2 umount /dev/sda4 umount /a2/sys umount /a2/proc umount /a2/dev/pts umount /a2/dev echo 'a2 er nu forladt' (Mit kubuntu ligger på /a2 som monteres automatisk ved start.) Nu kan jeg starte f.eks. kubuntus dia (og libreoffice) fra en terminal, og hvis jeg gør det med et & efter, fungerer fungerer programmet videre selv efter exit fra chroot. Hvad synes I om min løsning? Jeg har haft noget i samme stil (med /home bind-mounted) for at kunne bruge en ældre version af bl.a. xpra. Jeg havde alle mine bind-mounts i /etc/fstab og en desktop launcher, der "run in terminal" kørte su -c "chroot /opt/wheezy /bin/su - stderr -c /usr/bin/xfce4-terminal & bg" (Med --userspec ville den linie sikkert kunne skæres kraftigt ned.) Launcher'en startede en terminal og alt startet i den terminal blev kørte fra en wheezy installation, jeg havde debootstrap'et i /opt/wheezy. Det virkede fint til mit formål. Det er selvfølgelig ikke uproblematisk at køre to forskellige systemer på samme home-partition, men hvis man ikke bruger samme programmer på dem, burde det vel ikke skabe de store problemer? Hvis programmer opførte sig nogenlunde pænt, ville det heller ikke være noget problem, at køre de samme programmer på samme homedir. Da jeg var studerende var vores homedirs mountet på Linux, HP-UX, IRIX, Solaris, ... og jeg tænkte ikke ret meget over, om jeg kunne tillade mig, at starte et program på en given platform eller ej. Men jeg ved godt, at der er nogle programmer, der meget gerne vil lave en "upgrade" af deres config i ~/.config uden at tænke over, at man måske deler sit homedir mellem mange forskellige installationer. Det er eet af problemer ved, at nogen ikke længere ser Linux som et multi-user system i UNIX-familien. -- Povl Ole
Om debian på desktoppen
Kære Debian-folk Jeg har adskillige gange opgivet debian på desktoppen fordi jeg ustandselig fik problemer med alt muligt der ikke rigtig virkede, bl.a. programmer som ikke fungerede og ikke kunne opdateres pga. debians restriktioner på hvornår programmer kunne blive stable. (Jeg har dog ikke prøvet bookworm af.) Jeg har så valgt at køre med kubuntu i årevis. Det skal lige bemærkes at jeg på min arbejdslaptop i årevis har kørt med 1 home-partition og 2 systempartitioner (så jeg kunne prøve nye systemer/versioner af uden at forstyrre mit arbejdssystem). Jeg har i stykke tid forsøgt forskellige forks af debian på gamle bærbare med f.eks. 4 GB Ram og en enkelt processor. Jeg har forsøgt: 1. Antix. Et temmelig godt system som jeg tilmed kørte fint et års tid min arbejdslaptop. Men det gik galt da jeg skulle opdatere systemet. Systemet er også lidt for nørdet at sætte op. F.eks. skal flere skriveborde sættes op i en eller anden fil som det selvfølgelig tog lidt netsøgningstid at finde og finde ud af hvordan den skulle ændres. Og meget af menusystemet var fyldt med forskellige desktop-systemer m.m. som man ikke lige havde tænkt sig at sætte sig ind i. Installation gik heller ikke altid lige godt. 2. Bunsenlab. Et godt system, men også for nørdet at sætte op. Jeg orkede ikke at det næsten altid var op ad bakke at ændre på et eller andet. 3. Puppy-linux. Et mærkeligt system som man altid er root på. Det lykkedes mig aldrig at installere det 100% på harddisken. Jeg kunne godt få det til at lægge systemfilerne på harddisken, men selve boot fungerede åbenbart kun fra usb. Ikke anvendeligt til daglig brug. 4. Q4OS. Den korte historie er at det er den bedste desktop jeg har kørt overhovedet. Jeg bruger kde-versionen idet det kde er så let at sætte op. Der er arbejdet med at gøre systemet letvægts så det fungerer rigtig godt på ældre laptops selvom det vist ikke er helt så letvægt som antix og bunsenlab. Installation har indtil videre fungeret perfekt. Så vidt jeg kan se har folkene bag Q4OS gjort det rigtige: De har lænet sig op ad to store systemer: debian og kde og tilpasset det forholdsvis lidt efter deres målsætning: "Fast and friendly, desktop oriented operating system based on Debian Linux. Providing a set of dedicated utilities and specific optimizations, combined with a focus on getting a productive system easily. This makes it ideal for people who want to get a working environment tailored to individual needs and preferences. From this perspective, Q4OS is suitable for both newcomers as well as experienced computer users." Jeg er meget tilfreds med at køre et debian system (sources er primært debian stable), for jeg har normalt ikke brug for de nyeste versioner af forskelligt software. Derimod er stabiliteten vigtig for mig. Men ind i mellem får man brug for en nyere version af et program. F.eks. er bookworm's version af dia håbløst buggy. Så fandt jeg på at chroot til min kubuntu som ligger (passivt) på den anden partion. Og vupti fungerede dia igen. Jeg lavede følgende skript: --- #!/bin/bash mount --bind /dev /a2/dev mount --bind /dev/pts /a2/dev/pts mount --bind /proc /a2/proc mount --bind /sys /a2/sys chroot /a2 mount /dev/sda4 /home chroot /a2 #Her kan man udføre alle mulige kommandoer. Skriptet venter til man kører: exit. #chroot --userspec=flem:flem /a2 (fungerer ikke - forstår ikke hvorfor) chroot /a2 umount /dev/sda4 umount /a2/sys umount /a2/proc umount /a2/dev/pts umount /a2/dev echo 'a2 er nu forladt' (Mit kubuntu ligger på /a2 som monteres automatisk ved start.) Nu kan jeg starte f.eks. kubuntus dia (og libreoffice) fra en terminal, og hvis jeg gør det med et & efter, fungerer fungerer programmet videre selv efter exit fra chroot. Hvad synes I om min løsning? Det er selvfølgelig ikke uproblematisk at køre to forskellige systemer på samme home-partition, men hvis man ikke bruger samme programmer på dem, burde det vel ikke skabe de store problemer? Bedste hilsener Flemming TH Bjerke Tlf. 22120366 PS: På min server kunne jeg ikke finde på at køre andet end debian. PPS: Jeg har også prøvet lubuntu på gamle bærbare, men det var nørdet og ikke særlig letvægts.
Re: RE: Problems installing QEMU packages on Debian 12 (stable)
Hi, thanks for checking, in the end I solved this by switching mirrors from default http://deb.debian.org/debian to http://ftp.cz.debian.org/debian - after updating I got the correct version of QEMU package. Maybe something was cached somewhere for several days, strange that I had to change the mirror.
Re: DNI electrónico en Debian
El 2024-05-03 a las 09:57 -0600, Alejandro G. Sanchez Martinez escribió: > En 02/05/24 01:41, Listas escribió: > > El jue, 02-05-2024 a las 09:10 +0200, Camaleón escribió: > > > > > > Quienes usáis un lector autónomo y os funciona bien, mejor si decís > > > marca, modelo (chipset) y tipo de conexión, seguro que resulta de > > > utilidad para quien pregunta y para futuros lectores de este hilo :-) > > > > > En concreto en mi caso es > > > > lector USB Alcor Micro AU9540. > > > > Pero cualquier lector que cumpla con la especificación CCID debería > > valer, básicamente todos los que se venden a día de hoy. > > > > Una lista de equipos soportados: > > https://ccid.apdu.fr/ccid/section.html > > > > Info de opensc: > > https://github.com/OpenSC/OpenSC/wiki/Smart-card-readers-%28Linux-and-Mac-OS-X%29 > > > > La especificación CCID: > > https://www.usb.org/sites/default/files/DWG_Smart-Card_CCID_Rev110.pdf > > > > Un saludo > > > > > Para lso que estasmo fuera de España si nos pudieran dar informaci+on de para > que lo utilizan > o cuales serían su funcuionalidad se lo agradeceriamos En España concretamente¹ es equivalente a la firma manuscrita, con lo que ello conlleva a efectos legales, jurídicos, administrativos y de todo tipo. Tanto el DNI electrónico (en soporte material de tarjeta física que integra un certificado digital) como el certificado electrónico cualificado (certificado en soporte software, es un archivo informático) se usan para identificarte/acreditarte ante cualquier instancia o entidad público y/o privada (gobierno, administraciones locales, empresas, contratos privados, etc...). Realmente útil tanto para personas físicas como para personas jurídicas (empresas o sus representantes). ¹Su uso es bastante desigual en otros países de la UE/EEE/Suiza, siendo Reino Unido caso aparte donde apenas se usa, al menos según mi experiencia personal. Saludos, -- Camaleón
Re: DNI electrónico en Debian
El 3/5/24 a las 17:57, Alejandro G. Sanchez Martinez escribió: > Para lso que estasmo fuera de España si nos pudieran dar informaci+on de para > que lo utilizan >o cuales serían su funcuionalidad se lo agradeceriamos Tiene las mismas funcionalidades que el certificado digital de la FNMT: https://www.fnmt.es/ceres permite identificarse y firmar digitalmente. Es útil sobre todo al relacionarse con la administración pública.
Re: DNI electrónico en Debian
En 02/05/24 01:41, Listas escribió: El jue, 02-05-2024 a las 09:10 +0200, Camaleón escribió: Quienes usáis un lector autónomo y os funciona bien, mejor si decís marca, modelo (chipset) y tipo de conexión, seguro que resulta de utilidad para quien pregunta y para futuros lectores de este hilo :-) En concreto en mi caso es lector USB Alcor Micro AU9540. Pero cualquier lector que cumpla con la especificación CCID debería valer, básicamente todos los que se venden a día de hoy. Una lista de equipos soportados: https://ccid.apdu.fr/ccid/section.html Info de opensc: https://github.com/OpenSC/OpenSC/wiki/Smart-card-readers-%28Linux-and-Mac-OS-X%29 La especificación CCID: https://www.usb.org/sites/default/files/DWG_Smart-Card_CCID_Rev110.pdf Un saludo Para lso que estasmo fuera de España si nos pudieran dar informaci+on de para que lo utilizan o cuales serían su funcuionalidad se lo agradeceriamos -- asanch...@e-compugraf.com Telegram: @xe1gnu B557 6185 4E38 59FB F58D D083 23A2 6FFD FA90 587C
Re: DNI electrónico en Debian
El jue, 02-05-2024 a las 09:10 +0200, Camaleón escribió: > > > Quienes usáis un lector autónomo y os funciona bien, mejor si decís > marca, modelo (chipset) y tipo de conexión, seguro que resulta de > utilidad para quien pregunta y para futuros lectores de este hilo :-) > En concreto en mi caso es lector USB Alcor Micro AU9540. Pero cualquier lector que cumpla con la especificación CCID debería valer, básicamente todos los que se venden a día de hoy. Una lista de equipos soportados: https://ccid.apdu.fr/ccid/section.html Info de opensc: https://github.com/OpenSC/OpenSC/wiki/Smart-card-readers-%28Linux-and-Mac-OS-X%29 La especificación CCID: https://www.usb.org/sites/default/files/DWG_Smart-Card_CCID_Rev110.pdf Un saludo
Re: DNI electrónico en Debian
El 2024-05-01 a las 21:42 +0200, Listas escribió: > El mié, 01-05-2024 a las 20:15 +0200, Luis Muñoz Fuente escribió: > > > > Hola a todos/as: > > ¿Alguien se identifica o firma con el DNI electrónico en Debian? > > Habitualmente uso el certificado digital de la FNMT pero estoy > > pensando comprar un lector de DNI por si me falla la firma con el > > certificado de la FNMT. > > Saludos > > Si, uso el DNIe con Debian testing y tarjetas criptográficas en general > con lector. Quienes usáis un lector autónomo y os funciona bien, mejor si decís marca, modelo (chipset) y tipo de conexión, seguro que resulta de utilidad para quien pregunta y para futuros lectores de este hilo :-) Saludos, -- Camaleón
Re: DNI electrónico en Debian
El mié, 01-05-2024 a las 20:15 +0200, Luis Muñoz Fuente escribió: > > Hola a todos/as: > ¿Alguien se identifica o firma con el DNI electrónico en Debian? > Habitualmente uso el certificado digital de la FNMT pero estoy > pensando comprar un lector de DNI por si me falla la firma con el > certificado de la FNMT. > Saludos Si, uso el DNIe con Debian testing y tarjetas criptográficas en general con lector. Un saludo
Re: DNI electrónico en Debian
Yo lo hago. Instalé en Debian 11 y se mantiene todo correcto después de que actualicé al 12. Configurado sobre Firefox. Único inconveniente que no he sabido configurar, firmar externamente con aplicaciones de cada organismo. No encuentra el almacén de certificados de Firefox. Tengo que guardar mi certificado en disco. También utilizo con lector de DNI electrónico. Un saludete El mié, 1 may 2024, 20:16, Luis Muñoz Fuente < luis.munoz@juntadeandalucia.es> escribió: > Hola a todos/as: > > ¿Alguien se identifica o firma con el DNI electrónico en Debian? > Habitualmente uso el certificado digital de la FNMT pero estoy pensando > comprar un lector de DNI por si me falla la firma con el certificado de la > FNMT. > > Saludos >
DNI electrónico en Debian
Hola a todos/as: ¿Alguien se identifica o firma con el DNI electrónico en Debian? Habitualmente uso el certificado digital de la FNMT pero estoy pensando comprar un lector de DNI por si me falla la firma con el certificado de la FNMT. Saludos
Re: Debian does not load zfs automatically at boot and strange messages displayed on the screen...
Am 30.04.2024 um 16:48 schrieb Mario Marietto: > Probably this is not the proper method to do it ? Done it in vm's and on bare metal many times. Never ran into your kind of problems. :-( Here is the guide, i suggest: https://openzfs.github.io/openzfs-docs/Getting%20Started/Debian/index.html#installation
Debian does not load zfs automatically at boot and strange messages displayed on the screen...
Hello to everyone. I've just installed Debian 12 (netinstall version with ssh server + web server) as guest os on top of Windows 11 using qemu + whpx. These are the parameters that I've used : I:\OS\vms\qemu\qemu-system-x86_64.exe -machine q35 -accel whpx -cpu kvm64,hv_relaxed,hv_time,hv_synic -m 8G -vga std -audiodev dsound,id=snd0 -device ich9-intel-hda -device hda-duplex,audiodev=snd0 -hda "I:\Backup\Linux\Debian.img" -drive file=\\.\PhysicalDrive5 -drive file=\\.\PhysicalDrive6 -drive file=\\.\PhysicalDrive8 -rtc base=localtime -device usb-ehci,id=usb,bus=pcie.0,addr=0x3 -device usb-tablet -device usb-kbd -smbios type=2 -nodefaults -netdev user,id=net0 -device e1000,netdev=net0,id=net0,mac=52:54:00:11:22:33 -device ich9-ahci,id=sata -bios "I:\OS\vms\qemu\OVMF_combined.fd" Actually it has two problems : 1) I've added the module zfs to /etc/modules because I want to autoload zfs as soon as Debian makes the booting,but it does not work. Probably this is not the proper method to do it ? 2) As you can see on the attached picture,I see a lot of strange messages on the screen ; I don't understand why they happen,but I would like to suppress them. [image: 2024-04-30 16 42 44.png] -- Mario.
Uninterruptible sleep apache process while aceessing nfs on debian 12 bookworm
Hi
We recently migrated to new nfs server running on debian 12 bookworm
On the client Apache processes started randomly switching to D state,
In apache fluststatus Process 93661 a mis 10786 sec
=
4-1 93661 1598/ W 15.92 10786 0 2367404 0.0 71.45 142.44 172.20.1.47 http/1.1
sisca.groupe-mfc.fr:80 POST
/deverrouille-fiche-ajax.php?sTable=prospects=243239
ps aux ==> Process 93661 un interruptible sleep
root@hexaom-v2-vm-prod-front2:~# while true; do date; ps auxf | awk
'{if($8=="D") print $0;}'; sleep 1; done
Fri 26 Apr 2024 12:37:59 PM CEST
www-data 93661 0.1 1.4 315100 120468 ? D08:45 0:14 \_
/usr/sbin/apache2 -k start
www-data 119374 0.2 0.0 0 0 ?D11:33 0:10 \_ [apache2]
www-data 127425 0.1 0.8 214520 68308 ?D12:27 0:00 \_
/usr/sbin/apache2 -k start
process stack : (can't attach using gdp gcore etc )
===
root@hexaom-v2-vm-prod-front2:~# cat /proc/93661/stack
[<0>] wait_on_commit+0x71/0xb0 [nfs]
[<0>] __nfs_commit_inode+0x131/0x180 [nfs]
[<0>] nfs_wb_all+0xb4/0x100 [nfs]
[<0>] nfs4_file_flush+0x6f/0xa0 [nfsv4]
[<0>] filp_close+0x2f/0x70
[<0>] __x64_sys_close+0x1e/0x60
[<0>] do_syscall_64+0x30/0x80
[<0>] entry_SYSCALL_64_after_hwframe+0x62/0xc7
=
In the client debian 11
=
rpcdebug -m nfs -s all
Apr 26 11:30:15 hexaom-v2-vm-prod-front2 kernel: [51318.693854]
decode_attr_fs_locations: fs_locations done, error = 0
Apr 26 11:30:15 hexaom-v2-vm-prod-front2 kernel: [51318.693871]
nfs41_sequence_process: Error 0 free the slot
Apr 26 11:30:15 hexaom-v2-vm-prod-front2 kernel: [51318.694161]
nfs41_sequence_process: Error 0 free the slot
Apr 26 11:30:15 hexaom-v2-vm-prod-front2 kernel: [51318.694301]
nfs41_sequence_process: Error 0 free the slot
=
No error in nfds server even with debug all : rpcdebug -m nfsd -s all
Information : on client and server
***
client :
root@hexaom-v2-vm-prod-front2:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;
root@hexaom-v2-vm-prod-front2:~# uname -a
Linux hexaom-v2-vm-prod-front2 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2
(2024-01-31) x86_64 GNU/Linux
root@hexaom-v2-vm-prod-front2:~# dpkg -l | grep -i nfs
ii liblockfile1:amd641.17-1+b1
amd64NFS-safe locking library
ii libnfsidmap2:amd640.25-6
amd64NFS idmapping library
ii nfs-common1:1.3.4-6
amd64NFS support files common to
client and server
fstab:
192.20.2.30:/NFS/sessions_v2 /srv/sessions nfs
defaults,rw,relatime,vers=4.1,hard,timeo=100,retrans=4,_netdev 0 0
=
Server:
=
root@SERVSESSION01:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;
Linux SERVSESSION01 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1
(2024-02-01) x86_64 GNU/Linux
*
root@SERVSESSION01:~# dpkg -l | grep nfs
ii libnfsidmap1:amd641:2.6.2-4 amd64
NFS idmapping library
ii nfs-common1:2.6.2-4 amd64
NFS support files common to client and server
ii nfs-kernel-server 1:2.6.2-4 amd64
support for NFS kernel server
root@SERVSESSION01:~# dpkg -l | grep rpc
ii libtirpc-common 1.3.3+ds-1 all
transport-independent RPC library - common files
ii libtirpc3:amd64 1.3.3+ds-1 amd64
transport-independent RPC library
ii rpcbind 1.2.6-6+b1 amd64
converts RPC program numbers into universal addresses
root@SERVSESSION01:~#
**
*
root@SERVSESSION01:~# cat /etc/default/nfs-common
# If you do not set values for the NEED_ options, they will be attempted
# autodetected; this should be sufficient for most people. Valid alternatives
# for the NEED_ options are "yes" and "no".
# Do you want to start the statd daemon? It is not needed for NFSv4.
NEED_STATD=
# Options for rpc.sta
Debian 12.5 i386 sudo returns "Illegal instruction"
> The new minimum requirement is i686. > Debian requires i686 compatibility - even when the arch is being displayed as i386 due to compatibility reasons. Thank you for your insights. I'll have to pay more attention to the release notes in the future. I have mourned the loss of my Soekris boxes and am over it.
Re: Debian 12.5 i386 sudo returns "Illegal instruction"
Am 25.04.2024 schrieb Vic tor : > On a fresh installation of Debian 12.5, i386 I receive "Illegal > instruction" when executing sudo. Is there any way to debug and > workaround this; should I take this to another list as a bug? Here it is described with gdb: https://stackoverflow.com/questions/10354147/find-which-assembly-instruction-caused-an-illegal-instruction-error-without-debu > This is on a Soekris net5501 powered by an AMD Geode LX which is the > only oddball factor. Debian requires i686 compatibility - even when the arch is being displayed as i386 due to compatibility reasons. According to this thread, the Geode LX lacks some i686 instructions. https://lists.debian.org/debian-user/2019/04/msg01093.html
Re: Debian 12.5 i386 sudo returns "Illegal instruction"
On Thu, Apr 25, 2024 at 09:54:17AM -0400, Vic tor wrote: > On a fresh installation of Debian 12.5, i386 I receive "Illegal instruction" > when executing sudo. Is there any way to debug and workaround this; should I > take this to another list as a bug? > > This is on a Soekris net5501 powered by an AMD Geode LX which is the only > oddball factor. I've been running Debian on these guys since version 8 without > any problem. https://www.debian.org/releases/stable/i386/release-notes/ch-information.en.html#i386-is-i686 Debian's support for 32-bit PC (known as the Debian architecture i386) now no longer covers any i586 processor. The new minimum requirement is i686. What this means that the i386 architecture now requires the "long NOP" (NOPL) instruction, while bullseye still supported some i586 processors without that instruction (e.g. the "AMD Geode"). If your machine is not compatible with this requirement, it is recommended that you stay with bullseye for the remainder of its support cycle.
Debian 12.5 i386 sudo returns "Illegal instruction"
On a fresh installation of Debian 12.5, i386 I receive "Illegal instruction" when executing sudo. Is there any way to debug and workaround this; should I take this to another list as a bug? This is on a Soekris net5501 powered by an AMD Geode LX which is the only oddball factor. I've been running Debian on these guys since version 8 without any problem.
Re: Debian@IBMx3550
В Вт, 23/04/2024 в 15:14 -0700, David Christensen пишет: > On 4/23/24 14:35, Greg wrote: > > Hi there, > > > > I got refurb IBM x3550 M3 7944 server and I'm a bit lost. Is there > > any > > Linux/Debian software (some gui would be nice) to monitor fan > > speed, > > temperatures, voltages, disks.. ? > > > > Thanks in advance for any help > > Greg > > > > > If you installed the Xfce desktop, add the "Sensor" plug-in/ applet > to > the Panel. Panel can display various temperatures, fan speeds, etc.. > > > Note that you may to set the SUID bit on /usr/sbin/hddtemp for disk > drive readings to be available: > > # chmod u+s /usr/sbin/hddtemp > > > David > Hello. You can use bpytop, that shows usage and stats for processor, memory, disks, network and processes. Or btop (it is written in C++ and is continuation of bashtop and bpytop).
Re: Debian, Postfix, Dovecot, MySQL, and argon2 password hashing scheme?
Am 25.04.2024 schrieb David Mehler : > Since changing systems to Debian 12.5 I can't send, though checking > the password with a manual login to Dovecot works fine. Sending mails is SMTP and therefore postfix on your machine. It can use PAM for auth. Do you use PAM?
Debian, Postfix, Dovecot, MySQL, and argon2 password hashing scheme?
Hello, I have a quick question. Can Debian, and/or it's Postfix/Dovecot/MySQL/MariaDB packages support the argon2 password hashing scheme? I had a previously-working e-mail setup on a *BSD system, utilizing the argon2ID scheme with Dovecot, Postfix, and MySQL. Since changing systems to Debian 12.5 I can't send, though checking the password with a manual login to Dovecot works fine. I'm wondering if I have to migrate the passwords from argon2ID to SHA512-CRYPT? Thanks. Dave. -- Sent from Mozilla Thunderbird 91.13.1
Problems installing QEMU packages on Debian 12 (stable)
Hi, I am trying to make KVM/QEMU work on my Debian 12. I follow https://wiki.debian.org/KVM but I get stuck already on installation, because apt-get reports non-existent packages on debian repos. I ran sudo apt install qemu-system libvirt-daemon-system virt-manager It resolves packages, but when fails on 404 on qemu / xen packages Full output is here: sudo apt install qemu-system libvirt-daemon-system virt-manager Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libcapi20-3 libodbc2 libosmesa6 libz-mingw-w64 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: gir1.2-ayatanaappindicator3-0.1 gir1.2-gtk-vnc-2.0 gir1.2-libosinfo-1.0 gir1.2-libvirt-glib-1.0 gir1.2-spiceclientglib-2.0 gir1.2-spiceclientgtk-3.0 gir1.2-vte-2.91 gnutls-bin ibverbs-providers ipxe-qemu libcacard0 libcapstone4 libdaxctl1 libexecs0 libfdt1 libfmt9 libgfapi0 libgfrpc0 libgfxdr0 libglusterfs0 libgtk-vnc-2.0-0 libgvnc-1.0-0 libibverbs1 libiscsi7 libisoburn1 libndctl6 libnss-mymachines libphodav-3.0-0 libphodav-3.0-common libpmem1 librados2 librbd1 librdmacm1 libspice-client-glib-2.0-8 libspice-client-gtk-3.0-5 libspice-server1 libtpms0 liburing2 libusbredirhost1 libusbredirparser1 libvdeplug2 libvirglrenderer1 libvirt-clients libvirt-daemon libvirt-daemon-config-network libvirt-daemon-config-nwfilter libvirt-daemon-driver-lxc libvirt-daemon-driver-qemu libvirt-daemon-driver-vbox libvirt-daemon-driver-xen libvirt-daemon-system-systemd libvirt-glib-1.0-0 libvirt-glib-1.0-data libvirt-l10n libvirt0 libxencall1 libxendevicemodel1 libxenevtchn1 libxenforeignmemory1 libxengnttab1 libxenhypfs1 libxenmisc4.17 libxenstore4 libxentoolcore1 libxentoollog1 libxml2-utils mdevctl netcat-openbsd ovmf python3-libvirt python3-libxml2 qemu-block-extra qemu-efi-aarch64 qemu-efi-arm qemu-system-arm qemu-system-common qemu-system-data qemu-system-gui qemu-system-mips qemu-system-misc qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-utils seabios spice-client-glib-usb-acl-helper swtpm swtpm-libs swtpm-tools systemd-container virt-viewer virtinst xorriso Suggested packages: libvirt-clients-qemu libvirt-login-shell libvirt-daemon-driver-storage-gluster libvirt-daemon-driver-storage-iscsi-direct libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-zfs numad auditd nfs-common open-iscsi pm-utils systemtap zfsutils samba vde2 trousers python3-guestfs ssh-askpass xorriso-tcltk jigit cdck The following NEW packages will be installed: gir1.2-ayatanaappindicator3-0.1 gir1.2-gtk-vnc-2.0 gir1.2-libosinfo-1.0 gir1.2-libvirt-glib-1.0 gir1.2-spiceclientglib-2.0 gir1.2-spiceclientgtk-3.0 gir1.2-vte-2.91 gnutls-bin ibverbs-providers ipxe-qemu libcacard0 libcapstone4 libdaxctl1 libexecs0 libfdt1 libfmt9 libgfapi0 libgfrpc0 libgfxdr0 libglusterfs0 libgtk-vnc-2.0-0 libgvnc-1.0-0 libibverbs1 libiscsi7 libisoburn1 libndctl6 libnss-mymachines libphodav-3.0-0 libphodav-3.0-common libpmem1 librados2 librbd1 librdmacm1 libspice-client-glib-2.0-8 libspice-client-gtk-3.0-5 libspice-server1 libtpms0 liburing2 libusbredirhost1 libusbredirparser1 libvdeplug2 libvirglrenderer1 libvirt-clients libvirt-daemon libvirt-daemon-config-network libvirt-daemon-config-nwfilter libvirt-daemon-driver-lxc libvirt-daemon-driver-qemu libvirt-daemon-driver-vbox libvirt-daemon-driver-xen libvirt-daemon-system libvirt-daemon-system-systemd libvirt-glib-1.0-0 libvirt-glib-1.0-data libvirt-l10n libvirt0 libxencall1 libxendevicemodel1 libxenevtchn1 libxenforeignmemory1 libxengnttab1 libxenhypfs1 libxenmisc4.17 libxenstore4 libxentoolcore1 libxentoollog1 libxml2-utils mdevctl netcat-openbsd ovmf python3-libvirt python3-libxml2 qemu-block-extra qemu-efi-aarch64 qemu-efi-arm qemu-system qemu-system-arm qemu-system-common qemu-system-data qemu-system-gui qemu-system-mips qemu-system-misc qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-utils seabios spice-client-glib-usb-acl-helper swtpm swtpm-libs swtpm-tools systemd-container virt-manager virt-viewer virtinst xorriso 0 upgraded, 96 newly installed, 0 to remove and 0 not upgraded. Need to get 97,7 MB/143 MB of archives. After this operation, 974 MB of additional disk space will be used. Do you want to continue? [Y/n] y Err:1 http://deb.debian.org/debian bookworm/main amd64 gnutls-bin amd64 3.7.9-2+deb12u1 404 Not Found [IP: 2a04:4e42:41::644 80] Err:2 http://deb.debian.org/debian bookworm/main amd64 systemd-container amd64 252.19-1~deb12u1 404 Not Found [IP: 2a04:4e42:41::644 80] Err:3 http://deb.debian.org/debian bookworm/main amd64 libnss-mymachines amd64 252.19-1~deb12u1 404 Not Found [IP: 2a04:4e42:41::644 80] Err:4 http://deb.debian.org/debian bookworm/main amd64 libxentoolcore1 amd64 4.17.2+76-ge1f9cb16e2-1~deb12u1 404 Not Found [IP: 2a04:4e42:41::644
Re: Install Debian 12.5 on QNAP TS-210
On 24.04.2024 19:49, David Hörnlund wrote: Hi debian-user, I have an old QNAP TS-210 that would continue to be useful for me. If it is still possible to use it with the latest Debian Stable. There is a webpage at https://www.cyrius.com/debian/kirkwood/qnap/ts-219/ That have instruktions on how to install Debian 10 on this device. Can I install Debian 10 on the device today still or is that version not available anymore? Are the .Deb packades still on the mirrors? If the files are available will it install or is it blocked somehow? If I follow the steps on the webpage and do what the author suggests: My recommendation is for the third option; Arnaud Mouiche has created a script that re-configures the partition layout. Arnaud Mouiche's method has been used by many users with success. Will Debian 12 have the necessary packades and cpu architecture support to allow Debian 12 to boot and run. But also receive updates and new software configured for the QNAP TS-210? According to the author Debian dropped the support for this device when support ended for Debian 10. The Marvel ARM SoC IC is still supported by kernel [1], so the only reason support was ended at Debian 10 is indeed because of limited space on the flash device. I don't see why it shouldn't work, if information on Arnaud Mouiche's Github page [2] is correct. If I had this device I'd definitely gave it a try. But you have to be careful, since the whole process requires re-flashing custom firmware, you might end up with bricked device. Another option is to simply continue to use QNAP internal OS. [1] https://www.kernel.org/doc/html/v6.1/arm/marvell.html#kirkwood-family [2] https://github.com/amouiche/qnap_mtd_resize_for_bullseye -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Install Debian 12.5 on QNAP TS-210
Hi debian-user,I have an old QNAP TS-210 that would continue to be useful for me. If it is still possible to use it with the latest Debian Stable.There is a webpage at https://www.cyrius.com/debian/kirkwood/qnap/ts-219/That have instruktions on how to install Debian 10 on this device.Can I install Debian 10 on the device today still or is that version not available anymore? Are the .Deb packades still on the mirrors? If the files are available will it install or is it blocked somehow?If I follow the steps on the webpage and do what the author suggests:My recommendation is for the third option; Arnaud Mouiche has created a script that re-configures the partition layout.Arnaud Mouiche's method has been used by many users with success.Will Debian 12 have the necessary packades and cpu architecture support to allow Debian 12 to boot and run. But also receive updates and new software configured for the QNAP TS-210?According to the author Debian dropped the support for this device when support ended for Debian 10. I need to know If it is possible to continue using this device or If I should deposit it in the garbage bin. So it get sent to electronics recycling.RegardsDavid
Re : CD vendeurs debian
Bonjour JC, En pensant aux autres utilisateurs de la liste, je te signale que le lien que tu as mis pour getlinux est erroné. La page d'accueil est à l'adresse : https://www.getlinux.fr La page pour voir les offres de CD est : https://www.getlinux.fr/index.php?route=product/manufacturer/info_id=11 Bien cordialement, Cassis - Mail d'origine - De: jc gucci À: debian-user-french@lists.debian.org Envoyé: Mon, 22 Apr 2024 09:40:54 +0200 (CEST) Objet: CD vendeurs debian https://www.debian.org/CD/vendors/#fr vendeur de support d'installation de debian https://www.getlinux.f le lien fonctionne j'ai pas encore essayé la commande (5,99$) https://www.hypra.fr/ le lien ne fonctionne pas
Re: Debian@IBMx3550
On Tue, Apr 23, 2024 at 5:35 PM Greg wrote: > Hi there, > > I got refurb IBM x3550 M3 7944 server and I'm a bit lost. Is there any > Linux/Debian software (some gui would be nice) to monitor fan speed, > temperatures, voltages, disks.. ? > KDE has a bunch of monitoring widgets. Do you have a GUI Installed? > Thanks in advance for any help > Greg > > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Re: Debian@IBMx3550
On 4/23/24 14:35, Greg wrote: Hi there, I got refurb IBM x3550 M3 7944 server and I'm a bit lost. Is there any Linux/Debian software (some gui would be nice) to monitor fan speed, temperatures, voltages, disks.. ? Thanks in advance for any help Greg If you installed the Xfce desktop, add the "Sensor" plug-in/ applet to the Panel. Panel can display various temperatures, fan speeds, etc.. Note that you may to set the SUID bit on /usr/sbin/hddtemp for disk drive readings to be available: # chmod u+s /usr/sbin/hddtemp David
Re: Debian@IBMx3550
On Tue, Apr 23, 2024 at 5:35 PM Greg wrote: > Hi there, > > I got refurb IBM x3550 M3 7944 server and I'm a bit lost. Is there any > Linux/Debian software (some gui would be nice) to monitor fan speed, > temperatures, voltages, disks.. ? > I believe the package you are looking for is lm-sensors. Jeff
Debian@IBMx3550
Hi there, I got refurb IBM x3550 M3 7944 server and I'm a bit lost. Is there any Linux/Debian software (some gui would be nice) to monitor fan speed, temperatures, voltages, disks.. ? Thanks in advance for any help Greg
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
On Tue, Apr 23, 2024 at 6:26 AM Curt wrote: > > On 2024-04-22, Reid wrote: > > > > I'm sorry I irked you so much Curt, but you don't have to be rude. > > I'm Curt. Let's be serious. You be Frank and I'll be Earnest.
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
On 2024-04-22, Reid wrote: > > I'm sorry I irked you so much Curt, but you don't have to be rude. I'm Curt.
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
On Mon, Apr 22, 2024 at 05:02:09PM -0400, Stefan Monnier wrote: > >> > Do you have any suggestion as to which list would be better to contact? > >> > Original: https://lists.debian.org/debian-user/2024/04/msg00324.html > >> Maybe `reportbug debian-installer`? > > but perhaps without all the deception crap, unless you really mean > > to impugn the developers' motives. > > Yup, better try to make the developers/maintainers your friends, so you > may get them to do something with which they disagree just to make you > happy, rather than refuse to do something out of spite, even tho they > know it's right. > Hi Stefan, As you say, there are ways to get the developers to pay attention to you. One of them, at least, is to be constructive and to assume good faith. Developers will often take the best technical solution rather than doing it "just to make you happy". Rarely do developers do something out of spite though there may be massive technical disagreements. It's probably worth remembering that Debian developers are also users of Debian - and that we're all more or less on the same side. Imputation of bad faith (or snarky comments) don't help either the person commented on or the reputation of the commenter, necessarily. With every good wish, as ever, Andrew Cater [amaca...@debian.org] > > Stefan >
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
>> > Do you have any suggestion as to which list would be better to contact? >> > Original: https://lists.debian.org/debian-user/2024/04/msg00324.html >> Maybe `reportbug debian-installer`? > but perhaps without all the deception crap, unless you really mean > to impugn the developers' motives. Yup, better try to make the developers/maintainers your friends, so you may get them to do something with which they disagree just to make you happy, rather than refuse to do something out of spite, even tho they know it's right. Stefan
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
Andrew M.A. Cater wrote: > That's probably a bug in Calamares. I checked with one of the live cd > maintainers on this. As has been pointed out, the live cd is really > intended more for checking than for major use but it does need some work. > If you found the non-free components - where were they - under the /firmware > directory? Thank you for the very helpful reply Andrew. I always use Debian's "Graphical Installer" option. I'm not sure what Calamares is, but will look into it. However, I will also re-word what I now believe to be the primary issue here into a more succinct message, figure out how to add line-wrap, and re-submit to a more appropriate list. Thank you for everyone's helpful replies. Despite what one person said about not taking me seriously, I believe there's an important problem here, and that fixing it will be a good thing for the Debian project.
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
- Original message - From: Curt > On Mon, 22 Apr 2024, Curt wrote: > >> How can you be taken seriously when you can't even wrap your lines >> according to our venerable guidelines? >> Get a popular setting going, buddy. >> >> And, though it's true I extolled Proust recently, being succinct with >> well-wrapped lines is the height of mailing-list sophistication (unless >> your Marcel, which you ain't). > >The Debian mailing list guidelines (for our less supple intellects). 1. Disregard important suggestions of newcomers who don't line wrap. 2. Bombastically tell them they don't have supple intellects. Are those part of the mailing list guidelines, Curt? I'm sorry I irked you so much Curt, but you don't have to be rude. It was the first time I've ever messaged a Debian list, and it's been years since I've had to set line-wrap. "Let us be grateful to the people who make us happy; they are the charming gardeners who make our souls blossom." ― Marcel Proust
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
On Sun, Apr 21, 2024 at 11:31:03AM -0700, Reid wrote: > Debian's policy change on non-free-firmware has made much of the Debian.org > website very misleading, and some Debian OS installers have become very > Free Software UNfriendly and deceptive. The following is my experience, > and the reasons why I believe Debian must re-word their promotional web > pages, and update all their installers to respect user choice regarding > installation of non-free-firmware or not: I respect your experience. I think Debian made strenuous efforts to make the change, to publicise it, to hold an open vote. It was covered by a bunch of the tech press - it wasn't hidden in any way. Others have pointed you to the resources on that. > > I'm a 10+ year Debian user, and a longtime Free Software supporter. Two > weeks ago I was shocked to discover 29 non-free components in the Debian > desktop I'd been using for the last couple months. There hadn't been any > opt-in or even a notice about Debian's major policy change during the > installation process (I use the Debian installer via the Live images), > so I was completely unaware. > That's probably a bug in Calamares. I checked with one of the live cd maintainers on this. As has been pointed out, the live cd is really intended more for checking than for major use but it does need some work. If you found the non-free components - where were they - under the /firmware directory? > In my initial attempts to figure out what was going on, I also didn't find > any prominent announcement of the major policy change on Debian.org's > homepage. Moreover, the "Our Philosophy" and "Why Debian" homepage links > still give the impression that Debian is Free-Software-Friendly. That's > extremely misleading now (automatically installing 29 non-free components > with neither permission nor warning is not Free Software friendly). > Debian *is* Free software friendly: the manufacturers aren't and the non-free firmware included is to allow people to actually install Debian. The project deliberately split the firmware out into a new repository, tagged as non-free and gave instructions as to what that was. The Project doesn't recommend the use of other non-free software but retains that repository separately for those that want to use it. > If Debian is going to continue promoting itself with those "Our Philosophy" > and "Why Debian" pages, there should at least be opt-ins during the > installation process of every Debian download, as well as prominent warnings > of the new policy on the download pages. Until that's done, the > "Our Philosophy" and "Why Debian" pages (and perhaps others) should be > re-worded so as to not be so misleading. > The philosophy remains the same: there is an option during installation and there are explicit opt-ins to each repository that gets added to /etc/apt/sources.list or equivalent. If you *really* want to check, do an expert install of Debian which includes the lowest priority questions that can generally be omitted in a standard install. > I was disappointed to eventually read of Debian's "vote" > on non-free-firmware. Though I do understand the desire to make Debian more > friendly to new users, doing so by misleading and alienating many existing > users doesn't make a lot of sense IMO: > The vote was as standard vote via General Resolution not just a "vote". Doing this has allowed some new users to install Debian. Visually impaired users may need non-free firmware just to be able to hear the installer: others may need WiFi to work - not all machines now have Ethernet available. > After reading of this change, I then spent the next week trying to figure > out how to re-install Debian without the non-free firmware. That's when I > discovered that Debian has suddenly become very Free-Software-UNfriendly. > Even when I used the "firmware=never" method on the Debian installer > (Live image dvd), the 29 non-free components were still installed! Without > warning. That "firmware=never" method is what Debian.org itself is > recommending (on a rather deep link sadly), but it doesn't even work! > See above: this may be a consequence of using the live DVD > So I eventually abandoned that longtime favorite method of installing my > preferred desktop, and switched to the NON-Live DVD installation... But > then discovered that using "firmware=never" method there also blocks > FREE-firmware that used to get installed. So now my Wifi adapter didn't > work, whereas it always worked with Debian 11/Bullseye and earlier > installations. Which chipset, please? If you installed the free firmware package, what changed? > > Ultimately it took me about a week, and about a dozen Debian Bookworm >
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
On 2024-04-22, Nate Bargmann wrote: > > I endure this on many other mailing lists unrelated to Debian, > particularly from groups.io that have a Web interface. It's a violation of Debian mailing list posting rules, guidelines, and tips. It irks me that in certain cases these guidelines are evoked with a supercilious alacrity, and at other times not at all, leading me to believe in the inherent bias of the rule-makers. > >
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
* On 2024 22 Apr 09:39 -0500, Curt wrote: > On 2024-04-21, Reid wrote: > > You seem to be suggesting that Debian users now need to read XX pages of > > release notes and guides in order to learn that what they're installing is > > not what the Debian.org homepage "Why Debian", "Our Philosophy", and "Who > > We Are / What We Do" pages are currently promoting Debian as. > > How can you be taken seriously when you can't even wrap your lines > according to our venerable guidelines? > > https://wiki.debian.org/DebianMailingLists > > Set linewrap to 65-78 characters. 72 is a popular setting. Looking at the OP's headers I see: X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.11.0-alpha0-379-gabd37849b7-fm-20240408.001-gabd37849 It appears our friend is using a Web browser and likely is presented with a text box that looks all nice and neat with wrapping and all but hits the list as one long line per paragraph. > Get a popular setting going, buddy. Until he sets up a real MUA, I doubt the formatting will improve. I endure this on many other mailing lists unrelated to Debian, particularly from groups.io that have a Web interface. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 signature.asc Description: PGP signature
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
On 2024-04-22, fxkl4...@protonmail.com wrote: > On Mon, 22 Apr 2024, Curt wrote: > >> On 2024-04-21, Reid wrote: >>> You seem to be suggesting that Debian users now need to read XX pages of >>> release notes and guides in order to learn that what they're installing is >>> not what the Debian.org homepage "Why Debian", "Our Philosophy", and "Who >>> We Are / What We Do" pages are currently promoting Debian as. >> >> How can you be taken seriously when you can't even wrap your lines >> according to our venerable guidelines? >> >> https://wiki.debian.org/DebianMailingLists >> >> Set linewrap to 65-78 characters. 72 is a popular setting. >> >> Get a popular setting going, buddy. >> >> And, though it's true I extolled Proust recently, being succinct with >> well-wrapped lines is the height of mailing-list sophistication (unless >> your Marcel, which you ain't). >> >> Of course, it's also true these guidelines are never evoked with >> anything approaching equanimity, so forget I even mentioned them. >> > > mentioned what > The Debian mailing list guidelines (for our less supple intellects). --
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
On Mon, 22 Apr 2024, Curt wrote: > On 2024-04-21, Reid wrote: >> You seem to be suggesting that Debian users now need to read XX pages of >> release notes and guides in order to learn that what they're installing is >> not what the Debian.org homepage "Why Debian", "Our Philosophy", and "Who We >> Are / What We Do" pages are currently promoting Debian as. > > How can you be taken seriously when you can't even wrap your lines > according to our venerable guidelines? > > https://wiki.debian.org/DebianMailingLists > > Set linewrap to 65-78 characters. 72 is a popular setting. > > Get a popular setting going, buddy. > > And, though it's true I extolled Proust recently, being succinct with > well-wrapped lines is the height of mailing-list sophistication (unless > your Marcel, which you ain't). > > Of course, it's also true these guidelines are never evoked with > anything approaching equanimity, so forget I even mentioned them. > mentioned what
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
On 2024-04-21, Reid wrote: > You seem to be suggesting that Debian users now need to read XX pages of > release notes and guides in order to learn that what they're installing is > not what the Debian.org homepage "Why Debian", "Our Philosophy", and "Who We > Are / What We Do" pages are currently promoting Debian as. How can you be taken seriously when you can't even wrap your lines according to our venerable guidelines? https://wiki.debian.org/DebianMailingLists Set linewrap to 65-78 characters. 72 is a popular setting. Get a popular setting going, buddy. And, though it's true I extolled Proust recently, being succinct with well-wrapped lines is the height of mailing-list sophistication (unless your Marcel, which you ain't). Of course, it's also true these guidelines are never evoked with anything approaching equanimity, so forget I even mentioned them.
Re: CD vendeurs debian
Bonjour,
Pour créer une clef USB debian on peut suivre
https://debian-facile.org/doc:install:usb-boot
On 4/22/24 09:40, jc gucci wrote:
https://www.debian.org/CD/vendors/#fr
vendeur de support d'installation de debian
https://www.getlinux.f le lien fonctionne j'ai pas encore essayé la
commande (5,99$)
https://www.hypra.fr/ le lien ne fonctionne pas
et si vous m'adresser par courrier une clef USB je peux vous installer
une Debian (ou Ubuntu) récente dessus et vous la renvoyer par courrier
simple (indiquez moi votre adresse postale).
Avec d'autres je développe le moteur d'inférences libre RefPerSys
<http://refpersys.org/> ("*REF*lexive *PER*sistent *SYS*tem", sous
licence GPLv3+ ou CeCILL) pour et sur Debian. Je cherche des
applications et/ou des contributions et/ou un consortium ITEA
<https://itea4.org/> ou HorizonEurope
<https://www.horizon-europe.gouv.fr/> qui pourrait être intéressés.
Et des supports avec Debian sont vendus (en ligne) par
https://enventelibre.org/fr/debian/94-cle-usb-debian.html
<https://enventelibre.org/fr/debian/94-cle-usb-debian.html-- Basile
Starynkevitch (only mine opinions / les
opinions sont miennes uniquement)8 rue de la Faïencerie, 92340
Bourg-la-Reine, Franceweb page: starynkevitch.net/Basile/See/voir:
https://github.com/RefPerSys/RefPerSys>
Les associations APRIL <https://april.org/> et AFUL
<https://aful.org/association/> (dont je suis membre) peuvent vous aider
à installer Debian. Ou moi-même si vous venez chez moi (92340
Bourg-la-Reine en Île-de-France). Contactez moi préalablement sur mon
téléphone portable (+33-068501 suivi de la somme de cinquante-neuf et de
2300).
librement
--
Basile Starynkevitch
(only mine opinions / les opinions sont miennes uniquement)
8 rue de la Faïencerie, 92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/
See/voir:https://github.com/RefPerSys/RefPerSys
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
On Sun Apr 21, 2024 at 9:58 PM BST, Reid wrote: > If the Installers are not ALL going to give users the choice to opt-in > or opt-out of non-free components, then those above-mentioned > promotional pages really need to be updated so as to not be misleading > users. I'm sure the Debian WWW team would be welcome of some help addressing issues. The communication point for them is the debian-www[1] mailing list, and there's a www.debian.org pseudo-package in the Debian BTS[2] where bugs and patches can be filed. [1] https://lists.debian.org/debian-www/ [2] https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=www.debian.org > But BETTER yet, why not just update all the installers to give users > that choice? That's what I'm strongly suggesting. Something very > wrong/misleading/deceptive is happening right now. Likewise, the installer team communicate with a dedicated list debian-boot[3], and the installer(s) have their own BTS components: one is debian-installer[4], but I'm not sure what the Live DVD is covered by. [3] https://lists.debian.org/debian-boot/ [4] https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=debian-installer The list you are posting on is a User list, so there's no guarantee that the relevant Developers will see your messages. Best wishes, -- Please do not CC me for listmail. Jonathan Dowland ✎j...@debian.org https://jmtd.net
CD vendeurs debian
https://www.debian.org/CD/vendors/#fr vendeur de support d'installation de debian https://www.getlinux.f le lien fonctionne j'ai pas encore essayé la commande (5,99$) https://www.hypra.fr/ le lien ne fonctionne pas
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
On 21 Apr 2024 13:58 -0700, from reid...@proinbox.com (Reid): > You seem to be suggesting that Debian users now need to read XX > pages of release notes and guides in order to learn that what > they're installing is not what the Debian.org homepage "Why Debian", > "Our Philosophy", and "Who We Are / What We Do" pages are currently > promoting Debian as. > > That's not right. Period. If the Installers are not ALL going to > give users the choice to opt-in or opt-out of non-free components, > then those above-mentioned promotional pages really need to be > updated so as to not be misleading users. I'm saying that _this hasn't changed_ between Bullseye and Bookworm. Reading the release notes or the installation guide has been very strongly recommended practice for a _very_ long time; and the _documented_ behavior of the installer, except for the non-free / non-free-firmware split, is essentially unchanged in this regard. Lambasting the Debian developers with a post on the Debian _users_ mailing list seems to me to be unlikely to lead to the improvements which you clearly seek. Making a _reasoned_ bug report against the appropriate package, _without_ including pages of hyperbole, seems more likely to have a _constructive_ outcome for everyone involved. > But BETTER yet, why not just update all the installers to give users > that choice? That's what I'm strongly suggesting. Something very > wrong/misleading/deceptive is happening right now. If that's what you are suggesting, _I_ suggest to make a wishlist bug report to that effect against the appropriate packages, which is how such suggestions are made and tracked in Debian. Again, _without_ pages of hyperbole which can only serve to annoy and detract from the point you seem to be trying to make. (Yes, I'm sure you feel differently, but consider what is relevant for someone trying to triage or fix an issue rather than your feelings about it.) If you're able to also provide a proposed patch to that effect, then that's even better. I also suggest to please take a moment to read through the Debian Code of Conduct <https://www.debian.org/code_of_conduct>. May I suggest paying particular attention to point 2 "assume good faith" and point 4 "try to be concise"? It's certainly fine to elaborate on the reasoning behind the point you're making, but especially if you elaborate at length (and I would certainly call ~1700 words "at length" in this context), the specific point you're making should ideally be up front so that people can quickly and easily tell what you're talking about and whether that's relevant to them. Consider that a courtesy to the some 3000 people on this list. -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
On Sun 21 Apr 2024 at 21:59:21 (-0400), Stefan Monnier wrote: > > Do you have any suggestion as to which list would be better to contact? > > Original: https://lists.debian.org/debian-user/2024/04/msg00324.html > > Maybe `reportbug debian-installer`? but perhaps without all the deception crap, unless you really mean to impugn the developers' motives. Cheers, David.
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
> Do you have any suggestion as to which list would be better to contact? > Original: https://lists.debian.org/debian-user/2024/04/msg00324.html Maybe `reportbug debian-installer`? Stefan
Re: Debian non-free-firmware policy making OS misleading and Free Software unfriendly
Do you have any suggestion as to which list would be better to contact? Original: https://lists.debian.org/debian-user/2024/04/msg00324.html - Original message - From: fxkl4...@protonmail.com Date: Sunday, April 21, 2024 3:52 PM do you think the debian gods are listening On Sun, 21 Apr 2024, Stefan Monnier wrote: >> If Debian is going to continue promoting itself with those "Our Philosophy" >> and "Why Debian" pages, there should at least be opt-ins during the >> installation process of every Debian download, as well as prominent warnings >> of the new policy on the download pages. > > Agreed. It should be easy to adjust the installation process with an > extra step whether to include/install non-free-firmware or not. > It's also an opportunity to raise awareness of the problem.
