Bug 191527 - [patch] net/libvncserver compile warning patched upstream
Summary: [patch] net/libvncserver compile warning patched upstream
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Many People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-01 13:35 UTC by Duane
Modified: 2014-07-27 01:11 UTC (History)
1 user (show)

See Also:


Attachments
Patch to bring port to upstream state. (490 bytes, patch)
2014-07-01 13:35 UTC, Duane
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Duane 2014-07-01 13:35:19 UTC
Created attachment 144311 [details]
Patch to bring port to upstream state.

Compiling net/libvncserver produces a warning for rfbregion.c:754 about '=+ 2' being likely mistyped for '+= 2'.  I don't know what effect this has but the patch has been applied upstream although a new release has not been tagged.

Adding this patch will bring this port in line with upstream in the absence of a tagged release.
Comment 1 commit-hook freebsd_committer freebsd_triage 2014-07-27 01:08:38 UTC
A commit references this bug:

Author: marino
Date: Sun Jul 27 01:08:31 UTC 2014
New revision: 363005
URL: http://svnweb.freebsd.org/changeset/ports/363005

Log:
  net/libvncserver: fix compile warning

  PR:		191527
  Submitted by:	Duane

Changes:
  head/net/libvncserver/Makefile
  head/net/libvncserver/files/patch-libvncserver_rfbregion.c
Comment 2 John Marino freebsd_committer freebsd_triage 2014-07-27 01:11:28 UTC
Thanks, but next time submit a diff that creates the patch.  This diff only contained the contents of the patch, so I had to create the file name, bump it, etc.

Diffs should be relative to the entire port.