From owner-freebsd-ports@freebsd.org Sun Oct 18 20:25:46 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 A69E5A188E1 for ; Sun, 18 Oct 2015 20:25:46 +0000 (UTC) (envelope-from fonz@skysmurf.nl) Received: from biertje.skysmurf.nl (unknown [IPv6:2001:984:78b5:1:21b:78ff:fea8:3f22]) (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 2D9AA2A2 for ; Sun, 18 Oct 2015 20:25:45 +0000 (UTC) (envelope-from fonz@skysmurf.nl) Received: from biertje.skysmurf.nl (localhost [127.0.0.1]) by biertje.skysmurf.nl (8.14.9/8.14.9) with ESMTP id t9IKPhxj041153; Sun, 18 Oct 2015 22:25:43 +0200 (CEST) (envelope-from fonz@biertje.skysmurf.nl) Received: (from fonz@localhost) by biertje.skysmurf.nl (8.14.9/8.14.9/Submit) id t9IKPgKY041152; Sun, 18 Oct 2015 22:25:42 +0200 (CEST) (envelope-from fonz) Date: Sun, 18 Oct 2015 22:25:42 +0200 From: "A.J. \"Fonz\" van Werven" To: Lev Serebryakov Cc: freebsd-ports Subject: Re: How to close bug which should be reported upstream? Message-ID: <20151018202542.GA41125@biertje.skysmurf.nl> References: <91850152.20151018224325@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1yeeQ81UyVL57Vl7" Content-Disposition: inline In-Reply-To: <91850152.20151018224325@serebryakov.spb.ru> X-PGP-Key: http://www.skysmurf.nl/~fonz/fonz_pubkey.asc User-Agent: Mutt/1.5.24 (2015-08-30) 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: Sun, 18 Oct 2015 20:25:46 -0000 --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Lev Serebryakov wrote: > How to close bug which should be reported upstream and is not easily > fixable by port maintainer? If I understand your question correctly, you or somebody else has submitted a bug that can only (or almost only) be fixed by the upstream vendor. My suggestion would be to: a) add a comment to the bug explaining that it has to be fixed upstream; b) post a message here on the ports mailing list, with a link to the bug report, asking that a committer take appropriate action, such as closing the bug (or suspending it, if such a thing exists). On the upside, your message here will probably already be read by a committer who knows what to do :-) Hope this helps, AvW --=20 I'm not completely useless, I can be used as a bad example. --1yeeQ81UyVL57Vl7 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWJABGAAoJEAfP7gJTaCe8mjUP/1o3l+mxdQzjuuwiQJ6ylNKD /ntwleBoyjGA3Iioyd5ItZYcpkIgl8PVELQT4IWYmzF8SXA79nTr/oQSJHXMGhsu lZgXOJtyrnaVr/HBJO/83OME8V2telpuXz7rtSDiak0sK+1LGAQf2+L5wy8OJBIX piLDX35HPIIRy3azlm8Uz6Kgo1rTpgm/RYN96jMmB5/xAkfoJngRcn0CT2Cigmq/ YOFcHSBqtRRAGbj9hLdMT0pYgj119oM1YlbZy7k6HYk2Jnrt+dXf3h9ikPsZqXab IkkzNqbOZpNmOSWOCB/4FM1f/9q5uNmL2XS/VxszuXn7KZc1MTyj8b21uD/S7N+D UHBtUOLfO8n+mSyBRFSZ5HnzETQTkLpJ9osY93fZ+7BHnzlv7QbU4Z0jF4eXe8YZ oQ2Ao2z/DythYD14F3ysMr5ZfW/I7TUYl+THwIdoOGZZ53uWc/Ry3Iyltjpk2jjB PSKieVvI2QJVYHzALftOx+u/NmHRmHlyhXTTAeVaTmwwxxpIesXUYLGdMwCXOjDG Fy5W0reG90kVtBqVtIwZenU0AuVG9bEXJQmuZuie8lTu/vKbAICjH1eilvwY6hIZ HSPjk8d52YzWG0qiwypVp4yOcvsUwX8ax10bsl6GiOnWiPM4LWhU+XxLqBXhcFlO oZ9/2SwvV21fi+y4MYBU =BUOX -----END PGP SIGNATURE----- --1yeeQ81UyVL57Vl7--