Needs Maintainer is software that has been accepted for inclusion and/or there has been expressed interest in, where we have determined that a dedicated maintainer / integrator is needed to provide the best experience for Solus users.
Wed, Jul 17
Mon, Jul 15
Thu, Jul 11
Wed, Jul 10
Just wanted to let everyone know that there is a flatpak build available as of late.
Wed, Jul 3
Tue, Jul 2
Hey Josh, thanks for the feedback I'll be sure to the communicate them to the theme's author. Can you give a screenshot example of the input text when volume overdrive is enabled? I've enabled volume overdrive but don't know what input text you're referring to. What other changes need to be made to integrate it better with Budgie 10.5?
I'm not really impressed with the current state of this theme with Budgie, I'd like to see some more theming support around Budgie 10.5 be made (such as removing the input text when volume overdrive is enabled) and a new release be made.
Mon, Jul 1
I would help to maintain this package. I might need some help along the way, but I have some experience with terraform.
Sat, Jun 29
As a note, a new release has been tagged on Github: https://github.com/debauchee/barrier/archive/v2.3.0.tar.gz
Fri, Jun 28
Yeah it does build without the full dependencies list, if they are inherited from another dependency or of they are in the system base/devel, we don't list them.
Solbuild does strip the binaries by default unless instructed not to do it.
I added the the git commit/branch info although I suppose you really need this for developers & testers while we will normally stick to tagged releases.
Thu, Jun 27
- Does it actually build without full dependencies list?
- Description is ok, it doesn't matter too much.
- git commit and branch are printed in logs and shown in about tab. It makes it easier to see which version/commit is user running when reporting issues.
- --buildtype=debug should prevent debug symbols stripping (however I don't know if solbuild is stripping binaries anyway and how is it configured). It also may affect compiler optimizations. There is one weird unresolved issue related to optimizations: https://github.com/tkashkin/GameHub/issues/162.
@tkashkin I made a lighter version of your package.yml in D6623, would you mind having a look ?
What are the git options in the meson configure used for ? (I omitted them), I was also lazy for the package description but since your provide appdata it doesn't really matter.
I have pushed a new stable release: https://github.com/tkashkin/GameHub/releases/tag/0.14.1-2-master
Source tarball: https://github.com/tkashkin/GameHub/archive/0.14.1-2-master.tar.gz
@tkashkin No, there are no problems with including this in the repository once Granite is no longer a dependency. It passes our package inclusion policy, has clear value-add, etc. otherwise 👍
@JoshStrobl I was actually thinking about moving away from granite. Now I have finally done it and latest commit in dev branch doesn't use granite anymore.
I plan to push new stable release soon after some testing.
@tkashkin No, you're not just using it for widgets, you're also using it for the very DateTime APIs I had to fix and send a PR to Granite for (because it also broke Tootle). They haven't even merged it in, I lack any confidence in elementary ensuring Granite works reliably on other operating systems, and since then we've added the following section as a reason for rejection to our Package Inclusion Policy:
It is great to see that @tkashkin considers the current versions stable, and seems pretty determined at helping making Gamehub available as an eopkg. It seems to clear the issues that lead @DataDrake to tagging this task as Wontfix earlier (correct?).
Wed, Jun 26
I am willing to maintain this package.
Losing this packet would be very sad, it's a really good replacement of notepad++.
Tue, Jun 25
Mon, Jun 24
Sounds reasonable. They seem to be discussing the matter on how releases should be handled in future. There seem to be only a handful of people committing, and as a community driven effort there will be quaters with more/less commits.
I'd like to see a new, stable release of this fork before it is accepted for inclusion. The last release was in January whereas Synergy is under much heavier, active development with more frequent releases. Not opposed at all to having it replace synergy however, should it prove to be an active fork that is capable of putting out routine releases.
Sun, Jun 23
Jun 20 2019
0.3 (a.k.a. pre-0.4) is compile-only.
0.4 isn't out yet.
Last release still April 2017, last commit 1 year ago.
No 3.5 on the download page.
Checked, no 0.3 or 0.4 in releases page.
https://gitlab.gnome.org/World/Shortwave/releases - releases link, 7.2 still latest, released in Nov 2018.
Jun 19 2019
New version 1.1.1 was released recently, so i will try to package it.
Version 0.18 is released. Can someone try their luck with this version?
I am currently working on packaging this. I have a pretty much working package except from the fact that carla-control doesn't work yet because it can't find liblo (even though it is installed)...