From owner-freebsd-ports-bugs@FreeBSD.ORG  Wed Feb 25 08:44:14 2015
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
Delivered-To: freebsd-ports-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id E49C527D
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 25 Feb 2015 08:44:14 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id CA9E410E
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 25 Feb 2015 08:44:14 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1P8iEvF016352
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 25 Feb 2015 08:44:14 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 198019] [PATCH]: FreeBSD 10.1 fix for comms/telldus-core
Date: Wed, 25 Feb 2015 08:44:14 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: johan@stromnet.se
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-198019-13-EHEyLg48eY@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-198019-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-198019-13@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2015 08:44:15 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198019

--- Comment #5 from johan@stromnet.se ---
Thanks for quick fixes!

When can one expect this to be in 10.1-RELEASE (or 9.3-RELEASE) as available
via freebsd-update?

The original submitted patch contained this workaround (at least working on
FreeBSD 10.1) until proper is usable:

action "dev=`usbconfig dump_device_desc | grep $sernum -B14|grep ugen|cut -f1
-d':'`; chgrp dialer /dev/$$dev; chmod 660 /dev/$$dev;
    ..."

Unless this can be in generic relatively soon, I'd prefer to have the above
hack in the port to avoid breakage. Without the chown/chmod the port is
unusable.

-- 
You are receiving this mail because:
You are the assignee for the bug.