Menú alternativo
Toggle preferences menu
Menú alternativo personal
No has accedido
Tu dirección IP será visible si haces alguna edición

Diferencia entre revisiones de «Arch Linux»

De TechShareRoom wiki
Línea 18: Línea 18:


== Solución a problemas ==
== Solución a problemas ==
*Downgrade a package - [https://ostechnix.com/downgrade-package-arch-linux/ How To Downgrade A Package] - [https://www.makeuseof.com/prevent-packages-from-getting-updated-arch-linux/ How to Prevent Packages From Getting Updated in Arch Linux]
=== Downgrade a package ===
*[https://ostechnix.com/downgrade-package-arch-linux/ How To Downgrade A Package]
*[https://www.makeuseof.com/prevent-packages-from-getting-updated-arch-linux/ How to Prevent Packages From Getting Updated in Arch Linux]


*Failed to commit transaction
=== Failed to commit transaction ===
  <nowiki>error: failed to commit transaction (conflicting files)
  <nowiki>error: failed to commit transaction (conflicting files)
python-commonmark: /usr/lib/python3.10/site-packages/commonmark-0.9.1.dist-info/LICENSE exists in filesystem</nowiki>
python-commonmark: /usr/lib/python3.10/site-packages/commonmark-0.9.1.dist-info/LICENSE exists in filesystem</nowiki>
or
<nowiki>error: failed to commit transaction (conflicting files)
node-gyp: /usr/lib/node_modules/node-gyp/node_modules/tar/node_modules/minipass/index.mjs exists in filesystem</nowiki>


Solución 1:
Solución 1:
Línea 32: Línea 39:
  <nowiki>sudo rm /usr/lib/python3.10/site-packages/commonmark-0.9.1.dist-info/LICENSE</nowiki>
  <nowiki>sudo rm /usr/lib/python3.10/site-packages/commonmark-0.9.1.dist-info/LICENSE</nowiki>


*Failed to write file
or
 
<nowiki>sudo rm /usr/lib/node_modules/node-gyp/node_modules/tar/node_modules/minipass/index.mjs</nowiki>
 
=== Failed to prepare transaction (could not satisfy dependencies)  ===
For example you have this message:
 
installing kio5 (5.111.0-1) breaks dependency 'kio' required by kfiredragonhelper
 
You have to:
 
<nowiki>sudo pacman -R kfiredragonhelper</nowiki>
 
Then, update your system normally and remove each time required packages if you don´t use them.
 
=== Failed to write file ===
  <nowiki>Failed to write file "/sys/module/pcie_aspm/parameters/policy": Operation not permitted
  <nowiki>Failed to write file "/sys/module/pcie_aspm/parameters/policy": Operation not permitted
error: command failed to execute correctly</nowiki>
error: command failed to execute correctly</nowiki>
Línea 40: Línea 62:
You have to use pcie_aspm=force as boot parameter if support, or use pcie_aspm=off if not support.
You have to use pcie_aspm=force as boot parameter if support, or use pcie_aspm=off if not support.


*Possibly missing firmware
=== Possibly missing firmware ===
  <nowiki>WARNING: Possibly missing firmware for module</nowiki>
  <nowiki>WARNING: Possibly missing firmware for module</nowiki>


Solución: Pendiente
Solución: Pendiente

Revisión del 02:06 1 nov 2023

KDE

Recursos

Mantenimiento

Reparación

Solución a problemas

Downgrade a package

Failed to commit transaction

error: failed to commit transaction (conflicting files)
python-commonmark: /usr/lib/python3.10/site-packages/commonmark-0.9.1.dist-info/LICENSE exists in filesystem

or

error: failed to commit transaction (conflicting files)
node-gyp: /usr/lib/node_modules/node-gyp/node_modules/tar/node_modules/minipass/index.mjs exists in filesystem

Solución 1:

sudo pacman -S npm --overwrite '/usr/lib/node_modules/npm/*'

Solución 2:

sudo rm /usr/lib/python3.10/site-packages/commonmark-0.9.1.dist-info/LICENSE

or

sudo rm /usr/lib/node_modules/node-gyp/node_modules/tar/node_modules/minipass/index.mjs

Failed to prepare transaction (could not satisfy dependencies)

For example you have this message:

installing kio5 (5.111.0-1) breaks dependency 'kio' required by kfiredragonhelper

You have to:

sudo pacman -R kfiredragonhelper

Then, update your system normally and remove each time required packages if you don´t use them.

Failed to write file

Failed to write file "/sys/module/pcie_aspm/parameters/policy": Operation not permitted
error: command failed to execute correctly

Solución:

You have to use pcie_aspm=force as boot parameter if support, or use pcie_aspm=off if not support.

Possibly missing firmware

WARNING: Possibly missing firmware for module

Solución: Pendiente