I'd like to see everything in /usr/lib moved to /usr/share and no /usr/share/java.

So, by the looks of it he abandoned gotop in favor of ytop and then stopped developing ytop. bottom is just something he recommended as a replacement. If you go back to the gotop repo now, he's advertising a maintained fork here: https://github.com/xxxserxxx/gotop

For future reference, filing a new Package Request is not the way to get a deprecated package back. Someone needs to step up and maintain it.

LGTM. Thanks!

We have no plans of adding any additional software to Third Party. I personally use the Flatpak with Zoom and it works fine for my needs.

We don't ship pre-release versions of software unless absolutely necessary. You will need to wait until this lands in a stable release or compile it yourself.

Cheers!

@kyrios123 Is this still an issue?

I'll get this in the next update.

Closing due to lack of response in over 30 days.

Closing due to lack fo response in over 30 days.

Sorry. I'll get this one in the next update.

Actually, it looks like you need to reinstall either slick-greeter (default) or lightdm-gtk-greeter at least first since they would have been removed when you uninstalled lightdm.

@sethfl can you please check ~/.xsession-errors from TTY immediately following the failure? Thanks.

I can't reproduce this on Budgie. Need to see some logs folks.

In T7471#174412, @nazar wrote:

Also, it should be possible to save some bandwidth removing about 1G of programming.haskell from dependencies, here's detailed list https://hastebin.com/afutukisoq.sql

@clivejo kup (kernel) hasn't seen a release in 3 years so wouldn't be eligible for inclusion anyways. If people need it, they can install it themselves. If they are using ypkg to build it, they will find out soon enough that there's a name conflict and adjust accordingly. We cannot and should not base package naming decisions on something that doesn't exist in the repo at the time of Request.

What error(s) are you getting? You've given us nothing to go on.

This is fixed in Unstable, pending a quick sync after I touch base with @JoshStrobl.