~ sudo DIFFPROG=meld pacdiff|result=
this has no result
➜ ~ pacdiff -o
/etc/passwd.pacnew
/etc/shells.pacnew
/etc/locale.gen.pacnew
/etc/pacman.conf.pacnew
/etc/pam.d/sddm.pacnew
/etc/tlp.conf.pacnew
~ sudo DIFFPROG=meld pacdiff|result=
this has no result
➜ ~ pacdiff -o
/etc/passwd.pacnew
/etc/shells.pacnew
/etc/locale.gen.pacnew
/etc/pacman.conf.pacnew
/etc/pam.d/sddm.pacnew
/etc/tlp.conf.pacnew
ignore /etc/passwd
- or be very, very careful!
/etc/shells
is also not that important
same for /etc/locale.gen
/etc/pacman.conf
I just described above
don’t know about the two others - /etc/tlp.con
f ist just because you made some changes that are now different from the defaults
you can check, but likely just ignore
It is about tracking and incorporating important changes to these sometimes critical configuration files.
If you installed meld:
sudo DIFFPROG=meld pacdiff
…or just:
pacdiff
to run the program.
shows only diff on passwd.pacnew
You have some reading to do. Cheers.
I commented out the two lines:
[community]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
Saved the file, but then:
~ sudo pacman -Syy
:: Synchronizing package databases...
error: failed to synchronize all databases (no servers configured for repository)
comment out this line as well:
[community]
the result should be:
#[community]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
#[community]
#SigLevel = PackageRequired
#Include = /etc/pacman.d/mirrorlist
This solved my problem! Thanks so much.
So, we have a great community, but I have to take it out?!
No.
Like it is now, it is … disabled.
It’s just a comment right now.
(putting a # in front of a line makes it a comment …)
It’s as if it was not there at all.
You may as well take it out.
Noone and nothing needs it anymore - it does not exist anymore.
The issue is I still have Community in /etc/pacman.conf. Comment it out solved the problem. Got it figured out here: Pamac can't remove, install or update - #3
It doesn’t matter whether to press on Choose or Cancel.
I’ll but in one last time:
@XJia you need to pay attention to the Announcements for your branch’s updates. which I presume is the Stable Updates updates.
Also, you mentioned this:
…and it sort of makes me think you just want to point and click. I apologise if I’m wrong. But the fact is that Manjaro, no actually Linux in general, requires a much more hand-on, involved approach. So take a look here, and consider it going forward:
If you find that Manjaro, then probably Linux in general isn’t for you, I recommend Windows to save yourself a lot of headaches.
Though I’ve used Manjaro for over 1 year, I’ve abandoned Windows for 20 years. You need to give wiser recommendation.
Doesn’t look that way from your unhandled .pacnew
files. Or the fact that you don’t like the terminal. Or the fact that you couldn’t sort this relatively common problem on your own.
So excuse me for taking all the evidence into consideration before I make a recommendation. I’ll recommend Gentoo for the next person that asks about Linux, since that’s powerful. Sh1t man, I should’ve given it to my brother since he very rarely uses his computer.
Well it has been ca. 8-9 Months since community is gone…it was kept empty to account for not properly updated machines, but i can understand it will not be kept forever and was taken down. Thanks for the tip, now we know what to expect in the next days in the forum
So, tell us about Gentoo.
Oh, nevermind, it’s wildly off-topic.
You mean update the local databases (but not the system), so that next time they use -S
they could end up in a partial update state.
@XJia If you haven’t already, do a proper update:
sudo pacman -Syu
https://wiki.archlinux.org/title/System_maintenance#Partial_upgrades_are_unsupported
Except that it (quite literally) took me a whole weekend to get a (relatively) basic system, it was good. And back then, the kernel took a lot longer than 5 minutes to compile…
To be fair, that chance is always there if you’re not careful.
If you define “not careful” as updating the databases but not the system.
Although there’s also the possibility of a failed update that was left uncompleted.