I opened a terminal and it didn't work.
Could you perhaps be a little more descriptive?
- What didn’t work?
- Post the command output showing any command entered plus any errors that might have resulted.
- Please engage in a more meaningful way to help others help you.
- The forum is not a one-stop-shop for magical solutions; you are expected to contribute as much as possible.
Quick tip: To have command output display in English, please prefix your commands with LC_ALL=C;
Example: LC_ALL=C sudo pacman -Syu
This is the least helpful wording to describe your issue.
duardo-ax370gaming5 eduardo]# bash recreate-pkg-list.sh -q | tee pkg-list.txt
bash: recreate-pkg-list.sh: Arquivo ou diretório inexistente
[eduardo-ax370gaming5 eduardo]# recreate-pkg-list.sh -q | tee pkg-list.txt
bash: recreate-pkg-list.sh: comando não encontrado
Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text
sudo pacman -Syu ✔
[sudo] senha para eduardo:
:: Sincronizando a base de dados de pacotes...
erro: falha ao sincronizar todas as bases de dados (não foi possível travar a base de dados)
Please read my previous post again and try to understand the quick tip given.
Would you be more comfortable using your native language, or perhaps Spanish? I ask because we can move this topic to another language section, if you like.
Note that responses might be fewer.
Regards.
You tried to run the script when you did not even have it yet. ![]()
Save the content of that script as some file name, then use that name to run the script.
Tip: If your system is not installed in English, then please prefix every command whose output is requested by the helpful volunteers on this forum with “LANG=C”, as in the example below… ![]()
LANG=C pacman -Syu
Alternatively, you can start a new session specifically for running such commands as requested, and enter the command… ![]()
LANG=C
… separately as the first command. You will then no longer need to prefix the following commands with it, because it will set the $LANG variable for the remainder of that command-line session — and only in that terminal, so you need not worry that it would affect the rest of your system.
And how do I do that?
It seems to be working again.
LANG=C sudo pacman -Syu ✔
[sudo] password for eduardo:
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
warning: ckbcomp: local (1.242-1) is newer than extra (1.227-2)
warning: game-devices-udev: local (0.25-0.1) is newer than extra (0.24-1)
warning: pamac-tray-icon-plasma: local (0.1.4-1) is newer than extra (0.1.3-3)
there is nothing to do
You seem to be having difficulty, generally. The following article raises some important issues about using Manjaro:
Try… ![]()
sudo pacman -Syyuu
… just this once.
This does indicate that the system is in an incompletely-maintained state and whilst this particular entry isn’t presently an issue, there are likely other untended .pacnew files.
The output of the following command might reveal something:
pacdiff -o
You are actually asking how you copy/paste the text, the content of the script, which is right there
and how to save that to a file the name of which you are free to choose?
@linux-aarhus said that he saved it as recreate-pkg-list.sh
He said where it came from and linked to it:
the post #8 in the thread on the Arch forum.
And then he described how to use it, assuming you used the same name as he did.
There appear to be many basic skills missing here.
LANG=C pacdiff -0 1 ✘ 4s
zsh: command not found: pacdif
The command, the program, pacdiff is in the package:
pacman-contrib
and it is not installed on your machine
To install it:
sudo pacman -Syu pacman-contrib
(could be difficult in the state your installation is in - will probably not work)
Further:
the command given was:
pacdiff -o
It was not what you wrote:
pacdiff -0
(you wrote the number zero - in the example it was the lower case letter o)
Thus there is no reason to continue.
More specifically there no reason to examine the system to compile a list of packages to rebuild the local metadata.
@Momotaros You may want to prepare yourself for the next incident..
Closed without a clearly acknowledged solution.