From owner-freebsd-ports@freebsd.org Wed Jul 8 12:25:40 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 911DD996A7E for ; Wed, 8 Jul 2015 12:25:40 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7D1731574 for ; Wed, 8 Jul 2015 12:25:40 +0000 (UTC) (envelope-from lists@opsec.eu) Received: by mailman.ysv.freebsd.org (Postfix) id 7C170996A7D; Wed, 8 Jul 2015 12:25:40 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7BA61996A7C for ; Wed, 8 Jul 2015 12:25:40 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (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 366071572 for ; Wed, 8 Jul 2015 12:25:40 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1ZCoPw-0006A2-5y; Wed, 08 Jul 2015 14:25:36 +0200 Date: Wed, 8 Jul 2015 14:25:36 +0200 From: Kurt Jaeger To: Bro Cc: ports@freebsd.org Subject: Re: Unresolved issue with libtorrent-rasterbar (1.0.4) port Message-ID: <20150708122536.GD49099@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jul 2015 12:25:40 -0000 Hi! > I see the libtorrent-rasterbar port was updated to version 1.0.4, however, > the port has an unresolved problem reported here: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198072 > > Wouldn't it be a good practice to address any open issues before updating > to newer versions? The port has no maintainer, so probably the PR was overlooked. Can you test whether the problem still persists, and if yes, update the patch in the PR ? -- pi@opsec.eu +49 171 3101372 5 years to go !