I am having problems building the latest progress report version due to high memory usage during the build. Any chance we could get it merged in it's current state please?

As stated in the above comments, I am having weird issues when trying to make the old pinned Gnome-MPV work in Budgie. Have you been able to test it out? @JoshStrobl

• Add a maintainer file

• Switch from replaces to using conflicts

• Switch from replaces to conflicts

• Use the correct download link

In D7409#117922, @JoshStrobl wrote:

Stupid question but Phabricator changed how whitespace is rendered in diffs, could you validate that the indentation changes retain the usages of spaces please?

• Clean up the build deps to sort out review comments

• Remove flask dep to sort out review

• Add tests for the package

I believe that git will be installed from the git fetch of the version (git|https://github.com/keybase/client : v4.6.1), in other words you should be able to it that from the builddeps as well.

• Add patch from falkTX to get the mixed 64/32bit mode to work in 1.9.13

I think this is better dealt upon by a member of the core team. I don't want to risk massive breakage.

Remove commented out install command that I forgot to remove

This has moved down in my priority list because I had a deeper dive in to this and had a little conversation with the Carla developer (also main maintainer for jack1 and jack2). It turns out that Carla features a windows bridge that needs MinGW64 to build but he said that it is much better than fully relying on wine like this software. The whole way this software works also seems to be a bit annoying, but I haven’t tested using it apart from looking at the manual.

I can step up to officially maintain this package if it's okay for you? I have one of these GPUs and I have updated it a couple times now :)

• Got 32bit build working with metadata support (I think so at least).

• Add homepage

• Update homepage to https (website update happened yesterday).

• Remove the last 32bit leftover. (I promise this is the last one...)

• Remove 32bit leftovers

• Drop 32-bit mixed mode for now. (db5-32bit-devel seems to be broken ish?)

Add MAINTAINER file

Slight summary update

That is wonderful information @YakoYakoYokuYoku. I might need this for a packaging project, so it would be amazing to have it in the repo :)

While you’re at it I would like to get this reviewed too if you don’t mind 🙂

Thanks Josh 🙂

Could I get a review on this one please?

Would you mind re-reviewing this one? @JoshStrobl

I am honestly having troubles figuring out what's wrong.
Issue can not be replicated in version 1.39.0, but everything else can, which means that it is not due to this commit!
Issues does not replicate in deb package or flatpak package with latest versions...

• Update to 1.9.13 (the fancy new meta-data api had to be turned off to build it)

I am pretty sure that those OpenAL rebuilds have been fun I shed for a long time. It was my revision that was merged and I believe I saw those rebuilds being done but the checkbox was never ticked though. I might be wrong but I am pretty sure. @JoshStrobl

Looks like python-pyliblo is missing too. https://dev.getsol.us/source/python-pyliblo/browse/master/abi_used_libs

• Remove hard dep on jack-audio-connection kit (fluidsynth depends on it will be installed anyhow)

It looks like eopkg doesn't handle multiple drop in replacement packages very well. Would be good if we could wire in some small support in to it to tell that jack-audio-connection-kit and jack2 are drop in replacements for each other. Right now if you have jack2 installed it will want to replace it with jack-audio-connection-kit when updating a package linked to jack1. Jack1 and jack2 both have their weaknesses and strengths so deprecating jack1 should NOT be an option at the moment.

Changes requested in the old revision have been applied and I'm adding you all to subscribers here. I am sorry that Arcanist did this to us but it should be all fine now :)

Thanks for the reviews guys. I will need to open a new revision though, because Acanist has decided that this revision is empty and wont let me push updates to it any more :(
Should have a new one up shortly...

• Drop professional to be more in line with jack2

Of course arcanist behaves badly and tells me that it can't parse empty diffs and I seem to be getting it just with this differential :(
I just had a little change to switch conflicts to replaces but I can't do that now. If this is accepted, could that be done afterwards?

Slight update to the summary

• Make sure that arcanist works (cuz it segfaults on jack2)

Wonderful 👍 Thanks for testing 🙂

I am running Budgie and I am having severe issues getting a pinned version of Gnome MPV to even start from the panel. I have tested straight out renaming the desktop file to the old file name, installing the old desktop file but with modifications for celluloid (and to be hidden) and the new desktop file with modifications to be hidden. For the first one it shows up in the menu perfectly but all of them won't start when pressed from the pinned instance in the panel. Setting the desktop files to not be hidden makes them show up in the menu and they do work, but as I said the Budgie panel doesn't want to start them when pinned for me...

The update to version 1.4.0 is in unstable right now. I can't replicate this in 1.4.0, but someone better test it before we close this :)

In D6911#115752, @JoshStrobl wrote:

Sorry for the delay, is there any chance we could get a symlink of the celluloid desktop file to io.github.GnomeMpv.desktop? That way existing pinned instances of GNOME MPV should still work. Thanks!

• Remove patch and verify rebuilding against vala 46.2

Add MAINTAINERS.md

• Use the correct way of using variable macros

My revision D7239 will just need to be merged and then this should probably be fixed.

Make sure that ladspa support actually works and add lash support

• Rebuild against Gnome 3.34 updates

• Rebuild against Gnome 3.34 updates

Update brave to 0.68.142

Update to 0.68.141

• Update against vala 46.1 (seems to make the tests work again yay)

I have a fully working package.yml file for this and will send it in for review later today if all goes to plan...

Yes, I have started looking in to packaging it but it’s not really done yet...

Will update this to 0.68.141 tomorrow...