mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #20] CentOS-7 compatibility layer warnings #14
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#14
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 @truatpasteurdotfr on GitHub (Mar 9, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/20
Operating Systems
CentOS-7
Barrier Version
2.0.0-RC2
Steps to reproduce bug
running barrier on CentOS-7 gives this warning message:
when clicking on the [] server checkbox these additionnal lines appears:
list of the avahi packages installed on the machine:
@walker0643 commented on GitHub (Mar 10, 2018):
These warnings seems to be benign. Several other projects using libraries for apple technology have seen them and most seem to disregard them ...
eg:
https://github.com/nfarina/homebridge/blob/master/README.md#errors-on-startup
The question now becomes one of whether or not it is worth it to "fix" code that otherwise works.
@truatpasteurdotfr commented on GitHub (Mar 12, 2018):
Either fix, or put an entry for a FAQ, with a better wording than "the cost of removing the issue at the core of the errors isn't worth the effort", imho.
@walker0643 commented on GitHub (Mar 13, 2018):
More info:
https://src.fedoraproject.org/rpms/cups/tree/f15
The 5 patches beginning with cups-avahi- are what the cups folks had to do to get this warning to go away. I'm not finding any indication whatsoever of a change in functionality. It seems to be simply an effort to get developers not to use Apple APIs even though they are supported now and have been for > 10 years (this warning is older than that).
@walker0643 commented on GitHub (Mar 13, 2018):
Fixed in
921a40c684