[GH-ISSUE #1374] No v2.4.0 stable snap (broken edge builds?) #1066

Closed
opened 2026-05-05 07:25:43 -06:00 by gitea-mirror · 11 comments
Owner

Originally created by @maxiberta on GitHub (Nov 3, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1374

What happened?

There is no v2.4.0 snap published on any channel, afaik. Are there any plans to publish it to stable? The latest stable snap is 2.3.3 from 4 Aug 2020; and the latest on edge is 2.3.3-293-g00e182d2 from just 2 days ago, then it just stopped. Maybe check the snap autobuild job? (The snap badge in the README is apparently broken showing the alt text, btw). Ideally if edge builds were fine, you would just need to pick one and promote it to candidate or stable for all supported architectures.

By the way, should the release instructions maybe include any snap-specific steps?

Let me know if I can help! Congrats on the new release, btw \o/

Version

From Git HEAD or commit (specify below)

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

https://snapcraft.io/barrier

What OSes are you seeing the problem on? (Check all that apply)

Linux

What OS versions are you using?

Ubuntu 21.10

Relevant log output

$ snap info barrier | tail -5
channels:
  latest/stable:    2.3.3-2-gbbd1accb   2020-08-04 (384) 57MB -
  latest/candidate: ^                                         
  latest/beta:      ^                                         
  latest/edge:      2.3.3-293-g00e182d2 2021-11-01 (678) 57MB -

Any other information

No response

Originally created by @maxiberta on GitHub (Nov 3, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1374 ### What happened? There is no `v2.4.0` snap published on any channel, afaik. Are there any plans to publish it to `stable`? The [latest stable snap is 2.3.3 from 4 Aug 2020](https://snapcraft.io/barrier); and the latest on `edge` is `2.3.3-293-g00e182d2` from just 2 days ago, then it just stopped. Maybe check [the snap autobuild job](https://build.snapcraft.io/user/debauchee/barrier)? (The snap badge in the [README](https://github.com/debauchee/barrier/blob/master/README.md#ci-build-status) is apparently broken showing the alt text, btw). Ideally if edge builds were fine, you would just need to pick one and promote it to candidate or stable for all supported architectures. By the way, should the [release instructions](https://github.com/debauchee/barrier/blob/master/RELEASING.md) maybe include any snap-specific steps? Let me know if I can help! Congrats on the new release, btw \o/ ### Version From Git HEAD or commit (specify below) ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? https://snapcraft.io/barrier ### What OSes are you seeing the problem on? (Check all that apply) Linux ### What OS versions are you using? Ubuntu 21.10 ### Relevant log output ```shell $ snap info barrier | tail -5 channels: latest/stable: 2.3.3-2-gbbd1accb 2020-08-04 (384) 57MB - latest/candidate: ^ latest/beta: ^ latest/edge: 2.3.3-293-g00e182d2 2021-11-01 (678) 57MB - ``` ### Any other information _No response_
gitea-mirror 2026-05-05 07:25:43 -06:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@p12tic commented on GitHub (Nov 3, 2021):

We unfortunately don't control the snap builds, please contact the maintainer of the snap package directly.

<!-- gh-comment-id:958979997 --> @p12tic commented on GitHub (Nov 3, 2021): We unfortunately don't control the snap builds, please contact the maintainer of the snap package directly.
Author
Owner

@shymega commented on GitHub (Nov 3, 2021):

Well, it's owned by an ex-member of the project, but I have some limited access. I have updated the stable channel to v2.4.0, but for reasons unknown to me, I cannot add v2.3.4 to the channels.

A build has been triggered, if someone using Snap has any issues with it, ping me - I use Flatpak myself... on the note of Flatpak, I do have access to that as well.

On Wed, Nov 3, 2021, at 12:22 PM, Povilas Kanapickas wrote:

Closed #1374 https://github.com/debauchee/barrier/issues/1374.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/debauchee/barrier/issues/1374#event-5561513536, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKF2QBIB2XSEE3DTNL4YTTUKESQDANCNFSM5HIBDTGQ.

--
Kind regards,

Dom Rodriguez (also known as shymega)

<!-- gh-comment-id:959129869 --> @shymega commented on GitHub (Nov 3, 2021): Well, it's owned by an ex-member of the project, but I have some limited access. I have updated the stable channel to v2.4.0, but for reasons unknown to me, I cannot add v2.3.4 to the channels. A build has been triggered, if someone using Snap has any issues with it, ping me - I use Flatpak myself... on the note of Flatpak, I *do* have access to that as well. On Wed, Nov 3, 2021, at 12:22 PM, Povilas Kanapickas wrote: > Closed #1374 <https://github.com/debauchee/barrier/issues/1374>. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/debauchee/barrier/issues/1374#event-5561513536>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAKF2QBIB2XSEE3DTNL4YTTUKESQDANCNFSM5HIBDTGQ>. -- Kind regards, -- Dom Rodriguez (also known as shymega)
Author
Owner

@shymega commented on GitHub (Nov 3, 2021):

OK, so a new Snap build for v2.4.0 is ready. For unknown reasons, the v2.3.4 release is not 'seen' by Snapcraft. v2.4.0 is on the stable channel.

<!-- gh-comment-id:959746886 --> @shymega commented on GitHub (Nov 3, 2021): OK, so a new Snap build for v2.4.0 is ready. For unknown reasons, the v2.3.4 release is not 'seen' by Snapcraft. v2.4.0 is on the stable channel.
Author
Owner

@maxiberta commented on GitHub (Nov 5, 2021):

Thanks @shymega! Glad you're now in control of the snap.
Are automatic edge builds still up and running? It looks like the edge channel has been closed in the last couple of days. Actually, I have installed a snap from edge that's no longer published:

tracking:     latest/edge
refresh-date: 2 days ago, at 11:41 -03
channels:
  latest/stable:    2.4.0-4-gac5a1bfd 2021-11-03 (682) 57MB -
  latest/candidate: ↑                                       
  latest/beta:      ↑                                       
  latest/edge:      ↑                                       
installed:          2.4.0-6-g141ab9ec            (691) 57MB -
<!-- gh-comment-id:961954497 --> @maxiberta commented on GitHub (Nov 5, 2021): Thanks @shymega! Glad you're now [in control of the snap](https://forum.snapcraft.io/t/change-of-ownership-for-snap-in-store/27351). Are automatic `edge` builds still up and running? It looks like the `edge` channel has been closed in the last couple of days. Actually, I have installed a snap from `edge` that's no longer published: ```bash tracking: latest/edge refresh-date: 2 days ago, at 11:41 -03 channels: latest/stable: 2.4.0-4-gac5a1bfd 2021-11-03 (682) 57MB - latest/candidate: ↑ latest/beta: ↑ latest/edge: ↑ installed: 2.4.0-6-g141ab9ec (691) 57MB - ```
Author
Owner

@shymega commented on GitHub (Nov 5, 2021):

No worries.

Yeah, I disabled the Edge channel until I can get an automatic Snap release going, and I also need to read up on the edge channel. My understanding is that the Edge channel would be the Snap equivalent of mainline on Git..?

I can republish Edge to v2.4.0 if you'd like me to, or if others need it. I can't seem to get v2.3.4 on the Snap though, which is quite irritating.

On Fri, Nov 5, 2021, at 2:46 PM, Maximiliano Bertacchini wrote:

Thanks @shymega https://github.com/shymega! Glad you're now in
control of the snap
https://forum.snapcraft.io/t/change-of-ownership-for-snap-in-store/27351.
Are automatic edge builds still up and running? It looks like the
edge channel has been closed in the last couple of days. Actually, I
have installed a snap from edge that's no longer published:

tracking: latest/edge
refresh-date: 2 days ago, at 11:41 -03
channels:
latest/stable: 2.4.0-4-gac5a1bfd 2021-11-03 (682) 57MB -
latest/candidate: ↑
latest/beta: ↑
latest/edge: ↑
installed: 2.4.0-6-g141ab9ec (691) 57MB -

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/debauchee/barrier/issues/1374#issuecomment-961954497,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKF2QHN2ZJ6RHDDQEUUIHDUKPU5JANCNFSM5HIBDTGQ.

--
Kind regards,

Dom Rodriguez (also known as shymega)

<!-- gh-comment-id:961957479 --> @shymega commented on GitHub (Nov 5, 2021): No worries. Yeah, I disabled the Edge channel until I can get an automatic Snap release going, and I also need to read up on the edge channel. My understanding is that the Edge channel would be the Snap equivalent of mainline on Git..? I can republish Edge to v2.4.0 if you'd like me to, or if others need it. I can't seem to get v2.3.4 on the Snap though, which is quite irritating. On Fri, Nov 5, 2021, at 2:46 PM, Maximiliano Bertacchini wrote: > Thanks @shymega <https://github.com/shymega>! Glad you're now in > control of the snap > <https://forum.snapcraft.io/t/change-of-ownership-for-snap-in-store/27351>. > Are automatic `edge` builds still up and running? It looks like the > `edge` channel has been closed in the last couple of days. Actually, I > have installed a snap from `edge` that's no longer published: > > tracking: latest/edge > refresh-date: 2 days ago, at 11:41 -03 > channels: > latest/stable: 2.4.0-4-gac5a1bfd 2021-11-03 (682) 57MB - > latest/candidate: ↑ > latest/beta: ↑ > latest/edge: ↑ > installed: 2.4.0-6-g141ab9ec (691) 57MB - > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/debauchee/barrier/issues/1374#issuecomment-961954497>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAKF2QHN2ZJ6RHDDQEUUIHDUKPU5JANCNFSM5HIBDTGQ>. -- Kind regards, -- Dom Rodriguez (also known as shymega)
Author
Owner

@maxiberta commented on GitHub (Nov 5, 2021):

Exactly, edge is "for users wanting to closely track development" and it is supposed to contain builds from main or master. That's the main use case of build.snapcraft.io afaik.

I wouldn't worry about v2.3.4 honestly, having v2.4.0 already. If you really want to publish it, I think the right way to do it would be to ask the snap store admins to open a track for it, so that users would be able to install from e.g. v2.3/stable. But again, I don't think it's much use really.

<!-- gh-comment-id:961972479 --> @maxiberta commented on GitHub (Nov 5, 2021): Exactly, `edge` is ["for users wanting to closely track development"](https://snapcraft.io/docs/channels) and it is supposed to contain builds from `main` or `master`. That's the main use case of [build.snapcraft.io](https://build.snapcraft.io) afaik. I wouldn't worry about v2.3.4 honestly, having v2.4.0 already. If you really want to publish it, I *think* the right way to do it would be to [ask the snap store admins to open a track](https://forum.snapcraft.io/t/process-for-aliases-auto-connections-and-tracks/455) for it, so that users would be able to install from e.g. `v2.3/stable`. But again, I don't think it's much use really.
Author
Owner

@shymega commented on GitHub (Nov 5, 2021):

Right. Currently, I can't even set up webhooks to trigger a Snap build. I don't have permission to create webhooks on this repo. Ideally, that's how I'd like it to be, that way we can build an Edge snap when master/main updates... but in terms of v2.3.4, I'll ask about that, as I think it'd be a good compromise for Snap users who merely don't want to use v2.4.0 just yet, but also want security fixes.

Thanks for the advice though.

<!-- gh-comment-id:962002518 --> @shymega commented on GitHub (Nov 5, 2021): Right. Currently, I can't even set up webhooks to trigger a Snap build. I don't have permission to create webhooks on this repo. Ideally, that's how I'd like it to be, that way we can build an Edge snap when master/main updates... but in terms of v2.3.4, I'll ask about that, as I think it'd be a good compromise for Snap users who merely don't want to use v2.4.0 *just yet*, but also want security fixes. Thanks for the advice though.
Author
Owner

@maxiberta commented on GitHub (Nov 5, 2021):

Just fyi, snaps can also be built on Github and published to the Snap Store with snapcore/action-build and snapcore/action-publish.

<!-- gh-comment-id:962017981 --> @maxiberta commented on GitHub (Nov 5, 2021): Just fyi, snaps can also be built on Github and published to the Snap Store with [snapcore/action-build](https://github.com/snapcore/action-build) and [snapcore/action-publish](https://github.com/snapcore/action-publish).
Author
Owner

@shymega commented on GitHub (Nov 5, 2021):

Hm. We use Azure Pipelines, and I don't think we use Actions for this sort of stuff. I'd also rather do it on Snapcraft, as it can then do it's "security vulns checking" it emails me about ;)

Thanks for the pointer.

<!-- gh-comment-id:962020995 --> @shymega commented on GitHub (Nov 5, 2021): Hm. We use Azure Pipelines, and I don't think we use Actions for this sort of stuff. I'd also rather do it on Snapcraft, as it can then do it's "security vulns checking" it emails me about ;) Thanks for the pointer.
Author
Owner

@maxiberta commented on GitHub (Nov 5, 2021):

Sure. Snaps don't need to be built on Snapcraft for the security checks to be enabled. It scans published snaps themselves afaik, as long as they were built with SNAPCRAFT_BUILD_INFO=1 (which the action-build already does).

<!-- gh-comment-id:962042195 --> @maxiberta commented on GitHub (Nov 5, 2021): Sure. Snaps don't need to be built on Snapcraft for the security checks to be enabled. It scans published snaps themselves afaik, as long as they were built with `SNAPCRAFT_BUILD_INFO=1` (which the `action-build` already does).
Author
Owner

@shymega commented on GitHub (Nov 5, 2021):

I see. Well, permissions on this repo don't allow me to use Actions. I believe the owner of the organisation can only do it.

<!-- gh-comment-id:962067884 --> @shymega commented on GitHub (Nov 5, 2021): I see. Well, permissions on this repo don't allow me to use Actions. I believe the owner of the organisation can only do it.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#1066
No description provided.