I completely agree. I tried switching to Linux a few times in high school (early-mid '00s), and always had false starts with Fedora or Ubuntu. Usually the package manager would break and everything would fall to pieces. I ended up installing Arch as a Subversion server for some personal projects, and that's what finally made it click.
I use Arch exclusively at work and at home. I do Linux development, which means I have to test out our product on other distros, usually Ubuntu. Eight-plus years later, and Ubuntu's package manager still falls over nine times out of ten. Fedora falls over. Mint falls over. I don't know what I'm doing wrong.
Arch Just Works. It's dead simple, requires very little maintenance, and when something does go wrong (maybe once a year), it's easy to fix or roll back. Arch is just files on a hard drive, not some nebulous set of five different package sources and databases and "releases" and blech.
Although many years ago I had problems when updating, in the recent years everything just works and I don't need to worry about upgrading the whole distro every 6 months.
Unavailable dependencies from mirrors.
Girlfriends OpenSUSE for example ran fine for a few months and now its stuck in an infinite update/upgrade loop or whatever it is trying to do - I really dont have the time to look into it. But the problem is, zypper cant update but really wants to update. Most likely it is conflicts between different repositories, or unavailable shit from some repository. But how useful would OpenSUSE be without the ability to play mp3 files?
So all her programs are now outdated, getting older and older.
Ive seen the same on most .deb based distros Ive tried - failure to update/upgrade a package or collection of packages - breaks the entire system.
Oh you ran apt-get install something previously? Well now that failed, and I will not let you continue until you resolve the issue, the other package will be REMOVED, and the current package cannot be installed, but for an update is who the fuck cares stfu ragequit* * (installs archlinux).
ha. ha ha ha. so many things in effing all distros that are complete and utter ux fuster clucks.
Further, it might seem arcane to have to type "apt-get install -f" to install dependencies for an autonomous .deb package, but I'm not sure how different that is from having to learn, for example, the myriad switches for pacman.
Pacman doesnt leave me with a broken package-manager when a package fails to install. For example
pacman -S thatprogram
and if it fails, then next time I do pacman -S otherpgoram or pacman -Syu
it goes fine, there is nothing from thatprogram which complains or bugs me. Unlike Ubuntu/Debian where
apt-get install fail
and thus everything I try to do now will fail unless I resolve the fail.
pacman also has far less switches, at least I know only of -Q -Qs -S -Ss -Sy -U and -Ql | grep for something Im looking for. Thats all I need to know really. Like 4 or 5 switches/commands.
But look at apt,
apt-get {things here but not search!} {ugh so many switchs here} apt-{what its not really called search!?} dpkg-{jesus-christ-so-many-options}
This is exactly why I detest apt.
Our products at my last company ran Ubuntu and Mint. I detested dealing with the package manager.
I wrote so much stuff to get around apt when dealing with software packages. I wrote a Maven-based update system (with user-friendly wrappers) for pulling down updates on customer units, and my boss wrote an SVN-based solution for internal dev work. I wrote our own validation system to determine if a package can be safely installed, and if it passed, it'd get shoved in with dpkg -i --force-all, because I didn't trust dpkg to do it itself. I wrote a meta-package system (basically a tarball of debs + a manifest file) so I could guarantee atomic installation (read the manifest, verify every deb in the metapackage, and abort before installing anything if even a single package fails verification).
> pacman also has far less switches, at least I know only of -Q -Qs -S -Ss -Sy -U and -Ql | grep for something Im looking for. Thats all I need to know really. Like 4 or 5 switches/commands.
-Qo is pretty useful, too.
Which means you didn't try Debian stable. deb based or not doesn't matter, all that matters is distribution policies on packaging, migrations and releases.
What is the nginx version for Debian stable, is it even in the repositories yet?
> What is the nginx version for Debian stable, is it even in the repositories yet?
It's none of my business to stop you from hating Debian. Just don't blame ".deb based distros" as if them being deb based was the reason of your suffering.
I figure it must be something I'm doing, but I don't know what it could be, as updating is literally the first thing I do.
Glad you've had a good experience with Arch. I've been using Debian and derivatives for years. I've occasionally seen hiccups with apt but I can almost always trace them to network trouble rather than the distro itself. In the other cases, reading the manpages or googling a bit helped unbork the system. It sounds like you didn't exercise your sysadmin/debugging skills.
But really, installing a system and using the system-provided package manager to perform a system update should "Just Work." And my experience is that this almost always ends in failure, and usually in a broken system. I dunno.
Maybe something like that already exists? I can't be the only person who has this "wants custom X but generic Y" problem.
Such an approach is usually looked down upon in the Arch community. I hate that it is. I love Arch. I love the package system, I love the wiki, I love everything about it. What I don't love is redoing everything each time I have a fresh install. Yeah, it probably takes 10 minutes to get a working system up and a day to get everything as I want it, but I hate just knowing I have to do it all again.
I really want a distro based on Arch which gets over those fears. Again, Antergos probably fits and papyros.io looks really interesting, too.
That's really too bad, because I think a method for sharing curated sets would be great. Maybe the problem isn't so much that sets would be bad, but that it might cause people's expectations of arch to change. Like, if you do everything yourself and it breaks, it's your fault, but if the system does it for you and it breaks, now it's arch's/the maintainer's fault. I don't know if that would happen, but it seems like there might be some danger of a cultural shift.
Anyway, Antergos... It looks like it uses Ubiquity to install, so I'm not sure it seems any better than anything else I've tried, but I'm only just starting to check it out so maybe there's more to it.
[edit] oh, duh, I see now that Antergos is arch-based. It looks nice. I'll have to see what the text-based installer is like.
A couple others that I believe use Arch repos and rolling-release updates directly: ArchBang (Open Box wm): http://www.wiki.archbang.org/index.php?title=Main_Page
Bridge Linux (Gnome, KDE, XFCE) http://sourceforge.net/projects/bridgelinux/
There's list of all the Arch-based distros here: http://distrowatch.com/search.php?basedon=Arch
Once you're past that initial stage, there's really no downside any more.
That said, some distros like nix and guix are addressing a much needed problem now---how to be able to get reproducible builds. Sadly, they haven't learnt many lessons Arch taught us. Last time I tried nix, installing mutt eventually pulled in python as a dependency!