Usually you shouldn't just use -Sy (partial upgrade) and should instead use -Syu (full upgrade), or else it might cause dependency issues, but upgrading archlinux-keyring is one of the exceptions when this is fine, at least as long as you follow up with -Syu again.
@@xrafter never happened to me, so I don't know. Arch Wiki says -Sy is unsupported and actively recommends -Syu instead. I'm not entirely sure, but in such case of dropping support, wouldn't the package be moved to the AUR? I remember this happened to anki. If I understand correctly, the responsibility of managing dependencies to match legacy versions when a breaking update happens is then on the maintainer. In any case, breaking a single unsupported package is better than breaking packages system-wide.
what can happen if you are a long time without updating is that you have a big update that includes essential or sensitive packages such as the kernel, if your pc is not very powerful it could freeze and you will have to restart (because the task execution queue could saturate the cpu), when you reboot you may have a kernel panic or boot problems, that happened to me when I didn't use my 2008 laptop for months, I was testing how endeavors worked, update (approx 2~3 GB) that It included the kernel and other base packages (I don't remember which ones), the laptop froze when it had to update the kernel, rebooted and had boot problems and then a kernel panic (that was the first and last time I had a kernel panic), I didn't mind at all since I was just testing how it worked before definitely moving to arch. Maybe the problem was something else since my laptop is a Dell Latitude 6400 (well known for having thermal throttling problems due to the BIOS), a pretty bad one but it's the only one I have :c
the y is telling pacman to refresh all package databases, so this is the same as apt update and the u upgrades all packages and this is the same as apt upgrade it is not a partial upgrade, please before you write stuff, read the man, so new to linux users learn stuff the right way i got no problem with you think it is a partial update it is your system, you do you, just keep your crazy to your self that is all 😉
@@zeocamo Refreshing package databases without upgrading is exactly what the Arch Wiki defines as a partial upgrade, if you actually go read it (e.g. under the System_maintenace page), because any subsequent package installation (or individual upgrade) risks a dependency upgrade, which might break other packages. If you follow up with -Syu (or just -Su), as stated in the original comment, it is fine because you did a full upgrade. A partial upgrade is installing or upgrading anything between those commands. Please, before you write stuff, read the docs, so new linux users don't break their system because of a comment lacking in description. I've got no problem with you, you think it isn't a partial upgrade, it's your system, you do you. Just keep your crazy to yourself, that is all ;)
Hey DT. Thanks for the great content. Funny thing, just yesterday I ran into the exact same problem with the keyring for the first time. Fortunately, Archwiki came to help. You won't believe it but it was your efforts in promoting free and open-source software that lead me to the world of Linux. I am a general physician!!! My main problem was with windows and its unstable updates and its inferior command-line capabilities which interrupted my work as a researcher who heavily uses data analysis and works with large databases. I am sure you have a wide variety of audiences from all over the world with different professions. All the best.
I have two remarks: - You should check first if there is a pacman running before simply deleting the /var/lib/pacman/db.lck (that's the whole purpose of this lockfile - to avoid parallel access to the pacman sync and database structures) - there is pacman-static in the AUR. This is a statically linked version of pacman which is really helpful when you by accident render your normal pacman unusable (say, partial upgrading a glibc).
Since you're using ArcoLinux, you can use `fixkey` alias in the terminal to fix the PGP signature error... There is also an alias for removing db.lck but i forgot it, you can check it in your aliases.
Those are only the default aliases. He uses his own bash/zsh/fish config with his own aliases and everything so unless he has them in his config as well he won’t have those.
Hey DT, Many thanks for the excellent content as always. I have been looking for a solution to my failing updates on and off for the past 3 months without any luck until today. Keyring update solved it for me. As a experimenting Arch user I am a big fan of the content you provide and the knowledge you impart to users like myself. You are a legend!
This happened to me this morning, I did a few searches and found in a thread from 2009 that the solution was to update only that package (the problem was another but it still worked), nice video btw
Those tips were great, DT, thanks. I ran into that import key issue but didn't thought about upgrading the keyring. Don't even remember how I solved it. In addition to the hook to clean the pkg cache, I wrote a script to also clean the pkg cache from paru.
Sep 13: Thank you very much for this fix I decided to re-install Manjaro on my computer and I noticed that i had a big update and it wouldn't update at all till i found this video, now its updating just fine .....THANK YOU
I hear it shouldn't be an issue if you update regularly, but the fix is pretty simple. As for automating it, I don't know enough about the process to say if there aren't any cons to doing it, but I'm guessing it would have issues with security and/or portability.
Most Arch based distros will also have their own *-keyring files for their keys. It's not always the arch-keyring that raises the problem from the first part of the video.
so what the heck do you do when syncing archlinux-keyring wont go through because, guess what, corrupted file/invalid PGP signature on the archlinux-keyring package itself?
That Pacman keys error has been happening way to much lately. At least once a month lately for me... :-( I also have a hook that runs and cleans mine too! Lol Oh hell thoses Haskil files, 200 updates and 190 of them are the little Haskel files... HaHAHAhA... OK, sure the pacman crunching sound would be neat the first time but after 200 times it would not be so cute... 🕹️🕹️🕹️ Thanks DT for sharing the fix! LLAP 🖖
Clean pacman cache. It is not recommended to make hook after each update to clean whole cache. Sometimes you need downgrade the package or there is something corrupted and you need fast revert. Good practice is to keep 2 or 3 last versions of packages in the system. Clean whole cache is important to call MANUALLY according to your full working system and available disk space. Additional note, paccache without parameter keeps last 3 versions, it is much more better if you plan some automatic solutions.
I had this problem and it took a bit long to find an answer (like 5 minutes). Pacman should tell us to update the keyring first (or even do it automatically). Also, I don't understand what the keyring actually is, you could have explained it in this video!
Finally! DT uses vim 😎 I've had a bunch of commands to keep track of my pacman cache involving paccache. I've never cared about pacman hooks. That looks brilliant, I need to look into that. However, one should also keep track of AUR helpers (paru, yay) that use their own dedicated cache. I've recently cleaned out 70 GB of rubbish out of that folder.
It's strange I see him using vim in almost every video. When he's doing any admin or new system it's always his default. Not sure why everyone thinks he doesn't. I've only seen him using emacs for long coding videos on his own system.
Thanks for sharing bro! What about when you get asked yes or no questions a thousand times? For instance ......Replace appstream-qt with extra/appstream-qt5? And it never ends!
Just had a problem with this earlier. although I did find the fix on the arch wiki, if feels like you read my mind right there. edit: Oh, turns out the same package was acting up. Makes sense
Indeed paccache is available via pacman-contrib. I've been able to sync regular arch repos fine with Artix Linux. I'm not sure if it's where I am located but with debian/devuan I've always had repo problems where I am located when I lived up north the debian repos would sync fine. Just something I have thought about with the video. For whatever reason arch repos are the most responsive where I am located.
Use to have that same problem with Debian occasionally, and on occasion years ago with Firefox, it use to have a 'lock' file and would have to delete it in order to get Firefox to start back up. Would keep saying it was already running.
I actually had this exact issue on Arcolinux, I really had to delve deep into the google-ocean to get down to something that resolved it..aand it worked..aand I wished I was not as sloppy writing notes so I could remember the working solution for the next time it will happen.
I wonder if it’s good practice to use a hook to tell pacman to reboot the system every time a kernel is upgraded - something like: [Trigger] Operation = Upgrade Type = Package Target = linux* [Action] Description = Rebooting into new kernel… When = PostTransaction Exec = /usr/bin/systemctl reboot Then again, not a fan of having work interrupted in this way - although it looks like you’ve got “reboot-important-updates.hook” yourself.
I turned mine into a hybrid drive. 256 GB SSD for root and 512 GB HDD for home. Copied my entire home folder to the HDD and updated my fstab. I'm not going to run out of room anytime soon.
sudo paccache -rk0 removes all cached installed packages. That's my default. Especially chromebooks that sometimes don't have enough storage to even update.
i swear i had to format my disk last night and since i didnt have much time to install arch manually i tried to install the ones that provide an installer...I swear i formatted my disk 12 times from 11pm last night to 3pm today because i wasnt able to find a way around the pgp signature tingy ,and in the end i ended up installing arch manually to make it work...Only if this video was available 24h ago...Either way thanks! We're probably going to need it soon again!
I think the most obvious step was to just go and read the wiki. wiki.archlinux.org/title/Pacman#"Failed_to_commit_transaction_(invalid_or_corrupted_package)"_error
Oh no no no. Do NOT delete the lock file unless you are EXTRA sure that you're not running another program that's performing a mutable operation using pacman (e.g. paru, pamac). You are potentially introducing an extremely dangerous race condition that could break your system without recourse. Run-once scripts could be run twice, TOCTOU will likely occur; in general just a unpredictable and unrecoverable mess of a situation that you DO NOT want to end up in. If you don't understand what any of this means and just want the issue fixed, do me a favour and just reboot first, then delete the lock file if still necessary. This will greatly reduce your risk.
I tend to ps aux | grep pacman or something like to understand issue than first kill process than delete the lock. It also happens in apt too. Generally dumb apps like systems own app store causes this. For example ubuntu and manjaro did that.
@Distrotube - hey there's some guy on TH-cam Ergewbai Sultanov who copying and publishing your videos constantly, maybe do something with this?? I know your videos are creative licences but he don't even write that you are creator of that.
DT you should be given knighthood status for (bad ass)ory by the Queen or Linus Torvald or somebody like that. You just saved my ass, and I thank you for it. I'm a nobody or I'd do it myself 😄
Hmm. You’re giving me the distinct impression that pacman is a very haphazardly designed package manager that throws a lot of errors for stuff it should automatically handle, and doesn’t know how to clean up after itself. Think I’ll stick with apt and dnf, BTW. They’ve never given me problems like this.
Hey dt, hope you'll be doing fine. Can you please make a course like playlist where you teach "How to build your Arch Linux from scratch" just the way you setup all of your window manager, xmonad, xmobar and system trays etc. That will be great if you do so because it will teach all of us how to create our own systems the way we like and also makes us way more familiar with how the linux works underneath and all. Because i think it's time for all of us to stop being a script kitty and start acting like a pro user, such as yourself.
Hopefully you read these. I have no idea why people use arch despite it breaking constantly. Do you like the challenge and like to learn how to fix things? Because the only thing I hear from arch users is that its stable, but when you look at the "new" category in arch 99% of it is tech support.
I mean, if you're really dumb then sure, this might be disastrous. However, speaking as someone who's only been using Arch for a couple of months, I encountered this same error with this same package yesterday, so I simply looked it up on the Arch wiki, where it's clearly documented along with the solution, and fixed it myself within two minutes, having never seen it before or having a clue what it was. Then I got on with my day.
@@CaptainKenway no pacman should be more smart when I first started to use linux package managers were awful, still there are cases and issues to iron out but we came a long way for sure, also instead of creating detailed manuals for damn near all issues we should fix dependency resolution and hierarchy. Manuals should be there don't get me wrong but also if issue is document and understand enough to be placed in a wiki it should be patched. I know it is hard to catch all cases (damn hate myself to be honest) there is no excuse. After all package manager is the heart of any distro.
@@CaptainKenway well good for you and yes reading the wiki will help resolve the issue but why is this a problem in the first place. OS should always “just work” and users shouldn’t have to be troubleshooting core functionality. This was a failure on arch and not the user.
![ประสบการณ์ จ้าง Developer ที่ผมจะไม่มีวันลืม [ภาค2]](http://i.ytimg.com/vi/pZbsSDRrmXA/mqdefault.jpg)
Usually you shouldn't just use -Sy (partial upgrade) and should instead use -Syu (full upgrade), or else it might cause dependency issues, but upgrading archlinux-keyring is one of the exceptions when this is fine, at least as long as you follow up with -Syu again.
Doesn't -Syu break old packages that no longer maintained tho?
@@xrafter never happened to me, so I don't know. Arch Wiki says -Sy is unsupported and actively recommends -Syu instead.
I'm not entirely sure, but in such case of dropping support, wouldn't the package be moved to the AUR? I remember this happened to anki. If I understand correctly, the responsibility of managing dependencies to match legacy versions when a breaking update happens is then on the maintainer. In any case, breaking a single unsupported package is better than breaking packages system-wide.
what can happen if you are a long time without updating is that you have a big update that includes essential or sensitive packages such as the kernel, if your pc is not very powerful it could freeze and you will have to restart (because the task execution queue could saturate the cpu), when you reboot you may have a kernel panic or boot problems, that happened to me when I didn't use my 2008 laptop for months, I was testing how endeavors worked, update (approx 2~3 GB) that It included the kernel and other base packages (I don't remember which ones), the laptop froze when it had to update the kernel, rebooted and had boot problems and then a kernel panic (that was the first and last time I had a kernel panic), I didn't mind at all since I was just testing how it worked before definitely moving to arch.
Maybe the problem was something else since my laptop is a Dell Latitude 6400 (well known for having thermal throttling problems due to the BIOS), a pretty bad one but it's the only one I have :c
the y is telling pacman to refresh all package databases, so this is the same as apt update and the u upgrades all packages and this is the same as apt upgrade
it is not a partial upgrade, please before you write stuff, read the man, so new to linux users learn stuff the right way
i got no problem with you think it is a partial update it is your system, you do you, just keep your crazy to your self that is all
😉
@@zeocamo Refreshing package databases without upgrading is exactly what the Arch Wiki defines as a partial upgrade, if you actually go read it (e.g. under the System_maintenace page), because any subsequent package installation (or individual upgrade) risks a dependency upgrade, which might break other packages.
If you follow up with -Syu (or just -Su), as stated in the original comment, it is fine because you did a full upgrade. A partial upgrade is installing or upgrading anything between those commands. Please, before you write stuff, read the docs, so new linux users don't break their system because of a comment lacking in description.
I've got no problem with you, you think it isn't a partial upgrade, it's your system, you do you. Just keep your crazy to yourself, that is all ;)
Hey DT. Thanks for the great content. Funny thing, just yesterday I ran into the exact same problem with the keyring for the first time. Fortunately, Archwiki came to help. You won't believe it but it was your efforts in promoting free and open-source software that lead me to the world of Linux. I am a general physician!!! My main problem was with windows and its unstable updates and its inferior command-line capabilities which interrupted my work as a researcher who heavily uses data analysis and works with large databases. I am sure you have a wide variety of audiences from all over the world with different professions. All the best.
I have two remarks:
- You should check first if there is a pacman running before simply deleting the /var/lib/pacman/db.lck (that's the whole purpose of this lockfile - to avoid parallel access to the pacman sync and database structures)
- there is pacman-static in the AUR. This is a statically linked version of pacman which is really helpful when you by accident render your normal pacman unusable (say, partial upgrading a glibc).
When I watch DT with the slanted camera angle I often think I'm watching a Batman villain in his lair using Arch.
Since you're using ArcoLinux, you can use `fixkey` alias in the terminal to fix the PGP signature error... There is also an alias for removing db.lck but i forgot it, you can check it in your aliases.
Those are only the default aliases. He uses his own bash/zsh/fish config with his own aliases and everything so unless he has them in his config as well he won’t have those.
They're available if you are using arco, and he is... But making your own is cool too!
This is such a lifesaver! I had this once happen, and I was like, 'well, what do I do now?' This was very helpful - thank you Derek!
I don't even use any arch based distros but still watched til the end 🤣. Great content as always DT!
Hey DT, Many thanks for the excellent content as always. I have been looking for a solution to my failing updates on and off for the past 3 months without any luck until today. Keyring update solved it for me. As a experimenting Arch user I am a big fan of the content you provide and the knowledge you impart to users like myself. You are a legend!
This happened to me this morning, I did a few searches and found in a thread from 2009 that the solution was to update only that package (the problem was another but it still worked), nice video btw
Those tips were great, DT, thanks.
I ran into that import key issue but didn't thought about upgrading the keyring. Don't even remember how I solved it.
In addition to the hook to clean the pkg cache, I wrote a script to also clean the pkg cache from paru.
Yep. This saved me. This should get a lot of views. Very very useful info, thanks man!
Sep 13: Thank you very much for this fix I decided to re-install Manjaro on my computer and I noticed that i had a big update and it wouldn't update at all till i found this video, now its updating just fine .....THANK YOU
Pacman should repopulate keys automatically. What do you think?
Seconded. I'm guessing there may be reasons why it doesn't, but I can't think of any.
I hear it shouldn't be an issue if you update regularly, but the fix is pretty simple. As for automating it, I don't know enough about the process to say if there aren't any cons to doing it, but I'm guessing it would have issues with security and/or portability.
Ole ole y ole thank you very much !! The key error was messing up with me xD really good video!
Literally manually empty the cache in /var/ and redownload keys
Update the keys, refresh pacman
Problem solved.
Gigantic kek
Hilarious. I got this same exact error just minutes before I started watching your video. Good timing! 🙂
Thankyou man! The keyring soultion really did it for me. God bless, you have no idea what big problem you had solved for me!
i encountered this today and look it's even the same error package lol
Edit: Thanks DT for making this video very informative ❤️❤️
Most Arch based distros will also have their own *-keyring files for their keys. It's not always the arch-keyring that raises the problem from the first part of the video.
Is there any reason why pacman can't solve keyring error by itself?
so what the heck do you do when syncing archlinux-keyring wont go through because, guess what, corrupted file/invalid PGP signature on the archlinux-keyring package itself?
Asking the important questions here.
This helped me out a lot, great show
That Pacman keys error has been happening way to much lately. At least once a month lately for me... :-(
I also have a hook that runs and cleans mine too! Lol Oh hell thoses Haskil files, 200 updates and 190 of them are the little Haskel files... HaHAHAhA...
OK, sure the pacman crunching sound would be neat the first time but after 200 times it would not be so cute... 🕹️🕹️🕹️
Thanks DT for sharing the fix!
LLAP 🖖
Clean pacman cache. It is not recommended to make hook after each update to clean whole cache. Sometimes you need downgrade the package or there is something corrupted and you need fast revert. Good practice is to keep 2 or 3 last versions of packages in the system. Clean whole cache is important to call MANUALLY according to your full working system and available disk space. Additional note, paccache without parameter keeps last 3 versions, it is much more better if you plan some automatic solutions.
I had this problem and it took a bit long to find an answer (like 5 minutes). Pacman should tell us to update the keyring first (or even do it automatically). Also, I don't understand what the keyring actually is, you could have explained it in this video!
i ran all of your commands and still when i do a pacman -Syu it gives me a corrupted file error and if i delete y/N i say yes to all then errors out?!
Great timing, just ran into this today 😂
Thanks a lot DT this is very helpful now I know what I’ve to do if I have an issue. Take care
a completely other question, installing Solus on virtualbox 6.1 doesnt work , what settings in vbox can be done?
why dont they just make pacman update the keyring package before everything else?
Finally! DT uses vim 😎
I've had a bunch of commands to keep track of my pacman cache involving paccache. I've never cared about pacman hooks. That looks brilliant, I need to look into that.
However, one should also keep track of AUR helpers (paru, yay) that use their own dedicated cache. I've recently cleaned out 70 GB of rubbish out of that folder.
It's strange I see him using vim in almost every video. When he's doing any admin or new system it's always his default. Not sure why everyone thinks he doesn't. I've only seen him using emacs for long coding videos on his own system.
paccache command not found ... EDIT:- Ok now I installed pacman-contrib package ...
You gotta give a thumbs up everytime you learn something new!
"I don't wanna talk any louder, but I could been proving myself that it's harder to fine tune the bits when a bigger stream is floating..."
I get the same error when I try to run sudo pacman -Sy archlinux-keyring , what to do now ?
error: failed to synchronize all databases (no servers configured for repository).How to solve this..please help
same error when I update today! Thank you!
sudo pacman -Syu
:: Synchronising package databases...
error: failed to synchronize all databases (unable to lock database)
is it possible to make a preTransitionHook and install arch-linux-keyring before any other operation also?
Thanks for sharing bro! What about when you get asked yes or no questions a thousand times?
For instance ......Replace appstream-qt with extra/appstream-qt5?
And it never ends!
I had a keyring error with a few extra packages. I was worried for a sec until I tried just updating the keyring before the update itself.
I am stuck with this and I can not seem to solve it any suggestions please I am pulling my hair out. error: key "xxxx" could not be looked up remotely
Just had a problem with this earlier. although I did find the fix on the arch wiki, if feels like you read my mind right there.
edit: Oh, turns out the same package was acting up. Makes sense
It did happen to me too today and I did (sudo pacman -Sy archlinux-keyring) and it did work. Since it is not the first time I encountred this problem.
Do any of these work for the failed retrieving core.db error
I had the same issue few days ago, I've logged in as a root, cleared the pacman cache and then did the Syu and it worked.
ah yes the arch-keyring thing. so annoying when u forget that it exists lol
I'm guessing there is a place that you put these so people can get a good look at some examples of these files and formats?
to run paccache, install pacman-contiib package first.
Thanks a lot, great video, I'll save it for the future needs
Indeed paccache is available via pacman-contrib. I've been able to sync regular arch repos fine with Artix Linux. I'm not sure if it's where I am located but with debian/devuan I've always had repo problems where I am located when I lived up north the debian repos would sync fine. Just something I have thought about with the video. For whatever reason arch repos are the most responsive where I am located.
Use to have that same problem with Debian occasionally, and on occasion years ago with Firefox, it use to have a 'lock' file and would have to delete it in order to get Firefox to start back up. Would keep saying it was already running.
It sounds better to me to have separate hook for remove, that is clearing all of cached files for the package being removed.
Is like my mirrors in debían repository is not working
I actually had this exact issue on Arcolinux, I really had to delve deep into the google-ocean to get down to something that resolved it..aand it worked..aand I wished I was not as sloppy writing notes so I could remember the working solution for the next time it will happen.
You're a legend DT 🏆
I wonder if it’s good practice to use a hook to tell pacman to reboot the system every time a kernel is upgraded - something like:
[Trigger]
Operation = Upgrade
Type = Package
Target = linux*
[Action]
Description = Rebooting into new kernel…
When = PostTransaction
Exec = /usr/bin/systemctl reboot
Then again, not a fan of having work interrupted in this way - although it looks like you’ve got “reboot-important-updates.hook” yourself.
maybe instead of rebooting you can notify-send a reminder to reboot the system
Haha I see all of us had the same issue on the same day lmao, classic keyring issue
I turned mine into a hybrid drive. 256 GB SSD for root and 512 GB HDD for home. Copied my entire home folder to the HDD and updated my fstab.
I'm not going to run out of room anytime soon.
sudo paccache -rk0 removes all cached installed packages. That's my default. Especially chromebooks that sometimes don't have enough storage to even update.
i swear i had to format my disk last night and since i didnt have much time to install arch manually i tried to install the ones that provide an installer...I swear i formatted my disk 12 times from 11pm last night to 3pm today because i wasnt able to find a way around the pgp signature tingy ,and in the end i ended up installing arch manually to make it work...Only if this video was available 24h ago...Either way thanks! We're probably going to need it soon again!
I think the most obvious step was to just go and read the wiki.
wiki.archlinux.org/title/Pacman#"Failed_to_commit_transaction_(invalid_or_corrupted_package)"_error
Oh no no no. Do NOT delete the lock file unless you are EXTRA sure that you're not running another program that's performing a mutable operation using pacman (e.g. paru, pamac). You are potentially introducing an extremely dangerous race condition that could break your system without recourse. Run-once scripts could be run twice, TOCTOU will likely occur; in general just a unpredictable and unrecoverable mess of a situation that you DO NOT want to end up in.
If you don't understand what any of this means and just want the issue fixed, do me a favour and just reboot first, then delete the lock file if still necessary. This will greatly reduce your risk.
I tend to ps aux | grep pacman or something like to understand issue than first kill process than delete the lock. It also happens in apt too. Generally dumb apps like systems own app store causes this. For example ubuntu and manjaro did that.
Excellent, I run on this key error the other day and couldn’t find a solution on line.
I get the pgp error when installing the keyring aswell
Wow. Thanks for sharing.
didn't know about paccache -r, that cleared out 21GB for me haha
@Distrotube - hey there's some guy on TH-cam Ergewbai Sultanov who copying and publishing your videos constantly, maybe do something with this?? I know your videos are creative licences but he don't even write that you are creator of that.
DT you should be given knighthood status for (bad ass)ory by the Queen or Linus Torvald or somebody like that. You just saved my ass, and I thank you for it. I'm a nobody or I'd do it myself 😄
Hmm. You’re giving me the distinct impression that pacman is a very haphazardly designed package manager that throws a lot of errors for stuff it should automatically handle, and doesn’t know how to clean up after itself. Think I’ll stick with apt and dnf, BTW. They’ve never given me problems like this.
Hey dt, hope you'll be doing fine. Can you please make a course like playlist where you teach "How to build your Arch Linux from scratch" just the way you setup all of your window manager, xmonad, xmobar and system trays etc. That will be great if you do so because it will teach all of us how to create our own systems the way we like and also makes us way more familiar with how the linux works underneath and all. Because i think it's time for all of us to stop being a script kitty and start acting like a pro user, such as yourself.
i love these kind of videos
Majaro user all ears here !
how did i not know about -Scc
Hopefully you read these. I have no idea why people use arch despite it breaking constantly. Do you like the challenge and like to learn how to fix things? Because the only thing I hear from arch users is that its stable, but when you look at the "new" category in arch 99% of it is tech support.
I love you! thank you.
Happened to me recently too
hi
oh im used to these issues
And this ladies and gentlemen, is why you don’t run bleeding edge for daily use.
I mean, if you're really dumb then sure, this might be disastrous. However, speaking as someone who's only been using Arch for a couple of months, I encountered this same error with this same package yesterday, so I simply looked it up on the Arch wiki, where it's clearly documented along with the solution, and fixed it myself within two minutes, having never seen it before or having a clue what it was. Then I got on with my day.
@@CaptainKenway no pacman should be more smart when I first started to use linux package managers were awful, still there are cases and issues to iron out but we came a long way for sure, also instead of creating detailed manuals for damn near all issues we should fix dependency resolution and hierarchy. Manuals should be there don't get me wrong but also if issue is document and understand enough to be placed in a wiki it should be patched. I know it is hard to catch all cases (damn hate myself to be honest) there is no excuse. After all package manager is the heart of any distro.
@@CaptainKenway well good for you and yes reading the wiki will help resolve the issue but why is this a problem in the first place. OS should always “just work” and users shouldn’t have to be troubleshooting core functionality. This was a failure on arch and not the user.
Thank u
early
For those interested, since pacman 6.0 a new conf is available : ParallelDownloads = X
Saves a lot of time when upgrading.
Always amazing DT. BTW recompile-xmondad fail to recompile lately.
sudo su
apt-get update && apt-get upgrade -y