Barrier: Ubuntu snap seems to be "stuck" on 2.3.2

[linaori]

As the release was 2 weeks ago, how long will it take for the snap to update? Is there an alternative way of installing that also works for Ubuntu 20.04? I could really use the 2.3.3 build because it's supposed to solve the hangs.

[shymega]

@AdrianKoshka is responsible for Snap. CC'ing them.

[poirier]

I just checked out the v2.3.3 tag and built the Debian package and it was labeled 2.3.2 instead of 2.3.3. I haven't done this before and might have missed something, but it's possible the version number wasn't incremented for Debian and what looks like 2.3.2 is really 2.3.3.

[poirier]

Maybe it comes from https://github.com/debauchee/barrier/blob/v2.3.3/Build.properties ?

[maxiberta]

The current stable snap is old: it was published last november, according to https://snapcraft.io/barrier (or check snap info barrier).

Publishing the snap on the Snap Store is super easy: literally, just drag the existing 2.3.3 daily builds from "edge" to "stable" at https://snapcraft.io/moonlight/releases (or via snapcraft release). If @AdrianKoshka doesn't show up soon, maybe consider filing a dispute to request a transfer of ownership in the Snap Store?

[linaori]

It's been only 7 days, best to give them some time. While I love to have the new version, I don't think having to wait a few days makes it worth disputing ownership.

[maxiberta]

2.3.3 was released 21 days ago. Anyway, just worth mentioning all possible options.

[shymega]

On it. @AdrianKoshka gave me access a few days ago... apparently ownership cannot be transferred to me.

[shymega]

Right, looks like I've done it.

[shymega]

FWIW, I am now the maintainer of both the Snap and Flatpak. Ideally I'd like to get CI to automatically make GitHub releases, and update the Snap & Flatpak. I should probably make a tracking issue for that. Anyway, please ping me instead of @AdrianKoshka regarding Snap/Flatpak. They are no longer involved with Barrier...

[shymega]

I just checked out the v2.3.3 tag and built the Debian package and it was labeled 2.3.2 instead of 2.3.3. I haven't done this before and might have missed something, but it's possible the version number wasn't incremented for Debian and what looks like 2.3.2 is really 2.3.3.

Bumped Build.properties to the latest tag with commit 6b718712.

Let me know if that works, @poirier.

[shymega]

@poirier Looking at the Debian package repositories, Barrier is available with v2.3.3 on Unstable. Can you run me through the process you're having issues with? We can always make this a separate issue.

[poirier]

I just apt installed the build dependencies, run dpkg-buildpackage -us -uc, and noticed that it built barrier_2.3.2_amd64.deb instead of barrier_2.3.3_amd64.deb.

It's still doing that on master now, so I guess Build.properties did not affect it. What did seem to bump the version was faking a 2.3.3 entry in debian/changelog. I don't know if that's the proper process for setting the Debian package version though. I'm not experienced with building Debian packages.

I reported it on this issue because I thought it might explain the reported problem of 2.3.3 not showing up some places. It could easily be a separate issue.