mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #826] Implement and maintain a PPA for Barrier older/new releases #655
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#655
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @shymega on GitHub (Aug 6, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/826
As well as providing Snaps and Flatpaks for Barrier, it would be
beneficial to provide a PPA for Barrier. This would allow for older
versions of Ubuntu (or derivatives) to use the latest version of
Barrier. Although a Snap/Flatpak is available, some users may wish
to use Barrier without tht.
I will look into implementing this soon, this issue is merely a
tracker.
@fcastilloec commented on GitHub (Feb 21, 2022):
I totally agree with this. I just installed the
snapversion and I couldn't make it work. The server wasn't seeing anybody... Had to install my distro version, which is old, and then it worked.@shymega commented on GitHub (Feb 23, 2022):
Hi,
I am no longer involved in the Barrier project, and have moved to a fork, whilst also beginning work on my new primary focus: a hybrid KVM. As I am no longer involved with Barrier, I cannot assist anymore, as I have no access to the administration/management tools.
Apologies for the inconvenience.
@shymega commented on GitHub (Feb 23, 2022):
You reacted with the confused emoji, I'm just explaining there's nothing I can do with this issue now.