Thanks @algent. I will happily help out answering questions and address issues upstream if any problems arise :)
However, I am using Fedora at the moment so I won't be able to maintain anything unfortunately :/

In T10084#191330, @joebonrichie wrote:

Assigning to maintainer

I think it is best to leave V where it is and not include it in the repository. It is still very much broken and has gained a kind of cult following with a lot of claims about the language that simply isn’t true. See https://christine.website/blog/v-vaporware-2019-06-23 as the first in a series of posts about it.

Please update the MAINTAINERS.md file as well. I have stepped down as a maintainer, so I will not update it anytime soon and you could thus take over the maintainership if you want. Keep in mind that you would not have been allowed to land this update unless that was the case. The MAINTAINERS.md file usually forbids other people to land patches for the packages.

Feel free to remove me from the Maintainer file. You know that I have stepped down...

Feel free to take over this when it can land. Abandoning for now.

I think you better get the MAINTAINERS.md file updated while at it.

It might just be me, but it feels a bit sketchy to use a download from a third part site, even if it is the one linked to by the main project.

Is there anything wrong with using the GitHub tarball? https://github.com/godotengine/godot/archive/refs/tags/3.3-stable.tar.gz

@JoshStrobl Would you mind backporting the MimeType patch when you update Go to 1.16.3, now that it has landed upstream? That would mean backporting my patch https://github.com/golang/go/commit/3e8ba91275cdeb0af4c8b30f9cc788fd42cfbbd3 and https://github.com/golang/go/commit/7b19fb1d560908a848e07e091fb5df61f4848389 (for a bug fix making it work better on other Linux distros).

Sorry for it taking such a long time, I have been quite busy. I now have a PR up for Go that properly fixes this issue and makes mimetype lookup work on Solus: https://github.com/golang/go/pull/45271

• Update celluloid to 0.21

In D10775#177488, @algent wrote:

There is a task open for this T9615 "Update brave to 1.21.73"

If I understand the README correctly, it seems as if we won't even be able to call it "Vital" in the repos...

In D10568#173980, @JoshStrobl wrote:

Any reason we aren't bumping this to 104? I know it doesn't really have any Linux related fixes, but that would *actually* fix the task :D

I think I have been running in to the same issue a few times. Quite annoying. I am also seeing it on Budgie if that has something to do with it. Though I am still running on an updated install of Solus 4.1 and not a reinstall of 4.2, if it matters.

Sorry, my schedule is very tight. I find myself having less and less time for packaging. Will see if I can get this updated in the coming days.

My JACK installation was broke at some point and I was pretty sure that it was because of https://dev.getsol.us/T9378. I had pretty much given up, and accepted that as to why it was broken, after all the time I spent trying to get it working. Seems strange that the limits.conf file would be the issue, given that I know that I tested that in what feels like 100 times, but if it is, I will happily accept that :)

@TeenCorn The best way of testing it (in my opinion) is by opening a project session in Ardour and use JACK. It is going to error and won't be usable if realtime isn't working.

Can this be reconsidered now that we have 4.14 as the LTS kernel?

I see, thanks for looking into the issue. Also, fyi, we probably can't deprecate fuse-exfat as it would mean that users of exfat on the LTS kernels have no support for that filesystem.

I don't think we can deprecate exfat-utils just yet. This one is not yet supported by Gnome disks (you can't partition using exfat).

In D10305#169149, @aleksvor wrote:

@Jacalz, that's because how bugfix releases of bash and readline work. They don't make self-contained tarballs for minor releases - they release patchsets that need to be applied on top of major release tarball.

Just out of curiosity, why are there always multiple patches back-ported from upstream every time bash is updated. Wouldn't it be enough to just use the releases?
Sorry if this is a stupid question, was just wandering as we don't really do so with any other packages unless there are very critical bugs that need fixed.

Use pkgconfig instead

Sorry for editing the policy. It was the only way it would let me unassign myself.

The version looks to be a buggy mess. Freezes and stuff. I am not the maintainer of the package. I don't have the time to look into why it doesn't work.

Sorry, it looks like I have stopped getting notifications for new releases. Will get this updated.

Oh gosh, sorry. I had forgotten that I was the maintainer of this :/

No worries. I hadn’t realised that it was a kernel config and opened the task a bit too late, that’s all :)

No rush. Thanks for adding it. Much appreciated :)

@JoshStrobl I saw that you just added a new config to the kernel. Any chance that you might be able to squeeze this in before the rebuilds? ?

@silke Thanks for posting the differential. I have much less time over nowadays, so feel free to keep yourself as the maintainer please :)

Alright. Probably shouldn't have jumped to that conclusion that soon. Looks like it might need to be enabled in the kernel settings first and Gnome Disks does not support these userspace utilities just yet.

Yay. This should now be unblocked. Will have a look at possibly packaging this in the near future :)

Nice. Thank you for doing this. I used to do this myself, but with the limited time I have nowadays, I am very happy to see someone continuing the tradition ?

I think all it does is tell LMMS to fail more gracefully if wine isn't installed at runtime. Last time I had a go at it, it was broken and wouldn't build. You have a version that now manages to build. I figured you could test how it behaves with and without wine installed ;)

We used -DWANT_VST_NOWINE=1 before to get a round it, see https://dev.getsol.us/R1974:1d4f6e6654dc05c4f086d4c51d4f05cefe3e3d16.

This is a nice change and thanks for fixing wine build, however I don't think adding wine-32bit as a rundep is a good way to move forward. Wine is a massive piece of code and I don't think every LLMS user wants to download wine when they install LMMS.

Sorry for not getting brave updated for some time now. I've had massive amounts of work to do IRL and haven't gotten any time to do packaging stuff.

Will go ahead and add it to fluidsynth when this lands ?

I updated to latest unstable and almost everything is working fine, except for one issue with the budgie application menu (sorry if that's not the correct name).
If I press it just after the desktop has just appeared after a computer restart, it shows up too high up and does not respond to clicks:

@YakoYakoYokuYoku Do you think this could be something you would be willing to work on, given the work you are putting into updating and testing D10026? ?

Alright then. Will do so :)

@silke Thank you. Looks like I am remembering incorrectly then. Looking forward to seeing one posted :)

It is going to be very exciting to hopefully see those patches landing @silke. I think I remember seeing a differential revision opened here for integrating it, but I can't seem to find it any more. Am I remembering incorrectly or is it just very hard to find?

Sure thing. Will go ahead later this week when I get some time :)

Sorry. I thought that I already had updated to 3.0. Will get that updated and fixed soon ?

This is an issue with JACK sadly. The kernel config CONFIG_RT_GROUP_SCHED breaks realtime jack support. See https://discuss.getsol.us/d/608-jack-audio-refuses-to-start-in-realtime-mode/8 for more information.

Thanks for the kind words. Here are the resulting files for how for I managed to get:

Sorry people. I haven’t had any luck with getting this thing set up for testing due to the poor amount of documentation for doing so. I probably won’t have the time to put in more effort into this due to having a lot going on in life at the moment. Someone else will have to continue this.

This brings up the topic that we probably should drop FeedReader from the repositories.

Alright. Looking into this, it is very clear to me that I have absolutely no idea how to test this. Documentation is scarce or non existing :I

Looks like the pw-jack and pw-pulse got built automatically. Will try do some testing and hopefully get a revision out in a few days.