From owner-freebsd-ports@freebsd.org Sun Jun 26 04:41:23 2016 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 E144AB80533 for ; Sun, 26 Jun 2016 04:41:23 +0000 (UTC) (envelope-from ppathiakis@atlantisservices.net) 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 CD55D1B4A for ; Sun, 26 Jun 2016 04:41:23 +0000 (UTC) (envelope-from ppathiakis@atlantisservices.net) Received: by mailman.ysv.freebsd.org (Postfix) id CC953B80532; Sun, 26 Jun 2016 04:41:23 +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 CC478B80531 for ; Sun, 26 Jun 2016 04:41:23 +0000 (UTC) (envelope-from ppathiakis@atlantisservices.net) Received: from messages.atlantisservices.net (atlantisservices.net [96.39.127.150]) (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 A5EF31B49 for ; Sun, 26 Jun 2016 04:41:23 +0000 (UTC) (envelope-from ppathiakis@atlantisservices.net) Received: from [192.168.0.29] (desktop4.192atlantisservices.net [192.168.0.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by messages.atlantisservices.net (Postfix) with ESMTPSA id BE24C2401F; Sun, 26 Jun 2016 04:41:15 +0000 (UTC) Subject: Re: Asterisk port To: Kyle Evans , Paul Pathiakis References: <45126beb-141b-f0ec-3415-11c994fa5d87@mail.atlantisservices.net> Cc: ports@freebsd.org From: Paul Pathiakis Message-ID: <576F5CEB.20509@atlantisservices.net> Date: Sun, 26 Jun 2016 00:41:15 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jun 2016 04:41:24 -0000 Thank you! Sadly, that was my thread, too... *smacks head* Looks like I'm guilty of a bad filter on my mail folder. Fixed. Thank you all, P. On 6/25/2016 9:48 AM, Kyle Evans wrote: > On Thu, Jun 23, 2016 at 3:34 PM, Paul Pathiakis > wrote: >> Hi, >> >> The port for Asterisk software PBX is woefully out of date. The current >> version is 2.x and the latest in ports/pkgs is 1.8. Version 1.8 is >> DEPRECATED. >> >> Thank you! >> >> Paul Pathiakis > In addition to Kurt's response, here's the previous response from > madpilot@ about versioning: > https://lists.freebsd.org/pipermail/freebsd-ports/2016-June/103439.html From owner-freebsd-ports@freebsd.org Sun Jun 26 06:40:14 2016 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 74119B809F4 for ; Sun, 26 Jun 2016 06:40:14 +0000 (UTC) (envelope-from info@elmolinodesantacruz.com) 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 620C719E3 for ; Sun, 26 Jun 2016 06:40:14 +0000 (UTC) (envelope-from info@elmolinodesantacruz.com) Received: by mailman.ysv.freebsd.org (Postfix) id 5BEB8B809F3; Sun, 26 Jun 2016 06:40:14 +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 5B8A3B809F2 for ; Sun, 26 Jun 2016 06:40:14 +0000 (UTC) (envelope-from info@elmolinodesantacruz.com) Received: from wnv01smtp.worldnetvisions.com (wnv01smtp.worldnetvisions.com [203.81.46.248]) by mx1.freebsd.org (Postfix) with ESMTP id 2549B19E2 for ; Sun, 26 Jun 2016 06:40:13 +0000 (UTC) (envelope-from info@elmolinodesantacruz.com) Received: from wnvpl-wcpanel01.c.curious-memory-93501.internal (227.177.167.107.bc.googleusercontent.com [107.167.177.227]) by wnv01smtp.worldnetvisions.com (Postfix) with ESMTP id 455AA2917E3 for ; Sun, 26 Jun 2016 13:28:40 +0800 (SGT) Received: from [198.20.167.133] (port=61581 helo=elmolinodesantacruz.com) by wnvpl-wcpanel01.c.curious-memory-93501.internal with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.87) (envelope-from ) id 1bH2mY-00031W-1g for ports@freebsd.org; Sun, 26 Jun 2016 13:38:58 +0800 From: Alex Lim To: ports@freebsd.org Subject: Re: swift copy Date: 25 Jun 2016 22:38:37 -0700 Message-ID: <20160625223837.6947C81F5C78271D@elmolinodesantacruz.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jun 2016 06:40:14 -0000 From owner-freebsd-ports@freebsd.org Sun Jun 26 09:40:40 2016 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 0033BB809E6 for ; Sun, 26 Jun 2016 09:40:40 +0000 (UTC) (envelope-from sean@slcasa.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id C3F9A129C for ; Sun, 26 Jun 2016 09:40:39 +0000 (UTC) (envelope-from sean@slcasa.com) Received: by mailman.ysv.freebsd.org (Postfix) id BF82AB809E5; Sun, 26 Jun 2016 09:40:39 +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 BF1D7B809E4 for ; Sun, 26 Jun 2016 09:40:39 +0000 (UTC) (envelope-from sean@slcasa.com) Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0103.outbound.protection.outlook.com [207.46.100.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A772E1297; Sun, 26 Jun 2016 09:40:38 +0000 (UTC) (envelope-from sean@slcasa.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=GY6.onmicrosoft.com; s=selector1-slcasa-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=zWTV703iQAjDhq+abq2pIgoQl0s2+/6XzlmPi8jIg9g=; b=RhJhvGd3M5eyt09KUwlGG/q/Klsh6X1wola5g8VNJJNlGKLMsNTWWgAEahgSP0j8kLJLhZy2tZjN43+lxPlRgc4HMErT1eoBJ8r0D+wLvDp25uM17Il4wlJxvcrWRCFlwwDU51RSq34/nZMKWtIArEnjSg7ZZzOCU4A1ldWMZpg= Received: from BY2PR0101MB1446.prod.exchangelabs.com (10.163.152.140) by BY2PR0101MB1448.prod.exchangelabs.com (10.163.152.142) with Microsoft SMTP Server (TLS) id 15.1.523.12; Sun, 26 Jun 2016 09:25:14 +0000 Received: from BY2PR0101MB1446.prod.exchangelabs.com ([10.163.152.140]) by BY2PR0101MB1446.prod.exchangelabs.com ([10.163.152.140]) with mapi id 15.01.0523.019; Sun, 26 Jun 2016 09:25:14 +0000 From: Sean To: "rm@FreeBSD.org" CC: "ports@FreeBSD.org" Subject: FreeBSD Port: deluge-1.3.12,1 Thread-Topic: FreeBSD Port: deluge-1.3.12,1 Thread-Index: AdHPihKUoupvWduSRkCxGNiMuqUrJw== Date: Sun, 26 Jun 2016 09:25:14 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=sean@slcasa.com; x-originating-ip: [107.184.146.42] x-ms-office365-filtering-correlation-id: 0f63b4b1-9d9b-4731-b704-08d39da3c7fa x-microsoft-exchange-diagnostics: 1; BY2PR0101MB1448; 6:cRsZxreXULz5E1u9FXCqnLZT229k4L/JJ+t4KhRfKDFKpIrVMgUSZgEiPyBTuAwp+xYHZPDgKBKxTXlY3n3TvV+4JoJqAOTnCQd7WBA++NNDfROjZZWeJExxXlfDfI4va8FVe2Hg4uj6zvufNS6d9FfX4m6iXuqvNecI5q+d6XUvZc7+38Mo9BT3HblaPo769iwRsabjTqwsyCEd8Xf1waKGqnj73+1uX1/XxK3ibebWIEAuhyZJbpyCvlfUq+8Yat0uizn8LgbB/IQc+046fZxWLTfHEq8IjfE/UY6Eilh5BwTEz1BFW+489f+1BreIBKVWuWLszQRQuXGi1/s7wg==; 5:NQuT3GEpM8GHf2NEjuSPss8+kDjs759UgYLsi019qBwxbz4ERC+NmJs/cmZOzxQhSTQmLjiAlnGGgcIPBbVYPv3m688IZO0V5MhRUFpY/V8EYCeFsnIxR6TovvY4+lrshyei4AcJrDjXcRt48YaNTQ==; 24:53AYXFjElcfdulqhXyjtIs+ee61v0RhoSFQii999bkqeedJvggSragX/b08mji/83kM35DpMXog24Sb1hIZmxqjgNU268Cn2Y3cYTYdHjZo=; 7:UcKP5BYg8BOSMnQDEDoLUcEZn5Aa5/RMVpYJYruQc19Q+az2wHmGT5LZ1zgFgJky34Z9eT8em+90FMCJ82Syo7mGRM5XY9HfNAurXgCLzkFkUbWwJgV9V0Y7Kl7gormBruJVXEroi7NGJwZgbplEtYkNbLl5oI3t5rDAjP0f4a2aXzhWhfKgChlyEMhHN2ua7Hkdlh6mM1nXnuvaiH8ufZP9PGt6MtW0c6L0Lm/eMFzsjXE/zaJebIKLRiXKeQc2pDyF9kgS4rut3J2DHqYvBw== x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2PR0101MB1448; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(21748063052155); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040130)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041072)(6043046); SRVR:BY2PR0101MB1448; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0101MB1448; x-forefront-prvs: 0985DA2459 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(189002)(5423002)(199003)(66066001)(189998001)(2900100001)(87936001)(10400500002)(19580395003)(97736004)(9686002)(81166006)(11100500001)(81156014)(105586002)(5003600100003)(7696003)(33656002)(8936002)(101416001)(106356001)(7736002)(19625215002)(86362001)(15975445007)(92566002)(229853001)(77096005)(110136002)(2351001)(50986999)(54356999)(7846002)(558084003)(586003)(3660700001)(19300405004)(2906002)(74316001)(3846002)(5640700001)(5630700001)(790700001)(6116002)(102836003)(2501003)(450100001)(4326007)(122556002)(3280700002)(5002640100001)(1730700003)(16236675004)(8676002)(68736007); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0101MB1448; H:BY2PR0101MB1446.prod.exchangelabs.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: slcasa.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: slcasa.com X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jun 2016 09:25:14.3253 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 4a88c908-bbfd-439b-9a57-2588ae2c1f10 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0101MB1448 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jun 2016 09:40:40 -0000 pkg install deluge is installing everything but deluge. Something changed f= rom when I installed it earlier this year. I noticed you made some changes a couple of month ago. Sorry if I sent this to the wrong place. Sean Choquette From owner-freebsd-ports@freebsd.org Sun Jun 26 15:17:35 2016 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 1EB17B81224 for ; Sun, 26 Jun 2016 15:17:35 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD73D2C05 for ; Sun, 26 Jun 2016 15:17:34 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: by mail-qk0-x22c.google.com with SMTP id t127so186384168qkf.1 for ; Sun, 26 Jun 2016 08:17:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=2kdWRBPA6LeZ8IUu5RVpHu6PjImWSadyqU3FMisIqHI=; b=kwQUxzjBgPi2HEJGVITTuJCMrlOtH76bC4ZmmXNpNCruHa0wYHCZOR+uny9iqHRNsw dG0tAAQvzYjxn9trF8gtaTFwDNXAnbZnhbL8GLssKCQVSeXuJpsyj+KIKwpTL0MLGnW6 ZIdBzIiLm1HeYPYYwAHbaHdktzSgLzF146am4x2gHeDQOOgrv9SObywZj+G7q0NvFsfE R8Tly9AJheHro3CAH4AKbbfCCrSQ60S3Qc8ZKsZUC4GYn65qzomcB3jXmEqhv6pxY2Rq S7yNLQKGdxmEr6AxxIeWYByXT3DXfHD4/B1aMnkpDRsffaUK/mEge0bHvbJcfD+OgFpG BPKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=2kdWRBPA6LeZ8IUu5RVpHu6PjImWSadyqU3FMisIqHI=; b=IxyU5XIlxqpgj2AP7mmks8T0fsh1X28aN9tnKPzo5s6GS0qcuq6G6SmZCf0U16sRTo l7bJOAYIMLpiOWZgaurMnXYYTM7dCMJbpMN4qGtuX4OZ8uHaJFmAaT57Z0djTtWcM8KI +uQ030r4urvRllTBE1Dtoj8Xvsmhp/pYqZL4vywxm4YjrVicNzx1fO4nWp3NLyGrdr0o HKn2OXz0iPGMsnRNiiThmdAW3WWL90b4NNhvMsRm0lj6DMXm7TFRmOk0oVFDeOvL6FRD BtX2TnBOBqXCcbCSp6BG7KZq1IB21m1ox0Mp/VyOjD3d39X1OAKq4FHmSVUs4PXia75n r0kQ== X-Gm-Message-State: ALyK8tLTvXAWkIhpkQq9xDqttwDiraM7QKgWvqu42zeMmb8x1IPZuQCL/oyrhDWi1THnvUAcvsYZrRVhMPBXXg== X-Received: by 10.55.155.18 with SMTP id d18mr18090642qke.103.1466954254013; Sun, 26 Jun 2016 08:17:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.77.135 with HTTP; Sun, 26 Jun 2016 08:17:33 -0700 (PDT) In-Reply-To: References: <20160625082348.GG20495@graf.pompo.net> From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= Date: Sun, 26 Jun 2016 17:17:33 +0200 Message-ID: Subject: Re: QA script error (libc++) To: Ben Woods Cc: FreeBSD Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jun 2016 15:17:35 -0000 On Sat, Jun 25, 2016 at 7:50 PM, Ben Woods wrote: > On Saturday, 25 June 2016, Fernando Apestegu=C3=ADa >> >> Also portlint doesn't seem to be in sync with >> the new stuff in ports. In my case it complains about the TIMESTAMP >> new line in distinfo and the directories not found in the ports >> collection (due to the removal of ${PORTSDIR} while defining the >> dependencies). >> >> Thanks! >> >> > -- >> > Th. Thomas. > > > If you update your version of portlint to 2.17.2 it can handle both of th= ose > things. > http://www.freshports.org/ports-mgmt/portlint I missed that because I sticked to the the quaterly branch in pkg. Thanks! > > Regards, > Ben > > > -- > > -- > From: Benjamin Woods > woodsb02@gmail.com From owner-freebsd-ports@freebsd.org Sun Jun 26 17:14:38 2016 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 04F5FB81DE3 for ; Sun, 26 Jun 2016 17:14:38 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id E1534219E for ; Sun, 26 Jun 2016 17:14:37 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id DD213B81DE2; Sun, 26 Jun 2016 17:14:37 +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 DCD06B81DE1 for ; Sun, 26 Jun 2016 17:14:37 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from vfemail.net (onethreetwo.vfemail.net [199.16.11.132]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9DE1D219B for ; Sun, 26 Jun 2016 17:14:37 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: (qmail 38778 invoked by uid 89); 26 Jun 2016 17:14:30 -0000 Received: from localhost (HELO freequeue.vfemail.net) (127.0.0.1) by localhost with (DHE-RSA-AES256-SHA encrypted) SMTP; 26 Jun 2016 17:14:30 -0000 Received: (qmail 73941 invoked by uid 89); 26 Jun 2016 12:00:22 -0000 Received: by simscan 1.3.1 ppid: 73937, pid: 73939, t: 0.0024s scanners:none Received: from unknown (HELO smtp102-2.vfemail.net) (172.16.100.62) by FreeQueue with SMTP; 26 Jun 2016 12:00:22 -0000 Received: (qmail 2373 invoked by uid 89); 26 Jun 2016 12:00:22 -0000 Received: by simscan 1.4.0 ppid: 2352, pid: 2370, t: 0.8940s scanners:none Received: from unknown (HELO nil) (amJlaWNoQHZmZW1haWwubmV0@172.16.100.27) by mail.vfemail.net with ESMTPA; 26 Jun 2016 12:00:21 -0000 From: Jan Beich To: FreeBSD Ports mailing list Cc: Bryan Drewery Subject: USE_PACKAGE_DEPENDS_ONLY set - not building missing dependency from source References: <201606250232.u5P2Wndq091282@beefy5.nyi.freebsd.org> Date: Sun, 26 Jun 2016 14:00:03 +0200 In-Reply-To: <201606250232.u5P2Wndq091282@beefy5.nyi.freebsd.org> (pkg-fallout@freebsd.org's message of "Sat, 25 Jun 2016 02:32:49 GMT") Message-ID: <7fdc-gny4-wny@vfemail.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jun 2016 17:14:38 -0000 --=-=-= Content-Type: text/plain pkg-fallout@FreeBSD.org writes: > Ident: $FreeBSD: head/multimedia/vapoursynth/Makefile 415615 2016-05-22 01:10:34Z jbeich $ > Log URL: http://beefy5.nyi.freebsd.org/data/101i386-default/417455/logs/vapoursynth-r32.log > Build URL: http://beefy5.nyi.freebsd.org/build.html?mastername=101i386-default&build=417455 > Log: > > build started at Sat Jun 25 02:32:41 UTC 2016 [...] > =================================================== > ===> vapoursynth-r32 depends on executable: sphinx-build - not found > ===> vapoursynth-r32 depends on package: /packages/All/py34-sphinx-1.4.4.txz - not found > ===> USE_PACKAGE_DEPENDS_ONLY set - not building missing dependency from source > *** Error code 1 I'm starting to get failures for a port that hasn't changed for a month. Anyone got a clue? The regression appears to be from r417413 which landed without an exp-run suggesting any fallout is due to badly written ports. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQF8BAEBCgBmBQJXb8PDXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREQjQ0MzY3NEM3RDIzNTc4NkUxNDkyQ0VF NEM3Nzg4MzQ3OURCRERCAAoJEOTHeINHnb3buA0IAKORRojnJLWYHVpUQllHGoNa doNC2is3oUxks0gVM/ZO/vdu9QQzpoysvt5BLzDtvu8GFWqsSdulTbksFDbyj103 L3jwB11w5F+5/sWeF3RgNyOQAibYiza3e0xToELn8STq6Xj0hDipse1pWrH2Ewaf 3j+VZEtDqk8Fy3e90n59ccSjqILjKsKstbupAzwCd8GnlD9NirugDcBo/xIK9nxi +ILHL8KTIf4of8O5WqELKSpmBnvIX9OrSa3IiMM3JTZlygAtjo6BfmNpNUopZDYF OxXxyJBW0uGy34lW2FwYqkPIXX4qQpKcD7RU/h8ZLcNEfsklhDywqi5G4du/rWs= =C/Fe -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-ports@freebsd.org Mon Jun 27 09:16:09 2016 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 298B2B847BD for ; Mon, 27 Jun 2016 09:16:09 +0000 (UTC) (envelope-from matthias.andree@tu-dortmund.de) Received: from unimail.uni-dortmund.de (mx1.HRZ.tu-dortmund.de [129.217.128.51]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "unimail.tu-dortmund.de", Issuer "TU Dortmund CA - G01" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 481EE24F3; Mon, 27 Jun 2016 09:16:08 +0000 (UTC) (envelope-from matthias.andree@tu-dortmund.de) Received: from mandree.no-ip.org (x4e30e39e.dyn.telefonica.de [78.48.227.158]) (authenticated bits=0) by unimail.uni-dortmund.de (8.16.0.16/8.16.0.16) with ESMTPSA id u5R9G59J021082 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 27 Jun 2016 11:16:06 +0200 (CEST) Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 4AB1123CF76; Mon, 27 Jun 2016 11:16:05 +0200 (CEST) From: Matthias Andree Subject: blanket portmgr approval vs. non-fixing changes (was: svn commit: r417590 - in head/databases/db6: . files and 417595 (revert)) To: Mathieu Arnold , araujo@freebsd.org References: <201606261724.u5QHOLdG081392@repo.freebsd.org> <57701AEB.1050001@tu-dortmund.de> <5770A392.6010605@tu-dortmund.de> <84e4fcf5-7b99-1cc6-e6bd-d3c594a5d102@marino.st> <91BC5F8F9FDB9246529D0693@atuin.in.mat.cc> Cc: marino@freebsd.org, Sunpoet Po-Chuan Hsieh , ports-committers , FreeBSD Ports Management Team , freebsd-ports@FreeBSD.org Message-ID: <5770EED4.1070202@tu-dortmund.de> Date: Mon, 27 Jun 2016 11:16:04 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <91BC5F8F9FDB9246529D0693@atuin.in.mat.cc> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 09:16:09 -0000 [Sorry for this re-send, I feel we need to re-send thisto ports@ so the discussion goes to a public and archived list.] Am 27.06.2016 um 10:16 schrieb Mathieu Arnold: > > > +--On 27 juin 2016 16:10:36 +0800 Marcelo Araujo > wrote: > | 2016-06-27 16:02 GMT+08:00 Mathieu Arnold : > |> | Read here for reference: > |> | > |> https://www.freebsd.org/doc/en/books/porters-handbook/makefile-maintainer > |> | .html > |> > |> That pages says, exactly the opposite of what you are trying to says: > |> > | > | No it doesn't! > | > | And this is the normal workflow: > | 1) Port has a maintainer, and it needs update. > | 2) Open a PR with the patch. > | 3) After 2 weeks, and with timeout; anybody can commit it. > | > | > | And about the ownership and belong to the community, I do believe in that, > | that is the basic in a legal point of view. > > That page says that the maintainer has to be consulted, except for changes > covered by the blanket approval, where the change can be committed > immediately. > > In this case, Sunpoet had every right to commit the thing he did without > asking or notifying the maintainer. TL;DR given at the very end. 1. Given the portmgr@ rules, that is our current policy, that portmgr@ as the overseers of the ports system have delegated, by the blanket approval, part of their ultimate responsibility to the public. 2. What I was meaning to state was that (and I'll not pick at the kind soul who has modernized the port) we should only apply the blanket approval if ports have fallen into disrepair. 2b. This was not the case with db6, the port wasn't known broken to me, so why do we permit and encourage going the fast path for changes that do not /repair/ a port (for instance, if it's not building, to fix misspellings), and I'm surprised because some two months ago, it has already gone through a modernization round after gahr's PR, , that also combined a feature addition and required a bit more work to get right, see changesets 415741 and 415743. 3. What would have been bad about filing a PR in this case? The argument "maintainers aren't doing it" is covered by the maintainer timeout. Anything that does not need the fast path should go through some form of review, most naturally through a PR filed to the port's maintainer. 4. Do we need to tighten up the set of required tests a committed does before committing non-maintainer updates? I'm scratching my head over this one since the failure in r417590 that got remedied in r417595 was rather peculiar, and I'm not sure if anyone, including myself, would have figured that out. It might have slipped through the cracks even if I'd reviewed it. 4b. It's probably better to extend the committer's guide and/or porter's handbook and have a list of test recommendations where we list things that trigger a certain test requirement. I. e. things to test IN ADDITION to the usual "poudriere testport" or "make DEVELOPER=yes clean all check-plist package" and portlint coverage. Meaning that if someone tweaks any of the WRK* and *DIR/*SRC-related variables, "also test 'make clean extract do-patch makepatch' on a copy of the port directory" or thereabouts. There seem to be at least two distinct camps, in one camp, maintainers go along Marcelo's and my trains of thought, in the other, maintainers cherish fast and low-ceremony progress, marino has argued along these lines, and some other portmgr@ members have pushed for progress in the past. I don't mean to bikeshed or split up our project here, just refine our existing policies. TL;DR: I propose: - the blanket approval should be tightened up a bit and encourage that non-trivial and non-urgent changes go through the PR and invoke mantainer timeout after the shortest possible period. - we discuss about an assisting set of "change these variables foo.*regexp, and you also need to test 'make foo' and 'make bar'" rules in the form of a concise list. From owner-freebsd-ports@freebsd.org Mon Jun 27 09:27:33 2016 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 46366B84BB1 for ; Mon, 27 Jun 2016 09:27:33 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F2B092B13; Mon, 27 Jun 2016 09:27:32 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: by mail-yw0-x22f.google.com with SMTP id b72so150884501ywa.3; Mon, 27 Jun 2016 02:27:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=YJ8zbfnpXNXKqhbisJ9BGFJFYFjjzXFUQvjNICLa4Vs=; b=N6KFbaeeHaHqMZr9zy2Y/4smLzCgv/XQPFcGI2tqvx32iW8gd+bT3qtJzlac07GJd0 4hmrNZIxIEXIUHFzjpIkSsd7nWrfE3BR7ZU+Ew6qFpxLRq91zbixDvYAwc9XSZrmkGE3 QAslxumd0D3jMkPHp1drTqfhvao6cXro/U7hGx4Jqd39xy22hLsubTJIjj+/p0GuEMHL PGUjmfaAK2QyrsRcI3AFA/BLuu2FeSskV6FpNpJjmxvnkA3ggn8YqRoqwMMhVLmmvP8x Lquv+paZPKc5C/rxSxoAndPkl3nAOt+hj8LWfYodfzbx+A4UVrwQZG4ihILQl/YrYAR8 dBeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=YJ8zbfnpXNXKqhbisJ9BGFJFYFjjzXFUQvjNICLa4Vs=; b=UZHGq59pHKOLIkJzdSrCMoGLacdm1xyf22amTjecLnir3+mrx4dg3B3fT0Do6JX9Fk 530EjqGDURWhxku//QA04HHua12/r4VMFznQTr4JV+yFnuuIBreBROxoPsBiJajxZvig hBCIipzjRNgRP0Xmtv52g5BExU1XbAqSf8yFlReEVcNow4nkUJb6tubeVan94N3I7oDA SkbMoCHde6lCnQKXY9cpG1utIvs+lU38YEFu7LzDN7mLBEgfgpoumdMjPu/6CKhIN/pj ef/GFKt27IyfEPilzEt0uGdeiT9nbDUkI67ahr4Ipcpi+UnrYJseMDCcHB6B0cgIG7PM Mr7Q== X-Gm-Message-State: ALyK8tIykVV5k2hBNdUENDGnrIrqMkzXUZWqh6wAa3FkS9hU3Rxe2Uy5Bog9Opeelqqz/k1rvQKkWHZSjYnSSA== X-Received: by 10.37.212.207 with SMTP id m198mr10981333ybf.20.1467019652063; Mon, 27 Jun 2016 02:27:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.10.212 with HTTP; Mon, 27 Jun 2016 02:27:31 -0700 (PDT) Reply-To: araujo@freebsd.org In-Reply-To: <5770EAD2.4060302@tu-dortmund.de> References: <201606261724.u5QHOLdG081392@repo.freebsd.org> <57701AEB.1050001@tu-dortmund.de> <5770A392.6010605@tu-dortmund.de> <84e4fcf5-7b99-1cc6-e6bd-d3c594a5d102@marino.st> <91BC5F8F9FDB9246529D0693@atuin.in.mat.cc> <5770EAD2.4060302@tu-dortmund.de> From: Marcelo Araujo Date: Mon, 27 Jun 2016 17:27:31 +0800 Message-ID: Subject: Re: blanket portmgr approval vs. non-fixing changes (was: svn commit: r417590 - in head/databases/db6: . files and 417595 (revert)) To: Matthias Andree Cc: Mathieu Arnold , marino@freebsd.org, Sunpoet Po-Chuan Hsieh , ports-committers , FreeBSD Ports Management Team , freebsd-ports Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 09:27:33 -0000 2016-06-27 16:58 GMT+08:00 Matthias Andree : > Am 27.06.2016 um 10:16 schrieb Mathieu Arnold: > > > > > > +--On 27 juin 2016 16:10:36 +0800 Marcelo Araujo < > araujobsdport@gmail.com> > > wrote: > > | 2016-06-27 16:02 GMT+08:00 Mathieu Arnold : > > |> | Read here for reference: > > |> | > > |> > https://www.freebsd.org/doc/en/books/porters-handbook/makefile-maintainer > > |> | .html > > |> > > |> That pages says, exactly the opposite of what you are trying to says: > > |> > > | > > | No it doesn't! > > | > > | And this is the normal workflow: > > | 1) Port has a maintainer, and it needs update. > > | 2) Open a PR with the patch. > > | 3) After 2 weeks, and with timeout; anybody can commit it. > > | > > | > > | And about the ownership and belong to the community, I do believe in > that, > > | that is the basic in a legal point of view. > > > > That page says that the maintainer has to be consulted, except for > changes > > covered by the blanket approval, where the change can be committed > > immediately. > > > > In this case, Sunpoet had every right to commit the thing he did without > > asking or notifying the maintainer. > > > TL;DR given at the very end. > > > 1. Given the portmgr@ rules, that is our current policy, that portmgr@ > as the overseers of the ports system have delegated, by the blanket > approval, part of their ultimate responsibility to the public. > > 2. What I was meaning to state was that (and I'll not pick at the kind > soul who has modernized the port) we should only apply the blanket > approval if ports have fallen into disrepair. > > > 2b. This was not the case with db6, the port wasn't known broken to me, > so why do we permit and encourage going the fast path for changes that > do not /repair/ a port (for instance, if it's not building, to fix > misspellings), and I'm surprised because some two months ago, it has > already gone through a modernization round after gahr's PR, > , that also > combined a feature addition and required a bit more work to get right, > see changesets 415741 and 415743. > > > 3. What would have been bad about filing a PR in this case? > > The argument "maintainers aren't doing it" is covered by the maintainer > timeout. Anything that does not need the fast path should go through > some form of review, most naturally through a PR filed to the port's > maintainer. > > > 4. Do we need to tighten up the set of required tests a committed does > before committing non-maintainer updates? > > I'm scratching my head over this one since the failure in r417590 that > got remedied in r417595 was rather peculiar, and I'm not sure if anyone, > including myself, would have figured that out. It might have slipped > through the cracks even if I'd reviewed it. > > 4b. It's probably better to extend the committer's guide and/or porter's > handbook and have a list of test recommendations where we list things > that trigger a certain test requirement. I. e. things to test IN > ADDITION to the usual "poudriere testport" or "make DEVELOPER=yes clean > all check-plist package" and portlint coverage. Meaning that if someone > tweaks any of the WRK* and *DIR/*SRC-related variables, "also test 'make > clean extract do-patch makepatch' on a copy of the port directory" or > thereabouts. > mat@ thanks for all the explanation and time. Unfortunately, I still make things a bit manual at my side, but usually my testbed is: 1) Portlint. 2) Make and likes on i386 and amd64(clean vm). I think, include more information about test recommendations is always good. > > > There seem to be at least two distinct camps, in one camp, maintainers > go along Marcelo's and my trains of thought, in the other, maintainers > cherish fast and low-ceremony progress, marino has argued along these > lines, and some other portmgr@ members have pushed for progress in the > past. > > I don't mean to bikeshed or split up our project here, just refine our > existing policies. > > > TL;DR: I propose: > > - the blanket approval should be tightened up a bit and encourage that > non-trivial and non-urgent changes go through the PR and invoke > mantainer timeout after the shortest possible period. > Personally, I like the first option! And in addition, we have phabricator as an option too, at least for src, the reviews are made very quickly. So, could be defined a short timeout, at least for those that are active and would like to help make a review, seems something reasonable. Also I do understand about all the modernization and definitely we need it, maybe 2 days timeout is enough for an active maintainer to reply that he is busy or he is working on that. > > - we discuss about an assisting set of "change these variables > foo.*regexp, and you also need to test 'make foo' and 'make bar'" rules > in the form of a concise list. > > Thanks, -- -- Marcelo Araujo (__)araujo@FreeBSD.org \\\'',)http://www.FreeBSD.org \/ \ ^ Power To Server. .\. /_) From owner-freebsd-ports@freebsd.org Mon Jun 27 10:06:31 2016 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 1AF36B81C37 for ; Mon, 27 Jun 2016 10:06:31 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 08F6A22CC for ; Mon, 27 Jun 2016 10:06:31 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 04D62B81C36; Mon, 27 Jun 2016 10:06:31 +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 047E3B81C35 for ; Mon, 27 Jun 2016 10:06:31 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org (portscout.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (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 EC5A522CB for ; Mon, 27 Jun 2016 10:06:30 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.15.2/8.15.2) with ESMTP id u5RA6Uks033177 for ; Mon, 27 Jun 2016 10:06:30 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.15.2/8.15.2/Submit) id u5RA6Uok033176; Mon, 27 Jun 2016 10:06:30 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201606271006.u5RA6Uok033176@portscout.freebsd.org> X-Authentication-Warning: portscout.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Mon, 27 Jun 2016 10:06:30 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 10:06:31 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ graphics/netpbm | 10.35.98 | 10.47.62 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Mon Jun 27 10:13:01 2016 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 7F81FB81E87 for ; Mon, 27 Jun 2016 10:13:01 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (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 2B4FC27ED for ; Mon, 27 Jun 2016 10:13:00 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3rdPd51sDvzZsD for ; Mon, 27 Jun 2016 12:02:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject:received:received; s=mail; t= 1467021767; x=1468836168; bh=JGuZd+wbbmJc53DuN4Rnt3FbnuFaR918V2/ jX9F/D50=; b=aOB3dGD5REXatCW1zYJkEqNsjmYU4PhHQCcym7lOC6Vwl1+SG14 4UhXYlQ+FrkOxMFP4K7W4BkCKt5GISPTEmg0QYCs/8p7nauLr35NeRnwl9mpdLJT AOEO0Rojf3qkcQpFkVC2nWdXyov/YdNGx/nFGQ4iH58kgGXxkXPWX5Vg= Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id q3i2_45hMLOd for ; Mon, 27 Jun 2016 12:02:47 +0200 (CEST) Received: from marvin.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA for ; Mon, 27 Jun 2016 12:02:47 +0200 (CEST) Subject: Re: blanket portmgr approval vs. non-fixing changes To: freebsd-ports@freebsd.org References: <201606261724.u5QHOLdG081392@repo.freebsd.org> <57701AEB.1050001@tu-dortmund.de> <5770A392.6010605@tu-dortmund.de> <84e4fcf5-7b99-1cc6-e6bd-d3c594a5d102@marino.st> <91BC5F8F9FDB9246529D0693@atuin.in.mat.cc> <5770EED4.1070202@tu-dortmund.de> From: Guido Falsi Message-ID: <18e609c1-e095-99b0-893a-0bb30d3c3d45@madpilot.net> Date: Mon, 27 Jun 2016 12:02:46 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <5770EED4.1070202@tu-dortmund.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 10:13:01 -0000 On 06/27/16 11:16, Matthias Andree wrote: > [Sorry for this re-send, I feel we need to re-send thisto ports@ so the > discussion goes to a public and archived list.] > > Am 27.06.2016 um 10:16 schrieb Mathieu Arnold: >> >> >> +--On 27 juin 2016 16:10:36 +0800 Marcelo Araujo >> wrote: >> | 2016-06-27 16:02 GMT+08:00 Mathieu Arnold : >> |> | Read here for reference: >> |> | >> |> https://www.freebsd.org/doc/en/books/porters-handbook/makefile-maintainer >> |> | .html >> |> >> |> That pages says, exactly the opposite of what you are trying to says: >> |> >> | >> | No it doesn't! >> | >> | And this is the normal workflow: >> | 1) Port has a maintainer, and it needs update. >> | 2) Open a PR with the patch. >> | 3) After 2 weeks, and with timeout; anybody can commit it. >> | >> | >> | And about the ownership and belong to the community, I do believe in that, >> | that is the basic in a legal point of view. >> >> That page says that the maintainer has to be consulted, except for changes >> covered by the blanket approval, where the change can be committed >> immediately. >> >> In this case, Sunpoet had every right to commit the thing he did without >> asking or notifying the maintainer. > > > TL;DR given at the very end. > > > 1. Given the portmgr@ rules, that is our current policy, that portmgr@ > as the overseers of the ports system have delegated, by the blanket > approval, part of their ultimate responsibility to the public. > > 2. What I was meaning to state was that (and I'll not pick at the kind > soul who has modernized the port) we should only apply the blanket > approval if ports have fallen into disrepair. I'd say that it's a matter of urgency for the change. Need for urgency is evident for broken ports and also serious security issues. It could be less evident for infrastructure changes which need to be urgently deployed to a major number of ports, or changes to head which require patching a lot of ports (one good example could be the recent update to libc++ 3.8.0 in head, even if it could be accounted as "broken ports" case, so with a relatively high degree of urgency). > 3. What would have been bad about filing a PR in this case? > > The argument "maintainers aren't doing it" is covered by the maintainer > timeout. Anything that does not need the fast path should go through > some form of review, most naturally through a PR filed to the port's > maintainer. > I agree with this, if there is no urgency there's no need to leverage a blanket. > TL;DR: I propose: > > - the blanket approval should be tightened up a bit and encourage that > non-trivial and non-urgent changes go through the PR and invoke > mantainer timeout after the shortest possible period. I agree on adding a note on the blankets encouraging patches to go through a PR whenever they are not urgent. This raises the problem of having a good definition of urgent. I have stated above what I think is urgent. I'd like to add that changes to the ports infrastructure aren't always urgent, the general blanket was created at a time when a lot of things were changing in the ports tree and there was a need for a fast application of those changes, since the state of the tree was hindering progress. We are now in a much better situation and most changes are less urgent, and can wait some time. I'd say usually such changes should go through bugzilla or phabric review, with portmgr adding special case blankets for specific changes which should hit the tree as soon as possible, if this is not an excessive burden on portmgr. I'm not sure I agree on lowering the 14 days timeout for bug reports. I usually reply in a matter of hours if at all possible, 2-3 days when I take a long time, at least with a "going to test" message, but not all people can manage this, lowering timeouts could raise the bar on being a maintainer which is something I think we should avoid. > > - we discuss about an assisting set of "change these variables > foo.*regexp, and you also need to test 'make foo' and 'make bar'" rules > in the form of a concise list. I think it could be enough to state a list of make targets which one must warrant keep working, it's obvious that make config, make install and make deinstall should work correctly, less obvious for other targets. -- Guido Falsi From owner-freebsd-ports@freebsd.org Mon Jun 27 10:34:31 2016 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 0D96AB80366 for ; Mon, 27 Jun 2016 10:34:31 +0000 (UTC) (envelope-from hps@selasky.org) 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 ED2A32222 for ; Mon, 27 Jun 2016 10:34:30 +0000 (UTC) (envelope-from hps@selasky.org) Received: by mailman.ysv.freebsd.org (Postfix) id EC832B80365; Mon, 27 Jun 2016 10:34:30 +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 EC079B80363; Mon, 27 Jun 2016 10:34:30 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 459AC2221; Mon, 27 Jun 2016 10:34:30 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 5CE521FE022; Mon, 27 Jun 2016 12:34:21 +0200 (CEST) Subject: pkg SAT_SOLVER bugs To: Slawa Olhovchenkov , Baptiste Daroussin References: <20150414200459.GE39658@ivaldir.etoilebsd.net> <20150421103454.GR1394@zxy.spb.ru> <5593D0AE.2010205@selasky.org> Cc: ports@FreeBSD.org, FreeBSD Current From: Hans Petter Selasky Message-ID: <416359ce-1dcd-1160-5c56-f120a0f6358f@selasky.org> Date: Mon, 27 Jun 2016 12:38:02 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <5593D0AE.2010205@selasky.org> Content-Type: multipart/mixed; boundary="------------AA5E85B16E334BA99B677397" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 10:34:31 -0000 This is a multi-part message in MIME format. --------------AA5E85B16E334BA99B677397 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi, I found some bugs in PKG with regard to the SAT_SOLVER environment variable. Please find patch attached :-) Issues fixed: 1) No need to use hash table when generating SAT rules for external solver. Variables are already in a linear array. Fix encoding and decoding of SAT data. 2) Endless variable loop caused pkg to crash. 3) it->inverse was checked for non-zero, while it should actually be checked for -1 only. SAT rules produces were all negative. How to verify: make -C /usr/ports/math/picosat all install clean env SAT_SOLVER=picosat pkg upgrade --HPS --------------AA5E85B16E334BA99B677397 Content-Type: text/x-patch; name="pkg.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="pkg.diff" --- ./work/pkg-1.8.99.6/libpkg/pkg_solve.c.orig 2016-06-27 10:32:46.119810000 +0200 +++ ./work/pkg-1.8.99.6/libpkg/pkg_solve.c 2016-06-27 12:28:07.901757000 +0200 @@ -118,8 +118,6 @@ #define PKG_SOLVE_CHECK_ITEM(item) \ ((item)->var->to_install ^ (item)->inverse) -#define PKG_SOLVE_VAR_NEXT(a, e) ((e) == NULL ? &a[0] : (e + 1)) - /* * Utilities to convert jobs to SAT rule */ @@ -1302,45 +1300,23 @@ fprintf(file, "}\n"); } -struct pkg_solve_ordered_variable { - struct pkg_solve_variable *var; - int order; - UT_hash_handle hh; -}; - int pkg_solve_dimacs_export(struct pkg_solve_problem *problem, FILE *f) { - struct pkg_solve_ordered_variable *ordered_variables = NULL, *nord; - struct pkg_solve_variable *var; struct pkg_solve_rule *rule; struct pkg_solve_item *it; - int cur_ord = 1; - - /* Order variables */ - var = NULL; - while ((var = PKG_SOLVE_VAR_NEXT(problem->variables, var))) { - nord = calloc(1, sizeof(struct pkg_solve_ordered_variable)); - nord->order = cur_ord ++; - nord->var = var; - HASH_ADD_PTR(ordered_variables, var, nord); - } fprintf(f, "p cnf %d %zu\n", (int)problem->nvars, kv_size(problem->rules)); for (unsigned int i = 0; i < kv_size(problem->rules); i++) { rule = kv_A(problem->rules, i); LL_FOREACH(rule->items, it) { - HASH_FIND_PTR(ordered_variables, &it->var, nord); - if (nord != NULL) { - fprintf(f, "%s%d ", (it->inverse ? "-" : ""), nord->order); - } + size_t order = it->var - problem->variables; + if (order < problem->nvars) + fprintf(f, "%ld ", (long)((order + 1) * it->inverse)); } fprintf(f, "0\n"); } - - HASH_FREE(ordered_variables, free); - return (EPKG_OK); } @@ -1443,26 +1419,42 @@ return (EPKG_OK); } +static bool +pkg_solve_parse_sat_output_store(struct pkg_solve_problem *problem, const char *var_str) +{ + struct pkg_solve_variable *var; + ssize_t order; + + order = strtol(var_str, NULL, 10); + if (order == 0) + return (true); + if (order < 0) { + /* negative value means false */ + order = - order - 1; + if ((size_t)order < problem->nvars) { + var = problem->variables + order; + var->flags &= ~PKG_VAR_INSTALL; + } + } else { + /* positive value means true */ + order = order - 1; + if ((size_t)order < problem->nvars) { + var = problem->variables + order; + var->flags |= PKG_VAR_INSTALL; + } + } + return (false); +} + int pkg_solve_parse_sat_output(FILE *f, struct pkg_solve_problem *problem) { - struct pkg_solve_ordered_variable *ordered_variables = NULL, *nord; - struct pkg_solve_variable *var; - int cur_ord = 1, ret = EPKG_OK; + int ret = EPKG_OK; char *line = NULL, *var_str, *begin; size_t linecap = 0; ssize_t linelen; bool got_sat = false, done = false; - /* Order variables */ - var = NULL; - while ((var = PKG_SOLVE_VAR_NEXT(problem->variables, var))) { - nord = calloc(1, sizeof(struct pkg_solve_ordered_variable)); - nord->order = cur_ord ++; - nord->var = var; - HASH_ADD_INT(ordered_variables, order, nord); - } - while ((linelen = getline(&line, &linecap, f)) > 0) { if (strncmp(line, "SAT", 3) == 0) { got_sat = true; @@ -1474,22 +1466,8 @@ /* Skip unexpected lines */ if (var_str == NULL || (!isdigit(*var_str) && *var_str != '-')) continue; - cur_ord = 0; - cur_ord = abs((int)strtol(var_str, NULL, 10)); - if (cur_ord == 0) { + if (pkg_solve_parse_sat_output_store(problem, var_str)) done = true; - break; - } - - HASH_FIND_INT(ordered_variables, &cur_ord, nord); - if (nord != NULL) { - if (*var_str == '-') { - nord->var->flags &= ~PKG_VAR_INSTALL; - } - else { - nord->var->flags |= PKG_VAR_INSTALL; - } - } } while (begin != NULL); } else if (strncmp(line, "v ", 2) == 0) { @@ -1499,23 +1477,8 @@ /* Skip unexpected lines */ if (var_str == NULL || (!isdigit(*var_str) && *var_str != '-')) continue; - cur_ord = 0; - cur_ord = abs((int)strtol(var_str, NULL, 10)); - if (cur_ord == 0) { + if (pkg_solve_parse_sat_output_store(problem, var_str)) done = true; - break; - } - - HASH_FIND_INT(ordered_variables, &cur_ord, nord); - - if (nord != NULL) { - if (*var_str == '-') { - nord->var->flags &= ~PKG_VAR_INSTALL; - } - else { - nord->var->flags |= PKG_VAR_INSTALL; - } - } } while (begin != NULL); } else { @@ -1531,7 +1494,6 @@ ret = EPKG_FATAL; } - HASH_FREE(ordered_variables, free); free(line); return (ret); --------------AA5E85B16E334BA99B677397-- From owner-freebsd-ports@freebsd.org Mon Jun 27 11:52:32 2016 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 D573BB82F0E for ; Mon, 27 Jun 2016 11:52:32 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id B08602ACF for ; Mon, 27 Jun 2016 11:52:32 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id AFD32B82F0A; Mon, 27 Jun 2016 11:52:32 +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 AA970B82F09; Mon, 27 Jun 2016 11:52:32 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6BF262ACD; Mon, 27 Jun 2016 11:52:32 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pf0-x231.google.com with SMTP id i123so61429070pfg.0; Mon, 27 Jun 2016 04:52:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:reply-to:subject:references:to:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=EycICaEdjhTo//l/OAJVyQciL0wOLLoWWSCTk+n3odM=; b=htpkuJqld8BdhBr98P57wsEs7fE5hYSSNZViyeQeu3g9WXuyvjqlvcRzJUTsWs4KiU /GFK2wWjzVcGLKIwUSPBgUS7riJc3us3ovI09TOLll97RcoGAdzyXs3GWsWN5gxEbX9Y 1UFZ4VlZkGDQ8iUOgCzCIDuNJtjSW3tFyD4oN/5jhHEZ00M7kf108PdcOH5NM9uNpGJ2 /lfjV/fELOEk8k20cCpynQ3fjrn9iZz1f5liOaRujstT+vAuCOGgYt2eKuGsG9H00Z2I RwCD46TNQQOZ0PiNaWR3sI5POuEYLuw+TvoLgqDl2RzS3Dw3NO6UBw18w5Dm8SaDUzAS 7GhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:reply-to:subject:references:to:cc:from :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=EycICaEdjhTo//l/OAJVyQciL0wOLLoWWSCTk+n3odM=; b=DEbEPfy2mH9xY+uCr9byBEjEkAS+ysjDhk0QjTloDfWnZw18NH66Q2gmSKm3hxvShh 49kWQbW6bU2MF8tbRc/CfZFa8eWaNFVXkhQw25jnSQI/yq/9B0xpMMfDefQ33aIBabsy St50awly7N2x8wWw/RgH2oJD46GdkYBd4Myf3VfZEg9w9ZGQd1dY4Hy2g6PJ5UhDlc7P nM5XTMdEGjorasulKAooLL6PkSZr/ipYJmeXVN+dHahlPugSgDDQ2R/X8hxHmWL/IzS4 p0lpUv1cdyZLO6gPcPbYICHuN1/NNCbv30FDW5RffKEjtbxXmMN/mzTQ2EnuhC7nla0a 6+hg== X-Gm-Message-State: ALyK8tIg4pWaqp3oY/EBldKdt5DN0UGvQrYPuh+ejxB3jQhbgzsjmO6tOG/pvyk24IKmdQ== X-Received: by 10.98.103.66 with SMTP id b63mr32994714pfc.141.1467028351757; Mon, 27 Jun 2016 04:52:31 -0700 (PDT) Received: from ?IPv6:2001:44b8:31ae:7b01:6866:ec26:8c89:33cf? (2001-44b8-31ae-7b01-6866-ec26-8c89-33cf.static.ipv6.internode.on.net. [2001:44b8:31ae:7b01:6866:ec26:8c89:33cf]) by smtp.gmail.com with ESMTPSA id b186sm6216458pfa.61.2016.06.27.04.52.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Jun 2016 04:52:31 -0700 (PDT) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: pkg SAT_SOLVER bugs References: <20150414200459.GE39658@ivaldir.etoilebsd.net> <20150421103454.GR1394@zxy.spb.ru> <5593D0AE.2010205@selasky.org> <416359ce-1dcd-1160-5c56-f120a0f6358f@selasky.org> To: Hans Petter Selasky , Slawa Olhovchenkov , Baptiste Daroussin Cc: ports@FreeBSD.org, FreeBSD Current From: Kubilay Kocak Message-ID: <44a43ec3-4f64-3de6-4f48-cb1b7231f9a2@FreeBSD.org> Date: Mon, 27 Jun 2016 21:52:23 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Thunderbird/47.0 MIME-Version: 1.0 In-Reply-To: <416359ce-1dcd-1160-5c56-f120a0f6358f@selasky.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 11:52:32 -0000 On 27/06/2016 8:38 PM, Hans Petter Selasky wrote: > Hi, > > I found some bugs in PKG with regard to the SAT_SOLVER environment > variable. Please find patch attached :-) Nice! Can you report upstream @ https://github.com/freebsd/pkg if you haven't already > Issues fixed: > 1) No need to use hash table when generating SAT rules for external > solver. Variables are already in a linear array. Fix encoding and > decoding of SAT data. > 2) Endless variable loop caused pkg to crash. > 3) it->inverse was checked for non-zero, while it should actually be > checked for -1 only. SAT rules produces were all negative. > > How to verify: > > make -C /usr/ports/math/picosat all install clean > > env SAT_SOLVER=picosat pkg upgrade > > --HPS From owner-freebsd-ports@freebsd.org Mon Jun 27 11:55:37 2016 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 42397B840B8 for ; Mon, 27 Jun 2016 11:55:37 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 1D95D2D02 for ; Mon, 27 Jun 2016 11:55:37 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 1916DB840B5; Mon, 27 Jun 2016 11:55:37 +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 1896DB840B3; Mon, 27 Jun 2016 11:55:37 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E35E2D01; Mon, 27 Jun 2016 11:55:36 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id a66so111701390wme.0; Mon, 27 Jun 2016 04:55:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=WiWx8x4/lp4jrP21DKIpwkgbtmUhf8eUpB6WQ1rjGSs=; b=fgeQPOvmTwezIKEWDF7UJN4LsQDBPFP9/vk4LonEAEI15Tvkq6UvGSAzJlNEgf9i90 7yPAGJBurFGjHII7KW1U8OJV/ATedP8rtsfnZUSnKDlPRSg1l/f/780wL+sVxjqBwMfQ f/f2j2RXVqLUcbJ19g1jApngSTewvoYFuRRg9iGieuuqJoqVUV3CqLhUB2MXpt4uXg5r sUq7s5jgEWDy+C5ut4U6Lj/XS7s1k7R3iWAby/0aCBPsuCahKNFla3ywYFdMxrsNgPk+ WtIeT0ffPkffvE2DNRTtM27dpmHaBO+ep+bRxEBRdMIFsWHrErvfdPniHQudjfBcThKg 5MpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=WiWx8x4/lp4jrP21DKIpwkgbtmUhf8eUpB6WQ1rjGSs=; b=bHANb1QFtsNa7Lfg34kr5U9F4zkadM4HpCv8du2ukL9LY6ovsOVsU3vMTYebMYcQNC SfgebKfAb1anDmYn3WxdteqskI2GU6xF5dmUjl+vVqA6XDb1H0rZ8/sISJQyOswhbhRD ltHiWRzWvO7LNTFXJ/x7VaxkHp5uO+pfX8sfHOhgRxsvU6q/0FqiVduYJLlOzj6kQmXe UX/aLzsB5bZ9ec+L91+hPBBohJgzH0uNKfitpCVxceimiHfLAzlfGt/iG28jiiTvLyc3 tQuqfkMRlX0iWO7MUiKOvEdtWt2naWRXbRgO+jbSo7wNLRSbZbOlsjhHpMJ4Is/KMFrg yuqQ== X-Gm-Message-State: ALyK8tLxU9G+N8mvqvmnK0KquBP389XmHiluudeoUSri4XgHTvbqAzOrFQ2dmD8wF1CM/Q== X-Received: by 10.28.145.68 with SMTP id t65mr9705470wmd.31.1467028535239; Mon, 27 Jun 2016 04:55:35 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id h8sm1191459wjg.9.2016.06.27.04.55.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Jun 2016 04:55:34 -0700 (PDT) Sender: Baptiste Daroussin Date: Mon, 27 Jun 2016 13:55:33 +0200 From: Baptiste Daroussin To: Hans Petter Selasky Cc: Slawa Olhovchenkov , ports@FreeBSD.org, FreeBSD Current Subject: Re: pkg SAT_SOLVER bugs Message-ID: <20160627115533.gqvdsmtzwnvrrfuo@ivaldir.etoilebsd.net> References: <20150414200459.GE39658@ivaldir.etoilebsd.net> <20150421103454.GR1394@zxy.spb.ru> <5593D0AE.2010205@selasky.org> <416359ce-1dcd-1160-5c56-f120a0f6358f@selasky.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="r5fafvid2ollsvjd" Content-Disposition: inline In-Reply-To: <416359ce-1dcd-1160-5c56-f120a0f6358f@selasky.org> User-Agent: Mutt/1.6.1-neo (2016-06-11) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 11:55:37 -0000 --r5fafvid2ollsvjd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 27, 2016 at 12:38:02PM +0200, Hans Petter Selasky wrote: > Hi, >=20 > I found some bugs in PKG with regard to the SAT_SOLVER environment variab= le. > Please find patch attached :-) >=20 > Issues fixed: > 1) No need to use hash table when generating SAT rules for external solve= r. > Variables are already in a linear array. Fix encoding and decoding of SAT > data. > 2) Endless variable loop caused pkg to crash. > 3) it->inverse was checked for non-zero, while it should actually be chec= ked > for -1 only. SAT rules produces were all negative. >=20 > How to verify: >=20 > make -C /usr/ports/math/picosat all install clean >=20 > env SAT_SOLVER=3Dpicosat pkg upgrade >=20 > --HPS Thank you I will look into shortly Best regards, Bapt --r5fafvid2ollsvjd Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXcRQyAAoJEGOJi9zxtz5aIZkQAMJQv1kj+AAHPKvaT8L+tO21 Xr3BruHii53Q5BSIbccAb3rx2atPbziXJ/JWS4HfVpVUJ2hz2i1Z6hpD+krVt8Jg IXZnXzgIbaFbM/unDrTob3lEkn5/M6wTaFN7cUIMTR98ECDVhqMonEOZcr9rRFMp yE+W0CAlF5LKoLmMYML2tuDQnfW9Lkr8qkM1Ik0ag5uecX7u7JszO39dAnEM9Zph H9jtIWfHhaEmRqiJJ/gbHfcSo5fskvLF0TfdBlwytVjCM9vhXJO525pofEmcS8Y/ eZYXC6Rb/jFA20c7Xf4YoIo8AZEok419vF6GsfcVPQvSEBSDFrEq0fTdFgjq3DGh haJYtnaNA6EUf6p0Sb5ZEaJZtXUG46P/zY99LUTLXeP1KOkY3CnWxPuycdE4s5ej JShFs8ONwCOrJMabSuzsdisCXL2KWazsZKzJVdEIBQy5sblYHBiUoiphwLeJmkoL 50B7xqv4SFFpdEvGYLGxjZBI0yGQJWWmyH+vL/thjfuIOW+ubNu8pNiNtuiL/O4S tfkpXDTBEiY3OfLfybkm7mUpfpg/eV3nFo56IkGB6RhaM+gGK0d+5Hmu1lzg+Ur8 e4qpJcNJ9a0DOg9C6akstkGhBNISaz1mwMJJTo8OWleZaVQqSC9BvJZc3vpGfchQ PmrCeFdzRbaF2Ief6Mhu =MeX6 -----END PGP SIGNATURE----- --r5fafvid2ollsvjd-- From owner-freebsd-ports@freebsd.org Mon Jun 27 12:19:54 2016 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 96F26B84F6C for ; Mon, 27 Jun 2016 12:19:54 +0000 (UTC) (envelope-from bsdports@cloudzeeland.nl) Received: from ceto.cloudzeeland.nl (cloudzeeland.xs4all.nl [83.161.133.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloudzeeland.nl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E4F62ED5 for ; Mon, 27 Jun 2016 12:19:53 +0000 (UTC) (envelope-from bsdports@cloudzeeland.nl) Received: from ceto.cloudzeeland.nl (ceto.cloudzeeland.nl [10.10.10.30]) by ceto.cloudzeeland.nl (Postfix) with ESMTP id 2F8C747B7883 for ; Mon, 27 Jun 2016 14:19:49 +0200 (CEST) Received: from [10.10.10.34] (ares.cloudzeeland.nl [82.176.127.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by ceto.cloudzeeland.nl (Postfix) with ESMTPSA id E7B9D47B7807 for ; Mon, 27 Jun 2016 14:19:48 +0200 (CEST) To: FreeBSD Ports ML From: JosC Subject: ! mDNSResponder Port update Error Message-ID: <6142424f-19e6-1359-64ae-7b1e4e761401@cloudzeeland.nl> Date: Mon, 27 Jun 2016 14:19:50 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 X-Virus-Scanned: ClamAV using ClamSMTP on ceto.cloudzeeland.nl Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 12:19:54 -0000 [mDNSResponder-576.30.xx] Dear portmaintainer, Just got an error on installing latest version of DNSResponder: ../mDNSShared/dnsextd_lexer.l: In function 'yylex': ../mDNSShared/dnsextd_lexer.l:77: error: 'yylineno' undeclared (first use in this function) ../mDNSShared/dnsextd_lexer.l:77: error: (Each undeclared identifier is reported only once ../mDNSShared/dnsextd_lexer.l:77: error: for each function it appears in.) gmake: *** [Makefile:527: objects/prod/dnsextd_lexer.l.o] Error 1 *** [do-build] Error code 1 Stop in /usr/ports/net/mDNSResponder. --- cut --- Can you advise how to solve this issue? Thanksand keep up the good work! Jos Chrispijn From owner-freebsd-ports@freebsd.org Mon Jun 27 12:24:14 2016 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 0958AB721E9; Mon, 27 Jun 2016 12:24:14 +0000 (UTC) (envelope-from gahr@FreeBSD.org) Received: from mail.ptrcrt.ch (gahr.cloud.tilaa.com [84.22.109.158]) (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 5995C2454; Mon, 27 Jun 2016 12:24:11 +0000 (UTC) (envelope-from gahr@FreeBSD.org) Received: from webmail.ptrcrt.ch (www.gahr.ch [192.168.1.2]) by mail.ptrcrt.ch (OpenSMTPD) with ESMTPSA id f18263d1 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Mon, 27 Jun 2016 12:24:08 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 27 Jun 2016 14:24:08 +0200 From: Pietro Cerutti To: JosC Cc: FreeBSD Ports ML , owner-freebsd-ports@freebsd.org Subject: Re: ! mDNSResponder Port update Error Organization: The FreeBSD Project In-Reply-To: <6142424f-19e6-1359-64ae-7b1e4e761401@cloudzeeland.nl> References: <6142424f-19e6-1359-64ae-7b1e4e761401@cloudzeeland.nl> Message-ID: <9701a274df82d8d1a227d80e98b0d95b@gahr.ch> X-Sender: gahr@FreeBSD.org User-Agent: Roundcube Webmail/1.2.0 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 12:24:14 -0000 On 2016-06-27 14:19, JosC wrote: > [mDNSResponder-576.30.xx] Can you please update your ports tree and try again? mDNSResponder has recently been updated to 625.41.2. > > Dear portmaintainer, > > Just got an error on installing latest version of DNSResponder: > > ../mDNSShared/dnsextd_lexer.l: In function 'yylex': > ../mDNSShared/dnsextd_lexer.l:77: error: 'yylineno' undeclared (first > use in this function) > ../mDNSShared/dnsextd_lexer.l:77: error: (Each undeclared identifier > is reported only once > ../mDNSShared/dnsextd_lexer.l:77: error: for each function it appears > in.) > gmake: *** [Makefile:527: objects/prod/dnsextd_lexer.l.o] Error 1 > *** [do-build] Error code 1 > > Stop in /usr/ports/net/mDNSResponder. > > --- cut --- > > Can you advise how to solve this issue? > > Thanksand keep up the good work! > > Jos Chrispijn > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to > "freebsd-ports-unsubscribe@freebsd.org" -- Pietro Cerutti gahr@FreeBSD.org PGP Public Key: http://gahr.ch/pgp From owner-freebsd-ports@freebsd.org Mon Jun 27 14:25:48 2016 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 5CA82B81CDF for ; Mon, 27 Jun 2016 14:25:48 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [204.109.59.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "apnoea.adamw.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8DC5425FD; Mon, 27 Jun 2016 14:25:47 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id 28bdceb0 TLS version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 27 Jun 2016 08:25:25 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: blanket portmgr approval vs. non-fixing changes (was: svn commit: r417590 - in head/databases/db6: . files and 417595 (revert)) From: Adam Weinberger In-Reply-To: Date: Mon, 27 Jun 2016 08:25:42 -0600 Cc: Matthias Andree , Mathieu Arnold , marino@freebsd.org, Sunpoet Po-Chuan Hsieh , ports-committers , FreeBSD Ports Management Team , freebsd-ports Content-Transfer-Encoding: quoted-printable Message-Id: <2A4F1FFE-8B27-4569-8CCA-D498B5235D18@adamw.org> References: <201606261724.u5QHOLdG081392@repo.freebsd.org> <57701AEB.1050001@tu-dortmund.de> <5770A392.6010605@tu-dortmund.de> <84e4fcf5-7b99-1cc6-e6bd-d3c594a5d102@marino.st> <91BC5F8F9FDB9246529D0693@atuin.in.mat.cc> <5770EAD2.4060302@tu-dortmund.de> To: araujo@freebsd.org X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 14:25:48 -0000 > On 27 Jun, 2016, at 3:27, Marcelo Araujo = wrote: >=20 >=20 >=20 > 2016-06-27 16:58 GMT+08:00 Matthias Andree = : > Am 27.06.2016 um 10:16 schrieb Mathieu Arnold: > > > > > > +--On 27 juin 2016 16:10:36 +0800 Marcelo Araujo = > > wrote: > > | 2016-06-27 16:02 GMT+08:00 Mathieu Arnold : > > |> | Read here for reference: > > |> | > > |> = https://www.freebsd.org/doc/en/books/porters-handbook/makefile-maintainer > > |> | .html > > |> > > |> That pages says, exactly the opposite of what you are trying to = says: > > |> > > | > > | No it doesn't! > > | > > | And this is the normal workflow: > > | 1) Port has a maintainer, and it needs update. > > | 2) Open a PR with the patch. > > | 3) After 2 weeks, and with timeout; anybody can commit it. > > | > > | > > | And about the ownership and belong to the community, I do believe = in that, > > | that is the basic in a legal point of view. > > > > That page says that the maintainer has to be consulted, except for = changes > > covered by the blanket approval, where the change can be committed > > immediately. > > > > In this case, Sunpoet had every right to commit the thing he did = without > > asking or notifying the maintainer. >=20 >=20 > TL;DR given at the very end. >=20 >=20 > 1. Given the portmgr@ rules, that is our current policy, that portmgr@ > as the overseers of the ports system have delegated, by the blanket > approval, part of their ultimate responsibility to the public. >=20 > 2. What I was meaning to state was that (and I'll not pick at the kind > soul who has modernized the port) we should only apply the blanket > approval if ports have fallen into disrepair. >=20 >=20 > 2b. This was not the case with db6, the port wasn't known broken to = me, > so why do we permit and encourage going the fast path for changes that > do not /repair/ a port (for instance, if it's not building, to fix > misspellings), and I'm surprised because some two months ago, it has > already gone through a modernization round after gahr's PR, > , that = also > combined a feature addition and required a bit more work to get right, > see changesets 415741 and 415743. >=20 >=20 > 3. What would have been bad about filing a PR in this case? >=20 > The argument "maintainers aren't doing it" is covered by the = maintainer > timeout. Anything that does not need the fast path should go through > some form of review, most naturally through a PR filed to the port's > maintainer. >=20 >=20 > 4. Do we need to tighten up the set of required tests a committed does > before committing non-maintainer updates? >=20 > I'm scratching my head over this one since the failure in r417590 that > got remedied in r417595 was rather peculiar, and I'm not sure if = anyone, > including myself, would have figured that out. It might have slipped > through the cracks even if I'd reviewed it. >=20 > 4b. It's probably better to extend the committer's guide and/or = porter's > handbook and have a list of test recommendations where we list things > that trigger a certain test requirement. I. e. things to test IN > ADDITION to the usual "poudriere testport" or "make DEVELOPER=3Dyes = clean > all check-plist package" and portlint coverage. Meaning that if = someone > tweaks any of the WRK* and *DIR/*SRC-related variables, "also test = 'make > clean extract do-patch makepatch' on a copy of the port directory" or > thereabouts. >=20 > mat@ thanks for all the explanation and time. >=20 > Unfortunately, I still make things a bit manual at my side, but = usually my testbed is: > 1) Portlint. > 2) Make and likes on i386 and amd64(clean vm). >=20 > I think, include more information about test recommendations is always = good. > =20 >=20 >=20 > There seem to be at least two distinct camps, in one camp, maintainers > go along Marcelo's and my trains of thought, in the other, maintainers > cherish fast and low-ceremony progress, marino has argued along these > lines, and some other portmgr@ members have pushed for progress in the > past. >=20 > I don't mean to bikeshed or split up our project here, just refine our > existing policies. >=20 >=20 > TL;DR: I propose: >=20 > - the blanket approval should be tightened up a bit and encourage that > non-trivial and non-urgent changes go through the PR and invoke > mantainer timeout after the shortest possible period. >=20 > Personally, I like the first option! And in addition, we have = phabricator as an option too, at least for src, the reviews are made = very quickly. > So, could be defined a short timeout, at least for those that are = active and would like to help make a review, seems something reasonable. >=20 > Also I do understand about all the modernization and definitely we = need it, maybe 2 days timeout is enough for an active maintainer to = reply that he is busy or he is working on that.=20 > =20 > =20 >=20 > - we discuss about an assisting set of "change these variables > foo.*regexp, and you also need to test 'make foo' and 'make bar'" = rules > in the form of a concise list. Maintainership too often means that change requests get ignored for two = weeks before they're committed. Aside from large, complex, interconnected systems, I think that we = should do away with ports maintainership entirely. Maintainership serves = absolutely no purpose that peer-review wouldn't do better. Any committer should be able to commit to any port. That used to be what = ports@FreeBSD.org meant, that it was being maintained by everybody. But = somehow, in the last few years that turned into a message that it's = being maintained by nobody, so now ports *have* to be maintained by = somebody, even if that person never touches it again. # Adam --=20 Adam Weinberger adamw@adamw.org http://www.adamw.org From owner-freebsd-ports@freebsd.org Mon Jun 27 15:02:46 2016 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 5E329B846DB for ; Mon, 27 Jun 2016 15:02:46 +0000 (UTC) (envelope-from pi@FreeBSD.org) Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4]) (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 18D5D2CF7; Mon, 27 Jun 2016 15:02:46 +0000 (UTC) (envelope-from pi@FreeBSD.org) Received: from pi by fc.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bHY3a-000Atx-GY; Mon, 27 Jun 2016 17:02:38 +0200 Date: Mon, 27 Jun 2016 17:02:38 +0200 From: Kurt Jaeger To: Adam Weinberger Cc: araujo@freebsd.org, Matthias Andree , Mathieu Arnold , marino@freebsd.org, Sunpoet Po-Chuan Hsieh , ports-committers , FreeBSD Ports Management Team , freebsd-ports Subject: Re: blanket portmgr approval vs. non-fixing changes (was: svn commit: r417590 - in head/databases/db6: . files and 417595 (revert)) Message-ID: <20160627150238.GJ2369@fc.opsec.eu> References: <5770A392.6010605@tu-dortmund.de> <84e4fcf5-7b99-1cc6-e6bd-d3c594a5d102@marino.st> <91BC5F8F9FDB9246529D0693@atuin.in.mat.cc> <5770EAD2.4060302@tu-dortmund.de> <2A4F1FFE-8B27-4569-8CCA-D498B5235D18@adamw.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2A4F1FFE-8B27-4569-8CCA-D498B5235D18@adamw.org> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 15:02:46 -0000 Hi! [adamw] > Maintainership too often means that change requests get ignored > for two weeks before they're committed. That is the case sometimes, yes. But oftern maintainership provides identification with the project and proud of achievement etc, which causes people to invest time and skills in the project. Maintainership also provides a point of contact that one can ask for run-tests or for additional experience some potential port user can contact. It provides 'community'. > Aside from large, complex, interconnected systems, I think that > we should do away with ports maintainership entirely. Maintainership > serves absolutely no purpose that peer-review wouldn't do better. If we add to the role of the maintainer the wish from the ports community to the maintainer that she/he provides some run-test environment and practical (daily?) experience with a port, that would definitly be positive. Not all ports would need maintainers, if the role changes like that. > Any committer should be able to commit to any port. That used to > be what ports@FreeBSD.org meant, that it was being maintained by > everybody. For complex ports, we do not always have committers that have run-test resources. For those it's good to have some maintainer. > But somehow, in the last few years that turned into a > message that it's being maintained by nobody, so now ports *have* > to be maintained by somebody, even if that person never touches it > again. The queue of uncommitted ports PRs shows that it's not always the maintainers that are the bottle-neck, sometimes it's the committers. -- pi@FreeBSD.org +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Mon Jun 27 15:22:54 2016 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 206EDB84A57 for ; Mon, 27 Jun 2016 15:22:54 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DC07526FB; Mon, 27 Jun 2016 15:22:53 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pa0-x22b.google.com with SMTP id b13so60091168pat.0; Mon, 27 Jun 2016 08:22:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:reply-to:subject:references:to:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=l8/6GcLIo5mT6suwAPviunnmGY/X0u0CbR1ZjvDJGYs=; b=UUF6HrJ1/GOi6fiylyG/24HzlLAsaBcvxFF1JwCsRor7mEMaMNoreBww48d6raTh+i AVqA6Uig+FO669M0t4/bSC0T2SOaLhAcMhstlOcI8+eO75H7+ZUJMTLxU4G4taWTzDI5 skJKNWCebXegizoGhRHDNb49TZQnCp0KQJSWSZSdph9FJ+GgFctwO8kKwJODCVw3T+DC WTbkS4OYOeUijaI4AxsKjVKFwVApyvF2GwgIz3eb9ldX1U8qgt3M+qKjfOh7uNuZKw+6 cLXY3qHD3cUDyRa4SxlFq0tSGPWgL2dNuHUK3BQTCIZtbsDK8Q5FEjv9lnz5jBbnoI5d S0GA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:reply-to:subject:references:to:cc:from :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=l8/6GcLIo5mT6suwAPviunnmGY/X0u0CbR1ZjvDJGYs=; b=cSULJSmqH9T5leOabQP2yCskIfowHp+yCVuHt+SKI8b9sMTlKrEhRJc3k+5FinkvBN SaX15nT/7hOfqZtuP4RBFwcX8NmvDGtBbfUhd3BMCuJR19PAhyKQ8/vPfzB+SCQXoDPZ Rsd0uJmJdoyZqvIZQI3M6jKcQan7vhEMoVA0hf9rN1Svwb6CPaNOGBtn5imnrMQ8DlK3 qUCQelcKsYMoA25++bFfyghVGC8OSy2+xMbfnBTUxNHln5ffiWeYU+ogf/VNpmFMpVQH 1hpk6z5zfDUBO228bK0GbQK5dZ7mohTrFQkPKU6vZmC2Sw+4ZyuC488u6u88ipeVOW9d MFFw== X-Gm-Message-State: ALyK8tLuO8GBb1ILkUzObRiywjEoA0z12hABrPAAFM7kyDhSznSPFfHAbThtvwWN4ekW3w== X-Received: by 10.66.89.34 with SMTP id bl2mr35206671pab.80.1467040973105; Mon, 27 Jun 2016 08:22:53 -0700 (PDT) Received: from ?IPv6:2001:44b8:31ae:7b01:6866:ec26:8c89:33cf? (2001-44b8-31ae-7b01-6866-ec26-8c89-33cf.static.ipv6.internode.on.net. [2001:44b8:31ae:7b01:6866:ec26:8c89:33cf]) by smtp.gmail.com with ESMTPSA id m8sm474603pfi.27.2016.06.27.08.22.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Jun 2016 08:22:52 -0700 (PDT) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: blanket portmgr approval vs. non-fixing changes References: <201606261724.u5QHOLdG081392@repo.freebsd.org> <57701AEB.1050001@tu-dortmund.de> <5770A392.6010605@tu-dortmund.de> <84e4fcf5-7b99-1cc6-e6bd-d3c594a5d102@marino.st> <91BC5F8F9FDB9246529D0693@atuin.in.mat.cc> <5770EAD2.4060302@tu-dortmund.de> <2A4F1FFE-8B27-4569-8CCA-D498B5235D18@adamw.org> To: Adam Weinberger , araujo@freebsd.org Cc: Matthias Andree , Mathieu Arnold , marino@freebsd.org, Sunpoet Po-Chuan Hsieh , ports-committers , FreeBSD Ports Management Team , freebsd-ports From: Kubilay Kocak Message-ID: <9364c255-9733-b1a0-68a1-a058ca78d95e@FreeBSD.org> Date: Tue, 28 Jun 2016 01:22:45 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Thunderbird/47.0 MIME-Version: 1.0 In-Reply-To: <2A4F1FFE-8B27-4569-8CCA-D498B5235D18@adamw.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 15:22:54 -0000 On 28/06/2016 12:25 AM, Adam Weinberger wrote: >> On 27 Jun, 2016, at 3:27, Marcelo Araujo >> wrote: >> >> >> >> 2016-06-27 16:58 GMT+08:00 Matthias Andree >> : Am 27.06.2016 um 10:16 schrieb >> Mathieu Arnold: >>> >>> >>> +--On 27 juin 2016 16:10:36 +0800 Marcelo Araujo >>> wrote: | 2016-06-27 16:02 GMT+08:00 >>> Mathieu Arnold : |> | Read here for reference: >>> |> | |> >>> https://www.freebsd.org/doc/en/books/porters-handbook/makefile-maintainer >>> >>> |> | .html >>> |> |> That pages says, exactly the opposite of what you are >>> trying to says: |> | | No it doesn't! | | And this is the normal >>> workflow: | 1) Port has a maintainer, and it needs update. | 2) >>> Open a PR with the patch. | 3) After 2 weeks, and with timeout; >>> anybody can commit it. | | | And about the ownership and belong >>> to the community, I do believe in that, | that is the basic in a >>> legal point of view. >>> >>> That page says that the maintainer has to be consulted, except >>> for changes covered by the blanket approval, where the change can >>> be committed immediately. >>> >>> In this case, Sunpoet had every right to commit the thing he did >>> without asking or notifying the maintainer. >> >> >> TL;DR given at the very end. >> >> >> 1. Given the portmgr@ rules, that is our current policy, that >> portmgr@ as the overseers of the ports system have delegated, by >> the blanket approval, part of their ultimate responsibility to the >> public. >> >> 2. What I was meaning to state was that (and I'll not pick at the >> kind soul who has modernized the port) we should only apply the >> blanket approval if ports have fallen into disrepair. >> >> >> 2b. This was not the case with db6, the port wasn't known broken to >> me, so why do we permit and encourage going the fast path for >> changes that do not /repair/ a port (for instance, if it's not >> building, to fix misspellings), and I'm surprised because some two >> months ago, it has already gone through a modernization round after >> gahr's PR, >> , that >> also combined a feature addition and required a bit more work to >> get right, see changesets 415741 and 415743. >> >> >> 3. What would have been bad about filing a PR in this case? >> >> The argument "maintainers aren't doing it" is covered by the >> maintainer timeout. Anything that does not need the fast path >> should go through some form of review, most naturally through a PR >> filed to the port's maintainer. >> >> >> 4. Do we need to tighten up the set of required tests a committed >> does before committing non-maintainer updates? >> >> I'm scratching my head over this one since the failure in r417590 >> that got remedied in r417595 was rather peculiar, and I'm not sure >> if anyone, including myself, would have figured that out. It might >> have slipped through the cracks even if I'd reviewed it. >> >> 4b. It's probably better to extend the committer's guide and/or >> porter's handbook and have a list of test recommendations where we >> list things that trigger a certain test requirement. I. e. things >> to test IN ADDITION to the usual "poudriere testport" or "make >> DEVELOPER=yes clean all check-plist package" and portlint coverage. >> Meaning that if someone tweaks any of the WRK* and >> *DIR/*SRC-related variables, "also test 'make clean extract >> do-patch makepatch' on a copy of the port directory" or >> thereabouts. >> >> mat@ thanks for all the explanation and time. >> >> Unfortunately, I still make things a bit manual at my side, but >> usually my testbed is: 1) Portlint. 2) Make and likes on i386 and >> amd64(clean vm). >> >> I think, include more information about test recommendations is >> always good. >> >> >> >> There seem to be at least two distinct camps, in one camp, >> maintainers go along Marcelo's and my trains of thought, in the >> other, maintainers cherish fast and low-ceremony progress, marino >> has argued along these lines, and some other portmgr@ members have >> pushed for progress in the past. >> >> I don't mean to bikeshed or split up our project here, just refine >> our existing policies. >> >> >> TL;DR: I propose: >> >> - the blanket approval should be tightened up a bit and encourage >> that non-trivial and non-urgent changes go through the PR and >> invoke mantainer timeout after the shortest possible period. >> >> Personally, I like the first option! And in addition, we have >> phabricator as an option too, at least for src, the reviews are >> made very quickly. So, could be defined a short timeout, at least >> for those that are active and would like to help make a review, >> seems something reasonable. >> >> Also I do understand about all the modernization and definitely we >> need it, maybe 2 days timeout is enough for an active maintainer to >> reply that he is busy or he is working on that. >> >> >> >> - we discuss about an assisting set of "change these variables >> foo.*regexp, and you also need to test 'make foo' and 'make bar'" >> rules in the form of a concise list. > > Maintainership too often means that change requests get ignored for > two weeks before they're committed. > > Aside from large, complex, interconnected systems, I think that we > should do away with ports maintainership entirely. Maintainership > serves absolutely no purpose that peer-review wouldn't do better. There's two senses of 'ownership' that are often conflated, or at least almost never made explicit. The kind we want, more of, and would hate to lose: - responsibility, accountability, pride in 'looking after' something The other we don't: - territorial, xenophobic (mine/yours, ours/theirs), hoarding, exclusive use Which one we have, get, or foster, has everything to do with how we teach people we do things around here, how clearly we articulate our goals and intentions, and nothing to do with MAINTAINER intrinsically. All: How did you feel the first time you saw your email on a maintainer line? That is priceless and shouldn't be confused with the 'bad' kind of ownership. > Any committer should be able to commit to any port. That used to be > what ports@FreeBSD.org meant, that it was being maintained by > everybody. But somehow, in the last few years that turned into a > message that it's being maintained by nobody, so now ports *have* to > be maintained by somebody, even if that person never touches it > again. > > # Adam > Having a discussion after an example of fallout (whether correct or not), is unfortunately, precisely the worst time (reactively) to be making well-informed, collaborative decisions. What we don't disagree on: - High quality changes, minimal user impact - Minimal latency and barriers to progress (not at the cost of quality) - Ways for contributors to specialise or take on greater responsibility if they want to and can. The above are *not* mutually exclusive goals, they do however require people to think beyond single priority solutions. Finally, if the question is: "How can we have all of them?", what are the possibilities? ./koobs From owner-freebsd-ports@freebsd.org Mon Jun 27 15:49:21 2016 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 799CFB84EA2 for ; Mon, 27 Jun 2016 15:49:21 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [204.109.59.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "apnoea.adamw.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9A08F220E; Mon, 27 Jun 2016 15:49:20 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id 125a260d TLS version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 27 Jun 2016 09:48:57 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: blanket portmgr approval vs. non-fixing changes From: Adam Weinberger In-Reply-To: <9364c255-9733-b1a0-68a1-a058ca78d95e@FreeBSD.org> Date: Mon, 27 Jun 2016 09:49:15 -0600 Cc: araujo@freebsd.org, Matthias Andree , Mathieu Arnold , marino@freebsd.org, Sunpoet Po-Chuan Hsieh , ports-committers , FreeBSD Ports Management Team , freebsd-ports Content-Transfer-Encoding: quoted-printable Message-Id: <031F150B-A701-405E-AE9B-62EC548CF8A2@adamw.org> References: <201606261724.u5QHOLdG081392@repo.freebsd.org> <57701AEB.1050001@tu-dortmund.de> <5770A392.6010605@tu-dortmund.de> <84e4fcf5-7b99-1cc6-e6bd-d3c594a5d102@marino.st> <91BC5F8F9FDB9246529D0693@atuin.in.mat.cc> <5770EAD2.4060302@tu-dortmund.de> <2A4F1FFE-8B27-4569-8CCA-D498B5235D18@adamw.org> <9364c255-9733-b1a0-68a1-a058ca78d95e@FreeBSD.org> To: koobs@FreeBSD.org X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 15:49:21 -0000 > On 27 Jun, 2016, at 9:22, Kubilay Kocak wrote: >=20 > On 28/06/2016 12:25 AM, Adam Weinberger wrote: >>> On 27 Jun, 2016, at 3:27, Marcelo Araujo >>> wrote: >>>=20 >>>=20 >>>=20 >>> 2016-06-27 16:58 GMT+08:00 Matthias Andree >>> : Am 27.06.2016 um 10:16 schrieb >>> Mathieu Arnold: >>>>=20 >>>>=20 >>>> +--On 27 juin 2016 16:10:36 +0800 Marcelo Araujo >>>> wrote: | 2016-06-27 16:02 GMT+08:00 >>>> Mathieu Arnold : |> | Read here for reference:=20 >>>> |> | |> >>>> = https://www.freebsd.org/doc/en/books/porters-handbook/makefile-maintainer >>>>=20 >>>>=20 > |> | .html >>>> |> |> That pages says, exactly the opposite of what you are >>>> trying to says: |> | | No it doesn't! | | And this is the normal >>>> workflow: | 1) Port has a maintainer, and it needs update. | 2) >>>> Open a PR with the patch. | 3) After 2 weeks, and with timeout; >>>> anybody can commit it. | | | And about the ownership and belong >>>> to the community, I do believe in that, | that is the basic in a >>>> legal point of view. >>>>=20 >>>> That page says that the maintainer has to be consulted, except >>>> for changes covered by the blanket approval, where the change can >>>> be committed immediately. >>>>=20 >>>> In this case, Sunpoet had every right to commit the thing he did >>>> without asking or notifying the maintainer. >>>=20 >>>=20 >>> TL;DR given at the very end. >>>=20 >>>=20 >>> 1. Given the portmgr@ rules, that is our current policy, that >>> portmgr@ as the overseers of the ports system have delegated, by >>> the blanket approval, part of their ultimate responsibility to the >>> public. >>>=20 >>> 2. What I was meaning to state was that (and I'll not pick at the >>> kind soul who has modernized the port) we should only apply the >>> blanket approval if ports have fallen into disrepair. >>>=20 >>>=20 >>> 2b. This was not the case with db6, the port wasn't known broken to >>> me, so why do we permit and encourage going the fast path for >>> changes that do not /repair/ a port (for instance, if it's not >>> building, to fix misspellings), and I'm surprised because some two >>> months ago, it has already gone through a modernization round after >>> gahr's PR,=20 >>> , that >>> also combined a feature addition and required a bit more work to >>> get right, see changesets 415741 and 415743. >>>=20 >>>=20 >>> 3. What would have been bad about filing a PR in this case? >>>=20 >>> The argument "maintainers aren't doing it" is covered by the >>> maintainer timeout. Anything that does not need the fast path >>> should go through some form of review, most naturally through a PR >>> filed to the port's maintainer. >>>=20 >>>=20 >>> 4. Do we need to tighten up the set of required tests a committed >>> does before committing non-maintainer updates? >>>=20 >>> I'm scratching my head over this one since the failure in r417590 >>> that got remedied in r417595 was rather peculiar, and I'm not sure >>> if anyone, including myself, would have figured that out. It might >>> have slipped through the cracks even if I'd reviewed it. >>>=20 >>> 4b. It's probably better to extend the committer's guide and/or >>> porter's handbook and have a list of test recommendations where we >>> list things that trigger a certain test requirement. I. e. things >>> to test IN ADDITION to the usual "poudriere testport" or "make >>> DEVELOPER=3Dyes clean all check-plist package" and portlint = coverage. >>> Meaning that if someone tweaks any of the WRK* and >>> *DIR/*SRC-related variables, "also test 'make clean extract >>> do-patch makepatch' on a copy of the port directory" or=20 >>> thereabouts. >>>=20 >>> mat@ thanks for all the explanation and time. >>>=20 >>> Unfortunately, I still make things a bit manual at my side, but >>> usually my testbed is: 1) Portlint. 2) Make and likes on i386 and >>> amd64(clean vm). >>>=20 >>> I think, include more information about test recommendations is >>> always good. >>>=20 >>>=20 >>>=20 >>> There seem to be at least two distinct camps, in one camp, >>> maintainers go along Marcelo's and my trains of thought, in the >>> other, maintainers cherish fast and low-ceremony progress, marino >>> has argued along these lines, and some other portmgr@ members have >>> pushed for progress in the past. >>>=20 >>> I don't mean to bikeshed or split up our project here, just refine >>> our existing policies. >>>=20 >>>=20 >>> TL;DR: I propose: >>>=20 >>> - the blanket approval should be tightened up a bit and encourage >>> that non-trivial and non-urgent changes go through the PR and >>> invoke mantainer timeout after the shortest possible period. >>>=20 >>> Personally, I like the first option! And in addition, we have >>> phabricator as an option too, at least for src, the reviews are >>> made very quickly. So, could be defined a short timeout, at least >>> for those that are active and would like to help make a review, >>> seems something reasonable. >>>=20 >>> Also I do understand about all the modernization and definitely we >>> need it, maybe 2 days timeout is enough for an active maintainer to >>> reply that he is busy or he is working on that. >>>=20 >>>=20 >>>=20 >>> - we discuss about an assisting set of "change these variables=20 >>> foo.*regexp, and you also need to test 'make foo' and 'make bar'" >>> rules in the form of a concise list. >>=20 >> Maintainership too often means that change requests get ignored for >> two weeks before they're committed. >>=20 >> Aside from large, complex, interconnected systems, I think that we >> should do away with ports maintainership entirely. Maintainership >> serves absolutely no purpose that peer-review wouldn't do better. >=20 > There's two senses of 'ownership' that are often conflated, or at = least > almost never made explicit. >=20 > The kind we want, more of, and would hate to lose: >=20 > - responsibility, accountability, pride in 'looking after' something >=20 > The other we don't: >=20 > - territorial, xenophobic (mine/yours, ours/theirs), hoarding, = exclusive use >=20 > Which one we have, get, or foster, has everything to do with how we > teach people we do things around here, how clearly we articulate our > goals and intentions, and nothing to do with MAINTAINER intrinsically. >=20 > All: How did you feel the first time you saw your email on a = maintainer > line? That is priceless and shouldn't be confused with the 'bad' kind = of > ownership. You're a wise man, koobs. What I said was a classic nirvana fallacy. = That feeling of seeing my name on a maintainer line is precisely why I = contributed to FreeBSD a second time. And you're completely right that = there is a difference between owning a toy and being the only one = allowed to play with it. I am a huge fan of the blanket. I'd sent an email to portmgr requesting = it shortly before it got announced. So whether or not one had anything = to do with the other, I like to pretend that I played a part in its = creation. I guess I just don't understand why it really bothers some = others. # Adam --=20 Adam Weinberger adamw@adamw.org http://www.adamw.org From owner-freebsd-ports@freebsd.org Mon Jun 27 16:07:09 2016 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 B039FB843F1 for ; Mon, 27 Jun 2016 16:07:09 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 435192D12; Mon, 27 Jun 2016 16:07:08 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with SMTP id HZ3vbS1ROkqLbHZ3xbEPgZ; Mon, 27 Jun 2016 10:07:07 -0600 X-Authority-Analysis: v=2.2 cv=UoshDK4B c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=pD_ry4oyNxEA:10 a=pGLkceISAAAA:8 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=MmrIztTIlQST59YeKiwA:9 a=6kGIvZw6iX1k4Y-7sg4_:22 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id B13B51378A; Mon, 27 Jun 2016 09:07:03 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id u5RG73t8005803; Mon, 27 Jun 2016 09:07:03 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201606271607.u5RG73t8005803@slippy.cwsent.com> X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.6 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Matthias Andree cc: Mathieu Arnold , araujo@freebsd.org, marino@freebsd.org, Sunpoet Po-Chuan Hsieh , ports-committers , FreeBSD Ports Management Team , freebsd-ports@FreeBSD.org Subject: Re: blanket portmgr approval vs. non-fixing changes (was: svn commit: r417590 - in head/databases/db6: . files and 417595 (revert)) In-Reply-To: Message from Matthias Andree of "Mon, 27 Jun 2016 11:16:04 +0200." <5770EED4.1070202@tu-dortmund.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jun 2016 09:07:03 -0700 X-CMAE-Envelope: MS4wfJ5ClsZBoGKRaPtZNTHl4p70PW+gIfTu6czhZFmCHgRFAbPtJH/cT90GQhFF637GuA3PtqCQVi4Q8XgmNedUOa5OfWWNTD0/EUKJVNHnOjAcUO7IUC3j 9RG3qSP/ElqOHTvwDLbbCkWMWGxjPwMZwEvHF0+zzyZMvvo49Y9hT0shdt5gOJWZ/hjiqt4Lk/QWOJDCs68gc2Z0ZWMc9aqcHZspSCXr7lHs64wxD7sjGR24 jHYOnEhEGs3+/+V1zHuHskZRxjrHZegaVrLcM6bCARd01RlRjLcHAI3tJLZH4B7/4779SRKbrbwxGTyFvx9rzgdcP4nmEDiK5bXV78tOMbIKqfTxSL0PtX65 Xra//FADYgAIffbOX5yZjxhOgeUyuldSMepxLwZFwIgSw6Jxf2l6uF7WAbtMngUYhIHT1TZE X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 16:07:09 -0000 In message <5770EED4.1070202@tu-dortmund.de>, Matthias Andree writes: > [Sorry for this re-send, I feel we need to re-send thisto ports@ so the > discussion goes to a public and archived list.] > > Am 27.06.2016 um 10:16 schrieb Mathieu Arnold: > > > > > > +--On 27 juin 2016 16:10:36 +0800 Marcelo Araujo > > wrote: > > | 2016-06-27 16:02 GMT+08:00 Mathieu Arnold : > > |> | Read here for reference: > > |> | > > |> https://www.freebsd.org/doc/en/books/porters-handbook/makefile-maintaine > r > > |> | .html > > |> > > |> That pages says, exactly the opposite of what you are trying to says: > > |> > > | > > | No it doesn't! > > | > > | And this is the normal workflow: > > | 1) Port has a maintainer, and it needs update. > > | 2) Open a PR with the patch. > > | 3) After 2 weeks, and with timeout; anybody can commit it. > > | > > | > > | And about the ownership and belong to the community, I do believe in that > , > > | that is the basic in a legal point of view. > > > > That page says that the maintainer has to be consulted, except for changes > > covered by the blanket approval, where the change can be committed > > immediately. > > > > In this case, Sunpoet had every right to commit the thing he did without > > asking or notifying the maintainer. > > > TL;DR given at the very end. > > > 1. Given the portmgr@ rules, that is our current policy, that portmgr@ > as the overseers of the ports system have delegated, by the blanket > approval, part of their ultimate responsibility to the public. > > 2. What I was meaning to state was that (and I'll not pick at the kind > soul who has modernized the port) we should only apply the blanket > approval if ports have fallen into disrepair. > > > 2b. This was not the case with db6, the port wasn't known broken to me, > so why do we permit and encourage going the fast path for changes that > do not /repair/ a port (for instance, if it's not building, to fix > misspellings), and I'm surprised because some two months ago, it has > already gone through a modernization round after gahr's PR, > , that also > combined a feature addition and required a bit more work to get right, > see changesets 415741 and 415743. > > > 3. What would have been bad about filing a PR in this case? > > The argument "maintainers aren't doing it" is covered by the maintainer > timeout. Anything that does not need the fast path should go through > some form of review, most naturally through a PR filed to the port's > maintainer. > > > 4. Do we need to tighten up the set of required tests a committed does > before committing non-maintainer updates? > > I'm scratching my head over this one since the failure in r417590 that > got remedied in r417595 was rather peculiar, and I'm not sure if anyone, > including myself, would have figured that out. It might have slipped > through the cracks even if I'd reviewed it. > > 4b. It's probably better to extend the committer's guide and/or porter's > handbook and have a list of test recommendations where we list things > that trigger a certain test requirement. I. e. things to test IN > ADDITION to the usual "poudriere testport" or "make DEVELOPER=yes clean > all check-plist package" and portlint coverage. Meaning that if someone > tweaks any of the WRK* and *DIR/*SRC-related variables, "also test 'make > clean extract do-patch makepatch' on a copy of the port directory" or > thereabouts. > > > There seem to be at least two distinct camps, in one camp, maintainers > go along Marcelo's and my trains of thought, in the other, maintainers > cherish fast and low-ceremony progress, marino has argued along these > lines, and some other portmgr@ members have pushed for progress in the > past. > > I don't mean to bikeshed or split up our project here, just refine our > existing policies. > > > TL;DR: I propose: > > - the blanket approval should be tightened up a bit and encourage that > non-trivial and non-urgent changes go through the PR and invoke > mantainer timeout after the shortest possible period. > > - we discuss about an assisting set of "change these variables > foo.*regexp, and you also need to test 'make foo' and 'make bar'" rules > in the form of a concise list. Mathias, I'm surprised at your position. I recall a commit you made to one of my ports a few years ago, to which I objected. Your position now is a complete reversal of your arguments then. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-ports@freebsd.org Mon Jun 27 16:10:52 2016 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 21711B844AF; Mon, 27 Jun 2016 16:10:52 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CF7B12F4D; Mon, 27 Jun 2016 16:10:51 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-vk0-x234.google.com with SMTP id j2so238282150vkg.2; Mon, 27 Jun 2016 09:10:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=M8KfP9+bDZR69cVnaGXV+LQH/VdxwEJYmsxHURKorf8=; b=h47KVp/aWOoDm0/edRoEZNTwhawFnCyR70XTNSRcLj5JskEweIkw4FHovEjEDBo++w k+78GdE6Dbi/NLNbz+/J2jxKnf4e0umbj6OX428UgU8kU1vhQgBC1nEC51AZinTpHT9a /GgfnZSN4D4UBtfdx1YFnCk/G1aysgHB2bqm+i++X30Ktrm2EabbQhTNI4wfiTKFTabT GdjPr/CZbEowEYT9vK+L8Ygo4BkaDKn7aTMeo839WM0qkXKa956TMvwyP/XUkJiDKsVE ZXQ8xIGtdlJ3OVoIVLMESu1VXwmVmOnhXo5QGbRnstk80CUb7fBp4NseJCu1OmXez9Kw QOtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=M8KfP9+bDZR69cVnaGXV+LQH/VdxwEJYmsxHURKorf8=; b=PJgjTE1xxJHbJs49kZSao9OhOKVxTqdFc3JIhHFCnHp0LLAr4N5Q9OcHMyW4jj5hvd nXRz9O0bQRgc0v7c8C+kenhMXF1W6pbdZ0FVNfEC0gOAh/zCviNs0lQxaOUkbzqQ1shb 2I6eihmlw7r3oTddLDVctrFcHjTvtDPEcsO8vU+cfpEf8WI9CkuBMVO+7SPUC9/lOgE7 T6iPXfdJWOedptROgcQq4kCD6R4tBZpFMLSNZ7QsAy5+6SFRNXLPN9IRYm/Qkxzs6oLQ g/gw7MCGsv7+6MM6nPmACxe6Dcj92EbKFMlMshqtQFlXAkxQNYvLeeLYLPMtZ1LYk1JW ZG4A== X-Gm-Message-State: ALyK8tIVvLmIZrsgKq7AX+9aC8AfvRZOuZO0l9SLv7cEY8xS0dtDdabs1fp+KmqU+rnw62IYOrDxx8m+Z8SH3A== X-Received: by 10.159.40.229 with SMTP id d92mr9021433uad.100.1467043850880; Mon, 27 Jun 2016 09:10:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.54.196 with HTTP; Mon, 27 Jun 2016 09:10:50 -0700 (PDT) In-Reply-To: <20160627121104.GA59506@FreeBSD.org> References: <576EC008.9060109@innolan.dk> <20160625185613.4698194.7455.7812@gmail.com> <576EFC4A.9020000@innolan.dk> <20160627121104.GA59506@FreeBSD.org> From: Russell Haley Date: Mon, 27 Jun 2016 09:10:50 -0700 Message-ID: Subject: Re: Latest MonoDevelop Progress To: Freebsd-mono , freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 16:10:52 -0000 On Mon, Jun 27, 2016 at 5:11 AM, Romain Tarti=C3=A8re = wrote: > On Sun, Jun 26, 2016 at 11:25:06PM -0700, Russell Haley wrote: >> On Sat, Jun 25, 2016 at 2:48 PM, Carsten Larsen wrote: >> > On 25-06-2016, 20:56 Russell Haley wrote: >> > > I'm unsure to where they get copied. >> > >> > [...] >> > >> > The Debian package consist of 955 files (and folders): >> > http://pastebin.com/ATS2M4F7 >> >> Thanks Carsten, that is the confirmation I needed. Great reference here: >> >> https://github.com/gentoo/dotnet/issues/111 > > In case it helps, there is an old patch for adding > devel/referenceassemblies-pcl to the ports tree (but installing binaries > through the ports system is ugly, so I did not pushed it in the official > ports): > https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D168589&action=3Dedi= t Awesome, thanks. Since most (or all) of the mono stuff is in GitHub, I am liking the idea of creating a project in Github to control all the patches, instead of doing it through svn patches. It will make everything WAY easier to push back upstream. Not that it matters, eh, Ivan? :0) Russ From owner-freebsd-ports@freebsd.org Mon Jun 27 17:04:03 2016 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 74D39B8149E for ; Mon, 27 Jun 2016 17:04:03 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 5839D221D for ; Mon, 27 Jun 2016 17:04:03 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 53E53B8149C; Mon, 27 Jun 2016 17:04:03 +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 53884B8149B for ; Mon, 27 Jun 2016 17:04:03 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 3857C221C; Mon, 27 Jun 2016 17:04:03 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [IPv6:::1]) by freefall.freebsd.org (Postfix) with ESMTP id 2B6B017EC; Mon, 27 Jun 2016 17:04:03 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id C9ED91C23F; Mon, 27 Jun 2016 17:04:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id 8S8s86VNyCj2; Mon, 27 Jun 2016 17:03:59 +0000 (UTC) Subject: Re: USE_PACKAGE_DEPENDS_ONLY set - not building missing dependency from source DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com 54A151C239 To: Jan Beich , FreeBSD Ports mailing list References: <201606250232.u5P2Wndq091282@beefy5.nyi.freebsd.org> <7fdc-gny4-wny@vfemail.net> From: Bryan Drewery Organization: FreeBSD Message-ID: <65756e68-af20-5594-e719-4b5a4795b36f@FreeBSD.org> Date: Mon, 27 Jun 2016 10:03:55 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <7fdc-gny4-wny@vfemail.net> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="DM35dHgFJxcV7SfHU03GPmN7eldvSnd10" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 17:04:03 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --DM35dHgFJxcV7SfHU03GPmN7eldvSnd10 Content-Type: multipart/mixed; boundary="gudvjOAE9LLvWStmk8lgkvoJ2LChw4fD2" From: Bryan Drewery To: Jan Beich , FreeBSD Ports mailing list Message-ID: <65756e68-af20-5594-e719-4b5a4795b36f@FreeBSD.org> Subject: Re: USE_PACKAGE_DEPENDS_ONLY set - not building missing dependency from source References: <201606250232.u5P2Wndq091282@beefy5.nyi.freebsd.org> <7fdc-gny4-wny@vfemail.net> In-Reply-To: <7fdc-gny4-wny@vfemail.net> --gudvjOAE9LLvWStmk8lgkvoJ2LChw4fD2 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 6/26/16 5:00 AM, Jan Beich wrote: > pkg-fallout@FreeBSD.org writes: >=20 >> Ident: $FreeBSD: head/multimedia/vapoursynth/Makefile 415615 = 2016-05-22 01:10:34Z jbeich $ >> Log URL: http://beefy5.nyi.freebsd.org/data/101i386-default/417= 455/logs/vapoursynth-r32.log >> Build URL: http://beefy5.nyi.freebsd.org/build.html?mastername=3D= 101i386-default&build=3D417455 >> Log: >> >> build started at Sat Jun 25 02:32:41 UTC 2016 > [...] >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<= phase: build-depends >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> =3D=3D=3D> vapoursynth-r32 depends on executable: sphinx-build - not= found >> =3D=3D=3D> vapoursynth-r32 depends on package: /packages/All/py34-sp= hinx-1.4.4.txz - not found >> =3D=3D=3D> USE_PACKAGE_DEPENDS_ONLY set - not building missing depen= dency from source >> *** Error code 1 >=20 > I'm starting to get failures for a port that hasn't changed for a month= =2E > Anyone got a clue? The regression appears to be from r417413 which land= ed > without an exp-run suggesting any fallout is due to badly written ports= =2E >=20 r417413 was the right fix either way as the old code before the do-depends.sh conversion was also passing DEPENDS_ARGS: subpkgfile=3D`(cd $$dir; ${MAKE} $$depends_args -V PKGFILE)`; \ The problem here is a bug in Poudriere not handling DEPENDS_ARGS properly. The port is forcing python3 as the default even though packages are built with default 2. Dependencies are only built for python2 and this port wants a python3 dependency. It's covered in https://github.com/freebsd/poudriere/issues/259. I've been working on a fix lately and am close to having it complete, which is why I did r417413, because the framework was doing the wrong thing. net/tiny-network-utilities is another example where this is a problem and PACKAGE_BUILDING was used to set IGNORE to avoid the problem for now.= --=20 Regards, Bryan Drewery --gudvjOAE9LLvWStmk8lgkvoJ2LChw4fD2-- --DM35dHgFJxcV7SfHU03GPmN7eldvSnd10 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJXcVx8AAoJEDXXcbtuRpfPiqoH/irSI2T4ewNknu1NaBSxGV/I Bw6pxrIj7XVmd/IRC5tvRQtKrnuK0aGBU97UfPERDonMJhcXgAvr0ybHsjfAx7FN 1kPRZjNIgJlDOh29dgHyDDEiDoqyQrfgqX1Z7TgRPkMHQX8R9usvh5ppLs6ZtZ6q gxnI17DR2J9uHGhF7t5R3IyqJRy8YUqPVUqcOVzPMILncbGJ5JKL72GkQmIRFjG7 pVHIVzualYEkq5gJ+t+Wta6xiWzlpyFADkZmYQniOErLsl4Cq8fHYkzykJQhnFYn 0d1qL4yoyKf3iDNs43mpoimh1T6mCLAw1lqhSfl1Q+3oKxyrfnXvFrTNVWHziw0= =TD4/ -----END PGP SIGNATURE----- --DM35dHgFJxcV7SfHU03GPmN7eldvSnd10-- From owner-freebsd-ports@freebsd.org Mon Jun 27 18:06:03 2016 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 EF168B841DC; Mon, 27 Jun 2016 18:06:03 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD58A21E9; Mon, 27 Jun 2016 18:06:03 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-vk0-x229.google.com with SMTP id j2so242521231vkg.2; Mon, 27 Jun 2016 11:06:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc; bh=uqi5feDamAw01JhhXlVDB/fqnUXxzz3v80juJnC86Is=; b=C2Z87HeK1CwPMY4UvkFV9mreLvdnm3Hsj5QWP0fwYJBzcBh691fHbTtKNHrOGdP6I6 81tR6xCKZ9Y7I9WS/orl/ea4WJemX2/iOW3YE46ExaW8JRFn8/kyb7h23FKR9JBhNSE0 8J41tw4PkxY1l369XgO5QcyfYFdE5CGbBAoGeVEfDBW/xgnqrXfEst+tAljcASUY+MJh WGKjPIL+JZ1xmPxtb/0gsPXxVejzwl628TOdXEe9030JzqtCt0lQhiu6Z3byPT2Iizf4 T8+Jn007s8oJGTrAUT+vgunZZiZA7PWojxYZM7opa/3s93ovBbFaaN+NUhdYa8V/Yj8s EerQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=uqi5feDamAw01JhhXlVDB/fqnUXxzz3v80juJnC86Is=; b=Oe6pkNbPsVd9TEkGAmIvWfMRcfgywac52ZLZXzWxpUuSJgFmxJedN0eBrBEVqDEPd/ khgHVUuKxtjqslnWS5LEGTU0sCTDyas6QUS3ZFXPd1O0AdZwQaG/B5NFD4L75njben4y Xk2N2zE+WoSs0QLQVmPTbgYi09v1EOj1RlBVtS1MoyXsLnESH4RWrBuIHQvsQg/UrO/K Smft92BOVJmRGsx+h8y4KuO9CllAuuOVL5vonz+BoPsqR69Hww8JDpsA3QBPJJ/3iIjp 9QiGo7xZXAOaOBCuZQM93lSFM04OIPEVsu8bhNXBn2cyYbKXBt365EzLGPoqZP1kr6HC caZg== X-Gm-Message-State: ALyK8tIyApKjd8rwhAyhNTrWaWC6lPeVFneqkit8xAL6JzIm0x1xNXjPcydoalQXiRONCDJk6SJNisx5pqgsoQ== X-Received: by 10.31.210.133 with SMTP id j127mr8868988vkg.143.1467050762672; Mon, 27 Jun 2016 11:06:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.54.196 with HTTP; Mon, 27 Jun 2016 11:06:02 -0700 (PDT) From: Russell Haley Date: Mon, 27 Jun 2016 11:06:02 -0700 Message-ID: Subject: Maintaining mono/.net To: freebsd-ports@freebsd.org Cc: Freebsd-mono Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 18:06:04 -0000 Hello Ports Team, A couple of us on the freebsd-mono@ mailing list are having a discussion on how best to maintain the mono ports/.net ports. One of the things that has come up is maintaining the patches for "all this stuff". The current paradigm in FreeBSD as I understand it is to use the files directory and apply the patches to the port via svn/ports tree. However, with the ubiquity of GitHub in opensource, it now seems to be feesable to simply create a Github accound to maintain a bunch of forked repositories (which is essentially a patched git repository!). This makes it easier to create and apply patches and gives us the natural path to push things back upstream. In the end, we would just pull from the FreeBSD specific repository, which is no different than, say, pulling from the mono project directly. This email is a request for response from anyone on the ports team (or FreeBSD general) to give some input as to the acceptability of this solution, as well as any "gotchas" we haven't thought of yet. Thanks in advance! Russ From owner-freebsd-ports@freebsd.org Mon Jun 27 18:21:24 2016 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 55540B84658; Mon, 27 Jun 2016 18:21:24 +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 1BB752AC3; Mon, 27 Jun 2016 18:21:24 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bHb9w-000OIq-Ug; Mon, 27 Jun 2016 20:21:24 +0200 Date: Mon, 27 Jun 2016 20:21:24 +0200 From: Kurt Jaeger To: Russell Haley Cc: freebsd-ports@freebsd.org, Freebsd-mono Subject: Re: Maintaining mono/.net Message-ID: <20160627182124.GA79889@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.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 18:21:24 -0000 Hi! > A couple of us on the freebsd-mono@ mailing list are having a > discussion on how best to maintain the mono ports/.net ports. One of > the things that has come up is maintaining the patches for "all this > stuff". The current paradigm in FreeBSD as I understand it is to use > the files directory and apply the patches to the port via svn/ports > tree. However, with the ubiquity of GitHub in opensource, it now seems > to be feesable to simply create a Github accound to maintain a bunch > of forked repositories (which is essentially a patched git > repository!). >From my point of view, while not perfect, it sounds reasonable. -- pi@opsec.eu +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Mon Jun 27 19:43:40 2016 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 6015DB84197 for ; Mon, 27 Jun 2016 19:43:40 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm18-vm9.access.bullet.mail.gq1.yahoo.com (nm18-vm9.access.bullet.mail.gq1.yahoo.com [216.39.62.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3923A2E53 for ; Mon, 27 Jun 2016 19:43:39 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1467056440; bh=7yt4LQIr9vgsYsGXAuUbSdqQseIJQDvX9UUgml/8cWQ=; h=From:To:Subject:Date:From:Subject; b=QTcwljkyHI811bvB66G4PeJwjok5XbOSKE18DQn8yCvd9bhgTq1VkoC1z5IHAUINRhpheyNfVUAXtXj7k8Iwgxz5AKNyjeRIpnkgKNgZd69C4hk/tjvVR86+VgxMt3l/ZS9iMdTPjyV1HyrR1TeSvBKZs6qnXWKX8GyP/Y5oFH8= Received: from [216.39.60.172] by nm18.access.bullet.mail.gq1.yahoo.com with NNFMP; 27 Jun 2016 19:40:40 -0000 Received: from [67.195.22.113] by tm8.access.bullet.mail.gq1.yahoo.com with NNFMP; 27 Jun 2016 19:40:40 -0000 Received: from [127.0.0.1] by smtp115.sbc.mail.gq1.yahoo.com with NNFMP; 27 Jun 2016 19:40:40 -0000 X-Yahoo-Newman-Id: 443188.32702.bm@smtp115.sbc.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: uLsMC94VM1kq86ryUigJcjrZP5mdriF9KNtCpANaoeEFuYH dx5yL2WcPHMXYYavp_tXY6dp59.z00oVt3Q1PlnZfWOEgJrEJTAhaPIndjoP q4W_qjGHgS1JVrK10bKmd1C58VFwjz7lNpju368j7Kg97XXkuFEr2Zg15mCd z22wCWSRf7Wvd80qnANX3ISHFfSvCla9y.4IBQTZ3SaY5_Fj7KwYHqJD_bWe aDa8jONUURXTnE3oBuBff_T_13fb3jNLNJL8vM3ZYlBxmmykJnU.WIuASrgi Ka8Kyjpbna8iZH2UACPiK9ONN5F7ZG7Zc9_YE3EqHLt9T6I1MnMnSxJkD1_Z urukNrbyd9.cFcUSb.UDYEa4_RUBtWelragrpHFsX_WNJckO.2GKZhE_Uxjo yJzu0hte03ZIiRy13zKS8LfPv3VOmnrMaRCy6IVfHDTwXWe6yE.BT6CqfgDg EtkiVBGfE7ks3EkG3Y0bD3whRnFsw_xpNUcHV9F4dxeLrBZ8vFpjeLGAmMEV HAT3bS3KsIbF2zB_tf.6e59X.6_X24aZ0DlrZNsO0jfbZYjKXhg6GHg-- X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: ports-list freebsd Subject: PKG: MariaDB 10.1 doesn't supply my.cnf.* files Date: Mon, 27 Jun 2016 15:40:39 -0400 Message-ID: <6203nb160pm6p9jjgtg2v5lqs1833daqe9@4ax.com> X-Mailer: Forte Agent 4.2/32.1118 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 19:43:40 -0000 Just installed the MariaDB 10.1 package under 10.3, and discovered that there are no my.cnf.* files included as was standard in the past. That seems like a regression of sorts. From owner-freebsd-ports@freebsd.org Mon Jun 27 19:16:53 2016 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 896D5B8497F for ; Mon, 27 Jun 2016 19:16:53 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (mail.sorbs.net [67.231.146.200]) by mx1.freebsd.org (Postfix) with ESMTP id 749292C3C; Mon, 27 Jun 2016 19:16:52 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0O9G00F4M0G8AO10@hades.sorbs.net>; Mon, 27 Jun 2016 11:24:11 -0700 (PDT) Subject: Re: blanket portmgr approval vs. non-fixing changes To: koobs@FreeBSD.org, Adam Weinberger , araujo@freebsd.org Cc: Matthias Andree , marino@freebsd.org, ports-committers , Mathieu Arnold , freebsd-ports , FreeBSD Ports Management Team , Sunpoet Po-Chuan Hsieh References: <201606261724.u5QHOLdG081392@repo.freebsd.org> <57701AEB.1050001@tu-dortmund.de> <5770A392.6010605@tu-dortmund.de> <84e4fcf5-7b99-1cc6-e6bd-d3c594a5d102@marino.st> <91BC5F8F9FDB9246529D0693@atuin.in.mat.cc> <5770EAD2.4060302@tu-dortmund.de> <2A4F1FFE-8B27-4569-8CCA-D498B5235D18@adamw.org> <9364c255-9733-b1a0-68a1-a058ca78d95e@FreeBSD.org> From: Michelle Sullivan Message-id: <57716D89.1050108@sorbs.net> Date: Mon, 27 Jun 2016 20:16:41 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 In-reply-to: <9364c255-9733-b1a0-68a1-a058ca78d95e@FreeBSD.org> X-Mailman-Approved-At: Mon, 27 Jun 2016 20:04:12 +0000 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 19:16:53 -0000 Kubilay Kocak wrote: > > All: How did you feel the first time you saw your email on a maintainer > line? That is priceless and shouldn't be confused with the 'bad' kind of > ownership. > Don't forget that many people see their name/email in the maintainer line as being responsible for the port.. so someone goes makes blanket changes which actually breaks stuff.. that reflects on the person in the Maintainer line - whether you want it to do so or not, whether you believe it or not.. Regards, -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-ports@freebsd.org Mon Jun 27 20:48:59 2016 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 5FC6DB85385 for ; Mon, 27 Jun 2016 20:48:59 +0000 (UTC) (envelope-from jbeich@freebsd.org) 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 4679C26BB for ; Mon, 27 Jun 2016 20:48:59 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 42241B85384; Mon, 27 Jun 2016 20:48:59 +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 3F5D3B85383 for ; Mon, 27 Jun 2016 20:48:59 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from vfemail.net (onethreetwo.vfemail.net [199.16.11.132]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CA43226B9 for ; Mon, 27 Jun 2016 20:48:58 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: (qmail 13036 invoked by uid 89); 27 Jun 2016 20:48:51 -0000 Received: from localhost (HELO freequeue.vfemail.net) (127.0.0.1) by localhost with (DHE-RSA-AES256-SHA encrypted) SMTP; 27 Jun 2016 20:48:51 -0000 Received: (qmail 13017 invoked by uid 89); 27 Jun 2016 20:48:34 -0000 Received: by simscan 1.3.1 ppid: 13012, pid: 13014, t: 0.0032s scanners:none Received: from unknown (HELO smtp102-2.vfemail.net) (172.16.100.62) by FreeQueue with SMTP; 27 Jun 2016 20:48:34 -0000 Received: (qmail 14645 invoked by uid 89); 27 Jun 2016 20:48:34 -0000 Received: by simscan 1.4.0 ppid: 14630, pid: 14642, t: 0.5624s scanners:none Received: from unknown (HELO nil) (amJlaWNoQHZmZW1haWwubmV0@172.16.100.27) by mail.vfemail.net with ESMTPA; 27 Jun 2016 20:48:33 -0000 From: Jan Beich To: Bryan Drewery Cc: FreeBSD Ports mailing list Subject: Re: USE_PACKAGE_DEPENDS_ONLY set - not building missing dependency from source References: <201606250232.u5P2Wndq091282@beefy5.nyi.freebsd.org> <7fdc-gny4-wny@vfemail.net> <65756e68-af20-5594-e719-4b5a4795b36f@FreeBSD.org> Date: Mon, 27 Jun 2016 22:48:26 +0200 In-Reply-To: <65756e68-af20-5594-e719-4b5a4795b36f@FreeBSD.org> (Bryan Drewery's message of "Mon, 27 Jun 2016 10:03:55 -0700") Message-ID: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 20:48:59 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Bryan Drewery writes: > On 6/26/16 5:00 AM, Jan Beich wrote: > >> pkg-fallout@FreeBSD.org writes: >>=20 >>> Ident: $FreeBSD: head/multimedia/vapoursynth/Makefile 415615 >>> 2016-05-22 01:10:34Z jbeich $ >>> Log URL: >>> http://beefy5.nyi.freebsd.org/data/101i386-default/417455/logs/vapoursy= nth-r32.log >>> Build URL: http://beefy5.nyi.freebsd.org/build.html?mastername=3D1= 01i386-default&build=3D417455 >>> Log: >>> >>> build started at Sat Jun 25 02:32:41 UTC 2016 >> [...] >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>> =3D=3D=3D> vapoursynth-r32 depends on executable: sphinx-build - not = found >>> =3D=3D=3D> vapoursynth-r32 depends on package: /packages/All/py34-sph= inx-1.4.4.txz - not found >>> =3D=3D=3D> USE_PACKAGE_DEPENDS_ONLY set - not building missing depend= ency from source >>> *** Error code 1 >>=20 >> I'm starting to get failures for a port that hasn't changed for a month. >> Anyone got a clue? The regression appears to be from r417413 which landed >> without an exp-run suggesting any fallout is due to badly written ports. >>=20 > > r417413 was the right fix either way as the old code before the > do-depends.sh conversion was also passing DEPENDS_ARGS: > > subpkgfile=3D`(cd $$dir; ${MAKE} $$depends_args -V PKGFILE)`; \ > > The problem here is a bug in Poudriere not handling DEPENDS_ARGS > properly. The port is forcing python3 as the default even though > packages are built with default 2. Dependencies are only built for > python2 and this port wants a python3 dependency. sphinx-build is called by gmake, not python, so any python version would work fine. Notice, the dependency line doesn't specify PYTHON_PKGNAMEPRIFX. > It's covered in > https://github.com/freebsd/poudriere/issues/259. I've been working on a > fix lately and am close to having it complete, which is why I did > r417413, because the framework was doing the wrong thing. I don't see how that issue would help here. py27-sphinx, py34-sphinx, etc. cannot be installed at the same time due to a conflict in bin/sphinx-*. If something else installed the port using different python version vapoursynth would fail to build due to unsatisfied dependencies. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQF8BAEBCgBmBQJXcZEaXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREQjQ0MzY3NEM3RDIzNTc4NkUxNDkyQ0VF NEM3Nzg4MzQ3OURCRERCAAoJEOTHeINHnb3bnCgH/j3JHxayqsd9eii2wcDBa4uB KMum/qIWxQWoijsi3csXpXUOLe/cJyVbP+b3CDYrliMlY1Q59swgiWEa9YhNjx03 c74YbmfYhDUvJnNeVL/7/Si9PXknr9NAvDvwkIsqVMc0jsqvMblBdujxNe4tQNUi hAIvb9lmLBb4Gm4ij4SmBOVRhGF9WOaBgNy5Hbh5JD72jCYy3zqCm2yFexxPEj5q 9WtPtSYdlIUOSzXhp1t0gpnB7Xe5XEZDzeRagyaL28Pg4OGfmPcv8xGBc+H9KEMH Hg2STHF+HSIryvp7eLBzoLKivQYWX3EWTSTUF9o8mGqibmxeV0Ptd+E7Q8h3KqI= =ypGM -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-ports@freebsd.org Mon Jun 27 20:51:31 2016 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 E1D93B85417 for ; Mon, 27 Jun 2016 20:51:31 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm14-vm5.access.bullet.mail.gq1.yahoo.com (nm14-vm5.access.bullet.mail.gq1.yahoo.com [216.39.63.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B920F2920 for ; Mon, 27 Jun 2016 20:51:31 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1467060568; bh=/nayUfBlI/HlJvN9OffyYj3DDmuc99/V/LL4reBjYIw=; h=From:To:Subject:Date:References:In-Reply-To:From:Subject; b=pKd+2VOEAiZS7vWdPrRuJtx4cz1PRTISuJEHrswm9fXfBzi6KMOs/KcPpWvTBTfC2vFytJuK8aGrcLOA0Hh8CHOTA9Yr4tDOwx7SVanP6Gvzd/s198fMxK7LRG7YmUJKwxnVWIDdILay7aXllyMODNwWeAk+OZFDJK6nqHAcJc0= Received: from [216.39.60.166] by nm14.access.bullet.mail.gq1.yahoo.com with NNFMP; 27 Jun 2016 20:49:28 -0000 Received: from [67.195.22.113] by tm2.access.bullet.mail.gq1.yahoo.com with NNFMP; 27 Jun 2016 20:49:28 -0000 Received: from [127.0.0.1] by smtp115.sbc.mail.gq1.yahoo.com with NNFMP; 27 Jun 2016 20:49:28 -0000 X-Yahoo-Newman-Id: 818296.16254.bm@smtp115.sbc.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: DojsSbcVM1mnAkOlCUGnSga0Vj_pu0lPuPGjDewQAEUIDuV oSB6iO07fk__Uia061eKczvQvxzfKmh3SGpwRBo8gyrRdPijO_9FswMIXWoE OmeqO21kUOYLaYk2r_XAh9Nqdw96ut.Vz3vbOYWiT9iLz1HfIEdxD3B1cZps 7mTrfMlrXvPcS_chFM.Vr_54X4oHfvRRJeRAP8qf5sRi3dU9C20Cjis9sMlw qc.SW.vihje1Q.7.e8dGw.iIdA0HBjt_EqhyTeQmWlD9oa.DqbVcYWBqjQdJ aaZtrm5hLMe6ResnP.nuE.h8IKAH6.BaADt6TUMUv2yIaDeJlJlcGGODfizg MveED4mE_O0W7gWSOCBTXHmfbsw3q1Se8U466VbxqSX46IukRT57aOp_vXhQ rKqs.OPTyeemv5ZmJWb4VRmQsu8tAPVRhIghfDFer5NZaYY1JrtDioDefuWD 19FQldyDBfxNLvw7FKIXMaU9tPCcUm7KCvHdjipkrjVgb_dNMoetkepav2Cs Q4aUBbofGKSYoARnISRbfTJmVP1KjDXMBRagvfqqkIQI23GXSOuJDLbIKjwv 4 X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: freebsd-ports@freebsd.org Subject: Re: PKG: MariaDB 10.1 doesn't supply my.cnf.* files Date: Mon, 27 Jun 2016 16:49:27 -0400 Message-ID: <2843nbllvoaijo0e9pb057enk9a7jpvds8@4ax.com> References: <6203nb160pm6p9jjgtg2v5lqs1833daqe9@4ax.com> In-Reply-To: <6203nb160pm6p9jjgtg2v5lqs1833daqe9@4ax.com> X-Mailer: Forte Agent 4.2/32.1118 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 20:51:32 -0000 False alarm -- they're now named my-*.cnf rather than, as I seem to remember, my.cnf.* >Just installed the MariaDB 10.1 package under 10.3, and >discovered that there are no my.cnf.* files included as was >standard in the past. That seems like a regression of sorts. >_______________________________________________ >freebsd-ports@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-ports >To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Mon Jun 27 20:21:39 2016 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 857FFB84D11 for ; Mon, 27 Jun 2016 20:21:39 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A0E4277C; Mon, 27 Jun 2016 20:21:38 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with SMTP id Hd2Db57JLBLFmHd2EbiUZK; Mon, 27 Jun 2016 14:21:37 -0600 X-Authority-Analysis: v=2.2 cv=W5d6blek c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=pD_ry4oyNxEA:10 a=5noeBbRCAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=jKalHx2oKn8LmRi9RhoA:9 a=pILoi4Qadgk23tj5ZfSS:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id E81AB13752; Mon, 27 Jun 2016 13:21:32 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id u5RKLVhQ057899; Mon, 27 Jun 2016 13:21:32 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201606272021.u5RKLVhQ057899@slippy.cwsent.com> X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.6 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Michelle Sullivan cc: koobs@FreeBSD.org, Adam Weinberger , araujo@freebsd.org, Matthias Andree , marino@freebsd.org, ports-committers , Mathieu Arnold , freebsd-ports , FreeBSD Ports Management Team , Sunpoet Po-Chuan Hsieh Subject: Re: blanket portmgr approval vs. non-fixing changes In-Reply-To: Message from Michelle Sullivan of "Mon, 27 Jun 2016 20:16:41 +0200." <57716D89.1050108@sorbs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jun 2016 13:21:31 -0700 X-CMAE-Envelope: MS4wfN6SNQTCNdE5TZpfoNMs+QWz4iJ2uZymbnOh2AxUVfskAJUA+JtKSF3KRV3BsKn1I6WZJ9Ki3CsFDTrH/fYc6QqG0vatebE1XGPP63lJ1P0zX2VHX3XP ZaQhuQOvR3T3zepbjZIGdrFT3XsHnQhyQjy7mhFbFmVLPtKaOZCWSLrUsqX46WOtshP9AFAem3FB2VfxyYUBGbYiSW3cAr+HN++fEiq3oZ0/B5DD0lxl16uW 2+MQtcQQeBjwiimJylJY2QLhQciOKa8LHg5LAfTD7nKignrFC3esfi0XBWPZmCfviB0+A9Pz36arFgwXhLoeq0512E/qkKJh2OPxI6CgBC8NPevSzg9OuCwf Ou6yFAwmt57qKQPXOHhOeokQIaGHzZiaX9UtWwn9VXDkOaFAFQ4m4DoOLT3lSgja+HT8f3ynO5VMiOtLiKoPp1Q49gxMn6fzFDaNqffOluHxHE4VSrD3ELiy BcB/xNgjh/9ZbsTniWr3LHFPl1kt4d2s903ksA== X-Mailman-Approved-At: Mon, 27 Jun 2016 21:17:26 +0000 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 20:21:39 -0000 In message <57716D89.1050108@sorbs.net>, Michelle Sullivan writes: > Kubilay Kocak wrote: > > > > All: How did you feel the first time you saw your email on a maintainer > > line? That is priceless and shouldn't be confused with the 'bad' kind of > > ownership. > > > > Don't forget that many people see their name/email in the maintainer > line as being responsible for the port.. so someone goes makes blanket > changes which actually breaks stuff.. that reflects on the person in the > Maintainer line - whether you want it to do so or not, whether you > believe it or not.. I think it's more than the maintainer perceives that they're responsible. Getting that email from freebsd-pkg-fallout I think there was and maybe still is a general impression that is had. I for one take the attitude, you break it, you fix it and I don't hesitate to email any committer who made a blanket change that broke something. It's only fair because fixing breakage caused by others also takes away from other productive work and projects, as some of us do have time constraints and time pressure due to other commitments. I have no problems with blanket approval as long as everyone understands the rules of engagement. I think the maintainer has final say on version updates and general structure such as supported options or anything that adds additional support requirements. For example, someone submits a PR to add option X. Adding option X should require maintainer approval whereas implementation of options helpers shouldn't require maintainer approval (but if anything breaks, the committer breaking the port should fix it). Anything else should be fair game. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-ports@freebsd.org Mon Jun 27 21:22:30 2016 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 50588B85DD9 for ; Mon, 27 Jun 2016 21:22:30 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 318192239 for ; Mon, 27 Jun 2016 21:22:30 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 30E5CB85DD8; Mon, 27 Jun 2016 21:22:30 +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 3099FB85DD7 for ; Mon, 27 Jun 2016 21:22:30 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 174AC2238; Mon, 27 Jun 2016 21:22:30 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [IPv6:::1]) by freefall.freebsd.org (Postfix) with ESMTP id 082641CC5; Mon, 27 Jun 2016 21:22:30 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id A9D1A1C9A7; Mon, 27 Jun 2016 21:22:29 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id FS7cL03xNvii; Mon, 27 Jun 2016 21:22:24 +0000 (UTC) Subject: Re: USE_PACKAGE_DEPENDS_ONLY set - not building missing dependency from source DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com D9FE71C99E To: Jan Beich References: <201606250232.u5P2Wndq091282@beefy5.nyi.freebsd.org> <7fdc-gny4-wny@vfemail.net> <65756e68-af20-5594-e719-4b5a4795b36f@FreeBSD.org> Cc: FreeBSD Ports mailing list From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: <71d0a76b-8492-c51f-fc55-609afc97c497@FreeBSD.org> Date: Mon, 27 Jun 2016 14:21:48 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6RcTwU9bnpopRdQCLfq3smU51CHoxP2aR" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 21:22:30 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6RcTwU9bnpopRdQCLfq3smU51CHoxP2aR Content-Type: multipart/mixed; boundary="6Bpcu1FB6bSskLFcW06lrIwjnbhoXeL75" From: Bryan Drewery To: Jan Beich Cc: FreeBSD Ports mailing list Message-ID: <71d0a76b-8492-c51f-fc55-609afc97c497@FreeBSD.org> Subject: Re: USE_PACKAGE_DEPENDS_ONLY set - not building missing dependency from source References: <201606250232.u5P2Wndq091282@beefy5.nyi.freebsd.org> <7fdc-gny4-wny@vfemail.net> <65756e68-af20-5594-e719-4b5a4795b36f@FreeBSD.org> In-Reply-To: --6Bpcu1FB6bSskLFcW06lrIwjnbhoXeL75 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 6/27/2016 1:48 PM, Jan Beich wrote: > Bryan Drewery writes: >=20 >> On 6/26/16 5:00 AM, Jan Beich wrote: >> >>> pkg-fallout@FreeBSD.org writes: >>> >>>> Ident: $FreeBSD: head/multimedia/vapoursynth/Makefile 415615 >>>> 2016-05-22 01:10:34Z jbeich $ >>>> Log URL: >>>> http://beefy5.nyi.freebsd.org/data/101i386-default/417455/logs/vapou= rsynth-r32.log >>>> Build URL: http://beefy5.nyi.freebsd.org/build.html?mastername=3D= 101i386-default&build=3D417455 >>>> Log: >>>> >>>> build started at Sat Jun 25 02:32:41 UTC 2016 >>> [...] >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>> =3D=3D=3D> vapoursynth-r32 depends on executable: sphinx-build - n= ot found >>>> =3D=3D=3D> vapoursynth-r32 depends on package: /packages/All/py34-= sphinx-1.4.4.txz - not found >>>> =3D=3D=3D> USE_PACKAGE_DEPENDS_ONLY set - not building missing dep= endency from source >>>> *** Error code 1 >>> >>> I'm starting to get failures for a port that hasn't changed for a mon= th. >>> Anyone got a clue? The regression appears to be from r417413 which la= nded >>> without an exp-run suggesting any fallout is due to badly written por= ts. >>> >> >> r417413 was the right fix either way as the old code before the >> do-depends.sh conversion was also passing DEPENDS_ARGS: >> >> subpkgfile=3D`(cd $$dir; ${MAKE} $$depends_args -V PKGFILE)`; \ >> >> The problem here is a bug in Poudriere not handling DEPENDS_ARGS >> properly. The port is forcing python3 as the default even though >> packages are built with default 2. Dependencies are only built for >> python2 and this port wants a python3 dependency. >=20 > sphinx-build is called by gmake, not python, so any python version woul= d > work fine. Notice, the dependency line doesn't specify PYTHON_PKGNAMEPR= IFX. >=20 ~/svn/ports/multimedia/vapoursynth # make -V DEPENDS_ARGS PYTHON_VERSION=3Dpython3.4 This means it will force any dependencies of python to build for 3.4. This happens in any direct usage of ports, including portmaster and portupgrade. Poudriere is wrong here to not build a py34-sphynx. If it really doesn't matter what version it is then the dependency could be changed to the specific package name of the default python, but ... PYTHON_USES=3D python:3.3- This line forces vapoursynth to be built for 3.4. Removing the :3.3- fixes the problem: ~/svn/ports/multimedia/vapoursynth # make -V DEPENDS_ARGS PYTHON_VERSION=3Dpython2.7 >> It's covered in >> https://github.com/freebsd/poudriere/issues/259. I've been working on= a >> fix lately and am close to having it complete, which is why I did >> r417413, because the framework was doing the wrong thing. >=20 > I don't see how that issue would help here. It helps because you need to understand the DEPENDS_ARGS feature to understand what's going on here. It's quite an old feature that poudriere has failed to support, which causes these USE_PACKAGE_DEPENDS_ONLY failures. Note again that the fix I made in r417413 was fixing a regression from when the dependency handling in Mk/bsd.port.mk was moved to Mk/Scripts/do-depends.sh. >=20 > py27-sphinx, py34-sphinx, etc. cannot be installed at the same time due= > to a conflict in bin/sphinx-*. If something else installed the port Right, nothing I'm working on allows installing multiple versions of the same package at the same time. I am fixing Poudriere to build multiple versions of dependencies in its queue, rather then only building the python2.7 version of dependencies and thus hitting the problem you mailed about. > using different python version vapoursynth would fail to build due to > unsatisfied dependencies. >=20 --=20 Regards, Bryan Drewery --6Bpcu1FB6bSskLFcW06lrIwjnbhoXeL75-- --6RcTwU9bnpopRdQCLfq3smU51CHoxP2aR Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJXcZkTAAoJEDXXcbtuRpfPUOAIAM/0lf7eA2Ourk+0FJoeFI1Z gQVGBKhaBmo2oqyhC0sFi1D1jTgmiXMIleeKzMVgwe9RVypokMPDjb/voI0h2xY/ sqGWZdGZU7KEDsjTIXWkrgvBuz1SnbXLr22SiLjzbavGUTmv5fZvYAlbWv5w2R0X 93UNFLk7DMgNUkOT/8bFep93MDeqr7h0OSkyaZ6sHlENC6w4O7RVdRMuAV5fLC++ tIUhKouhb1oMWoRdsD0CYRUzU0p0UdcWQ27wxEw2UrIN8tT9Em7Qp5epLaQD5P4w wyiTD3ijLEbBt3krXtVOvZtg/nSMAvFGGIXtd379UK9ZtEg8Jt18ZVkaGTSPSqY= =bzkt -----END PGP SIGNATURE----- --6RcTwU9bnpopRdQCLfq3smU51CHoxP2aR-- From owner-freebsd-ports@freebsd.org Mon Jun 27 21:23:13 2016 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 0D974B85E22 for ; Mon, 27 Jun 2016 21:23:13 +0000 (UTC) (envelope-from dan@langille.org) Received: from clavin1.langille.org (clavin.langille.org [162.208.116.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "clavin.langille.org", Issuer "StartCom Class 2 Primary Intermediate Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E038F23EC; Mon, 27 Jun 2016 21:23:12 +0000 (UTC) (envelope-from dan@langille.org) Received: from (clavin1.int.langille.org (clavin1.int.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) with ESMTPSA id E777E36DB ; Mon, 27 Jun 2016 21:22:57 +0000 (UTC) From: Dan Langille Subject: 2016Q2 - no Mk/Uses/mysql.mk Date: Mon, 27 Jun 2016 17:22:56 -0400 Message-Id: Cc: brnrd@FreeBSD.org To: FreeBSD Ports Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 21:23:13 -0000 I've been working with the 2016Q2 branch with respect to FreshPorts. I tried running make -V on branches/2016Q2 and it failed with: Error message is: make: "/usr/local/repos/PORTS-2016Q2/Mk/bsd.port.mk" = line 1433: Cannot open /usr/local/repos/PORTS-2016Q2/Mk/Uses/mysql.mk It seems that recent changes to Mk also need to be backported to = branches if there is a commit on that branch. Agreed? --=20 Dan Langille - BSDCan / PGCon dan@langille.org From owner-freebsd-ports@freebsd.org Mon Jun 27 21:42:12 2016 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 89618B847E0 for ; Mon, 27 Jun 2016 21:42:12 +0000 (UTC) (envelope-from rodrigo@freebsd.org) Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [IPv6:2a01:e0c:1:1599::10]) (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 5AB0E261B for ; Mon, 27 Jun 2016 21:42:12 +0000 (UTC) (envelope-from rodrigo@freebsd.org) Received: from [192.168.1.32] (unknown [78.194.61.125]) by smtp1-g21.free.fr (Postfix) with ESMTP id 1E9C2B00294 for ; Mon, 27 Jun 2016 21:38:45 +0200 (CEST) Subject: Re: pkg SAT_SOLVER bugs To: freebsd-ports@freebsd.org References: <20150414200459.GE39658@ivaldir.etoilebsd.net> <20150421103454.GR1394@zxy.spb.ru> <5593D0AE.2010205@selasky.org> <416359ce-1dcd-1160-5c56-f120a0f6358f@selasky.org> From: Rodrigo OSORIO Message-ID: <81eaaea2-edc7-9337-0b53-ff6df1c1beca@freebsd.org> Date: Mon, 27 Jun 2016 23:42:08 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <416359ce-1dcd-1160-5c56-f120a0f6358f@selasky.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 21:42:12 -0000 On 06/27/16 12:38, Hans Petter Selasky wrote: > Hi, > > I found some bugs in PKG with regard to the SAT_SOLVER environment > variable. Please find patch attached :-) > > Issues fixed: > 1) No need to use hash table when generating SAT rules for external > solver. Variables are already in a linear array. Fix encoding and > decoding of SAT data. > 2) Endless variable loop caused pkg to crash. > 3) it->inverse was checked for non-zero, while it should actually be > checked for -1 only. SAT rules produces were all negative. > > How to verify: > > make -C /usr/ports/math/picosat all install clean > > env SAT_SOLVER=picosat pkg upgrade > > --HPS > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > Thanks! this patch saves my day, I was stuck reinstalling a computer in current, and after few rounds using pkg the solver start complaining and pretending missing packages was yet installed. I apply you patch on top of the last version in ports and the patch work as a charm. I'll keep testing it until a new version comes. regards, - rodrigo From owner-freebsd-ports@freebsd.org Mon Jun 27 22:09:47 2016 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 59C2AB85269 for ; Mon, 27 Jun 2016 22:09:47 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D2C422C3C; Mon, 27 Jun 2016 22:09:46 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id v199so116855424wmv.0; Mon, 27 Jun 2016 15:09:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=kZH1WCZE/jvulswBYRtUPAvVz0dmNfInfSR5O2pdPMo=; b=kXaya79cFYigtiArUFJJRMipdIxehV6KcxJBQzBUKPryIdJ5UxHH4BrjzeYM9PCoM3 mneUT/edzjhpVwH68Mi3w/IjEv1x02hhcRdouxQ4aBkTXxtlPqa8XnqKDDRsRR2sRATN XmYxqKZHYKj+lyPAytN8BlZC/pD3eT+JejbMN9entpr8VKBw/pudzJV9CXFQzzM+5QUw 9TeFttAhm+hf3bfAhRmMBg2HvFhfwWOVNJtdHkWjvb9dewqs0UuzY/P5T13y94/DbWoJ c0o33e+9LfrVv03XQfVB6uZrO85BAdXwxotPUl8j8DIDoU/9+ga4sSM+zzSIgz/uAj59 Ok/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=kZH1WCZE/jvulswBYRtUPAvVz0dmNfInfSR5O2pdPMo=; b=MsJHgctuZx1/35G/LGab2ECqvLdZP05oqneNPKMXFzYYSaVbETl0M5E8hhwUM1fGLw mszUkdnvWkdd1c27N+duiUGRciSkDdxcBsLs/eSyKELEyCFMGx07UR5X3Y7q2Hjv/QeG zN05uW3MN82r0eTLFuvzpjdQvrBAcV8O57zOsWn/OK7m2VqJ1MMEp10M9D0vTOKuWieg SA1d2CvArusDUxPbuWb5cB2CZwZO16QrsR/xOHfWwnfcV/u6T4HjtD3RJIjAlPh1V6b4 PIy84m9DjhbJZYCMg20Pmoz+k9ls7yILEfdV2or1xyc2nCXmhnapex3nN0bvYkqlWTB1 M80w== X-Gm-Message-State: ALyK8tJ3dLHAv9ukB1+a26TiP6Cnkx9OHcYtq8vUX6XkGhbsWmalMmpazhbrd28MgjYzTg== X-Received: by 10.194.167.39 with SMTP id zl7mr2964951wjb.98.1467065385297; Mon, 27 Jun 2016 15:09:45 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id bh7sm5986910wjb.22.2016.06.27.15.09.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Jun 2016 15:09:44 -0700 (PDT) Sender: Baptiste Daroussin Date: Tue, 28 Jun 2016 00:09:42 +0200 From: Baptiste Daroussin To: Rodrigo OSORIO Cc: freebsd-ports@freebsd.org Subject: Re: pkg SAT_SOLVER bugs Message-ID: <20160627220942.gy7t3klnswmukz6q@ivaldir.etoilebsd.net> References: <20150414200459.GE39658@ivaldir.etoilebsd.net> <20150421103454.GR1394@zxy.spb.ru> <5593D0AE.2010205@selasky.org> <416359ce-1dcd-1160-5c56-f120a0f6358f@selasky.org> <81eaaea2-edc7-9337-0b53-ff6df1c1beca@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tgtwzxc5dak6i2b5" Content-Disposition: inline In-Reply-To: <81eaaea2-edc7-9337-0b53-ff6df1c1beca@freebsd.org> User-Agent: Mutt/1.6.1-neo (2016-06-11) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2016 22:09:47 -0000 --tgtwzxc5dak6i2b5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 27, 2016 at 11:42:08PM +0200, Rodrigo OSORIO wrote: > On 06/27/16 12:38, Hans Petter Selasky wrote: > > Hi, > >=20 > > I found some bugs in PKG with regard to the SAT_SOLVER environment > > variable. Please find patch attached :-) > >=20 > > Issues fixed: > > 1) No need to use hash table when generating SAT rules for external > > solver. Variables are already in a linear array. Fix encoding and > > decoding of SAT data. > > 2) Endless variable loop caused pkg to crash. > > 3) it->inverse was checked for non-zero, while it should actually be > > checked for -1 only. SAT rules produces were all negative. > >=20 > > How to verify: > >=20 > > make -C /usr/ports/math/picosat all install clean > >=20 > > env SAT_SOLVER=3Dpicosat pkg upgrade > >=20 > > --HPS > >=20 > >=20 > > _______________________________________________ > > freebsd-ports@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > >=20 >=20 > Thanks! this patch saves my day, I was stuck reinstalling a computer in > current, and after few rounds using pkg the solver start complaining and > pretending missing packages was yet installed. >=20 > I apply you patch on top of the last version in ports and the patch work = as > a charm. I'll keep testing it until a new version comes. >=20 > regards, > - rodrigo that is unrelated, what saved you it that building from ports you switched = form 1.8.5 to 1.8.6 his patch is to solve the use of an external SAT solver whic= h I admit I haven't tested for a while. Pkg 1.8.6 is the default binary package for all release but head right now, pending for the next build cycle. Best regards, Bapt --tgtwzxc5dak6i2b5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXcaQPAAoJEGOJi9zxtz5a4okQAIezpNF2tRVdWZTbWMlPvYI0 YTPGAryJXCq5ueaxaOlVX/hfHn88hTwuJBs3q1HvKSkvtzOzu1nq4H8zk+NIa2vc CGw4uMwiqFEWwHa1NceRPd896lI+cSQRqY5qWosO1LF+u4104DjaZXUhodbmD6Dm aCE74JWDhiwMINF6EydAA1OQruvgU3HOFzOD8Nq1sQ1jTPn5Rs3GzjlF8uAg0Bqm zO7FRA/tvUOacImJs8p5Ad0Z5eK9yWphNXAmAuR78cyw4WGRHILEzhbsYZnxpLSJ 3BT/5uJVKYUMC0r3Mm9p4dP6xtt+1TOFElbDmvv3evMci1LJVFkr+5PW3HsdVmcP cSIelxqM+OWcpvz1ThBfT3NaXeRuWfW+eMuMRbv9gMn5oso85woqoWomxJ2xpKFg BiU+yu1if7mNCrAseoYizs6t05mvgNqGXi/i2SzvQzVVihr43knRwQQeC/bBPDAS mea5baHCHZq26dwi8ckclFhP18UnNFNYG5oCi5YgGCyLmaFpLK+XTY6L7VRE6m/W ZbF+L5e5AKL/v4zFg9kv3Wk3J4WVU9WY9SLTta9vL9p+1ccNRQkuy8X0y2xiU+g/ ZbLdmBCSpoK8BRbBxTuSwwlELLjVDWBHtDGSkPnkPteTxiRl8sWiEmFebfNmeL2Y 7B8tohIl2cNGIDeAgDb3 =F1uG -----END PGP SIGNATURE----- --tgtwzxc5dak6i2b5-- From owner-freebsd-ports@freebsd.org Tue Jun 28 07:42:31 2016 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 90367B85B2F; Tue, 28 Jun 2016 07:42:31 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 22F062E43; Tue, 28 Jun 2016 07:42:31 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: by mail-wm0-x22b.google.com with SMTP id 187so25490912wmz.1; Tue, 28 Jun 2016 00:42:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=aQBi+ctQAWoWY1b2Ut0kdrhWdJe2D2n6zXhJM0xwqxU=; b=d8KOY0yb84wabty51EnjUc7do7JwlAqjCr6e0oBfjZeMfsIVH//QxulX448Kn7AsEv vXTqChTD0vRtNWCe9e09A9lDpLsfBvKCpsTqhlg3Mfw3u2bJP82mwQY55knTk62XG4S+ uP4a7JWkSJEiQk2hKtQ3WXArS9df1BuLp+PbU0sYfX8sePUWaVTc5cw3yqoZVi8j6Hxk fgrvyhMeuuniKVTDerOKjCG+g9qieeNrEysJG+Iy+p9pBPd7JVFubZY4K0Awvx2xwbUR cYYh+M1sXfa+jCjcttlvLuvuWVk9VVROU6p+FPURpQNkJGpfIEK2IXgzFwJ/yhM5Zvwm O9qg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=aQBi+ctQAWoWY1b2Ut0kdrhWdJe2D2n6zXhJM0xwqxU=; b=XInl/mnNJ27HmtUYIckhEbEOlxrV7o99TdnPIZwP8n4ay3Ybg2PEOcAz8xOPcoiZha u6Zt0FUqQlu/HAAhqqL1U38JpObdu9X4GMu1u7GQggvDTIcwHEMDj92u0jcyHN36rAZ/ z1YJz6cCqFcC8jom4MXPHOaSPGiIE7NzSdyERYvDvQm9xENIbj4UMaLWPaEh9SdIepCZ YSrzOm+zMzV0XTufPW5HU8L1qd52C4as+XicHiSUeRfkdoIMbs4DTSNNttjFPEpJxSz1 ivZ/gLyaJuvktYYAPAYdu2+mgSs8GrNXc0zE8yfxx64W0mzVKsx31VA6uRm0LkB5XTqp F6Lw== X-Gm-Message-State: ALyK8tLcnHYQJkVAY5V3LKLXfz1pvKSp0PJT+QATqpxHaG//iGaj+kjqwSEWvFlvyFIvtQ== X-Received: by 10.194.80.70 with SMTP id p6mr1471869wjx.45.1467099749439; Tue, 28 Jun 2016 00:42:29 -0700 (PDT) Received: from zmaj.softwarehood.com (178-221-67-149.dynamic.isp.telekom.rs. [178.221.67.149]) by smtp.googlemail.com with ESMTPSA id cx8sm7202970wjb.37.2016.06.28.00.42.28 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 28 Jun 2016 00:42:28 -0700 (PDT) Message-ID: <57722A63.5070102@gmail.com> Date: Tue, 28 Jun 2016 09:42:27 +0200 From: Ivan Radovanovic User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130812 Thunderbird/17.0.8 MIME-Version: 1.0 To: Russell Haley CC: Freebsd-mono , freebsd-ports@freebsd.org Subject: Re: Latest MonoDevelop Progress References: <576EC008.9060109@innolan.dk> <20160625185613.4698194.7455.7812@gmail.com> <576EFC4A.9020000@innolan.dk> <20160627121104.GA59506@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 07:42:31 -0000 On 06/27/2016 18:10, Russell Haley napisa: > ... > patches, instead of doing it through svn patches. It will make > everything WAY easier to push back upstream. Not that it matters, eh, > Ivan? :0) > I already see who is to be in charge of pushing everything upstream :-P From owner-freebsd-ports@freebsd.org Tue Jun 28 07:48:20 2016 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 AC927B85D07; Tue, 28 Jun 2016 07:48:20 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 54F18213D; Tue, 28 Jun 2016 07:48:20 +0000 (UTC) (envelope-from radovanovic@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id r201so14343907wme.1; Tue, 28 Jun 2016 00:48:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=7cVa9ZcDWRxTgteJaWb2VUt89aE8mBB5NZy4ZTcqcMM=; b=uRgpVhWNK9ua5l6SqXMoaceblj4q9dEVqbYEJ68hg3EdOsTpjcBhUq7RrLhnk8DaFW kbuuxjILaZ2BHfQcifLCah3RAl9RYNQhz2RCCQ+wajQqqE36K4xQ2gaIOpAUCcVekqw5 SWSXs2y3p7egWpm2tfRqyJ4ACQzNg4P3irOTgeslJ2caCxZ6ji9f/0Q++jaJ8AOukJ8A GEc5R4nDAPSceOlYPKWcgHKPl6Too4FLQAlV8Ltjm9P5DAiHgbryRgblVRFv2thCFa0/ b8hplDigzaZoAL5FLPcAgxC9G64QmNjVhYVmFwtzO2RMT+nin00N5lCoVkKk+29twE+K zR5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=7cVa9ZcDWRxTgteJaWb2VUt89aE8mBB5NZy4ZTcqcMM=; b=Kx7QEONs9FRTI+tOyl/B+dzlHQq4OjGUEURvfcv8uIT5PbDZ37vdWumijdIhqAYh61 bv5A0FgdKFzhFhcqBqKAyNrs2yqhFJK4qi5StmN8egpHbJCaQLCXTHdXdfuyvtiiM8Yy 6qFs6rrYPPP8dhgUwaH/9N75N2PzwgFf7itfzRWxrKt0biRmjJbc+GjH2/MWHh+qGTz0 ZcKvCnHZtx57jAJeiNrVtvGJs/S2VnYjjNWNaUSIUfcO1GXnfuX0GGVWnJV/O2h1KVzU 8TacnSsK7gY2cZDlQRzPuDu52zXlFJM992rQsG+VecN12ckMb/DEoQOiAlemDYMSzwMb ICbQ== X-Gm-Message-State: ALyK8tKFkeWkh6kAjXzoETeLpiptUYF6jTjkR74JkHJ4i0hcZs56oX8BblqP+Uv9rLYQ3A== X-Received: by 10.28.54.134 with SMTP id y6mr13891669wmh.96.1467100098944; Tue, 28 Jun 2016 00:48:18 -0700 (PDT) Received: from zmaj.softwarehood.com (178-221-67-149.dynamic.isp.telekom.rs. [178.221.67.149]) by smtp.googlemail.com with ESMTPSA id b4sm5691252wjd.16.2016.06.28.00.48.18 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 28 Jun 2016 00:48:18 -0700 (PDT) Message-ID: <57722BC1.5050307@gmail.com> Date: Tue, 28 Jun 2016 09:48:17 +0200 From: Ivan Radovanovic User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130812 Thunderbird/17.0.8 MIME-Version: 1.0 To: Kurt Jaeger CC: Russell Haley , Freebsd-mono , freebsd-ports@freebsd.org Subject: Re: Maintaining mono/.net References: <20160627182124.GA79889@home.opsec.eu> In-Reply-To: <20160627182124.GA79889@home.opsec.eu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 07:48:20 -0000 On 06/27/2016 20:21, Kurt Jaeger napisa: > Hi! > >> A couple of us on the freebsd-mono@ mailing list are having a >> discussion on how best to maintain the mono ports/.net ports. One of >> the things that has come up is maintaining the patches for "all this >> stuff". The current paradigm in FreeBSD as I understand it is to use >> the files directory and apply the patches to the port via svn/ports >> tree. However, with the ubiquity of GitHub in opensource, it now seems >> to be feesable to simply create a Github accound to maintain a bunch >> of forked repositories (which is essentially a patched git >> repository!). > > From my point of view, while not perfect, it sounds reasonable. > We are open for all (good) ideas (good in sense: easier to use, requiring less effort to maintain patches) :-) From owner-freebsd-ports@freebsd.org Tue Jun 28 08:20:51 2016 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 453D4B8596B for ; Tue, 28 Jun 2016 08:20:51 +0000 (UTC) (envelope-from kpg@caomhin.org) Received: from zoidberg.compliantgroup.com (zoidberg.compliantgroup.com [94.23.207.160]) by mx1.freebsd.org (Postfix) with ESMTP id 1720B2459 for ; Tue, 28 Jun 2016 08:20:50 +0000 (UTC) (envelope-from kpg@caomhin.org) Received: from thoth.home (host86-191-17-32.range86-191.btcentralplus.com [86.191.17.32]) (Authenticated sender: master@caomhin.org) by zoidberg.compliantgroup.com (Postfix) with ESMTPSA id 5301A14D2FB for ; Tue, 28 Jun 2016 10:12:57 +0200 (CEST) Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: freebsd-ports@freebsd.org Subject: Re: blanket portmgr approval vs. non-fixing changes References: <201606272021.u5RKLVhQ057899@slippy.cwsent.com> Date: Tue, 28 Jun 2016 09:12:46 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Kevin Golding" Message-ID: In-Reply-To: <201606272021.u5RKLVhQ057899@slippy.cwsent.com> User-Agent: Opera Mail/1.0 (Win32) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 08:20:51 -0000 On Mon, 27 Jun 2016 21:21:31 +0100, Cy Schubert wrote: > In message <57716D89.1050108@sorbs.net>, Michelle Sullivan writes: >> Don't forget that many people see their name/email in the maintainer >> line as being responsible for the port.. so someone goes makes blanket >> changes which actually breaks stuff.. that reflects on the person in the >> Maintainer line - whether you want it to do so or not, whether you >> believe it or not.. > > I think it's more than the maintainer perceives that they're responsible. > Getting that email from freebsd-pkg-fallout I think there was and maybe > still is a general impression that is had. I for one take the attitude, > you > break it, you fix it and I don't hesitate to email any committer who > made a > blanket change that broke something. It's only fair because fixing > breakage > caused by others also takes away from other productive work and projects, > as some of us do have time constraints and time pressure due to other > commitments. I think it goes beyond just breakages though. Recently I had a couple of ports to update so I made sure my tree was current first thing in the morning, I went through and updated. Then I ran all the build logs etc. submitted my patches to bugzilla - and about the same time someone did a blanket update of RUN_DEPENDS in my ports. Including a PORTREVISION bump. It's easy to argue that's a very trivial change that doesn't needs maintainer involvement, but it also impacted my day. So I updated my tree again and did the whole process again which was inconvenient, but I also found myself cringing at any users of the port perhaps updating on the PORTREVISION and then a couple of days later when my more complete update was committed having to do it again. I thought it looked bad as I was obsoleting the patches and build logs I submitted a couple of hours earlier too. Had I known about the blanket update I could've rolled that into my updates or something, but it was just suddenly there. There was no public warning of that change coming (and I did search the relevant lists just to make sure I hadn't missed something). Luckily my ports are mostly trivial so the actual impact was fairly low, but it still annoyed me and made me feel that it made me look bad. It still took extra time to do these simple updates, especially once I started wondering what I'd missed to not catch this beforehand. I felt rather lucky that I'm quite a low volume maintainer in that regard because it could've easily sucked up a lot more of my time. On the flipside blanket updates will logically come from people who give far more time to this stuff than me. Will they be happy with having to jump through hoops for the likes of me? If I'm unhappy about the extra time this caused me maybe I'm being unfair in asking them to spend time checking for pending updates before doing something. Maybe I just need to suck it up and let the big players do their thing. -- Kevin From owner-freebsd-ports@freebsd.org Tue Jun 28 09:17:13 2016 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 B9C8EB73A88 for ; Tue, 28 Jun 2016 09:17:13 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4662F2109 for ; Tue, 28 Jun 2016 09:17:13 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id a66so17907427wme.0 for ; Tue, 28 Jun 2016 02:17:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=q6OYVeFKFY9EbprYqzFGG1Xx8K+aWaVrR8IpMHKdgJs=; b=XMVULyBKqcqalFzYKw/PyvsNtmK/mdXv+vjYbjRPcQeCjRWX6pew53vmvVJw+tg0db KCsvITRFyKq2iedqmF6PvYoyqF1aeEgjJZOtn4KsnU+zzCh8LlcK0yTTkvXwSdmucc8P 0LbuGjG6ELfYKK0WJ6gq7dsLoVlTPqrSx0HndR+sOqaKb8pGrq/Haszoy9xyRr8MYTBt E6z5CggsxNTw93Q+png8ywn51zB3vCjHSl7dWMSn1avxNdObYgzUxhDl3DhmYTIKoVmf bjXuefItuO0g00AMFce1iJAZdy1V0UdhPMT6dItU67yB3jXGELgxgmorLJJS0l5Mib/B f+Uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=q6OYVeFKFY9EbprYqzFGG1Xx8K+aWaVrR8IpMHKdgJs=; b=iMu8zOE2FIQRyMvV93tN3rceGBod7fXaOLNbzHdn18eyriX+CZ8pwUYFvwg49thM9U zpOhiybSujnWTlJRWM0pLEHBEPBely1nrngtmZWKD9+lHJCF5wPvQU11hZXoGoJyNA0t QNh+rcHmAnilpIRmPY+2W/+afi4dYiTLFJwfGCopS5YabXr7sDuEDMwkNAnWadTzfN2t 0pbUL2jaZCY3tkWpjYESlbj8suf1Z1PiWwzaekcji4tMNFiQmrUBVVVHCA2zwCIHymlY sDKvlY8aY9chxxk0Dgcmg0z9rDT6quw8E8mzGwEy1vnHfPP3iTQ/LJkBh4Rd27su7kPh pw/g== X-Gm-Message-State: ALyK8tLLIPU8J2i13haxQSI3gzAeUeep4DPFbXarPpV3EeEyB2Q/6yl/ky+ZLI78Tnsl+Q== X-Received: by 10.194.168.225 with SMTP id zz1mr2222752wjb.114.1467105431663; Tue, 28 Jun 2016 02:17:11 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id h8sm5795865wjg.9.2016.06.28.02.17.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Jun 2016 02:17:10 -0700 (PDT) Sender: Baptiste Daroussin Date: Tue, 28 Jun 2016 11:17:10 +0200 From: Baptiste Daroussin To: Kevin Golding Cc: freebsd-ports@freebsd.org Subject: Re: blanket portmgr approval vs. non-fixing changes Message-ID: <20160628091709.pbvq7lekss2ql2en@ivaldir.etoilebsd.net> References: <201606272021.u5RKLVhQ057899@slippy.cwsent.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="umjymritqrrpj45u" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1-neo (2016-06-11) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 09:17:13 -0000 --umjymritqrrpj45u Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 28, 2016 at 09:12:46AM +0100, Kevin Golding wrote: > On Mon, 27 Jun 2016 21:21:31 +0100, Cy Schubert > wrote: >=20 > > In message <57716D89.1050108@sorbs.net>, Michelle Sullivan writes: >=20 > > > Don't forget that many people see their name/email in the maintainer > > > line as being responsible for the port.. so someone goes makes blanket > > > changes which actually breaks stuff.. that reflects on the person in = the > > > Maintainer line - whether you want it to do so or not, whether you > > > believe it or not.. > >=20 > > I think it's more than the maintainer perceives that they're responsibl= e. > > Getting that email from freebsd-pkg-fallout I think there was and maybe > > still is a general impression that is had. I for one take the attitude, > > you > > break it, you fix it and I don't hesitate to email any committer who > > made a > > blanket change that broke something. It's only fair because fixing > > breakage > > caused by others also takes away from other productive work and project= s, > > as some of us do have time constraints and time pressure due to other > > commitments. >=20 > I think it goes beyond just breakages though. Recently I had a couple of > ports to update so I made sure my tree was current first thing in the > morning, I went through and updated. Then I ran all the build logs etc. > submitted my patches to bugzilla - and about the same time someone did a > blanket update of RUN_DEPENDS in my ports. Including a PORTREVISION bump. > It's easy to argue that's a very trivial change that doesn't needs > maintainer involvement, but it also impacted my day. >=20 > So I updated my tree again and did the whole process again which was > inconvenient, but I also found myself cringing at any users of the port > perhaps updating on the PORTREVISION and then a couple of days later when= my > more complete update was committed having to do it again. I thought it > looked bad as I was obsoleting the patches and build logs I submitted a > couple of hours earlier too. >=20 > Had I known about the blanket update I could've rolled that into my updat= es > or something, but it was just suddenly there. There was no public warning= of > that change coming (and I did search the relevant lists just to make sure= I > hadn't missed something). Luckily my ports are mostly trivial so the actu= al > impact was fairly low, but it still annoyed me and made me feel that it m= ade > me look bad. It still took extra time to do these simple updates, especia= lly > once I started wondering what I'd missed to not catch this beforehand. I > felt rather lucky that I'm quite a low volume maintainer in that regard > because it could've easily sucked up a lot more of my time. >=20 > On the flipside blanket updates will logically come from people who give = far > more time to this stuff than me. Will they be happy with having to jump > through hoops for the likes of me? If I'm unhappy about the extra time th= is > caused me maybe I'm being unfair in asking them to spend time checking for > pending updates before doing something. Maybe I just need to suck it up a= nd > let the big players do their thing. >=20 What you are asking is part of the blanket in particular when changing thin= gs in individual ports, we expect committers to have a look at pending PR (yes I = know I have been guilty of individual port change without sometime checking about pending PR which was wrong from my side) For sweeping changes this is a bit different as when a change touches a lar= ge portion of the tree we can not expect the committer to have a look at each individual ports. Best regards, Bapt --umjymritqrrpj45u Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXckCLAAoJEGOJi9zxtz5aNUYP/2bw0SP65gJ0tECLGACygQ6t RxSN2DGGokxFczPUYKJGnBDlT2kKAHzml7e0C6rysqfMc69FAjhHJRDIuaa+vJFr 80q9DtHKPQIqkbRiSdp+RJI2s6ICD5S4AJArEsfMBhJX4gTtJ+IbJDbq1Zc6nDBl BYooRbxl8rLISoz9cFNgPdcQY82+RHx9GQrhLrojPTH/QPzqiIO0AwfVwbWdYisN E70D0W5CmqB1miJ/bHmLxepSfvE/ihGPJwkZy0cSGIa4cHlmVmHibjxG8NckEIOY lckzYuWstubiwkJoJFcosu4Z0XnUA52GGj+qSsF7yzq5XSmL2KAVKI3GxcFG1xII zJRyxEmdao6gq2Q0Lk7wn/vP0JNecYHNgyDrSQvqcRKjgaLiv8Mj2CIClyV6KSS8 lCCloxR3nroAZsWupHYuffkM+qFhzlsF9jrQfjWyHpMjAnmIbeowgzfLtqsvKqxL dSX/C//8q2xNJWcvjuPUaJlqQTFjZEOiuNt8U0p9yxDbSWZ1HxflAKxDOeicpZVW ajSpClOcFnJX7fXwK0uGTY4eZHI/02qP75qs+LyseTSYXwm8xBhCDtnuuAuqnA6c CS+56CUd7brOhMGS5/Y2HKn+5IMckekwvxMEJ25EqZbz7Ka9EkVxlGkqeh7VQJ5z lkiVrgf4aufd+9zptbaL =yw7O -----END PGP SIGNATURE----- --umjymritqrrpj45u-- From owner-freebsd-ports@freebsd.org Tue Jun 28 09:43:11 2016 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 AB3AFB84379; Tue, 28 Jun 2016 09:43:11 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5131821D1; Tue, 28 Jun 2016 09:43:11 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id v199so131796952wmv.0; Tue, 28 Jun 2016 02:43:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=feRSMkw+tcrlXhLAc704lKVZK19HJD8kptxUq5e5k5c=; b=RtwcNSmRl8EjlkVCQD9VFf5N6EJnPFSvkm1RUUvrW699LMA7Q0uvIQwlS49pP4HqCp Dzmmm/S9e5u0DeneSM2Xk0hDgJfrzNNPgPzPvyh2TiogyFRGoQQhzWQwQsqU+Ne64yiP h5mJpkZHY+Wzy5zPa1beBtlMFHoZCXvL7P3+hi+FVxOnwKDExdG63Vvbp9gsad1ZoAOO m9yjXX+bqLkfHFfWNuxxYUNZ5cH2hWDIAMEEOWkCpJY+SwqjILWvcWXOEG5F81CY8I2p U6T7wffGxFIUsB8ytL9N8elbiV27WCV+GjI53Z8LfLYqPRzdogyesw2LwB5VVOC7hUYB 5cjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=feRSMkw+tcrlXhLAc704lKVZK19HJD8kptxUq5e5k5c=; b=L+IU/tUjPHFC4SaZD9Lot/ak7XP9xaAlspLyKt4dqhK7MkoZwBLtLJ+TyoUGH3ZmG4 V3TIePpQmuGkfsN785JHJE7MTkGlWSfRwdZ7CX5qBioil9ZKq+a+VyIWktCCee0fgrqG 03MJn+qTcUq29vUT5rj+ELsiwphsQGgYUyPHM48WpWKOhOO89K0D2EWU45j5Nm8ccQXp 0/mttHFSiCgEDTUsH057XkWKIAlUtEQA4aNA29XpRSB/BhV0oQatQr4TnVp77ABmBYt6 BlU/IzNyh/yklJICzfhK1fJ20I8wG701cw9QjbpMLXoGV/ypr6dOTcqRuluaB3SS7GJE 3ntA== X-Gm-Message-State: ALyK8tLvU+UYg1az5cG4E+qc8XIxY1HEyRrk2KikvF7wThAYlOZI8PFntHCNtTjQ7j7R9w== X-Received: by 10.194.200.164 with SMTP id jt4mr2148486wjc.18.1467106989885; Tue, 28 Jun 2016 02:43:09 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id x83sm6161373wmx.9.2016.06.28.02.43.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Jun 2016 02:43:08 -0700 (PDT) Sender: Baptiste Daroussin Date: Tue, 28 Jun 2016 11:43:08 +0200 From: Baptiste Daroussin To: Russell Haley Cc: freebsd-ports@freebsd.org, Freebsd-mono Subject: Re: Maintaining mono/.net Message-ID: <20160628094307.bepxy46dp5igizeh@ivaldir.etoilebsd.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="lixkatwcgx7j2zrq" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1-neo (2016-06-11) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 09:43:11 -0000 --lixkatwcgx7j2zrq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 27, 2016 at 11:06:02AM -0700, Russell Haley wrote: > Hello Ports Team, >=20 > A couple of us on the freebsd-mono@ mailing list are having a > discussion on how best to maintain the mono ports/.net ports. One of > the things that has come up is maintaining the patches for "all this > stuff". The current paradigm in FreeBSD as I understand it is to use > the files directory and apply the patches to the port via svn/ports > tree. However, with the ubiquity of GitHub in opensource, it now seems > to be feesable to simply create a Github accound to maintain a bunch > of forked repositories (which is essentially a patched git > repository!). This makes it easier to create and apply patches and > gives us the natural path to push things back upstream. In the end, we > would just pull from the FreeBSD specific repository, which is no > different than, say, pulling from the mono project directly. >=20 > This email is a request for response from anyone on the ports team (or > FreeBSD general) to give some input as to the acceptability of this > solution, as well as any "gotchas" we haven't thought of yet. Thanks > in advance! >=20 There are absolutely nothing against this. Actually some ports were already doing that before the github era :D The only difficulty the history told us is : when active people get less ac= tive for various reasons you need to make sure enough people continues to get ac= cess to the said repo. Tracking upstream updates because more complicated for people not in the te= am (we already saw in the past ports stucked for more than 5/6 years actions b= eing taken (maintainer of the forked becoming mostly MIA) It also depends how many patches you end up with, I haven't checked the mono/.net ports but if that is just a bunch of small patches then the overh= ead is not worth the pain, if there are lots of patches then sure maintaining y= our repo is simpler. Depending on how active you (the team) are and how close to the upstream yo= u are one can also see those repositories as "temporary" until all the amount of patches are upstreamed and when done the ports can switch back to the offic= ial distfiles (this is always a goal for ports upstreaming all our patches so w= e can remain as close as possible from the vanilla sources) That said I do applause the effort. As a conclusion do what ever you think = is the easiest mechanism for you as long as things like monodevelop and friend= s can be pushed in a working state again. Best regards, Bapt --lixkatwcgx7j2zrq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXckS3AAoJEGOJi9zxtz5aeW0P/RUw/RMiHuzD7zqCUKi0hunG 8aIxGweJcqDtR30OFvi9WVQyck0t9MXEfa008NIo4yXx8xawdyPmy8mO1G/Xm9aK bSIcIt9scnPp/K0u8sEC1/e20NqUep6+THRxOGyoUZdI88FXnWF3oWAvXV17ENZA lXdhcFDtoZRe8Zp6gCgxMnwoxhAZ5aiZMNRMf8jHyPAWBomnguHaxF1w4kG5vMIN 4+FHy0OmCmDrWPVnnB/kZkikqHanRwLCnrFvfAjGeZGsnNaI9HTXjuK7gDgPAZ+7 c7eWGRGF/2nAGsiEXvyuT8zj3zzng2lSAbrcEJLNtRX9hA+vXKQTnOfBjVWIVm3D cjiKYSw22PqPYQk6eegtVu9YRFjhtqgqFMakHju5IHN/mfR63g62upJRIast8B4W cXTg8ddYejUBdOPqwk/ySSNTq9WOYZ4kniw3JnmlO0BrK7p5R7nRy5lexJ3oI/lW MOpkZqKPLhusV2eM8fE5WXbjxa1nCYJ35WdkBjTFhcVs3unRJ12A10AJVHXo1CWL 5Jsp6fy+mSe0KCIbQADFbnAXz7ZBy7zzZqXF4fboRkin3XdMg8radPdPQ8F8e6Ty Ty91R59NqZ0dG1rFXHFEvEFW3VBlAUn6u9acbRY+H/uv7SKulx6zQZ4zTbV64Uam 4KtWFVBwudFH6eVnWXqD =FNbm -----END PGP SIGNATURE----- --lixkatwcgx7j2zrq-- From owner-freebsd-ports@freebsd.org Tue Jun 28 10:16:27 2016 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 44D08B84C3E for ; Tue, 28 Jun 2016 10:16:27 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 F1DC22FA2 for ; Tue, 28 Jun 2016 10:16:26 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 23B5228428 for ; Tue, 28 Jun 2016 12:16:18 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 6751C28438 for ; Tue, 28 Jun 2016 12:16:17 +0200 (CEST) Message-ID: <57724E71.4030600@quip.cz> Date: Tue, 28 Jun 2016 12:16:17 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: How to change repository name of installed packages in local database? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 10:16:27 -0000 I searched the man pages but cannot find the answer. If we have machine with packages installed from more than one repository and one day we want to use some already installed packages from another repository, is there any easy way of switching this packages to another repo? I am looking for something similar to "pkg set" but we do not want to change package name or package origin but package repository information recorded in sqlite. Example: # pkg query '%R %n' | sort codelab libiconv codelab mariadb55-server codelab p5-Error codelab p5-Term-ReadKey codelab p5-subversion codelab pkg-rmleaf codelab unzip codelab vim-lite redmine320 ImageMagick-nox11 redmine320 ca_root_nss redmine320 curl redmine320 expat redmine320 fontconfig redmine320 freetype2 redmine320 indexinfo .. .. Now we need to switch all packages from testing repo "redmine320" to production repo "codelab". Is there any other way instead of manual deinstall and reinstall of all those packages? Miroslav Lachman From owner-freebsd-ports@freebsd.org Tue Jun 28 10:28:58 2016 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 97F1AB84ECA for ; Tue, 28 Jun 2016 10:28:58 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.kissl.de (host64.kissl.de [213.239.241.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "*.shmhost.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6205425D5 for ; Tue, 28 Jun 2016 10:28:57 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.homeoffice.local (dslb-092-078-013-119.092.078.pools.vodafone-ip.de [92.78.13.119]) (Authenticated sender: web104p1) by host64.kissl.de (Postfix) with ESMTPSA id AC65567F5B; Tue, 28 Jun 2016 12:21:25 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: How to change repository name of installed packages in local database? From: Franco Fichtner In-Reply-To: <57724E71.4030600@quip.cz> Date: Tue, 28 Jun 2016 12:21:25 +0200 Cc: freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <64C2D51B-E357-4882-A500-A37A3D570669@lastsummer.de> References: <57724E71.4030600@quip.cz> To: Miroslav Lachman <000.fbsd@quip.cz> X-Mailer: Apple Mail (2.3124) X-Virus-Scanned: clamav-milter 0.99 at host64.kissl.de X-Virus-Status: Clean X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 10:28:58 -0000 > On 28 Jun 2016, at 12:16 PM, Miroslav Lachman <000.fbsd@quip.cz> = wrote: >=20 > Now we need to switch all packages from testing repo "redmine320" to = production repo "codelab". # pkg annotate -A ${PKG} repository ${REPO} Cheers, Franco= From owner-freebsd-ports@freebsd.org Tue Jun 28 10:33:20 2016 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 408A9B8510A for ; Tue, 28 Jun 2016 10:33:20 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D0B352A98 for ; Tue, 28 Jun 2016 10:33:19 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id v199so133590401wmv.0 for ; Tue, 28 Jun 2016 03:33:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=EvIpQuB/Q0qL6CgBBBCJDhvpTjxXA2abFw6ks1VQTAg=; b=X0gngmrRjKv6gfG9UGn27dJ/AbjHIGwQkJM2qEmDIIFblun69LAqKnqAi9qpJDYMG2 Dasl0gu0NjLwQZb8Kp7iAmdAuv8v+QnJvsWCuG+RF3na/tCa9OiwHDfiXfezUjylL8sa fqwpQmmvEBhQPv14UfPzmUaaKnRJ1nogBDb0+wuGBjn7N21mrc9pSU76sViHFeZZSlGP i7W8OBMP04jqWFdPOoLOZ423C/jmZjEfvkJGtZP2aFTiIoMqSOmaAa33mtK23nAQWhmn Dn6636LWrE+UfYB7cLxcnKPaq8d/BEbi43++sCJtbem2J27Y46Ey61zNYNxcYOxpfIAF C7Ag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=EvIpQuB/Q0qL6CgBBBCJDhvpTjxXA2abFw6ks1VQTAg=; b=jrcPId1kx/ztSD5QVHwnP9MZxXlDJur+ao9tHUlFgH4/XrZHBLbjCny6n9pImvS4BQ C1J4Psx0S98pt+Rvm1ZCwmURzFfrO+VUGeRNU7Tl7xbWNul3pxBu1ZPlHu37NV4UreYR mNexZeqEM5IOUR54tG5MxzSVL4socqw6wNCdJzOob0oLcQK9e/8eTK9IsP7ipx9Y2/Uc pEr2ucBDWMrtx6TsA1lOtVI1SeZQLApLgy+vIHJ2ANDjhSYJlkIbrRXHB5GAa5iBkStp Z4xGryQBFNv8ylpKTn5OHTZwk+tgeeJmS0nyuFrzO3WPUUUqbB/952uDf9KCXyS+9C/N NqvA== X-Gm-Message-State: ALyK8tLRkvDxIvcZil660GOpf45s8C318jbwQkKv20KVXPaAPHqhd9zzW6Kkitw8+nV5eA== X-Received: by 10.194.114.42 with SMTP id jd10mr2226596wjb.88.1467109998383; Tue, 28 Jun 2016 03:33:18 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id v70sm3157935wmf.18.2016.06.28.03.33.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Jun 2016 03:33:17 -0700 (PDT) Sender: Baptiste Daroussin Date: Tue, 28 Jun 2016 12:33:16 +0200 From: Baptiste Daroussin To: Miroslav Lachman <000.fbsd@quip.cz> Cc: freebsd-ports@freebsd.org Subject: Re: How to change repository name of installed packages in local database? Message-ID: <20160628103316.zabg6oipxqnfge3f@ivaldir.etoilebsd.net> References: <57724E71.4030600@quip.cz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="zxbtvtp2f5bhoz6t" Content-Disposition: inline In-Reply-To: <57724E71.4030600@quip.cz> User-Agent: Mutt/1.6.1-neo (2016-06-11) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 10:33:20 -0000 --zxbtvtp2f5bhoz6t Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 28, 2016 at 12:16:17PM +0200, Miroslav Lachman wrote: > I searched the man pages but cannot find the answer. > If we have machine with packages installed from more than one repository = and > one day we want to use some already installed packages from another > repository, is there any easy way of switching this packages to another > repo? > I am looking for something similar to "pkg set" but we do not want to cha= nge > package name or package origin but package repository information recorded > in sqlite. >=20 > Example: >=20 > # pkg query '%R %n' | sort > codelab libiconv > codelab mariadb55-server > codelab p5-Error > codelab p5-Term-ReadKey > codelab p5-subversion > codelab pkg-rmleaf > codelab unzip > codelab vim-lite > redmine320 ImageMagick-nox11 > redmine320 ca_root_nss > redmine320 curl > redmine320 expat > redmine320 fontconfig > redmine320 freetype2 > redmine320 indexinfo > .. > .. >=20 > Now we need to switch all packages from testing repo "redmine320" to > production repo "codelab". >=20 > Is there any other way instead of manual deinstall and reinstall of all > those packages? >=20 # remove the "repository" annotation pkg annotate -D expat repository # add the new one pkg annotate -A expat repository codelab For convenience we could allow to overrite an existing one, but we do not y= et Best regards, bapt --zxbtvtp2f5bhoz6t Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXclJsAAoJEGOJi9zxtz5aQo0P+gI2zHKEi/BXarc20Rq5zDU7 OZKD2Uw+3svVjDS7gR2+AzzgUFphkHKxMhb34z7x9yxlOYuZ2nRPbXlj67kl9N3P /XDN+fhTOVFbR8QJfH+hqIy7pEc31FmudzGR8LxkEG4fi7nL3fVE2woufT6p5wTT iUuwTXYl5t8uL9DuF4XWDBqFH7KlGfn2y16gdus/7d1frN9/Wy1wrwh2KJ6YthjB qv0u4bxYLAteyy0lUatnqsOlj6XSLu7sEAzR6EkF2jF+ZqUrqCORTwNyevBv19QB JcFjCl/xAYJxtt9Jl36U5uhfOBWoHjlZfXaJtXeme1EsQpcCUpXp0Y/hvpMb4fW8 BFJGPey0FrlsxDtcXour8E3O/G470OEyq8XVRiYYIv9slPScJl3t1S7QMu+Ip76p cN1brxLLcaM4TmLgVelu69W9JKVkhg4Rf3XPuFBlVM1MXYUMip5r6dzI0LWg30Ok pOHmNvaHVUlFnUibmW2RZ4PpRFyWmzluuU9iYHQLE7M2mmNNgv9hmJUuZiX3klfC pw2QK+XSgRa9Ed8wgaliO3fJVQpbxhlK4bcIJ3m0T32v+rxzU3v8NQfVk1bX7w77 B3I2aLa5eAtuiLgAeUoZ9QepOPdIlA5jS06P7W4PDhNyvNVOT6lK6P0Qa0rMfRNN RG1oCWWlSjcH93QQWjES =umgN -----END PGP SIGNATURE----- --zxbtvtp2f5bhoz6t-- From owner-freebsd-ports@freebsd.org Tue Jun 28 10:51:23 2016 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 0288BB8543E for ; Tue, 28 Jun 2016 10:51:23 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 659572156; Tue, 28 Jun 2016 10:51:22 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id B7F0928435; Tue, 28 Jun 2016 12:51:19 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id E951A28429; Tue, 28 Jun 2016 12:51:18 +0200 (CEST) Message-ID: <577256A6.6020303@quip.cz> Date: Tue, 28 Jun 2016 12:51:18 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Baptiste Daroussin CC: freebsd-ports@freebsd.org Subject: Re: How to change repository name of installed packages in local database? References: <57724E71.4030600@quip.cz> <20160628103316.zabg6oipxqnfge3f@ivaldir.etoilebsd.net> In-Reply-To: <20160628103316.zabg6oipxqnfge3f@ivaldir.etoilebsd.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 10:51:23 -0000 Baptiste Daroussin wrote on 06/28/2016 12:33: > On Tue, Jun 28, 2016 at 12:16:17PM +0200, Miroslav Lachman wrote: >> I searched the man pages but cannot find the answer. >> If we have machine with packages installed from more than one repository and >> one day we want to use some already installed packages from another >> repository, is there any easy way of switching this packages to another >> repo? [...] >> Now we need to switch all packages from testing repo "redmine320" to >> production repo "codelab". >> >> Is there any other way instead of manual deinstall and reinstall of all >> those packages? >> > > # remove the "repository" annotation > pkg annotate -D expat repository > > # add the new one > pkg annotate -A expat repository codelab > > For convenience we could allow to overrite an existing one, but we do not yet Modification with pkg annotate -M works for me! # pkg annotate -M rubygem-web-console repository codelab rubygem-web-console-2.3.0: Change annotation tagged: repository to new value: codelab? [y/N]: y rubygem-web-console-2.3.0: Modified annotation tagged: repository # pkg annotate -S rubygem-web-console repository rubygem-web-console-2.3.0: Tag: repository Value: codelab I switched all repo "redmine320" packages to repository "codelab" with following command (not so elegant) # pkg query '%R %n' | awk '$1 == "redmine320" { print $2 }' | xargs -L1 -J % pkg annotate -y -M % repository codelab Thank you Bapt and Franco! Miroslav Lachman From owner-freebsd-ports@freebsd.org Tue Jun 28 11:03:39 2016 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 70367B85981 for ; Tue, 28 Jun 2016 11:03:39 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from mail.skysmurf.nl (spectrum.skysmurf.nl [83.162.175.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.skysmurf.nl", Issuer "mail.skysmurf.nl" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F3EAE2CAD for ; Tue, 28 Jun 2016 11:03:38 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from spectrum.skysmurf.nl (mail.skysmurf.nl [192.168.42.4]) by mail.skysmurf.nl (8.15.2/8.15.2) with SMTP id u5SB3MeW052582; Tue, 28 Jun 2016 13:03:22 +0200 (CEST) (envelope-from freebsd@skysmurf.nl) Received: by spectrum.skysmurf.nl (sSMTP sendmail emulation); Tue, 28 Jun 2016 13:03:22 +0200 Date: Tue, 28 Jun 2016 13:03:22 +0200 From: Alphons van Werven To: Kevin Golding Cc: freebsd-ports@freebsd.org Subject: Re: blanket portmgr approval vs. non-fixing changes Message-ID: <20160628110322.GA51760@spectrum.skysmurf.nl> References: <201606272021.u5RKLVhQ057899@slippy.cwsent.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LZvS9be/3tNcYl/X" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.skysmurf.nl/~fonz/fonz_pubkey.asc User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 11:03:39 -0000 --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Kevin Golding wrote: > and about the same time someone did a blanket update of RUN_DEPENDS in > my ports. Including a PORTREVISION bump. It's easy to argue that's a > very trivial change that doesn't needs maintainer involvement, but it > also impacted my day. [snip] > Had I known about the blanket update I could've rolled that into my > updates or something, but it was just suddenly there. There was no > public warning of that change coming Maintainers are already notified by e-mail of commits resulting from PRs because they are put on the CC list. Maybe it's just me, but I think it would be very nice if maintainers were *always* automagically notified of *any* commits to their ports, including those subject to blanket approval. With any luck, such notifications are received in time to prevent (or at least limit) wasted time such as in the above case. Moreover, keeping maintainers informed also eliminates having to wonder "Ey, what's this 'ere then?" the next time they look at their ports. And finally, I'd surmise it would also help keeping maintainers abreast of developments in the ports infrastructure in general. I know that the PR notifications come from BugZilla and not from SVN, so what I don't know is how feasible it is rig up something like this, but I do know that I for one would quite appreciate something along these lines. Fonz (bla bla bla, something about two cents, bla bla bla) --=20 A.J. "Fonz" van Werven mailsig: Ob technicas difficultates, lux in fine cuniculum non operatur. --LZvS9be/3tNcYl/X Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJXcll6AAoJEAfP7gJTaCe83FYQAMmru5vp6HBPp+nXfA4MFKZX jvAL4rcyngCvpHMsPLMBIJaX6fRD5eK7YJuEG+jXdxe91L59a1/m4cdD+xiQxn05 fAvVzrtSu+kuhYbn+z6lB8/Y9L7qZLGrZdbHvNuPUSOJHmC/eqDkGICz97SDJxJo GLYh7mMdyprtVr3NZ84DEJCYXkl3eKQ7G+k62AfDvTaKb/3n7oP9YKBmNhQ/CmrO IQ6nudv0umHvjxoHtbRvGbY8hwfaamLjeDbZftT80zIOGQRpqxWPXwpCrOI3jRPV NtjFv9ohyGu3xVW49Dvz65T1AFCIj8oLq6GQQECGgvy6WKNbYfzjtciiS1272T7M FCpOF5gqQ+OriBhSF/TkKxmwDm22Fw76ncieaDrHxTG7qEdFQ8YScqH8SWQhxdaK sV14ORE2A/38NNL29KDS7L/GKqumqOeC4GuzVYGAdDpsUr38YrwNr1MVxywsCXU9 pXBFyyYsaZMP2wV32+LIEMPk5b35Qgp9Wm3/ugwP/CtHGRaN2WmLLntVACapUAMJ Cr8qjhMnncwXdDeZfJSdr/bg0SRdXe1h8lxykqYt71S59Dx7muFqykrhspNwjCOp xZtCyCU1hqSsXNOcQBuJ/7wns6StPoUCcuhAzCD6gjQfgbmM4+NIbbpKaC+tBLO9 0156NkzemiNmK+GzpnU9 =yMf4 -----END PGP SIGNATURE----- --LZvS9be/3tNcYl/X-- From owner-freebsd-ports@freebsd.org Tue Jun 28 11:44:41 2016 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 42D32B84588 for ; Tue, 28 Jun 2016 11:44:41 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 EA5C9223C for ; Tue, 28 Jun 2016 11:44:39 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id u5SBiXeH026842 for ; Tue, 28 Jun 2016 11:44:33 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id u5SBiXib026841 for freebsd-ports@freebsd.org; Tue, 28 Jun 2016 04:44:33 -0700 (PDT) (envelope-from david) Date: Tue, 28 Jun 2016 04:44:33 -0700 From: David Wolfskill To: freebsd-ports@freebsd.org Subject: Unexpected output from "pkg updating -d 20160626" Message-ID: <20160628114433.GF1358@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="AnSJTMMZ92c40QA7" Content-Disposition: inline User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 11:44:41 -0000 --AnSJTMMZ92c40QA7 Content-Type: multipart/mixed; boundary="5uhzMJlTksuFv+PE" Content-Disposition: inline --5uhzMJlTksuFv+PE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable As part of my daily update of FreeBSD on my laptop, on the first reboot after installing the freshly-built kernel & world, I use portmaster to update any installed ports that have been updated since I last updated. This morning, for the first time in ... months, I think, the "pkg updating -d ..." command I run to start the process actually generated some output -- quite a bit of it. But I'm at a loss to understand why it did: only one of the ports it mentioned is installed, and that one didn't get updated by "portmaster -ad"; the others aren't installed at all. My ports working copy is ports/head, at r417708. I'm running: FreeBSD g1-252.catwhisker.org 10.3-STABLE FreeBSD 10.3-STABLE #406 r302244= M/302246:1003505: Tue Jun 28 04:11:52 PDT 2016 root@g1-252.catwhisker.o= rg:/common/S1/obj/usr/src/sys/CANARY amd64 now; when I ran "pkg updating -d ...", I was running: FreeBSD g1-252.catwhisker.org 10.3-STABLE FreeBSD 10.3-STABLE #405 r302220= M/302222:1003504: Mon Jun 27 04:03:47 PDT 2016 root@g1-252.catwhisker.o= rg:/common/S1/obj/usr/src/sys/CANARY amd64 and pkg reports: g1-252(10.3-S)[2] pkg --version 1.8.6 The "pkg updating" command I issued was: pkg updating -d 20160626 For each port in the resulting output, I ran "pkg info -o ...", with the following results: g1-252(10.3-S)[1] pkg info -o ftp/wget wget-1.18 ftp/wget g1-252(10.3-S)[2] pkg info -o databases/py-apsw pkg: No package(s) matching databases/py-apsw g1-252(10.3-S)[3] pkg info -o security/openssl\* pkg: No package(s) matching security/openssl* g1-252(10.3-S)[4] pkg info -o security/libressl\* pkg: No package(s) matching security/libressl* g1-252(10.3-S)[5] pkg info -o www/node\* pkg: No package(s) matching www/node* g1-252(10.3-S)[6] pkg info -o textproc/xmlroff pkg: No package(s) matching textproc/xmlroff g1-252(10.3-S)[7] pkg info -o databases/postgresql-repmgr pkg: No package(s) matching databases/postgresql-repmgr g1-252(10.3-S)[8] pkg info -o www/h2o pkg: No package(s) matching www/h2o g1-252(10.3-S)[9] pkg info -o security/libressl-devel pkg: No package(s) matching security/libressl-devel g1-252(10.3-S)[10] pkg info -o mail/opensmtpd-extras\* pkg: No package(s) matching mail/opensmtpd-extras* g1-252(10.3-S)[11] When I actually ran "portmaster -ad" it reported: =3D=3D=3D>>> The following actions will be taken if you choose to proceed: Upgrade pcre-8.38_1 to pcre-8.39 Upgrade bash-4.3.42_1 to bash-4.3.46 Upgrade p5-DateTime-Locale-1.04 to p5-DateTime-Locale-1.05 Upgrade p5-IO-Socket-SSL-2.027 to p5-IO-Socket-SSL-2.029 Upgrade firefox-47.0_1,1 to firefox-47.0.1,1 =3D=3D=3D>>> Proceed? y/n [y] and on completion, it reported: =3D=3D=3D>>> The following actions were performed: Upgrade of pcre-8.38_1 to pcre-8.39 Upgrade of bash-4.3.42_1 to bash-4.3.46 Upgrade of p5-DateTime-Locale-1.04 to p5-DateTime-Locale-1.05 Upgrade of p5-IO-Socket-SSL-2.027 to p5-IO-Socket-SSL-2.029 Upgrade of firefox-47.0_1,1 to firefox-47.0.1,1 Any ideas on why "pkg updating" produced such output? I have attached a copy of the actual output itself. Thanks! Peace, david --=20 David H. Wolfskill david@catwhisker.org Those who would murder in the name of God or prophet are blasphemous coward= s. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --5uhzMJlTksuFv+PE Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="pkg_updating.txt" Content-Transfer-Encoding: quoted-printable 20160627: AFFECTS: users of ftp/wget AUTHOR: vd@FreeBSD.org Wget 1.18 fixes a security vulnerability (CVE-2016-4971) and the fix introduces a backward-incompatibility for HTTP->FTP redirects. Any script= that relies on the old behaviour must use --trust-server-names in order to tru= st the HTTP response and redirect to the new filename. 20160619 AFFECTS: users of databases/py-apsw AUTHOR: rm@FreeBSD.org SQLite 3.12 completely changed the semantics of VFS.xGetLastError() in an incompatible way. This required a rewrite of the relevant C, Python and t= est code. If you implement or use this method then you have to rewrite your c= ode too. Also note that running the test suite from an earlier version of APSW against this or future SQLite versions will result in consuming all memor= y, swap or address space (an underlying integer changed meaning). 20160616 AFFECTS: users of security/openssl*, security/libressl* AUTHOR: mat@FreeBSD.org Previously, to tell the ports tree, you needed to set: WITH_OPENSSL_PORT=3Dyes =20 And if you wanted a port that was not security/openssl, you needed to add, for example: OPENSSL_PORT=3D security/libressl Now, all you need to do is: DEFAULT_VERSIONS+=3D ssl=3Dlibressl =20 Valid values are base, openssl, openssl-devel, libressl, and libressl-dev= el. 20160614 AFFECTS: users of www/node, www/node5, and www/node4 AUTHOR: adamw@FreeBSD.org node now prefers a few libraries from ports to the versions bundled with node. However, node cannot use the libssl from LibreSSL. If you are using LibreSSL as your SSL provider, you must enable the "BUNDLED_SSL" option when building node. 20160611 AFFECTS: users of textproc/xmlroff AUTHOR: hrs@FreeBSD.org The library part of xmlroff has been separated into textproc/libfo. Remove the installed xmlroff first when upgrading it because older xmlroff than 0.6.2_6 have files which libfo installs. A typical error message is the following: pkg-static: libfo-0.6.2 conflicts with xmlroff-0.6.2_5 (installs files in= to the same place). Problematic file: /usr/local/include/libfo-0.6/libfo/a= rea/fo-area.h 20160610 AFFECTS: users of databases/postgresql-repmgr AUTHOR: bofh@FreeBSD.org The port has been repocopied to databases/postgresql-repmgr2 and current post has been updated to 3.x series. If anyone is still looking forward to use the 2.x please upgrade as following. # portmaster -o databases/postgresql-repmgr2 databases/postgresql-repmgr or # portupgrade -o databases/postgresql-repmgr2 databases/postgresql-repmgr Otherwise if you want to move on with 3.x series just use # portmaster -r databases/postgresql-repmgr or # portupgrade -fr databases/postgresql-repmgr 20160605 AFFECTS: Users of www/h2o AUTHOR: junovitch@FreeBSD.org File paths no longer have a trailing / appended to them. This enables directing specific paths to a file but may break existing configurations. Refer to https://h2o.examp1e.net/configure/file_directives.html and revise your yaml config appropriately. 20160601 AFFECTS: users of security/libressl-devel AUTHOR: brnrd@FreeBSD.org The port has been updated to the latest "unstable" version of LibreSSL. The shared library versions of the libraries have been bumped. With this update, the patch for the OPENSSL_VERSION_NUMBER has been removed. This causes issues with a number of ports. Patches for many of these issues can be found on https://wiki.freebsd.org/LibreSSL/Ports#OPENSSL_VERSION_NUMBER After upgrading to 2.4.0, manually update all packages that depend on any of the libraries provided by LibreSSL (libssl, libcrypto and libtls) since the versions of these libraries have changed. Normally, you can obtain the list of dependent software by running the following command: # pkg info -r libressl-devel Then you should rebuild all ports depending on libressl-devel to avoid dangling shared library dependencies. Poudriere and pkg handle this correctly, portmaster and portupgrade users can use the following to rebuild all dependent ports. Portmaster users: portmaster -r libressl-devel Portupgrade users: portupgrade -fr security/libressl-devel 20160527 AFFECTS: Users of mail/opensmtpd-extras (any of them) AUTHOR: adamw@FreeBSD.org The invocation for extras has changed. Some extras might fail unless you pass all options/arguments separated by quotes: filter myfilter dnsbl "-c /var/chroot/dnsbl" "-h my.dnsbl.com" Additionally, extras now run in a chroot. Either pass "-C" to skip the chroot entirely (not recommended), or put all required config files, resolv.conf, and external binaries into the chroot. For example: # mkdir -p /var/chroot/dnsbl/etc # cp /etc/resolv.conf /var/chroot/dnsbl/etc And pass "-c /var/chroot/dnsbl" to the filter. --5uhzMJlTksuFv+PE-- --AnSJTMMZ92c40QA7 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJXcmMgXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4X8pgIAJWENkQ789ZuiPbr3AJzu+EX 9bsj9e8luxHU1G0rZ0ZZLPwk3akO0JMrp3dd06YkitVntPkvUO87xCOdiC+p11Vv k4oYm6WTKDVZbT4q4tlzJ0LaMmcvlL0xiVCxo9Sweko2fDS0PVIkIYzmNX/Ol0t4 sMTC2IAUDGVyramLJqHBNS/lx1KXqPf09WHzi0n6zOImuHXFBjgXUlRx/UibXP4C piiA5oAKxa4tTv+r9q+sNwIKEw3OMG4EDZ1s4O5rmzAsxQzB0C5rUQummY2xtyPw b0+GmPhFwKtf1K1HQnpEibbUyiHD3RSHnH5qlIDe46a4TuouPnnbmJ7crQQcz3U= =ML0o -----END PGP SIGNATURE----- --AnSJTMMZ92c40QA7-- From owner-freebsd-ports@freebsd.org Tue Jun 28 11:56:54 2016 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 B7942B848EE for ; Tue, 28 Jun 2016 11:56:54 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (prod2.absolight.net [79.143.243.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7F97A2953; Tue, 28 Jun 2016 11:56:54 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id CD09BBDC86; Tue, 28 Jun 2016 13:56:51 +0200 (CEST) Received: from gw.in.absolight.net (gw-ecl.in.absolight.net [79.143.241.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.in.absolight.net", Issuer "CA Cert Signing Authority" (not verified)) by prod2.absolight.net (Postfix) with ESMTPSA id B3C0EBDC80; Tue, 28 Jun 2016 13:56:51 +0200 (CEST) Received: from ogg.in.absolight.net (ogg.in.absolight.net [79.143.241.239]) by gw.in.absolight.net (Postfix) with ESMTP id 3338D6125; Tue, 28 Jun 2016 13:56:51 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by ogg.in.absolight.net (Postfix) with ESMTP id E81432B5DC87; Tue, 28 Jun 2016 13:56:50 +0200 (CEST) Date: Tue, 28 Jun 2016 13:56:50 +0200 From: Mathieu Arnold To: Dan Langille , FreeBSD Ports cc: brnrd@FreeBSD.org Subject: Re: 2016Q2 - no Mk/Uses/mysql.mk Message-ID: <7970193C92B17CEB73FA8DAD@ogg.in.absolight.net> In-Reply-To: References: X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========3911BF7C469AA34B0E13==========" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 11:56:54 -0000 --==========3911BF7C469AA34B0E13========== Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline +--On 27 juin 2016 17:22:56 -0400 Dan Langille wrote: | I've been working with the 2016Q2 branch with respect to FreshPorts. | | I tried running make -V on branches/2016Q2 and it failed with: | | Error message is: make: "/usr/local/repos/PORTS-2016Q2/Mk/bsd.port.mk" | line 1433: Cannot open /usr/local/repos/PORTS-2016Q2/Mk/Uses/mysql.mk | | It seems that recent changes to Mk also need to be backported to branches | if there is a commit on that branch. Well, no, people merging things are supposed to check what they are doing and not commit stupid patches, which is the case here. Which port has USES=mysql on 2016Q2 ? -- Mathieu Arnold --==========3911BF7C469AA34B0E13========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQJ8BAEBCgBmBQJXcmYCXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IRBYP/2vjnFSSPPQirrz2plZrCOq3 KW+0tNlFxv+ubUv2SSYGgycy8zARRi9uJ1+XSgU7q2xeIDyb0N53GkXWvCZDGFRY bgIEkMdcH+jAiykoOHce1khdNrzkt2eqrBm5hbLwTIz91glWUWBdrrQv3jYVLtKc 63UDz7e7eZ7LvVf7wbPZOdHZ6mW1ykRxUolOMkkJFlM1pYX2hIZ2238thAlV1sXq rDkOtnu8WMS2MI1xDA/6zi8apNZztxh80YUryQIFAV5Lm46GsTPRNjc25skJy4zv mtVAwNoWRpVXyePbMJ/c/eUfyuVZZj1BT7uhASm/A4M7ny+j40KID1C6JUZCeELD xVwB8pXsFuKxNpIHUGZgoZSMbPF+/NMrqygX476vV66H9xytKifZIWL193l7QyAZ 7QPQOJom6ysrciB128/XWColQctQjFJCSzKoPSWpm+Engqa6EtgaRCTmnJoMQkLs O9PI+tEIPWao4k3aLZGhTUtk+eHZBJ38ElcwvbwN3PlkxrTSdhxhEAU0sCDJMdjb ykMKvH1sX+s1NYY1Ir9mlkisdTkbN+84li+mRUVP4NhM3LDDxpHxc9FgO5A1bOYc AKAOmdovOglV6N1pWn//tJNwE4J7f6aNrgbZrv2TcVvHYmY9UBHUsNImrhnhsqLy kSdewjKPseVBZVoBAAlb =qyFU -----END PGP SIGNATURE----- --==========3911BF7C469AA34B0E13==========-- From owner-freebsd-ports@freebsd.org Tue Jun 28 14:30:26 2016 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 25851B859B9 for ; Tue, 28 Jun 2016 14:30:26 +0000 (UTC) (envelope-from dan@langille.org) Received: from clavin1.langille.org (clavin.langille.org [162.208.116.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "clavin.langille.org", Issuer "StartCom Class 2 Primary Intermediate Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F2FDA27F2; Tue, 28 Jun 2016 14:30:25 +0000 (UTC) (envelope-from dan@langille.org) Received: from (clavin1.int.langille.org (clavin1.int.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) with ESMTPSA id A320536D4 ; Tue, 28 Jun 2016 14:30:16 +0000 (UTC) Subject: Re: 2016Q2 - no Mk/Uses/mysql.mk Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: multipart/signed; boundary="Apple-Mail=_52BFC4D7-19C8-4880-B1EA-31A5FB3A3CFD"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.6b2 From: Dan Langille In-Reply-To: <7970193C92B17CEB73FA8DAD@ogg.in.absolight.net> Date: Tue, 28 Jun 2016 10:30:10 -0400 Cc: FreeBSD Ports , brnrd@FreeBSD.org Message-Id: <131F3A1C-75A0-4597-9C8A-1C14EE875323@langille.org> References: <7970193C92B17CEB73FA8DAD@ogg.in.absolight.net> To: Mathieu Arnold X-Mailer: Apple Mail (2.3124) X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 14:30:26 -0000 --Apple-Mail=_52BFC4D7-19C8-4880-B1EA-31A5FB3A3CFD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Jun 28, 2016, at 7:56 AM, Mathieu Arnold wrote: >=20 >=20 >=20 > +--On 27 juin 2016 17:22:56 -0400 Dan Langille = wrote: > | I've been working with the 2016Q2 branch with respect to FreshPorts. > | > | I tried running make -V on branches/2016Q2 and it failed with: > | > | Error message is: make: = "/usr/local/repos/PORTS-2016Q2/Mk/bsd.port.mk" > | line 1433: Cannot open = /usr/local/repos/PORTS-2016Q2/Mk/Uses/mysql.mk > | > | It seems that recent changes to Mk also need to be backported to = branches > | if there is a commit on that branch. >=20 > Well, no, people merging things are supposed to check what they are = doing > and not commit stupid patches, which is the case here. >=20 > Which port has USES=3Dmysql on 2016Q2 ? Log: MFH: r416066 net-mgmt/cacti: 0.8.8g -> 0.8.8h It appears to have already been fixed in Revision 416207: - no USES=3Dmysql allowed in the quarterly branch re = https://svnweb.freebsd.org/ports/branches/2016Q2/net-mgmt/cacti/Makefile?v= iew=3Dlog = Ooops. Sorry for the noise. I'll look at the new commits on that port. = I was analyzing commits which FreshPorts had difficulty processing. Nothing to see here. Please move along... -- Dan Langille - BSDCan / PGCon dan@langille.org --Apple-Mail=_52BFC4D7-19C8-4880-B1EA-31A5FB3A3CFD Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQJ7BAEBCgBmBQJXcon3XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1MTE2RjM0ODIzRDdERDM4OTY0OUJBNzdF QjIxNTlERUU5NzI3MzlGAAoJEOshWd7pcnOfRF8P+JzdlKPutNyHmK0WM7Alc9RJ JPX0+/sJOfaSQREdu/Qi1WCo6i5bUeLHSrVzKcfyTDkpAAn40PP89LigOg8qeK6O 8Xzxr6OrrXpyvQHF27enKtv5UYOkAz9LU53Pr+q+UjTx6mFsHcghW+J4Z+VVP4OU GQBgiuM3BkVoG2RXrPnnFmTfaEDuQPDhNP3Eujsy06Uq0F8CNHgFGPUPKI4j66cx xJ6A/LwaW2LYcz0vbR4D+LpiqBUYT9gimoHrdaA5cwwwDIv7DRyXMPfgeYyErq75 a3xo68dkz5IWnDJnkT9gYpSRH6nIWtqhpYBJJN/LBQYhFSzVi6mK7kc7BwJtZ4WV dcZgSTIJZQCAgN20skD1DQpPLpinJ1tm7UECIXmDoL1L49GfZ4s7o2Jzl1wkkdM9 mux3dck9cEmymhdCjF5Kt1suGNL5OuHhOEirIC/bldAVCySVObsHZZYtxizgmX35 6QQmpvmKdFB+2M6cupoJMK/4Ita0E2lT42IpF8tjg6cEzqC16kVM2aeM3g8p6hiP vD3t1ALDn0OHMVirrxY3Uz9VxLAIHZtTm3DzYm0yZINFZqrZBv2rfMXahSpCLws7 4Qx+E6fu8Oyr+F4+MAPJbK4XnH+kVP1rVX9p1H3X7jlRdQrDIV20Hyc3dVtHv89/ F73drWExaFhjgfUWFUE= =g72v -----END PGP SIGNATURE----- --Apple-Mail=_52BFC4D7-19C8-4880-B1EA-31A5FB3A3CFD-- From owner-freebsd-ports@freebsd.org Tue Jun 28 14:58:50 2016 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 C3216B8525C for ; Tue, 28 Jun 2016 14:58:50 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (prod2.absolight.net [79.143.243.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5F35F2C55; Tue, 28 Jun 2016 14:58:50 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 451D4BDC89; Tue, 28 Jun 2016 16:58:48 +0200 (CEST) Received: from gw.in.absolight.net (gw-ecl.in.absolight.net [79.143.241.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.in.absolight.net", Issuer "CA Cert Signing Authority" (not verified)) by prod2.absolight.net (Postfix) with ESMTPSA id 2CD71BDC88; Tue, 28 Jun 2016 16:58:48 +0200 (CEST) Received: from ogg.in.absolight.net (ogg.in.absolight.net [79.143.241.239]) by gw.in.absolight.net (Postfix) with ESMTP id 7F40F6125; Tue, 28 Jun 2016 16:58:47 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by ogg.in.absolight.net (Postfix) with ESMTP id 1475E2B6134E; Tue, 28 Jun 2016 16:58:47 +0200 (CEST) Date: Tue, 28 Jun 2016 16:58:46 +0200 From: Mathieu Arnold To: Dan Langille cc: FreeBSD Ports , brnrd@FreeBSD.org Subject: Re: 2016Q2 - no Mk/Uses/mysql.mk Message-ID: <988FA8093FFCEAC15BBC1315@ogg.in.absolight.net> In-Reply-To: <131F3A1C-75A0-4597-9C8A-1C14EE875323@langille.org> References: <7970193C92B17CEB73FA8DAD@ogg.in.absolight.net> <131F3A1C-75A0-4597-9C8A-1C14EE875323@langille.org> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========67672882EB9DFF985368==========" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 14:58:50 -0000 --==========67672882EB9DFF985368========== Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline +--On 28 juin 2016 10:30:10 -0400 Dan Langille wrote: |> On Jun 28, 2016, at 7:56 AM, Mathieu Arnold wrote: |> |> |> |> +--On 27 juin 2016 17:22:56 -0400 Dan Langille wrote: |> | I've been working with the 2016Q2 branch with respect to FreshPorts. |> | |> | I tried running make -V on branches/2016Q2 and it failed with: |> | |> | Error message is: make: "/usr/local/repos/PORTS-2016Q2/Mk/bsd.port.mk" |> | line 1433: Cannot open /usr/local/repos/PORTS-2016Q2/Mk/Uses/mysql.mk |> | |> | It seems that recent changes to Mk also need to be backported to |> | branches if there is a commit on that branch. |> |> Well, no, people merging things are supposed to check what they are doing |> and not commit stupid patches, which is the case here. |> |> Which port has USES=mysql on 2016Q2 ? | | Log: | MFH: r416066 | | net-mgmt/cacti: 0.8.8g -> 0.8.8h | | It appears to have already been fixed in Revision 416207: | | - no USES=mysql allowed in the quarterly branch | | re | https://svnweb.freebsd.org/ports/branches/2016Q2/net-mgmt/cacti/Makefile? | view=log | | | Ooops. Sorry for the noise. I'll look at the new commits on that port. | I was analyzing commits which FreshPorts had difficulty processing. | | Nothing to see here. Please move along... Well, no, the noise is good, it should be reported to the committer that did the commit, like other breakage are, so that said committer knows and fixes the problem. -- Mathieu Arnold --==========67672882EB9DFF985368========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQJ8BAEBCgBmBQJXcpCmXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IvS8P/2zdENc0yQYaMWDsmLlmNoru 3v8SZsmRN0fypcodrEyWXO/s//orrzhLjCf/bUgizzlPG2RLo+iQbXABg2+Vmcfb EIhnE4YI7wIH9THoYB3Iao4MLxMSr35Bk17xx3ka/xhPpYz0M62KWfYMGX2AC898 FuCZDzebTp6ryyFpcZZKYzrA738IlkUt+UwTj70ZmhGypkrNwVcrRuZp1C/v1emY kibSSlSJkWi1mLcLiSqaM+Acw1K3VIRoh37oY45q1DDdkKz0GRreiYOCjffpZwGl zbkP8Nqh6D/iGzMRd7en/CLjjlYmNclneuCbPS0s2au9Uf+23VU8V7QW7TI4Q347 vmMYNmWD/4fjM1IjJXVHBpWqxF1qZJBmJ1PxJ/HbSuZ6begXN7gY2IU7CNHa/Plp TCtxByNG8RCvb32dm9uUcBEDCD+fBmvXqVbs3jd3z6/bk4ErPplrKCIe4Vznywi+ 0p3LmxsuxlNUHLKQ5jauCIT3/Y1Gw6e2jA/Admk1gIdBtT65xg/gSZxijwRRoFfz 5zqju8RxZMRgU8YZ+3lCcwd+q1eukrL4f+xXoMIBY0CIdNBTRQMFIywHcWQ7EUOD COAkpHThcICh3003yx/wJgokmdboLBg6hlWchgZfxtKPyYpHAAXFX/vuvIjmUQnd hGdYjWslI6LQa+OrS+qA =9DtI -----END PGP SIGNATURE----- --==========67672882EB9DFF985368==========-- From owner-freebsd-ports@freebsd.org Tue Jun 28 15:49:00 2016 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 58737B815F4 for ; Tue, 28 Jun 2016 15:49:00 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 44E9F2F52 for ; Tue, 28 Jun 2016 15:49:00 +0000 (UTC) (envelope-from hps@selasky.org) Received: by mailman.ysv.freebsd.org (Postfix) id 444B7B815F3; Tue, 28 Jun 2016 15:49:00 +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 413AEB815F2; Tue, 28 Jun 2016 15:49:00 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 5B6912F51; Tue, 28 Jun 2016 15:48:59 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 0FBE11FE022; Tue, 28 Jun 2016 17:48:51 +0200 (CEST) Subject: Re: pkg SAT_SOLVER bugs To: Baptiste Daroussin References: <20150414200459.GE39658@ivaldir.etoilebsd.net> <20150421103454.GR1394@zxy.spb.ru> <5593D0AE.2010205@selasky.org> <416359ce-1dcd-1160-5c56-f120a0f6358f@selasky.org> <20160627115533.gqvdsmtzwnvrrfuo@ivaldir.etoilebsd.net> Cc: Slawa Olhovchenkov , ports@FreeBSD.org, FreeBSD Current From: Hans Petter Selasky Message-ID: <0671148b-d7cd-f8ad-906d-a0baa1b98cf5@selasky.org> Date: Tue, 28 Jun 2016 17:52:32 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <20160627115533.gqvdsmtzwnvrrfuo@ivaldir.etoilebsd.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 15:49:00 -0000 On 06/27/16 13:55, Baptiste Daroussin wrote: > On Mon, Jun 27, 2016 at 12:38:02PM +0200, Hans Petter Selasky wrote: >> Hi, >> >> I found some bugs in PKG with regard to the SAT_SOLVER environment variable. >> Please find patch attached :-) >> >> Issues fixed: >> 1) No need to use hash table when generating SAT rules for external solver. >> Variables are already in a linear array. Fix encoding and decoding of SAT >> data. >> 2) Endless variable loop caused pkg to crash. >> 3) it->inverse was checked for non-zero, while it should actually be checked >> for -1 only. SAT rules produces were all negative. >> >> How to verify: >> >> make -C /usr/ports/math/picosat all install clean >> >> env SAT_SOLVER=picosat pkg upgrade >> >> --HPS > > Thank you I will look into shortly > Hi Baptiste, Are you handling this one or do you want me to create an issue at github. Thank you! --HPS From owner-freebsd-ports@freebsd.org Tue Jun 28 15:56:56 2016 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 D6B5FB81A71 for ; Tue, 28 Jun 2016 15:56:56 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) 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 B1C9026B4 for ; Tue, 28 Jun 2016 15:56:56 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id AD79AB81A6F; Tue, 28 Jun 2016 15:56:56 +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 AA809B81A6E; Tue, 28 Jun 2016 15:56:56 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 77F1426B3; Tue, 28 Jun 2016 15:56:56 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pa0-x22e.google.com with SMTP id bz2so7705200pad.1; Tue, 28 Jun 2016 08:56:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:reply-to:subject:references:to:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=cTwYkHXuHZwDheyP4k6wzuz7lvfl2urcdyg2ytKLK3o=; b=Br86p23YpQFGceGVzG1ZkEY5cIu/1j1BzIQfhQShZV5k0spXl6l65f92nCjwtrEyDH 3gdQ+0rxsmSvD01jwwaklxGYtx5sirhhGOkU+meSYWYhjZoT0aA4LAQosD5YP2IO+QoA LUDHd3uXs3LK0XSqC6dsF1TcGZsflYk8Kx0+DfaEgMIvMr2Hu8Li/3XdAGbhgXerSzd7 dDF4GSlNGAGIMVSTks3qJcQozKc28uqVn1gNxxVC6KwUdmFTFGwdHqA5gL327IovpBeJ F8xt5kQc1xiAPNQtMtwtX1cUcB9NvArYmSdquQqZjuGTHN2kLAYzTLc1bWvrXZFcB+Ha TWJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:reply-to:subject:references:to:cc:from :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=cTwYkHXuHZwDheyP4k6wzuz7lvfl2urcdyg2ytKLK3o=; b=EIVlfGo2LiRlPlEtgzTr1VES/tsVhL3HOwHwcmmr5w82kCDNSGhb2ijiq/dkkDz9Ni ZFOI6DqfKTRGfEafzFr6P33CNoJbfaNwvBjm//hqhLdSAcBIHnk/S5/kUu0Rg8wwnbOY FAYeFOM2UqqyAJivvi6BTgeQG3A8ri0KQngBKygJ3LtTfjXyZNA9/1ohnxsXW48Bt52o Lq3wQr8xK2YWXDvfZFBRKH7qpz/P4dqw3cgnVoDn8rX7KCnBRYb63xayPqTWu2XtgUhz URvs6P49vUBQPL4/kHFXv0FOZkbIxtR6S4HHv0zl3C3XyaEswcDl6SIC/Z9Ik7ukMKMR ZvAw== X-Gm-Message-State: ALyK8tJzThHq+2dQ7qkopKGPHcVrnWkN9t06V+GqzfkVoOL5aLNWGTzDUJjP2VIRHHPOzw== X-Received: by 10.66.118.169 with SMTP id kn9mr2935421pab.109.1467129415903; Tue, 28 Jun 2016 08:56:55 -0700 (PDT) Received: from ?IPv6:2001:44b8:31ae:7b01:ac25:cc30:5165:1dd1? (2001-44b8-31ae-7b01-ac25-cc30-5165-1dd1.static.ipv6.internode.on.net. [2001:44b8:31ae:7b01:ac25:cc30:5165:1dd1]) by smtp.gmail.com with ESMTPSA id b71sm7549981pfc.51.2016.06.28.08.56.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Jun 2016 08:56:55 -0700 (PDT) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: pkg SAT_SOLVER bugs References: <20150414200459.GE39658@ivaldir.etoilebsd.net> <20150421103454.GR1394@zxy.spb.ru> <5593D0AE.2010205@selasky.org> <416359ce-1dcd-1160-5c56-f120a0f6358f@selasky.org> To: Hans Petter Selasky , Slawa Olhovchenkov , Baptiste Daroussin Cc: ports@FreeBSD.org, FreeBSD Current From: Kubilay Kocak Message-ID: Date: Wed, 29 Jun 2016 01:56:47 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Thunderbird/47.0 MIME-Version: 1.0 In-Reply-To: <416359ce-1dcd-1160-5c56-f120a0f6358f@selasky.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 15:56:56 -0000 On 27/06/2016 8:38 PM, Hans Petter Selasky wrote: > Hi, > > I found some bugs in PKG with regard to the SAT_SOLVER environment > variable. Please find patch attached :-) > > Issues fixed: > 1) No need to use hash table when generating SAT rules for external > solver. Variables are already in a linear array. Fix encoding and > decoding of SAT data. > 2) Endless variable loop caused pkg to crash. > 3) it->inverse was checked for non-zero, while it should actually be > checked for -1 only. SAT rules produces were all negative. > > How to verify: > > make -C /usr/ports/math/picosat all install clean > > env SAT_SOLVER=picosat pkg upgrade > > --HPS > Heads-up: Have just updated picosat to its latest version, enjoy! From owner-freebsd-ports@freebsd.org Tue Jun 28 16:22:43 2016 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 6DFB7B85309 for ; Tue, 28 Jun 2016 16:22:43 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 481F42B39 for ; Tue, 28 Jun 2016 16:22:43 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 4740BB85307; Tue, 28 Jun 2016 16:22:43 +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 42295B85306; Tue, 28 Jun 2016 16:22:43 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D5C922B38; Tue, 28 Jun 2016 16:22:42 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id a66so35587074wme.0; Tue, 28 Jun 2016 09:22:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Wfm9SQter/9xI4CZpVW0sTS0Ow3/UjDqlGBixQDKYP0=; b=KC+S2bDOFtLohiTkxyJ022Q+B7ggsBchhef2cG21LUsmk8O21fpwaSitKe8Bz0f8hl Qd32sEz+LZ+LA3S3UtVNw97567lfaRH24UYUUYJjeAyw0p4moX6E3myQEDlMx7YdOI+6 JL7aJHVDL3zfDihb+yPhunL1ZJQZBRWTxu94kIegVcgNIHuZAfAhPJu0lOqrSkeMakZ6 wFx3nWpRtbqLyci7Ge/RMgZcPuP3cflQcXCJ27inrT9z399mqXtR6h+t59dWMAoicE3d IrIm9wjGFQLtHDQjz+pQsHopHVLmEWdz9ewdE8Mk+y7RvbZCZXESRYh4XDv9TLOluRm8 X9Pw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=Wfm9SQter/9xI4CZpVW0sTS0Ow3/UjDqlGBixQDKYP0=; b=QupBOZSJ6Ya3k0HqzvOf3GQHpbdc6MZ3hzOjMlYqgG6Abrtc8BC0yut1DE80YzzAwT 0oEn4h0gqhcNFifxoGgQBkawoL130sArd+fbgMGZibufUNnu3O3t/xetdVSFNC//HW1Y RjdOABuXY4WVLj1dyFCh58IWLefDc0Nar71Ry8tT4eHHm4fp/2rrcQecugz6g7jqDA9Z fw3RVH18LipOWr7NLvFKH40cLCD8hG3kwrt9V/4v+KKQQEu3/Gh24oSdESUXAGTFZMnM /Azj/4b8enFXSjAHkyDqn3TTidcqeOkqUU3FU1+gw/988BolUcii2UPzRtbrhoz8WEBT RbxA== X-Gm-Message-State: ALyK8tLJBnQQ6af5X8LzwzkkmK041DjhA5ni/vjCtv8euICQEvttCF//WPvRZ08ZNdzOWQ== X-Received: by 10.194.82.161 with SMTP id j1mr4315510wjy.65.1467130961313; Tue, 28 Jun 2016 09:22:41 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id f73sm3757307wmg.1.2016.06.28.09.22.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Jun 2016 09:22:40 -0700 (PDT) Sender: Baptiste Daroussin Date: Tue, 28 Jun 2016 18:22:39 +0200 From: Baptiste Daroussin To: Hans Petter Selasky Cc: Slawa Olhovchenkov , ports@FreeBSD.org, FreeBSD Current Subject: Re: pkg SAT_SOLVER bugs Message-ID: <20160628162239.nopc2r2mtleuszpm@ivaldir.etoilebsd.net> References: <20150414200459.GE39658@ivaldir.etoilebsd.net> <20150421103454.GR1394@zxy.spb.ru> <5593D0AE.2010205@selasky.org> <416359ce-1dcd-1160-5c56-f120a0f6358f@selasky.org> <20160627115533.gqvdsmtzwnvrrfuo@ivaldir.etoilebsd.net> <0671148b-d7cd-f8ad-906d-a0baa1b98cf5@selasky.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="5tssyup75cku5k4s" Content-Disposition: inline In-Reply-To: <0671148b-d7cd-f8ad-906d-a0baa1b98cf5@selasky.org> User-Agent: Mutt/1.6.1-neo (2016-06-11) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 16:22:43 -0000 --5tssyup75cku5k4s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 28, 2016 at 05:52:32PM +0200, Hans Petter Selasky wrote: > On 06/27/16 13:55, Baptiste Daroussin wrote: > > On Mon, Jun 27, 2016 at 12:38:02PM +0200, Hans Petter Selasky wrote: > > > Hi, > > >=20 > > > I found some bugs in PKG with regard to the SAT_SOLVER environment va= riable. > > > Please find patch attached :-) > > >=20 > > > Issues fixed: > > > 1) No need to use hash table when generating SAT rules for external s= olver. > > > Variables are already in a linear array. Fix encoding and decoding of= SAT > > > data. > > > 2) Endless variable loop caused pkg to crash. > > > 3) it->inverse was checked for non-zero, while it should actually be = checked > > > for -1 only. SAT rules produces were all negative. > > >=20 > > > How to verify: > > >=20 > > > make -C /usr/ports/math/picosat all install clean > > >=20 > > > env SAT_SOLVER=3Dpicosat pkg upgrade > > >=20 > > > --HPS > >=20 > > Thank you I will look into shortly > >=20 >=20 > Hi Baptiste, >=20 > Are you handling this one or do you want me to create an issue at github. > Thank you! >=20 I am handling it BTW not that picosat is the one we use internally already :D Best regards Bapt --5tssyup75cku5k4s Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXcqRPAAoJEGOJi9zxtz5acagQAKZqpdQ5XLmufX2lCsWndnRv WM0aySvnlXJ0+FEmCIHMZBF1xnIupOQA5ZaBFFMcUXFruCuNykEpgSdKVxBP1SA7 VwBoFlQCDolHsA4ItNidGn8SioPdUG+M0ufqEvgOd7vVkT+QJajlYeccBp0Rss3J LQY7t7eBji9jRcHcrMvdXgY28DdPntu72qxypiMc3Vfc5EycR93Nm4ImoKWZMbk/ X+5ph5zM3xM/NwImTOZO13nZfjhmKRR5GGlcgC6QR1c6enaE9ua8LRA4/hbLsyqX 0dVgRXYwmy51+GzNewAQU2Et+9EOCz8CWxcXEk6dgxl6C89YYhrhelEK/or+be0Z NcMgAki5BZfluVekMuOGEzdqm6UMIbq2lsMQBN2HwwUQjMmBMHUcP0J5ahQOOkEp brXalOiTBQwctUqxRXSA4ob+vbALcn8z08TLtq2WjDYnl1E0s3hoHe+PfHgLTbHE e6mj54Nt5KXqMogZKAjT6K6xkDT56vQNndP1RXnfS7wS+7t6K2zZs/k7nzekcjKk b3D27UtxPo4uqsDo4q717GFr84bzgt6uBq1Uz1ZN+Daahw/6MO16TD6M4ZHgIsaT y+nIu7MRsHRI6/n5G56eI72Rk4YCq2Mp2tZeV14qoMWK5Ro54DjLEQeceZIPQK1C cC1VeVVbAaXbFgpwLJO3 =5/Q9 -----END PGP SIGNATURE----- --5tssyup75cku5k4s-- From owner-freebsd-ports@freebsd.org Tue Jun 28 16:24:04 2016 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 20936B853F1 for ; Tue, 28 Jun 2016 16:24:04 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E287C2DB8 for ; Tue, 28 Jun 2016 16:24:03 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pa0-x22b.google.com with SMTP id hl6so7896074pac.2 for ; Tue, 28 Jun 2016 09:24:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:reply-to:subject:references:to:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=3UTtc51bO0ZwTdmsjIvVuFr/RiPAvjTZyH/rX9HCdZY=; b=q0RS9r9zF4/1qdzlgweqTLRXrVpXDiIcAFB+pMvukyyocw3nP1S2WmLU+Um9KYRihw rzEz4H7iJsKehUyYoa6WE0mFTzZUP+Qiv+0hXoDse8IeKBvsbp9LUorZBXvaZp3JbKd3 BD5ky6co8cV4FmmitCUaksdvG1XoO1/9/BlE5NXJ57gW8IMHcGzJurbcgOmdoWyHD7zG tOUDSMvkOLSVYtCCEXehVDYtBngtCwnLEnk3lyQ4Galk2sPTeWyXwdN3XRc+0+OthMaB guS7doevR3qoivXFaKotTAX+TO2ej1mgn3hpSzq9nLvRwdN8TfGp3vX5xYOFT2lJI0kO cCbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:reply-to:subject:references:to:cc:from :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=3UTtc51bO0ZwTdmsjIvVuFr/RiPAvjTZyH/rX9HCdZY=; b=HrdIHdwwad1S4B+Ut6kmCyEBqwvU0nSBHoIV2kKtQEOFVumSH9DNDETk/jnyaEMGyg BonkYLnDJ6zp8bc1b3FPk1ITtWbgzg/KVwwqT6AE/0tl2UB0EkFSvoaor+5MhslAvJul S8TIKFXxW8bTxgfpKyq+12EdZ3Eji+i5xDSjQWiHkyG6xEW/ylGkedVguqHFOL6IG2Ws FibrTyZoVflRZwdBOhwpRp/7u09ojDdr6gzrBOLYoOelZQcONEDul5hM6XID4hZyrf/g peo2vy6YfIxCoBY2/hWhanQTLXAzLDJDGwuJ0CoxiNWoMjPcgQTpGgLSt5LQT5fH7VVX cwbQ== X-Gm-Message-State: ALyK8tJBNw/UsSvOnw0627VNhqWYw28yHLtCSLDH/ePckVHidvbK6sd/gm0X4OmfrgDE5Q== X-Received: by 10.66.118.169 with SMTP id kn9mr3161817pab.109.1467131043479; Tue, 28 Jun 2016 09:24:03 -0700 (PDT) Received: from ?IPv6:2001:44b8:31ae:7b01:ac25:cc30:5165:1dd1? (2001-44b8-31ae-7b01-ac25-cc30-5165-1dd1.static.ipv6.internode.on.net. [2001:44b8:31ae:7b01:ac25:cc30:5165:1dd1]) by smtp.gmail.com with ESMTPSA id w63sm478187pfi.9.2016.06.28.09.24.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Jun 2016 09:24:03 -0700 (PDT) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: blanket portmgr approval vs. non-fixing changes References: <201606272021.u5RKLVhQ057899@slippy.cwsent.com> <20160628110322.GA51760@spectrum.skysmurf.nl> To: Alphons van Werven , Kevin Golding Cc: freebsd-ports@freebsd.org From: Kubilay Kocak Message-ID: Date: Wed, 29 Jun 2016 02:23:55 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Thunderbird/47.0 MIME-Version: 1.0 In-Reply-To: <20160628110322.GA51760@spectrum.skysmurf.nl> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 16:24:04 -0000 On 28/06/2016 9:03 PM, Alphons van Werven wrote: > Maintainers are already notified by e-mail of commits resulting from PRs > because they are put on the CC list. Maybe it's just me, but I think it > would be very nice if maintainers were *always* automagically notified of > *any* commits to their ports, including those subject to blanket approval. Good idea, as long as people could opt-in/out as appropriate. > With any luck, such notifications are received in time to prevent (or at > least limit) wasted time such as in the above case. Moreover, keeping > maintainers informed also eliminates having to wonder "Ey, what's this > 'ere then?" the next time they look at their ports. And finally, I'd > surmise it would also help keeping maintainers abreast of developments in > the ports infrastructure in general. > > I know that the PR notifications come from BugZilla and not from SVN, so > what I don't know is how feasible it is rig up something like this, but I > do know that I for one would quite appreciate something along these lines. Quite feasible, hit me up off list and we can discuss further :) ./koobs From owner-freebsd-ports@freebsd.org Tue Jun 28 16:53:03 2016 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 0B448B85C62 for ; Tue, 28 Jun 2016 16:53:03 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id ECE1023E3 for ; Tue, 28 Jun 2016 16:53:02 +0000 (UTC) (envelope-from julian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id EC17CB85C61; Tue, 28 Jun 2016 16:53:02 +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 EBC1CB85C60 for ; Tue, 28 Jun 2016 16:53:02 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B274823E1 for ; Tue, 28 Jun 2016 16:53:02 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-236-103.lns20.per1.internode.on.net [121.45.236.103]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u5SGquEQ025556 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 28 Jun 2016 09:53:00 -0700 (PDT) (envelope-from julian@freebsd.org) To: "ports@FreeBSD.org" From: Julian Elischer Subject: best way to tune ports to add a CLFAGS entry Message-ID: <7d454696-f910-7533-5757-74eb624f9315@freebsd.org> Date: Wed, 29 Jun 2016 00:52:51 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 16:53:03 -0000 At work I am doing various cross compiles in order to make a product under freebsd that actually will run under a modified FreeBSD that runs on an appliance. We want to get away from hand rolling everything to leverage all teh work in getting ports working well on FreeBSD. We have some extra syscalls and some structures have different sizes, so we need to compile/link agains an alternate set of includes/libraries and not those in /usr/include or /usr/lib. Ideally I want to use the "--sysroot" and "-isystem" options to the compiler/linker or failing that, add a -I or -L entries to make it look at the correct includes and libraries, not those in the base system. In many ports CFLAGS etc. are sent in via the arguments to ./configure or environment vars, but there are many other ports that have other ways to specify these. Does the ports framework have any standard way to do this? LDEXTRA_ARGS or EXTRA_CFLAGS or similar? I've looked around and can't really see anything. Best would be a single file to which I could add these things but adding them to the environment would also work. yours in ports ignorance.. Julian From owner-freebsd-ports@freebsd.org Tue Jun 28 20:02:40 2016 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 D0F71B864D7 for ; Tue, 28 Jun 2016 20:02:40 +0000 (UTC) (envelope-from brnrd@FreeBSD.org) Received: from smtp01.qsp.nl (smtp01.qsp.nl [193.254.214.162]) by mx1.freebsd.org (Postfix) with ESMTP id 618092572; Tue, 28 Jun 2016 20:02:40 +0000 (UTC) (envelope-from brnrd@FreeBSD.org) Received: from smtp01.qsp.nl (localhost [127.0.0.1]) by smtp01.qsp.nl (Postfix) with ESMTP id 568002A0D5F; Tue, 28 Jun 2016 21:57:20 +0200 (CEST) Received: from mail.brnrd.eu (unknown [193.164.217.85]) by smtp01.qsp.nl (Postfix) with ESMTP; Tue, 28 Jun 2016 21:57:20 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=brnrd.eu; h=date:from:to:subject:message-id; s=default; bh=8w8KN7Bw3hXEGo5OB8hD1JAIVGOkGhlzURtxsaWvsos=; b=C2HiOiOTmal3Kqfh3OhEjRHzqbe34UD7CGk6lFal6ZZH/uauprCntPCLFDHg7jxXpzoHdpzKszroW/pJKwFweX6zufm7mdgn/lg8RY0qOLiYTtoN1Wd0W5FR6kyXwWCxe0zsij1HPDZ+dETFRqOlDrqlB4Wgu3Zd1lfewoLRc1jmmo5YS92if8Em4Pc+tf6qrjezm+oji6ol5epUZVp7n6DqedWdldvOUOfIOdwMBbc9OUsCNZPZ5ODuAm3Xhrn2Zy7AcDLmIUrRb99c7wm5WY5lKgg3Z4xSsalzDmofRN6KUqoMmJyir+uBb+ygLRRiKWEhCBrWBDTph/Z5+eQL8g== Received: by bachfreund.nl (OpenSMTPD) with ESMTPSA id d4f0225b TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 28 Jun 2016 21:57:18 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Date: Tue, 28 Jun 2016 21:57:17 +0200 From: Bernard Spil To: Mathieu Arnold Cc: Dan Langille , FreeBSD Ports Subject: Re: 2016Q2 - no Mk/Uses/mysql.mk In-Reply-To: <988FA8093FFCEAC15BBC1315@ogg.in.absolight.net> References: <7970193C92B17CEB73FA8DAD@ogg.in.absolight.net> <131F3A1C-75A0-4597-9C8A-1C14EE875323@langille.org> <988FA8093FFCEAC15BBC1315@ogg.in.absolight.net> Message-ID: <388f61fead8522e594f78d9f563321a6@imap.brnrd.eu> X-Sender: brnrd@FreeBSD.org User-Agent: Roundcube Webmail/1.2.0 X-SMTP-Virus-Scanned: clamav at smtp01 X-Spam-Status: No, score=1.6 required=5.0 tests=HK_RANDOM_ENVFROM, HK_RANDOM_FROM,UNPARSEABLE_RELAY autolearn=disabled version=3.4.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on svfilter02.qsp.nl X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 20:02:40 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2016-06-28 16:58, Mathieu Arnold wrote: > +--On 28 juin 2016 10:30:10 -0400 Dan Langille wrote: > |> On Jun 28, 2016, at 7:56 AM, Mathieu Arnold wrote: > |> > |> > |> > |> +--On 27 juin 2016 17:22:56 -0400 Dan Langille wrote: > |> | I've been working with the 2016Q2 branch with respect to FreshPorts. > |> | > |> | I tried running make -V on branches/2016Q2 and it failed with: > |> | > |> | Error message is: make: "/usr/local/repos/PORTS-2016Q2/Mk/bsd.port.mk" > |> | line 1433: Cannot open /usr/local/repos/PORTS-2016Q2/Mk/Uses/mysql.mk > |> | > |> | It seems that recent changes to Mk also need to be backported to > |> | branches if there is a commit on that branch. > |> > |> Well, no, people merging things are supposed to check what they are doing > |> and not commit stupid patches, which is the case here. > |> > |> Which port has USES=mysql on 2016Q2 ? > | > | Log: > | MFH: r416066 > | > | net-mgmt/cacti: 0.8.8g -> 0.8.8h > | > | It appears to have already been fixed in Revision 416207: > | > | - no USES=mysql allowed in the quarterly branch > | > | re > | https://svnweb.freebsd.org/ports/branches/2016Q2/net-mgmt/cacti/Makefile? > | view=log > | | ?view=log> > | > | Ooops. Sorry for the noise. I'll look at the new commits on that port. > | I was analyzing commits which FreshPorts had difficulty processing. > | > | Nothing to see here. Please move along... > > Well, no, the noise is good, it should be reported to the committer that > did the commit, like other breakage are, so that said committer knows and > fixes the problem. Just lucky that it wasn't me. Good thing to keep in mind with these kinds of changes! Usually only the actual update is committed, not a check for these kinds of changes to the ports framework! I've got some Python patches in review that now have USES= ssl which would break in Q2 as well! Luckily no security fixes in there afaik. Cheers, Bernard. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJXctaeAAoJEHT7/r+FArC0rzsP/jx32UsjVtA8dgYHCf+gM7mt gz55FCOT7XI+m13nAZWpI3VfsW2MuA99j/B/npXMfDSqixGSDfZyFq0Xr+MPP9UU b48TGrXbEUVQvkG4dRy5WK/J0XcqwO2x+ajD29lJtHZE/2aTMrBoXRYYifQkx0ew iDftQDlauGp8usNjgAVrZffRkj0q0v2cQGcepL8iqHuKXA63b9dsxV65BeIUFLPE hnL+AneFqiaXa9zSc72/o3PS173Y8d3XaSxPjw4pRBBuD4mDDadAdebUz/ZCVwug k6g+LsVs+iqjn8nq1O6wgqJHh7LKLU04WGSPYHSUl7ErzmBOlxKJleFM3gOur2Og 9qy/dLwvftlNtEZ/8aI00ZVcKd4kzyoYZxa215g3A+vd+zDOTSPOWE3VgNoyf4KK NHrKkrKH3f7/5um4RBuJf69lFs1X7RNuPPCXONnO1t3xDDOeOFAseKrQodDqfTo2 nC9X/Kf1cHi/wU9aF0DqttJj10fXdjbkthcKlSZ+dwk6p+wEEwLorbXrGI00f/aG R6UFa5XhdQxkBYGiBKwPaNTEsNoGo0BhK48z5oknt9rv6Psm8C7Sa99euCVFMxqY FftKkp3Iy731AnrApWkzaDd9CNtkvomhYZklx1rG/cqOq+0Xz+clFV1BADSZS2T1 Bd+0Wkqzm5WA7FDgjNOP =WchY -----END PGP SIGNATURE----- From owner-freebsd-ports@freebsd.org Tue Jun 28 20:41:05 2016 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 C915AB86D20 for ; Tue, 28 Jun 2016 20:41:05 +0000 (UTC) (envelope-from mailreturn@smtp6.ymlpsrvr.net) Received: from smtp6.ymlpsrvr.net (smtp6.ymlpsrvr.net [185.83.49.16]) (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 7439127E2 for ; Tue, 28 Jun 2016 20:41:05 +0000 (UTC) (envelope-from mailreturn@smtp6.ymlpsrvr.net) Date: Tue, 28 Jun 2016 21:39:15 +0200 To: freebsd-ports@freebsd.org From: Hosiery Street Subject: Independence Day Sale, starts right now. Message-ID: <30d13783b06863434fae022e6030fbef@smtp6.ymlpsrvr.net> X-YMLPcode: 8ryt+513+93820 MIME-Version: 1.0 Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 20:41:05 -0000 --------------------------------------------------------------------------= ------ This email newsletter was sent to you in graphical HTML format. If you're seeing this version, your email program prefers plain text = emails. You can read the original version online: http://ymlp48.com/zFdEBC --------------------------------------------------------------------------= ------ HAPPY INDEPENDENCE DAY!!! ( http://hosierystreet.com/&refer=3Dem_716 ) SALE!!!! FREE SHIPPING FOR FREEDOM WEEKEND!!!! ON ALL ORDERS $25 AND UP IN CONTIGUOUS US of A!!!!! Dear Customer Thank you so much for shopping at HosieryStreet.com As in every email (just a few times a year) we would like to remind you first and foremost that if you don't want to be on our sale list please unsubscribe below and you will be removed from this email list immediately. We do not want to SPAM anyone. PLEASE DO NOT REPORT THIS AS SPAM. The following is a few of our HOTTEST items you may be interested in: 5 HOTTEST DEALS FROM BESTFORM ( http://www.hosierystreet.com/system/scripts/search.cgi?&p=3D1&&Company=3DB= estform&Submit2=3DSearch&action=3Dsearch&per_page=3D90&sort_by=3DBrand#Sea= rch&refer=3Dem_716 ). NOW ONLY: $8.99 Bestform Double Lined Front Close Cotton Sport Bra. #6014 Click here for more info >>> ( http://www.hosierystreet.com/system/scripts/results_big.cgi?product=3Dbef6= 014&refer=3Dem_716 )NOW ONLY: $8.49 Bestform INVISABRA Undewire# 6502 Click here for more info >>> ( http://www.hosierystreet.com/system/scripts/results_big.cgi?product=3Dbf65= 02&refer=3Dem_716 ) NOW ONLY: $6.99 Bestform BodyCottons Softcup # 6715 Click here for more info >>> ( http://www.hosierystreet.com/system/scripts/results_big.cgi?product=3Dbf67= 15&refer=3Dem_716 )NOW ONLY: $10.99 Bestform Shirred Front Sport Bra. #6040 Click here for more info >>> ( http://www.hosierystreet.com/system/scripts/results_big.cgi?product=3Dbef6= 040&refer=3Dem_716 )NOW ONLY: $6.99 Bestform BodyCottons Softcup # 6825 Click here for more info >>> ( http://www.hosierystreet.com/system/scripts/results_big.cgi?product=3Dbf68= 25&refer=3Dem_716 ) or click here for more BestForm Bras at Greatly Discounted Prices... ( http://www.hosierystreet.com/system/scripts/search.cgi?&p=3D1&&Company=3DB= estform&Submit2=3DSearch&action=3Dsearch&per_page=3D90&sort_by=3DBrand#Sea= rch&refer=3Dem_716 ) 6 MORE GREAT DEALS FROM VASSARETTE ( http://www.hosierystreet.com/system/scripts/search.cgi?&p=3D1&&txtSearch= =3D&search_type=3Din_all&category=3D21&Company=3DVassarette&price_from=3D&= price_to=3D&command=3Dadvance_search&action=3Dsearch&cmdGetCustomers=3DGet= +Result&per_page=3D90&sort_by=3DBrand#Search&refer=3Dem_716 ). NOW ONLY: $3.99 Vassarette Light Control Hi-Cut Brief Click here for more info >>> ( http://www.hosierystreet.com/system/scripts/results_big.cgi?product=3D48-0= 01&refer=3Dem_716 )NOW ONLY: $3.99 Vassarette Light Control Brief Click here for more info >>> ( http://www.hosierystreet.com/system/scripts/results_big.cgi?product=3D40-0= 01&refer=3Dem_716 )NOW ONLY: $3.99 Vassarette Light Control Brief Click here for more info >>> ( http://www.hosierystreet.com/system/scripts/results_big.cgi?product=3D40-0= 01&refer=3Dem_716 ) NOW ONLY: $9.89 Vassarette BodyCurves Microfiber Wireless Contour Click here for more info >>> ( http://www.hosierystreet.com/system/scripts/results_big.cgi?product=3D72-2= 39&refer=3Dem_716 )NOW ONLY: $11.49 Vassarette RealSexy Her Secret Push Up UW Click here for more info >>> ( http://www.hosierystreet.com/system/scripts/results_big.cgi?product=3D75-3= 20&refer=3Dem_716 ) NOW ONLY: $12.99 Vassarette BodyCurves Flir-T FF Contour UW. #75-818 Click here for more info >>> ( http://www.hosierystreet.com/system/scripts/results_big.cgi?product=3D75-8= 18&refer=3Dem_716 ) or click here for more ON SALE Vassarette Bras... ( http://www.hosierystreet.com/system/scripts/search.cgi?&p=3D1&&txtSearch= =3D&search_type=3Din_all&category=3D21&Company=3DVassarette&price_from=3D&= price_to=3D&command=3Dadvance_search&action=3Dsearch&cmdGetCustomers=3DGet= +Result&per_page=3D90&sort_by=3DBrand#Search&refer=3Dem_716 ) ------------------------- PLEASE CHECK OUT OUR VANITY FAIR BRA LINE!!! ( http://www.hosierystreet.com/system/scripts/search.cgi?txtSearch=3D&search= _type=3Din_all&category=3D21&Company=3DVanity+Fair&price_from=3D&price_to= =3D&command=3Dadvance_search&action=3Dsearch&cmdGetCustomers=3DGet+Result&= refer=3Dem_716 ) MORE INFO >>> CLICK HERE >>> ( http://www.hosierystreet.com/system/scripts/search.cgi?txtSearch=3D&search= _type=3Din_all&category=3D21&Company=3DVanity+Fair&price_from=3D&price_to= =3D&command=3Dadvance_search&action=3Dsearch&cmdGetCustomers=3DGet+Result&= refer=3Dem_716 ) _____________________________ Unsubscribe / Change Profile: = http://ymlp48.com/ugmjwyjqgsgymqesgbumgguwhwh Powered by YourMailingListProvider From owner-freebsd-ports@freebsd.org Tue Jun 28 20:45:03 2016 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 551AAB86F38 for ; Tue, 28 Jun 2016 20:45:03 +0000 (UTC) (envelope-from rodrigo@freebsd.org) Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [IPv6:2a01:e0c:1:1599::10]) (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 24CE72B8A; Tue, 28 Jun 2016 20:45:03 +0000 (UTC) (envelope-from rodrigo@freebsd.org) Received: from [192.168.1.32] (unknown [78.194.61.125]) by smtp1-g21.free.fr (Postfix) with ESMTP id 276F3B00514; Tue, 28 Jun 2016 20:41:32 +0200 (CEST) Subject: Re: pkg SAT_SOLVER bugs To: Baptiste Daroussin References: <20150414200459.GE39658@ivaldir.etoilebsd.net> <20150421103454.GR1394@zxy.spb.ru> <5593D0AE.2010205@selasky.org> <416359ce-1dcd-1160-5c56-f120a0f6358f@selasky.org> <81eaaea2-edc7-9337-0b53-ff6df1c1beca@freebsd.org> <20160627220942.gy7t3klnswmukz6q@ivaldir.etoilebsd.net> Cc: freebsd-ports@freebsd.org From: Rodrigo OSORIO Message-ID: <31cddde4-7c78-a1c6-042a-42b713c20ffc@freebsd.org> Date: Tue, 28 Jun 2016 22:44:52 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <20160627220942.gy7t3klnswmukz6q@ivaldir.etoilebsd.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 20:45:03 -0000 On 06/28/16 00:09, Baptiste Daroussin wrote: > On Mon, Jun 27, 2016 at 11:42:08PM +0200, Rodrigo OSORIO wrote: >> On 06/27/16 12:38, Hans Petter Selasky wrote: >>> Hi, >>> >>> I found some bugs in PKG with regard to the SAT_SOLVER environment >>> variable. Please find patch attached :-) >>> >>> Issues fixed: >>> 1) No need to use hash table when generating SAT rules for external >>> solver. Variables are already in a linear array. Fix encoding and >>> decoding of SAT data. >>> 2) Endless variable loop caused pkg to crash. >>> 3) it->inverse was checked for non-zero, while it should actually be >>> checked for -1 only. SAT rules produces were all negative. >>> >>> How to verify: >>> >>> make -C /usr/ports/math/picosat all install clean >>> >>> env SAT_SOLVER=picosat pkg upgrade >>> >>> --HPS >>> >>> >>> _______________________________________________ >>> freebsd-ports@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-ports >>> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >>> >> >> Thanks! this patch saves my day, I was stuck reinstalling a computer in >> current, and after few rounds using pkg the solver start complaining and >> pretending missing packages was yet installed. >> >> I apply you patch on top of the last version in ports and the patch work as >> a charm. I'll keep testing it until a new version comes. >> >> regards, >> - rodrigo > > that is unrelated, what saved you it that building from ports you switched form > 1.8.5 to 1.8.6 his patch is to solve the use of an external SAT solver which I > admit I haven't tested for a while. > > Pkg 1.8.6 is the default binary package for all release but head right now, > pending for the next build cycle. > > Best regards, > Bapt > Ouch, that hurts but you're right ;) sorry for the unnecessary noise From owner-freebsd-ports@freebsd.org Tue Jun 28 20:52:18 2016 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 EA715B850D6 for ; Tue, 28 Jun 2016 20:52:18 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B6542EFD for ; Tue, 28 Jun 2016 20:52:17 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([77.181.5.243]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0LzKmP-1bMRuC3IeH-014TTG for ; Tue, 28 Jun 2016 22:52:09 +0200 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 5A46C23D856 for ; Tue, 28 Jun 2016 22:52:08 +0200 (CEST) Subject: Re: blanket portmgr approval vs. non-fixing changes To: freebsd-ports@freebsd.org References: <201606261724.u5QHOLdG081392@repo.freebsd.org> <57701AEB.1050001@tu-dortmund.de> <5770A392.6010605@tu-dortmund.de> <84e4fcf5-7b99-1cc6-e6bd-d3c594a5d102@marino.st> <91BC5F8F9FDB9246529D0693@atuin.in.mat.cc> <5770EED4.1070202@tu-dortmund.de> <18e609c1-e095-99b0-893a-0bb30d3c3d45@madpilot.net> From: Matthias Andree Message-ID: <5772E377.1050509@gmx.de> Date: Tue, 28 Jun 2016 22:52:07 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <18e609c1-e095-99b0-893a-0bb30d3c3d45@madpilot.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K0:uDPqCQDFFiFjplBxZdP8N7k22KMmj6ydpqq2zzBX9smRP9nyDFj tl2ZvvKOGBAymqKfZrMdYaYRa3Hnl7dozcdjCLgjo0yQmtFdQTzG4tG939Vrqu/GU5Uj5mI uE3W4Yl7NMJPE+iJUav8Ni134EQryrlhmw67HIToZq9WP/G87LhcGeBKDNzQeqjikw8F/Mm fbbjQTufI74Sj6PewwthA== X-UI-Out-Filterresults: notjunk:1;V01:K0:rOzjBuA6U+s=:H8ac5gz/qIM3drQp0h/BEo cjj44Wer9imzs+QsXwXp3LGIqYzm8RHFomMCnvPjZq0w6l1PssAB0uwnW1VRxLIW95bjcQVks dBDjad2xQQmjm+puqrTccIAYX/0N2DhjttlF8UH8oFSXoUXqdH0nlsDznNvYiMbpMeTrteR+L jIhp3/Fl0JPMa1wRNdA5fP0BX9VR0cZYToYrSw3xCE66kDloF3vZ1XZmGQ3fYaZDYblaUGH7u dAQV2dtE6qnSrWuqYkGHapZBS2p9Ea4IM2uGh20hoYvrHeamN5m5QDsIQZryznXupDe6OmObl ZcaTnqyLwW0ludKEzhVZvsFDTJsoKvUoE/tBVw4KVjgSHABAGV4kgKs5ugYQetgDIbWAejJaG xcTNV143+TfbQGXGzDmX1Vr56yeOKZLLYKqOFzvo98tyaZJyVOiuZMBQbkzo0VVx430+Jen9+ TVJqrPzwGZYn2CA9jYbUmiH6xh2FJo8qj9HRw82ShrdzPZWpLgpp3jkglJYhz4WtdfJNPvXDs iRLYYGSu0RNqsQ59C8goWJAAJh7MoakES/+v9uri5XefM99Ut/KH5uN5X5TUxd2rNFaIY/M1c Uw/NcCkiej1JTNdhWs+kBHmHyCoYCTwPzzAywL/e7HCUKDPTQ7HoO/8MPdczbl7cuzWYeGWWr 1xNaCnb7N6ZNoznf2UQx7hWLbW1deDy4lyIyEtlT81DUMIWVYFltAS6dqQtbbZ7E0J8RlVmbf /eGwrijbCnSWmzt1Nhu8aQqT9XsUSH1GLkdTe0wI9QaAYPFrspKeiyaSCjmrRLmhB3OHwRFeg LenO4Oc X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 20:52:19 -0000 Am 27.06.2016 um 12:02 schrieb Guido Falsi: >> 2. What I was meaning to state was that (and I'll not pick at the >> kind soul who has modernized the port) we should only apply the >> blanket approval if ports have fallen into disrepair. >=20 > I'd say that it's a matter of urgency for the change. Need for > urgency is evident for broken ports and also serious security > issues. >=20 > It could be less evident for infrastructure changes which need to be=20 > urgently deployed to a major number of ports, or changes to head > which require patching a lot of ports (one good example could be the > recent update to libc++ 3.8.0 in head, even if it could be accounted > as "broken ports" case, so with a relatively high degree of > urgency). Yeah - but then again head or -CURRENT is a moving target and by definition non-urgent and maintainers are encouraged, but not formally required, to support it. Generally you're raising a good point, but I'd wager the guess that most of these changes do need more extensive planning anyways and portmgr@ or whoever is driving such a sweeping infrastructure change will want to seek the maintainer's assistance. I'll normally be happy to help with such changes, only not under pressure= . [...] > We are now in a much better situation and most changes are less > urgent, and can wait some time. I'd say usually such changes should > go through bugzilla or phabric review, with portmgr adding special > case blankets for specific changes which should hit the tree as soon > as possible, if this is not an excessive burden on portmgr. On a related note, once in a while I am checking what's on Bugzilla's table only to find that even the stuff that looks easy (maintainer port submission or similar) breaks early or raises my suspicion. Unfortunately that often means I drop a PR and don't really help getting the ports PR cleared. When Miwi and I think Kris proposed me for a commits bit the deal used to be "if the project is find if I mostly tend to my ports"... and not much has changed since. > I'm not sure I agree on lowering the 14 days timeout for bug reports. > I usually reply in a matter of hours if at all possible, 2-3 days > when I take a long time, at least with a "going to test" message, but > not all people can manage this, lowering timeouts could raise the bar > on being a maintainer which is something I think we should avoid. I concur with that. I'll normally respond within 72 hours, often within 24, and sometimes quicker if the urgency catches my eye. A catchy subject on a message Cc:d to my @FreeBSD.org address helps a lot. "SECURITY" is sure to get my attention rather fast. > I think it could be enough to state a list of make targets which one=20 > must warrant keep working, it's obvious that make config, make > install and make deinstall should work correctly, less obvious for > other targets. That would work for me, too, as a first step. From owner-freebsd-ports@freebsd.org Tue Jun 28 20:59:24 2016 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 4ADCFB8523B for ; Tue, 28 Jun 2016 20:59:24 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9D5512198 for ; Tue, 28 Jun 2016 20:59:23 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([77.181.5.243]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0Lbuo0-1bjK5u2EEO-00jLOK for ; Tue, 28 Jun 2016 22:59:14 +0200 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 8A2AC23D856 for ; Tue, 28 Jun 2016 22:59:13 +0200 (CEST) Subject: Re: blanket portmgr approval vs. non-fixing changes To: freebsd-ports@freebsd.org References: <201606271607.u5RG73t8005803@slippy.cwsent.com> From: Matthias Andree Message-ID: <5772E521.4080909@gmx.de> Date: Tue, 28 Jun 2016 22:59:13 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <201606271607.u5RG73t8005803@slippy.cwsent.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K0:tudGt30+v5vaxFuEHKVvKQiRz4b/+wZIzup651fNUnEBbtF6YOf xzcX0zsI+xLorC3Gi54x3zNSAbh+e9R5IMn3tsrlePQAoWXfGHRA9ihKx0FyJnLVQhrsiqi c93zVnApZs5h6xIvgR1JiKdqbvUS7qx03aOdA2nGFONm8aghzCWfxN0CeAtp/Qt3fLs3l9m WxqOd+8mL4avEbx2rUXVw== X-UI-Out-Filterresults: notjunk:1;V01:K0:wMKBSS1erXg=:msTBqNTlRDgxYRP9jBv+6h pqEiVugULYTTEyPmjgTrpVLdJKWM/ChuulEHiFYVz7EP4/PO0LmbuKWGrylLngdbfXv4av7u7 FGpiMjQvTgkV+4iZkF1F8f8Z5eZyrM2gbPmjS2Po/zg268pbdybIn8bNyP9g4/f9F6QJNn2la tgkp2iYv+NP7vK1mcU/2MiibqoVvAQe1lUMHWgge9CFv15Isw/YL0/3lKQPa5bpboIBJ1wcOG PSsAJMZg6mN0zCDujURBSrK0Nl6yMj/a+YBPwnrkx1E3T162u4+gnmpxFuvMVMxqDfcRHSkl0 2DQMkcPSchQUNmMY8ONsk97LaD3ZtM2/4fZM5q+dqWL/kRfeVnUWMgZ/tK0zBYS6cBPhyecw5 yxH+4ZynCgKQ0WJ2oajdTO16vMeEVg9nr5aw1ri3w0iIu0smh7aVztQOhtS+wx82s6M68013d /7Hkncyvcb95N3gONUw6cSRn2Tzon5rLEMZny+igR3XuyPkzMkHbHumA5AIPs2RoROBBlgZAd jPBniiwuMt8XNtNqRcgmh64tlG3KN038o8w2tRMJDWYaOGp7iT5jJfS7RaLwxIYBU9fRQmPZX VcfVzQn0N2oS8mqOhtU+ce2TAO3/JfLVfItdrmM8s551/dOgm8OZcIrzBhGeCGhonbBfGJ+zd VI4wJP3Xxvn2AZ4/39fdUgoj/gJVn5z4tMwNF5Av2OaFALIHSJD0fDnbdAviHVryZXC8RRGdu i/p4RbxCpt7wXz20onJpaZxxmK1Kpk56PqH5L0ziePNRH8HnOibi5UWmqOv+tNQr9a93keQIh 01o259L X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 20:59:24 -0000 Am 27.06.2016 um 18:07 schrieb Cy Schubert: > Mathias, Cy, Mind the double t please. > I'm surprised at your position. I recall a commit you made to one of my= =20 > ports a few years ago, to which I objected. Your position now is a comp= lete=20 > reversal of your arguments then. Quite possible. Things and views change over time. My day job has changed (a few years ago already -- I've been working for a car part supplier for the past almost five years), personal life has changed a bit (less radically), and with it my experience and a sense of how I priorize matters. Some matters I would have found "urgent" earlier now lost this attribute, and I figured that more haste often means more work to clear up some unintended mess, and I value sustainability higher. "Touch things less often." I know some people subscribe to "release early, release often" to get improvements deployed, and I'll consider that to some extent, but not if it goes at the expense of quality or raises the release efforts [1] beyond reason. [1] this includes dealing with PRs, committing to ports, and similar. [Which reminds me I still need to see to getting the self-tests for sysutils/e2fsprogs sorted so that I can commit the upgrade to 1.43.1. We've skipped 1.43 deliberately because it had a few regressions that Ted Ts'o and I have sorted out before 1.43.1.] From owner-freebsd-ports@freebsd.org Tue Jun 28 21:16:11 2016 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 C7969B856EB for ; Tue, 28 Jun 2016 21:16:11 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3AAD52B1A for ; Tue, 28 Jun 2016 21:16:10 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([77.181.5.243]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MRXVc-1ath9k20pU-00Sh8S for ; Tue, 28 Jun 2016 23:16:08 +0200 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id A4CC223D856 for ; Tue, 28 Jun 2016 23:16:07 +0200 (CEST) Subject: Re: blanket portmgr approval vs. non-fixing changes To: freebsd-ports@freebsd.org References: <201606272021.u5RKLVhQ057899@slippy.cwsent.com> <20160628091709.pbvq7lekss2ql2en@ivaldir.etoilebsd.net> From: Matthias Andree Message-ID: <5772E90C.6020908@gmx.de> Date: Tue, 28 Jun 2016 23:15:56 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <20160628091709.pbvq7lekss2ql2en@ivaldir.etoilebsd.net> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="whFBI4hllivU89RVQv0PdCjCSuUpQRqFE" X-Provags-ID: V03:K0:lYUmJJ6YC7erSFQjvUNSjmUscsUxKXoZqsmNXLSrtsU2wAdRy7A CMwWuX+thNJlUoV+Y9CXniT78+5hHAdYpHr8TkaczBF9kte2U2T3nih6PjSCFojRE3l6dGi /vcd5JdwTv8maSQNpsxu0voyEHpXWMRd6WkE98Gm1ImARcUeiGxqPA0MDLfpDR+VWXvnrTA l91EBtKOtEcbyorIa6u4g== X-UI-Out-Filterresults: notjunk:1;V01:K0:ek0/mbnFL7o=:B/lCauXdxPblzerMiv5J4j y3C2aBCFCg3yGo+rmZaCgv40kzh+E0xeslKJrbes5BBEywxO92UrNEtXunmkkka6RUCIfadsf w0k4rOhHVv94rs8L8rsBj8y9d2oqjVZunsNTAO5XG4vMAfkNkKou1mVVh7CiBK2hvWJvmoS0M JZWQnqSE9tdP0m0LDgIqe3xHi7Snhu2IUnOLwwP/YCfCw01GJwip0fE2lTnL6VKomfp8nf9dz YtvvdY22zV4HEkunWCw3Io5ArIYfxVDbP3EUie2RpC2w3Qj15GBoZkFKEkfzf2eVtLCPF9DSa sdQ9dXrzXUOvdfESItBBrlSBPVrOoywmH7tBLtEbuj2dB/VAN6Ah4nmXucGshF1Bn3v0+90ou D8/clomd3Ev53Y3vgRO1UIMH/DCfU7xcNIVhKpcfAOyWvZqAuFH+afc0WGbPcPaOvYjE8it4p jF3nWhtDB1YCtU0AvH6BRZEgjYwrqdvGoc6SiGpNuFVZsnH4trd8HBvQYNDEOeCDtuXlx2eMB QmNVIzJZfRFUSVKa0VSLPgFD12bPYNJBz6+L/ckYsUygyIdtGsk3whWMUl05wKsLC9nnez3DA t64JsmXHiCfIR7pWl8CQRZXWaMWlXH5O7QejqbSLc3lrDoVuGBtkqkhwHPd5YaE6XVfBDdMF2 Wb5ic3URnALADR73ZQbGgGYF/ZKLo2URPTkWcQl1gGswbDsHPKBu2mtvR5q7u9vXXqk6SPimB dh+FeqIWOyfkUsJ9RotX2F4QLHYsl2xIpFKnNv3Sn6HjL8/8YyGvwwiRPrI= X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 21:16:11 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --whFBI4hllivU89RVQv0PdCjCSuUpQRqFE Content-Type: multipart/mixed; boundary="7HfmuKT66Ri6JgaohPdCgU5Ehd1iUpaNM" From: Matthias Andree To: freebsd-ports@freebsd.org Message-ID: <5772E90C.6020908@gmx.de> Subject: Re: blanket portmgr approval vs. non-fixing changes References: <201606272021.u5RKLVhQ057899@slippy.cwsent.com> <20160628091709.pbvq7lekss2ql2en@ivaldir.etoilebsd.net> In-Reply-To: <20160628091709.pbvq7lekss2ql2en@ivaldir.etoilebsd.net> --7HfmuKT66Ri6JgaohPdCgU5Ehd1iUpaNM Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Am 28.06.2016 um 11:17 schrieb Baptiste Daroussin: > What you are asking is part of the blanket in particular when changing = things in > individual ports, we expect committers to have a look at pending PR (ye= s I know > I have been guilty of individual port change without sometime checking = about > pending PR which was wrong from my side) >=20 > For sweeping changes this is a bit different as when a change touches a= large > portion of the tree we can not expect the committer to have a look at e= ach > individual ports. Baptiste, to give you a provoking counter example: By that logic, I would not have been expected to notice that the bitcoin garbage insisted on db48, I could just have killed it off and moved the bitcoin ports onto db5. (That's stretching it a bit because there was Peter Wemm's objection to the DEPRECATED=3D tag on record alrea= dy.) Meaning that, in this thread: I beg to differ on sweeping changes. These do need a thorough review, and often a series of -exp runs, to keep the number of casualties low. If I had gone by this policy of sweeping changes, we'd nuked all DB2, DB3 and DB4 ports and had force moved all the bitcoin and openldap ports and whatnot onto db5 without consulting anyone, and I guess we'd heard a lot more screaming than with the approach I chose, meaning look at several dozen of ports before committing the breaking and sweeping changes. And I do think we should, opposite to what you are proposing, make the committer spend extra time for high-profile ports that entail sweeping changes to chase down the breaking change to, say, a library port. Cheers, Matthias --7HfmuKT66Ri6JgaohPdCgU5Ehd1iUpaNM-- --whFBI4hllivU89RVQv0PdCjCSuUpQRqFE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXcukXAAoJEOQSsVbv84VaKYEP/2noIt6iBu2fvaa+WJ5Uzouu P1P9Qny0MkAVQWIY0NJuNyuJWub00aKxK0eR8qmJnqM94N9GQFOP+WxJCSEJKlKC lrA/ODzSPpQhqQlqxlsjUdVRYVO6knyNbrYqiBby8Y7IY/ZaAXp7SqbAZTFym4PQ Lzbdx0wWeejO30dx5kPCLaaIs9CEdl5LTQQdU/D26xPCkI0caniknwISL+kAO2HO 1O/AiPHGLdMAf++j7/0G6DnR9ggHtMCL4Wovt6XhznitQT0U+0r+kNGbKZ2RsE2F qb1mx/Dv3eeucu/Nc9E4jcUgBKmvGD5xavu8/r3sMzdqHhjHy9NAW6u1A8sDegRS 9nwg59md5Y/Wf525zgTRoTYkDMlSsjFeEBEx+TBiEzVW5R+4I7tvce3EMRm3C+Ae ocaxw0Sbi5j/yqhxqyVQzXmmHq2I9P5EWtHDaacfldT72R9iMykrFZedpo+E19i8 8GvvT+O44q4q3jf/xrzgF77V4PjRYmlImcnokPHfcD452pTtcCBtoGJaRaYxY4Nq yjdi1jKi/7uOSfSe3KOYyR6C0dbrfSfC6BXphZ5gh9ild3R2bjEQxJPz4Ev8zVCD GjuDVI789qJvXS9Nk1c+oGFIXiUhamn98QswUgoDFMZA6OdBJ4G3cCIzo7BUn5sQ fECvc/CyPDYPamJtbGmJ =Qy22 -----END PGP SIGNATURE----- --whFBI4hllivU89RVQv0PdCjCSuUpQRqFE-- From owner-freebsd-ports@freebsd.org Tue Jun 28 21:33:46 2016 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 17CE7B85C2C for ; Tue, 28 Jun 2016 21:33:46 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A258D2482 for ; Tue, 28 Jun 2016 21:33:45 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id f126so156585137wma.1 for ; Tue, 28 Jun 2016 14:33:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=JzFhEWuWM8lub9lqMPRhQ7HVHnCOxA2iRUD/6FmAFSg=; b=b2IKJ+YfGdFn3T8FADmcrL+HxlVYPl3MTTTojegaEZw5Eu/7JDuh6FQSjbF+0irt6c TyyWneyPipoSyFdMOZm6d7HtI4AVMRLzNktWCU8DJbeg4FL8VPoJm1rsU2PZ2ZEDIWIy 98cAWsWuH5BE6w9Ov0G6VF3klaexb+921us4WcpYCR7wLyWikiTAWmO+QH0c4Gk9K2v5 1c2J3oywniNnalVNr3GagkSpMccWaBkHVwOddm3rLftykPIlJSzLUMOPK8Yjl1NMFs0X h0qqD258wriiiskOlTfwTuE+8kAFnPkSuFBJzwlC5VnwI+PTOFuM7RqDxVygiiujAJgV MsEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=JzFhEWuWM8lub9lqMPRhQ7HVHnCOxA2iRUD/6FmAFSg=; b=UwYg/rbHL2zBIeOn3KFtxMfwkABfJPL/rR2R8C78O9EqEQaETG6+Cl9GfvcMm5WqGl Eq59ZXmB6nE+C9ETfp769mO3FPtasMdlKKfePm7plYlti6w3UXoc0Xm3QFyQDErZoOQy XleDeCtmQSUL2xS3ThDfR3zkxrrK30f3XVSuDqd7NZxuOQXxp1GpchZUgrpLuCR838sB ESuzne9E7HYRDdKLKoRU1ZZptuVcq+E6iG2x0T19lxbNEWrSGLsdwXdOdxvlM1VU4uVH zxqV+YIzsI4xTeksBJoHgyBOcLSthGHV83+rjmS6m6qt5XPSp23LWWTeVLqADVw2CY8G 7TIg== X-Gm-Message-State: ALyK8tJLbzZZENNgkhqGL5kXY/cyxYcl0+koFv76C6w+Woza0oyoBAmyKKlzUA570zvMDw== X-Received: by 10.28.189.215 with SMTP id n206mr18532201wmf.76.1467149623314; Tue, 28 Jun 2016 14:33:43 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id f140sm796077wmf.22.2016.06.28.14.33.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Jun 2016 14:33:42 -0700 (PDT) Sender: Baptiste Daroussin Date: Tue, 28 Jun 2016 23:33:41 +0200 From: Baptiste Daroussin To: Matthias Andree Cc: freebsd-ports@freebsd.org Subject: Re: blanket portmgr approval vs. non-fixing changes Message-ID: <20160628213341.vvtobzbvxabphsqc@ivaldir.etoilebsd.net> References: <201606272021.u5RKLVhQ057899@slippy.cwsent.com> <20160628091709.pbvq7lekss2ql2en@ivaldir.etoilebsd.net> <5772E90C.6020908@gmx.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="q7x72cz5lllomj2d" Content-Disposition: inline In-Reply-To: <5772E90C.6020908@gmx.de> User-Agent: Mutt/1.6.1-neo (2016-06-11) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 21:33:46 -0000 --q7x72cz5lllomj2d Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 28, 2016 at 11:15:56PM +0200, Matthias Andree wrote: > Am 28.06.2016 um 11:17 schrieb Baptiste Daroussin: >=20 > > What you are asking is part of the blanket in particular when changing = things in > > individual ports, we expect committers to have a look at pending PR (ye= s I know > > I have been guilty of individual port change without sometime checking = about > > pending PR which was wrong from my side) > >=20 > > For sweeping changes this is a bit different as when a change touches a= large > > portion of the tree we can not expect the committer to have a look at e= ach > > individual ports. >=20 > Baptiste, >=20 > to give you a provoking counter example: >=20 > By that logic, I would not have been expected to notice that the > bitcoin garbage insisted on db48, I could just have killed it off and > moved the bitcoin ports onto db5. (That's stretching it a bit because > there was Peter Wemm's objection to the DEPRECATED=3D tag on record alrea= dy.) >=20 >=20 > Meaning that, in this thread: I beg to differ on sweeping changes. >=20 > These do need a thorough review, and often a series of -exp runs, to > keep the number of casualties low. If I had gone by this policy of > sweeping changes, we'd nuked all DB2, DB3 and DB4 ports and had force > moved all the bitcoin and openldap ports and whatnot onto db5 without > consulting anyone, and I guess we'd heard a lot more screaming than with > the approach I chose, meaning look at several dozen of ports before > committing the breaking and sweeping changes. >=20 > And I do think we should, opposite to what you are proposing, make the > committer spend extra time for high-profile ports that entail sweeping > changes to chase down the breaking change to, say, a library port. >=20 I might have been not explicit enough, of course any changes should be test= ed, and of course high profile ports breaking means special attention and preve= nt the sweeping change to actually happen. Read the context... here we were speaking of changes that adds extra works = for=20 maintainers on individual ports and the fact that someone should check for = PR on everysingle port that are going to be touched. In that case on a sweeping c= hange like what mat did for removal of ${PORTSDIR} you cannot expect the committe= r to check everysingle ports for pending PR, but of course you can expect that f= or every single change sweep or not the committer has to test all the ports to= uched by the change to ensure they do not break. Bapt --q7x72cz5lllomj2d Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXcutPAAoJEGOJi9zxtz5aBngP/3FlXV6FepjWuXM/VxJbPYXm 0JgfCJ3hOvp7PSKVpL0+KeXrqraVWzyQNNtmMDNn1ZK0JUbrEYJpzw2MNkZ5G2pT Ef30/lCwnqktxpWGtxP9oZJHyxPXr325LLrlRoRt6YxzYFgfPMMUOxueEmaUUeOi dh7Nw4wDRu24d3mNVKpY28dbmo6AwPifZ/0bdWGCk3pKaGzQVW5r0aCL9+2pu5XS JAkI4dCZRNWsjqXFQiqeYxrb8J2GYby7ii2jny+g8op6eEig/IVkkenZnbTmVQnT S3cd3ea3Hj5pXzTzbLrATnErAR1tEfxG1X28ECh9ZFYVMZ5r99SbOdTsS93PoSgj 7ESicGpXbOhhafmnM6KvOvUbIR5MwiQ8Ew6ZDYFCJDVA37zkl12pDyQ6TJrhDYgT 1dNnv8+BESFDAV9eiXARwgSCnWvFRUz24/mIveeIWjcJ4+/SXiql3sItZPVg0qpP Oj6jC5vHWd9qgG2waqEiXlXBewKKIMIFCO+IacJh/PlEFSXuCr6y8TL+hdC+Duk0 vcfuVPLBQcqD4uctbGGXdzrhzLtCYgG42AQ6a+0eDhdc19BNwKdRwNNbH7iNR93t rfi526hkJDQJXFLOyvPaEjc8TZnjTSiTd0koOGQunDCVar+qBnr/IzFDKJR0hbsr zFdydnQtBHdfKPT5cTjm =zZ6H -----END PGP SIGNATURE----- --q7x72cz5lllomj2d-- From owner-freebsd-ports@freebsd.org Tue Jun 28 22:27:03 2016 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 43A7BB867D9 for ; Tue, 28 Jun 2016 22:27:03 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (flets-sg1027.kamome.or.jp [202.216.24.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BF0ED2BC9 for ; Tue, 28 Jun 2016 22:27:01 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (kx.openedu.org [103.15.187.19]) by kx.openedu.org (8.14.5/8.14.5) with ESMTP id u5SMCDQU079882 for ; Wed, 29 Jun 2016 07:12:13 +0900 (JST) (envelope-from kiri@kx.openedu.org) Message-Id: <201606282212.u5SMCDQU079882@kx.openedu.org> Date: Wed, 29 Jun 2016 07:12:13 +0900 From: KIRIYAMA Kazuhiko To: freebsd-ports Subject: Is there still broken lang/ruby23 ? User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.6 MULE XEmacs/21.4 (patch 22) (Instant Classic) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jun 2016 22:27:03 -0000 Hi, Is there still broken lang/ruby23[1]. Or can build in latest 11.0-* ? [1] http://permalink.gmane.org/gmane.os.freebsd.devel.pkg-fallout/294364 --- KIRIYAMA Kazuhiko From owner-freebsd-ports@freebsd.org Wed Jun 29 00:43:45 2016 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 EE51EB8134B for ; Wed, 29 Jun 2016 00:43:45 +0000 (UTC) (envelope-from alfred@freebsd.org) 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 DDD95205B for ; Wed, 29 Jun 2016 00:43:45 +0000 (UTC) (envelope-from alfred@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id DCF69B81349; Wed, 29 Jun 2016 00:43:45 +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 DC974B81348 for ; Wed, 29 Jun 2016 00:43:45 +0000 (UTC) (envelope-from alfred@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id D04A7205A; Wed, 29 Jun 2016 00:43:45 +0000 (UTC) (envelope-from alfred@freebsd.org) Received: from AlfredMacbookAir.local (unknown [IPv6:2601:645:8003:a4d6:d0d1:6b95:f41e:a128]) by elvis.mu.org (Postfix) with ESMTPSA id 75014346DE8D; Tue, 28 Jun 2016 17:43:44 -0700 (PDT) Subject: Re: best way to tune ports to add a CLFAGS entry To: Julian Elischer , "ports@FreeBSD.org" References: <7d454696-f910-7533-5757-74eb624f9315@freebsd.org> From: Alfred Perlstein Organization: FreeBSD Message-ID: <577319BF.5040403@freebsd.org> Date: Tue, 28 Jun 2016 17:43:43 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <7d454696-f910-7533-5757-74eb624f9315@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 00:43:46 -0000 On 6/28/16 9:52 AM, Julian Elischer wrote: > At work I am doing various cross compiles in order to make a product > under freebsd that actually will run under a modified FreeBSD that > runs on an appliance. We want to get away from hand rolling everything > to leverage all teh work in getting ports working well on FreeBSD. > > We have some extra syscalls and some structures have different sizes, > so we need to compile/link agains an alternate set of > includes/libraries and not those in /usr/include or /usr/lib. > > Ideally I want to use the "--sysroot" and "-isystem" options to the > compiler/linker or failing that, add a -I or -L entries to make it > look at the correct includes and libraries, not those in the base system. > > > In many ports CFLAGS etc. are sent in via the arguments to ./configure > or environment vars, but there are many other ports that have other > ways to specify these. > > Does the ports framework have any standard way to do this? > LDEXTRA_ARGS or EXTRA_CFLAGS or similar? > > I've looked around and can't really see anything. Best would be a > single file to which I could add these things but adding them to the > environment would also work. > > yours in ports ignorance.. Sounds like a decent idea to override includedirs, but I wouldn't trust it. :) Why not do what NANOBSD/FreeNAS do and compile inside a chroot (or even VM) with the proper includes and such installed? It sounds like a big sledgehammer to use a chroot or a VM, but in reality it's MUCH safer than some port accidentally pulling something from the wrong /usr/include and then you spending hours, days, etc tracking it down. Trust me, I've seen the fallout and it's NOT FUN!!! For FreeNAS we made it so that you could run the FreeNAS OS (trueos) as the actual build server and that saved us a huge number of headaches. If you're very, very against the idea of VM or chroot then you could just make /usr/include actually contain YOUR includes as you probably shouldn't need them otherwise on a build server. -Alfred -Alfred From owner-freebsd-ports@freebsd.org Wed Jun 29 01:19:06 2016 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 6AA07B81A53 for ; Wed, 29 Jun 2016 01:19:06 +0000 (UTC) (envelope-from junovitch@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 60B552E76; Wed, 29 Jun 2016 01:19:06 +0000 (UTC) (envelope-from junovitch@FreeBSD.org) Received: from Silverstone (localhost [IPv6:::1]) by freefall.freebsd.org (Postfix) with ESMTP id BBA581FF9; Wed, 29 Jun 2016 01:19:05 +0000 (UTC) (envelope-from junovitch@FreeBSD.org) Date: Tue, 28 Jun 2016 21:19:04 -0400 From: Jason Unovitch To: David Wolfskill Cc: freebsd-ports@freebsd.org Subject: Re: Unexpected output from "pkg updating -d 20160626" Message-ID: <20160629011859.GA30167@Silverstone> References: <20160628114433.GF1358@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160628114433.GF1358@albert.catwhisker.org> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 01:19:06 -0000 On Tue, Jun 28, 2016 at 04:44:33AM -0700, David Wolfskill wrote: > As part of my daily update of FreeBSD on my laptop, on the first reboot > after installing the freshly-built kernel & world, I use portmaster to > update any installed ports that have been updated since I last updated. > > This morning, for the first time in ... months, I think, the "pkg > updating -d ..." command I run to start the process actually generated > some output -- quite a bit of it. > > But I'm at a loss to understand why it did: only one of the ports it > mentioned is installed, and that one didn't get updated by "portmaster > -ad"; the others aren't installed at all. > > My ports working copy is ports/head, at r417708. > > I'm running: > FreeBSD g1-252.catwhisker.org 10.3-STABLE FreeBSD 10.3-STABLE #406 r302244M/302246:1003505: Tue Jun 28 04:11:52 PDT 2016 root@g1-252.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY amd64 > > now; when I ran "pkg updating -d ...", I was running: > FreeBSD g1-252.catwhisker.org 10.3-STABLE FreeBSD 10.3-STABLE #405 r302220M/302222:1003504: Mon Jun 27 04:03:47 PDT 2016 root@g1-252.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY amd64 > > and pkg reports: > g1-252(10.3-S)[2] pkg --version > 1.8.6 > > The "pkg updating" command I issued was: pkg updating -d 20160626 Hello David, I did replicate this and it seemed related to a handful of recent UDPATING entries that were made without a trailing colon after the date. I normalized all the entries for consistency and am seeing `pkg updating -d 20160626` return the expected output for me. Please see if that resolved the issue for you as well. Jason From owner-freebsd-ports@freebsd.org Wed Jun 29 01:27:02 2016 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 6A984B81D2B for ; Wed, 29 Jun 2016 01:27:02 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 2072E2292; Wed, 29 Jun 2016 01:27:01 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id u5T1QxII035217; Wed, 29 Jun 2016 01:26:59 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id u5T1Qxb1035216; Tue, 28 Jun 2016 18:26:59 -0700 (PDT) (envelope-from david) Date: Tue, 28 Jun 2016 18:26:59 -0700 From: David Wolfskill To: Jason Unovitch Cc: freebsd-ports@freebsd.org Subject: Re: Unexpected output from "pkg updating -d 20160626" Message-ID: <20160629012659.GY1358@albert.catwhisker.org> Reply-To: freebsd-ports@freebsd.org References: <20160628114433.GF1358@albert.catwhisker.org> <20160629011859.GA30167@Silverstone> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="LshPJsoFywXB25Uq" Content-Disposition: inline In-Reply-To: <20160629011859.GA30167@Silverstone> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 01:27:02 -0000 --LshPJsoFywXB25Uq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 28, 2016 at 09:19:04PM -0400, Jason Unovitch wrote: > ... > > The "pkg updating" command I issued was: pkg updating -d 20160626 >=20 > Hello David, > I did replicate this and it seemed related to a handful of recent > UDPATING entries that were made without a trailing colon after the date. > I normalized all the entries for consistency and am seeing `pkg updating > -d 20160626` return the expected output for me. Please see if that > resolved the issue for you as well. >=20 > Jason Aye; it did -- thank you for figuring out what was catalyzing it! :-) Oddly enough, my build machine (which I keep in lock-step with my laptop, except that it runs a GENERIC kernel) hadn't experienced the symptom; on the other hand, it has very few ports installed. Peace, david --=20 David H. Wolfskill david@catwhisker.org Those who would murder in the name of God or prophet are blasphemous coward= s. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --LshPJsoFywXB25Uq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJXcyPjXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4X7m0IAMs15kVw1cEvaAVPS7SQxj4v wNcrm+/s1SVU6OF78d9xyCN7+lPcKxFh6sYeXKUmsks4IsCX3WrreJKTxd5aQg7O 7fGSPZs64aONKWmIIhfSjYb5fJWQWNyyR2vdpjG+6Utmh9VsTpxK8jEEikKAXagv F0mdXGJCvPo418QTTjT0Cd6oY6IUPDi/YFx+SbyLujNoXXtjupGfuF20B6wHpsoJ g0Yq6aA5i9dnL863/qoM5+Ym+2P80MQ6bJb+RMqR8N1n42UA2+FCGCLS1LdVfjTc iZ+MPSApvy2LQdc2fUh8H64mr0FrdrzFHZlEe52WVQgYg14ICzalg0QPV1MR1bg= =gEh+ -----END PGP SIGNATURE----- --LshPJsoFywXB25Uq-- From owner-freebsd-ports@freebsd.org Wed Jun 29 02:14:12 2016 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 96BA6B8626F for ; Wed, 29 Jun 2016 02:14:12 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 60C912811 for ; Wed, 29 Jun 2016 02:14:12 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from [0.0.0.0] (cpe-071-065-239-148.nc.res.rr.com [71.65.239.148] (may be forged)) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id u5T2DkPs077377 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 29 Jun 2016 02:14:02 GMT (envelope-from swills@FreeBSD.org) Subject: Re: Is there still broken lang/ruby23 ? To: KIRIYAMA Kazuhiko , freebsd-ports References: <201606282212.u5SMCDQU079882@kx.openedu.org> From: Steve Wills Message-ID: <407b9391-86f0-4305-8bc3-3d5b21aacab3@FreeBSD.org> Date: Tue, 28 Jun 2016 22:13:44 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <201606282212.u5SMCDQU079882@kx.openedu.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Wed, 29 Jun 2016 02:14:04 +0000 (UTC) X-Spam-Status: No, score=2.8 required=4.5 tests=HELO_MISC_IP, RCVD_ILLEGAL_IP, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.99.1 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 02:14:12 -0000 Yes, I haven't looked at it yet, but if you want to take a look, I'd welcome patches. Steve On 06/28/16 06:12 PM, KIRIYAMA Kazuhiko wrote: > Hi, > > Is there still broken lang/ruby23[1]. Or can build in latest > 11.0-* ? > > [1] http://permalink.gmane.org/gmane.os.freebsd.devel.pkg-fallout/294364 > > --- > KIRIYAMA Kazuhiko > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@freebsd.org Wed Jun 29 04:00:15 2016 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 3831BB855EE for ; Wed, 29 Jun 2016 04:00:15 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) 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 2622D2516 for ; Wed, 29 Jun 2016 04:00:15 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: by mailman.ysv.freebsd.org (Postfix) id 25746B855ED; Wed, 29 Jun 2016 04:00:15 +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 22C6FB855EC for ; Wed, 29 Jun 2016 04:00:15 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C0D272514; Wed, 29 Jun 2016 04:00:13 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id u5T4138u092653; Tue, 28 Jun 2016 21:01:10 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: "ports@FreeBSD.org" , Julian Elischer In-Reply-To: <7d454696-f910-7533-5757-74eb624f9315@freebsd.org> References: <7d454696-f910-7533-5757-74eb624f9315@freebsd.org> From: "Chris H" Subject: Re: best way to tune ports to add a CLFAGS entry Date: Tue, 28 Jun 2016 21:01:10 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <4965d81328da090eb4f0a555af67ea77@ultimatedns.net> Content-Transfer-Encoding: 8bit X-Milter: Spamilter (Reciever: udns.ultimatedns.net; Sender-ip: 127.0.0.1; Sender-helo: ultimatedns.net; ) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 04:00:15 -0000 On Wed, 29 Jun 2016 00:52:51 +0800 Julian Elischer wrote > At work I am doing various cross compiles in order to make a product > under freebsd that actually will run under a modified FreeBSD that > runs on an appliance. We want to get away from hand rolling everything > to leverage all teh work in getting ports working well on FreeBSD. > > We have some extra syscalls and some structures have different sizes, > so we need to compile/link agains an alternate set of > includes/libraries and not those in /usr/include or /usr/lib. > > Ideally I want to use the "--sysroot" and "-isystem" options to the > compiler/linker or failing that, add a -I or -L entries to make it > look at the correct includes and libraries, not those in the base system. > > > In many ports CFLAGS etc. are sent in via the arguments to ./configure > or environment vars, but there are many other ports that have other > ways to specify these. > > Does the ports framework have any standard way to do this? > LDEXTRA_ARGS or EXTRA_CFLAGS or similar? > > I've looked around and can't really see anything. Best would be a > single file to which I could add these things but adding them to the > environment would also work. > > yours in ports ignorance.. > Hi Julian. While I can't answer your question directly. Maybe a USES=FAKE_INCLUDE, USES=FAKE_LIB? No. I haven't implemented it. Just throwing it out there, while it occurs to me. If someone doesn't beat me to it. I'd like to look into the feasibility of something like this, to accommodate something along the lines of what you're asking about. I often shy away from tasks I'd like to undertake, because it seems like too much work to cobble up just the right environment to accomplish it. But if I could make a universal convenience knob like I mention above. It'd be perfect. Tho I haven't thought it completely through. I like the sound of it. :-) Apologies, for stepping on your thread. Hope you don't mind. > > Julian > > --Chris From owner-freebsd-ports@freebsd.org Wed Jun 29 05:46:10 2016 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 E8144B84AC5; Wed, 29 Jun 2016 05:46:10 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A357F2F77; Wed, 29 Jun 2016 05:46:10 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-vk0-x22d.google.com with SMTP id j3so52112242vkb.0; Tue, 28 Jun 2016 22:46:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Sfb08UBTUV6cLvNA2ccs05FExVj5zWh2bZTyFSFzcRY=; b=v/DB9rP974/4pFRrFGqAjEbru1Mvg9tBYRXLge17qrukp8xezgkEHCkeeLv8MLC+M7 GhgaifkinUXPjoYzPLW8fwbcQWz7c+7LQORUQQgVyieQXYx/yK48O0KZIun4qBY8AvNA 6dIfGWZrNem3BO/JENlV4qS2mnH0XHRG9AXf8EF2gLkMpSS84QGMjsig+2wcKv0mzNIk O9zV5I0InApoOpxGNhNPhAP/hMgY999RhHQQwN1oTTlGVl6EYktg0EmfVHTE3jgdmAK1 mREF99rCQ0qRg0uf32+40O+QG5HWyZ2M6CyaitSyiY4IjyxAJC9iF2h4AVDZJNZ6yw/V mA8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Sfb08UBTUV6cLvNA2ccs05FExVj5zWh2bZTyFSFzcRY=; b=SJjEDTl0bGvkTr0EvWCdwdutdHwzgZUbDly+BDfAJ+bSK0VchrU6No0GhPeZbbL0CJ YaByJMxtZxSHWR89KP6TKpFBnBRmuGthrte+nU4QeabSEHIioIE/wC7aPtxVQ746aM4u m8kWfGBVIGkOkHVnXiykBVMVZj0UjbaaPol1YvXVpjnyPnNY+7zDNK07/rdDbYmjAsd0 7XXio2shq39EBy4p3WFlSf2byQF5RUblFXSRqlDQ2VhMi2CRYzxroYR/r2j6tbDb+QGt B1sZyOdvRoBHCKW+o8KwxQ0bFu18lqjrPgZvVFVIyEoRLOm+0B+/z+/uyLdBdh6D14+P nYRg== X-Gm-Message-State: ALyK8tJW1Pcxec9pPvr3LQC0DuRsozQMKStkPOU3nGqRaMzcxjb2d06KZ3nX6om3EFotHFCY2Z1N2tFqHbLZug== X-Received: by 10.159.34.104 with SMTP id 95mr2773452uad.86.1467179169626; Tue, 28 Jun 2016 22:46:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.54.196 with HTTP; Tue, 28 Jun 2016 22:46:09 -0700 (PDT) In-Reply-To: <20160628094307.bepxy46dp5igizeh@ivaldir.etoilebsd.net> References: <20160628094307.bepxy46dp5igizeh@ivaldir.etoilebsd.net> From: Russell Haley Date: Tue, 28 Jun 2016 22:46:09 -0700 Message-ID: Subject: Re: Maintaining mono/.net To: Baptiste Daroussin Cc: freebsd-ports@freebsd.org, Freebsd-mono Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 05:46:11 -0000 On Tue, Jun 28, 2016 at 2:43 AM, Baptiste Daroussin wrote: > On Mon, Jun 27, 2016 at 11:06:02AM -0700, Russell Haley wrote: >> Hello Ports Team, >> >> A couple of us on the freebsd-mono@ mailing list are having a >> discussion on how best to maintain the mono ports/.net ports. One of >> the things that has come up is maintaining the patches for "all this >> stuff". The current paradigm in FreeBSD as I understand it is to use >> the files directory and apply the patches to the port via svn/ports >> tree. However, with the ubiquity of GitHub in opensource, it now seems >> to be feesable to simply create a Github accound to maintain a bunch >> of forked repositories (which is essentially a patched git >> repository!). This makes it easier to create and apply patches and >> gives us the natural path to push things back upstream. In the end, we >> would just pull from the FreeBSD specific repository, which is no >> different than, say, pulling from the mono project directly. >> >> This email is a request for response from anyone on the ports team (or >> FreeBSD general) to give some input as to the acceptability of this >> solution, as well as any "gotchas" we haven't thought of yet. Thanks >> in advance! >> > There are absolutely nothing against this. Actually some ports were already > doing that before the github era :D > > The only difficulty the history told us is : when active people get less active > for various reasons you need to make sure enough people continues to get access > to the said repo. > > Tracking upstream updates because more complicated for people not in the team > (we already saw in the past ports stucked for more than 5/6 years actions being > taken (maintainer of the forked becoming mostly MIA) > > It also depends how many patches you end up with, I haven't checked the > mono/.net ports but if that is just a bunch of small patches then the overhead > is not worth the pain, if there are lots of patches then sure maintaining your > repo is simpler. > > Depending on how active you (the team) are and how close to the upstream you are > one can also see those repositories as "temporary" until all the amount of > patches are upstreamed and when done the ports can switch back to the official > distfiles (this is always a goal for ports upstreaming all our patches so we can > remain as close as possible from the vanilla sources) > > That said I do applause the effort. As a conclusion do what ever you think is > the easiest mechanism for you as long as things like monodevelop and friends can > be pushed in a working state again. > > Best regards, > Bapt Thanks for the input everyone. I think the overhead of keeping volatile patches in a globally accessible area is worth while. One of the things I struggled with historically is how to share my local changes that I couldn't commit to the svn tree. I have created an open source organization called FreeBSD-DotNet in Github. I have differentiated from the Mono moniker because the merging of the frameworks is inevitable with the purchase of Xamarian. I went a little crazy and forked a whole bunch of stuff, which I now think is a bad idea. The only thing that currently requires customization would be the ports tree itself (MonoDevelop doesn't build yet, but I haven't needed to change any code). However, I think we can put a bunch of how-to and wiki stuff in there for the development efforts. SO, with that: Anyone wishing to join the FreeBSD-DotNet organization can go to https://github.com/FreeBSD-DotNet and send a request. I'll try to flesh out an outstanding items list that can be ratified sometime in the next couple of weeks. Thanks, Russ From owner-freebsd-ports@freebsd.org Wed Jun 29 06:12:33 2016 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 B90B2B86084 for ; Wed, 29 Jun 2016 06:12:33 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id A5A182C98 for ; Wed, 29 Jun 2016 06:12:33 +0000 (UTC) (envelope-from julian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id A4C02B86083; Wed, 29 Jun 2016 06:12:33 +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 A2201B86082 for ; Wed, 29 Jun 2016 06:12:33 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C1A92C96; Wed, 29 Jun 2016 06:12:32 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-236-103.lns20.per1.internode.on.net [121.45.236.103]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u5T6CQTc027648 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 28 Jun 2016 23:12:30 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: best way to tune ports to add a CLFAGS entry To: Alfred Perlstein , "ports@FreeBSD.org" References: <7d454696-f910-7533-5757-74eb624f9315@freebsd.org> <577319BF.5040403@freebsd.org> From: Julian Elischer Message-ID: Date: Wed, 29 Jun 2016 14:12:20 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <577319BF.5040403@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 06:12:33 -0000 On 29/06/2016 8:43 AM, Alfred Perlstein wrote: > > > On 6/28/16 9:52 AM, Julian Elischer wrote: >> At work I am doing various cross compiles in order to make a >> product under freebsd that actually will run under a modified >> FreeBSD that runs on an appliance. We want to get away from hand >> rolling everything to leverage all teh work in getting ports >> working well on FreeBSD. >> >> We have some extra syscalls and some structures have different >> sizes, so we need to compile/link agains an alternate set of >> includes/libraries and not those in /usr/include or /usr/lib. >> >> Ideally I want to use the "--sysroot" and "-isystem" options to the >> compiler/linker or failing that, add a -I or -L entries to make it >> look at the correct includes and libraries, not those in the base >> system. >> >> >> In many ports CFLAGS etc. are sent in via the arguments to >> ./configure or environment vars, but there are many other ports >> that have other ways to specify these. >> >> Does the ports framework have any standard way to do this? >> LDEXTRA_ARGS or EXTRA_CFLAGS or similar? >> >> I've looked around and can't really see anything. Best would be a >> single file to which I could add these things but adding them to >> the environment would also work. >> >> yours in ports ignorance.. > > Sounds like a decent idea to override includedirs, but I wouldn't > trust it. :) > > Why not do what NANOBSD/FreeNAS do and compile inside a chroot (or > even VM) with the proper includes and such installed? we DO compile in a chroot. but that still requires that the local binaries use one set of .so files and the generated ones use a different set.. I do have ways around it.. like "rm -rf /usr/include/sys; ln -sfh /usr/product/sys/sys /usr/include/sys" > > It sounds like a big sledgehammer to use a chroot or a VM, but in > reality it's MUCH safer than some port accidentally pulling > something from the wrong /usr/include and then you spending hours, > days, etc tracking it down. Trust me, I've seen the fallout and > it's NOT FUN!!! oh I have too.. tha't why I'm using a chroot, bur we dont' want to generate a new chroot for every sub-point-release, and have to store it away forever, so I'm making the chroots be "semi permanent" which means that differences arize between them and the sources as we diverge, and before we build another chroot.. > > For FreeNAS we made it so that you could run the FreeNAS OS (trueos) > as the actual build server and that saved us a huge number of > headaches. > yes I agree that would be nice but there are a large number of legacy issues at play so a cross-build style work flow is what I can get to. > If you're very, very against the idea of VM or chroot then you could > just make /usr/include actually contain YOUR includes as you > probably shouldn't need them otherwise on a build server. yeah I'm kind of doing that already.. IN the chroot.. wish I didn't have to. the chroot system binaries are pretty much -RELEASE binaries. but we use them to generare FOO-OS binaries which have to link to other .so files. > -Alfred > > > > > -Alfred > From owner-freebsd-ports@freebsd.org Wed Jun 29 06:17:07 2016 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 2E4F1B8611B for ; Wed, 29 Jun 2016 06:17:07 +0000 (UTC) (envelope-from julian@freebsd.org) 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 1A0722E1A for ; Wed, 29 Jun 2016 06:17:07 +0000 (UTC) (envelope-from julian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 15A4EB8611A; Wed, 29 Jun 2016 06:17:07 +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 153B8B86119 for ; Wed, 29 Jun 2016 06:17:07 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C460F2E19 for ; Wed, 29 Jun 2016 06:17:06 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-236-103.lns20.per1.internode.on.net [121.45.236.103]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u5T6GjhW027660 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 28 Jun 2016 23:16:47 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: best way to tune ports to add a CLFAGS entry To: Chris H , "ports@FreeBSD.org" References: <7d454696-f910-7533-5757-74eb624f9315@freebsd.org> <4965d81328da090eb4f0a555af67ea77@ultimatedns.net> From: Julian Elischer Message-ID: Date: Wed, 29 Jun 2016 14:16:39 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <4965d81328da090eb4f0a555af67ea77@ultimatedns.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 06:17:07 -0000 On 29/06/2016 12:01 PM, Chris H wrote: > On Wed, 29 Jun 2016 00:52:51 +0800 Julian Elischer wrote > >> At work I am doing various cross compiles in order to make a product >> under freebsd that actually will run under a modified FreeBSD that >> runs on an appliance. We want to get away from hand rolling everything >> to leverage all teh work in getting ports working well on FreeBSD. >> >> We have some extra syscalls and some structures have different sizes, >> so we need to compile/link agains an alternate set of >> includes/libraries and not those in /usr/include or /usr/lib. >> >> Ideally I want to use the "--sysroot" and "-isystem" options to the >> compiler/linker or failing that, add a -I or -L entries to make it >> look at the correct includes and libraries, not those in the base system. >> >> >> In many ports CFLAGS etc. are sent in via the arguments to ./configure >> or environment vars, but there are many other ports that have other >> ways to specify these. >> >> Does the ports framework have any standard way to do this? >> LDEXTRA_ARGS or EXTRA_CFLAGS or similar? >> >> I've looked around and can't really see anything. Best would be a >> single file to which I could add these things but adding them to the >> environment would also work. >> >> yours in ports ignorance.. >> > Hi Julian. > While I can't answer your question directly. > Maybe a USES=FAKE_INCLUDE, USES=FAKE_LIB? > No. I haven't implemented it. Just throwing it out there, while > it occurs to me. If someone doesn't beat me to it. I'd like > to look into the feasibility of something like this, to > accommodate something along the lines of what you're asking about. > I often shy away from tasks I'd like to undertake, because it seems > like too much work to cobble up just the right environment to > accomplish it. But if I could make a universal convenience knob > like I mention above. It'd be perfect. Tho I haven't thought it > completely through. I like the sound of it. :-) > > Apologies, for stepping on your thread. Hope you don't mind. USES_SYSROOT=/foo/bar would be the way to describe it feedable from the environment, and interpretted by each package as it suits it. (or taken from /etc/ports.conf) . Is there a file like that? seems that /etc/make.conf is still controlling it. >> Julian >> >> > --Chris > > > From owner-freebsd-ports@freebsd.org Wed Jun 29 07:40:10 2016 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 D0014B865CC for ; Wed, 29 Jun 2016 07:40:10 +0000 (UTC) (envelope-from bradleythughes@fastmail.fm) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 A7C972E93 for ; Wed, 29 Jun 2016 07:40:10 +0000 (UTC) (envelope-from bradleythughes@fastmail.fm) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 6D59722618 for ; Wed, 29 Jun 2016 03:40:03 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Wed, 29 Jun 2016 03:40:03 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=J5Q FPqOzvTBEz3qSYl6JcETq2S8=; b=OxSey1pjc9SFtIUbOQKKgyZW5LBPVYKnaLi sbEscU49wjf/aEQShkYIqMJY7O7LPER4PqO/1JR3MxSsGvPIGscwQthQbtelqdfX U3JXbTLKV/GTxRitWh/LNgO3Qwrgpl4WllL2B5ZaYOvOIDSAMOX/8Zm0l5EZQMvh czZcVg/4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=J5QFPqOzvTBEz3qSYl6JcETq2S8=; b=mrCX5 o8io7bkDXbzpHSaO4cZvScKsoJZztMxVh70dYKd2sxonJQ6y+cuvtiwjYJQbEfwQ 5sjB+eLNDHj/8qpgBlGu4nR9hvbK7MZic5knDxUXMLlCfMaivE6gOzaFuxVC4PCS F3p71hEtFtLEamf+1qEVsUpXKuRiyF1ckCJsLo= X-Sasl-enc: GC7MmluiTxKZY1oDVucyKNAUAW2mdrY4tKXQbwYKk+hL 1467186003 Received: from [192.168.0.62] (ip84-247-143-250.breiband.no [84.247.143.250]) by mail.messagingengine.com (Postfix) with ESMTPA id DBA23F2A15 for ; Wed, 29 Jun 2016 03:40:02 -0400 (EDT) From: "Bradley T. Hughes" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: PRs ready for commit for www/node* Message-Id: Date: Wed, 29 Jun 2016 09:40:01 +0200 To: freebsd-ports@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 07:40:10 -0000 Howdy! I've got several patches pending for the www/node* ports (I'm the = maintainer for these ports). One is a fix for several build failures = that have been recently reported, one is to fix portlint warnings, and = the others are version bumps to address security issues. Build fix: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210618 portlint fix: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210619 Version bumps: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210518 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210519 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210520 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210521 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210522 I'd appreciate help from a willing and able committer to get these in = the tree, ideally before the next quarterly branch is cut. Thanks in advance! :) -- Bradley T. Hughes bradleythughes@fastmail.fm From owner-freebsd-ports@freebsd.org Wed Jun 29 11:15:54 2016 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 DEECBB8559B for ; Wed, 29 Jun 2016 11:15:54 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (mail.sorbs.net [67.231.146.200]) by mx1.freebsd.org (Postfix) with ESMTP id C70D923FE for ; Wed, 29 Jun 2016 11:15:54 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0O9J008GU6AO9I00@hades.sorbs.net> for freebsd-ports@freebsd.org; Wed, 29 Jun 2016 04:23:14 -0700 (PDT) Subject: Re: blanket portmgr approval vs. non-fixing changes To: Matthias Andree Cc: freebsd-ports@freebsd.org References: <201606272021.u5RKLVhQ057899@slippy.cwsent.com> <20160628091709.pbvq7lekss2ql2en@ivaldir.etoilebsd.net> <5772E90C.6020908@gmx.de> <20160628213341.vvtobzbvxabphsqc@ivaldir.etoilebsd.net> From: Michelle Sullivan Message-id: <5773ADE0.7060204@sorbs.net> Date: Wed, 29 Jun 2016 13:15:44 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 In-reply-to: <20160628213341.vvtobzbvxabphsqc@ivaldir.etoilebsd.net> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 11:15:55 -0000 Baptiste Daroussin wrote: > On Tue, Jun 28, 2016 at 11:15:56PM +0200, Matthias Andree wrote: >> >> And I do think we should, opposite to what you are proposing, make the >> committer spend extra time for high-profile ports that entail sweeping >> changes to chase down the breaking change to, say, a library port. >> > I might have been not explicit enough, of course any changes should be tested, > and of course high profile ports breaking means special attention and prevent > the sweeping change to actually happen. > Sorry I think you're wrong at this point. Define "high profile" ... Some library port that other obscure ports are dependent on..? What say postgresql94-client or perhaps p5-Bucardo... something that only a few ports (if any) rely on, yet would be a massive problem for a lot of production servers/services if they were suddenly and quietly broken... It's an all or nothing thing, you either ensure your sweeping changes don't break anything, or don't care about anything and just put out an announcement that you made the change. Selecting some random list of what you consider should not be broken (or should be fixed first) based on some random list of what you think is important is a short sighted and unprofessional methodology as it creates more uncertainty and confusion.. My opinion, feel free to ignore as usual. -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-ports@freebsd.org Wed Jun 29 11:34:11 2016 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 AB3FCB85BDB for ; Wed, 29 Jun 2016 11:34:11 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 995302E2E for ; Wed, 29 Jun 2016 11:34:11 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 98CB6B85BD6; Wed, 29 Jun 2016 11:34:11 +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 987ACB85BD5 for ; Wed, 29 Jun 2016 11:34:11 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org (portscout.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (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 8C5AE2E2C for ; Wed, 29 Jun 2016 11:34:11 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.15.2/8.15.2) with ESMTP id u5TBYBOO038002 for ; Wed, 29 Jun 2016 11:34:11 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.15.2/8.15.2/Submit) id u5TBYBGd038001; Wed, 29 Jun 2016 11:34:11 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201606291134.u5TBYBGd038001@portscout.freebsd.org> X-Authentication-Warning: portscout.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Wed, 29 Jun 2016 11:34:11 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 11:34:11 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ chinese/tin | 2.3.3 | 2.3.4 ------------------------------------------------+-----------------+------------ multimedia/flvtool++ | 1.2.1 | 1.2.1-1 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Wed Jun 29 12:05:15 2016 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 E36A9AC5128 for ; Wed, 29 Jun 2016 12:05:15 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AD2222A45 for ; Wed, 29 Jun 2016 12:05:15 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 59E05BDD56; Wed, 29 Jun 2016 14:05:13 +0200 (CEST) Received: from gw.in.absolight.net (gw-ecl.in.absolight.net [79.143.241.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.in.absolight.net", Issuer "CA Cert Signing Authority" (not verified)) by prod2.absolight.net (Postfix) with ESMTPSA id 347E8BDD46; Wed, 29 Jun 2016 14:05:13 +0200 (CEST) Received: from ogg.in.absolight.net (ogg.in.absolight.net [79.143.241.239]) by gw.in.absolight.net (Postfix) with ESMTP id 717076145; Wed, 29 Jun 2016 14:05:11 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by ogg.in.absolight.net (Postfix) with ESMTP id 95FB42B70B4D; Wed, 29 Jun 2016 14:05:09 +0200 (CEST) Date: Wed, 29 Jun 2016 14:05:09 +0200 From: Mathieu Arnold To: Michelle Sullivan , Matthias Andree cc: freebsd-ports@freebsd.org Subject: Re: blanket portmgr approval vs. non-fixing changes Message-ID: <1F6847D731A66548F6179F88@ogg.in.absolight.net> In-Reply-To: <5773ADE0.7060204@sorbs.net> References: <201606272021.u5RKLVhQ057899@slippy.cwsent.com> <20160628091709.pbvq7lekss2ql2en@ivaldir.etoilebsd.net> <5772E90C.6020908@gmx.de> <20160628213341.vvtobzbvxabphsqc@ivaldir.etoilebsd.net> <5773ADE0.7060204@sorbs.net> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========13C0A2FEFA827A98FFF0==========" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 12:05:16 -0000 --==========13C0A2FEFA827A98FFF0========== Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline +--On 29 juin 2016 13:15:44 +0200 Michelle Sullivan wrote: | Baptiste Daroussin wrote: |> On Tue, Jun 28, 2016 at 11:15:56PM +0200, Matthias Andree wrote: |>> |>> And I do think we should, opposite to what you are proposing, make the |>> committer spend extra time for high-profile ports that entail sweeping |>> changes to chase down the breaking change to, say, a library port. |>> |> I might have been not explicit enough, of course any changes should be |> tested, and of course high profile ports breaking means special |> attention and prevent the sweeping change to actually happen. |> | Sorry I think you're wrong at this point. | | Define "high profile" ... Some library port that other obscure ports are | dependent on..? What say postgresql94-client or perhaps p5-Bucardo... | something that only a few ports (if any) rely on, yet would be a massive | problem for a lot of production servers/services if they were suddenly | and quietly broken... High profile is gmake, gettext, or libpng, those important things. -- Mathieu Arnold --==========13C0A2FEFA827A98FFF0========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQJ8BAEBCgBmBQJXc7l1XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IPcoQAIs9R7mDV9mSergpZEJ9sydZ XBD0Ne4ReTssPO3rXsYf6GlEjlkTrWnDMYit4vasBzALcd2RPC3WbiNHrcNmgnn/ HGJJBBH7jJYWgqzCzny6HxUgVPUPwiKxEgxsa1jM+jIafnsARXIF4dP3UKDXHWOH 9tHxDYzqvXVihuPLNL+lMp06xECa/vUy7kIst0UBeF/6uq5jRSPgF5Ke6N0RkjZl /+3bS4KLDy3do+K41Me0AkM4DZUn//ehrea1/2PSjyMlqf9BmI7PyeLjivcmQu4t tpdybYqA1/N9xBrdDNexVP05+zurI2vBFXI5Phm53g7xnmGFouJEW/Kc4olTiPVW ab1lwaNgkXC3JgVUCzgv+evpWu/1bgav7Su/r3cT5f1neIdtRHvfj18jWe0LFuxB X8Iqv/+ehVpYpOJVpcDkoOE4mvUJ0ICn2cQz9I3s6fTBqQkpZAdikKYPzjdQvSHy IwSL9HD/LDi5jJwkqL9pAxQJlsf53LcOfYeNhBv0zMe6logPwsO2ErBUh34JIG6P 0Q0oB1kRbBP+akMq5ssOFlqj3DwxUHDycUUeTe0n4IxS5C5BmYHWAphfzlA1AOBO hi/b1Im6ZT5bnqpIZJma94jIf1hW/MFQbGPyusZiPLs7rqMAWvnA2IijygOhd52S psP1Zulx6iHn7vJ04OEj =uZhh -----END PGP SIGNATURE----- --==========13C0A2FEFA827A98FFF0==========-- From owner-freebsd-ports@freebsd.org Wed Jun 29 16:35:51 2016 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 3B0D3B8623F for ; Wed, 29 Jun 2016 16:35:51 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (mail.sorbs.net [67.231.146.200]) by mx1.freebsd.org (Postfix) with ESMTP id 2A28F290C; Wed, 29 Jun 2016 16:35:50 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0O9J008IZL439I00@hades.sorbs.net>; Wed, 29 Jun 2016 09:43:17 -0700 (PDT) Subject: Re: blanket portmgr approval vs. non-fixing changes To: Mathieu Arnold , Matthias Andree Cc: freebsd-ports@freebsd.org References: <201606272021.u5RKLVhQ057899@slippy.cwsent.com> <20160628091709.pbvq7lekss2ql2en@ivaldir.etoilebsd.net> <5772E90C.6020908@gmx.de> <20160628213341.vvtobzbvxabphsqc@ivaldir.etoilebsd.net> <5773ADE0.7060204@sorbs.net> <1F6847D731A66548F6179F88@ogg.in.absolight.net> From: Michelle Sullivan Message-id: <5773F8E2.9030702@sorbs.net> Date: Wed, 29 Jun 2016 18:35:46 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 In-reply-to: <1F6847D731A66548F6179F88@ogg.in.absolight.net> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 16:35:51 -0000 Mathieu Arnold wrote: > +--On 29 juin 2016 13:15:44 +0200 Michelle Sullivan > wrote: > | Baptiste Daroussin wrote: > |> On Tue, Jun 28, 2016 at 11:15:56PM +0200, Matthias Andree wrote: > |>> > |>> And I do think we should, opposite to what you are proposing, make the > |>> committer spend extra time for high-profile ports that entail sweeping > |>> changes to chase down the breaking change to, say, a library port. > |>> > |> I might have been not explicit enough, of course any changes should be > |> tested, and of course high profile ports breaking means special > |> attention and prevent the sweeping change to actually happen. > |> > | Sorry I think you're wrong at this point. > | > | Define "high profile" ... Some library port that other obscure ports are > | dependent on..? What say postgresql94-client or perhaps p5-Bucardo... > | something that only a few ports (if any) rely on, yet would be a massive > | problem for a lot of production servers/services if they were suddenly > | and quietly broken... > > High profile is gmake, gettext, or libpng, those important things. > No disrespect intended, however... gettext-runtime sure 100% with you... gettext-devel ...? gmake? (break gmake it stops people compiling lots, but doesn't actually break production servers) libpng ... 50/50 on that .. its sorta like postgres*-* I have servers that don't have libpng, and I have servers that don't.. ...but that's sort of my point... it really should be an all or nothing thing... and IMHO it should be 'all'... Bulk changes in my opinion should not leave something that was working, not working. Regards, -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-ports@freebsd.org Wed Jun 29 16:46:20 2016 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 F389BB865A3 for ; Wed, 29 Jun 2016 16:46:20 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8E36F2156 for ; Wed, 29 Jun 2016 16:46:20 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: by mail-wm0-x229.google.com with SMTP id a66so82374044wme.0 for ; Wed, 29 Jun 2016 09:46:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cordula-ws.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=MCwPdjO9kxK6woedU64eWKiL+owTVUVXMkqxW9RK5sI=; b=12YNQsAKWJOopVDfJkhuhOmVa2ewYrxp2KfByJSLrEVH+0Kt9j9X6SK20s+aWeSnwv uyx+tyV50VfYD9sKlVscuPiYXn5id36P/cUHFIZ+U4QlrDtmOhmBqQ5ZVysmorUp/a/r O5ZUl0l8nIOXGe9fHHfuc+n/TWBHVai9ZJ/1+b6yxrYVx6mBq0LxTAlaqC0T1GtS48EP tphJON4J0uRVT0TwCi+oma8Q2hjBL7/FNAnBDU69gu+nocnxRBjAYynyiv+AGJKIfMPM /ZU3J+0Hoq6ULNyo+VWVuIg6QzohYqDcwXNQqc8HzALiwEuFPVHZ43VE0z+YuZr0Z9c8 ib5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=MCwPdjO9kxK6woedU64eWKiL+owTVUVXMkqxW9RK5sI=; b=nBtkOytGjpCc03htLhofyDCzzy2qgyIF9GHYTauLZCb3Dwr0e4M16gYD9RftBgGoma w7b9pOQwU5wXmgMizmuzJrQIfSvQpRHtN/J7uSVXe+jSW+ayG78sZdNmL2uRFuzPTidu rNQ8FVl7FxNzBOal1aMrT0Erl7DxzUQQIbq3k07GfZLz4soJvoTxwA3IQLVBawMQwKhz +yVknyiL6+21nMRIw+pXwmpTRL1MkmI8Fu7IpDoH3WpguDudChEwCaM6NRLctaCf1seL jC1qpF40rPwLaApB5+N/9pbgoekgGxYGnLJeFyxXI9ffkSWMkSbCNnE2YWrs4glwfDYT dGxQ== X-Gm-Message-State: ALyK8tJ3QRc5bZgLD/x/2D/T/3hTD7G3+wbt7jShvNj1wze5/doGkhRlKSNB0hohBao6yA== X-Received: by 10.194.88.5 with SMTP id bc5mr10208428wjb.100.1467218778830; Wed, 29 Jun 2016 09:46:18 -0700 (PDT) Received: from phenom.fritz.box (p4FDBBA34.dip0.t-ipconnect.de. [79.219.186.52]) by smtp.gmail.com with ESMTPSA id jf3sm4520401wjb.41.2016.06.29.09.46.16 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Jun 2016 09:46:17 -0700 (PDT) To: freebsd-ports@freebsd.org From: cpghost Subject: audio/csound6 endless loop and creates empty sound files Message-ID: <595c83d9-abb6-93db-51e5-d5e46f6d6c81@cordula.ws> Date: Wed, 29 Jun 2016 18:46:12 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 16:46:21 -0000 Hello, has anyone used audio/csound6 recently on FreeBSD? It compiles just fine, but it creates bogus output, AFAICS. Here's an example, simplified from Chapter 1 of The CSound Book: http://www.csounds.com/chapter1/ $ cat e1.orc sr = 44100 kr = 4410 ksmps = 10 nchnls = 1 instr 101 a1 oscil 10000, 440, 1 out a1 endin $ cat e1.sco ; Function 1 uses the GEN10 subroutine to compute a sine wave f 1 0 4096 10 1 ;inst start duration i 101 0 3 Running "csound e1.orc e1.sco" on Linux would create a file "test.wav" with a 440 Hz tone that can be rendered with any program like mplayer, vlc, etc... It would also display a sine wave as text. On FreeBSD, csound just runs in an endless loop, and test.wav grows and grows. If I stop csound with Ctrl-C, and inspect test.wav with hd(1), there's a header, followed by 00-bytes; that's all. I can vary the output format, it doesn't matter: always 00 samples are being output in an endless loop: $ csound e1.orc e1.sco virtual_keyboard real time MIDI plugin for Csound 0dBFS level = 32768.0 Csound version 6.06 (double samples) Jun 29 2016 libsndfile-1.0.26 orchname: e1.orc Elapsed time at end of orchestra compile: real: 0.004s, CPU: 0.000s sorting score ... ... done Elapsed time at end of score sort: real: 0.004s, CPU: 0.000s --Csound version 6.06 (double samples) Jun 29 2016 graphics suppressed, ascii substituted 0dBFS level = 32768.0 orch now loaded audio buffered in 256 sample-frame blocks writing 512-byte blks of shorts to test.wav (WAV) SECTION 1: ^C csound command: Interrupt csoundPerform(): stopped. inactive allocs returned to freespace end of score. overall amps: 0.0 overall samples out of range: 0 0 errors in performance Elapsed time at end of performance: real: 9.596s, CPU: 9.539s 256 512 sample blks of shorts written to test.wav (WAV) $ ls -l test.wav -rw-r--r-- 1 cpghost users 221763644 Jun 29 18:35 test.wav $ hd test.wav 00000000 52 49 46 46 34 d8 37 0d 57 41 56 45 66 6d 74 20 |RIFF4.7.WAVEfmt | 00000010 10 00 00 00 01 00 01 00 44 ac 00 00 88 58 01 00 |........D....X..| 00000020 02 00 10 00 64 61 74 61 10 d8 37 0d 00 00 00 00 |....data..7.....| 00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 0d37d830 Needless to say that this output file plays silent. So, there's something definitively broken in audio/csound6, because this happens ONLY on FreeBSD, not on Linux. More details on the port: $ uname -a FreeBSD phenom.fritz.box 10.3-STABLE FreeBSD 10.3-STABLE #0 r299381: Tue May 10 21:34:52 CEST 2016 root@phenom.fritz.box:/usr/obj/usr/src/sys/GENERIC amd64 $ cat /var/db/ports/audio_csound6/options # This file is auto-generated by 'make config'. # Options for csound6-6.06_1 _OPTIONS_READ=csound6-6.06_1 _FILE_COMPLETE_OPTIONS_LIST=ALSA CURL DSSI FLTK FLUIDSYNTH HDF5 JACK LUA NLS OPENMP OSC PNG PORTAUDIO PULSEAUDIO OPTIONS_FILE_UNSET+=ALSA OPTIONS_FILE_SET+=CURL OPTIONS_FILE_SET+=DSSI OPTIONS_FILE_SET+=FLTK OPTIONS_FILE_SET+=FLUIDSYNTH OPTIONS_FILE_SET+=HDF5 OPTIONS_FILE_UNSET+=JACK OPTIONS_FILE_SET+=LUA OPTIONS_FILE_SET+=NLS OPTIONS_FILE_SET+=OPENMP OPTIONS_FILE_SET+=OSC OPTIONS_FILE_SET+=PNG OPTIONS_FILE_UNSET+=PORTAUDIO OPTIONS_FILE_SET+=PULSEAUDIO I've tried various options, and recompiled audio/libsndfile too, but still couldn't get csound6 to work correctly. Any advice? Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-ports@freebsd.org Wed Jun 29 21:50:55 2016 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 2CB5DB862F4 for ; Wed, 29 Jun 2016 21:50:55 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD26125BC; Wed, 29 Jun 2016 21:50:54 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id v199so197668859wmv.0; Wed, 29 Jun 2016 14:50:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=uIzqh0t4WuDtanXxLtpbn+fkz/wkXpnvRTi8M9Hc8Lw=; b=uOW62f444cNqdynonlOwynoO6333ect9Npv5z9KAVE9aLJ2k21SDdw9ST5Fki7lIkX rIP/GfpUnHLKd0TiuR7E8q4c8tOwf7LYS4T7IzoR42gce2XgUZ3mZLPUJK6q+BtXRjhM qx0lzir2EGyqKMqf4jYGqH9FTwNEzTnjCvumODMVJrhyPuuUya11/rArm6ofBvgr6Ya3 3bm5fZVd6C7NSw55pOXQO4fXOmYTOXyPtrAmuDrBEItcxW6F2IHLq3tkLn9X8QHy3I4X F+sdvJcJbegxAOPCAmcd2qR+q0HNRTNGPxB1oYPKy46Ky3PBOIAfB0gkjndp1fa2s64V r4aA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=uIzqh0t4WuDtanXxLtpbn+fkz/wkXpnvRTi8M9Hc8Lw=; b=jYmZaLQt8bKn/xENaPLxroMAdKh11AnWZEbJcoCl/I7KLUSUVhQvjG51JmooL6Daid GMut1TI5cLuKX/TE9prsa9kW78y71YRTlQfDs02RnLvM4lwtZ/21AJiiG0UR7jICoczh ujGDessKQnplTOf7lNXZp1UmqEA/KbQ/OwmHTZDbkB7mc1+GVqUcHfffiEqPxaTx6LDy 0LUIW8moz7ITjU2zhOspVMCEc4qgNoixDzKENA53kMCWxud9+oGA+BdDT3dQ6kD/+u13 NWMSa/ONPxFBLaayC108PzcJ6PWU0+76Ts140k9ZNWowaevAeRnVhfTS8IbRxDWhoSS9 xDow== X-Gm-Message-State: ALyK8tJFUpm+tkgY21XHmnOp9Al+8ATVn+FSDZmkH2w6ffm/uQFMJ9ptpb2LzruRO4aYJw== X-Received: by 10.28.167.69 with SMTP id q66mr11434826wme.100.1467237053192; Wed, 29 Jun 2016 14:50:53 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id k6sm166638wjz.28.2016.06.29.14.50.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Jun 2016 14:50:51 -0700 (PDT) Sender: Baptiste Daroussin Date: Wed, 29 Jun 2016 23:50:50 +0200 From: Baptiste Daroussin To: Michelle Sullivan Cc: Mathieu Arnold , Matthias Andree , freebsd-ports@freebsd.org Subject: Re: blanket portmgr approval vs. non-fixing changes Message-ID: <20160629215050.eaxj2s4z7qqm5xjx@ivaldir.etoilebsd.net> References: <201606272021.u5RKLVhQ057899@slippy.cwsent.com> <20160628091709.pbvq7lekss2ql2en@ivaldir.etoilebsd.net> <5772E90C.6020908@gmx.de> <20160628213341.vvtobzbvxabphsqc@ivaldir.etoilebsd.net> <5773ADE0.7060204@sorbs.net> <1F6847D731A66548F6179F88@ogg.in.absolight.net> <5773F8E2.9030702@sorbs.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sgrnc2voh2nkktiz" Content-Disposition: inline In-Reply-To: <5773F8E2.9030702@sorbs.net> User-Agent: Mutt/1.6.1-neo (2016-06-11) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 21:50:55 -0000 --sgrnc2voh2nkktiz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 29, 2016 at 06:35:46PM +0200, Michelle Sullivan wrote: > Mathieu Arnold wrote: > > +--On 29 juin 2016 13:15:44 +0200 Michelle Sullivan > > wrote: > > | Baptiste Daroussin wrote: > > |> On Tue, Jun 28, 2016 at 11:15:56PM +0200, Matthias Andree wrote: > > |>> > > |>> And I do think we should, opposite to what you are proposing, make = the > > |>> committer spend extra time for high-profile ports that entail sweep= ing > > |>> changes to chase down the breaking change to, say, a library port. > > |>> > > |> I might have been not explicit enough, of course any changes should = be > > |> tested, and of course high profile ports breaking means special > > |> attention and prevent the sweeping change to actually happen. > > |> > > | Sorry I think you're wrong at this point. > > | > > | Define "high profile" ... Some library port that other obscure ports = are > > | dependent on..? What say postgresql94-client or perhaps p5-Bucardo... > > | something that only a few ports (if any) rely on, yet would be a mass= ive > > | problem for a lot of production servers/services if they were suddenly > > | and quietly broken... > >=20 > > High profile is gmake, gettext, or libpng, those important things. > >=20 > No disrespect intended, however... >=20 > gettext-runtime sure 100% with you... gettext-devel ...? > gmake? (break gmake it stops people compiling lots, but doesn't actually > break production servers) > libpng ... 50/50 on that .. its sorta like postgres*-* I have servers th= at > don't have libpng, and I have servers that don't.. >=20 > ...but that's sort of my point... it really should be an all or nothing > thing... and IMHO it should be 'all'... Bulk changes in my opinion should > not leave something that was working, not working. >=20 > Regards, In theory yes, but in reality how to you handle texinfo update have breakin= g the syntax and leaving 10 ports are not dependency on and have not been updated upstream for around 15 years? (Yeah I have been through that and actually f= ixed 8 of those and left the 2 others because I really could no find the fix and actually noone complained and this was more than 2 years ago). of a lib like let say libpng which have a security issue moving you do newer version of the lib which of course because how stable libpng API is you end= up having to fix 250 ports and you end up with 3 ports you cannot update becau= se over complicated code and those ports have not been maintained for more tha= n 10 years... you mark those 2 ports as broken and deprecate them. What about upgrading ruby to the officially commanded version but then you discover puppet37 is broken and upstream claims they don't care and won= 't ever fix? you end up with marking it as broken and the one who care about puppet37 (which was my case) then you come up and propose a fix and save the ports That is all this is about, of course we expect each committer to aim at 100= % of non breakage when you do changes but the reality is always a bit different.= and yes if 2 leaf ports are marked as broken in the battle they so be it. We have more than 26k ports in the ports tree. Which is way more than any o= ther operaring system I am aware of, on this list there are around 10-15% of them which are things without any active upstream, often written in old version = of C/C++ which breaks on regular basis after libc/toolchain updates and we oft= en manage to make survive (see the getline/dprintf fixes I have been committing recently for exemple). The number of working port 'percentage of the entire ports tree' have never= been so high on the entire ports tree since the last 8 years at least (I haven't= made any statistics before) since the blanket, the overwhole general quality has improved a lot, resulting in less breakage in the ports tree than what it w= as before. If one really want to get numbers I can provide numbers about what was the number of failing ports with the default options (which is supposed to be t= he most tested) 8 years ago, 6 years ago, 2 years ago and now. I have the same numbes with non default options but use on regular basis op= tions like NLS off or DOCS off. We cannot write down a rule that is supposed to describe what is just "comm= on sense" but again my initial message was: yes of course we do aim at 0 break= ages on changes, and yes sometime sweep changes leads into marking as broken 2 p= orts. Pushing sweep changes to be 100% free of breakage leads to people being sca= red about doing some important modification that are really needed for a while. Look at the history of boost updates for example or ICU... After how long someone really had a look at the bugs from libtool we were suffering for li= ke forever because of overlinking for example - not only - (leading to constant breakage of inplace building) etc. If I only take the freebsd 10 amd64 packages on last run we only got: 13 pa= ckage build failure over 26k leading to 93 skipped packages on the quarterly bran= ch and only 11 on the head branch of the ports tree leading to 86 build skipped (meaning no hugh profile packages). Best regards, Bapt --sgrnc2voh2nkktiz Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXdEKnAAoJEGOJi9zxtz5aKcoQAN4GAlHKXPU+jwhOikFMP+aw TOimo+0OTVWH3WXII0apoVH8UGTEV2RXzfJrg0LPxCWPUgZCEtUBfa54BcO40olm H5uxT/Ua3BcEX+UXsYbiSyrJwqJJY8msKmhfVRSrK/DS4QWrJbCu7V+AYpNQPuAV pgCuepgf+KdDthUD5n1aZejR6AjniKNh7XSXQylK6oI+93UIpoDAKYqx9rOCvNoS kzvPQOTp14FKMG/mdFq4JLJJyAtQXpRuEbkyulVgf32HACZqhQdI5gypaL7NwD6/ pCjI5dr296b/9HLZ8KShsQRAZMZmCWDmv8E8NbUWO7RVYt6fHNoZq+nvaXWbKZu5 jo2sR9lcAr5UgM3bnkLki1IpztO7ImSP0CAwlkS1Gk79tOY9Q4NBUvTFLJ1NCzjL 5LVSsO5qL/YgHkoknCHJCcsB66E12qMCXjBLnUEr26gaPrigHMDugLZ9mDaPJBxk IAEz52Q89aomXgIJ+QclPdf0iyw2zCZQT5F8k+eBEp7pk48kLCGNegeKrfOfXDF2 B/R7KCrhE7ERtwO1pb8Fx5uVy9mqwz6Hg98AJoWpaLPvHTfKTm/Ur7J9Hcjb1CU9 8bbZi5ofr9bc1Qc7VqIYlYESDL+kD+Rhe3R+hmyUldAiiOyij1PvovGEwmt0hSy7 4JDwQgrZHalHf4CaFtsE =bufv -----END PGP SIGNATURE----- --sgrnc2voh2nkktiz-- From owner-freebsd-ports@freebsd.org Wed Jun 29 23:16:30 2016 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 AFF43B8693E for ; Wed, 29 Jun 2016 23:16:30 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 978092B62 for ; Wed, 29 Jun 2016 23:16:30 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: by mailman.ysv.freebsd.org (Postfix) id 93070B8693D; Wed, 29 Jun 2016 23:16:30 +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 92A86B8693C for ; Wed, 29 Jun 2016 23:16:30 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from forward17h.cmail.yandex.net (forward17h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::a2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ECFF2B61 for ; Wed, 29 Jun 2016 23:16:30 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from smtp3h.mail.yandex.net (smtp3h.mail.yandex.net [IPv6:2a02:6b8:0:f05::117]) by forward17h.cmail.yandex.net (Yandex) with ESMTP id B750E20613 for ; Thu, 30 Jun 2016 02:16:14 +0300 (MSK) Received: from smtp3h.mail.yandex.net (localhost [127.0.0.1]) by smtp3h.mail.yandex.net (Yandex) with ESMTP id 6F7431B4035E for ; Thu, 30 Jun 2016 02:16:14 +0300 (MSK) Received: by smtp3h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 5xATMt2O6l-GDhmgsQa; Thu, 30 Jun 2016 02:16:13 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1467242173; bh=GfRPuA+onoeqOB6p4WsrBV8QftE5E0PGNP1cPEvRCoI=; h=Message-ID:Subject:From:To:Date:Content-Type:X-Mailer: Mime-Version:Content-Transfer-Encoding; b=RWeNUmkLRfGhTmXvSJxKknnD6SscDPmclELiHagyFlLhaWTrgSvbMaKWgFZkN7RSw Y2wMzMMq3QpRWxhjlY2xTas+CsHAT1l54P3rZFac/lrwMTVQdrEqGI5gg1b5Z39Xg0 tfebIJLTwqp4SZj2dcAxeuXCJ366+TJuybTpGzAs= Authentication-Results: smtp3h.mail.yandex.net; dkim=pass header.i=@yandex.com X-Yandex-Suid-Status: 1 0 Message-ID: <1467242155.22542.4.camel@yandex.com> Subject: python 3.4.5 update From: Stari Karp To: FreeBSD Ports Date: Wed, 29 Jun 2016 19:15:55 -0400 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 23:16:30 -0000 Hi! I tried to update Python on my  10.3-RELEASE-p5 (akd64) and I got: .... .... ports/lang/python34/work/Python-3.4.5 ./python -E -m ensurepip  $ensurepip --root=/usr/ports/lang/python34/work/stage/ ;  fi /bin/rm -f /usr/ports/lang/python34/work/stage/usr/local/lib/libpython3.so # Upstream Issue: http://bugs.python.org/issue17975 for i in /usr/ports/lang/python34/work/stage/usr/local/lib/python3.4/lib- dynload/*.so; do  /usr/bin/strip $i; done # Strip shared extensions ====> Compressing man pages (compress-man) ===>>> Creating a backup package for old version python34-3.4.4_3 Creating package for python34-3.4.4_3 process with pid 2056 still holds the lock process with pid 2056 still holds the lock process with pid 2056 still holds the lock process with pid 2056 still holds the lock process with pid 2056 still holds the lock process with pid 2056 still holds the lock pkg: Cannot get an advisory lock on a database, it is locked by another process ===>>> Starting check for runtime dependencies ===>>> Gathering dependency list for lang/python34 from ports ===>>> Dependency check complete for lang/python34 ===>>> All >> python34-3.4.4_3 (1/1) ===>  Installing for python34-3.4.5 ===>  Checking if python34 already installed ===>   An older version of python34 is already installed (python34- 3.4.4_3)       You may wish to ``make deinstall'' and install this port again       by ``make reinstall'' to upgrade it properly.       If you really wish to overwrite the old port of python34       without deleting it first, set the variable "FORCE_PKG_REGISTER"       in your environment or the "make install" command line. *** Error code 1 Stop. make[1]: stopped in /usr/ports/lang/python34 *** Error code 1 Stop. make: stopped in /usr/ports/lang/python34 ===>>> A backup package for python34-3.4.4_3 should        be located in /usr/ports/packages/portmaster-backup ===>>> Installation of python34-3.4.5 (lang/python34) failed ===>>> Aborting update ===>>> Update for lang/python34 failed ===>>> Aborting update Thank you very much. SK From owner-freebsd-ports@freebsd.org Thu Jun 30 01:19:31 2016 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 5804CB85A17 for ; Thu, 30 Jun 2016 01:19:31 +0000 (UTC) (envelope-from korekontakt@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 31EF9212F for ; Thu, 30 Jun 2016 01:19:31 +0000 (UTC) (envelope-from korekontakt@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 2DC65B85A16; Thu, 30 Jun 2016 01:19:31 +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 2D4CEB85A14 for ; Thu, 30 Jun 2016 01:19:31 +0000 (UTC) (envelope-from korekontakt@gmail.com) Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E6393212C; Thu, 30 Jun 2016 01:19:30 +0000 (UTC) (envelope-from korekontakt@gmail.com) Received: by mail-qt0-x22c.google.com with SMTP id m2so35016169qtd.1; Wed, 29 Jun 2016 18:19:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=yBt1mJDEyi95stoZm02ANrX/hMd4rRSKr4J1P1RkXN8=; b=ERiy06sNQ96mgUOepqD/3y22KSRTIOjJW+T/gu05WB8ylLhvVoGBPjGrnkCW8Yz5l/ hSKm1iWfbiZfJObQQ6CLggbep1RUqYeN77yFNWISu09fnTii6MZEhL+SZfWBeWNJB2YI VFBzUMLLdzq11RbX3q+uEatfwEmadhw+QyVufzHfivJ8mcX0IHT/aAYJjkhMZ6bJc66+ Gkx+KFBYrCqca9wnG9PqjhwGOcj9RXolUx5BMlOlUEB6kDM3gPZt9ew1Ou3+cpUPBJ7S dzMD67GzExgJtWqDCQblLRiKmbl0BZy4FxNeWuX4xYEetTiJnPibSq6SjJ5G6y3/O5iO m62Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=yBt1mJDEyi95stoZm02ANrX/hMd4rRSKr4J1P1RkXN8=; b=MG3ITkPka6qWWzZMvN2pYFboT44uQZuiMkoCVhx31yrV5Ntk3kTTZlqp1CpXoe7QCN TVl8Ing/Db0TdH8MilQK9attLLMQ/gz5XexpgHQFKV78H2P3wSqrz6uRuRB1sx61zxYi B17Aj0dXg22dPWjAOhsvjZBcmp9mdPwlYtW1hWKW62ldxmCpraQUVvkasH4mMcnXz0Xd NhHktSUWHT9KFDGFK87Mau3sZ4l2EToocYoMrfqOnU8GwiRDW5v0Y0Gn6BR2XevmRImQ MvtP1a+XEt5oYgtGcgjAtTASdxahuKt7V3yU6+Oq/O4TFSvl51MFLBj5gOV9YK7OpvVF 7mdg== X-Gm-Message-State: ALyK8tLJZ5GMhD3Gcm9HYlbIPSQb9pV93PrWGQtXfQ1MRAHkY4tkQqQmhDIEbAD7v7LFZT9v9YirWga0xmXaUg== MIME-Version: 1.0 X-Received: by 10.200.53.39 with SMTP id y36mr18519698qtb.92.1467249569929; Wed, 29 Jun 2016 18:19:29 -0700 (PDT) Received: by 10.237.52.229 with HTTP; Wed, 29 Jun 2016 18:19:29 -0700 (PDT) Received: by 10.237.52.229 with HTTP; Wed, 29 Jun 2016 18:19:29 -0700 (PDT) In-Reply-To: References: <20160609190710.GT41922@home.opsec.eu> <9f300278-31ab-bc50-1fc7-8e7e6dc44215@toco-domains.de> <8txv-34vw-wny_-_@vfemail.net> Date: Thu, 30 Jun 2016 09:19:29 +0800 Message-ID: Subject: Re: Torch7 ports (Was: Wxlua / Zbstudio) From: Raymond Cheung To: Jan Beich Cc: ports@freebsd.org, Kurt Jaeger , Torsten Zuehlsdorff Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 01:19:31 -0000 Hi all, I tried the Jan's git ports. However, I got 21 errors out of 127 torch tests. It said FFI can't point to some structures. Also, I can require nn even it was installed via luarocks. It said the tester suite is missing. Are the blas finding codes located at math/TH? Thanks. Raymond On Jun 24, 2016 17:12, "Raymond Cheung" wrote: > Hi Jan and Torsten, > > Thanks a lot for your help. > > I will try it later after taking a break. As I lack knowledge on C/C++, I > spent a month to retry many ways on FreeBSD 10/11. I feel tried. > Fortunately, I got some clues. > > During this month, I also learnt a lot on FreeBSD. As least I can build > and install new world/kernel from GhostBSD 10.3 to 11 Alpha 4. > > Thanks again for your help. > > Raymond > On Jun 24, 2016 06:41, "Jan Beich" wrote: > >> Torsten Zuehlsdorff writes: >> >> > Hello Raymond, >> > >> >> OpenBlas (make config; # with OpenMP option), OpenMP, Lapack & ++, >> GotoBlas >> >> are installed. Header files of OpenBlas is also included to >> >> $CMAKE_LIBRARY_PATH. However, I still got the same error message, >> missing >> >> lapack. >> > >> > There are various variables to set to specify where to look vor the >> > libs, like lapack. >> > >> > Sadly i'm out of time. Tomorrow i'm heading into vacation. When back i >> > will come back to your request and try to create a port for >> > this. Maybe we could success together (with more time). >> >> I did some work in the past on Torch7 ports before losing interest[1]. >> Check math/TH if you want to see how it detects OpenBLAS (default). >> >> $ git clone https://github.com/jbeich/freebsd-ports torch-ports >> $ export PORTSDIR=$PWD/torch-ports >> $ cd $PORTSDIR/devel/lua-trepl >> $ make install >> $ th51 >> >> -- >> [1] Many Torch pkgs rely on luarocks to build and resolve dependencies >> and some have a hard dependency on luajit. My approach didn't scale >> as writing such ports often required translating *.rockspec files >> which can quickly grow into maintenance nightmare, so an infra work >> had to be done beforehand. >> > From owner-freebsd-ports@freebsd.org Thu Jun 30 04:37:00 2016 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 6605DB87F8F for ; Thu, 30 Jun 2016 04:37:00 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from mail.mahoroba.org (ent.mahoroba.org [IPv6:2001:2f0:104:8010::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "asuka.mahoroba.org", Issuer "ca.mahoroba.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CBDAB2A24; Thu, 30 Jun 2016 04:36:59 +0000 (UTC) (envelope-from ume@mahoroba.org) Received: from asuka.mahoroba.org (ume@ent.mahoroba.org [IPv6:2001:2f0:104:8010::1]) (user=ume mech=DIGEST-MD5 bits=0) by mail.mahoroba.org (8.15.2/8.15.2) with ESMTPSA/inet6 id u5U4ajAM063402 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Thu, 30 Jun 2016 13:36:49 +0900 (JST) (envelope-from ume@mahoroba.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mahoroba.org; s=20081103; t=1467261411; bh=VyD+aFTibjdkbeRsV9ZQBeDyKzLo/CCj3bO1v3Whs+8=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=ABN0SxPAhyRz5MncDNfSw8pS4NXh6z8y9swPunJdWaWSk8rWElthRNwYqBhBpsu3F gwJ5T3mmW/Sl4arC/lMUicYMDZSjTi2rTiLzslvexpBN9RX66l6XYKZgwLrOCAC65w a8tw4JVWF621y1NUlWSGOmNetFDmYA7lK78l0QMQ= Date: Thu, 30 Jun 2016 13:36:44 +0900 Message-ID: From: Hajimu UMEMOTO To: Steve Wills Cc: KIRIYAMA Kazuhiko , freebsd-ports Subject: Re: Is there still broken lang/ruby23 ? In-Reply-To: <407b9391-86f0-4305-8bc3-3d5b21aacab3@FreeBSD.org> References: <201606282212.u5SMCDQU079882@kx.openedu.org> <407b9391-86f0-4305-8bc3-3d5b21aacab3@FreeBSD.org> User-Agent: xcite1.60> Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO) X-Operating-System: FreeBSD 10.3-STABLE X-PGP-Key: http://www.mahoroba.org/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE X-PGP-Key: http://www.mahoroba.org/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: multipart/mixed; boundary="Multipart_Thu_Jun_30_13:36:44_2016-1" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6 (mail.mahoroba.org [IPv6:2001:2f0:104:8010::1]); Thu, 30 Jun 2016 13:36:51 +0900 (JST) X-Virus-Scanned: clamav-milter 0.99.2 at asuka.mahoroba.org X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on asuka.mahoroba.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 04:37:00 -0000 --Multipart_Thu_Jun_30_13:36:44_2016-1 Content-Type: text/plain; charset=US-ASCII Hi, >>>>> On Tue, 28 Jun 2016 22:13:44 -0400 >>>>> Steve Wills said: Kazuhiko> Is there still broken lang/ruby23[1]. Or can build in latest Kazuhiko> 11.0-* ? Kazuhiko> [1] http://permalink.gmane.org/gmane.os.freebsd.devel.pkg-fallout/294364 swills> Yes, I haven't looked at it yet, but if you want to take a look, I'd swills> welcome patches. Could you put the attached two patches into lang/ruby23/files and give it a try? --Multipart_Thu_Jun_30_13:36:44_2016-1 Content-Type: text/x-patch; name="patch-ccan_list_list.h"; charset=US-ASCII Content-Disposition: attachment; filename="patch-ccan_list_list.h" Content-Transfer-Encoding: 7bit --- ccan/list/list.h.orig 2015-09-06 07:10:54 UTC +++ ccan/list/list.h @@ -57,7 +57,7 @@ struct list_head * Example: * static struct list_head my_list = LIST_HEAD_INIT(my_list); */ -#define LIST_HEAD_INIT(name) { { &name.n, &name.n } } +#define CCAN_LIST_HEAD_INIT(name) { { &name.n, &name.n } } /** * LIST_HEAD - define and initialize an empty list_head @@ -72,8 +72,8 @@ struct list_head * Example: * static LIST_HEAD(my_global_list); */ -#define LIST_HEAD(name) \ - struct list_head name = LIST_HEAD_INIT(name) +#define CCAN_LIST_HEAD(name) \ + struct list_head name = CCAN_LIST_HEAD_INIT(name) /** * list_head_init - initialize a list_head --Multipart_Thu_Jun_30_13:36:44_2016-1 Content-Type: text/x-patch; name="patch-thread__pthread.c"; charset=US-ASCII Content-Disposition: attachment; filename="patch-thread__pthread.c" Content-Transfer-Encoding: 7bit --- thread_pthread.c.orig 2016-04-15 16:07:07 UTC +++ thread_pthread.c @@ -1154,7 +1154,7 @@ native_sleep(rb_thread_t *th, struct tim } #ifdef USE_UBF_LIST -static LIST_HEAD(ubf_list_head); +static CCAN_LIST_HEAD(ubf_list_head); /* The thread 'th' is registered to be trying unblock. */ static void --Multipart_Thu_Jun_30_13:36:44_2016-1 Content-Type: text/plain; charset=US-ASCII -- Hajimu UMEMOTO ume@mahoroba.org ume@FreeBSD.org http://www.mahoroba.org/~ume/ --Multipart_Thu_Jun_30_13:36:44_2016-1-- From owner-freebsd-ports@freebsd.org Thu Jun 30 06:28:20 2016 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 6DF24B879AF for ; Thu, 30 Jun 2016 06:28:20 +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 38AE82B6D for ; Thu, 30 Jun 2016 06:28:20 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bIVSU-0004pA-8B; Thu, 30 Jun 2016 08:28:18 +0200 Date: Thu, 30 Jun 2016 08:28:18 +0200 From: Kurt Jaeger To: "Bradley T. Hughes" Cc: freebsd-ports@freebsd.org Subject: Re: PRs ready for commit for www/node* Message-ID: <20160630062818.GD79889@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.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 06:28:20 -0000 Hi! > I've got several patches pending for the www/node* ports [...] > I'd appreciate help from a willing and able committer to get these > in the tree, ideally before the next quarterly branch is cut. Done. -- pi@opsec.eu +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Thu Jun 30 06:33:32 2016 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 AD847B87BD7 for ; Thu, 30 Jun 2016 06:33:32 +0000 (UTC) (envelope-from bradleythughes@fastmail.fm) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 7F0B12F81 for ; Thu, 30 Jun 2016 06:33:32 +0000 (UTC) (envelope-from bradleythughes@fastmail.fm) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D66EF2045A; Thu, 30 Jun 2016 02:33:30 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 30 Jun 2016 02:33:30 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=kVQQ5EROYuF8rBYiGyoxoW/Nuyo=; b=UlG6/Y YgkpCVFrPGjuZSBgAVQW2miReJpJ8uZLx9NXEZ8cKLZ6K3mdHKT9GvgfoV9B0YDw DLzdT4yNAsXUtImAPukVrzrfKE8t/iPPvH40gYLhSnBCCiSudxt4ScgF9GZwMAoY CgDeESG342SdElRQbi8yAMFe5jnHS2pRmXQ9k= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=kVQQ5EROYuF8rBY iGyoxoW/Nuyo=; b=HlxtdRGbokLWJOlxsMPYTCyv76I/S8fxCQs0tGmhqCFuvmh 1xhQN5aJuW6N9OxJI4osMBApF4u+u0LP2lZOlM1LLTKpxLDZc9279DRMnD1Ny+yn FmYuimEHoeZVY92GDjRekR46r6eQKF4wmGdwZ/MAP9yfnx1Ih+S2JQUyXleA= X-Sasl-enc: UrMT/e9h8iPLM4XurZvsWKUjCHvV6Q3UsIl4OaG3NIng 1467268410 Received: from [192.168.0.62] (ip84-247-143-250.breiband.no [84.247.143.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 37809CCD34; Thu, 30 Jun 2016 02:33:30 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: PRs ready for commit for www/node* From: "Bradley T. Hughes" In-Reply-To: <20160630062818.GD79889@home.opsec.eu> Date: Thu, 30 Jun 2016 08:33:29 +0200 Cc: freebsd-ports@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <0456B014-5A0D-4506-A804-E1254E82B996@fastmail.fm> References: <20160630062818.GD79889@home.opsec.eu> To: Kurt Jaeger X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 06:33:32 -0000 > On 30 Jun 2016, at 08:28, Kurt Jaeger wrote: > > Hi! > >> I've got several patches pending for the www/node* ports [...] > >> I'd appreciate help from a willing and able committer to get these >> in the tree, ideally before the next quarterly branch is cut. > > Done. Thanks, Kurt. I appreciate it :) -- Bradley T. Hughes bradleythughes@fastmail.fm From owner-freebsd-ports@freebsd.org Thu Jun 30 07:14:45 2016 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 D3551B86557 for ; Thu, 30 Jun 2016 07:14:45 +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 98EB92EFD; Thu, 30 Jun 2016 07:14:45 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bIWBM-0004uX-Q3; Thu, 30 Jun 2016 09:14:40 +0200 Date: Thu, 30 Jun 2016 09:14:40 +0200 From: Kurt Jaeger To: Hajimu UMEMOTO Cc: Steve Wills , KIRIYAMA Kazuhiko , freebsd-ports Subject: Re: Is there still broken lang/ruby23 ? Message-ID: <20160630071440.GF79889@home.opsec.eu> References: <201606282212.u5SMCDQU079882@kx.openedu.org> <407b9391-86f0-4305-8bc3-3d5b21aacab3@FreeBSD.org> 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.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 07:14:45 -0000 Hi! > Kazuhiko> Is there still broken lang/ruby23[1]. Or can build in latest > Kazuhiko> 11.0-* ? > > Kazuhiko> [1] http://permalink.gmane.org/gmane.os.freebsd.devel.pkg-fallout/294364 > > swills> Yes, I haven't looked at it yet, but if you want to take a look, I'd > swills> welcome patches. > > Could you put the attached two patches into lang/ruby23/files and give > it a try? Testbuild on 11a (r302198M) on a loaded host was OK, but make check-plist found bin/erb missing. I'll now test poudriere. -- pi@opsec.eu +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Thu Jun 30 09:02:56 2016 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 5F211B8621D for ; Thu, 30 Jun 2016 09:02:56 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) 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 4133120CE for ; Thu, 30 Jun 2016 09:02:56 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mailman.ysv.freebsd.org (Postfix) id 3CEE2B8621C; Thu, 30 Jun 2016 09:02:56 +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 3C8D6B8621B for ; Thu, 30 Jun 2016 09:02:56 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 12A9120CD for ; Thu, 30 Jun 2016 09:02:55 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mail-io0-x22c.google.com with SMTP id t74so66080556ioi.0 for ; Thu, 30 Jun 2016 02:02:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=2t43vZ3O8cYYX4TlB1smczEMC1LwDwpguQFBH45nn+A=; b=G/tb8ZdbdlkA/5dCY7EUGf2OZGb1AeVY7Zz5frd8MK08pEaMRQ9jEJkZC9ce1DKAro OZ6XgyWVTE6gNDReoLmBpPiHCSNfMv6AdqY8tv+oKUdq1tyCOs+3YkNAiGF4yRZ58GLS QybsSU3OPiqI013nYpEQHTOmrfn15c4Nol1BA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=2t43vZ3O8cYYX4TlB1smczEMC1LwDwpguQFBH45nn+A=; b=HIwqj6fAnocnFK6tTSwawxTnpL1vVyqGpKal5DhLk7BJWwAN4njkZxmDH2lUSmFoxx X+cY+yg+3GvHZBRaxYmKux4nSQcsyWb5inM5UQLhGhZgnfThgYmU5GcKltNSznidwhmE PomOjFiOor+nJ5yZfJEWLh8EUjceUh1/crs+4/EV8dDlpPAySp0yLPmEhyHcTmOups8Q hPdoyMt1huUhu3fZNGzmlIOOhe87yp26j4APldadBmd/W9w0IDG2L65J/BP0F1InYPSy /F3rRHX+Ytm7jyPAQXc6vE+E6mESU5ep/PLjN9OHD8nPAN3qkEcOCuYWlfaSklgpCRcS MKCg== X-Gm-Message-State: ALyK8tIF2yT/PPwoETpt95QPrR3eRrJKNSu7rigWwx3kBRHyOiprxi8o+k6MGY7zoXMxFznyi2mAEJKlJuS5Vw== X-Received: by 10.107.182.136 with SMTP id g130mr13895736iof.27.1467277374720; Thu, 30 Jun 2016 02:02:54 -0700 (PDT) MIME-Version: 1.0 References: <1467242155.22542.4.camel@yandex.com> In-Reply-To: <1467242155.22542.4.camel@yandex.com> From: =?UTF-8?Q?Otac=C3=ADlio_de_Ara=C3=BAjo_Ramos_Neto?= Date: Thu, 30 Jun 2016 09:02:44 +0000 Message-ID: Subject: Re: python 3.4.5 update To: Stari Karp , FreeBSD Ports Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 09:02:56 -0000 Em qua, 29 de jun de 2016 20:16, Stari Karp escreveu: > > > Hi! > > I tried to update Python on my > 10.3-RELEASE-p5 (akd64) and I got: > > > .... > .... > ports/lang/python34/work/Python-3.4.5 ./python -E -m > ensurepip $ensurepip --root=/usr/ports/lang/python34/work/stage/ ; fi > /bin/rm -f > /usr/ports/lang/python34/work/stage/usr/local/lib/libpython3.so > # Upstream Issue: http://bugs.python.org/issue17975 > for i in > /usr/ports/lang/python34/work/stage/usr/local/lib/python3.4/lib- > dynload/*.so; do /usr/bin/strip $i; done > # Strip shared extensions > ====> Compressing man pages (compress-man) > > ===>>> Creating a backup package for old version python34-3.4.4_3 > Creating package for python34-3.4.4_3 > process with pid 2056 still holds the lock > process with pid 2056 still holds the lock > process with pid 2056 still holds the lock > process with pid 2056 still holds the lock > process with pid 2056 still holds the lock > process with pid 2056 still holds the lock > pkg: Cannot get an advisory lock on a database, it is locked by another > process > > ===>>> Starting check for runtime dependencies > ===>>> Gathering dependency list for lang/python34 from ports > ===>>> Dependency check complete for lang/python34 > > ===>>> All >> python34-3.4.4_3 (1/1) > > ===> Installing for python34-3.4.5 > ===> Checking if python34 already installed > ===> An older version of python34 is already installed (python34- > 3.4.4_3) > You may wish to ``make deinstall'' and install this port again > by ``make reinstall'' to upgrade it properly. > If you really wish to overwrite the old port of python34 > without deleting it first, set the variable "FORCE_PKG_REGISTER" > in your environment or the "make install" command line. > *** Error code 1 > > Stop. > make[1]: stopped in /usr/ports/lang/python34 > *** Error code 1 > > Stop. > make: stopped in /usr/ports/lang/python34 > > ===>>> A backup package for python34-3.4.4_3 should > be located in /usr/ports/packages/portmaster-backup > > ===>>> Installation of python34-3.4.5 (lang/python34) failed > ===>>> Aborting update > > ===>>> Update for lang/python34 failed > ===>>> Aborting update > > Thank you very much. > > SK > Are you shure that no other process is handling The ports at the same time? Like doing a query. []'S -Otacilio > From owner-freebsd-ports@freebsd.org Thu Jun 30 10:34:21 2016 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 AA05AB87A8C for ; Thu, 30 Jun 2016 10:34:21 +0000 (UTC) (envelope-from portscout@FreeBSD.org) 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 957DC2ABA for ; Thu, 30 Jun 2016 10:34:21 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 94EADB87A8A; Thu, 30 Jun 2016 10:34:21 +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 949B8B87A89 for ; Thu, 30 Jun 2016 10:34:21 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org (portscout.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (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 883412AB9 for ; Thu, 30 Jun 2016 10:34:21 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.15.2/8.15.2) with ESMTP id u5UAYLOf058033 for ; Thu, 30 Jun 2016 10:34:21 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.15.2/8.15.2/Submit) id u5UAYLbs058032; Thu, 30 Jun 2016 10:34:21 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201606301034.u5UAYLbs058032@portscout.freebsd.org> X-Authentication-Warning: portscout.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Thu, 30 Jun 2016 10:34:21 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 10:34:21 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/m6811-binutils | 2.15 | 2.26.1 ------------------------------------------------+-----------------+------------ emulators/mame | 0.166 | mame0175 ------------------------------------------------+-----------------+------------ emulators/mess | 0.166 | mame0175 ------------------------------------------------+-----------------+------------ java/netty | 3.9.2 | 3.10.6 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Thu Jun 30 12:28:42 2016 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 7B17AB86CDA for ; Thu, 30 Jun 2016 12:28:42 +0000 (UTC) (envelope-from alexander@treg.io) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 5D76A27F3 for ; Thu, 30 Jun 2016 12:28:42 +0000 (UTC) (envelope-from alexander@treg.io) Received: by mailman.ysv.freebsd.org (Postfix) id 5CC19B86CD8; Thu, 30 Jun 2016 12:28:42 +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 5C663B86CD7 for ; Thu, 30 Jun 2016 12:28:42 +0000 (UTC) (envelope-from alexander@treg.io) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D81CE27F1 for ; Thu, 30 Jun 2016 12:28:41 +0000 (UTC) (envelope-from alexander@treg.io) Received: by mail-lf0-x235.google.com with SMTP id f6so54292825lfg.0 for ; Thu, 30 Jun 2016 05:28:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=treg-io.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=MXt0n7t6kcCciEAGuq9UKXvkpvoh/+HbuMEoII9Jc4A=; b=wV0IbNcyvAw1DeIZ9IFwiVsAh5IuoqCb7Ym0b/7ezXSB3sSiogaEVgMMP/J7+IL4Tu umorOA14dlAyIJ+opFUQBOYLBvTwvtpqkelsX+6nn139r9Leh4RFxB9dMifnwEQplHQn 7QOVbwlqRTppfDY4YUMU7iWxYVFoejvgniZQE0S3A5H2X8Pb2UBAJTxuTewxQoNYHf/U rx66EnXfZimbCg+FqU0re31sH81ggkdQ/LZb9tJelMhMMOsMd/khTmWoay0VBRCA0QyG e1ZLvN+IGXdqdqMJlMz5E2I6MyKLYYL0DXYykVVeSemDzCv09EwZL+GUoCZam3xp7S2v OWIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=MXt0n7t6kcCciEAGuq9UKXvkpvoh/+HbuMEoII9Jc4A=; b=a1GwxvQN4bu6XVnd2wN/X7CRNliJiSq+YDnuzkpJ0xKYSv9joIibZtM4y1JUZmD2RG SVba2l3rg94u2e+UIp1kd9D7tK9DabX6F2SX8HewfNhNpayMiyzMUBl79vh517deZ4/T iDIDnvn3PFxNpARUAKpIsfXuuf/kqXTMiUJNpxQk81erbj35u8UtJJFofDceP6bgQ1Vo C+oeu1LNJ6XNipF501/GNXghUicZBmT1bwSvz88C9LUzjK6rmlqPwAwGullmENrzYm1G HhCucEam+MfWRBB4MIlHzet7Do++Nofr3ZBPkHOJGOvfPjmthnpC+B2pHLkGUNjTcKU/ Hbwg== X-Gm-Message-State: ALyK8tJKVZbNslPBXHzskEyvgky/gPjy17j5iYNy+5yfaz+5iNHKMIeyRpU7PZh/olhxYPggBc4r3bzDEAr8QQ== X-Received: by 10.25.78.138 with SMTP id c132mr4394953lfb.174.1467289719702; Thu, 30 Jun 2016 05:28:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.109.103 with HTTP; Thu, 30 Jun 2016 05:28:39 -0700 (PDT) X-Originating-IP: [195.159.218.126] From: Alexander Holte-Davidsen Date: Thu, 30 Jun 2016 14:28:39 +0200 Message-ID: Subject: www/uchiwa port To: ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 12:28:42 -0000 Hi, I created a new port a few week back; https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210071 I was wondering if someone with commit access could please take a look and see if it's okay to get this into the ports tree. If any changes needs to be done to have this commit please let me know and I will update the port accordingly. Best regards, Alexander From owner-freebsd-ports@freebsd.org Thu Jun 30 14:25:32 2016 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 BB616B86AA9 for ; Thu, 30 Jun 2016 14:25:32 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id A66222D83 for ; Thu, 30 Jun 2016 14:25:32 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: by mailman.ysv.freebsd.org (Postfix) id A5C61B86AA6; Thu, 30 Jun 2016 14:25:32 +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 A5700B86AA3 for ; Thu, 30 Jun 2016 14:25:32 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from fmailer.gwdg.de (fmailer.gwdg.de [134.76.11.16]) (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 6B6712D82 for ; Thu, 30 Jun 2016 14:25:31 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from um-excht-a02.um.gwdg.de ([134.76.11.222] helo=email.gwdg.de) by mailer.gwdg.de with esmtp (Exim 4.80) (envelope-from ) id 1bIcdG-0005kT-AT; Thu, 30 Jun 2016 16:07:54 +0200 Received: from pc028.nfv.nw-fva.de (134.76.242.1) by email.gwdg.de (134.76.9.211) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 30 Jun 2016 16:07:54 +0200 Subject: Re: python 3.4.5 update References: <1467242155.22542.4.camel@yandex.com> CC: =?UTF-8?Q?Otac=c3=adlio_de_Ara=c3=bajo_Ramos_Neto?= , FreeBSD Ports From: Rainer Hurling To: Stari Karp Message-ID: <6f10d7ea-45d9-3231-bd46-301506bba753@gwdg.de> Date: Thu, 30 Jun 2016 16:07:48 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Level: - X-Virus-Scanned: (clean) by clamav X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 14:25:32 -0000 Am 30.06.16 um 11:02 schrieb Otacílio de Araújo Ramos Neto: > Em qua, 29 de jun de 2016 20:16, Stari Karp escreveu: > >> >> >> Hi! >> >> I tried to update Python on my >> 10.3-RELEASE-p5 (akd64) and I got: >> >> >> .... >> .... >> ports/lang/python34/work/Python-3.4.5 ./python -E -m >> ensurepip $ensurepip --root=/usr/ports/lang/python34/work/stage/ ; fi >> /bin/rm -f >> /usr/ports/lang/python34/work/stage/usr/local/lib/libpython3.so >> # Upstream Issue: http://bugs.python.org/issue17975 >> for i in >> /usr/ports/lang/python34/work/stage/usr/local/lib/python3.4/lib- >> dynload/*.so; do /usr/bin/strip $i; done >> # Strip shared extensions >> ====> Compressing man pages (compress-man) >> >> ===>>> Creating a backup package for old version python34-3.4.4_3 >> Creating package for python34-3.4.4_3 >> process with pid 2056 still holds the lock >> process with pid 2056 still holds the lock >> process with pid 2056 still holds the lock >> process with pid 2056 still holds the lock >> process with pid 2056 still holds the lock >> process with pid 2056 still holds the lock >> pkg: Cannot get an advisory lock on a database, it is locked by another >> process >> >> ===>>> Starting check for runtime dependencies >> ===>>> Gathering dependency list for lang/python34 from ports >> ===>>> Dependency check complete for lang/python34 >> >> ===>>> All >> python34-3.4.4_3 (1/1) >> >> ===> Installing for python34-3.4.5 >> ===> Checking if python34 already installed >> ===> An older version of python34 is already installed (python34- >> 3.4.4_3) >> You may wish to ``make deinstall'' and install this port again >> by ``make reinstall'' to upgrade it properly. >> If you really wish to overwrite the old port of python34 >> without deleting it first, set the variable "FORCE_PKG_REGISTER" >> in your environment or the "make install" command line. >> *** Error code 1 >> >> Stop. >> make[1]: stopped in /usr/ports/lang/python34 >> *** Error code 1 >> >> Stop. >> make: stopped in /usr/ports/lang/python34 >> >> ===>>> A backup package for python34-3.4.4_3 should >> be located in /usr/ports/packages/portmaster-backup >> >> ===>>> Installation of python34-3.4.5 (lang/python34) failed >> ===>>> Aborting update >> >> ===>>> Update for lang/python34 failed >> ===>>> Aborting update >> >> Thank you very much. >> >> SK >> > > Are you shure that no other process is handling The ports at the same time? > Like doing a query. > > []'S > -Otacilio > As far as I know, portmaster itself has some not yet solved problems with ports, escpecially in a mixed system of ports, installed as a package by pkg and build from sources. For me, there are some possible opportunities, to circumstance this behaviour: 1) portmaster -m "FORCE_PKG_REGISTER" lang/python34 [this also does not work in all situations :( ] 2) portmaster lang/perl5 lang/python34 [(re)installing something like lang/perl5 before should help always ] 3) cd /usr/ports/lang/python34 make clean && make install Please keep in mind, that your failed update already deinstalled the old python 3.4.4 port, but failed to install the new version. So, at the moment, python 3 is probably not installed on your system. You can get back the old version by pkg add /usr/ports/packages/portmaster-backup/python34-3.4.4_3 as stated by portmasters message. HTH, Rainer Hurling From owner-freebsd-ports@freebsd.org Thu Jun 30 15:13:57 2016 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 0DEE4B87B80 for ; Thu, 30 Jun 2016 15:13:57 +0000 (UTC) (envelope-from vivek@khera.org) 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 E647A2EFD for ; Thu, 30 Jun 2016 15:13:56 +0000 (UTC) (envelope-from vivek@khera.org) Received: by mailman.ysv.freebsd.org (Postfix) id E214FB87B7F; Thu, 30 Jun 2016 15:13:56 +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 E1B8BB87B7D for ; Thu, 30 Jun 2016 15:13:56 +0000 (UTC) (envelope-from vivek@khera.org) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8656E2EFC for ; Thu, 30 Jun 2016 15:13:56 +0000 (UTC) (envelope-from vivek@khera.org) Received: by mail-wm0-x233.google.com with SMTP id r201so123457235wme.1 for ; Thu, 30 Jun 2016 08:13:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=khera.org; s=google11; h=mime-version:from:date:message-id:subject:to; bh=5Pf7TkzQy6tfxb7iefPQPqChZrOWNoY2aLRYBNsnsQQ=; b=YmTUR6Tax28tiKE1tR6+iCWpl5CZhw16p5dE2rSRWOvAKWVdYgim7TGOmmD1bpbbnl Au0GhsW2lBukZu7zDBOD4ubdPNtnz2mlmHVoecfXhxXS8xzeYAKPVzvoC1kEbFK5WMIT DpgVwdDmamwNPBWw9t0W6mVzW7YrL5maYI9Po= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=5Pf7TkzQy6tfxb7iefPQPqChZrOWNoY2aLRYBNsnsQQ=; b=OAzzs2385WD1t61wFzJ8CThxFlecci+Ck0mXjQzIscCI3CbnWytc72r0VzZXwBJyB1 yUr/cRlFn+iIKYOn4Mohd12cRyy/M3hGWDqRf6LhG9XU+F4zK0+ACnX72tLZGuUPIH4m YGcPall2o3wXT1mUw7ZqXYUUxEvsqCRGa+N+ZRUb6Y/WR9SOc0jNnbvwWVeY24CzWOaB jv/B/CVTlxAq8NQMdQn1M6c82ACHh+rbLcuX025QGfn91IZ1xzi7nSIW+rIlz5SekdML tNQXOE4EfRLeX/IZjIIWvC/o2JS22atW9EnfjDDvCT01j2AT48PjRQRtf85Dq8rn86pX gI4Q== X-Gm-Message-State: ALyK8tLCbitXNS84rzA/3k+VoUm6F0sZhmNMvT/C6QNe6FCG4ZWXR6I1HOm6HjJURQdyzhSxri3Th4eB6pNE6Q== X-Received: by 10.194.89.5 with SMTP id bk5mr15888333wjb.55.1467299634479; Thu, 30 Jun 2016 08:13:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.203.130 with HTTP; Thu, 30 Jun 2016 08:13:53 -0700 (PDT) From: Vick Khera Date: Thu, 30 Jun 2016 11:13:53 -0400 Message-ID: Subject: wordpress CLI To: FreeBSD Ports List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 15:13:57 -0000 Can I get a commit on 209583 ? It is a port for the wordpress CLI tool. It has been sitting there for a month and a half now with no action whatsoever. Thanks! From owner-freebsd-ports@freebsd.org Thu Jun 30 15:25:37 2016 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 55ED9B87E11 for ; Thu, 30 Jun 2016 15:25:37 +0000 (UTC) (envelope-from vivek@khera.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3A5212453 for ; Thu, 30 Jun 2016 15:25:37 +0000 (UTC) (envelope-from vivek@khera.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3622EB87E10; Thu, 30 Jun 2016 15:25:37 +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 35CEDB87E0E for ; Thu, 30 Jun 2016 15:25:37 +0000 (UTC) (envelope-from vivek@khera.org) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C52B32452 for ; Thu, 30 Jun 2016 15:25:36 +0000 (UTC) (envelope-from vivek@khera.org) Received: by mail-wm0-x22f.google.com with SMTP id v199so226135997wmv.0 for ; Thu, 30 Jun 2016 08:25:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=khera.org; s=google11; h=mime-version:from:date:message-id:subject:to; bh=fbJrbjLrJ95UZceVNopLPxwF1Eiyt2+0L2IvuFz0JoY=; b=UKwK6xEY2gTeBBsqBbM2DevpJTGBsDic5/gzWG8ySA0q9CIi3e30UZ0ggNBBzSvlci SD9SKT4dj6mOeb+JglorCv8GUVwsv36PQaQhoczPmKbTfawurPl++adw3g1LZ/sx+HJ0 ZqIU4OoSVa132vLT6ThYoxq8DdbHOfGEGbeOM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=fbJrbjLrJ95UZceVNopLPxwF1Eiyt2+0L2IvuFz0JoY=; b=RN99eUMiZikszB5QzcZ3OTjnCo8RMmXYYbosIA58LHOkSZTCfFOoYbUWLgJLvs81E6 ChtUSDgENU67YJ3qfJUuH4TTYzsCKdqRRU3LwgJdfD/XJUfOnUeuPD9btFrbN8MuyEF/ FvifhWVu+KCGQJzqU4g1ZS9hYdyLUcCR1nM42UEhQAHv3HNmz9+CW4RreVSFxMcYdnHp up9HEdJvbEvmPwlGemcp7gnXqX2kiPP3XHAi+hlcPSySp/I5J0pMmERm91SR/muZR0RP FC5+fUJ8zp3CKu/tGXPr22rZlNG8sXYmCWUcMpfM54x8r573cHFJpdEnVk99YitzPGsB s15g== X-Gm-Message-State: ALyK8tIFWvWDMxtHj4EIqmowVhPDhT4S3WjErWJr1ZADJ6iZVEAtZwogOhHw3aDQ1I2lTATAV2tdL0d8be4fCQ== X-Received: by 10.28.65.85 with SMTP id o82mr14714527wma.16.1467300335128; Thu, 30 Jun 2016 08:25:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.203.130 with HTTP; Thu, 30 Jun 2016 08:25:34 -0700 (PDT) From: Vick Khera Date: Thu, 30 Jun 2016 11:25:34 -0400 Message-ID: Subject: is USES=ncurses useless? To: FreeBSD Ports List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 15:25:37 -0000 I've observed (and filed PR 206471 ) that the USES=ncurses flag in a port does not result in the port actually linking with the ncurses library provided by the port. Does anyone else notice this? Specifically two ports I've encountered that have this issue are tmux and tty-clock. They both specify the ncurses from ports, yet link to base system ncurses library. They register dependencies against the ncurses port, too, which seems to be the only accomplishment of this setting. Full gory details are in the PR linked above. I'd appreciate any comments. From owner-freebsd-ports@freebsd.org Thu Jun 30 15:26:07 2016 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 D8E14B87E48 for ; Thu, 30 Jun 2016 15:26:07 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id B351A24FD for ; Thu, 30 Jun 2016 15:26:07 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id B2A5BB87E46; Thu, 30 Jun 2016 15:26:07 +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 B24A6B87E45 for ; Thu, 30 Jun 2016 15:26:07 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7FACC24FC for ; Thu, 30 Jun 2016 15:26:07 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pa0-x234.google.com with SMTP id b13so29368201pat.0 for ; Thu, 30 Jun 2016 08:26:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:reply-to:subject:references:to:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=7BLUTJFFBKsj26JazF1HiJGcW5RqTZiUl7tOF0xV51U=; b=vnOv+8qdyMIS5wfcckZy2JtTtt5zEg8KWibQMBrO+TirPQ2H+xqmORdc3akgzl46Pi DMgsRIqylmgeWVi6TyZJdV2rFC7Zqi5UgUZXU3jg0J56U6D8E454u8BE76slTgyNnSXK QabtLaNVzAuS5d1GTNtjvZiFdcSleGMr9xgZgcjGNrN5kojc3PqDfoouE/msNMDUzT+P /wjQmNrexCIhnlwh+w/WAOdhbBB83i1lu84C2uxvB4C7BsGWIJohIodu8XEFFxfDyh0a xBjNzxFExmlJE0cGKjrQKAcO39nbOpj65aFeSaMyGwefPX8CwXTS7bgX3Zvkgex+d5FD a/zQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:reply-to:subject:references:to:cc:from :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=7BLUTJFFBKsj26JazF1HiJGcW5RqTZiUl7tOF0xV51U=; b=S98/zsZp90Ab/0ZsoBD+NlRiTrPITMM3of7HuOnO6I2dosqlzrSXQ+eeqssVcU0h9K Of+80k8EIdKbw2PPVCxTodk7wOq3H/VOpP8kwivKyxQpctA44Ssk1798Sins3SLL8kcX JxHzewxuhLE7DbfmrWg+MJKkWCNbp5zod2B3UbWENVe1q8NXP+moePJY4b+F/k6vSrtE aVUB5pufwqFI5MMkPaiBEk28esCCXggDqDYG/5VMFVGuTT40LLPwRsrvBWmaasF+QlhA RbPMBnFNLF0YLDwXj/sZMCDrEvl5iSDuiL4XswA6mXN3/+cdOuIqDVaq5WqWXdgbWuFO Iqyg== X-Gm-Message-State: ALyK8tJohES4wQJP4+zedHVpsM10ssRMKA4+TdNc2v+1n/cjERceKO2z2tag1rSF9fPD0w== X-Received: by 10.66.135.40 with SMTP id pp8mr22570235pab.113.1467300366914; Thu, 30 Jun 2016 08:26:06 -0700 (PDT) Received: from ?IPv6:2001:44b8:31ae:7b01:1c07:2e44:3dfe:74a0? (2001-44b8-31ae-7b01-1c07-2e44-3dfe-74a0.static.ipv6.internode.on.net. [2001:44b8:31ae:7b01:1c07:2e44:3dfe:74a0]) by smtp.gmail.com with ESMTPSA id t10sm6732888pan.34.2016.06.30.08.26.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Jun 2016 08:26:06 -0700 (PDT) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: python 3.4.5 update References: <1467242155.22542.4.camel@yandex.com> <6f10d7ea-45d9-3231-bd46-301506bba753@gwdg.de> To: Rainer Hurling , Stari Karp Cc: FreeBSD Ports , =?UTF-8?Q?Otac=c3=adlio_de_Ara=c3=bajo_Ramos_Neto?= From: Kubilay Kocak Message-ID: <3ff1d714-12e7-974a-6c31-c8612d6e6434@FreeBSD.org> Date: Fri, 1 Jul 2016 01:25:56 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Thunderbird/47.0 MIME-Version: 1.0 In-Reply-To: <6f10d7ea-45d9-3231-bd46-301506bba753@gwdg.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 15:26:07 -0000 On 1/07/2016 12:07 AM, Rainer Hurling wrote: > > Please keep in mind, that your failed update already deinstalled the old > python 3.4.4 port, but failed to install the new version. So, at the > moment, python 3 is probably not installed on your system. You can get > back the old version by Would be cool if this was detected, and the deinstall was reverted From owner-freebsd-ports@freebsd.org Thu Jun 30 15:34:47 2016 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 6DD02B861E8 for ; Thu, 30 Jun 2016 15:34:47 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) 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 49DBE2BE6 for ; Thu, 30 Jun 2016 15:34:47 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 45749B861E7; Thu, 30 Jun 2016 15:34:47 +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 45170B861E6 for ; Thu, 30 Jun 2016 15:34:47 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 140B12BE5 for ; Thu, 30 Jun 2016 15:34:47 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pa0-x231.google.com with SMTP id bz2so29355455pad.1 for ; Thu, 30 Jun 2016 08:34:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:reply-to:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=RH66I/8nfBYPYdNYHi/cqXpPvnIHx6goD/j3algOuVw=; b=TQofs5zTXTFdfA7vE7jrUQWy7YRaGHy8xgJNb8DH+Ef6QOmM8hvV1PPXMJeI/lFxWn yWPtNlqGjL5xxPQ5gMZh2T2bsQcpyVqPsSDH60hQuQmpSnSm/EDi/+tIo3fNfqvSRgLh lzwUHIUexKh/X6HgRTOmyj16AF6JZQZeLaOXRT+dCGMMIu7PgRS5w+oKiweRSNrogJRf X/+l5U3dIJ9eTKabBKQ/HlnKZU7yBVS25J8Eg/7ajqPynGSZ8U/fQGJiyZnn4Z/hUUkO 9S6GP17EUAYAO+B9Myk1Q6JkvKELDSbv7TTXVTGNEQv9soBl4d3WZNu/X8p5NQmwZdF2 JmgA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:reply-to:subject:references:to:from :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=RH66I/8nfBYPYdNYHi/cqXpPvnIHx6goD/j3algOuVw=; b=YnTn5YH1Q1h5fRVWAzXW/x4cYkxZPKiuL0FBCL6W7r4JTqtYcMldgbKJI/PA/ehey4 xkpCry8I4X27uvg+ChMPvFE2AmOChpCvHYBA1tXDH53p44MZGmwotexOfD5/NdKrI5PT 6L3N+eNrxfmEHMisTN0pGmQ+9OiK8HS3NbinW1p7chgmFQH7Xp9hudijsYFjWnJ+smlv QQuZ2tUocYYRDbHx4ffytWUYToQuHNmM8qtjTiv55HWwAHJdQrK3Yvi1cHKhxDDQipyS sgqNurCPHnjmbriXGAb6YkffYjFsrtPnWyYCq03Y9pj2HQxA6CGgkpLqELYxxyUKS5+j NJLA== X-Gm-Message-State: ALyK8tKZSC96Msew315orrY1CI9hyN5UIiUJRafzLNeg5JTh3FUF/k4RlytBQW85TBOjCQ== X-Received: by 10.66.79.2 with SMTP id f2mr22534126pax.14.1467300885143; Thu, 30 Jun 2016 08:34:45 -0700 (PDT) Received: from ?IPv6:2001:44b8:31ae:7b01:1c07:2e44:3dfe:74a0? (2001-44b8-31ae-7b01-1c07-2e44-3dfe-74a0.static.ipv6.internode.on.net. [2001:44b8:31ae:7b01:1c07:2e44:3dfe:74a0]) by smtp.gmail.com with ESMTPSA id c13sm6758008pfc.40.2016.06.30.08.34.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Jun 2016 08:34:44 -0700 (PDT) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: wordpress CLI References: To: Vick Khera , FreeBSD Ports List From: Kubilay Kocak Message-ID: <3f91101e-5f37-ff2b-705c-51109c085741@FreeBSD.org> Date: Fri, 1 Jul 2016 01:34:36 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Thunderbird/47.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 15:34:47 -0000 On 1/07/2016 1:13 AM, Vick Khera wrote: > Can I get a commit on 209583 > ? It is a port > for the wordpress CLI tool. It has been sitting there for a month and a > half now with no action whatsoever. > > Thanks! > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > Hi Vick I've triaged the issue and provided some review homework^W feedback as well. Give me a holler off list if you have any questions or need further pointers :) ./koobs From owner-freebsd-ports@freebsd.org Thu Jun 30 17:06:05 2016 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 22417B87AD2 for ; Thu, 30 Jun 2016 17:06:05 +0000 (UTC) (envelope-from pi@opsec.eu) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 129D92932 for ; Thu, 30 Jun 2016 17:06:05 +0000 (UTC) (envelope-from pi@opsec.eu) Received: by mailman.ysv.freebsd.org (Postfix) id 0E58EB87AD1; Thu, 30 Jun 2016 17:06:05 +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 0E038B87AD0 for ; Thu, 30 Jun 2016 17:06:05 +0000 (UTC) (envelope-from pi@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 CA3D52931 for ; Thu, 30 Jun 2016 17:06:04 +0000 (UTC) (envelope-from pi@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bIfPi-0005xX-FR; Thu, 30 Jun 2016 19:06:06 +0200 Date: Thu, 30 Jun 2016 19:06:06 +0200 From: Kurt Jaeger To: Alexander Holte-Davidsen Cc: ports@freebsd.org Subject: Re: www/uchiwa port Message-ID: <20160630170606.GG79889@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.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 17:06:05 -0000 Hi! > I created a new port a few week back; > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210071 > > I was wondering if someone with commit access could please take a look and > see if it's okay to get this into the ports tree. I had a quick look. > If any changes needs to be done to have this commit please let me know and > I will update the port accordingly. Have you tested it in poudriere ? The pkg-plist seems to be inconsistent, see those build logs: http://people.freebsd.org/~pi/logs/www__uchiwa-cur-1467305994.txt http://people.freebsd.org/~pi/logs/www__uchiwa-93a-1467305994.txt http://people.freebsd.org/~pi/logs/www__uchiwa-103-1467305994.txt -- pi@opsec.eu +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Thu Jun 30 19:23:48 2016 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 C3C86B875FB for ; Thu, 30 Jun 2016 19:23:48 +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 B3D892562 for ; Thu, 30 Jun 2016 19:23:48 +0000 (UTC) (envelope-from lists@opsec.eu) Received: by mailman.ysv.freebsd.org (Postfix) id B3285B875FA; Thu, 30 Jun 2016 19:23:48 +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 B2C6FB875F9 for ; Thu, 30 Jun 2016 19:23:48 +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 7E86D2561 for ; Thu, 30 Jun 2016 19:23:48 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bIhZ1-00065q-GU; Thu, 30 Jun 2016 21:23:51 +0200 Date: Thu, 30 Jun 2016 21:23:51 +0200 From: Kurt Jaeger To: Alexander Holte-Davidsen Cc: ports@freebsd.org Subject: Re: www/uchiwa port Message-ID: <20160630192351.GH79889@home.opsec.eu> References: <20160630170606.GG79889@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160630170606.GG79889@home.opsec.eu> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2016 19:23:48 -0000 Hi! The port is now in the tree. Thanks for the quick turnaround and fix! -- pi@opsec.eu +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Fri Jul 1 06:32:00 2016 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 648D5B8DF2F for ; Fri, 1 Jul 2016 06:32:00 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from vms173025pub.verizon.net (vms173025pub.verizon.net [206.46.173.25]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4B92E2C47 for ; Fri, 1 Jul 2016 06:31:56 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from vz-proxy-l002.mx.aol.com ([64.236.82.148]) by vms173025.mailsrvcs.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0O9M0098AI4JD750@vms173025.mailsrvcs.net> for freebsd-ports@FreeBSD.ORG; Fri, 01 Jul 2016 01:31:35 -0500 (CDT) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=btqxfxui c=1 sm=1 tr=0 a=hkQRW7prCrFMEwk2DGUM9Q==:117 a=cAmyUtKerLwA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=6T1jHB6Q9tUpeHkup_kA:9 a=QEXdDO2ut3YA:10 a=3ui2YaHfn1M7jfe4j8cA:9 a=_W_S_7VecoQA:10 Received: by 108.53.87.98 with SMTP id 5b4f5815; Fri, 01 Jul 2016 06:31:35 GMT To: "freebsd-ports@FreeBSD.ORG" From: "Mikhail T." Subject: Seeking testers for port of SikuliX-2014 Message-id: <580d497f-231a-5106-ff13-e5799adc5b51@aldan.algebra.com> Date: Fri, 01 Jul 2016 02:31:30 -0400 MIME-version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 06:32:00 -0000 I got the code to build and install on FreeBSD. The application starts, but I don't really know, how to use it. If you, or someone you know, do -- and have used it before on other platforms -- please, contact me directly. Thank you! -mi From owner-freebsd-ports@freebsd.org Fri Jul 1 09:15:35 2016 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 3EBA0B8862D for ; Fri, 1 Jul 2016 09:15:35 +0000 (UTC) (envelope-from starikarp@yandex.com) 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 23465268C for ; Fri, 1 Jul 2016 09:15:35 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: by mailman.ysv.freebsd.org (Postfix) id 1EE39B8862C; Fri, 1 Jul 2016 09:15:35 +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 1E8B5B8862B for ; Fri, 1 Jul 2016 09:15:35 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from forward4m.cmail.yandex.net (forward4m.cmail.yandex.net [IPv6:2a02:6b8:b030::1b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9C1F5268A for ; Fri, 1 Jul 2016 09:15:34 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from smtp1m.mail.yandex.net (smtp1m.mail.yandex.net [IPv6:2a02:6b8:0:2519::121]) by forward4m.cmail.yandex.net (Yandex) with ESMTP id A66D12104E; Fri, 1 Jul 2016 12:15:30 +0300 (MSK) Received: from smtp1m.mail.yandex.net (localhost [127.0.0.1]) by smtp1m.mail.yandex.net (Yandex) with ESMTP id 6AF0A6740882; Fri, 1 Jul 2016 12:15:30 +0300 (MSK) Received: by smtp1m.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id y15XGH6aka-FSYeFfCc; Fri, 01 Jul 2016 12:15:29 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1467364529; bh=udUxEIPpaVdpVthQ+FzZwp5UN4MVFbIaqecQl5K0GAs=; h=Message-ID:Subject:From:To:Date:In-Reply-To:References: Content-Type:X-Mailer:Mime-Version:Content-Transfer-Encoding; b=M6+dkN7KTfC3Z9nMCx0Rtfhj6YQSwBFLCCV99KxFH8+9HSFWuT/EIw2GppiMbiByt vjhBTglMFOcO/Dmjj4TCY+mm5fhtf43nxyjNNeEbB159lbruDKafpFYS/VdV4F0wCJ PK27IBcaW903xfuSzMzWJacnuHP53dN5y3y/0yvk= Authentication-Results: smtp1m.mail.yandex.net; dkim=pass header.i=@yandex.com X-Yandex-Suid-Status: 1 0,1 0 Message-ID: <1467364511.4381.1.camel@yandex.com> Subject: Re: python 3.4.5 update From: Stari Karp To: =?ISO-8859-1?Q?Otac=EDlio?= de =?ISO-8859-1?Q?Ara=FAjo?= Ramos Neto , FreeBSD Ports Date: Fri, 01 Jul 2016 05:15:11 -0400 In-Reply-To: References: <1467242155.22542.4.camel@yandex.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 09:15:35 -0000 On Thu, 2016-06-30 at 09:02 +0000, Otacílio de Araújo Ramos Neto wrote: > > > > > Em qua, 29 de jun de 2016 20:16, Stari Karp > escreveu: > > > > > > Hi! > > > > I tried to update Python on my  > > 10.3-RELEASE-p5 (akd64) and I got: > > > > > > .... > > .... > > ports/lang/python34/work/Python-3.4.5 ./python -E -m > > ensurepip  $ensurepip --root=/usr/ports/lang/python34/work/stage/ > > ;  fi > > /bin/rm -f > > /usr/ports/lang/python34/work/stage/usr/local/lib/libpython3.so > > # Upstream Issue: http://bugs.python.org/issue17975 > > for i in > > /usr/ports/lang/python34/work/stage/usr/local/lib/python3.4/lib- > > dynload/*.so; do  /usr/bin/strip $i; done > >                 # Strip shared extensions > > ====> Compressing man pages (compress-man) > > > > ===>>> Creating a backup package for old version python34-3.4.4_3 > > Creating package for python34-3.4.4_3 > > process with pid 2056 still holds the lock > > process with pid 2056 still holds the lock > > process with pid 2056 still holds the lock > > process with pid 2056 still holds the lock > > process with pid 2056 still holds the lock > > process with pid 2056 still holds the lock > > pkg: Cannot get an advisory lock on a database, it is locked by > > another > > process > > > > ===>>> Starting check for runtime dependencies > > ===>>> Gathering dependency list for lang/python34 from ports > > ===>>> Dependency check complete for lang/python34 > > > > ===>>> All >> python34-3.4.4_3 (1/1) > > > > ===>  Installing for python34-3.4.5 > > ===>  Checking if python34 already installed > > ===>   An older version of python34 is already installed (python34- > > 3.4.4_3) > >       You may wish to ``make deinstall'' and install this port > > again > >       by ``make reinstall'' to upgrade it properly. > >       If you really wish to overwrite the old port of python34 > >       without deleting it first, set the variable > > "FORCE_PKG_REGISTER" > >       in your environment or the "make install" command line. > > *** Error code 1 > > > > Stop. > > make[1]: stopped in /usr/ports/lang/python34 > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/ports/lang/python34 > > > > ===>>> A backup package for python34-3.4.4_3 should > >        be located in /usr/ports/packages/portmaster-backup > > > > ===>>> Installation of python34-3.4.5 (lang/python34) failed > > ===>>> Aborting update > > > > ===>>> Update for lang/python34 failed > > ===>>> Aborting update > > > > Thank you very much. > > > > SK > Are you shure that no other process is handling The ports at the same > time? Like doing a query. > > []'S > -Otacilio Yes, looks like that the problem was GNOME which was on. Thank you. From owner-freebsd-ports@freebsd.org Fri Jul 1 10:07:14 2016 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 6735EB89560 for ; Fri, 1 Jul 2016 10:07:14 +0000 (UTC) (envelope-from portscout@FreeBSD.org) 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 531E12A24 for ; Fri, 1 Jul 2016 10:07:14 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 513C6B8955E; Fri, 1 Jul 2016 10:07:14 +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 50EB9B8955D for ; Fri, 1 Jul 2016 10:07:14 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org (portscout.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (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 4351E2A23 for ; Fri, 1 Jul 2016 10:07:14 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.15.2/8.15.2) with ESMTP id u61A7EEJ001144 for ; Fri, 1 Jul 2016 10:07:14 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.15.2/8.15.2/Submit) id u61A7EVP001143; Fri, 1 Jul 2016 10:07:14 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201607011007.u61A7EVP001143@portscout.freebsd.org> X-Authentication-Warning: portscout.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Fri, 1 Jul 2016 10:07:14 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 10:07:14 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/efivar | 0.15 | 0.24 ------------------------------------------------+-----------------+------------ lang/sbcl | 1.3.1 | 1.3.7 ------------------------------------------------+-----------------+------------ www/links | 2.9 | 2.13 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Fri Jul 1 10:18:38 2016 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 172BFB899B4 for ; Fri, 1 Jul 2016 10:18:38 +0000 (UTC) (envelope-from idefix@fechner.net) 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 F1C1F2F32 for ; Fri, 1 Jul 2016 10:18:37 +0000 (UTC) (envelope-from idefix@fechner.net) Received: by mailman.ysv.freebsd.org (Postfix) id F11D8B899B3; Fri, 1 Jul 2016 10:18:37 +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 F0CA8B899B2 for ; Fri, 1 Jul 2016 10:18:37 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from anny.lostinspace.de (anny.lostinspace.de [IPv6:2001:608:a02::33]) (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 B8B362F31 for ; Fri, 1 Jul 2016 10:18:37 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from server.idefix.lan (aftr-88-217-181-136.dynamic.mnet-online.de [88.217.181.136]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: idefix@fechner.net) by anny.lostinspace.de (Postfix) with ESMTPSA id 0E748597AF9 for ; Fri, 1 Jul 2016 12:18:36 +0200 (CEST) DMARC-Filter: OpenDMARC Filter v1.3.1 anny.lostinspace.de 0E748597AF9 Authentication-Results: anny.lostinspace.de; dmarc=none header.from=fechner.net DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=fechner.net; s=default; t=1467368316; bh=B5O+em/FnX2PcKcY6eo6bNjk1IHiauIgB2c7a6qzejs=; h=To:From:Subject:Date; b=KitHFzoYtXs2Dr7SMAZrOXSyiTHXJOiUbuLOSaNCfC5QKzNnxuGj819C6/Xzr44xv LqKY70WToFT/0OpP6oqvyITGg2fKpQAAZgmEmDKTAwuitochHKa9jaT0/32uvkxwXP D5u4wyHNSY7zz3jduTdEPc2LMikTeOleBI209M9g= Received: from [192.168.0.151] (aftr-88-217-181-136.dynamic.mnet-online.de [88.217.181.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by server.idefix.lan (Postfix) with ESMTPSA id 6B900401980 for ; Fri, 1 Jul 2016 12:18:35 +0200 (CEST) To: ports@freebsd.org From: Matthias Fechner Subject: Remove options from poudriere option files for ports which were removed in the port Message-ID: <71272a33-1a98-47a1-394d-725def6282a5@fechner.net> Date: Fri, 1 Jul 2016 12:17:43 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 10:18:38 -0000 Dear all, it seems that poudriere can only add new options to its own options tracking, but cannot remove options that where removed from the Makefile of the port. Concrete example is for mail/postfix The option SPF was removed (2016-02-28): https://www.freshports.org/mail/postfix/ But if I execute: poudriere options -j 103amd64 -f 103amd64-pkglist it will not remove the option from the options file: 103amd64-options/mail_postfix/options Is there a possibility to clean up all the option files without starting again at zero with: poudriere options -c -j 103amd64 -f 103amd64-pkglist Thanks. Gru=C3=9F Matthias --=20 "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook From owner-freebsd-ports@freebsd.org Fri Jul 1 10:39:55 2016 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 94DD8B89EF1 for ; Fri, 1 Jul 2016 10:39:55 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 758A9288B for ; Fri, 1 Jul 2016 10:39:55 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 74EA6B89EF0; Fri, 1 Jul 2016 10:39:55 +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 74907B89EEF for ; Fri, 1 Jul 2016 10:39:55 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E170288A for ; Fri, 1 Jul 2016 10:39:55 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: by mail-oi0-x22c.google.com with SMTP id s66so105047075oif.1 for ; Fri, 01 Jul 2016 03:39:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=T08dZ3CCSQvCZkozcmzzYvk14Wv4BEIGAHl4sdloJWE=; b=SshP5XKJALZnu3buLSdSzj81F7FcZ3EEQi6Sq++qMHBoybsRro6w4fUE8Pl7j8KAK3 j9c1cDg1NXapYbmCFuHSASZ+4w92ksiatq+Vaugmqbpp3seK+GdgOEAQHmWiA2L6wv8G HsQ6XUJGNOsdRSZeuhVN22WU9sc0RuiDmI+uB5I5jkfLA7Kbac7f5kYqSzshv834zrFw KwvgsxDuQQv2PRIpCul14I5WUX1K6qLfgKuxSODbgaKVT3+aNKKJTNT94jCoO06eSzN/ F3VRHjJV/5GUmmz4jp+BpZpj0e40yg3my9KPmDSB7ulrAG+NxNQkE4AQ3brwtErb7oeE RCAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=T08dZ3CCSQvCZkozcmzzYvk14Wv4BEIGAHl4sdloJWE=; b=ZxRDjtr6vDdppn2MtKbb/Qnv4tmNn10CGQl4VRKcOLVWsZnnDcqpgUZFVO4Ii8ZCmQ OOeVMkpVXPKfmuBNDwLKM3RUiudOrACt955Mcfcv7ytn9BcxvWKRNiodBnGXL/TL6lWx 2UeOOgtrFjBnbaQzasKHTNJhJr0KQJs7pnIsECV1QsdBsmXzjNzTl89OMyxt/xvgAADP EK9QEh/Jvl5tIk6M6DaD7n5x26VMdLlVOoWCOcAnxcu/GEM7J0zKnSKZQKRSc6Qf9/Ru RMGLLN1COtotY0sPdoOBd/4nVABLFGxXlWKUyq61p0YHpd/xKripIWMTbHLPGlqXLhLt EHyg== X-Gm-Message-State: ALyK8tI/bRwYeNgVg7fD7CX7GSjaKuOEStky5zSGY2nYKmQ+Cq9m7aulQ9ze1tjdAWI8QIFLW0DDRU0qvIK/PA== X-Received: by 10.157.38.208 with SMTP id i16mr1683210otd.112.1467369594275; Fri, 01 Jul 2016 03:39:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.16.76 with HTTP; Fri, 1 Jul 2016 03:39:53 -0700 (PDT) In-Reply-To: <71272a33-1a98-47a1-394d-725def6282a5@fechner.net> References: <71272a33-1a98-47a1-394d-725def6282a5@fechner.net> From: Kimmo Paasiala Date: Fri, 1 Jul 2016 13:39:53 +0300 Message-ID: Subject: Re: Remove options from poudriere option files for ports which were removed in the port To: Matthias Fechner Cc: FreeBSD Ports Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 10:39:55 -0000 On Fri, Jul 1, 2016 at 1:17 PM, Matthias Fechner wrote= : > Dear all, > > it seems that poudriere can only add new options to its own options > tracking, but cannot remove options that where removed from the Makefile > of the port. > > Concrete example is for mail/postfix > > The option SPF was removed (2016-02-28): > https://www.freshports.org/mail/postfix/ > > But if I execute: > poudriere options -j 103amd64 -f 103amd64-pkglist > > it will not remove the option from the options file: > 103amd64-options/mail_postfix/options > > Is there a possibility to clean up all the option files without starting > again at zero with: > poudriere options -c -j 103amd64 -f 103amd64-pkglist > > Thanks. > > > Gru=C3=9F > Matthias > This is not a feature/bug of poudriere but of the ports system itself. There's no tracking of obsoleted or removed options and no clever methods to clean them up. It's only when you remove the options with 'make rmconfig' and rewrite them again trough the options dialog the obsoleted ones will be gone. -Kimmo From owner-freebsd-ports@freebsd.org Fri Jul 1 10:47:35 2016 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 D2613B8E25C for ; Fri, 1 Jul 2016 10:47:35 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) 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 BE3CA2D37 for ; Fri, 1 Jul 2016 10:47:35 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: by mailman.ysv.freebsd.org (Postfix) id BD803B8E25B; Fri, 1 Jul 2016 10:47:35 +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 BAE39B8E25A for ; Fri, 1 Jul 2016 10:47:35 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 787472D35 for ; Fri, 1 Jul 2016 10:47:34 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id B8E7F28478; Fri, 1 Jul 2016 12:47:25 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 938B728452; Fri, 1 Jul 2016 12:47:24 +0200 (CEST) Message-ID: <57764A3C.5000609@quip.cz> Date: Fri, 01 Jul 2016 12:47:24 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Matthias Fechner , ports@freebsd.org Subject: Re: Remove options from poudriere option files for ports which were removed in the port References: <71272a33-1a98-47a1-394d-725def6282a5@fechner.net> In-Reply-To: <71272a33-1a98-47a1-394d-725def6282a5@fechner.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 10:47:35 -0000 Matthias Fechner wrote on 07/01/2016 12:17: > Dear all, > > it seems that poudriere can only add new options to its own options > tracking, but cannot remove options that where removed from the Makefile > of the port. > > Concrete example is for mail/postfix > > The option SPF was removed (2016-02-28): > https://www.freshports.org/mail/postfix/ > > But if I execute: > poudriere options -j 103amd64 -f 103amd64-pkglist > > it will not remove the option from the options file: > 103amd64-options/mail_postfix/options > > Is there a possibility to clean up all the option files without starting > again at zero with: > poudriere options -c -j 103amd64 -f 103amd64-pkglist I don't think it's worth the effort. The old no longer existent options stored in the options files are harmless and simply unused by the ports Makefile. The options files are not intended to be user editable / viewable. The old options will be removed when some changes will be saved. And I am not sure that this is a problem of poudriere. I think it's rather issue in ports options framework. Isn't it? Miroslav Lachman From owner-freebsd-ports@freebsd.org Fri Jul 1 12:03:45 2016 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 7FED3B86627 for ; Fri, 1 Jul 2016 12:03:45 +0000 (UTC) (envelope-from jdm7dv@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4EA8D2F2A for ; Fri, 1 Jul 2016 12:03:45 +0000 (UTC) (envelope-from jdm7dv@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id a5so16209326ita.1 for ; Fri, 01 Jul 2016 05:03:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=Jkl5gvI6Cdw2tjWxj9xp/FmRtCrwKmtxxXcnKnfMWk4=; b=iLyqndPdy01/SzEeWD4rSqu4mJqexiu04lLi43+SqN2JfXBdvKP8pj+hFB9BpldtpN Trl5/tNAbRH5vLEYG2FkShYV/rjK+9QmUp8d2Im2fBBM1nBMpWmaw0b4ln5rqhLr9KOk uDNixy974PZS0eu1pWLk/1Vyo5Qb/LWOvMx5+8OUT25pRn0XMj4gI2koyO/Ft3ID5Ss8 qe+n/zLIP2nBX/jq0zxGiaOjJiOizcEFuPExga6GjiS98oTYb51u7RbIKHaY/Himl2N+ aQo3tTLt8zokP1YhMbp7DvY3vdrkenUZ40ptImHZYDHGMijOq1vlbjcmApSGaDXWTKG6 K6mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Jkl5gvI6Cdw2tjWxj9xp/FmRtCrwKmtxxXcnKnfMWk4=; b=FftkUct0C+T/yegZI3c2FxObyYCyXTnsc1Q9iyCOyX/5uUop4qdyk3TfKqUPdR7uRH Yhan6ANu4Z48haAhKzLDkQ53Hqy1fGaw3dL+zA0plppHXgRJp8Ius8PSG3Arup6Hk/Y3 UQmCGJQcOW5qBKdfuJ5NymMJkLl/t/22mkoYVbbSQu/XhMvsVZod+pSq7sKnvitQ+x8c 5iKoviEeIWaOLsE1+I8fDP/IaPFacJcXiuwwH6tSukhQq3zmZ6vTmztnt+HCSvSy7ZWp 0udbqlUPw3sNSQFMhqpssxL/PWELpuYVCzeHYGa/bnQnrSG4+1RAfCvdR55Fv4W2+ogE tYbA== X-Gm-Message-State: ALyK8tKAdZbeP2DPvGp5CqtYaM5pS3np6CDj4dloJFxlhyWivVYzCx9M9RFSVu3mGwmCquBpTUybcbBYp6apzQ== X-Received: by 10.36.57.199 with SMTP id l190mr32968751ita.5.1467374624160; Fri, 01 Jul 2016 05:03:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.28.15 with HTTP; Fri, 1 Jul 2016 05:03:43 -0700 (PDT) From: Jonathan Moore Date: Fri, 1 Jul 2016 08:03:43 -0400 Message-ID: Subject: OrbFit Software on FreeBSD To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 12:03:45 -0000 Hi, I was wondering it OrbFit was in the ports. I really haven't looked yet. It is what MPC uses, the nerve center for international asteroid detection. http://adams.dm.unipi.it/orbfit/ Thanks, Jonathan Moore From owner-freebsd-ports@freebsd.org Fri Jul 1 12:24:03 2016 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 E6868B86C0D for ; Fri, 1 Jul 2016 12:24:03 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [217.115.13.198]) (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 3359C2A60 for ; Fri, 1 Jul 2016 12:24:02 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: (qmail 40949 invoked from network); 1 Jul 2016 12:23:54 -0000 Received: from elektropost.org (HELO elektropost.org) (erdgeist@erdgeist.org) by elektropost.org with ESMTPS (DHE-RSA-AES128-SHA encrypted); 1 Jul 2016 12:23:54 -0000 Subject: Re: qmail maintainer looking for committer, added rc-scripts To: Kurt Jaeger References: <57a240da-5d36-0eec-fffa-7617d86ee2c7@erdgeist.org> <20160625144502.GB64102@home.opsec.eu> Cc: freebsd-ports From: Dirk Engling Message-ID: Date: Fri, 1 Jul 2016 14:23:53 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <20160625144502.GB64102@home.opsec.eu> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 12:24:04 -0000 On 25.06.16 16:45, Kurt Jaeger wrote: > Done. I noticed the port having several issues with portlint. If I start fixing them now, is there a way to release the port with identical ports version and patch level? I would not want users bothering to install "new" versions that only differ in the port's Makefile. erdgeist From owner-freebsd-ports@freebsd.org Fri Jul 1 12:34:29 2016 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 494E4B871B5 for ; Fri, 1 Jul 2016 12:34:29 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 138F52026 for ; Fri, 1 Jul 2016 12:34:29 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 2EBC5BDC8A; Fri, 1 Jul 2016 14:34:26 +0200 (CEST) Received: from gw.in.absolight.net (gw-ecl.in.absolight.net [79.143.241.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.in.absolight.net", Issuer "CA Cert Signing Authority" (not verified)) by prod2.absolight.net (Postfix) with ESMTPSA id 0726FBDC7F; Fri, 1 Jul 2016 14:34:26 +0200 (CEST) Received: from ogg.in.absolight.net (ogg.in.absolight.net [79.143.241.239]) by gw.in.absolight.net (Postfix) with ESMTP id 901D8616A; Fri, 1 Jul 2016 14:34:24 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by ogg.in.absolight.net (Postfix) with ESMTP id 91B252B97978; Fri, 1 Jul 2016 14:34:23 +0200 (CEST) Date: Fri, 01 Jul 2016 14:34:22 +0200 From: Mathieu Arnold To: Dirk Engling , Kurt Jaeger cc: freebsd-ports Subject: Re: qmail maintainer looking for committer, added rc-scripts Message-ID: <50DC73D12EA62465164D2E67@ogg.in.absolight.net> In-Reply-To: References: <57a240da-5d36-0eec-fffa-7617d86ee2c7@erdgeist.org> <20160625144502.GB64102@home.opsec.eu> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========E26E242776B713155333==========" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 12:34:29 -0000 --==========E26E242776B713155333========== Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline +--On 1 juillet 2016 14:23:53 +0200 Dirk Engling wrote: | On 25.06.16 16:45, Kurt Jaeger wrote: | |> Done. | | I noticed the port having several issues with portlint. If I start | fixing them now, is there a way to release the port with identical ports | version and patch level? | | I would not want users bothering to install "new" versions that only | differ in the port's Makefile. The qmail ports are horrible, mostly because of qmail. portlint is an external static lint tool, it will get things wrong, and it should not be followed blindly. -- Mathieu Arnold --==========E26E242776B713155333========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQJ8BAEBCgBmBQJXdmNOXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IHnAP/0FCafTlyCClHmgVA294EuOA G+QU838Qo5UxAnk8jvezDBYHgeeCpNP0pP8Tppam+AfYZkVNEFsiFpWrcI0s/YzR JpqvF7Owb+eZ/zkDySwuVQ7D/QaVz2uFc5fTg6qo+be0+7yvLO2ggAPU/6ojNiRD ceCRjYYoQtmyT/fNtHGdGx5731zhNoNf8XutWTZ69DLQMVO/vGWdSOheu24vuMbF knxip/PnV0StYyZzhinuj1+caLj3zK7kXV4p5561bileq/+TogPJfnkIC1iXisWA 3t+u9MRVdbwY3TLV36ssd42Nno29nBeFBP65VwHduQxL8e8c3MQsGarO0FCSkSef /9EP79i2OE7P1grhpbjmgVzcArMBZl+JmfEDdhWaUcbkOxFjEFcYJJITckxt91RC TqC90r1ww+l0ZnB5leoDM1RS5jFcvuMpu9Cet0NZqYi0pwC4xt5xKzvRxbSmgc+I MRQbfTRFVahHpCvmPWhrmcF3hLx9eNmcgso5PYfHanPsokFbu5WE+rZeTaFcGjaq 8mp+Z0BbyLmtbq/Fusz8AJj1Z2aRmnfnuukcGD8bKqIbZgnCrrcho93Ehkl5ZUTa eWT6OAqc6CuCQLZXGGhD4xQkl231yymsYJA6YNv3QM6SFcBVwssLJfo9dr/vQb81 WUGawFF7VSKzthPihd56 =mtKg -----END PGP SIGNATURE----- --==========E26E242776B713155333==========-- From owner-freebsd-ports@freebsd.org Fri Jul 1 12:36:30 2016 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 4241CB87308 for ; Fri, 1 Jul 2016 12:36:30 +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 04A99211A for ; Fri, 1 Jul 2016 12:36:30 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bIxgL-0007pn-Or; Fri, 01 Jul 2016 14:36:29 +0200 Date: Fri, 1 Jul 2016 14:36:29 +0200 From: Kurt Jaeger To: Dirk Engling Cc: Kurt Jaeger , freebsd-ports Subject: Re: qmail maintainer looking for committer, added rc-scripts Message-ID: <20160701123629.GI79889@home.opsec.eu> References: <57a240da-5d36-0eec-fffa-7617d86ee2c7@erdgeist.org> <20160625144502.GB64102@home.opsec.eu> 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.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 12:36:30 -0000 Hi! > > Done. > > I noticed the port having several issues with portlint. If I start > fixing them now, is there a way to release the port with identical ports > version and patch level? That depends on the changes. If the files ending up in the stagedir are different, then the PORTREVISION++ rule applies. > I would not want users bothering to install "new" versions that only > differ in the port's Makefile. Bending rules is frowned upon, but "wenn's der Wahrheitsfindung dient" 8-) -- pi@opsec.eu +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Fri Jul 1 13:31:13 2016 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 37EBBB87FAC for ; Fri, 1 Jul 2016 13:31:13 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from mail.skysmurf.nl (spectrum.skysmurf.nl [83.162.175.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.skysmurf.nl", Issuer "mail.skysmurf.nl" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D3BD92A21 for ; Fri, 1 Jul 2016 13:31:11 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from spectrum.skysmurf.nl (mail.skysmurf.nl [192.168.42.4]) by mail.skysmurf.nl (8.15.2/8.15.2) with SMTP id u61DMSc8032820; Fri, 1 Jul 2016 15:22:58 +0200 (CEST) (envelope-from freebsd@skysmurf.nl) Received: by spectrum.skysmurf.nl (sSMTP sendmail emulation); Fri, 01 Jul 2016 15:22:28 +0200 Date: Fri, 1 Jul 2016 15:22:27 +0200 From: Alphons van Werven To: Jonathan Moore Cc: freebsd-ports@freebsd.org Subject: Re: OrbFit Software on FreeBSD Message-ID: <20160701132227.GA32768@spectrum.skysmurf.nl> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fdj2RfSjLxBAspz7" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.skysmurf.nl/~fonz/fonz_pubkey.asc User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 13:31:13 -0000 --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Jonathan Moore wrote: > I was wondering it OrbFit was in the ports. I really haven't looked yet. I can't find it in the ports tree. I'd be happy to see if I can create a port for it, *provided* I can find the time. HTH, Fonz --=20 A.J. "Fonz" van Werven mailsig: Help! I'm a prisoner in a Chinese fortune cookie factory. --fdj2RfSjLxBAspz7 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJXdm6TAAoJEAfP7gJTaCe8RYIQAMWDF22vcHnZ8TmK7QuS4vqz 6sssRjIk76Pf6U0bY/DGhhoAp9XtP8HQwNFlYAq7qjygKXNoyNZakI7Z8T7N5rD9 qa2SudJlsQFPtVVfvSW7SToSzUAUUiMzylg+zfAw9VxovS9o0XoM80pWaTLEaTYL BDjtWI/t6mGcg4MG/4V4zXthMLm36/cX/swpli5rLqusW9kczIMHO769pa3pKkCU kvUWlcvmRqO1Ef187VLKpHF4X4W1vGSkTWjGm1v7ejPrkZs7S52mUIiM3Rq1e8a9 awt8mgs+mPAIk3uYfmVrbM9vLi4qSZSSUq7JaodW4ng20f27aNqXBQetco0aX7Qy Uo16r1TTImdngzftPwKqgjFcOY/CAYEkyU1JlkMqWVnMGFnj6OhH6by3oE9+JoAm XQfOzDWNc7uDQxeJ7SyKnLvpEBxXyYy4lsXB6ryb1EHaS3029KyobQufbSzltcsN YIjue9Wu13ORVnUSpC+Nt6PPt801frjORopU0RF3q1X9cXP5VO8deIpGStd/UDLP SCu582XwtVSOPZT7vDhTy4fZCBQYRy9qyT60XKFurUgHJWTOzAHUnukA8qGFJ7KA 9GGeFK7ZLyNXVT7nAHah4GX4OAKsL4NhzLinS+1o/bci8EyI1gWdZfMyGNd687VL P/zSTkRIN+ZMZnChO2E4 =k+Tx -----END PGP SIGNATURE----- --fdj2RfSjLxBAspz7-- From owner-freebsd-ports@freebsd.org Fri Jul 1 13:38:37 2016 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 58212B882A8 for ; Fri, 1 Jul 2016 13:38:37 +0000 (UTC) (envelope-from michelle@sorbs.net) 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 467322C61 for ; Fri, 1 Jul 2016 13:38:37 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: by mailman.ysv.freebsd.org (Postfix) id 4251CB882A7; Fri, 1 Jul 2016 13:38:37 +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 41FF5B882A6 for ; Fri, 1 Jul 2016 13:38:37 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (mail.sorbs.net [67.231.146.200]) by mx1.freebsd.org (Postfix) with ESMTP id 35A392C60 for ; Fri, 1 Jul 2016 13:38:36 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0O9M0016RZGJUW00@hades.sorbs.net> for ports@freebsd.org; Fri, 01 Jul 2016 05:45:57 -0700 (PDT) Subject: Re: Remove options from poudriere option files for ports which were removed in the port To: Miroslav Lachman <000.fbsd@quip.cz>, ports@freebsd.org References: <71272a33-1a98-47a1-394d-725def6282a5@fechner.net> <57764A3C.5000609@quip.cz> From: Michelle Sullivan Message-id: <57766442.40207@sorbs.net> Date: Fri, 01 Jul 2016 14:38:26 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 In-reply-to: <57764A3C.5000609@quip.cz> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 13:38:37 -0000 Miroslav Lachman wrote: > > > I don't think it's worth the effort. The old no longer existent > options stored in the options files are harmless and simply unused by > the ports Makefile. The options files are not intended to be user > editable / viewable. The old options will be removed when some changes > will be saved. Most of the time you are correct... however there is a gotcha.. Select a non default option, maintainer renames the option, suddenly subsequent packages are build without the option.. Not so much of a problem until you're talking about something like OpenSSL from Ports and OpenLDAP client and GSSAPI in some mix and match and one option suddently changes and some other dependent port is fundamentally changed where a security issue occurs and the new package is installed without the poor b******d looking after the machine realising that on reboot, apache is going to break, sudo is going to bread, access to postgresql is going to break etc etc etc... (I'm quoting some random sh*te mixed with experience here - as don't remember the exact details but I got caught - fortunately in my dev environment rather than prod, but you can be certain some will just deploy and get nailed... remote access only via SSH and no SU on non console etc..) > > And I am not sure that this is a problem of poudriere. I think it's > rather issue in ports options framework. Isn't it? Correct (but also poudriere wouln't get the change either.) -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-ports@freebsd.org Fri Jul 1 16:33:52 2016 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 C779DB8F686 for ; Fri, 1 Jul 2016 16:33:52 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from anny.lostinspace.de (anny.lostinspace.de [IPv6:2001:608:a02::33]) (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 8C57F2CB0 for ; Fri, 1 Jul 2016 16:33:52 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from server.idefix.lan (aftr-88-217-181-136.dynamic.mnet-online.de [88.217.181.136]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: idefix@fechner.net) by anny.lostinspace.de (Postfix) with ESMTPSA id 83B5859962C for ; Fri, 1 Jul 2016 18:33:41 +0200 (CEST) DMARC-Filter: OpenDMARC Filter v1.3.1 anny.lostinspace.de 83B5859962C Authentication-Results: anny.lostinspace.de; dmarc=none header.from=fechner.net DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=fechner.net; s=default; t=1467390821; bh=fSS9XG9weyORvBe5xWCq9h0IuUbkqSzL4/PqXLXkggA=; h=Subject:To:References:From:Date:In-Reply-To; b=CyuEPXrDL2HIz+74HsvrDknKxhIewB29DNwejytSyS5BztqE7uisSfPpAcBBU7INd GwEKZueKwicy2uPfcgNt0K52s2kdKe+pxLXTMKsK48dTSBzNLbfsc+rVO+3Oh3jzVB np5dEtT8QypofZ6eGsB9mQanm+c14LxUH/vg1FfY= Received: from [192.168.0.151] (aftr-88-217-181-136.dynamic.mnet-online.de [88.217.181.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by server.idefix.lan (Postfix) with ESMTPSA id EB49C402C33 for ; Fri, 1 Jul 2016 18:33:40 +0200 (CEST) Subject: Re: Remove options from poudriere option files for ports which were removed in the port To: freebsd-ports@freebsd.org References: <71272a33-1a98-47a1-394d-725def6282a5@fechner.net> From: Matthias Fechner Message-ID: Date: Fri, 1 Jul 2016 18:32:48 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 16:33:52 -0000 Am 01.07.2016 um 12:39 schrieb Kimmo Paasiala: > This is not a feature/bug of poudriere but of the ports system itself. > There's no tracking of obsoleted or removed options and no clever > methods to clean them up. It's only when you remove the options with > 'make rmconfig' and rewrite them again trough the options dialog the > obsoleted ones will be gone. thanks a lot. So I just keep to option files, as I do not really care what is in there. Poudriere is handling new optioins nicely. Thanks for explanation! Gruß Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook From owner-freebsd-ports@freebsd.org Fri Jul 1 17:28:33 2016 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 198BCB8E521 for ; Fri, 1 Jul 2016 17:28:33 +0000 (UTC) (envelope-from markmoellering@psyberation.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id F147A2B86 for ; Fri, 1 Jul 2016 17:28:32 +0000 (UTC) (envelope-from markmoellering@psyberation.com) Received: by mailman.ysv.freebsd.org (Postfix) id ECD18B8E520; Fri, 1 Jul 2016 17:28:32 +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 EC79BB8E51F for ; Fri, 1 Jul 2016 17:28:32 +0000 (UTC) (envelope-from markmoellering@psyberation.com) Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B4D7A2B85 for ; Fri, 1 Jul 2016 17:28:32 +0000 (UTC) (envelope-from markmoellering@psyberation.com) Received: by mail-qk0-x234.google.com with SMTP id t127so213367962qkf.1 for ; Fri, 01 Jul 2016 10:28:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=psyberation-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=E/gFqEaj6ur/cS0bN5Yu4HD47NJ/WsdPlxNe1FT3eWs=; b=u+/MctzFFvIn3tNk4Rdi/971oVgv9fimZCEpJFa34E/ksJkKaUePAVvst9Y5YRopkA SAUEoMrz1pzXsdrd/KwOBTzjmHwCEe+7MWRqrNWShI+43uqZ0NJYF/JnJpoc/rSc1Ur3 z8sredBQZmOXGnGGn2kP9yI2uk4xDZksV1RriA59vsuXvAu06Wsnjij+G42TUgAPNKMc WBcXNrFYqvxMM12rn9untgCFYprlqIjaPriiXyly8Sr4lAfWCgnr3Stf4zG2H25FnECc gf73renyG8J8EMJepvTdhtaaTqBAG7iHa6D+twPOl7wmiZlME1VYBbsQrYHGSWeomq7/ 6B3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=E/gFqEaj6ur/cS0bN5Yu4HD47NJ/WsdPlxNe1FT3eWs=; b=LDyVsK3URD3GMKnP71vX76Es2+FR2/kTJPazsyEGXt5LX7MZXAKy79Lxsmdh/h/Ffh N96J10oCOkQymHJPVImVyu/8p2K55LqdV7+i9L1YhMPtFQaDgpVmkvPUESZlzmqwKaYE zGpWP2LUbjP16/f1tsGCKfuINYVcjP4QYMuyedNU/xephOWoTAvuC7vBh77DyIjH1SpO 8qDOo6suIC0/i54wCq5lKPeNlO7GWkLy/jSxtHdYVAE4+DvPBb33+mYIuACTCzOwmkud ZnT0uC57GCoy/k2Qc7IFw9ermyxMnHKb7d5nxYTq+aa8+zptiMUD0bbZF7yQtPoYNPE9 iKMA== X-Gm-Message-State: ALyK8tIFtmWGDh5oTJO17LpQoTY69iHm9wO7vQD4wJBKYfyKL01/LA54/hIggje+XjfqnB9vUFd28YhMcjuPQQ== X-Received: by 10.55.192.88 with SMTP id o85mr27344434qki.15.1467394111428; Fri, 01 Jul 2016 10:28:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.49.106 with HTTP; Fri, 1 Jul 2016 10:28:31 -0700 (PDT) From: Mark Moellering Date: Fri, 1 Jul 2016 13:28:31 -0400 Message-ID: Subject: The unfs3 port / package To: ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 17:28:33 -0000 Hello, I recently started using this port and would like to suggest a change to the man page, indicating that this port requires rpcbind_enable="YES" in rc.conf. I also created a short and simple rc script, so that it can be started with the traditional unfsd_enable="YES" setting. Thank you for your time. If you have any questions, or if there is any way in which I can help, please let me know. Sincerely Mark Moellering From owner-freebsd-ports@freebsd.org Fri Jul 1 18:59:25 2016 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 4812FB8FAF8 for ; Fri, 1 Jul 2016 18:59:25 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1455F25F8 for ; Fri, 1 Jul 2016 18:59:25 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id u61IxIBt093652 for ; Fri, 1 Jul 2016 11:59:22 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201607011859.u61IxIBt093652@gw.catspoiler.org> Date: Fri, 1 Jul 2016 11:59:18 -0700 (PDT) From: Don Lewis Subject: what to do when base openssl isn't suitable To: freebsd-ports@FreeBSD.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 18:59:25 -0000 I've got a port that does not work with base openssl because it looks for libssl.pc. Other than that, I don't think it is picky about what flavor of ports ssl is installed. Because the default version of ssl still defaults to base, I don't see a way to get this port to build on the cluster, so there is no way to provide binary packages. That's a problem for end users because this port has bunch of huge build dependencies. Thoughts? From owner-freebsd-ports@freebsd.org Fri Jul 1 19:56:22 2016 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 028BCB8F6E0 for ; Fri, 1 Jul 2016 19:56:22 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.kissl.de (host64.kissl.de [213.239.241.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "*.shmhost.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C0F412DFF; Fri, 1 Jul 2016 19:56:21 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from [192.168.178.47] (ip9234d218.dynamic.kabel-deutschland.de [146.52.210.24]) (Authenticated sender: web104p1) by host64.kissl.de (Postfix) with ESMTPSA id F1FF46AD04; Fri, 1 Jul 2016 21:56:05 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: what to do when base openssl isn't suitable From: Franco Fichtner X-Mailer: iPhone Mail (13F69) In-Reply-To: <201607011859.u61IxIBt093652@gw.catspoiler.org> Date: Fri, 1 Jul 2016 21:56:04 +0200 Cc: freebsd-ports@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: <5E323927-472D-4313-B1CF-ADFADBCF5FB2@lastsummer.de> References: <201607011859.u61IxIBt093652@gw.catspoiler.org> To: Don Lewis X-Virus-Scanned: clamav-milter 0.99 at host64.kissl.de X-Virus-Status: Clean X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 19:56:22 -0000 Hi Don, > On 01.07.2016, at 20:59, Don Lewis wrote: >=20 > I've got a port that does not work with base openssl because it looks > for libssl.pc. Other than that, I don't think it is picky about what > flavor of ports ssl is installed. Because the default version of ssl > still defaults to base, I don't see a way to get this port to build on > the cluster, so there is no way to provide binary packages. That's a > problem for end users because this port has bunch of huge build > dependencies. Thoughts? Take a look at security/letskencrypt which pins its SSL to LibreSSL from por= ts, because it won't build with OpenSSL at all. Really nifty reworks happene= d recently with USES in that regard. Cheers, Franco From owner-freebsd-ports@freebsd.org Fri Jul 1 19:57:33 2016 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 82055B8F738 for ; Fri, 1 Jul 2016 19:57:33 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 4706F2ECE; Fri, 1 Jul 2016 19:57:32 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 96AB628423; Fri, 1 Jul 2016 21:57:29 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 8A2F928416; Fri, 1 Jul 2016 21:57:28 +0200 (CEST) Message-ID: <5776CB28.2000709@quip.cz> Date: Fri, 01 Jul 2016 21:57:28 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Don Lewis , freebsd-ports@FreeBSD.org Subject: Re: what to do when base openssl isn't suitable References: <201607011859.u61IxIBt093652@gw.catspoiler.org> In-Reply-To: <201607011859.u61IxIBt093652@gw.catspoiler.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 19:57:33 -0000 Don Lewis wrote on 07/01/2016 20:59: > I've got a port that does not work with base openssl because it looks > for libssl.pc. Other than that, I don't think it is picky about what > flavor of ports ssl is installed. Because the default version of ssl > still defaults to base, I don't see a way to get this port to build on > the cluster, so there is no way to provide binary packages. That's a > problem for end users because this port has bunch of huge build > dependencies. Thoughts? There are already packages depending on ports OpenSSL because they need /usr/local/libdata/pkgconfig/libssl.pc (installed by openssl-1.0.2_14) so I think you can make port depending on ports openssl. See nginx for example. .if defined(NGINX_OPENSSL) USE_OPENSSL= yes .if ${OSVERSION} < 1100000 WITH_OPENSSL_PORT=yes .endif .endif Miroslav Lachman From owner-freebsd-ports@freebsd.org Fri Jul 1 21:33:43 2016 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 613D9B8F9B6 for ; Fri, 1 Jul 2016 21:33:43 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 362A92D78 for ; Fri, 1 Jul 2016 21:33:43 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id u61LXZxT093978; Fri, 1 Jul 2016 14:33:39 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201607012133.u61LXZxT093978@gw.catspoiler.org> Date: Fri, 1 Jul 2016 14:33:35 -0700 (PDT) From: Don Lewis Subject: Re: what to do when base openssl isn't suitable To: franco@lastsummer.de cc: freebsd-ports@FreeBSD.org In-Reply-To: <5E323927-472D-4313-B1CF-ADFADBCF5FB2@lastsummer.de> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 21:33:43 -0000 On 1 Jul, Franco Fichtner wrote: > Hi Don, > >> On 01.07.2016, at 20:59, Don Lewis wrote: >> >> I've got a port that does not work with base openssl because it looks >> for libssl.pc. Other than that, I don't think it is picky about what >> flavor of ports ssl is installed. Because the default version of ssl >> still defaults to base, I don't see a way to get this port to build on >> the cluster, so there is no way to provide binary packages. That's a >> problem for end users because this port has bunch of huge build >> dependencies. Thoughts? > > Take a look at security/letskencrypt which pins its SSL to LibreSSL from ports, because it won't build with OpenSSL at all. Really nifty reworks happened recently with USES in that regard. Nope, USES=ssl doesn't take an argument. See: From owner-freebsd-ports@freebsd.org Fri Jul 1 21:41:42 2016 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 0B939B8FABE for ; Fri, 1 Jul 2016 21:41:42 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E1B162089 for ; Fri, 1 Jul 2016 21:41:41 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id u61LfYBN093987; Fri, 1 Jul 2016 14:41:38 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201607012141.u61LfYBN093987@gw.catspoiler.org> Date: Fri, 1 Jul 2016 14:41:34 -0700 (PDT) From: Don Lewis Subject: Re: what to do when base openssl isn't suitable To: 000.fbsd@quip.cz cc: freebsd-ports@FreeBSD.org In-Reply-To: <5776CB28.2000709@quip.cz> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 21:41:42 -0000 On 1 Jul, Miroslav Lachman wrote: > Don Lewis wrote on 07/01/2016 20:59: >> I've got a port that does not work with base openssl because it looks >> for libssl.pc. Other than that, I don't think it is picky about what >> flavor of ports ssl is installed. Because the default version of ssl >> still defaults to base, I don't see a way to get this port to build on >> the cluster, so there is no way to provide binary packages. That's a >> problem for end users because this port has bunch of huge build >> dependencies. Thoughts? > > There are already packages depending on ports OpenSSL because they need > /usr/local/libdata/pkgconfig/libssl.pc (installed by openssl-1.0.2_14) > so I think you can make port depending on ports openssl. > See nginx for example. > > .if defined(NGINX_OPENSSL) > USE_OPENSSL= yes USE_OPENSSL is now deprecated and has been replaced by USES=ssl > .if ${OSVERSION} < 1100000 > WITH_OPENSSL_PORT=yes WITH_OPENSSL_PORT is now deprecated. Even before that I don't think it was intended to be used in the port Makefile, only in /etc/make.conf. The suggested replacement is to put DEFAULT_VERSIONS+=ssl=openssl in /etc/make.conf. > .endif > .endif From owner-freebsd-ports@freebsd.org Fri Jul 1 23:14:03 2016 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 56E7BB8F6D0 for ; Fri, 1 Jul 2016 23:14:03 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 352532DEA for ; Fri, 1 Jul 2016 23:14:02 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id u61NF5Lj003804 for ; Fri, 1 Jul 2016 16:15:12 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <201607012141.u61LfYBN093987@gw.catspoiler.org> References: <201607012141.u61LfYBN093987@gw.catspoiler.org> From: "Chris H" Subject: Re: what to do when base openssl isn't suitable Date: Fri, 01 Jul 2016 16:15:12 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <19b788f5df8b3bf6e698418823613d9a@ultimatedns.net> Content-Transfer-Encoding: 8bit X-Milter: Spamilter (Reciever: udns.ultimatedns.net; Sender-ip: 127.0.0.1; Sender-helo: ultimatedns.net; ) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 23:14:03 -0000 On Fri, 1 Jul 2016 14:41:34 -0700 (PDT) Don Lewis wrote > On 1 Jul, Miroslav Lachman wrote: > > Don Lewis wrote on 07/01/2016 20:59: > >> I've got a port that does not work with base openssl because it looks > >> for libssl.pc. Other than that, I don't think it is picky about what > >> flavor of ports ssl is installed. Because the default version of ssl > >> still defaults to base, I don't see a way to get this port to build on > >> the cluster, so there is no way to provide binary packages. That's a > >> problem for end users because this port has bunch of huge build > >> dependencies. Thoughts? > > > > There are already packages depending on ports OpenSSL because they need > > /usr/local/libdata/pkgconfig/libssl.pc (installed by openssl-1.0.2_14) > > so I think you can make port depending on ports openssl. > > See nginx for example. > > > > .if defined(NGINX_OPENSSL) > > USE_OPENSSL= yes > > USE_OPENSSL is now deprecated and has been replaced by USES=ssl > > > .if ${OSVERSION} < 1100000 > > WITH_OPENSSL_PORT=yes > > WITH_OPENSSL_PORT is now deprecated. Even before that I don't think it > was intended to be used in the port Makefile, only in /etc/make.conf. > The suggested replacement is to put DEFAULT_VERSIONS+=ssl=openssl in > /etc/make.conf. Wouldn't something along the lines of SSL_LIB_DEPENDS= libssl.pc:security/openssl get it for you? Just a thought, because you asked. ;-) --Chris > > > > > .endif > > .endif > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Fri Jul 1 23:16:40 2016 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 152CDB8F751 for ; Fri, 1 Jul 2016 23:16:40 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B6552EAE for ; Fri, 1 Jul 2016 23:16:39 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id v199so42330302wmv.0 for ; Fri, 01 Jul 2016 16:16:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=1rXjkDDzRm+7erLVs3xB2jBs2U2k9gQ3W75roBpaAiY=; b=HuOIQ6TUwX+j5utBnos7sDxNWT3YZYbLS8ZjcWGlsQvMu3WPGNUUF0hj5CPRHOYCOH 8zSfKm1S58tEkWixVygcf9xGnUAoD7n7St59Qp8Z6thkgqkaFAlDSta8v4KiRiEgA/DZ 0KUwAIralvEi/lAJuX3/gTEwcep9vtGLC2Hh8s0Y2XnzOEcyWSPsnPQ28o5jfN5GDY/c BTdaERXxlbQrFDua+yUdC/Y3yRsv1xF98oLrj6YTERjJYmNMsuk2TcBWzcPoN+jzObtO Ba1iPF8NiHzo5ucZkRccomuI/zXfKChZfTisz+MFigJmKcCyYgwsnhZm9pEsnFMxOQLG 8cPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=1rXjkDDzRm+7erLVs3xB2jBs2U2k9gQ3W75roBpaAiY=; b=IJfLcLo5O+/lgoYv1m6YU365lFQQutIIXmjSG8OZZcacjLyWDKTIBsDVvIUE+NAL9K jN4vjtOu1rr5B0ftYtL+AXSBr8uzsQNkw8k+HX57Umo2m3qLzn51NiEW8Jj1mtrX8ouy HfGmz73Up+KKT5CjI7eVYrhIfivc8EqfDU+oYxc3LdTxo/4HUjM3y9yARa23ADBr4kZ5 44bPGTHjBSqWrJblE26CheWyXiGxPnP/w0WEnwQLLv+M8UeoDQtEezNFIAtnR6JZwHyy TAjr4MsfbHdYAJi7fNQrH3w874li0Qa+H0UXRVGMH7iTfkwTe68xpKtF4aR4Kd5uC7Mv 6hpw== X-Gm-Message-State: ALyK8tKegZpfGbK8em8UMFGe/VAL+csU7wy1D8gP16XOq9fs/1Gh69XZ4WeEUPINAeqQQw== X-Received: by 10.28.222.136 with SMTP id v130mr524410wmg.90.1467414997752; Fri, 01 Jul 2016 16:16:37 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by smtp.gmail.com with ESMTPSA id u145sm633844wmu.4.2016.07.01.16.16.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Jul 2016 16:16:37 -0700 (PDT) Sender: Baptiste Daroussin Date: Sat, 2 Jul 2016 01:16:36 +0200 From: Baptiste Daroussin To: Chris H Cc: freebsd-ports@freebsd.org Subject: Re: what to do when base openssl isn't suitable Message-ID: <20160701231636.hflccfi7mwnmbpqo@ivaldir.etoilebsd.net> References: <201607012141.u61LfYBN093987@gw.catspoiler.org> <19b788f5df8b3bf6e698418823613d9a@ultimatedns.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bbhzutijx2hoquuo" Content-Disposition: inline In-Reply-To: <19b788f5df8b3bf6e698418823613d9a@ultimatedns.net> User-Agent: Mutt/1.6.1-neo (2016-06-11) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 23:16:40 -0000 --bbhzutijx2hoquuo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 01, 2016 at 04:15:12PM -0700, Chris H wrote: > On Fri, 1 Jul 2016 14:41:34 -0700 (PDT) Don Lewis = wrote >=20 > > On 1 Jul, Miroslav Lachman wrote: > > > Don Lewis wrote on 07/01/2016 20:59: > > >> I've got a port that does not work with base openssl because it looks > > >> for libssl.pc. Other than that, I don't think it is picky about what > > >> flavor of ports ssl is installed. Because the default version of ssl > > >> still defaults to base, I don't see a way to get this port to build = on > > >> the cluster, so there is no way to provide binary packages. That's a > > >> problem for end users because this port has bunch of huge build > > >> dependencies. Thoughts? > > >=20 > > > There are already packages depending on ports OpenSSL because they ne= ed=20 > > > /usr/local/libdata/pkgconfig/libssl.pc (installed by openssl-1.0.2_14= )=20 > > > so I think you can make port depending on ports openssl. > > > See nginx for example. > > >=20 > > > .if defined(NGINX_OPENSSL) > > > USE_OPENSSL=3D yes > >=20 > > USE_OPENSSL is now deprecated and has been replaced by USES=3Dssl > >=20 > > > .if ${OSVERSION} < 1100000 > > > WITH_OPENSSL_PORT=3Dyes > >=20 > > WITH_OPENSSL_PORT is now deprecated. Even before that I don't think it > > was intended to be used in the port Makefile, only in /etc/make.conf. > > The suggested replacement is to put DEFAULT_VERSIONS+=3Dssl=3Dopenssl in > > /etc/make.conf. >=20 > Wouldn't something along the lines of >=20 > SSL_LIB_DEPENDS=3D libssl.pc:security/openssl >=20 libssl.pc? nothing will ever work with this line :) Best regards, Bapt --bbhzutijx2hoquuo Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXdvnRAAoJEGOJi9zxtz5anMoP/RJfDk5n0jwDMzQ1IkjlHJuG GNidtROU19HbU/tJBMhq7qlWbSmTHG8ieBg9QvSaswpH4GgazWzXdFwZqP1xdZsn TlaWV/SybZmP/GRkzKPf+c5kE1zCfYMc56XxCQwDrrEkHCIyN5SL70nWzlVqulwd Uc2nABJ2a0Th/0z3VLLMtl50697RqysT67cmc1R2hzmY2n4NwZ11l2/ru/9fnqmT /XBWnG53dK2N8LcfQuKGwXd43X1WKjIXmgtPT7gony0U4zqokKyEFNS00/Ab5oys pILEHxEKIxacGQY6wd387aJ/0uut1Pl4cWoHhjX6/6NR+DWPMSggMIlSHoQ9a0pA 3AHl8l6CA4RoyCn0Qvgy+MACfAPjXgppp5FeCSlSMl7S03ERz/UuKT+25CsUvVqf GAdwW28KM0WQantogR5dJG/E9rc9ORSP1BNyndoOHybZM/yySlQgjun/VU0nvEvx Zty2AF8NF2hXHjfQbuo/+q9xA4iVIHMAEeFziIhu8GY9hXgvUENpVJ+4WRwdOa+C aMxuGPxP3J6K/7eSbafAV914jiF9ku7+hObPMRfmG0gpAM3BpbecUVrcW8gDgCfq XzJBDeBmmZ1oIIt8qlJ+PgRhV10CgciwHX4Mx0Poh5hfl/lfH+VnaA9n8vIdQ59R piy0Btdp2/ZF26RACRfV =dzRf -----END PGP SIGNATURE----- --bbhzutijx2hoquuo-- From owner-freebsd-ports@freebsd.org Fri Jul 1 23:17:47 2016 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 B5558B8F7AC for ; Fri, 1 Jul 2016 23:17:47 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7CCD52F45 for ; Fri, 1 Jul 2016 23:17:47 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id u61NIpWY004209 for ; Fri, 1 Jul 2016 16:18:57 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <19b788f5df8b3bf6e698418823613d9a@ultimatedns.net> References: <201607012141.u61LfYBN093987@gw.catspoiler.org>, <19b788f5df8b3bf6e698418823613d9a@ultimatedns.net> From: "Chris H" Subject: Re: what to do when base openssl isn't suitable Date: Fri, 01 Jul 2016 16:18:57 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-Milter: Spamilter (Reciever: udns.ultimatedns.net; Sender-ip: 127.0.0.1; Sender-helo: ultimatedns.net; ) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 23:17:47 -0000 On Fri, 01 Jul 2016 16:15:12 -0700 "Chris H" wrote > On Fri, 1 Jul 2016 14:41:34 -0700 (PDT) Don Lewis > wrote > > > On 1 Jul, Miroslav Lachman wrote: > > > Don Lewis wrote on 07/01/2016 20:59: > > >> I've got a port that does not work with base openssl because it looks > > >> for libssl.pc. Other than that, I don't think it is picky about what > > >> flavor of ports ssl is installed. Because the default version of ssl > > >> still defaults to base, I don't see a way to get this port to build on > > >> the cluster, so there is no way to provide binary packages. That's a > > >> problem for end users because this port has bunch of huge build > > >> dependencies. Thoughts? > > > > > > There are already packages depending on ports OpenSSL because they need > > > /usr/local/libdata/pkgconfig/libssl.pc (installed by openssl-1.0.2_14) > > > so I think you can make port depending on ports openssl. > > > See nginx for example. > > > > > > .if defined(NGINX_OPENSSL) > > > USE_OPENSSL= yes > > > > USE_OPENSSL is now deprecated and has been replaced by USES=ssl > > > > > .if ${OSVERSION} < 1100000 > > > WITH_OPENSSL_PORT=yes > > > > WITH_OPENSSL_PORT is now deprecated. Even before that I don't think it > > was intended to be used in the port Makefile, only in /etc/make.conf. > > The suggested replacement is to put DEFAULT_VERSIONS+=ssl=openssl in > > /etc/make.conf. > > Wouldn't something along the lines of > > SSL_LIB_DEPENDS= libssl.pc:security/openssl > > get it for you? Ahem... that *should* have read SSL_LIB_DEPENDS= libssl.so:security/openssl Sorry. > > Just a thought, because you asked. ;-) > > --Chris > > > > > > > > > .endif > > > .endif > > > > > > _______________________________________________ > > freebsd-ports@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Fri Jul 1 23:31:05 2016 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 2CFBAB8FA1F for ; Fri, 1 Jul 2016 23:31:05 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E5A2F2657 for ; Fri, 1 Jul 2016 23:31:04 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id u61NW8Ta005450 for ; Fri, 1 Jul 2016 16:32:14 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <20160701231636.hflccfi7mwnmbpqo@ivaldir.etoilebsd.net> References: <201607012141.u61LfYBN093987@gw.catspoiler.org> <19b788f5df8b3bf6e698418823613d9a@ultimatedns.net>, <20160701231636.hflccfi7mwnmbpqo@ivaldir.etoilebsd.net> From: "Chris H" Subject: Re: what to do when base openssl isn't suitable Date: Fri, 01 Jul 2016 16:32:14 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <4c6170a82043b9d9b3064712ac66c411@ultimatedns.net> Content-Transfer-Encoding: 8bit X-Milter: Spamilter (Reciever: udns.ultimatedns.net; Sender-ip: 127.0.0.1; Sender-helo: ultimatedns.net; ) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 23:31:05 -0000 On Sat, 2 Jul 2016 01:16:36 +0200 Baptiste Daroussin wrote > On Fri, Jul 01, 2016 at 04:15:12PM -0700, Chris H wrote: > > On Fri, 1 Jul 2016 14:41:34 -0700 (PDT) Don Lewis > > wrote > > > On 1 Jul, Miroslav Lachman wrote: > > > > Don Lewis wrote on 07/01/2016 20:59: > > > >> I've got a port that does not work with base openssl because it looks > > > >> for libssl.pc. Other than that, I don't think it is picky about what > > > >> flavor of ports ssl is installed. Because the default version of ssl > > > >> still defaults to base, I don't see a way to get this port to build on > > > >> the cluster, so there is no way to provide binary packages. That's a > > > >> problem for end users because this port has bunch of huge build > > > >> dependencies. Thoughts? > > > > > > > > There are already packages depending on ports OpenSSL because they need > > > > /usr/local/libdata/pkgconfig/libssl.pc (installed by openssl-1.0.2_14) > > > > so I think you can make port depending on ports openssl. > > > > See nginx for example. > > > > > > > > .if defined(NGINX_OPENSSL) > > > > USE_OPENSSL= yes > > > > > > USE_OPENSSL is now deprecated and has been replaced by USES=ssl > > > > > > > .if ${OSVERSION} < 1100000 > > > > WITH_OPENSSL_PORT=yes > > > > > > WITH_OPENSSL_PORT is now deprecated. Even before that I don't think it > > > was intended to be used in the port Makefile, only in /etc/make.conf. > > > The suggested replacement is to put DEFAULT_VERSIONS+=ssl=openssl in > > > /etc/make.conf. > > > > Wouldn't something along the lines of > > > > SSL_LIB_DEPENDS= libssl.pc:security/openssl > > > libssl.pc? nothing will ever work with this line :) Right, and I noticed what I had done the moment I hit the send button. So was forced to send another reply with the *intended* suggestion. :/ SSLLIB_DESC= OpenSSL support SSL_LIB_DEPENDS= libssl.so:security/openssl SSLLIB_CONFIGURE_WITH= ssllib or perhaps more simply LIB_DEPENDS= libssl.so:security/openssl in an appropriate location for an SSL option, assuming it's even optional. > > Best regards, > Bapt --Chris -- From owner-freebsd-ports@freebsd.org Fri Jul 1 23:35:11 2016 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 B9DE7B8FB4A for ; Fri, 1 Jul 2016 23:35:11 +0000 (UTC) (envelope-from jbeich@vfemail.net) Received: from vfemail.net (onethreetwo.vfemail.net [199.16.11.132]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7B0B628DB for ; Fri, 1 Jul 2016 23:35:11 +0000 (UTC) (envelope-from jbeich@vfemail.net) Received: (qmail 29660 invoked by uid 89); 1 Jul 2016 23:35:04 -0000 Received: from localhost (HELO freequeue.vfemail.net) (127.0.0.1) by localhost with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Jul 2016 23:35:04 -0000 Received: (qmail 29562 invoked by uid 89); 1 Jul 2016 23:34:47 -0000 Received: by simscan 1.3.1 ppid: 29558, pid: 29560, t: 0.0025s scanners:none Received: from unknown (HELO smtp102-2.vfemail.net) (172.16.100.62) by FreeQueue with SMTP; 1 Jul 2016 23:34:47 -0000 Received: (qmail 9971 invoked by uid 89); 1 Jul 2016 23:34:47 -0000 Received: by simscan 1.4.0 ppid: 9964, pid: 9967, t: 0.6097s scanners:none Received: from unknown (HELO nil) (amJlaWNoQHZmZW1haWwubmV0@172.16.100.27) by mail.vfemail.net with ESMTPA; 1 Jul 2016 23:34:46 -0000 From: Jan Beich To: Don Lewis Cc: freebsd-ports@FreeBSD.org Subject: Re: what to do when base openssl isn't suitable References: <201607011859.u61IxIBt093652@gw.catspoiler.org> Date: Sat, 02 Jul 2016 01:34:38 +0200 In-Reply-To: <201607011859.u61IxIBt093652@gw.catspoiler.org> (Don Lewis's message of "Fri, 1 Jul 2016 11:59:18 -0700 (PDT)") Message-ID: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2016 23:35:11 -0000 --=-=-= Content-Type: text/plain Don Lewis writes: > I've got a port that does not work with base openssl because it looks > for libssl.pc. Other than that, I don't think it is picky about what > flavor of ports ssl is installed. Because the default version of ssl > still defaults to base, I don't see a way to get this port to build on > the cluster, so there is no way to provide binary packages. That's a > problem for end users because this port has bunch of huge build > dependencies. Thoughts? Have you tried putting a copy of libssl.pc under ${FILESDIR} and adjusting PKG_CONFIG_PATH or forcing configure to accept *FLAGS without? # from net-p2p/zetacoin/Makefile CONFIGURE_ENV= CRYPTO_CFLAGS="-I${OPENSSLINC}" CRYPTO_LIBS="-L${OPENSSLLIB} -lcrypto" \ SSL_CFLAGS="-I${OPENSSLINC}" SSL_LIBS="-L${OPENSSLLIB} -lssl" # from mail/mpop/Makefile OPENSSL_CONFIGURE_ENV=${OPENSSLINC:M/usr/include:C,.+,libssl_CFLAGS=" ",} \ ${OPENSSLLIB:M/usr/lib:C,.+,libssl_LIBS="-lssl -lcrypto",} --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQF8BAEBCgBmBQJXdv4OXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREQjQ0MzY3NEM3RDIzNTc4NkUxNDkyQ0VF NEM3Nzg4MzQ3OURCRERCAAoJEOTHeINHnb3bRckH/jMSn+ENpbsTBa/0GtRMud02 TDLge4+LNSjUGGYqxQVRSX5dREUnYw7BtuJsfPNOQAAkvgmrcBqoeOc2m4L0oYwI qjfuY6WOn+UuLlDPhsu1J24cgpmkNEZ7M6QHam9hyCZUXB3mjU+hFCmntpUxagzR rbxmTlF/WoefNo9g/zQ9uEH79spCrhdnP90uCGHhi3sGwxnS6POpJHnZA+0vZ4+j +WkoFjZlcdahS/tuXQLYGgDtRYN9MsWdS3JbEsd4+aGi8owJ4uy6AQLPSxCsKlee WteqvNKfrRTDDOvWNMR9eKdx1EDphQ6STiIfKSgMLvOWlGagHl4wKbEUfA3x80Q= =VjFW -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-ports@freebsd.org Sat Jul 2 02:25:49 2016 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 9B266B8F835 for ; Sat, 2 Jul 2016 02:25:49 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F25F2E2C for ; Sat, 2 Jul 2016 02:25:49 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id u622Pfbc094491; Fri, 1 Jul 2016 19:25:45 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201607020225.u622Pfbc094491@gw.catspoiler.org> Date: Fri, 1 Jul 2016 19:25:41 -0700 (PDT) From: Don Lewis Subject: Re: what to do when base openssl isn't suitable To: jbeich@vfemail.net cc: freebsd-ports@FreeBSD.org In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2016 02:25:49 -0000 On 2 Jul, Jan Beich wrote: > Don Lewis writes: > >> I've got a port that does not work with base openssl because it looks >> for libssl.pc. Other than that, I don't think it is picky about what >> flavor of ports ssl is installed. Because the default version of ssl >> still defaults to base, I don't see a way to get this port to build on >> the cluster, so there is no way to provide binary packages. That's a >> problem for end users because this port has bunch of huge build >> dependencies. Thoughts? > > Have you tried putting a copy of libssl.pc under ${FILESDIR} and > adjusting PKG_CONFIG_PATH or forcing configure to accept *FLAGS without? > > # from net-p2p/zetacoin/Makefile > CONFIGURE_ENV= CRYPTO_CFLAGS="-I${OPENSSLINC}" CRYPTO_LIBS="-L${OPENSSLLIB} -lcrypto" \ > SSL_CFLAGS="-I${OPENSSLINC}" SSL_LIBS="-L${OPENSSLLIB} -lssl" > > # from mail/mpop/Makefile > OPENSSL_CONFIGURE_ENV=${OPENSSLINC:M/usr/include:C,.+,libssl_CFLAGS=" ",} \ > ${OPENSSLLIB:M/usr/lib:C,.+,libssl_LIBS="-lssl -lcrypto",} Option #2 works, except on FreeBSD 9, where the base version of OpenSSL is too old. I'm ok with setting IGNORE in that case. From owner-freebsd-ports@freebsd.org Sat Jul 2 02:31:19 2016 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 8BE6AB8FAD5 for ; Sat, 2 Jul 2016 02:31:19 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FB6F209D for ; Sat, 2 Jul 2016 02:31:19 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id u622UvTt094500; Fri, 1 Jul 2016 19:31:01 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201607020231.u622UvTt094500@gw.catspoiler.org> Date: Fri, 1 Jul 2016 19:30:57 -0700 (PDT) From: Don Lewis Subject: Re: what to do when base openssl isn't suitable To: bsd-lists@bsdforge.com cc: freebsd-ports@freebsd.org In-Reply-To: <4c6170a82043b9d9b3064712ac66c411@ultimatedns.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2016 02:31:19 -0000 On 1 Jul, Chris H wrote: > On Sat, 2 Jul 2016 01:16:36 +0200 Baptiste Daroussin wrote > >> On Fri, Jul 01, 2016 at 04:15:12PM -0700, Chris H wrote: >> > On Fri, 1 Jul 2016 14:41:34 -0700 (PDT) Don Lewis >> > wrote >> > > On 1 Jul, Miroslav Lachman wrote: >> > > > Don Lewis wrote on 07/01/2016 20:59: >> > > >> I've got a port that does not work with base openssl because it looks >> > > >> for libssl.pc. Other than that, I don't think it is picky about what >> > > >> flavor of ports ssl is installed. Because the default version of ssl >> > > >> still defaults to base, I don't see a way to get this port to build on >> > > >> the cluster, so there is no way to provide binary packages. That's a >> > > >> problem for end users because this port has bunch of huge build >> > > >> dependencies. Thoughts? >> > > > >> > > > There are already packages depending on ports OpenSSL because they need >> > > > /usr/local/libdata/pkgconfig/libssl.pc (installed by openssl-1.0.2_14) >> > > > so I think you can make port depending on ports openssl. >> > > > See nginx for example. >> > > > >> > > > .if defined(NGINX_OPENSSL) >> > > > USE_OPENSSL= yes >> > > >> > > USE_OPENSSL is now deprecated and has been replaced by USES=ssl >> > > >> > > > .if ${OSVERSION} < 1100000 >> > > > WITH_OPENSSL_PORT=yes >> > > >> > > WITH_OPENSSL_PORT is now deprecated. Even before that I don't think it >> > > was intended to be used in the port Makefile, only in /etc/make.conf. >> > > The suggested replacement is to put DEFAULT_VERSIONS+=ssl=openssl in >> > > /etc/make.conf. >> > >> > Wouldn't something along the lines of >> > >> > SSL_LIB_DEPENDS= libssl.pc:security/openssl >> > >> libssl.pc? nothing will ever work with this line :) > Right, and I noticed what I had done the moment I hit > the send button. So was forced to send another reply > with the *intended* suggestion. :/ > > SSLLIB_DESC= OpenSSL support > > SSL_LIB_DEPENDS= libssl.so:security/openssl > SSLLIB_CONFIGURE_WITH= ssllib > > or perhaps more simply > > LIB_DEPENDS= libssl.so:security/openssl > > in an appropriate location for an SSL option, > assuming it's even optional. SSL is not optional. The above would work, but I think it would cause problems for anyone who chose libressl as their default because the two versions would conflict. Doing the above only when the default version is set to "base" would be safer, but it turns out that I can make the port work with base OpenSSL (except on FreeBSD 9) by passing the necessary magic environment variables to configure. I think that's good enough and avoids any potential conflicts. From owner-freebsd-ports@freebsd.org Sat Jul 2 10:46:56 2016 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 86798B88CF5 for ; Sat, 2 Jul 2016 10:46:56 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU004-OMC4S17.hotmail.com (blu004-omc4s17.hotmail.com [65.55.111.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4139A245B for ; Sat, 2 Jul 2016 10:46:55 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM03-CO1-obe.outbound.protection.outlook.com ([65.55.111.136]) by BLU004-OMC4S17.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sat, 2 Jul 2016 03:45:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=06nlbHxrjvWOyfuDT954Hzo2VXE97fMlYQZp7L3oDgI=; b=QxYIDVJNyKxwspcTKXd8NnJ/07rzeOUO0iV3FDgf+HxHaafKbXAImDM4/Aode5msse5NWlNGDcB6++lVpP8u6anVRDKsvbXsqgSPeftszr3+FKUmkrUByStNWyoNUhS9nHHO18+PeMeDAwyiDIgbQ2H4fE5CjlPeZJcS09xwfAZnTqvNwRrg78lYYtXId2zcaGYIC1h7FghmOa5hrfzgNchOLiL5rX1cEhuMvrGpXiAtQlATH04sfZqo/pWekb7BG6ROdV936dVHXrdBPo55bPPy4WN3hgOwH+xCMbLrZqlh2mEwV15RE8WhRGAuew8J8vgORrWyRadUdGpD1lnJzw== Received: from BY2NAM03FT064.eop-NAM03.prod.protection.outlook.com (10.152.84.52) by BY2NAM03HT082.eop-NAM03.prod.protection.outlook.com (10.152.85.60) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.534.7; Sat, 2 Jul 2016 10:45:47 +0000 Received: from SN2PR20MB0845.namprd20.prod.outlook.com (10.152.84.56) by BY2NAM03FT064.mail.protection.outlook.com (10.152.85.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.534.7 via Frontend Transport; Sat, 2 Jul 2016 10:45:47 +0000 Received: from SN2PR20MB0845.namprd20.prod.outlook.com ([10.169.198.13]) by SN2PR20MB0845.namprd20.prod.outlook.com ([10.169.198.13]) with mapi id 15.01.0534.015; Sat, 2 Jul 2016 10:45:46 +0000 From: Gerard Seibert To: FreeBSD Ports Subject: Re: what to do when base openssl isn't suitable Thread-Topic: what to do when base openssl isn't suitable Thread-Index: AQHR1E7jNRMJjBhjj066Gy2crCmIZA== Date: Sat, 2 Jul 2016 10:45:46 +0000 Message-ID: References: <201607020225.u622Pfbc094491@gw.catspoiler.org> In-Reply-To: <201607020225.u622Pfbc094491@gw.catspoiler.org> Reply-To: FreeBSD Ports Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=softfail (sender IP is 10.152.84.56) smtp.mailfrom=outlook.com; freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=fail action=none header.from=outlook.com; received-spf: SoftFail (protection.outlook.com: domain of transitioning outlook.com discourages use of 10.152.84.56 as permitted sender) x-ms-exchange-messagesentrepresentingtype: 1 x-eopattributedmessage: 0 x-forefront-antispam-report: CIP:10.152.84.56; IPV:NLI; CTRY:; EFV:NLI; SFV:NSPM; SFS:(10019020)(98900003); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2NAM03HT082; H:SN2PR20MB0845.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: 2fce2195-9c50-4d6a-bb53-08d3a26605ec x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(1601124038)(5061506196)(5061507196)(1603103041)(1601125047); SRVR:BY2NAM03HT082; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015012)(82015046); SRVR:BY2NAM03HT082; BCL:0; PCL:0; RULEID:; SRVR:BY2NAM03HT082; x-forefront-prvs: 0991CAB7B3 Content-Type: text/plain; charset="us-ascii" Content-ID: <370C4BE49278654CBF8946682A0968E3@namprd20.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Jul 2016 10:45:46.6212 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2NAM03HT082 X-OriginalArrivalTime: 02 Jul 2016 10:45:49.0188 (UTC) FILETIME=[E5695C40:01D1D44E] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2016 10:46:56 -0000 I have to admit that this whole discussion has gotten me confused. I use "openssl" from ports, always have and probably always will. I use to use the now apparently depreciate statement in the /etc/make.conf file: WITH_OPENSSL_PORT=3DYES >From what I am reading, I would replace that line with the following statement: DEFAULT_VERSIONS+=3D ssl=3Dopenssl to force the use of the "ports" version of "openssl". Is that correct, or is my interpretation of this incorrect? Thanks --=20 Carmel From owner-freebsd-ports@freebsd.org Sat Jul 2 11:20:28 2016 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 7DF6EB8641F for ; Sat, 2 Jul 2016 11:20:28 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by mx1.freebsd.org (Postfix) with ESMTP id D8ABD2E55; Sat, 2 Jul 2016 11:20:26 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ppp14-2-37-105.lns21.adl2.internode.on.net (HELO leader.local) ([14.2.37.105]) by ipmail06.adl6.internode.on.net with ESMTP; 02 Jul 2016 20:45:15 +0930 Subject: Re: what to do when base openssl isn't suitable To: Don Lewis , freebsd-ports@FreeBSD.org References: <201607011859.u61IxIBt093652@gw.catspoiler.org> From: Shane Ambler Message-ID: <5777A241.4040108@ShaneWare.Biz> Date: Sat, 2 Jul 2016 20:45:13 +0930 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <201607011859.u61IxIBt093652@gw.catspoiler.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2016 11:20:28 -0000 On 02/07/2016 04:29, Don Lewis wrote: > I've got a port that does not work with base openssl because it looks > for libssl.pc. Other than that, I don't think it is picky about what > flavor of ports ssl is installed. If it is looking for libssl.pc then it is using pkg-config to get the CFLAGS/CXXFLAGS/LDFLAGS to use for openssl. Search the Makefiles for pkg-config openssl --cflags --libs or the variable substituted equivalent, then patch it to suit. If you want to use the system openssl then manually adding -lssl -lcrypto where it adds the result from pkg-config should work. -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-ports@freebsd.org Sat Jul 2 14:12:44 2016 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 7EDC3B8F169 for ; Sat, 2 Jul 2016 14:12:44 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0585A2D75 for ; Sat, 2 Jul 2016 14:12:43 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 0C00294CD for ; Sat, 2 Jul 2016 14:12:39 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/0C00294CD; dkim=none; dkim-atps=neutral Subject: Re: what to do when base openssl isn't suitable To: freebsd-ports@freebsd.org References: <201607020225.u622Pfbc094491@gw.catspoiler.org> From: Matthew Seaman Message-ID: <6636d981-cd94-f195-8921-9792f45bef9b@FreeBSD.org> Date: Sat, 2 Jul 2016 15:12:32 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6BJ5OeDkLwdaXBx6vrCI6ooLkukiUGgDP" X-Virus-Scanned: clamav-milter 0.99.2 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2016 14:12:44 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6BJ5OeDkLwdaXBx6vrCI6ooLkukiUGgDP Content-Type: multipart/mixed; boundary="3iGff33dd0OQu2gQRV0x72Gupe5E7iUk3" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: <6636d981-cd94-f195-8921-9792f45bef9b@FreeBSD.org> Subject: Re: what to do when base openssl isn't suitable References: <201607020225.u622Pfbc094491@gw.catspoiler.org> In-Reply-To: --3iGff33dd0OQu2gQRV0x72Gupe5E7iUk3 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 02/07/2016 11:45, Gerard Seibert wrote: > I have to admit that this whole discussion has gotten me confused. I > use "openssl" from ports, always have and probably always will. I use > to use the now apparently depreciate statement in the /etc/make.conf > file: >=20 > WITH_OPENSSL_PORT=3DYES >=20 > From what I am reading, I would replace that line with the following > statement: >=20 > DEFAULT_VERSIONS+=3D ssl=3Dopenssl >=20 > to force the use of the "ports" version of "openssl". Is that correct, > or is my interpretation of this incorrect? These would work for an individual user to customize things via their /etc/make.conf file, and have the effect of causing all OpenSSL using ports to link against the ports version of OpenSSL. Except that neither of these constructs is valid for adding to a port's own Makefile -- and indeed, as you say, WITH_OPENSSL_PORT is no longer useable anywhere. USES=3Dssl unfortunately does not offer any argument to allow the port maintainer to limit what SSL library the user can select. There are two possible answers to this problem 1) Test the value of eg. OPENSSL_PORT after USES=3Dssl has been processed and error out if the user has chosen something incompatible with this port. 2) Make this port, and in fact all ports, compatible with as many as possible of the different variations on SSL libraries that the ports supports[*]. While (1) is superficially attractive, it basically means that your port is going to fragile in the face of changes to whichever SSL library is chosen: something that is likely to happen with different versions of FreeBSD or based on revealed security problems with these libraries. Not recommended. Essentially, you will need to be able to do (2) -- compile successfully against a number of different SSL library implementations. This is clearly much harder to do than (1), given that software consumers of SSL libraries will all have their own ideas about how to configure and link themselves, but on the whole there will be several groups of relatively similar solutions, likely one of which will be relevant and fairly easy to copy and adapt to the needs of a specific port. A lot of this work has already been done, and documented -- largely as a result of the desire to use LibreSSL as a generic replacement for OpenSSL. See Bernard Spil's wiki pages here: https://wiki.freebsd.org/OpenSSL/ There is a plan afoot to make all ported software only use SSL libraries from the ports, and reserve the base OpenSSL library as private to base system software. This will make SSL support in ports substantially easier, but it not here yet. Cheers, Matthew [*] which is currently base-OpenSSL, ports-OpenSSL, LibreSSL and maybe... a bunch of other contenders like GnuTLS, PolarSSL, WolfSSL. You've a reasonable assurance of success with the first three, but the rest are less commonly used, or have significant differences in their APIs, and more importantly, haven't had the work put in to make them generically portable[+]. [+] Also there's a question over whether these SSL libraries will be up to standard with the latest security ideas, such as obsoleting SSLv2, SSLv3 and TLSv1.0 in favour of TLSv1.1 or above. --3iGff33dd0OQu2gQRV0x72Gupe5E7iUk3-- --6BJ5OeDkLwdaXBx6vrCI6ooLkukiUGgDP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXd8vWXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATgQoP/20w8EMPoKZFQCGg0RJ3qkMJ 0WpeXHVdvr0Hv2YrWCpd3vGyd86EKm4e9KkLaH/SLYUGPjCI7koki4enwHZtZVWb dK25N6g/ObsCC6RWAOmN2b32LjWyvzwr5U7aMC3SBpOsyCuApmwpo3Pj1srSblcl BP8dc5Xns99H9wOUQ+X97PJNhxLa0FHpSMX5L1wXDh2n1RizJcHbg7CgyDSijG2v ofTb2I930rreh9NuBxC3edFSprorxsyavBMweqYVy137EulymdA54Wt+EB6zDJ0/ 9ZH4U9T72nVwliz3tkpqoTPwfe+2F9m3i7250bjBAYjVe4f+Ilv4BWOlWbpkeoNz bW0rYw8c8JOqtQX0H0Djfnj7y/m7du+gdLrv6pHvWVC1Po6cCgaCqRFgM7bqLKfm /GFGjaFdrham4smqFoy2QW7WPEvzjnGQZBTkP00TlXl9f5EoY1CtknSknlD2ld6O kJw2gFJzmv+8WR1PJoSmndTdBp+XDj+w+6MxGO8+1IVx5h2Qt/seviaDULDjWoeU ezmYw1Db8jwxTWZJCyHnzqmhguKZObgBnSBYH/QFsCva5lkqMOqneXG2eWbQkMjl fd2/VqFkNFPlgjBB2T9ctBCEjfv51FzIB7hbfs02oxna+ookRK6CnWssaYvw8KtH D9pm5AtaLV1eJeRXOH2n =RXZT -----END PGP SIGNATURE----- --6BJ5OeDkLwdaXBx6vrCI6ooLkukiUGgDP-- From owner-freebsd-ports@freebsd.org Sat Jul 2 16:10:53 2016 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 BDAEBB8FCF0 for ; Sat, 2 Jul 2016 16:10:53 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 86CB62044 for ; Sat, 2 Jul 2016 16:10:53 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id u62GAkUS096413 for ; Sat, 2 Jul 2016 09:10:50 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201607021610.u62GAkUS096413@gw.catspoiler.org> Date: Sat, 2 Jul 2016 09:10:46 -0700 (PDT) From: Don Lewis Subject: Re: what to do when base openssl isn't suitable To: freebsd-ports@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2016 16:10:53 -0000 On 2 Jul, Gerard Seibert wrote: > I have to admit that this whole discussion has gotten me confused. I > use "openssl" from ports, always have and probably always will. I use > to use the now apparently depreciate statement in the /etc/make.conf > file: > > WITH_OPENSSL_PORT=YES That's what I've been doing to build my own package set. > From what I am reading, I would replace that line with the following > statement: > > DEFAULT_VERSIONS+= ssl=openssl I believe that is correct. > to force the use of the "ports" version of "openssl". Is that correct, > or is my interpretation of this incorrect? > > Thanks > From owner-freebsd-ports@freebsd.org Sat Jul 2 17:41:17 2016 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 DD7FDB8FEC9 for ; Sat, 2 Jul 2016 17:41:17 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BEB872E53 for ; Sat, 2 Jul 2016 17:41:17 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id u62Hf9xk096553; Sat, 2 Jul 2016 10:41:14 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201607021741.u62Hf9xk096553@gw.catspoiler.org> Date: Sat, 2 Jul 2016 10:41:09 -0700 (PDT) From: Don Lewis Subject: Re: what to do when base openssl isn't suitable To: FreeBSD@ShaneWare.Biz cc: freebsd-ports@FreeBSD.org In-Reply-To: <5777A241.4040108@ShaneWare.Biz> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2016 17:41:18 -0000 On 2 Jul, Shane Ambler wrote: > On 02/07/2016 04:29, Don Lewis wrote: >> I've got a port that does not work with base openssl because it looks >> for libssl.pc. Other than that, I don't think it is picky about what >> flavor of ports ssl is installed. > > If it is looking for libssl.pc then it is using pkg-config to get the > CFLAGS/CXXFLAGS/LDFLAGS to use for openssl. > > Search the Makefiles for pkg-config openssl --cflags --libs or the > variable substituted equivalent, then patch it to suit. If you want to > use the system openssl then manually adding -lssl -lcrypto where it adds > the result from pkg-config should work. In this case, the configure script skips the call to pkg-config if $libssl_CFLAGS is set. I was able to get a successful build by passing the proper environment variables to configure without the need for patching it. This is what I added to the ports Makefile: .if ${SSL_DEFAULT} == base . if ${OPSYS} == FreeBSD && ${OSVERSION} < 1000000 IGNORE= base OpenSSL in FreeBSD 9 is too old, specify a ports version of SSL by adding DEFAULT_VERSIONS+=ssl=... to /etc/make.conf and rebuild everything that needs SSL . else CONFIGURE_ENV+= libcrypto_CFLAGS="-I${OPENSSLINC}" \ libcrypto_LIBS="-L${OPENSSLLIB} -lcrypto" \ libssl_CFLAGS="-I${OPENSSLINC}" \ libssl_LIBS="-L${OPENSSLLIB} -lssl" . endif .endif From owner-freebsd-ports@freebsd.org Sat Jul 2 18:33:42 2016 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 8FDE3B8FCBC for ; Sat, 2 Jul 2016 18:33:42 +0000 (UTC) (envelope-from korekontakt@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 69DD12283 for ; Sat, 2 Jul 2016 18:33:42 +0000 (UTC) (envelope-from korekontakt@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 69205B8FCBB; Sat, 2 Jul 2016 18:33:42 +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 68C26B8FCBA for ; Sat, 2 Jul 2016 18:33:42 +0000 (UTC) (envelope-from korekontakt@gmail.com) Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E8DA2282; Sat, 2 Jul 2016 18:33:42 +0000 (UTC) (envelope-from korekontakt@gmail.com) Received: by mail-qt0-x22e.google.com with SMTP id m2so72239407qtd.1; Sat, 02 Jul 2016 11:33:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JvJBps+ELPrJIrSofI0dZkXif5d10lE8QXuQeKKlWR4=; b=N6gFkRHPQrFQDQakSLpFYdly/8kPpwbH1qcO0iFtTSNu3h/234at2PwANX+zw71zoZ oiYF/yCf/4WUEXaY7z/AzpM0UCIVUUk6qYO2fwsqMJ676yWpc8VZCE8WtHacNLYuS/QE sPSy4DK+JqSGR88mQde4/VLogAleX4pXRXPdlaCf7tOhaFtZffped76NMpqcuCMDrriO hF23c5Jpzdfbtal65RbG74ZPvZwCBkih+2a7um/SYv5fdDqtJo6nSCJx+2XAG2fC6Jgv 8ny4WoKIGs00uTMVquMwzzjGl++bBGJ+5E7PUjaJGnGsdnFSr+FyJ0z5/JtRL1jQGArZ Y18w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JvJBps+ELPrJIrSofI0dZkXif5d10lE8QXuQeKKlWR4=; b=h0/FBNcNah/1G9NNqlECfyH/HNLPSzSxMY+0Ejzg8dFemTRkkNodsL9fwV89b8uQbE psA8rqBW9j+lJAKNeeaj8DPsK9CWR16acQqSHpfiNWjxBUplcs+syyCXHdY9XRm1QdV7 eTYMdD2dbZSNOWvp31LHhN1s1wb3vBRGvjEoXKIBXU5zmTuqBZl9x3h38YTLGxPhlfND 7Ai8gTv4kZslWE5wij4mTK/OZjnSyXDgkCuEW0OJ1AFnuqa9w8uFWejf6h27JgXtPpaz yDhtJfZVgDBtQwYlJ9vDTVQNVOpN+cQEoigkKv0BJi2gQiKFWGEtdSkcnj+CjqrnnUzi 2W2Q== X-Gm-Message-State: ALyK8tLEQGzY1WWBryY9pQK2qlaRPojdub6MBLvUPYjS+eNpylOrpk9WLR08cq3FJv5aAapEK75xjWyZpCF1hg== X-Received: by 10.237.55.168 with SMTP id j37mr6969514qtb.102.1467484421267; Sat, 02 Jul 2016 11:33:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.52.229 with HTTP; Sat, 2 Jul 2016 11:33:40 -0700 (PDT) In-Reply-To: References: <20160609190710.GT41922@home.opsec.eu> <9f300278-31ab-bc50-1fc7-8e7e6dc44215@toco-domains.de> <8txv-34vw-wny_-_@vfemail.net> From: Raymond Cheung Date: Sun, 3 Jul 2016 02:33:40 +0800 Message-ID: Subject: Re: Torch7 ports (Was: Wxlua / Zbstudio) To: Jan Beich Cc: ports@freebsd.org, Kurt Jaeger , Torsten Zuehlsdorff Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2016 18:33:42 -0000 I'm using FreeBSD 11.0-ALPHA5 to test. If I use clang/clang++ with the official distro, then nn.test() are passed but torch.test() are error/failed. If I use gcc/g++ for pkg/torch and others with clang/clang++ (and run exec '/usr/local/bin/lua51' -e ...), then two tests (max and min) of torch.test() are error/failed: max error in torch.max (value) - NaNs BOOL violation condition=false min error in torch.min - NaNs BOOL violation condition=false But I can't require 'nn': install/lib/lua/5.1/ffi.so: Undefined symbol "cpow" On Thu, Jun 30, 2016 at 9:19 AM, Raymond Cheung wrote: > Hi all, > > I tried the Jan's git ports. However, I got 21 errors out of 127 torch > tests. It said FFI can't point to some structures. Also, I can require nn > even it was installed via luarocks. It said the tester suite is missing. > > Are the blas finding codes located at math/TH? Thanks. > > Raymond > On Jun 24, 2016 17:12, "Raymond Cheung" wrote: > >> Hi Jan and Torsten, >> >> Thanks a lot for your help. >> >> I will try it later after taking a break. As I lack knowledge on C/C++, I >> spent a month to retry many ways on FreeBSD 10/11. I feel tried. >> Fortunately, I got some clues. >> >> During this month, I also learnt a lot on FreeBSD. As least I can build >> and install new world/kernel from GhostBSD 10.3 to 11 Alpha 4. >> >> Thanks again for your help. >> >> Raymond >> On Jun 24, 2016 06:41, "Jan Beich" wrote: >> >>> Torsten Zuehlsdorff writes: >>> >>> > Hello Raymond, >>> > >>> >> OpenBlas (make config; # with OpenMP option), OpenMP, Lapack & ++, >>> GotoBlas >>> >> are installed. Header files of OpenBlas is also included to >>> >> $CMAKE_LIBRARY_PATH. However, I still got the same error message, >>> missing >>> >> lapack. >>> > >>> > There are various variables to set to specify where to look vor the >>> > libs, like lapack. >>> > >>> > Sadly i'm out of time. Tomorrow i'm heading into vacation. When back i >>> > will come back to your request and try to create a port for >>> > this. Maybe we could success together (with more time). >>> >>> I did some work in the past on Torch7 ports before losing interest[1]. >>> Check math/TH if you want to see how it detects OpenBLAS (default). >>> >>> $ git clone https://github.com/jbeich/freebsd-ports torch-ports >>> $ export PORTSDIR=$PWD/torch-ports >>> $ cd $PORTSDIR/devel/lua-trepl >>> $ make install >>> $ th51 >>> >>> -- >>> [1] Many Torch pkgs rely on luarocks to build and resolve dependencies >>> and some have a hard dependency on luajit. My approach didn't scale >>> as writing such ports often required translating *.rockspec files >>> which can quickly grow into maintenance nightmare, so an infra work >>> had to be done beforehand. >>> >> From owner-freebsd-ports@freebsd.org Sat Jul 2 18:49:54 2016 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 588EEB8FF6A for ; Sat, 2 Jul 2016 18:49:54 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from mail.abinet.ru (mail.abinet.ru [136.243.72.227]) by mx1.freebsd.org (Postfix) with ESMTP id 1B19B27A8 for ; Sat, 2 Jul 2016 18:49:53 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from [10.0.0.1] (unknown [10.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.abinet.ru (Postfix) with ESMTPSA id 9F32A1BA00 for ; Sat, 2 Jul 2016 18:41:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=abinet.ru; s=dkim; t=1467484895; bh=NIawcU8NQ/vXP5ykk4dbdOu6DiDO4waWNPTTJm4eIHI=; h=Date:From:To:Subject:References:In-Reply-To; b=aDWEp/sJ4I27kxRNTxWfcsat1EjtPGz6XKcULL9Ctj+tknee4w6x1OP9hPwvnNwOK 6Csn0/rUh80bpbIMW01rZcS5Izxp7Ip8iS5gNtxN9p2lm6qqMDOpLjYDwMCvEOfz0s 4XvABvamR+WD0NG4HOamsXGU2xpPr6NNai1hpPXQ= Message-ID: <57780ADE.6020503@abinet.ru> Date: Sat, 02 Jul 2016 21:41:34 +0300 From: abi User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:) Gecko/20160112 FossaMail/25.2.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: what to do when base openssl isn't suitable References: <201607021610.u62GAkUS096413@gw.catspoiler.org> In-Reply-To: <201607021610.u62GAkUS096413@gw.catspoiler.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2016 18:49:54 -0000 I tried to build www/nginx today, however it seems ignoring DEFAULT_VERSIONS knob. Old style knobs works. On 02.07.2016 19:10, Don Lewis wrote: > On 2 Jul, Gerard Seibert wrote: >> I have to admit that this whole discussion has gotten me confused. I >> use "openssl" from ports, always have and probably always will. I use >> to use the now apparently depreciate statement in the /etc/make.conf >> file: >> >> WITH_OPENSSL_PORT=YES > That's what I've been doing to build my own package set. > >> From what I am reading, I would replace that line with the following >> statement: >> >> DEFAULT_VERSIONS+= ssl=openssl > I believe that is correct. > >> to force the use of the "ports" version of "openssl". Is that correct, >> or is my interpretation of this incorrect? >> >> Thanks >> > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"