Installing Every Arch Package
ta180m.exozy.me
Installing Every Arch Package
1–10 of 90 posts
Re: Installing Every Arch Package
#2Site was barely loading for me, here is a mirror.
Re: Installing Every Arch Package
#3Re: Installing Every Arch Package
#4If you only install supposedly non-conflicting packages, and there are conflicting file locations, isn't that a packaging bug?
Re: Installing Every Arch Package
#5https://archive.is/lQHf0 Site was barely loading for me, here is a mirror.
Re: Installing Every Arch Package
#6If you only install supposedly non-conflicting packages, and there are conflicting file locations, isn't that a packaging bug?
Re: Installing Every Arch Package
#7If you only install supposedly non-conflicting packages, and there are conflicting file locations, isn't that a packaging bug?
> As we used a lot of unsafe hacks (disabling dependency and file conflict checking, for instance) to get this to actually work, I wouldn’t recommend using this system for anything other than proving it’s possible.
Re: Installing Every Arch Package
#8If you only install supposedly non-conflicting packages, and there are conflicting file locations, isn't that a packaging bug?
Sounds like it, yeah.
I've been using Pacman for years never had a single problem with conflicts or anything else.
Re: Installing Every Arch Package
#9https://archive.is/lQHf0 Site was barely loading for me, here is a mirror.
Re: Installing Every Arch Package
#10If you only install supposedly non-conflicting packages, and there are conflicting file locations, isn't that a packaging bug?
> Investigate the file conflicts and file some Arch Linux bugs.
with a link to https://bugs.archlinux.org/task/73574, which is indeed a bug in the packaging script (it fails to consider python version 3.10 because it only globs 3.?).