- User Since
- Aug 2 2016, 10:57 PM (124 w, 13 h)
Abandoning, seeing as this is not accepted for inclusion and it is not clear as to what license this is actually under, where the source for it would be, etc. Not to mention using a Deb for this wouldn't be acceptable.
Mon, Dec 17
We aren't accepting any additional inclusions into the Third Party repository.
Please file a valid package request in accordance with https://getsol.us/articles/packaging/request-a-package/en/
This issue has been deemed by the developers to be an issue related to Budgie, our primary desktop environment. As Budgie is a distro-agnostic project, developed by Solus but leveraged by other operating systems and projects, we maintain a dedicated issue tracker for it. This issue tracker can be found at https://github.com/solus-project/budgie-desktop
None really needed
@DataDrake It isn't about re-introducing it, it's already in the repository. While I agree we'll never have it in the ISO / pre-installed, I don't see that as a reason to disallow it outright. The point in nuking stuff from the repo is things which are not maintained, are not feasible to maintain, are libraries which no longer have a respective reverse dependency, etc. Or we'd surely go down the route of nuking lightdm-settings, because there'd be no reason for someone to want to customize LightDM and not use our defaults, right? 😉 If @ZachBacon is willing to maintain, thoroughly test this across all editions / desktop experiences (since a failed start of the service will likely result in failing to ever get to your login manager) and ensure updates are done in a timely manner, I'm sure this is something that can remain in the repo.
Sun, Dec 16
Stop triaging issues.
That isn't relevant to us. We're holding back Nautilus, because we're actually able to (by virtue of having control over the stack).
Sat, Dec 15
LGTM. Nice work! Thanks @kyrios123 for helping him out =)
@linuxxnut Would love for you to step up and become the maintainer of this and we'd all be happy to help get you started with packaging :)
I'd encourage you to install the snap instead: sudo snap install spotify
Fri, Dec 14
Okay? We'll cross that bridge when we get there. Current release is 64.
Thu, Dec 13
Because that's how reverse dependencies work. nodejs is a runtime dependency of vscode and therefore removing nodejs will remove vscode. If you need another version of nodejs for whatever reason, use NVM.
Closing as WONTFIX. User no longer appears to be using Solus or is actively engaging with respect to the community, not maintaining their existing packages, etc.
Wed, Dec 12
Sounds like the issue you're reporting is one specific to Nautilus and its minimize size it enforces. Regardless of desktop environment, this is not something we can or will change.
Are you actually going to use this? I'm not really interested in you picking up yet another package that you'll update, sure, but not actually use (which is frankly more important).
So for R2104 mpdris2, I'm going to go ahead and test its functionality first, get its deps updated locally. It's sort of limping along (in git, anyways) but it is seemingly the best option for MPRIS support in mpd. I'm going to remove it from the list (but keep python-mpd on the list, since python-mpd2 is a thing now).
Known issue, reported on the old solus-sc tracker (we have a new repo at https://github.com/getsolus/solus-sc). Issues should be filed there, not here, until I've fully moved the project over to Phabricator and we have the tooling in place to facilitate its development.
NodeJS is a dependency of VSCODE when installing it, as far as why I don’t really know.
Yea, I'll kill it.
Tue, Dec 11
Closing due to lack of response.
In case you want to land this yourself, might want to amend the commit message. Also be sure to rebuild qtox against this.
Abandoning due to lack of action.
Upstream didn't provide any changelog, but I did quickly notice that the ugly artifacts and flickers were gone from the boot of my KDE Plasma computer.