Comment

Comment by nitrogen

Sometimes a newer version of package A will declare that it conflicts with package B. Maybe package C depended on both before the conflict was added. Then the package manager might find that the only way to resolve all conflicts is to remove C, which then auto-removes everything C depended on. Maybe C happens to be the "kububtu-desktop" package.
parent nitrogen 6 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton