Closed star-buck closed 5 years ago
if removing the "breeze-kde4-netrunner", the update works fine. Can we automatically force remove this so people don't have to worry or guess?
We needed the meta package to switch back to the upstream breeze-kde4 when our patches would no longer apply. Since then Manjaro dropped all *-kde4 packages from their repository, this includes breeze-kde4. Just removing the breeze-kde4-netrunner meta package from our repository will not fix this. Let me take a look into what can be done to correct this issue.
Actually, Arch is where breeze-kde4 was delegated to the AUR, and dropped from their repository. However, this would not be an issue for anyone that used the 2018.08 ISO, or that had updated their system before the breeze-kde4 package had been removed.
I can't force remove the package, but I can change it to require breeze instead of breeze-kde4 thus circumventing the problem.
OK, I updated the breeze-kde4-netrunner meta package. This will no longer cause a problem for anyone that hadn't updated their system prior to the breeze-kde4 package removal by upstream.
Good, thanks.
On Thu, Oct 25, 2018, 16:38 James Kittsmiller notifications@github.com wrote:
OK, I updated the meta package. This should no longer be a problem for anyone that hadn't update their system prior to the breeze-kde4 removal.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/blue-systems/netrunner-releases/issues/60#issuecomment-433240208, or mute the thread https://github.com/notifications/unsubscribe-auth/AAzRhojpdLkalOt1fCyVkQAyRxfCisAWks5uoktYgaJpZM4X60Qu .