Timeline for Install pacman on live OS to fix kernel panic caused by package upgrade
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 11, 2018 at 20:35 | comment | added | jasonwryan | There is, unsurprisingly, a wiki page for Node where all these options are described. | |
| Jul 11, 2018 at 20:33 | comment | added | Post Self | Ok, thanks for the tip, but all search results for virtualenv get me to Python (wiki.archlinux.org/index.php/Python/Virtual_environment) do you mean this? | |
| Jul 11, 2018 at 18:59 | comment | added | jasonwryan | Yes, it is a bad thing. Pacman is your package manager, installing things behind its back is always a bad idea. If you have to use pip/npm/gem do it in a virtualenv. | |
| Jul 11, 2018 at 18:49 | comment | added | Post Self | Yes, is that a bad thing? Why actually are the packages available on pacman, then? | |
| Jul 11, 2018 at 17:53 | comment | added | jasonwryan | The conflicts were because you used npm to install packages, not pacman. | |
| Jul 11, 2018 at 17:00 | history | edited | Post Self | CC BY-SA 4.0 | added 28 characters in body |
| Jul 11, 2018 at 16:59 | comment | added | Post Self | Hm, interesting. It did not break anything and my alternative was going through each conflict. All conflicting packages were from node anyways, so I can fix it easily if something should not be functioning | |
| Jul 11, 2018 at 16:03 | comment | added | jasonwryan | NEVER run -Syu with --force: it will break your system. That is why that switch has been deprecated. | |
| Jul 11, 2018 at 12:15 | history | edited | Post Self | CC BY-SA 4.0 | added 17 characters in body |
| Jul 11, 2018 at 11:56 | history | answered | Post Self | CC BY-SA 4.0 |