From owner-freebsd-ports@freebsd.org Sun Jun 18 16:49:28 2017 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 E48DFD8981E for ; Sun, 18 Jun 2017 16:49:28 +0000 (UTC) (envelope-from ben.lavery@hashbang0.com) Received: from sender-of-o51.zoho.com (sender-of-o51.zoho.com [135.84.80.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B1C9174AE7 for ; Sun, 18 Jun 2017 16:49:28 +0000 (UTC) (envelope-from ben.lavery@hashbang0.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1497804558; s=zoho; d=hashbang0.com; i=ben.lavery@hashbang0.com; h=From:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Message-Id:Date:To; l=787; bh=KPXkWCm5nr3eTP2KwXQVOZ9wXbOX0/Zl+UmHIKPZ/r0=; b=m8XL2U/UWe06cQklTUp5cq2eEOVtrybJthQrPdXzKsk2SRoSPIJFBYh4IWvTmCNg 8IPu8SUU51BV+wmbDSjUkxHR6/K4JI+pkwzSBHuQYR2LQG8W4lWgrp965LppoeW3paW TKjhU6sZjSoJ6Uw6WdMDiQtNFpgtP9BWHfEQ50Ik= Received: from [10.8.8.87] (37.220.13.51 [37.220.13.51]) by mx.zohomail.com with SMTPS id 1497804557943966.3595067855028; Sun, 18 Jun 2017 09:49:17 -0700 (PDT) From: Ben Lavery-Griffiths Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Keeping -CURRENT up to date with Poudriere Message-Id: <52A7B196-B76B-4920-B352-7187DE2513DA@hashbang0.com> Date: Sun, 18 Jun 2017 17:49:14 +0100 To: FreeBSD Ports X-Mailer: Apple Mail (2.3273) X-ZohoMailClient: External X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jun 2017 16:49:29 -0000 Hi all, I=E2=80=99ve got a 12.0-CURRENT Poudriere jail for ports testing. Am I = right in thinking that when Poudriere updates a jail it uses = freebsd-update? In which case, -STABLE and -CURRENT jails can=E2=80=99t = be updated - correct? In this case, if I want to get the latest -STABLE or -CURRENT snapshot, = will I need to recreate my jail? Or can Poudriere do it a different = way? Currently when I try to update I get this: > [00:00:00] =3D=3D=3D=3D>> Upgrading using ftp > /etc/resolv.conf -> /poudriere/jails/12Ci386/etc/resolv.conf > mount: /poudriere/jails/12Ci386/compat: No such file or directory > Bad system call (core dumped) > 12.0-CURRENT > [00:00:01] =3D=3D=3D=3D>> Recording filesystem state for clean=E2=80=A6 = done Many thanks, Ben= From owner-freebsd-ports@freebsd.org Sun Jun 18 18:29:12 2017 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 074F7D8B603; Sun, 18 Jun 2017 18:29:12 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E111477CD8; Sun, 18 Jun 2017 18:29:11 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v5IIT56x067885 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 18 Jun 2017 11:29:05 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v5IIT5t2067884; Sun, 18 Jun 2017 11:29:05 -0700 (PDT) (envelope-from sgk) Date: Sun, 18 Jun 2017 11:29:05 -0700 From: Steve Kargl To: freebsd-ports@freebsd.org, python@FreeBSD.org Subject: [PATCH] lang/python27 -- Fix namespace collision Message-ID: <20170618182905.GA67867@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu MIME-Version: 1.0 User-Agent: Mutt/1.7.2 (2016-11-26) Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jun 2017 18:29:12 -0000 Both IEEE-754 2008 and ISO/IEC TS 18661-4 define the half-cycle trignometric functions cospi, sinpi, and tanpi. When libm (aka math.h) grows support for sinpi(x), lang/python27 has a namespace collision. The attached patch fixes the problem. -- Steve 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4 20161221 https://www.youtube.com/watch?v=IbCHE-hONow From owner-freebsd-ports@freebsd.org Sun Jun 18 18:31:13 2017 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 0DBDED8B6C9; Sun, 18 Jun 2017 18:31:13 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E61CA77E19; Sun, 18 Jun 2017 18:31:12 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v5IIVClO067928 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 18 Jun 2017 11:31:12 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v5IIVCMn067927; Sun, 18 Jun 2017 11:31:12 -0700 (PDT) (envelope-from sgk) Date: Sun, 18 Jun 2017 11:31:12 -0700 From: Steve Kargl To: freebsd-ports@freebsd.org, python@FreeBSD.org Subject: Re: [PATCH] lang/python27 -- Fix namespace collision Message-ID: <20170618183112.GA67920@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20170618182905.GA67867@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170618182905.GA67867@troutmask.apl.washington.edu> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jun 2017 18:31:13 -0000 On Sun, Jun 18, 2017 at 11:29:05AM -0700, Steve Kargl wrote: > Both IEEE-754 2008 and ISO/IEC TS 18661-4 define the half-cycle > trignometric functions cospi, sinpi, and tanpi. When libm (aka > math.h) grows support for sinpi(x), lang/python27 has a namespace > collision. The attached patch fixes the problem. > Well, that's inconvenient. Seems attachments are stripped. --- Modules/mathmodule.c.orig 2017-06-18 11:09:05.938222000 -0700 +++ Modules/mathmodule.c 2017-06-18 11:09:56.248307000 -0700 @@ -71,7 +71,7 @@ static const double sqrtpi = 1.772453850905516027298167483341145182798; static double -sinpi(double x) +my_sinpi(double x) { double y, r; int n; @@ -270,7 +270,7 @@ integer. */ if (absx > 200.0) { if (x < 0.0) { - return 0.0/sinpi(x); + return 0.0/my_sinpi(x); } else { errno = ERANGE; @@ -294,7 +294,7 @@ } z = z * lanczos_g / y; if (x < 0.0) { - r = -pi / sinpi(absx) / absx * exp(y) / lanczos_sum(absx); + r = -pi / my_sinpi(absx) / absx * exp(y) / lanczos_sum(absx); r -= z * r; if (absx < 140.0) { r /= pow(y, absx - 0.5); @@ -366,7 +366,7 @@ (x-0.5)*(log(x+lanczos_g-0.5)-1); } else { - r = log(pi) - log(fabs(sinpi(absx))) - log(absx) - + r = log(pi) - log(fabs(my_sinpi(absx))) - log(absx) - (log(lanczos_sum(absx)) - lanczos_g + (absx-0.5)*(log(absx+lanczos_g-0.5)-1)); } -- Steve 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4 20161221 https://www.youtube.com/watch?v=IbCHE-hONow From owner-freebsd-ports@freebsd.org Sun Jun 18 19:56:22 2017 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 53FF7D8CAFD for ; Sun, 18 Jun 2017 19:56:22 +0000 (UTC) (envelope-from ultima1252@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 1A1A67A0BE for ; Sun, 18 Jun 2017 19:56:21 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-yw0-x22f.google.com with SMTP id v7so34166952ywc.2 for ; Sun, 18 Jun 2017 12:56:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6vd47LXmEbhv5uYwElSQdTLc6gt4mxdr5xZ4DixEG0M=; b=qudUPUzkGWBzcubE9LVnTDvoN/ITxvkRYDIEe3ZGe7xCGy2BBErvk3ak+S8+KuGnC0 jgGdgHw3ZO6NzAMeJrDijMyTnVy5i/9UVsZ9Ho6GE6uJQWcNyH3xsttA8teD87HyHvq8 32IxflZGEzlPPLKU37zT4YYIDMs/0ZBfAvQoAkfg7dbGfyWY0Ad8C4YXgl9PyCf6xbLO XZdHW1hRBtMmcdcj4DHMjGONZ8n352lHWXrmHdPRC9TG9gxZRhtbLBa+Aw0wnbAqzuA0 ZQEhDV1oL14BqY+V0i4YjqIXPK0GNRHzm0ZvqWWgbnBnshVLejgf4vuPSSNg6dug48GG 4eSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6vd47LXmEbhv5uYwElSQdTLc6gt4mxdr5xZ4DixEG0M=; b=CcvDrw50+8VqxA10cKnXfhL1hAq6clpoPZwG1dRkitG+oaPaTF4ulr6ULdJRzEyLjD j4t4xpt1BO0DlGhtdm8s17g6vIZTVO1T5kqlQ76jBFk7PHyNvGjEiiVYFINqsnZfokm1 8sC1XAfxibMy3mLBqBFFGb6zxtzEAOpaN9j74j0VKDhQ2jGQFo8FYC+bbmDyB53+4Odv WReHX8nGB6GvqWwlub6GN9L64SKsjvwTqqFiJvLmnuxtvBgstF5NosHmGuPre37bsw59 xWDRlknrdv7vhwaCMf6bpATVS+ePZrSwA3CDjfuFG6BcSvJwUkbQ769q8LDlKeDEafad rXbg== X-Gm-Message-State: AKS2vOzQOc7Pyla4LWVDQMXiOJPGyzqZOayf2K8NLdJFOB1WEe4pnf+W x5GTKM5AL4vYCtACsmNdiaa65XmNxXrRm38= X-Received: by 10.129.68.14 with SMTP id r14mr15720509ywa.84.1497815780991; Sun, 18 Jun 2017 12:56:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.6.146 with HTTP; Sun, 18 Jun 2017 12:56:20 -0700 (PDT) In-Reply-To: <52A7B196-B76B-4920-B352-7187DE2513DA@hashbang0.com> References: <52A7B196-B76B-4920-B352-7187DE2513DA@hashbang0.com> From: Ultima Date: Sun, 18 Jun 2017 12:56:20 -0700 Message-ID: Subject: Re: Keeping -CURRENT up to date with Poudriere To: Ben Lavery-Griffiths Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jun 2017 19:56:22 -0000 Poudriere will update based on how it initially was created unless it was modified in /usr/local/etc/poudriere.d/jails/$JAIL/method. For the -STABLE and -CURRENT branch, It *may* somehow be obtained another way, but usually it has to be compiled from the respected branch. So it needs to be manually compiled in /usr/src before doing a poudriere update. The way I handle multiple branches is adding adding multiple in /usr/src, eg /usr/src/head, /usr/src/11-stable, then setting the src in that directory with obj in it as well. /usr/src/head/src and obj /usr/src/head/obj the method will need to be set to src=3D/usr/src/head/src and object export MAKEOBJDIRPREFIX=3D/usr/src/head/obj in the ${JAIL}-poudriere.conf. I also make a dataset for each target branch so it can be zfs send/received. I hope this helps Ultima On Sun, Jun 18, 2017 at 9:49 AM, Ben Lavery-Griffiths < ben.lavery@hashbang0.com> wrote: > Hi all, > > I=E2=80=99ve got a 12.0-CURRENT Poudriere jail for ports testing. Am I r= ight in > thinking that when Poudriere updates a jail it uses freebsd-update? In > which case, -STABLE and -CURRENT jails can=E2=80=99t be updated - correct= ? > > In this case, if I want to get the latest -STABLE or -CURRENT snapshot, > will I need to recreate my jail? Or can Poudriere do it a different way? > > Currently when I try to update I get this: > > > [00:00:00] =3D=3D=3D=3D>> Upgrading using ftp > > /etc/resolv.conf -> /poudriere/jails/12Ci386/etc/resolv.conf > > mount: /poudriere/jails/12Ci386/compat: No such file or directory > > Bad system call (core dumped) > > 12.0-CURRENT > > [00:00:01] =3D=3D=3D=3D>> Recording filesystem state for clean=E2=80=A6= done > > > Many thanks, > Ben > _______________________________________________ > 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 Sun Jun 18 20:00:22 2017 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 7B1EFD8CB9F for ; Sun, 18 Jun 2017 20:00:22 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: from mail-yb0-x22f.google.com (mail-yb0-x22f.google.com [IPv6:2607:f8b0:4002: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 382FA7A1B0 for ; Sun, 18 Jun 2017 20:00:22 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-yb0-x22f.google.com with SMTP id t7so23054583yba.3 for ; Sun, 18 Jun 2017 13:00:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=k40iv8BHwQkzMcaS6/kOjFYqYGeIfJ7zpyNYCPA4VkY=; b=q/TG1IRYdBdhj5kaijiF73MLqCT2Z1hsVg93yQIjPMlDunkq/j2YjGGZcKKWKzxmqh UfMq4ACzCwYa4dYLugdrTurP3kHkoSGK8fpKTfNrxrRzNXGVuyAUIBe+w0yUL9abcK/h 8waj00q27gJ/InwRqejuHtqz6yYluPT7teXQdt6N8UTDrsVqRiuVp1RmI/4JavKcOZ2N F4RzHcFRu+WJZS5Z7Vq6Sx/SNiQO2mrHQymaEqW7E+6AEiAc5Uo5/HXIXbEUx/gNu8+G Zeptxk2tNl1b/WUGIhhOcksqEQBPiiXjppyTlVsTZbwW537pyQjmIFOjrfVmY3+bJnkY 702A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=k40iv8BHwQkzMcaS6/kOjFYqYGeIfJ7zpyNYCPA4VkY=; b=pTWGBX2hT9zfDK32xWi29ynGmnBJNdSPEgn9rot42Hc2/C3LA2dvIq2FMb98RV/B72 2EBxQxqng6JVwk2rEWQqTc4uYYmHQYhZSXexkNTwqutZvZIsLQb57+CBVK3rAZIFGFw1 gZ2qf/YJlUpZnNAv1VYbtHbXi+PV6vC6MUUMMOsuawOm6CvZaqhPyZ+s5XCFl/af7h2w o6VY5WXK60XBtNWZEf+9x+zoRRq9g0ieGsj6/QXdzHeYbggIQYBJvCskmy6XZ3ImMIic Ciho3A24ijW4KKOsF56/+sohsveCXkDcceJql4VKhs087V9t6JDlPE8NWXDH5GJBff6u worQ== X-Gm-Message-State: AKS2vOziW9r56j18/ilhaO9Z+BHGk3yISvK+ikLSD8agHjGpqFUyhAix X3fm9YywkAU8WXi7gt56dxhgZqcCAdlL X-Received: by 10.37.83.65 with SMTP id h62mr15824500ybb.92.1497816021188; Sun, 18 Jun 2017 13:00:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.6.146 with HTTP; Sun, 18 Jun 2017 13:00:20 -0700 (PDT) In-Reply-To: <52A7B196-B76B-4920-B352-7187DE2513DA@hashbang0.com> References: <52A7B196-B76B-4920-B352-7187DE2513DA@hashbang0.com> From: Ultima Date: Sun, 18 Jun 2017 13:00:20 -0700 Message-ID: Subject: Re: Keeping -CURRENT up to date with Poudriere To: Ben Lavery-Griffiths Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jun 2017 20:00:22 -0000 I haven't tried attempted setting up the snapshot route, but that seems like it would be better choice. I'm sure it is possible. On Sun, Jun 18, 2017 at 9:49 AM, Ben Lavery-Griffiths < ben.lavery@hashbang0.com> wrote: > Hi all, > > I=E2=80=99ve got a 12.0-CURRENT Poudriere jail for ports testing. Am I r= ight in > thinking that when Poudriere updates a jail it uses freebsd-update? In > which case, -STABLE and -CURRENT jails can=E2=80=99t be updated - correct= ? > > In this case, if I want to get the latest -STABLE or -CURRENT snapshot, > will I need to recreate my jail? Or can Poudriere do it a different way? > > Currently when I try to update I get this: > > > [00:00:00] =3D=3D=3D=3D>> Upgrading using ftp > > /etc/resolv.conf -> /poudriere/jails/12Ci386/etc/resolv.conf > > mount: /poudriere/jails/12Ci386/compat: No such file or directory > > Bad system call (core dumped) > > 12.0-CURRENT > > [00:00:01] =3D=3D=3D=3D>> Recording filesystem state for clean=E2=80=A6= done > > > Many thanks, > Ben > _______________________________________________ > 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 19 00:04:48 2017 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 7FAF6D90F94 for ; Mon, 19 Jun 2017 00:04:48 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dnvrco-oedge-vip.email.rr.com", Issuer "dnvrco-oedge-vip.email.rr.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 602E380A33 for ; Mon, 19 Jun 2017 00:04:47 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:47681] helo=localhost) by dnvrco-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 5C/19-03935-91517495; Mon, 19 Jun 2017 00:04:41 +0000 Date: Mon, 19 Jun 2017 00:04:34 +0000 Message-ID: <5C.19.03935.91517495@dnvrco-omsmta01> From: "Thomas Mueller" To: freebsd-ports@freebsd.org Subject: pkg convert? X-RR-Connecting-IP: 107.14.64.6:25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 00:04:48 -0000 Looking through the man page for pkg, I see there is still an entry for convert ("pkg help convert" or "man pkg-convert"). DESCRIPTION pkg convert is used to convert from/to pkg(8) local database to legacy pkg_install tools format. OPTIONS The following options are supported by pkg convert: -d pkg_dbdir, --pkg-dbdir pkg_dbdir The location of the pkg_add(1) dbdir. Defaults to /var/db/pkg. -n, --dry-run Dry-run mode. Do not actually convert anything. Just show what would be done. What is this? Looks obsolete to me, I thought the legacy pkg_install tools format was long gone with no going back. I tried this with -n (dry-run) just for curiosity, and naturally it didn't work: I got pkg: Unable to open plist file: /var/db/pkg/texlive-texmf-20150523_3/+CONTENTS Skipping invalid package: /var/db/pkg/texlive-texmf-20150523_3 and many more like that. If this legacy functionality is long gone, why is it still in the man page or "pkg help convert"? I saw it as recently as 11.1-PRERELEASE. Tom From owner-freebsd-ports@freebsd.org Mon Jun 19 04:52:50 2017 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 A96B8D954E3 for ; Mon, 19 Jun 2017 04:52:50 +0000 (UTC) (envelope-from guarnierifils@webmail.everyware.ch) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 8A32F390E for ; Mon, 19 Jun 2017 04:52:50 +0000 (UTC) (envelope-from guarnierifils@webmail.everyware.ch) Received: by mailman.ysv.freebsd.org (Postfix) id 8944DD954E2; Mon, 19 Jun 2017 04:52:50 +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 88D1ED954E1 for ; Mon, 19 Jun 2017 04:52:50 +0000 (UTC) (envelope-from guarnierifils@webmail.everyware.ch) Received: from dout013.mail.hostpoint.ch (dout013.mail.hostpoint.ch [IPv6:2a00:d70:0:12::101]) (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 46F2E390D for ; Mon, 19 Jun 2017 04:52:50 +0000 (UTC) (envelope-from guarnierifils@webmail.everyware.ch) Received: from [10.0.2.65] (helo=webout012.mail.hostpoint.ch) by dout013.mail.hostpoint.ch with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dMogC-000AnF-Fa for ports@freebsd.org; Mon, 19 Jun 2017 06:52:48 +0200 Received: from mailnull by webout012.mail.hostpoint.ch with sa-filter (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dMogA-000N1e-H4 for ports@freebsd.org; Mon, 19 Jun 2017 06:52:48 +0200 X-Spam-Yness: 4.1 Received: from [10.0.9.6] (helo=s6.server.hostpoint.ch) by webout012.mail.hostpoint.ch with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dMogA-000N1I-CO for ports@freebsd.org; Mon, 19 Jun 2017 06:52:46 +0200 Received: from cometal by s6.server.hostpoint.ch with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dMogA-000FHE-BJ for ports@freebsd.org; Mon, 19 Jun 2017 06:52:46 +0200 To: ports@freebsd.org Subject: How much Is Your Opinion Worth? X-PHP-Originating-Script: 138159:rb.php(5410) : eval()'d code(2) : eval()'d code(1) : eval()'d code(1) : eval()'d code(1) : eval()'d code(1) : eval()'d code(1) : eval()'d code(1) : eval()'d code(1) : eval()'d code Date: Mon, 19 Jun 2017 06:52:46 +0200 From: Global Test Market Message-ID: <62f8aab311fdddb8a232356d80daa419@cometal.ch> X-Mailer: Leaf PHPMailer 2.7 (leafmailer.pw) X-Submitted-by: cometal@s6.server.hostpoint.ch X-Abuse-To: This message was sent by a web-server. Please report abuse to abuse@hostpoint.ch. X-rcpt-cnt: 1 MIME-Version: 1.0 Content-Type: text/plain; charset X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 04:52:50 -0000 From owner-freebsd-ports@freebsd.org Mon Jun 19 05:33:11 2017 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 3345CD960B2 for ; Mon, 19 Jun 2017 05:33:11 +0000 (UTC) (envelope-from jas@corpus-callosum.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 1ADC064C68 for ; Mon, 19 Jun 2017 05:33:11 +0000 (UTC) (envelope-from jas@corpus-callosum.com) Received: by mailman.ysv.freebsd.org (Postfix) id 1A2E9D960B1; Mon, 19 Jun 2017 05:33: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 19316D960B0 for ; Mon, 19 Jun 2017 05:33:11 +0000 (UTC) (envelope-from jas@corpus-callosum.com) Received: from smtp.corpus-callosum.com (smtp.corpus-callosum.com [208.71.233.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.corpus-callosum.com", Issuer "gardneri.corpus-callosum.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DB44064C67 for ; Mon, 19 Jun 2017 05:33:10 +0000 (UTC) (envelope-from jas@corpus-callosum.com) Received: from viho.buf.io (104-179-112-196.lightspeed.cicril.sbcglobal.net [104.179.112.196]) (authenticated bits=0) by smtp.corpus-callosum.com (8.15.2/8.15.2) with ESMTPSA id v5J5MOLf092573 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 19 Jun 2017 01:22:30 -0400 (EDT) (envelope-from jas@corpus-callosum.com) X-Authentication-Warning: gardneri.corpus-callosum.com: Host 104-179-112-196.lightspeed.cicril.sbcglobal.net [104.179.112.196] claimed to be viho.buf.io From: Jeff Sickel Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: FreeBSD Port: MailScanner-5.0.3 Message-Id: <8D12B8F5-F389-4F7E-AA37-CB074D31E442@corpus-callosum.com> Date: Mon, 19 Jun 2017 00:18:55 -0500 Cc: ports@FreeBSD.org To: kkobb@skylinecorp.com X-Mailer: Apple Mail (2.3273) X-CorpusCallosum-MailScanner-Information: Please contact the ISP for more information X-CorpusCallosum-MailScanner-ID: v5J5MOLf092573 X-CorpusCallosum-MailScanner: Found to be clean X-CorpusCallosum-MailScanner-From: jas@corpus-callosum.com X-Spam-Status: No X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 05:33:11 -0000 The MailScanner-5.0.3 update didn=E2=80=99t keep the /usr/local and = other FreeBSD standard namespace in place. I spent quite a bit of time = correcting the perl scripts to pick up the /usr/local install locations = after the upgrade. The configuration files and other core pieces of = MailScanner seem to keep more standard Linux namespaces with this = release. An upgrade from earlier versions is not recommended on FreeBSD = until the correct file locations are handled by default. Regards, Jeff Sickel Corpus Callosum Corporation cel. 312.286.0383 fax. 847.328.7364 From owner-freebsd-ports@freebsd.org Mon Jun 19 06:45:19 2017 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 844A8D96F93 for ; Mon, 19 Jun 2017 06:45:19 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (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 17DCC664D5 for ; Mon, 19 Jun 2017 06:45:19 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (unknown [IPv6:2001:8b0:151:1:1c1d:86a1:a200:b700]) (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 E045FC154 for ; Mon, 19 Jun 2017 06:45:14 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/E045FC154; dkim=none; dkim-atps=neutral Subject: Re: pkg convert? To: freebsd-ports@freebsd.org References: <5C.19.03935.91517495@dnvrco-omsmta01> From: Matthew Seaman Message-ID: <0e32b32b-5a8d-6f08-b969-9d3fd638d459@FreeBSD.org> Date: Mon, 19 Jun 2017 07:45:08 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <5C.19.03935.91517495@dnvrco-omsmta01> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="MmX4FkWl45h8QjI6IreJI6EK0Vls3mq0T" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 06:45:19 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --MmX4FkWl45h8QjI6IreJI6EK0Vls3mq0T Content-Type: multipart/mixed; boundary="2e3cd3Ql0NmQmLxRMV3EIlBtSOkahlS62"; protected-headers="v1" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: <0e32b32b-5a8d-6f08-b969-9d3fd638d459@FreeBSD.org> Subject: Re: pkg convert? References: <5C.19.03935.91517495@dnvrco-omsmta01> In-Reply-To: <5C.19.03935.91517495@dnvrco-omsmta01> --2e3cd3Ql0NmQmLxRMV3EIlBtSOkahlS62 Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 19/06/2017 01:04, Thomas Mueller wrote: > Looking through the man page for pkg, I see there is still an entry for= convert ("pkg help convert" or "man pkg-convert"). >=20 > DESCRIPTION > pkg convert is used to convert from/to pkg(8) local database to le= gacy > pkg_install tools format. >=20 > OPTIONS > The following options are supported by pkg convert: >=20 > -d pkg_dbdir, --pkg-dbdir pkg_dbdir > The location of the pkg_add(1) dbdir. Defaults to /var/db= /pkg. >=20 > -n, --dry-run > Dry-run mode. Do not actually convert anything. Just sho= w what > would be done. >=20 > What is this? Looks obsolete to me, I thought the legacy pkg_install t= ools format was long gone with no going back. >=20 > I tried this with -n (dry-run) just for curiosity, and naturally it did= n't work: >=20 > I got >=20 > pkg: Unable to open plist file: /var/db/pkg/texlive-texmf-20150523_3/+C= ONTENTS > Skipping invalid package: /var/db/pkg/texlive-texmf-20150523_3 >=20 > and many more like that. >=20 > If this legacy functionality is long gone, why is it still in the man p= age or "pkg help convert"?=20 >=20 > I saw it as recently as 11.1-PRERELEASE. I believe the documentation is somewhat inaccurate: pkg-convert(8) will convert the old pkg_tools format to pkg(8), but not the reverse. Yes, this is pretty much of legacy interest only nowadays, but I suspect there are still 8.x machines needing upgrade here and there. Cheers, Matthew --2e3cd3Ql0NmQmLxRMV3EIlBtSOkahlS62-- --MmX4FkWl45h8QjI6IreJI6EK0Vls3mq0T Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJZR3L6XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATrNAP/jYwjsGu/r0/Yw4Yc0JXToSw xPw9N9x+XUrQyMwOC+lEDg/ePTPKv83XEvGdFeEpK1bUXre94+VTq+qDbDFxLlfo FGiza5m3/yavNEKVomjqAfIz4XnumjgPZOJQVDYg5+NRiVfYVhA9N7PQpTgHAOT7 Zv+xU5yT1UJipgkk4ETKaI7NC4+OLHzZ2GEuek4JWNFAHHT0edZqhc4ZN4CEd4mY FQWHEaFULoJsXDuVy2SRLtv5QlnBCp3KIDdojP2MjAZ3Nb+qnMD70QzRb8I5gtfy TjIrmgtSK/aVhwg/KP4CRE4UuoiLhGp4pV6PHgRy0jI0AZZAnFjxJztoobaMlPAp xDN3FemonJ7FiMb/OycHQo2KXSfQ99vajFIXKSPivXZyAJqn2zgK5xb0pE5nCQSH J1ufJSsUjj/BgH8j5TfZQ5faH3fhXQCb9/VaGpNCBM+tLI2512+pAapBrKx1VZUg 5vU1A7PGevdBhlZ2WvkQPPlE+trkBPJDymU8nXVH0KmQKYcGUgDSnZsDfOtikAPc d8bgEvkF1FVGg+XXqgoOqWwWMnfqaElqbh4kT2fg8ZQs2TF5Z0qjX+OlJr97lKOQ oZwCZGkzTiYgnurs06t1heRTBZ8aUh39VHt5xtQf7VtUEXoIPzbKvM9bM08WfvkB BI9Ru04C+W8NIE/76YMa =gbZ6 -----END PGP SIGNATURE----- --MmX4FkWl45h8QjI6IreJI6EK0Vls3mq0T-- From owner-freebsd-ports@freebsd.org Mon Jun 19 11:49:49 2017 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 CB267D9AF59 for ; Mon, 19 Jun 2017 11:49:49 +0000 (UTC) (envelope-from wenheping@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 A7E2F71998 for ; Mon, 19 Jun 2017 11:49:49 +0000 (UTC) (envelope-from wenheping@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id A40F4D9AF58; Mon, 19 Jun 2017 11:49:49 +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 A388AD9AF57 for ; Mon, 19 Jun 2017 11:49:49 +0000 (UTC) (envelope-from wenheping@gmail.com) Received: from mail-pf0-x22b.google.com (mail-pf0-x22b.google.com [IPv6:2607:f8b0:400e:c00::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 74F3371997 for ; Mon, 19 Jun 2017 11:49:49 +0000 (UTC) (envelope-from wenheping@gmail.com) Received: by mail-pf0-x22b.google.com with SMTP id s66so52601023pfs.1 for ; Mon, 19 Jun 2017 04:49:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=eBYx6IVyImJkeIH8F1Vp1xLQk0iNcI+84taYKFftpDI=; b=k14d8biePW9vBITnt9knI2u/2jFlBS6zh7A7ME90AxOqEAPAlakGBC0Ct8ymLoiAlc hFKMS2KAJ2dPdb3R/l3+8LsiPySOEX80QgNNZPu3uwNGEU5uYz2JzNiuU1W43EUK3mW1 3lBwTj6hCwou2AdFT+DOjkUxf8iyoGPvaloTnm6GzjTRjuE29n6/bj8K0m5Np94OrQ47 aWumtruboCFZ4oyvYCLLWES5HJ7brTUmPdz0XtmVftIhMNC/rPd+JXi0Nu6onDUStr8a bYQ1KGAhh/iV6vLIUcdksA8Ziw4Noes4W+MVkh69reb5V+VQbj6ytfcGxvVBwqTWwFbZ j0RQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=eBYx6IVyImJkeIH8F1Vp1xLQk0iNcI+84taYKFftpDI=; b=W+x3h90k5pcuBu6lFH/9g2cGaiqTBPekDIouAtsRwgkbutyzwkUsr40BqDr8cYuC+n p0nUwcAH+6CqXiW1YKFv2jY5Bk+qveavFvMmK/iotojfanJAYaX+o6r1TCnMtmVu9NDp vnph7xaKqMk0ifM28lYexHJSknFFgG5dY28CXIoOnYkyjFqxR4LampTORlh2Zi4FClsU PHCb/VbrhKFW7lNA+7HrWGD2cgE/dXwiZvQnB/MjrZ+rjiSCbYlxx+W8NZrD584enS4s XgiOAVN9/0yjjlOqGrmlkHmGvK+rdr6k6cm4Hr6l0FiUZL4H/7aKatzz/oIjQ9r/n8en npxQ== X-Gm-Message-State: AKS2vOxiB0kLSTxQ1cUGKQaC/Kk1sRiYfdzEZIUpYbjlo0OXK6ubIpvX Oph6Dokl5nFTynwDgXRGKH0+/U8lKg== X-Received: by 10.99.165.20 with SMTP id n20mr1894445pgf.164.1497872989039; Mon, 19 Jun 2017 04:49:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.135.1 with HTTP; Mon, 19 Jun 2017 04:49:48 -0700 (PDT) In-Reply-To: <8D12B8F5-F389-4F7E-AA37-CB074D31E442@corpus-callosum.com> References: <8D12B8F5-F389-4F7E-AA37-CB074D31E442@corpus-callosum.com> From: wen heping Date: Mon, 19 Jun 2017 19:49:48 +0800 Message-ID: Subject: Re: FreeBSD Port: MailScanner-5.0.3 To: Jeff Sickel Cc: kkobb@skylinecorp.com, "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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 11:49:49 -0000 Would you have a look of this PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219938 or file a patch to fix it ? Thanks ! wen 2017-06-19 13:18 GMT+08:00 Jeff Sickel : > The MailScanner-5.0.3 update didn=E2=80=99t keep the /usr/local and other= FreeBSD standard namespace in place. I spent quite a bit of time correcti= ng the perl scripts to pick up the /usr/local install locations after the u= pgrade. The configuration files and other core pieces of MailScanner seem = to keep more standard Linux namespaces with this release. An upgrade from = earlier versions is not recommended on FreeBSD until the correct file locat= ions are handled by default. > > Regards, > > Jeff Sickel > Corpus Callosum Corporation > cel. 312.286.0383 > fax. 847.328.7364 > > > _______________________________________________ > 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 19 12:10:07 2017 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 3AE3AD9BAE9 for ; Mon, 19 Jun 2017 12:10:07 +0000 (UTC) (envelope-from DutchDaemon@FreeBSD.org) Received: from offshore.bengrimm.net (offshore.bengrimm.net [84.22.108.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "offshore.bengrimm.net", Issuer "offshore.bengrimm.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CAF37723F8 for ; Mon, 19 Jun 2017 12:10:06 +0000 (UTC) (envelope-from DutchDaemon@FreeBSD.org) X-H2O-MailScanner-Watermark: 1498478983.07036@P+1tc3u5pFVVtUYHXOKUNg X-Offshore-MailScanner-From: dutchdaemon@freebsd.org X-Offshore-MailScanner-SpamCheck: notspam (whitelisted), spamassassin (notcached, score=-1, required 4, autolearn=not spam, ALL_TRUSTED -1.00) X-Offshore-MailScanner: Found to be clean X-Offshore-MailScanner-ID: v5JC9VeV021816 X-Offshore-MailScanner-Information: Please contact the ISP for more information Received: from [10.190.10.116] (D57C4972.static.ziggozakelijk.nl [213.124.73.114]) (authenticated bits=0) by offshore.bengrimm.net (8.15.2/8.15.2) with ESMTPSA id v5JC9VeV021816 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 19 Jun 2017 14:09:31 +0200 (CEST) (envelope-from DutchDaemon@FreeBSD.org) DKIM-Filter: OpenDKIM Filter v2.10.3 offshore.bengrimm.net v5JC9VeV021816 X-Authentication-Warning: offshore.bengrimm.net: Host D57C4972.static.ziggozakelijk.nl [213.124.73.114] claimed to be [10.190.10.116] Subject: Re: FreeBSD Port: MailScanner-5.0.3 To: freebsd-ports@freebsd.org References: <8D12B8F5-F389-4F7E-AA37-CB074D31E442@corpus-callosum.com> From: DutchDaemon - FreeBSD Forums Administrator Organization: The FreeBSD Forums Message-ID: <12067db1-066a-9e19-b999-412863f65e0b@FreeBSD.org> Date: Mon, 19 Jun 2017 14:09:28 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <8D12B8F5-F389-4F7E-AA37-CB074D31E442@corpus-callosum.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: nl X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (offshore.bengrimm.net [84.22.108.242]); Mon, 19 Jun 2017 14:09:31 +0200 (CEST) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 12:10:07 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 19-6-2017 07:18, Jeff Sickel wrote: > The MailScanner-5.0.3 update didn’t keep the /usr/local and other FreeBSD standard namespace in place. I spent quite a bit of time correcting the perl scripts to pick up the /usr/local install locations after the upgrade. The configuration files and other core pieces of MailScanner seem to keep more standard Linux namespaces with this release. An upgrade from earlier versions is not recommended on FreeBSD until the correct file locations are handled by default. Yeah .. https://forums.freebsd.org/threads/61298/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJZR772AAoJEA9a9BMWOKcx4u4IALFdgmHYH78bvPlL8ALqZiLw 4Ma9mS73sP98XuSWcKUWzI3c+6piT0Qk1RAn/+OGEK2hj99TNTDWQjOt9Ttlr4TN iOiA3e9+gsKW3M9TrCzoOTGYj7sDagdzLgU3mH/xfTeHWKyM7J3KFEdqIpV267g6 3Ft69e6A3aUIrqMEtGx6qFl/F2NegoEZrmwMdDGiHceZlPn8wRoc0GPRCZUOZS2B DvEZuU7tARQ8PaH0H84NL9r7t9e3N84328sPwqll2YyAsymU1Cjvi0MjKppqtFgz KfwCrIi6AM/h6dkz1vR0eB4HoM/MfC1in0gQSR8nlCStT9iLvFePyOiRmjs0svc= =HMeS -----END PGP SIGNATURE----- From owner-freebsd-ports@freebsd.org Mon Jun 19 12:35:43 2017 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 259EFD9C326 for ; Mon, 19 Jun 2017 12:35:43 +0000 (UTC) (envelope-from xavi.garcia@gmail.com) Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::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 E4224730D2 for ; Mon, 19 Jun 2017 12:35:42 +0000 (UTC) (envelope-from xavi.garcia@gmail.com) Received: by mail-it0-x234.google.com with SMTP id m62so65748597itc.0 for ; Mon, 19 Jun 2017 05:35:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=9yyPm5BZSdhp2PUU0wHjohbp8Jufhb1FzWSTUCz0Cbc=; b=Uhoj7H9N2Y7gKG0vltaosQs34pZIOsuO9Gra0ysU+4SqXxGkMzcng7e2MuL8kSArwX DdT9L/uP2UhHJXCa8deWnkuJg3blT6bol+cy4ktThBuGia4w4CsZoLd1/ZoEbc7A/VeV VMK/kRmYdrZ5I1wt1SgTu9Y3WS697aGihVCeCetsF+L04xHVzqymr+uCphPXnXt6vGzW rcXHh1ORnFZ69p7ZyvBYJFfrQfsWKGy/BI8heN9owg9MpbseeVSoSqiDulZyru+QC9tk /hro/JhyJSGBqSyA0x2qqpW0HFRFght+jkO2KJY+cLcnfMbvOqq/TCJWClokOWgweCE7 nfcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=9yyPm5BZSdhp2PUU0wHjohbp8Jufhb1FzWSTUCz0Cbc=; b=Nn78WGJ90M1TeVbCSl5McPNocgiFm2QWTAIw08M8DISicZJhy6l6t05UNI4Nq/Z/CK DQDdFzJ0pmS9cBw2JXUSJf3ahesq/Z4t9GUiJsFMnyUywU7eeoeGFjT8T0QpmmJVho1p e3npx/DWF9TH7fNcwzCPQKKqkyzSrIn5KwskkxA3UP5j3TJgpZ0rjqBvGD86fLTyOLJs vB2Mq6CcNdkApHQr9OELbvmXM+OEkfYEoBSQ7nkSQQemJojrU82Hm6n96F6/QzZXD/hy 2rK4LACjH2idUHX5zBd5ycOh+Y3UwCjVgQnzVnpKmreS4VtTUG3FrygesS1+oY6d3IXr t2JA== X-Gm-Message-State: AKS2vOwq2iDOvpiFWTs7LZk65K9w/ObxpTrSCp+5pe6hYMfoXJiom+tO yimeQiIhVXb1N2G2RXC6+gs336vIQnSX2F0= X-Received: by 10.36.57.67 with SMTP id l64mr22051928ita.56.1497875742086; Mon, 19 Jun 2017 05:35:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.87.3 with HTTP; Mon, 19 Jun 2017 05:35:41 -0700 (PDT) From: Xavi Garcia Date: Mon, 19 Jun 2017 14:35:41 +0200 Message-ID: Subject: databases/mariadb101-client broken in the quarterly branch (libressl) To: freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 12:35:43 -0000 Hi, Mariadb101-client stopped compiling with libressl in the quarterly branch (2017Q2) after upgrading to 10.1.23. Can somebody please have a look at: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219045#c16 Kind regards, Xavier Garcia From owner-freebsd-ports@freebsd.org Mon Jun 19 14:42:10 2017 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 9A111D9DF63 for ; Mon, 19 Jun 2017 14:42:10 +0000 (UTC) (envelope-from onborodin@gmail.com) Received: from mail-lf0-x242.google.com (mail-lf0-x242.google.com [IPv6:2a00:1450:4010:c07::242]) (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 1A4C976A70 for ; Mon, 19 Jun 2017 14:42:10 +0000 (UTC) (envelope-from onborodin@gmail.com) Received: by mail-lf0-x242.google.com with SMTP id x81so10878458lfb.3 for ; Mon, 19 Jun 2017 07:42:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:organization :mime-version:content-transfer-encoding; bh=SBYdlDmKlt2E+nvs2c5gcDAP11L2n7PNE2v29UlguMY=; b=gnzBaYCXs9+CanPh+utV8v6RgdPUf9ePraJWoAc1WTgPsOAAOWJ1PLBoyCLnqZGe8Q 3/MRLq7wM4kDy6crMjxhZH05zBz/u85/MxH9E6ZQ70FHQd+8oe011fcbdPfK3APhr2XC fXBvnxdBki+psrdKeYA9ank2oQRB80g8hN+PhBtCBKJzbRt7qOALxtofpGw/+uR6T7rA Bc4CEOrVkyGPXJ9KN1LjCIHPq8w6kLS3gn69uTzC2+iE2c2DVACyMC3WRCQZPZD5T3dr KjEGJVl19mFVET/kCitofdNSPrQfPtO83dDdZY7bOQKORg+h9e3L6S1DSgjTevO+8MyJ CbMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:organization:mime-version:content-transfer-encoding; bh=SBYdlDmKlt2E+nvs2c5gcDAP11L2n7PNE2v29UlguMY=; b=ki/cPdcs+l4U11Kr1Anw/aNUDFvyM9RbgWaaX4wJ1kqLRVQJ3WgjzIn4T6fALXBCL4 RepbWvptxB0T3LbP/cPi5VXbG6HXBKl3Ol8YZ6Gl/dZKzpAJnjHpizoj7AkHvCwAEMql TrSlvOrM8GSsEsvRLHOYoZWXAjj+1O93Wif69HoYztdiIPJbzyn7cHNIo6JUYA+QaUhl 6rpKNBLzDh7O14oc92mnfAdpTXeo0d7kTYLOykkb5cYBmhCM1GOpnPEcWQFhHA27vpK4 W52TjS9CvTF+giKV6CYcIYnovrVvrj3qGb7tBpFBjDaS9XU0YcUllY95ZmMDN4jEBZY3 264w== X-Gm-Message-State: AKS2vOwTAa+aiJfwA0jpurW57iUGYK+8thAIpCoEjGTH/1ci5HHRLZ9C lUN/XB4ofoAZImrk X-Received: by 10.25.217.77 with SMTP id q74mr7799046lfg.50.1497883328002; Mon, 19 Jun 2017 07:42:08 -0700 (PDT) Received: from localhost ([195.191.50.40]) by smtp.gmail.com with ESMTPSA id u11sm3134384lfi.36.2017.06.19.07.42.06 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 19 Jun 2017 07:42:07 -0700 (PDT) Date: Mon, 19 Jun 2017 16:42:03 +0200 From: Borodin Oleg To: freebsd-ports@freebsd.org Subject: Re: Questions about order of adding application to freebsd ports. Message-ID: <20170619164203.340b0cf2@gmail.com> In-Reply-To: <20170609082438.GN43031@home.opsec.eu> References: <20170609092338.1dfcf932@gmail.com> <20170609072859.GK43031@home.opsec.eu> <20170609101221.3b0c60e7@gmail.com> <20170609082438.GN43031@home.opsec.eu> Organization: The Home X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.31; amd64-portbld-freebsd11.0) 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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 14:42:10 -0000 On Fri, 9 Jun 2017 10:24:38 +0200 Kurt Jaeger wrote: > Hi! > > > > > I ask for little advice. > > > > I wrote web manager X.509 certificates http://minica.unix7.org/ and created a freebsd port for it. > > > > > > > > 1. Who could check quality and security of this code? > > > > > > The committer would check the port quality etc. > > > > Next dummy question from novice, excuse me =) > > > > How to become a new committer for a new port? > > There are two roles: The maintainer (the person that decides what > changes go into a port), and the committer (the person that > has commit rights to the freebsd port repository). > > For a new port, the submitter of the new port is normally also the > maintainer. > > I found your port and patches at > > http://minica.unix7.org/ > > and will have a look, anyway (if I find the time). > > > > Submit patches via bugs.freebsd.org for the two ports, and > > > the maintainers will decide if they include them. > > > > If they do not answer for a long-long time? > > Then the PR / patch runs into a maintainer timeout (14 days) and any > committer can override the maintainer (if the patch is valid). > > > Or the committer will have a bad mood? > > There are more committers, so one committer is hopefully not the bottleneck. > If one committer is not doing the job, poke another one to ask to take over. > > > So already it was some times. > > If you have cases like that (and I'm guilty of that as well), > post the PR number here and some other committer will pick it up. > Thank you too, Kurt, I will follow your instructions as you go along. With best regards, Oleg Borodin +7-952-058-72-64 borodin@unix7.org onborodin@gmail.com From owner-freebsd-ports@freebsd.org Mon Jun 19 16:17:31 2017 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 BC809DA032B for ; Mon, 19 Jun 2017 16:17:31 +0000 (UTC) (envelope-from xavi.garcia@gmail.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (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 849DA7AEAB for ; Mon, 19 Jun 2017 16:17:31 +0000 (UTC) (envelope-from xavi.garcia@gmail.com) Received: by mail-it0-x232.google.com with SMTP id m62so69530222itc.0 for ; Mon, 19 Jun 2017 09:17:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=jFYUz+Ehz0Cx+F7r3WFXy781iuz3NVlvhTnr65HgZps=; b=WA+ow05ayitNVsFmsgJV9DsSACTygxpPSnqSO8n9i54t/CJBTcLWK71el47YlKgY44 epEfUVADpAUiD5mkjcFRswttPnLG1Ue2voB4zjo5cznjWmc2rm+NqyYtEtHfik2Jsfms jAnTcyFOCcyvfBbT5pGXFvYrY/saiQzHcAqmdTf449m3tu2kgQKJk4QtEarpGA1J4DeV dw0B29UtteTRoNrnLHs2B7H6+FAcfWNgsxq45ZaZH1ySJamsMec+hwwvX1mjDkqZ/Iih Y11vjJG+8FPc5aEHIC5b4rIlg14My5mSQp2ulBV8atw67ii5UqfAZRfXOMUd8SBqnOi2 7fZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=jFYUz+Ehz0Cx+F7r3WFXy781iuz3NVlvhTnr65HgZps=; b=njuGeakfXoXUQ2ZDEqAE8gk5pRg0gEotZXwDY7WIeDV8KrsnCchZnygygIb6z9NGcn 9pDoAPQKwgz74Dtf3ZNlcQPvK5fsdS2Wghetflg5dqcLEKfxUeZR3S3UAhL7lMvC9DoA 3ngdd0lZN/FzstRUzp8nwSq9nHEaJgiXIA/d+uuK3K1cBx5yJ6//6t0cjF0Pw8Sf2tdW CgUc6+B3cY5b5ISLq73a5EUOHWQ0ICpBVBdUT/Bz8yBCzl2lofK83IgF6C3QB7tdmXq4 Eos7uNu7ZrVavXxaktq/Nhvnwaeo15uaGLoAlpk4oivRL6z+11RIR4aMx2JU/fQUAa+q ED3g== X-Gm-Message-State: AKS2vOxAt1/p+ww975IemyNszSA5GhT+Kv5K7WUGbMC4MJMMo5PB84f8 jifpoJ8g2L13xzE+ifqwOGUlEjend90Y X-Received: by 10.36.130.4 with SMTP id t4mr7415408itd.51.1497889050834; Mon, 19 Jun 2017 09:17:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.87.3 with HTTP; Mon, 19 Jun 2017 09:17:30 -0700 (PDT) In-Reply-To: References: From: Xavi Garcia Date: Mon, 19 Jun 2017 18:17:30 +0200 Message-ID: Subject: Re: databases/mariadb101-client broken in the quarterly branch (libressl) To: freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 16:17:31 -0000 After discussing the issue with a colleague, Q3 will be available next week and perhaps fixing the port in Q2 is not worth the effort if it's working in HEAD. I have to test this in our Poudriere running in the lab. Kind regards, Xavier Garcia 2017-06-19 14:35 GMT+02:00 Xavi Garcia : > Hi, > > Mariadb101-client stopped compiling with libressl in the quarterly branch > (2017Q2) after upgrading to 10.1.23. > > > Can somebody please have a look at: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219045#c16 > > Kind regards, > > Xavier Garcia > From owner-freebsd-ports@freebsd.org Mon Jun 19 18:24:42 2017 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 CB55CDA2395 for ; Mon, 19 Jun 2017 18:24:42 +0000 (UTC) (envelope-from ben.lavery@hashbang0.com) Received: from sender-of-o51.zoho.com (sender-of-o51.zoho.com [135.84.80.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9FC667F7AE for ; Mon, 19 Jun 2017 18:24:41 +0000 (UTC) (envelope-from ben.lavery@hashbang0.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1497896669; s=zoho; d=hashbang0.com; i=ben.lavery@hashbang0.com; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References; l=7222; bh=KyHa24mc5ecIoJbQBXFFw4kFvIM0a+Jg7Q09gvwKcq4=; b=V4UpOOT4XvVB3wxOG8BlxeVGAtVu7GTP04wNnrqJNH36gXGGD2LxoNayLpfTHkEE s4lx2R3Y6U5UmklVOpMF0KSUUOcEv8ragKzECUhrEP1AtmmPSkqZ4fjpUL6HMkPkHcH ltXxF03MdK9v0z2dQl7xmEbzjQodrpJJm07myJ+Q= Received: from [192.168.0.6] (cpc67734-bary4-2-0-cust251.5-1.cable.virginm.net [82.18.216.252]) by mx.zohomail.com with SMTPS id 1497896668900979.349877846514; Mon, 19 Jun 2017 11:24:28 -0700 (PDT) From: Ben Lavery-Griffiths Message-Id: <5FD6B35B-3591-4228-80C7-1FF8AB3DDC65@hashbang0.com> Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Keeping -CURRENT up to date with Poudriere Date: Mon, 19 Jun 2017 19:24:25 +0100 In-Reply-To: Cc: FreeBSD Ports To: Ultima References: <52A7B196-B76B-4920-B352-7187DE2513DA@hashbang0.com> X-Mailer: Apple Mail (2.3273) X-ZohoMailClient: External Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 18:24:42 -0000 Thanks very much, I=E2=80=99ll look into doing similar. Thanks again, Ben > On 18 Jun 2017, at 20:56, Ultima wrote: >=20 > Poudriere will update based on how it initially was created > unless it was modified in=20 > /usr/local/etc/poudriere.d/jails/$JAIL/method. For the > -STABLE and -CURRENT branch, It *may* somehow be > obtained another way, but usually it has to be compiled > from the respected branch. So it needs to be manually > compiled in /usr/src before doing a poudriere update. >=20 > The way I handle multiple branches is adding adding > multiple in /usr/src, eg /usr/src/head, /usr/src/11-stable, > then setting the src in that directory with obj in it as well. >=20 > /usr/src/head/src and obj /usr/src/head/obj the method > will need to be set to src=3D/usr/src/head/src and object > export MAKEOBJDIRPREFIX=3D/usr/src/head/obj in the > ${JAIL}-poudriere.conf. >=20 > I also make a dataset for each target branch so it can > be zfs send/received. >=20 >=20 > I hope this helps > Ultima >=20 > On Sun, Jun 18, 2017 at 9:49 AM, Ben Lavery-Griffiths = > wrote: > Hi all, >=20 > I=E2=80=99ve got a 12.0-CURRENT Poudriere jail for ports testing. Am = I right in thinking that when Poudriere updates a jail it uses = freebsd-update? In which case, -STABLE and -CURRENT jails can=E2=80=99t = be updated - correct? >=20 > In this case, if I want to get the latest -STABLE or -CURRENT = snapshot, will I need to recreate my jail? Or can Poudriere do it a = different way? >=20 > Currently when I try to update I get this: >=20 > > [00:00:00] =3D=3D=3D=3D>> Upgrading using ftp > > /etc/resolv.conf -> /poudriere/jails/12Ci386/etc/resolv.conf > > mount: /poudriere/jails/12Ci386/compat: No such file or directory > > Bad system call (core dumped) > > 12.0-CURRENT > > [00:00:01] =3D=3D=3D=3D>> Recording filesystem state for clean=E2=80=A6= done >=20 >=20 > Many thanks, > Ben > _______________________________________________ > 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 From owner-freebsd-ports@freebsd.org Mon Jun 19 18:26:51 2017 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 BF188DA2416 for ; Mon, 19 Jun 2017 18:26:51 +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 868867F889 for ; Mon, 19 Jun 2017 18:26:51 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dN1O0-000Oxp-7c; Mon, 19 Jun 2017 20:26:52 +0200 Date: Mon, 19 Jun 2017 20:26:52 +0200 From: Kurt Jaeger To: Borodin Oleg Cc: freebsd-ports@freebsd.org Subject: Re: Questions about order of adding application to freebsd ports. Message-ID: <20170619182652.GA2749@home.opsec.eu> References: <20170609092338.1dfcf932@gmail.com> <20170609072859.GK43031@home.opsec.eu> <20170609101221.3b0c60e7@gmail.com> <20170609082438.GN43031@home.opsec.eu> <20170619164203.340b0cf2@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170619164203.340b0cf2@gmail.com> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 18:26:51 -0000 Hi! > Thank you too, Kurt, I will follow your instructions as you go along. I've committed the two patches you submitted. I also added them to the CPAN ticket system attached to the upstream perl modules, so that the CPAN module maintainer can add them. -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-ports@freebsd.org Mon Jun 19 19:52:29 2017 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 2CADFDA349A for ; Mon, 19 Jun 2017 19:52:29 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.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 172FF81978 for ; Mon, 19 Jun 2017 19:52:28 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dN2SX-000Lor-9R for freebsd-ports@freebsd.org; Mon, 19 Jun 2017 13:35:37 -0600 Date: Mon, 19 Jun 2017 13:35:37 -0600 From: The Doctor To: freebsd-ports@freebsd.org Subject: Apache 2.4.26 Message-ID: <20170619193537.GA83537@doctor.nl2k.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 19:52:29 -0000 Anyone noticing problems with Apache 2.4.26 when trying to replace Apache 2.4.25 ? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism Talk Sense to a fool and he calls you foolish - Euripides From owner-freebsd-ports@freebsd.org Mon Jun 19 21:15:52 2017 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 45936DA4ECA for ; Mon, 19 Jun 2017 21:15:52 +0000 (UTC) (envelope-from jaapna@xs4all.nl) Received: from lb1-smtp-cloud2.xs4all.net (lb1-smtp-cloud2.xs4all.net [194.109.24.21]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CFC1384A9C for ; Mon, 19 Jun 2017 21:15:51 +0000 (UTC) (envelope-from jaapna@xs4all.nl) Received: from [192.168.1.181] ([80.100.158.12]) by smtp-cloud2.xs4all.net with ESMTP id alEY1v00A0GL7VL01lEe5u; Mon, 19 Jun 2017 23:14:39 +0200 From: Jaap Akkerhuis Message-Id: <20047649-9F01-450C-9E62-BF2148EFBD01@xs4all.nl> Content-Type: multipart/signed; boundary="Apple-Mail=_CC6885EC-A911-4CBA-8115-9D30C44C9DBA"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Keeping -CURRENT up to date with Poudriere Date: Mon, 19 Jun 2017 23:14:30 +0200 In-Reply-To: <5FD6B35B-3591-4228-80C7-1FF8AB3DDC65@hashbang0.com> Cc: Ultima , FreeBSD Ports To: Ben Lavery-Griffiths References: <52A7B196-B76B-4920-B352-7187DE2513DA@hashbang0.com> <5FD6B35B-3591-4228-80C7-1FF8AB3DDC65@hashbang0.com> X-Mailer: Apple Mail (2.3273) X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 21:15:52 -0000 --Apple-Mail=_CC6885EC-A911-4CBA-8115-9D30C44C9DBA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jun 19, 2017, at 20:24, Ben Lavery-Griffiths = wrote: >=20 > Thanks very much, >=20 > I=E2=80=99ll look into doing similar. What I do is to have STABLE and CURRENT jails using the svn method. Then "poudriere jail -u" takes care of the update. jaap --Apple-Mail=_CC6885EC-A911-4CBA-8115-9D30C44C9DBA Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org Comment: no-use-standard-socket iEYEARECAAYFAllIPrcACgkQIxHHWPCofYWLSgCfSeEbFYfVnBUJSbkWCYOZayfS aDcAn2aVxb0npsV/dRtHfxj+Iq6jO3KY =E3DQ -----END PGP SIGNATURE----- --Apple-Mail=_CC6885EC-A911-4CBA-8115-9D30C44C9DBA-- From owner-freebsd-ports@freebsd.org Mon Jun 19 21:24:22 2017 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 492E4DA50E3 for ; Mon, 19 Jun 2017 21:24:22 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: from mail-wr0-x244.google.com (mail-wr0-x244.google.com [IPv6:2a00:1450:400c:c0c::244]) (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 D281C84F1F for ; Mon, 19 Jun 2017 21:24:21 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: by mail-wr0-x244.google.com with SMTP id 77so15218606wrb.3 for ; Mon, 19 Jun 2017 14:24:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=WNDt7OpfTDi8DXYNMz/5lPmL9PsOz3oQkXLs8XyKKwE=; b=jT6i2JqfrlrDPfjvwz54QqKUpwkz10fVla3301gAzs+4U5EASGGC1NNctgxC3YJnA2 tFray2sC+S7jGCNHVDvNBLk4n0TieaNWvzjkhLnLCh+TbfKu7enbotgYSDMTtshCJZWg XdR4VW7LW2E3p1Osjbfkn4n8U/SUKLQ3n/5ZNEN8LoToBEtF8NlvB2eyfMNJvN9iVy6J 7xsuVzZOQn/hx/DLG0VKSvVChFQzMOK83BIKIUsQjVOa4a8CIkm28KWSJ1zehliMcogi Kqoa5crb4tWURLgbvVEHwO95yTpKkm6dfuWnMvAVSK5CzHt2czoG01Ztl+qkJFQTwt40 F08w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=WNDt7OpfTDi8DXYNMz/5lPmL9PsOz3oQkXLs8XyKKwE=; b=YVFtNwNDr5NfuvoEfrryba7ugYA090ur8XjyqhE6qjBsv25ondl6QI9muYgL7iKodh 2M67XyM8oiUo70unrPazV++ebA9w5haxXdQQbQhPyyK6waUxWJgLgfOt2zNaI/aE3VmL QmAxnKfdmD1LnpaL5mddNBXKen6uSxO8XJg4VifWjNUMtkV23gaL73b8bjGPwQ2VbEQf WlvFsXuGnNyBQjb6yFvxcixJVyLxhwivLXfjmqokvBPIqzT+yORGlLE37BpRWlDGc2IH KET+sMYUnK1sls4xYmiICm+0XkomZ1jJRcj7A2eRKiFrcQxOm87rir76xR8AMSMYMBkq v7WA== X-Gm-Message-State: AKS2vOxm7x5XlJAaWMi7ZIAGKeNhliMKfZqArItLR1GxPIvLQxZai2P4 G9LvBkVNFxZQFg== X-Received: by 10.223.152.34 with SMTP id v31mr14316613wrb.60.1497907460415; Mon, 19 Jun 2017 14:24:20 -0700 (PDT) Received: from gmail.com (tao.xtaz.uk. [2001:8b0:fe33::10]) by smtp.gmail.com with ESMTPSA id 2sm14725925wrx.26.2017.06.19.14.24.19 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 19 Jun 2017 14:24:20 -0700 (PDT) Date: Mon, 19 Jun 2017 22:24:18 +0100 From: Matt Smith To: Jaap Akkerhuis Cc: Ben Lavery-Griffiths , FreeBSD Ports , Ultima Subject: Re: Keeping -CURRENT up to date with Poudriere Message-ID: <20170619212417.GA47178@gmail.com> Mail-Followup-To: Matt Smith , Jaap Akkerhuis , Ben Lavery-Griffiths , FreeBSD Ports , Ultima References: <52A7B196-B76B-4920-B352-7187DE2513DA@hashbang0.com> <5FD6B35B-3591-4228-80C7-1FF8AB3DDC65@hashbang0.com> <20047649-9F01-450C-9E62-BF2148EFBD01@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20047649-9F01-450C-9E62-BF2148EFBD01@xs4all.nl> User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jun 2017 21:24:22 -0000 On Jun 19 23:14, Jaap Akkerhuis wrote: > >> On Jun 19, 2017, at 20:24, Ben Lavery-Griffiths wrote: >> >> Thanks very much, >> >> I’ll look into doing similar. > >What I do is to have STABLE and CURRENT jails using the svn method. >Then "poudriere jail -u" takes care of the update. > Why bother having the system compile it twice? If you use -m src=/usr/src then it will just use the already built STABLE world from your host build. Easy way to make it synced to the live system. And poudriere jail -u still works fine to update it. -- Matt From owner-freebsd-ports@freebsd.org Tue Jun 20 01:03:57 2017 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 8FCD3DA7EC0 for ; Tue, 20 Jun 2017 01:03:57 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dnvrco-oedge-vip.email.rr.com", Issuer "dnvrco-oedge-vip.email.rr.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F46765FC9 for ; Tue, 20 Jun 2017 01:03:56 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:11663] helo=localhost) by dnvrco-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 34/A9-03935-5B378495; Tue, 20 Jun 2017 01:00:38 +0000 Date: Tue, 20 Jun 2017 01:00:42 +0000 Message-ID: <34.A9.03935.5B378495@dnvrco-omsmta01> From: "Thomas Mueller" To: freebsd-ports@freebsd.org References: <5C.19.03935.91517495@dnvrco-omsmta01> <0e32b32b-5a8d-6f08-b969-9d3fd638d459@FreeBSD.org> Subject: Re: pkg convert? X-RR-Connecting-IP: 107.14.64.6:25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jun 2017 01:03:57 -0000 > On 19/06/2017 01:04, Thomas Mueller wrote: > > Looking through the man page for pkg, I see there is still an entry for convert ("pkg help convert" or "man pkg-convert"). > DESCRIPTION > > pkg convert is used to convert from/to pkg(8) local database to legacy > > pkg_install tools format. > OPTIONS > > The following options are supported by pkg convert: > > -d pkg_dbdir, --pkg-dbdir pkg_dbdir > > The location of the pkg_add(1) dbdir. Defaults to /var/db/pkg. > > -n, --dry-run > > Dry-run mode. Do not actually convert anything. Just show what > > would be done. > > What is this? Looks obsolete to me, I thought the legacy pkg_install tools format was long gone with no going back. > > I tried this with -n (dry-run) just for curiosity, and naturally it didn't work: > > I got > > pkg: Unable to open plist file: /var/db/pkg/texlive-texmf-20150523_3/+CONTENTS > > Skipping invalid package: /var/db/pkg/texlive-texmf-20150523_3 > > and many more like that. > > If this legacy functionality is long gone, why is it still in the man page or "pkg help convert"? > > I saw it as recently as 11.1-PRERELEASE. > I believe the documentation is somewhat inaccurate: pkg-convert(8) will > convert the old pkg_tools format to pkg(8), but not the reverse. > Yes, this is pretty much of legacy interest only nowadays, but I suspect > there are still 8.x machines needing upgrade here and there. > Cheers, > Matthew Actually, I have an old FreeBSD 8.2 installation on a 40 GB IDE hard drive, MBR with legacy FreeBSD bsdlabel on MBR slice 4, not enough maneuvering space for any upgrading. I had the later thought, pkg is also in NetBSD pkgsrc, maybe pkg convert in NetBSD, but I would be inclined to try only on a system already messed up sufficiently that there is nothing further to lose. Or one can use pkgsrc (ouch!) with FreeBSD with old pkg_* tools and decide to switch to FreeBSD pkgng format. Tom From owner-freebsd-ports@freebsd.org Tue Jun 20 02:29:19 2017 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 3C3A2D89FFD for ; Tue, 20 Jun 2017 02:29:19 +0000 (UTC) (envelope-from amutu@amutu.com) Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (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 ECB3A6A912 for ; Tue, 20 Jun 2017 02:29:18 +0000 (UTC) (envelope-from amutu@amutu.com) Received: by mail-oi0-x236.google.com with SMTP id p187so6638369oif.3 for ; Mon, 19 Jun 2017 19:29:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amutu-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=AJ1DyMo5RLmnHVdnhk51u3YFz6wNitjeDIBMFxiGeRc=; b=NhUWBWZm6JSRHKdzF1B6MjabVoC14SaUjzvtjJbz5qF0733xI4dNhfkxyy6iwPVwQo JWavtFaOjtWzCCP7SpeP8Vmz/N2sqXLCFeRcAIXPE/dz6SSLvMKmJGaBZuJ7Ep6q95Yu 9mXuetZPIekflIJJQtkvM60tTKEeQjADsMsNWysIBTfPDONrCmLCZJ0VCqy6cOncbuq9 RBUl5cvJryfyGMdAOJrQva95hhl8cKhBtIqqRl33qVx3ckHBqUXSsVHUsTDlOnQK+okA GTJG8dSh1Wwx8NC67dcAGkxHWVbF1c8rkbh9KFJWvBPLzLwibsMNt4QubEetWUcu/wWp jD9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=AJ1DyMo5RLmnHVdnhk51u3YFz6wNitjeDIBMFxiGeRc=; b=tQejar1fTTBNmSxom5hHfhcfjLB2mRKkOgCU2cM7r3ayr+uP/8MXTWElhsRfxADK78 yfxXQPAhBuzolzbe10mob3DlV9fEyXuZyww3QuqyrJ9b3+NAFiWX0MOxJcCiRs6kRYio 3pj0ZhftwqokDsyZ7czD+7Oxjf5K1UliQqTjtLkr6uXQCjD390v7PQl3kjUf3m7Ms9uY AjQfAsL9kmvDtETEwV9z/40FdWOGaE6aH/MDb7JFHTKUM4FmhwIZyAoT2pZ9tjuWv4Vl orzSAgmjpyu3TcOs0meV5x5l2f/pgh1JL5CKqfoJ84dqHOVFZEQw3vM1Mj+LotY1ylXf 5dug== X-Gm-Message-State: AKS2vOzO8RqBCzL/6dNFlricnCKyJYTs/RxuH5ykHl4KoO7fagWMY8XP rwrOGlL/qBt4TsYMKoWTFw== X-Received: by 10.202.93.212 with SMTP id r203mr12354271oib.219.1497925757949; Mon, 19 Jun 2017 19:29:17 -0700 (PDT) Received: from mail-ot0-f173.google.com (mail-ot0-f173.google.com. [74.125.82.173]) by smtp.gmail.com with ESMTPSA id p6sm3807078oie.24.2017.06.19.19.29.17 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Jun 2017 19:29:17 -0700 (PDT) Received: by mail-ot0-f173.google.com with SMTP id s7so80569341otb.3 for ; Mon, 19 Jun 2017 19:29:17 -0700 (PDT) X-Received: by 10.157.43.116 with SMTP id f49mr13708360otd.140.1497925757227; Mon, 19 Jun 2017 19:29:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.133.136 with HTTP; Mon, 19 Jun 2017 19:28:56 -0700 (PDT) In-Reply-To: <20170619212417.GA47178@gmail.com> References: <52A7B196-B76B-4920-B352-7187DE2513DA@hashbang0.com> <5FD6B35B-3591-4228-80C7-1FF8AB3DDC65@hashbang0.com> <20047649-9F01-450C-9E62-BF2148EFBD01@xs4all.nl> <20170619212417.GA47178@gmail.com> From: Jov Date: Tue, 20 Jun 2017 10:28:56 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Keeping -CURRENT up to date with Poudriere To: Matt Smith , Jaap Akkerhuis , Ben Lavery-Griffiths , FreeBSD Ports , Ultima Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jun 2017 02:29:19 -0000 I use -m url=3DSOMEURL to setup 12-CURRENT jail,like this: poudriere jail -c -j 12current-20170619 -m url=3D ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/12.0-CURRENT -v 12-CURRENTCURRENT When update, I just delete the old jail and setup another new one. Regards, Jov 2017-06-20 5:24 GMT+08:00 Matt Smith : > On Jun 19 23:14, Jaap Akkerhuis wrote: > >> >> On Jun 19, 2017, at 20:24, Ben Lavery-Griffiths >>> wrote: >>> >>> Thanks very much, >>> >>> I=E2=80=99ll look into doing similar. >>> >> >> What I do is to have STABLE and CURRENT jails using the svn method. >> Then "poudriere jail -u" takes care of the update. >> >> > Why bother having the system compile it twice? If you use -m src=3D/usr/s= rc > then it will just use the already built STABLE world from your host build= . > Easy way to make it synced to the live system. And poudriere jail -u stil= l > works fine to update it. > > > > -- > Matt > > _______________________________________________ > 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 Tue Jun 20 03:11:18 2017 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 1FEBCD8C071; Tue, 20 Jun 2017 03:11:18 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pg0-x241.google.com (mail-pg0-x241.google.com [IPv6:2607:f8b0:400e:c05::241]) (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 DE3556F93B; Tue, 20 Jun 2017 03:11:17 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pg0-x241.google.com with SMTP id e187so10387165pgc.3; Mon, 19 Jun 2017 20:11:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:reply-to:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ecHvhPYfkOHdsmRk6EKg8kDhNcSPBCn/28XADSUgF90=; b=Gj1rBVepdvExyyuZKHxX19YJ8SKANyeOcqriMG2xQYIhGcKn0liMkQYGnpBrBKPJx1 lJ0LrAS7VxPJbailk/rqYUTuMj70JdElwlFxus/P5Q4S8qz4gzaUIVpq+6X3JdHNBEt2 ZhnlCl1/pqWFdT5DKLR0IZPMleaIug2lwXEMz+xVGaAUtCUG5S8K+D48z+HZXME8/tNV burAnabCilpeGdVKFYZqgpSxUCoB1azGwG9CgGt0vyqIvNaIOPXWBwbO1qpU6NTgNSeP GNzfM0d9Qa9H98+k3dTy1m58KHpfP8JegWy4gpW4ZOXQ7sHNqS5xcEzUp0jYXjuSpFl1 ykFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:reply-to:subject:to:references:from :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=ecHvhPYfkOHdsmRk6EKg8kDhNcSPBCn/28XADSUgF90=; b=nF37knLYvPALxqq2ImPPNW+Ppmf31T11f4mV+DD3CqEs9WhMS5ncn9qgRn8zOuSd4m BQgs1PzRiGXfKP6KdZLRypAWCkGgQcyprhlZzghTc+gKl08Zg5BpVPcHBRT8Z0xU3/vg X7/sn63wTQky/gM9cYdqfVcObnC7DpbOrOdvJpqWP4pR2TXVzWDOyDqJV5pgrkdWKWal I2xwCdjp7p4PCGjGJ4SY468wjmVJdWc/a1mefDKzlLeG7dspYS5tyXg7TF8eLrOD9TNR ZNZtv61vJfYdmLsplfk+Hnu0qYrnh7bDp6HSnEjSB7XpXiawtByTRzKwVulljkV2C1VB 14eA== X-Gm-Message-State: AKS2vOyHwwgqHGM18yT+wv1TzWurun22sh2BpNXS2AzIWEUd0ZV//uMa 2eQhJw3N+VA39OYHcAw= X-Received: by 10.99.147.91 with SMTP id w27mr27740359pgm.24.1497928277189; Mon, 19 Jun 2017 20:11:17 -0700 (PDT) Received: from ?IPv6:2001:44b8:31ae:7b01:2042:3e8:d7ce:9b9c? (2001-44b8-31ae-7b01-2042-03e8-d7ce-9b9c.static.ipv6.internode.on.net. [2001:44b8:31ae:7b01:2042:3e8:d7ce:9b9c]) by smtp.gmail.com with ESMTPSA id v6sm11808081pfl.2.2017.06.19.20.11.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Jun 2017 20:11:16 -0700 (PDT) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: [PATCH] lang/python27 -- Fix namespace collision To: sgk@troutmask.apl.washington.edu, freebsd-ports@freebsd.org, python@FreeBSD.org References: <20170618182905.GA67867@troutmask.apl.washington.edu> <20170618183112.GA67920@troutmask.apl.washington.edu> From: Kubilay Kocak Message-ID: <9090f327-3266-35b3-8bf3-f83b7c741fe2@FreeBSD.org> Date: Tue, 20 Jun 2017 13:06:28 +1000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Thunderbird/54.0a2 MIME-Version: 1.0 In-Reply-To: <20170618183112.GA67920@troutmask.apl.washington.edu> Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jun 2017 03:11:18 -0000 On 6/19/17 4:31 AM, Steve Kargl wrote: > On Sun, Jun 18, 2017 at 11:29:05AM -0700, Steve Kargl wrote: >> Both IEEE-754 2008 and ISO/IEC TS 18661-4 define the half-cycle >> trignometric functions cospi, sinpi, and tanpi. When libm (aka >> math.h) grows support for sinpi(x), lang/python27 has a namespace >> collision. The attached patch fixes the problem. >> Hi Steve, Is this issue relevant only for particular (and/or future) FreeBSD versions ('where libm grows supports for x, y') or independent of base entirely? Also, could you open an upstream issue regarding this please, as a long-term target for all local (Python port) patches is that they are included upstream. This also ensures we can document all patches with their relevant upstream issue/commit references for our future selves and others. ./koobs > Well, that's inconvenient. Seems attachments are stripped. > > --- Modules/mathmodule.c.orig 2017-06-18 11:09:05.938222000 -0700 > +++ Modules/mathmodule.c 2017-06-18 11:09:56.248307000 -0700 > @@ -71,7 +71,7 @@ > static const double sqrtpi = 1.772453850905516027298167483341145182798; > > static double > -sinpi(double x) > +my_sinpi(double x) > { > double y, r; > int n; > @@ -270,7 +270,7 @@ > integer. */ > if (absx > 200.0) { > if (x < 0.0) { > - return 0.0/sinpi(x); > + return 0.0/my_sinpi(x); > } > else { > errno = ERANGE; > @@ -294,7 +294,7 @@ > } > z = z * lanczos_g / y; > if (x < 0.0) { > - r = -pi / sinpi(absx) / absx * exp(y) / lanczos_sum(absx); > + r = -pi / my_sinpi(absx) / absx * exp(y) / lanczos_sum(absx); > r -= z * r; > if (absx < 140.0) { > r /= pow(y, absx - 0.5); > @@ -366,7 +366,7 @@ > (x-0.5)*(log(x+lanczos_g-0.5)-1); > } > else { > - r = log(pi) - log(fabs(sinpi(absx))) - log(absx) - > + r = log(pi) - log(fabs(my_sinpi(absx))) - log(absx) - > (log(lanczos_sum(absx)) - lanczos_g + > (absx-0.5)*(log(absx+lanczos_g-0.5)-1)); > } > From owner-freebsd-ports@freebsd.org Tue Jun 20 03:49:34 2017 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 9EE9AD8D800; Tue, 20 Jun 2017 03:49:34 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 814C6719CB; Tue, 20 Jun 2017 03:49:34 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v5K3nR15075582 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 19 Jun 2017 20:49:27 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v5K3nRL9075581; Mon, 19 Jun 2017 20:49:27 -0700 (PDT) (envelope-from sgk) Date: Mon, 19 Jun 2017 20:49:27 -0700 From: Steve Kargl To: Kubilay Kocak Cc: freebsd-ports@freebsd.org, python@FreeBSD.org Subject: Re: [PATCH] lang/python27 -- Fix namespace collision Message-ID: <20170620034927.GA75540@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20170618182905.GA67867@troutmask.apl.washington.edu> <20170618183112.GA67920@troutmask.apl.washington.edu> <9090f327-3266-35b3-8bf3-f83b7c741fe2@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9090f327-3266-35b3-8bf3-f83b7c741fe2@FreeBSD.org> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jun 2017 03:49:34 -0000 On Tue, Jun 20, 2017 at 01:06:28PM +1000, Kubilay Kocak wrote: > On 6/19/17 4:31 AM, Steve Kargl wrote: > > On Sun, Jun 18, 2017 at 11:29:05AM -0700, Steve Kargl wrote: > >> Both IEEE-754 2008 and ISO/IEC TS 18661-4 define the half-cycle > >> trignometric functions cospi, sinpi, and tanpi. When libm (aka > >> math.h) grows support for sinpi(x), lang/python27 has a namespace > >> collision. The attached patch fixes the problem. > >> > > Is this issue relevant only for particular (and/or future) FreeBSD > versions ('where libm grows supports for x, y') or independent of base > entirely? It will be an issue with a future BSD. It seems to take a long time before any of my libm improvements are committed. At the moment, bde and I are probably the only people with sinpi(x) in our libm. I do, however, anticipate that glibc will get these functions in the future as portions of ISO/IEC TS 18661-4 have already been implemented. > Also, could you open an upstream issue regarding this please, as a > long-term target for all local (Python port) patches is that they are > included upstream. In the 5 minutes that I've searched, I've found https://bugs.python.org/ but there are no instructions on how to submit a bug report. -- Steve 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4 20161221 https://www.youtube.com/watch?v=IbCHE-hONow From owner-freebsd-ports@freebsd.org Tue Jun 20 12:45:19 2017 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 3250ED97E48 for ; Tue, 20 Jun 2017 12:45:19 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from sonic302-48.consmr.mail.ne1.yahoo.com (sonic302-48.consmr.mail.ne1.yahoo.com [66.163.186.174]) (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 E9F13804E3 for ; Tue, 20 Jun 2017 12:45:18 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1497962717; bh=7LTLI6NeGS/UOW52v7nX3vRfeSIzAJ9q1rMEjLL0BM8=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=elKrp4BQBeNwf3TFpXXtSS9UeASVjmC22QmOrCV1ZOxgbF+9+Bt7i/iLCgLBjIlEC/ZoWTX2AhS5lUKinfG3UpL5gfpfmolSncvxZJUfqZ3dKhhAo1ujT6Djiwqv1XCX8oQyL1j0DvEAiWIMW44daac3DsjK7zc9M4weUkkQtXB6ovOvW7QbxXJgqL/e4wZ0RXmq9HjvAPc9VteNWP4i6fem1PSXxBiVtCB5RdLPc8x9XuLV5WcQULij+MzN+SzF9XzZ05K+uhBMy0wNSn9+JRjcTxRDvWPBn7uj3dB6ybsC48J7Zl24S544z6QaPPgrvUNmWytWVn/1oVWCHnZ+qw== X-YMail-OSG: 84TTij8VM1mzYyKxHlNCZoTti1zQz7XQ6sDyRSNf5MRUPoKZSQuvMxFMtvgY0Tt MKxVpWJbbbQOidsFIAMeIAxDm7nM6cMXmSGj6hDTC9aTuZdkGlAzsrkpdTWIQsY1EygWgyI8mBwP cceWo9qywURGEA3TijUUa1ZGPz_J8U6cP.mIrt0TqWwSaMDjLntC3StsVM7T58f8V5Il7km2uL8p 3ud92fBF4y_r3B2ZQnw71VyoGNxUEupa3IA_6oYdNRneJzQzGJXhJ988Ok0OQ5QFoSchug5opk_v SwtqdYxwqxz1bzaS8Zjg9Hw4Ku8FJpvGW1.GrFlGm4vFMuG3B7yDFCyZ7ZG0A7db2UCILsvsygk7 pdtKt926qphiFxxKzv76j8CEzfIldIVeVOG8z_O4TPTo9wodHzat8smS_VzJHAjyqYvpyKjV0yWP OrTcA1D2b91NsSpJOtiipW2_gEGV_gqlu38Bp_XgbXtgS3N8Hxqp3mT0TQ3Qi6nFp7GZuAB7buME FIwtXI_t59V7tNokhcglna8ytJRBmHspMWcvG Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.ne1.yahoo.com with HTTP; Tue, 20 Jun 2017 12:45:17 +0000 Date: Tue, 20 Jun 2017 12:21:02 +0000 (UTC) From: Jeffrey Bouquet Reply-To: Jeffrey Bouquet To: Message-ID: <1356218856.2207512.1497961262380@mail.yahoo.com> Subject: perl problem MIME-Version: 1.0 References: <1356218856.2207512.1497961262380.ref@mail.yahoo.com> X-Mailer: WebService/1.1.9911 YahooMailBasic Mozilla/5.0 (X11; FreeBSD i386; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 Lightning/5.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jun 2017 12:45:19 -0000 Attachment probably not sent to the list. CD /usr/ports/devel/p5-List-Regexp [new june 20 ] make build ... Encode.c: loadable library and perl binaries are mismatched ( got handshake key 0x8900080, needed 0x7b00080 *** Error code 1 Stop. make: stopped in /usr/ports/devel/p5-List-Regexp I've installed perl from v11 pkg because v12-CURRENT has not been updated lately and binaries fail with 'fstat' or 'stat' errors However, this workaround fails with the exact same Encode.c error when using any perl port of note, for instance namefix... ............ apologies for the edge-case not-updated-yet question. ............... From owner-freebsd-ports@freebsd.org Tue Jun 20 19:21:43 2017 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 9EE6DDA004F for ; Tue, 20 Jun 2017 19:21:43 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::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 18DAE6FE74 for ; Tue, 20 Jun 2017 19:21:43 +0000 (UTC) (envelope-from xxjack12xx@gmail.com) Received: by mail-wr0-x234.google.com with SMTP id r103so104159773wrb.0 for ; Tue, 20 Jun 2017 12:21:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Vx2dg+9J4tSMyW1tPRf+6bGW/buHw2PofxEHJbDiXww=; b=I24+z2W/jF4H0xXkDiIl1hpNwJm5kzIh+KtP+cI+rQnSgofHm6D/+oozsyQXYdn38C mUoULJWFfx8t5fWgEUn2cJEFXalEsT1aCiL7nN2hR+Fn0mT+pwPDU+IUx8BGjFK7VuZZ efHzj10ZanO+nMcjC5XQ7/U9/DUA2zwgMijq0TpF7wzEDnxnvuy9z1vNcL0ogEPsRX/k pP5K4es2Pl8fW56Sritf0jk9L2rK6yRmHCa+CwlDeCeN7/ipKgcfSsqnqsW4umngWjrC Y4QjqBVfGg0bfhtm6jbDbcVftlZHgYP0AxskF/eeBZvVGKPfQNb+/NwITB35WcxHOjEm ESEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Vx2dg+9J4tSMyW1tPRf+6bGW/buHw2PofxEHJbDiXww=; b=KfOKqnIp9ImHhTfX4rBq73/FP3kaGTf3eQ1vM7J7/D7x1LUHjk/Zr2aEEsGUb19hcp MbI0pA3sWRLEeqGWyHt407x649q1T3u68BckgG/muoTVznBSRFpfKIgQbYaYAI1CrRD9 iUS7UB2tPEgdHycjvmnKzRBFHd0PGqcu8ilWm1TE1hmBj3RnDU9HyyLKwe69b38Qsf8+ ggc7zcKHDSKBOtuAeeT1t9JpWGX+jynwQ0NjQHfa6iE63V7o9o82Y5rPIX836giaVBrU /+imkFT/0VqkndNxVpMMHeoy/Y7CAdLmtZQcG/8N0li+YMsfnaVzWYDNMR8zkSOt2kJz kA5g== X-Gm-Message-State: AKS2vOwl8DPn3M2eqFZgS4bceY4PXZUj1y7VASHhoRyD2RDpqYODQcMq lCA5Bodj/fZn272+CdwcKX65fh81XQ== X-Received: by 10.28.66.86 with SMTP id p83mr4141148wma.31.1497986501504; Tue, 20 Jun 2017 12:21:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.176.241 with HTTP; Tue, 20 Jun 2017 12:21:00 -0700 (PDT) In-Reply-To: <20170619193537.GA83537@doctor.nl2k.ab.ca> References: <20170619193537.GA83537@doctor.nl2k.ab.ca> From: "Jack L." Date: Tue, 20 Jun 2017 12:21:00 -0700 Message-ID: Subject: Re: Apache 2.4.26 To: The Doctor Cc: FBSD Ports Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jun 2017 19:21:43 -0000 what kind of issues? On Mon, Jun 19, 2017 at 12:35 PM, The Doctor wrote: > Anyone noticing problems with Apache 2.4.26 when trying to replace Apache 2.4.25 ? > > -- > Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca > Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! > https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism > Talk Sense to a fool and he calls you foolish - Euripides > _______________________________________________ > 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 21 09:52:16 2017 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 6EEEBD8B40B for ; Wed, 21 Jun 2017 09:52:16 +0000 (UTC) (envelope-from ml@netfence.it) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 5AF0F3081 for ; Wed, 21 Jun 2017 09:52:16 +0000 (UTC) (envelope-from ml@netfence.it) Received: by mailman.ysv.freebsd.org (Postfix) id 5A271D8B40A; Wed, 21 Jun 2017 09:52:16 +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 58387D8B408 for ; Wed, 21 Jun 2017 09:52:16 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp206.alice.it (smtp206.alice.it [82.57.200.102]) by mx1.freebsd.org (Postfix) with ESMTP id DEE9B307E for ; Wed, 21 Jun 2017 09:52:15 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (95.250.147.61) by smtp206.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 5938655029DD88E3; Wed, 21 Jun 2017 11:52:07 +0200 Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) by soth.ventu (8.15.2/8.15.2) with ESMTP id v5L9q6lf038515; Wed, 21 Jun 2017 11:52:07 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu From: Andrea Venturoli To: ryanrfrederick@gmail.com, ports@freebsd.org Subject: net-mgmt/nagios-check_ports and jails Message-ID: <2cfd5c8c-b8b4-720a-5950-02bb59fe070b@netfence.it> Date: Wed, 21 Jun 2017 11:52:05 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jun 2017 09:52:16 -0000 Hello. I can't seem to get net-mgmt/nagios-check_ports for jails to work. Example: > # pkg audit -F > vulnxml file up-to-date > 0 problem(s) in the installed packages found. > # /usr/local/libexec/nagios/check_ports -j cacti > pkg: vulnxml file (null) does not exist. Try running 'pkg audit -F' first > [: -gt: unexpected operator > PORTS OK - security problem(s). | total_updates=0;0;0 security_problems=;0;0 > # /usr/local/etc/periodic/security/410.jailaudit > > Downloading a current audit database: > pkgng support enabled, using /usr/local/sbin/pkg version 1.10.1. > > portaudit for jails on xxxx.xxxxx - 5 problem(s) found. > > portaudit for jail: cacti (JID: 3) > > apache24-2.4.25_1 is vulnerable: > Apache httpd -- several vulnerabilities > CVE: CVE-2017-7679 > CVE: CVE-2017-7668 > CVE: CVE-2017-7659 > CVE: CVE-2017-3169 > CVE: CVE-2017-3167 > WWW: https://vuxml.FreeBSD.org/freebsd/0c2db2aa-5584-11e7-9a7d-b499baebfeaf.html > > 1 problem(s) found. > ... This host is using UFS and the jails on are created with EZJail. Any hint? bye & Thanks av. From owner-freebsd-ports@freebsd.org Wed Jun 21 11:43:06 2017 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 7CEB9D8D073 for ; Wed, 21 Jun 2017 11:43:06 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-oln040092004076.outbound.protection.outlook.com [40.92.4.76]) (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 3B0F965DC3; Wed, 21 Jun 2017 11:43:05 +0000 (UTC) (envelope-from carmel_ny@outlook.com) 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=Fb3tOzbBECIP79G2RU8I9/BTrPcsX8q5xuUMNTw0f0k=; b=AOZMWLc/2ZnJvOEjMr3oxWUi6TSXomRJNnQ9lyrZ8hwJZa7s/7JUWl/F+G6GkUQ++FPYKDWJSpysG7BJiTNIu98zzzNlq6ZUst/+JkzvWF/xHa6xzNscgfVve015RuZtE4rNSdIUCANX3/mQYU1yK1f8WSP1LGYVJOlHs7Z/C15pXfT07DQSB/ahDgxeaux7J/0fjmfWpLMnP2BN/7rZy/V7FjA/178i82H87QZYjWXH6elYpNV3N1cynWIqGuobA3tsZT/5pD3tkeup1tfxcYZ3SKa4PmM/LBfIpEuhq3sqo0ZE9YYohWKo5kJ05BDiAOnYdKd5+WO8Ur/a8tjvuA== Received: from CY1NAM02FT013.eop-nam02.prod.protection.outlook.com (10.152.74.57) by CY1NAM02HT015.eop-nam02.prod.protection.outlook.com (10.152.74.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1178.14; Wed, 21 Jun 2017 11:43:04 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com (10.152.74.54) by CY1NAM02FT013.mail.protection.outlook.com (10.152.75.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1178.14 via Frontend Transport; Wed, 21 Jun 2017 11:43:04 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) by BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) with mapi id 15.01.1199.015; Wed, 21 Jun 2017 11:43:04 +0000 From: Carmel NY To: FreeBSD Ports , "ohauer@FreeBSD.org" Subject: Update Postfix-current port. Thread-Topic: Update Postfix-current port. Thread-Index: AQHS6oOJdzd/k1EWgky0ynA+FRYKhA== Date: Wed, 21 Jun 2017 11:43:04 +0000 Message-ID: Reply-To: FreeBSD Ports Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=outlook.com; x-incomingtopheadermarker: OriginalChecksum:26C9241CA6F69BC287531B1BB719B36E1D5B1E43680AFAAEFB6028308ADD5D4F; UpperCasedChecksum:33CD4E0AE550BEBE6D433ED456DA21E62D7399DA21B954C1EBE16A4DB6C2C608; SizeAsReceived:7131; Count:44 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [RHmXDxV12xXCGCUwnFGXG+EbOY46Cnam] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; CY1NAM02HT015; 7:VQycV9CLsfwbMV30L/Z2TAIPGNQpLRp+0XFxqS/KAdycFitiUMi4bxudxbIjzBHhxnFGtT3Q1TI7ykhSYLGY7M7RVerLgaIBHFLdA2MZUPMbhQhW9ok2d8K3Nv72z76UdL3RtzRq3J60KJ5cmcefjqNMxfKGmyp1aqz75AOW5ggBHsHhIzLcA64LtUvjF9UJ439/mxxHDSzx+2Jojf1l56ID1sDRw7ei6ppnJeWvW4tluO+DTK4LEUn9nXyQ8FvNYtmg6GMZMczeMUXQp5c0BBbNuPtCULyt7wRUyBGZvgjf062Qs9RvpiMMvNbPz/dFbWtLl7+U95uGhRWmG6YoLEIaHXDHdu/jPm0TQuSjppkqcm84db7clq3Rij2V3GIXQyQEvWfetU9QYtXTMjCwM5g2I/rhxQVqGHHeRjpTgDbHqZDvVPmdoYl7NE91BZuiGCMhwb6OKIHjmaXJo+xroEELa5HjvngaM1Kon7d+WpA+YNc3oJ5hzfsdpwdVeVCCoP/eAOvdd+hPeXFkjxRsENIDNh8lGWiQS3UtnGad69PnXqU1iBzyjSxBgKFq3giGi8ffNKq6N8DCU2PfHKecjaECmU6KoqeakWFTeEZ1mdPAMTn/lJmy9Ul2+V07XcrVdDdLMRbCWDcFTIPWOhvvtb6FSoxPubowG8Eyu1m0BYHx/vcTjXNf7eyMVzQAoQrNuRL8ag5ixCS3tqmmkGAjf4MHM2VfYxF1HOF7ZX7k47mF6Zb+YRCsgtYNnI9+7mZ17IGFM43J98PbHOYBpq8pQg== x-incomingheadercount: 44 x-eopattributedmessage: 0 x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:CY1NAM02HT015; H:BN6PR2001MB1730.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: 21bc64bc-010c-4f12-6a34-08d4b89aab9a x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500055)(300135000095)(300000501055)(300135300095)(300000502055)(300135100095)(22001)(300000503055)(300135400095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045)(300000504055)(300135200095)(300000505055)(300135600095)(300000506048)(300135500095); SRVR:CY1NAM02HT015; x-ms-traffictypediagnostic: CY1NAM02HT015: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:CY1NAM02HT015; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY1NAM02HT015; x-forefront-prvs: 0345CFD558 spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jun 2017 11:43:04.1860 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1NAM02HT015 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jun 2017 11:43:06 -0000 The current version of the Postfix development available in the ports system is 3.3-20170502; however, the present version available is postfix-3.3-20170611. Is it possible to get the port's version undated? --=20 Carmel From owner-freebsd-ports@freebsd.org Wed Jun 21 11:59:28 2017 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 D3EF5D8D5D4 for ; Wed, 21 Jun 2017 11:59:28 +0000 (UTC) (envelope-from ryanrfrederick@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id AF93066391 for ; Wed, 21 Jun 2017 11:59:28 +0000 (UTC) (envelope-from ryanrfrederick@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id AEEB0D8D5D1; Wed, 21 Jun 2017 11:59:28 +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 AE904D8D5D0 for ; Wed, 21 Jun 2017 11:59:28 +0000 (UTC) (envelope-from ryanrfrederick@gmail.com) Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::230]) (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 70EC466390 for ; Wed, 21 Jun 2017 11:59:28 +0000 (UTC) (envelope-from ryanrfrederick@gmail.com) Received: by mail-ot0-x230.google.com with SMTP id s7so110300255otb.3 for ; Wed, 21 Jun 2017 04:59:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=P+sRKwtJ/ynlL8sOCwmDjUy3pPivkqNXFZlU8ywkCu8=; b=lYXirkqWggquZvTn6mMTXA5lPKV8dcImuhOrUSxV3GUIR/QbAuWYH5j+dAGP/84wX8 ykupjyPPn7njHgXoWBW/qK+da/LbnjnB95Uv9WQqzKVSnghk+Xe5ujJpxkM0bsJfo6sT Vqi8raMKcP/z33rvpbvnD7IM42WXyG+szScNjZB5l/MAAQ/WMiclE8aIS+sCekUu4jMu 6nQIwPRa5NoxGwDGjjjDcssjFDXIt4K537Wr6+DUMtCei0I//9uuy5i8TDjGJ8+1RoDq dHMnWs351LUH6hZOFHwebmMX9vxovavORG3DG3LayMLS221dHW6XVWffbCbrJjR0Q1z0 dPTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=P+sRKwtJ/ynlL8sOCwmDjUy3pPivkqNXFZlU8ywkCu8=; b=DWRvtX7HwvdQUmlrL0LwJ63X9wr+o05Kmii/OLX5BAa5q0uwfS0PnAd8rwBwXIcxI8 4z5rD3nr/hW7wKcVFGJ7yZti/CbvESFUWxi6MSTZPZw4uBFWsdQYc8QjeFUpW/1xIyXu gNGQMb3eHunJAaPreZ9WMio7oUnGmEM6w+RtasIZPHhhxh0N/o5IqiN9Mh1ptH6MOp+w dqA4D6mISkDMiFH9mgP7lUAnrIXOQGIdousMxAUaSILViF2V7PBvcOnSuXcf8t0dSPQu MHskyy0gwdz1eNIv/lGGMx4FDCfOekeQEKaklQoKKAwQ9vISXB7/FaSwm0lnTCSDZ4UJ HVRA== X-Gm-Message-State: AKS2vOyVzQeH/HLQhvFYT8zFm6+YKtYCFXTr7gx4qDRIYaiy2PaHxMsz 5g7DPUiHlVzkCZQ89JhS0Co+hlzyDdM5 X-Received: by 10.157.13.21 with SMTP id 21mr9053477oti.1.1498046367565; Wed, 21 Jun 2017 04:59:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.50.5 with HTTP; Wed, 21 Jun 2017 04:59:26 -0700 (PDT) Received: by 10.157.50.5 with HTTP; Wed, 21 Jun 2017 04:59:26 -0700 (PDT) In-Reply-To: <2cfd5c8c-b8b4-720a-5950-02bb59fe070b@netfence.it> References: <2cfd5c8c-b8b4-720a-5950-02bb59fe070b@netfence.it> From: Ryan Frederick Date: Wed, 21 Jun 2017 06:59:26 -0500 Message-ID: Subject: Re: net-mgmt/nagios-check_ports and jails To: Andrea Venturoli Cc: ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jun 2017 11:59:28 -0000 Hi Andrea, I have a pending pull request upstream that might resolve your issue. I'll take a look at it later today if time permits. Ryan On Jun 21, 2017 04:52, "Andrea Venturoli" wrote: > Hello. > > I can't seem to get net-mgmt/nagios-check_ports for jails to work. > > Example: > >> # pkg audit -F >> vulnxml file up-to-date >> 0 problem(s) in the installed packages found. >> # /usr/local/libexec/nagios/check_ports -j cacti pkg: vulnxml file >> (null) does not exist. Try running 'pkg audit -F' first >> [: -gt: unexpected operator >> PORTS OK - security problem(s). | total_updates=0;0;0 >> security_problems=;0;0 >> # /usr/local/etc/periodic/security/410.jailaudit >> Downloading a current audit database: >> pkgng support enabled, using /usr/local/sbin/pkg version 1.10.1. >> >> portaudit for jails on xxxx.xxxxx - 5 problem(s) found. >> >> portaudit for jail: cacti (JID: 3) >> >> apache24-2.4.25_1 is vulnerable: >> Apache httpd -- several vulnerabilities >> CVE: CVE-2017-7679 >> CVE: CVE-2017-7668 >> CVE: CVE-2017-7659 >> CVE: CVE-2017-3169 >> CVE: CVE-2017-3167 >> WWW: https://vuxml.FreeBSD.org/freebsd/0c2db2aa-5584-11e7-9a7d- >> b499baebfeaf.html >> >> 1 problem(s) found. >> ... >> > > This host is using UFS and the jails on are created with EZJail. > > Any hint? > > bye & Thanks > av. > From owner-freebsd-ports@freebsd.org Wed Jun 21 17:41:46 2017 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 CBAECD94B57 for ; Wed, 21 Jun 2017 17:41:46 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id B7EEB756E3 for ; Wed, 21 Jun 2017 17:41:46 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: by mailman.ysv.freebsd.org (Postfix) id B7573D94B56; Wed, 21 Jun 2017 17:41:46 +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 B704BD94B55 for ; Wed, 21 Jun 2017 17:41:46 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 901EF756E1 for ; Wed, 21 Jun 2017 17:41:46 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id v5LHY3Rk017840 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 21 Jun 2017 10:34:04 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me To: "ports@freebsd.org" From: Yuri Subject: Please commit the new port science/py-pymol: OpenGL based molecular visualization system Message-ID: <57e3e075-7497-79b1-2fd2-53fb7e158e5b@rawbw.com> Date: Wed, 21 Jun 2017 10:34:02 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jun 2017 17:41:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218729 I just verified, it builds fine. It has been previously deleted, but this shouldn't matter. Yuri From owner-freebsd-ports@freebsd.org Wed Jun 21 18:09:40 2017 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 40B40D9558D for ; Wed, 21 Jun 2017 18:09:40 +0000 (UTC) (envelope-from ryanrfrederick@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 1954176BCC for ; Wed, 21 Jun 2017 18:09:40 +0000 (UTC) (envelope-from ryanrfrederick@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 18A8BD9558C; Wed, 21 Jun 2017 18:09:40 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 184D9D9558B for ; Wed, 21 Jun 2017 18:09:40 +0000 (UTC) (envelope-from ryanrfrederick@gmail.com) Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (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 CB8A876BC9 for ; Wed, 21 Jun 2017 18:09:39 +0000 (UTC) (envelope-from ryanrfrederick@gmail.com) Received: by mail-oi0-x236.google.com with SMTP id c189so72112538oia.2 for ; Wed, 21 Jun 2017 11:09:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:from:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=I6bCnMiRE9sdNUge4KNZBu9fcdvC9X9dA5tnyGVsXjU=; b=e2ad4RmDk1scFNcJ/ZPSB7EH0/usqZu9/vmv46MSJHy2JqOb7ergcBjcZIhMjRttk2 cxTT4g0e/Ac+UgN61tO1i3uVoAHPPv5KxPkFMXa0EORxBN/CmXtqe9AeJ6PTBXr4TdEb OU0UbISfQw8BOj3SKlzSWwj7clqZ2ulm64orf4IhWMUUX3N81NlUVwQyGEfdnfTFflKg nOn/ep9Kj6Y71YsclcB7YhBHNtSoJrcoEdohMF4u5TblkAoh98aXb28kFEELxJ5kBsgh L0nwUFAQJ1t7IZPrzP45GU9g6hlW7lWH/0MGNpI28spd1RGYDBaCuXUhzpcmL/1eVQhl ns/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=I6bCnMiRE9sdNUge4KNZBu9fcdvC9X9dA5tnyGVsXjU=; b=ScBrvzzsuikZVR4gOHeKLow8RSev6sE4W5PrsYUJJGr/wWiSMq7dYkXlNaRuDiBpK3 RWiLKctN8Hyz0EbJNM1kPg8yW4O2+CRHy8Hi1oEn0dGE98du5u4cbnSgXEF4Hu1doNKy 4eVCnIehjq13tHk05qyEgQo5ULwn/tTmSS9Zjsqx9UdK9hhiLMHQmnly8wR+wqI7dsCF hfWzFZtHowUmKq4COnNVj1frody7wfbqR8/P8RDQE8p9X2api3xqrluwB1DjhRjLVX1e R3F84oggRK6kGcJ8bE/Kso8arOiOc4AtUNsBKZLrfHfpmB66l91XgdUx3jAKEPGy+2BG Xl/w== X-Gm-Message-State: AKS2vOwpMt6pM4RS/A487s7tbrkexjxbCczzJgYYKLgDCF3vdcwaytXf oLbeWWqu10yGkXQJLJE= X-Received: by 10.202.107.206 with SMTP id g197mr20862208oic.210.1498068578729; Wed, 21 Jun 2017 11:09:38 -0700 (PDT) Received: from [139.78.2.36] (bofh.it.okstate.edu. [139.78.2.36]) by smtp.googlemail.com with ESMTPSA id p2sm9522113ota.51.2017.06.21.11.09.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Jun 2017 11:09:38 -0700 (PDT) Subject: Re: net-mgmt/nagios-check_ports and jails From: Ryan Frederick To: Andrea Venturoli Cc: ports@freebsd.org References: <2cfd5c8c-b8b4-720a-5950-02bb59fe070b@netfence.it> Message-ID: <23a5901a-75e0-2624-066f-563fa0b181d3@gmail.com> Date: Wed, 21 Jun 2017 13:09:37 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jun 2017 18:09:40 -0000 Andrea, I took a look at ports-mgmt/jailaudit, and it works a bit differently than ports-mgmt/nagios-check_ports. jailaudit makes a list of packages installed in the jail and runs pkg(8) audit outside of the jail against the list. nagios-check_ports, on the other hand, calls pkg(8) audit with the -j option to run inside the jail and thus requires a copy of vuln.xml within the jail. I would suggest running `pkg audit -F` within the jails regularly or setup something to copy vuln.xml into the jails. That being said I do have a bugfix to commit upstream that unbreaks checking for updates within a jail from outside the jail. I'll hopefully get that released soon. Ryan On 06/21/2017 06:59 AM, Ryan Frederick wrote: > Hi Andrea, > > I have a pending pull request upstream that might resolve your issue. > I'll take a look at it later today if time permits. > > Ryan > > On Jun 21, 2017 04:52, "Andrea Venturoli" > wrote: > > Hello. > > I can't seem to get net-mgmt/nagios-check_ports for jails to work. > > Example: > > # pkg audit -F > vulnxml file up-to-date > 0 problem(s) in the installed packages found. > # /usr/local/libexec/nagios/check_ports -j cacti pkg: vulnxml > file (null) does not exist. Try running 'pkg audit -F' first > [: -gt: unexpected operator > PORTS OK - security problem(s). | total_updates=0;0;0 > security_problems=;0;0 > # /usr/local/etc/periodic/security/410.jailaudit > Downloading a current audit database: > pkgng support enabled, using /usr/local/sbin/pkg version 1.10.1. > > portaudit for jails on xxxx.xxxxx - 5 problem(s) found. > > portaudit for jail: cacti (JID: 3) > > apache24-2.4.25_1 is vulnerable: > Apache httpd -- several vulnerabilities > CVE: CVE-2017-7679 > CVE: CVE-2017-7668 > CVE: CVE-2017-7659 > CVE: CVE-2017-3169 > CVE: CVE-2017-3167 > WWW: > https://vuxml.FreeBSD.org/freebsd/0c2db2aa-5584-11e7-9a7d-b499baebfeaf.html > > > 1 problem(s) found. > ... > > > This host is using UFS and the jails on are created with EZJail. > > Any hint? > > bye & Thanks > av. > From owner-freebsd-ports@freebsd.org Wed Jun 21 19:33:14 2017 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 25BF7D97BBF for ; Wed, 21 Jun 2017 19:33:14 +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 E1C357BBDC; Wed, 21 Jun 2017 19:33:13 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dNlNL-0003eB-Nz; Wed, 21 Jun 2017 21:33:15 +0200 Date: Wed, 21 Jun 2017 21:33:15 +0200 From: Kurt Jaeger To: FreeBSD Ports Cc: "ohauer@FreeBSD.org" Subject: Re: Update Postfix-current port. Message-ID: <20170621193315.GC2749@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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jun 2017 19:33:14 -0000 Hi! > The current version of the Postfix development available in the ports > system is 3.3-20170502; however, the present version available is > postfix-3.3-20170611. Is it possible to get the port's version undated? Can you provide a patch via bugs.freebsd.org ? -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-ports@freebsd.org Wed Jun 21 20:01:52 2017 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 E9455D982AC for ; Wed, 21 Jun 2017 20:01:52 +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 B20307C9E6 for ; Wed, 21 Jun 2017 20:01:52 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dNlp6-0003hD-4r for freebsd-ports@freebsd.org; Wed, 21 Jun 2017 22:01:56 +0200 Date: Wed, 21 Jun 2017 22:01:56 +0200 From: Kurt Jaeger To: FreeBSD Ports Subject: Re: Update Postfix-current port. Message-ID: <20170621200156.GD2749@home.opsec.eu> References: <20170621193315.GC2749@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170621193315.GC2749@home.opsec.eu> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jun 2017 20:01:53 -0000 Hi! > > The current version of the Postfix development available in the ports > > system is 3.3-20170502; however, the present version available is > > postfix-3.3-20170611. Is it possible to get the port's version undated? > > Can you provide a patch via bugs.freebsd.org ? Oliver already fixed it. -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-ports@freebsd.org Thu Jun 22 06:15:40 2017 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 59B03DA71FB for ; Thu, 22 Jun 2017 06:15:40 +0000 (UTC) (envelope-from ml@netfence.it) 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 4303A6F0BF for ; Thu, 22 Jun 2017 06:15:40 +0000 (UTC) (envelope-from ml@netfence.it) Received: by mailman.ysv.freebsd.org (Postfix) id 42575DA71FA; Thu, 22 Jun 2017 06:15:40 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41EE7DA71F9 for ; Thu, 22 Jun 2017 06:15:40 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp205.alice.it (smtp205.alice.it [82.57.200.101]) by mx1.freebsd.org (Postfix) with ESMTP id CBDF96F0BE for ; Thu, 22 Jun 2017 06:15:39 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (95.250.147.61) by smtp205.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 594595F406DBF2EB; Thu, 22 Jun 2017 08:15:13 +0200 Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) by soth.ventu (8.15.2/8.15.2) with ESMTP id v5M6FBqs038319; Thu, 22 Jun 2017 08:15:12 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu Subject: Re: net-mgmt/nagios-check_ports and jails To: Ryan Frederick Cc: ports@freebsd.org References: <2cfd5c8c-b8b4-720a-5950-02bb59fe070b@netfence.it> <23a5901a-75e0-2624-066f-563fa0b181d3@gmail.com> From: Andrea Venturoli Message-ID: <1c9c0c88-eca5-7278-e498-50172bc5ef70@netfence.it> Date: Thu, 22 Jun 2017 08:15:11 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <23a5901a-75e0-2624-066f-563fa0b181d3@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 06:15:40 -0000 On 06/21/17 20:09, Ryan Frederick wrote: > Andrea, > > I took a look at ports-mgmt/jailaudit, and it works a bit differently > than ports-mgmt/nagios-check_ports. jailaudit makes a list of packages > installed in the jail and runs pkg(8) audit outside of the jail against > the list. nagios-check_ports, on the other hand, calls pkg(8) audit with > the -j option to run inside the jail and thus requires a copy of > vuln.xml within the jail. That's what I suspected. > I would suggest running `pkg audit -F` within the jails regularly or > setup something to copy vuln.xml into the jails. > > That being said I do have a bugfix to commit upstream that unbreaks > checking for updates within a jail from outside the jail. I'll hopefully > get that released soon. I'm in no hurry, so I can wait for soon :) Thanks for your work. bye av. From owner-freebsd-ports@freebsd.org Thu Jun 22 10:19:46 2017 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 8408BD8892D for ; Thu, 22 Jun 2017 10:19:46 +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 7019475C9D for ; Thu, 22 Jun 2017 10:19:46 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 682F0D8892A; Thu, 22 Jun 2017 10:19:46 +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 6669CD88927 for ; Thu, 22 Jun 2017 10:19:46 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org (portscout.ysv.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 1780575C98 for ; Thu, 22 Jun 2017 10:19:46 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.ysv.freebsd.org ([127.0.1.123]) by portscout.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id v5MAJjIg088023 for ; Thu, 22 Jun 2017 10:19:45 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v5MAJjPb088022; Thu, 22 Jun 2017 10:19:45 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201706221019.v5MAJjPb088022@portscout.ysv.freebsd.org> X-Authentication-Warning: portscout.ysv.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, 22 Jun 2017 10:19:45 +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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 10:19:46 -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 ------------------------------------------------+-----------------+------------ lang/js_of_ocaml | 2.5 | 3.0.0 ------------------------------------------------+-----------------+------------ 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 22 12:15:04 2017 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 2C0B9D8B43B for ; Thu, 22 Jun 2017 12:15:04 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::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 DC083792B1 for ; Thu, 22 Jun 2017 12:15:03 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: by mail-ua0-x22e.google.com with SMTP id 70so15024187uau.0 for ; Thu, 22 Jun 2017 05:15:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=zICKryFFL5ZCL6D9mBFRDI6B2YW3cVMnmsdCFtk0FQU=; b=TkZ5ArMnK7LkH7jBAoudfhCBdWqZlZjTDO+C4+bkP0jt0YGLM21ZPS3pc9yBrQecOe YVzIgszx6pSfF0YCXQonJMtx7Ch/90YrchTnC/cc91RiyBTEWSlVbHqzjKENiyQebKRo rmHfS2P69b6lkNJu7najKSByb53WLC9f7Se0DV2U22Dr7t+4oBoN1znkbFs3kT4kBI5J 4G4fu7OO25M6zkNLfukrOfD7rqEQG5QRejaTGK4r4Y54lmGokRSJBGr4qfnP8x8gKGAA K7LI3vR4nRxWXt7m3HSuaXRw2WMBBBJztu3rpRuBKPikRdOVYh5jUwp49vNK6/5VOtMx Y3FQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=zICKryFFL5ZCL6D9mBFRDI6B2YW3cVMnmsdCFtk0FQU=; b=JlrygYa7gkD/fvlfz7+ySkFLM9t4trHi9f4rO4NcAFEedV6YPZaRaUaKa9CDMu5IkX HVpajzKjz5uCRkaYyiNjR6mKJFvuVUwa/caPtrhNe7UaZMnxisqJK/eKqP36x6utPEd1 AwMupmDqNuZKCL9FxVwa8AUlCagQeUNpybK1cU/dMDMLRTms6KyJMI5a6sdaDg91FpNV ulU5qwSwHBoW4hB0nhmWo8Nr/RMiyOk86Co0xRoRxJKXcIL+vJiKpFMzWss5xIIlQCGS GUtYqBaJprsYnYsiMtu1vMpZHoqzP0guwqtC1ViV/hlilk2pu+NcmE+Yb+RrCgIz80vf MFBw== X-Gm-Message-State: AKS2vOx57xQwhQ4xgMoyhNbFTXAzPHkQlV1jgXzOVe4bZ4VWYoILkGX9 FwibHQD0Q75ChbBh6rQhWO+Iyko2d3E8 X-Received: by 10.176.69.100 with SMTP id r91mr2303915uar.153.1498133702703; Thu, 22 Jun 2017 05:15:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.178.70 with HTTP; Thu, 22 Jun 2017 05:15:02 -0700 (PDT) From: David Demelier Date: Thu, 22 Jun 2017 14:15:02 +0200 Message-ID: Subject: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 12:15:04 -0000 Hello, Today I've upgraded one of my personal FreeBSD servers. It's running FreeBSD 11.0 for a while. While I use quarterly ports branches, I usually update my ports tree before installing a new service and I faced some troubles: www/node was updated from 6.x to 7.x: unfortunately my etherpad instance is not compatible with 7.x. I needed to install www/node6. devel/mercurial was updated to 4.2: redmine has a small issue making repository browsing unavailable. I temporarily downgraded Mercurial to 4.0. I think the current process of having rolling-releases packages makes unpredictable upgrades as we have to manually check if the upgrade will be fine or not. When a user installs FreeBSD 11.0 on its system, it probably expects that everything will work fine until a next major upgrade like 12.0. That's why I think we really should implement branches for a specific FreeBSD version. When FreeBSD 12.0 is released, we should create a ports branch that will contains only fixes (such as security advisories, crash fixes and such). No minor or major upgrades until a new 13.0 version is released. This is the only way to make safe upgrades. If user think that a software is too old (since we have long delay between major releases) it can still use the default tree at its own risks. Additional benefits of having a ports tree by version: you don't need to have conditionals in ports Makefiles (how many ports check for FreeBSD version? a lot). Any comments are appreciated. Regards, -- Demelier David From owner-freebsd-ports@freebsd.org Thu Jun 22 12:18:57 2017 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 CA603D8B4E5 for ; Thu, 22 Jun 2017 12:18:57 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5CE1B793CA; Thu, 22 Jun 2017 12:18:57 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 9C2BD13CB9; Thu, 22 Jun 2017 12:18:56 +0000 (UTC) Date: Thu, 22 Jun 2017 14:18:56 +0200 From: Baptiste Daroussin To: David Demelier Cc: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="zzyr7xu5gmkw3kyi" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170609 (1.8.3) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 12:18:57 -0000 --zzyr7xu5gmkw3kyi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 22, 2017 at 02:15:02PM +0200, David Demelier wrote: > Hello, >=20 > Today I've upgraded one of my personal FreeBSD servers. It's running > FreeBSD 11.0 for a while. >=20 > While I use quarterly ports branches, I usually update my ports tree > before installing a new service and I faced some troubles: >=20 > www/node was updated from 6.x to 7.x: unfortunately my etherpad > instance is not compatible with 7.x. I needed to install www/node6. >=20 > devel/mercurial was updated to 4.2: redmine has a small issue making > repository browsing unavailable. I temporarily downgraded Mercurial to > 4.0. >=20 > I think the current process of having rolling-releases packages makes > unpredictable upgrades as we have to manually check if the upgrade > will be fine or not. When a user installs FreeBSD 11.0 on its system, > it probably expects that everything will work fine until a next major > upgrade like 12.0. That's why I think we really should implement > branches for a specific FreeBSD version. >=20 > When FreeBSD 12.0 is released, we should create a ports branch that > will contains only fixes (such as security advisories, crash fixes and > such). No minor or major upgrades until a new 13.0 version is > released. This is the only way to make safe upgrades. >=20 > If user think that a software is too old (since we have long delay > between major releases) it can still use the default tree at its own > risks. >=20 > Additional benefits of having a ports tree by version: you don't need > to have conditionals in ports Makefiles (how many ports check for > FreeBSD version? a lot). >=20 > Any comments are appreciated. As usual with such proposal, where do you find the manpower to handle the n= umber of branches required (the quarterly branches are already hard to maintain, = it is only one branch). What do you do for security fixes: backport to the stable version? who is backporting to software not maintained upstream any more in the given branc= h? Bapt --zzyr7xu5gmkw3kyi Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAllLta0ACgkQY4mL3PG3 Plo7mg//T6StwC/1xXbg/D0LiitCft4k6Ei2MHYvY8FcV2uoHU7SKEQ/iA13BnvE yILZWpf/OEwJ++Ae7WRQI+c2wG9ChTjOvVqMvlAlhJ3neogus6cCU8f9O1Kn1i21 arSIdQjxUSkfgtlRhJUv1LYd/li5EBOMPCnBtKkxWQM8Mxv+6h+qSrA3vJ87WBcG DuVBpl9ahj6V3NHnIHXgSSQdSNw4hrMhaCBIiVgUN88LeClNojQ7U74z5O+x9WOg 8UAZLg19rlC0GN5aeVmMIaZUqH5dLj+9cz2ggm2ikpF+MMfrNi7LnLFucm72FVXO ig3OMD9E65mxIe1oGpL64mrWHj8Xw5zidoMk/ikBX+A9p6/bAh6/lNt1KmckF0v8 GSs6K916Kzm1W2bbOQ1S9BNMyBY9DE/BYgPLASIEVQzlVKpeZz2MqsbISKQ3T8rl ynfQ9wxOIwPLEgdv/8AkCdkl9qFCM5DxXGVrGg9j27GtdSo14weiTaNQO6QvU0J/ FBYae8yUA9pd2Iw+o9A1A1of+goqMhRpfcQvvm+ApikU9rDJmTmtcbIgqB78NZoZ cesuMqmOlSn12G9FjAnxj451K62bfziBkKVoQoJVTEVG+2dkGaiE6AmZe2b8Ryyf +OY4XgXtnAQ4eGTb7rxY05iXx4I+W+Voz2Jv/inPLzKObOs7gf8= =AxvN -----END PGP SIGNATURE----- --zzyr7xu5gmkw3kyi-- From owner-freebsd-ports@freebsd.org Thu Jun 22 12:21:00 2017 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 96AB7D8B628 for ; Thu, 22 Jun 2017 12:21:00 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (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 1931379623 for ; Thu, 22 Jun 2017 12:21:00 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: by mail-lf0-x236.google.com with SMTP id m77so9929017lfe.0 for ; Thu, 22 Jun 2017 05:21:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/VafnOe9C+BFfKnjPwlJDJ5SiKdk8uWkxXAlprC/Gtw=; b=szkPx1HbQsvkrF6isqeg/j9eHrmV9C6XwHeVHypJ16HtsIBxIipG6lqdgZm4P12vas k6eLtcK3rMPqzrL9P7/EzcXQGcalMM9vdthVHNn95Bs8FtefGh/mEzaOqvQJhORpS/6C Uwmb+QziVVIz8cWYxqhnb6K8wSDdfP6epGAoOyf8eEcRX+bgq3OdpzjmAJ+0sTm747Gz plQ7lU2tk+1UBN2ep8tpY5JxE5Zz+NnG0gpTCTc6nV3sYT236E9J4rJamaJQ9+qL82F2 3YFzWohDnYXrh7u8jnk8QFRX3KkcCoproyEMwrIFsDG3/RORvaKYRKMyYzLrDz9OfKu6 fYGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=/VafnOe9C+BFfKnjPwlJDJ5SiKdk8uWkxXAlprC/Gtw=; b=YwtASnKfdKq33LHVA1TexgsPN9MM7iVbgQFKdDHpILXHs08YXkwYvnYagQqqpxDAb5 0o1QxddV+T5hCGb2pmqVEg0XoTq/hiIUW4JnnavmUhEzw1HGzoJKfjVhAtcP7LXL4/qW Mmo2eWHq4YYGj3GtBtp38fqn95ViyWfkiQwqXYsR5GOc2vJrJjX+SILJPOm+ocLx+u6+ 7ZUORJNC88+lfvXfYrcYGPw4KRc0csEsJGlwpmAndMK8L2xQnZ9jFio5iPfmxsl7cN2z ydKLc2o4aQ6UA/QS03rumuyy19ZNrJ5cTJkaOmlifBQ7aPY6WewW0WHdZF+R/Tljx2Wh J5KQ== X-Gm-Message-State: AKS2vOwRxdcBTbWmh9MW+a+wNTdLfOrXLPHNsSUIUwcF4/FZGzCZBRQd Jj0ngc9syIkCWUTlzJSsCteYa3sTUw== X-Received: by 10.25.22.105 with SMTP id m102mr906091lfi.66.1498134058092; Thu, 22 Jun 2017 05:20:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.196.88 with HTTP; Thu, 22 Jun 2017 05:20:56 -0700 (PDT) Received: by 10.25.196.88 with HTTP; Thu, 22 Jun 2017 05:20:56 -0700 (PDT) In-Reply-To: References: From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= Date: Thu, 22 Jun 2017 14:20:56 +0200 Message-ID: Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: David Demelier Cc: FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 12:21:00 -0000 El 22 jun. 2017 14:15, "David Demelier" escribi= =C3=B3: Hello, Today I've upgraded one of my personal FreeBSD servers. It's running FreeBSD 11.0 for a while. While I use quarterly ports branches, I usually update my ports tree before installing a new service and I faced some troubles: www/node was updated from 6.x to 7.x: unfortunately my etherpad instance is not compatible with 7.x. I needed to install www/node6. devel/mercurial was updated to 4.2: redmine has a small issue making repository browsing unavailable. I temporarily downgraded Mercurial to 4.0. I think the current process of having rolling-releases packages makes unpredictable upgrades as we have to manually check if the upgrade will be fine or not. When a user installs FreeBSD 11.0 on its system, it probably expects that everything will work fine until a next major upgrade like 12.0. That's why I think we really should implement branches for a specific FreeBSD version. When FreeBSD 12.0 is released, we should create a ports branch that will contains only fixes (such as security advisories, crash fixes and such). No minor or major upgrades until a new 13.0 version is released. This is the only way to make safe upgrades. If user think that a software is too old (since we have long delay between major releases) it can still use the default tree at its own risks. Additional benefits of having a ports tree by version: you don't need to have conditionals in ports Makefiles (how many ports check for FreeBSD version? a lot). Any comments are appreciated. Regards, CMIIW but when similar approaches come up, one of the reasons to not do it is man power. -- Demelier David _______________________________________________ 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 Thu Jun 22 12:22:02 2017 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 4C7AAD8B89F for ; Thu, 22 Jun 2017 12:22:02 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 162BD797B4; Thu, 22 Jun 2017 12:22:02 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 7299E13DA5; Thu, 22 Jun 2017 12:22:01 +0000 (UTC) Date: Thu, 22 Jun 2017 14:22:01 +0200 From: Baptiste Daroussin To: David Demelier Cc: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170622122201.cdnwly6qcev3eqav@ivaldir.net> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="lxtwp5reqvco6d2m" Content-Disposition: inline In-Reply-To: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> User-Agent: NeoMutt/20170609 (1.8.3) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 12:22:02 -0000 --lxtwp5reqvco6d2m Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 22, 2017 at 02:18:56PM +0200, Baptiste Daroussin wrote: > On Thu, Jun 22, 2017 at 02:15:02PM +0200, David Demelier wrote: > > Hello, > >=20 > > Today I've upgraded one of my personal FreeBSD servers. It's running > > FreeBSD 11.0 for a while. > >=20 > > While I use quarterly ports branches, I usually update my ports tree > > before installing a new service and I faced some troubles: > >=20 > > www/node was updated from 6.x to 7.x: unfortunately my etherpad > > instance is not compatible with 7.x. I needed to install www/node6. > >=20 > > devel/mercurial was updated to 4.2: redmine has a small issue making > > repository browsing unavailable. I temporarily downgraded Mercurial to > > 4.0. > >=20 > > I think the current process of having rolling-releases packages makes > > unpredictable upgrades as we have to manually check if the upgrade > > will be fine or not. When a user installs FreeBSD 11.0 on its system, > > it probably expects that everything will work fine until a next major > > upgrade like 12.0. That's why I think we really should implement > > branches for a specific FreeBSD version. > >=20 > > When FreeBSD 12.0 is released, we should create a ports branch that > > will contains only fixes (such as security advisories, crash fixes and > > such). No minor or major upgrades until a new 13.0 version is > > released. This is the only way to make safe upgrades. > >=20 > > If user think that a software is too old (since we have long delay > > between major releases) it can still use the default tree at its own > > risks. > >=20 > > Additional benefits of having a ports tree by version: you don't need > > to have conditionals in ports Makefiles (how many ports check for > > FreeBSD version? a lot). > >=20 > > Any comments are appreciated. >=20 > As usual with such proposal, where do you find the manpower to handle the= number > of branches required (the quarterly branches are already hard to maintain= , it is > only one branch). >=20 > What do you do for security fixes: backport to the stable version? who is > backporting to software not maintained upstream any more in the given bra= nch? >=20 > Bapt Oh and of course the day you freeze a branch you will have complain about "= how do I get python 3.8 on freebsd 11.0" Bapt --lxtwp5reqvco6d2m Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAllLtmgACgkQY4mL3PG3 PlpVbw/+L12cQigcuDiizgI2V6gCzwv9qoh4oyRWHgZAi/iBk4fBNonuB3TnrCZ8 9kluoeGRQ00fjL5Mwbdjr7nxS30hikanJuIZWvyBiqe7JCybEJsV3wdGUsi7N2aV 19G9Fxa85Gt1uZhEJm4hZPtEOpFtqY170DGeKAX7ZprLdZx6Wj6G2clqS7kd7fHA wcyo2WFzrHZpM0D+vqD9m9yLhWS9Z/0vGzFfqIJ7Prn6P/bm0s/Afil466dEzrE8 npKJJ4wikAheNRZQyq4MunCwm1DBjAga5Zh3/9Sy38Cxw7m3cD8V2WqZVS6k6AMq s/sAdiJm8zav8bv0zsiqJu1oZLA60uOIFNCK0uEckZvYZPHk6P4H1Oixnk8mrMwL RzadGNbP0QOhvULn1b9RMswTVxB1HGX+BFPzpdOaJASRYATkMljnOJVuat2Py2Dh cGmqWHyXcsgxr6YDGW+qciWTOwd8JXRafW/3tEwsypSmALvSf5efdmzZZAN4zpwo Zmp2vtvo2iXWdguDjHBrGk0WhLgFvxSK2Acj3zP1aaVvwEDNm+bP//6q6E0DdhYe 6sfXBX11ZDMy0BnQMNxUsvVAJACR61CYhrqhKdeSCmLJpojTIBzINgKHwDQLOWcX aD7Mvik0hMqKNYwY9JKkD421lsbUYLweENzX8S0PUCb1JY9/sfk= =Q87a -----END PGP SIGNATURE----- --lxtwp5reqvco6d2m-- From owner-freebsd-ports@freebsd.org Thu Jun 22 12:39:28 2017 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 2DCC7D8BBE6 for ; Thu, 22 Jun 2017 12:39:28 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: from mx.irealone.hr (mx.irealone.hr [IPv6:2a01:4f8:212:2d90::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 EB38279E39 for ; Thu, 22 Jun 2017 12:39:27 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mx.irealone.hr (Postfix, from userid 58) id 02EC34EB2; Thu, 22 Jun 2017 14:39:16 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on postfix.xoth.irealone.hr X-Spam-Level: X-Spam-Status: No, score=-101.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, LOCAL_WL_002 autolearn=ham autolearn_force=no version=3.4.1 Received: from mail.irealone.com (unknown [10.0.0.10]) by mx.irealone.hr (Postfix) with ESMTP id 918BC4EAC for ; Thu, 22 Jun 2017 14:39:16 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 22 Jun 2017 14:39:16 +0200 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Organization: Acheron Media In-Reply-To: References: Message-ID: X-Sender: vlad-fbsd@acheronmedia.com User-Agent: Roundcube Webmail/1.2.5 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 12:39:28 -0000 On 2017-06-22 14:15, David Demelier wrote: > > While I use quarterly ports branches, I usually update my ports tree > before installing a new service and I faced some troubles: What works best for us, to keep a stable production, is to track the HEAD with svn. That way we can pre-empt changes locally, test, and deploy into production, or block upstream changes by keeping some older version until something else is fixed. Otherwise as others have suggested, the problem is manpower and backporting patches. Although, in my experience having run both Ubuntu LTS and FreeBSD in production, when a maintainer, who is not the developer of some software, tries to backport patches, it often results in regressions and even more problems introduced. So I'd rather use rolling release directly from the developers with minimal local changes. A rolling release with clearly marked stable versions kept longer around (ala Gentoo), is the best way to solve the problem with ports without introducing extra manpower and the need to backport. -- Vlad K. From owner-freebsd-ports@freebsd.org Thu Jun 22 12:52:44 2017 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 100E1D8BFCE for ; Thu, 22 Jun 2017 12:52:44 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-ua0-x22c.google.com (mail-ua0-x22c.google.com [IPv6:2607:f8b0:400c:c08::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 A4F167A70C; Thu, 22 Jun 2017 12:52:43 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: by mail-ua0-x22c.google.com with SMTP id 70so16115892uau.0; Thu, 22 Jun 2017 05:52:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3LTTs0JWgoc4yj2xbQXk04QEe3yYRoINxHR3VujTSxI=; b=vPVhqVuGBY2dcySYPnRbJK7sj7mR1z9DINNFcMkojasmV6k1UoGJUYbud5KdnjqMDN Hl36SW03T6lxabxC+O5cVmB1d7EQm9UmJIbmYvTHmed2/eqEDoc7VqRmI5I2dQvATlcF /E+hjfjuiKoCSrMwQ43mfRpWm/6mpSxIS1IVlfEp5hVk4hjt5DsKjY0Q3EnfGfJEmuAQ NGBlo9A2U3mn87374g+oMtYo3vS+If7cxmKTZcGfxp9yIIQ4ijXmRoeS6Gp+dJx4vlqr jMR1iOzN4IDlBl5nQiCmWUZmawi0C0pM9GHRHX5n6PpwHA4hPNFO+TaFbGUTb++cYS8w 3jIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3LTTs0JWgoc4yj2xbQXk04QEe3yYRoINxHR3VujTSxI=; b=kNZhc07XaD90/tkBiuJYH8/+0tUL90R1fTKrIeakO4D7KWCgVexQEivsVTijoC0xKB qED1FPlI5TJ2lqttMEH/pLEWWptcgX0cXUd84NTJ2LNtGMvRMgD+PCkrHD9tPok1jksE ay6B3MLu8Ul/iNkVr/YYRBd3XINt5Dg8P7rWY7uIO7kzdgi2pB58GYZgUpZYy3WMIU5+ kwCAt2MOlu6AlZEICNeHOyYTUlJcgLJBuHFkUY1MBUWl+/qR7KQBKlnN2161WWXJ57z3 ErjILvZSVa+vGUhu1uaLWpo9xtDVhdwjAq0BvH2J2i4iKB00P3P6aRHSgq5/wFYh277e Cdww== X-Gm-Message-State: AKS2vOwNVh7SYYHx7cAN6NoNHXuwIEG8vz+nYyGopgfiNfwSkqyuU4vQ IhIr/MtKtpIZMrCVdxpWFoyhCog2lA== X-Received: by 10.176.2.22 with SMTP id 22mr2351376uas.0.1498135962565; Thu, 22 Jun 2017 05:52:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.178.70 with HTTP; Thu, 22 Jun 2017 05:52:42 -0700 (PDT) In-Reply-To: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> From: David Demelier Date: Thu, 22 Jun 2017 14:52:42 +0200 Message-ID: Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Baptiste Daroussin Cc: freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 12:52:44 -0000 2017-06-22 14:18 GMT+02:00 Baptiste Daroussin : > On Thu, Jun 22, 2017 at 02:15:02PM +0200, David Demelier wrote: > As usual with such proposal, where do you find the manpower to handle the number > of branches required (the quarterly branches are already hard to maintain, it is > only one branch). I think release branches won't need much maintainance as unless a security issue is found, no updates are necessary. > What do you do for security fixes: backport to the stable version? who is > backporting to software not maintained upstream any more in the given branch? > I would never backport anything. It's quite the opposite. If a security flaw is discovered in let say: OpenSSL; then we check if it's present in the release branch and top port in quarterly then HEAD if they are also affected by this issue. Regarding your second mail, the question may also apply on HEAD :-) Cheers, -- Demelier David From owner-freebsd-ports@freebsd.org Thu Jun 22 13:01:01 2017 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 ED904D8C0C8 for ; Thu, 22 Jun 2017 13:01:01 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.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 D74677A8C0 for ; Thu, 22 Jun 2017 13:01:01 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dO1if-000AwO-Sp for freebsd-ports@freebsd.org; Thu, 22 Jun 2017 07:00:21 -0600 Date: Thu, 22 Jun 2017 07:00:21 -0600 From: The Doctor To: freebsd-ports@freebsd.org Subject: NEW APR/APR-Utils Message-ID: <20170622130021.GB41229@doctor.nl2k.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 13:01:02 -0000 ARR and APR-utils are up to 1.6.X Please update ports accordingly. -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism Talk Sense to a fool and he calls you foolish - Euripides From owner-freebsd-ports@freebsd.org Thu Jun 22 14:05:24 2017 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 848DBD8CF6B for ; Thu, 22 Jun 2017 14:05:24 +0000 (UTC) (envelope-from scratch65535@att.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 661B07C368 for ; Thu, 22 Jun 2017 14:05:24 +0000 (UTC) (envelope-from scratch65535@att.net) Received: by mailman.ysv.freebsd.org (Postfix) id 627B3D8CF6A; Thu, 22 Jun 2017 14:05:24 +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 603FED8CF69 for ; Thu, 22 Jun 2017 14:05:24 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm2-vm10.access.bullet.mail.bf1.yahoo.com (nm2-vm10.access.bullet.mail.bf1.yahoo.com [216.109.114.83]) (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 0CEFC7C367 for ; Thu, 22 Jun 2017 14:05:23 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1498140204; bh=IIQyIe3S+owQQPd0Sm1xJ81ycmNRbxubuuFeOMoeFVY=; h=From:To:Subject:Date:References:In-Reply-To:From:Subject; b=I26ryp3Cc6lpx7mgkOmjlUdDr0Y2zAy9gf04HfnbhZjLy6Urihh3swwDOsfnuj68N5U5Qr6n/OSgWqxvdy3wnZvcl8TILMbGahQdEedTswk24q8ljlzSd+DE4Xvkm7jFYuzwRJ+qy42g8Z/I289A4TNM4bkA3cLn/9nloVm1Xt8= Received: from [66.196.81.164] by nm2.access.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 14:03:24 -0000 Received: from [98.139.221.158] by tm10.access.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 14:03:24 -0000 Received: from [127.0.0.1] by smtp118.sbc.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 14:03:24 -0000 X-Yahoo-Newman-Id: 707984.54945.bm@smtp118.sbc.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 9Q0C8jAVM1mlPOPHFT3LmoH97fRU488cLIu5lfJMDCNpnzI OOxRMayE2OFXa_wtZN0oS7Uo6pO3Q4giSI3lVqixBkGhltOCWE0lXHSNH0Hf rvgxZX7a8jS9Uu0hjLUaYJGLmOpZQ1_dJTNY2JbsUfBR6b6kC4ALqpUpvbJE SwnIpewXdqMAovclmfd2iVLldgsvFIwqiy6aq9gMpdoVf8yCG4G_Hidrzmax EvY0ACcg98BrHN1oIOrQ8e1mmKWiqzyZyYtPpbtStVQOcMuH3e2JCNHzQBSL dUpQ8A7DsK9pxLcqtEomYAKoXk5_A9dvZcOATAgQH75I00Se6EziX0nh3e60 AcBmxCGNb6PhiZBAAzHieCF6Y9f.1u_PCFgPWrk3zj7Em0NF1JD_Nsq5tsoW .8kICqeTct6rMyVj62qL25GcD5ZFvdv_IDLZ6OyMYFbgGDlxQqfQvWi_mZj6 7gmqcoiv.IIrNIy3P4W3CMRwuR42CgUJbPtW68dCqOIMaiz_YVPwPCKDfEOW ON.qRTn9SkpObzLliI4PFlAdn_p8an.bx04pZuMZv3A9f93CjZBhTtQ-- X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: freebsd-ports Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Date: Thu, 22 Jun 2017 10:03:33 -0400 Message-ID: References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> In-Reply-To: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> 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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 14:05:24 -0000 [Default] On Thu, 22 Jun 2017 14:18:56 +0200, Baptiste Daroussin wrote: >As usual with such proposal, where do you find the manpower to handle the number >of branches required (the quarterly branches are already hard to maintain, it is >only one branch). Please help me out here, Baptiste, because I'm apparently missing *something*. Out in industry, if you haven't enough people to do a new high-quality release every N months, and you can't get a headcount increase, then you cut the release schedule. Can't do 4 releases a year? Cut back to 2. Still too many? Cut back to 1. The alternatives to cutting the schedule are that (a) people begin burning out and quitting, (b) quality drops and your customer base begins abandoning you, or (c) both of the above. Why don't the same choices apply here? What am I missing? From owner-freebsd-ports@freebsd.org Thu Jun 22 14:16:45 2017 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 739CFD8D306 for ; Thu, 22 Jun 2017 14:16:45 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 5E5127CA7B for ; Thu, 22 Jun 2017 14:16:45 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5DB56D8D305; Thu, 22 Jun 2017 14:16: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 5D570D8D303 for ; Thu, 22 Jun 2017 14:16:45 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3CA487CA7A; Thu, 22 Jun 2017 14:16:45 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 6665015387; Thu, 22 Jun 2017 14:16:44 +0000 (UTC) Date: Thu, 22 Jun 2017 16:16:44 +0200 From: Baptiste Daroussin To: scratch65535@att.net Cc: freebsd-ports Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170622141644.yadxdubynuhzygcy@ivaldir.net> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="wfxmi5gdbp7oaui2" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170609 (1.8.3) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 14:16:45 -0000 --wfxmi5gdbp7oaui2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 22, 2017 at 10:03:33AM -0400, scratch65535@att.net wrote: > [Default] On Thu, 22 Jun 2017 14:18:56 +0200, Baptiste Daroussin > wrote: >=20 > >As usual with such proposal, where do you find the manpower to handle th= e number > >of branches required (the quarterly branches are already hard to maintai= n, it is > >only one branch). >=20 > Please help me out here, Baptiste, because I'm apparently missing > *something*. =20 >=20 > Out in industry, if you haven't enough people to do a new > high-quality release every N months, and you can't get a > headcount increase, then you cut the release schedule. Can't do > 4 releases a year? Cut back to 2. Still too many? Cut back to > 1. >=20 > The alternatives to cutting the schedule are that (a) people > begin burning out and quitting, (b) quality drops and your > customer base begins abandoning you, or (c) both of the above. >=20 > Why don't the same choices apply here? What am I missing? We only have 1 quarterly branch at the time :) The model with one branch per release will bring it to way more with a maintenance window way larger (actually it is 3 month making the quarterly relatively easy to maintain) Best regards, Bapt --wfxmi5gdbp7oaui2 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAllL0UcACgkQY4mL3PG3 Plow9xAAp/v4arZebWoF4U4Y97WyymtWdGhcgIJ5NMgeqoCGELjOggVtNP/8Akd4 3a1JtXnTNezZYmthF4EpoEN/BXjUwTFjMZQrARyk6u+Kf010Mszj2Wb93lJo9vy3 EBy/ewMZKQvpYXSMc7a9FS7Iw+aV/xZbyM/tg01ka/DVqwbN0Po1rrWmJofOcvpg 3+Lt/iKHFBaM6RpD3CHUR+YaS0NfBluo+0+CqKwCEPysrXHQnGk73aU2E/kOIK4D 3KMbxjwuerkTbWwzU5RLy+sn4CqJmAeyc8B5Nlb3WOnnV+6XEU+Mvt9lYKYYkwQl FqYMqkS2ZD8J4//av+3WrZoAo1rdNURqllTr3tPNFvZv81qcwEqFyKZciOHBGd/1 4XEIWq/oVsaJIfbCJ8mLHfhlArCn2DBZlgZMgdfFndzjV6Hg3UiYDzolUfW1HbuF FvrSTlJApiwIqDxu4wUagONmvHdApOp2vwP/CXVIaM4ZDq/R27heuECRCESBtEXT VcWcBO2UDKN2iIzGAc5kn7uG2PIbM/0N0NpLHcjIbRpFwhq/Tw2lZAewoMFQP3ll KG/v50ttq3UzWG1D3mytp7O5X4G9lDUQcN95LgacKwqXL4GCJlvB37TjrGj5RoP9 ikvKNaBH23LKpYXXIV2tGTsP4BATMroRmLD1aXDn6uwIC8o10f8= =1Zte -----END PGP SIGNATURE----- --wfxmi5gdbp7oaui2-- From owner-freebsd-ports@freebsd.org Thu Jun 22 14:28:13 2017 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 694CDD8D66A for ; Thu, 22 Jun 2017 14:28:13 +0000 (UTC) (envelope-from demelier.david@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 46EFA7CF65 for ; Thu, 22 Jun 2017 14:28:13 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 435BFD8D669; Thu, 22 Jun 2017 14:28:13 +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 42F09D8D668 for ; Thu, 22 Jun 2017 14:28:13 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::230]) (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 00B0F7CF64; Thu, 22 Jun 2017 14:28:12 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: by mail-ua0-x230.google.com with SMTP id g40so19143889uaa.3; Thu, 22 Jun 2017 07:28:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SMGWioU9cj06Lzkg/Lox2rCv/Qr1Y3T+BB80iw3XKw4=; b=oK4VoS5N8953G898EF9jT3TLFax26+neYxFa+4zEPhBuLxhpRdoBZYIJUMA8Iamusb mixWHhAkY3/OJlnctvmORbQRVaH9srLK0pglUzUGxrlavyRw5TV4w1jAPsl520CsTqJO jX+ymYkP/Xvy36ECg7s0+YHkrE2OONyb31k9v2YulM5P1MT8Hk6fNFYMp7pWK6dcWAJx ZOznFw07cHkbL3DQJxokoaMkqOL02YWHs7KN0IN+Cm84J+3Jep3r7ss1H6yGRQUpx3mG OaQSMMsgO1T9y9HQqSGFSf5yU56Etmyhf4NOnvdb8OzmOsaRfKOjugZ3CbSnIePVjJ6D jDHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SMGWioU9cj06Lzkg/Lox2rCv/Qr1Y3T+BB80iw3XKw4=; b=TjKg+Z9NwnkRcmzzPuoPY2Q5LL744PJa5f1LY0Bg1r1AMVOyMEHW7ybBJlMTzOhPN0 GIFb5+/rzBPR7DKTkplO82HAwyp8yPVtdlhe6K0gqluom64MleA8IX7HwyrfichVZM06 6OsLR9oJ568sLuMR5g6dALd/xmvqB8+AOWK4zB2wpONmqzyaRwHZ4EjTQpcEj7/KgSvB U2BxGbvJJ4Pn/X+PoESoAsbamh9Lz0DI+uUugemve2z9PpCQybgZx7kLyYlw+d84aANC HrkUpUqkNLQQLo7eHQig+KFVzikmBJwQsXK2gIB6Jo6izSXanDSluDbn/NQgRxHZdH0u g4Tw== X-Gm-Message-State: AKS2vOxpMhvNwe2lpdWvjksdVRKU1nWjehz2QDX4pQamNF8cNQmW4UL5 MCNMSREMgJgBL6rfWAKS0Tl6y3VlGw== X-Received: by 10.159.36.54 with SMTP id 51mr2272061uaq.133.1498141691550; Thu, 22 Jun 2017 07:28:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.178.70 with HTTP; Thu, 22 Jun 2017 07:28:11 -0700 (PDT) In-Reply-To: <20170622141644.yadxdubynuhzygcy@ivaldir.net> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> From: David Demelier Date: Thu, 22 Jun 2017 16:28:11 +0200 Message-ID: Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Baptiste Daroussin Cc: scratch65535@att.net, freebsd-ports Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 14:28:13 -0000 2017-06-22 16:16 GMT+02:00 Baptiste Daroussin : > The model with one branch per release will bring it to way more with a > maintenance window way larger (actually it is 3 month making the quarterly > relatively easy to maintain) So after three months if you don't switch branch, you're outdated since bugfixes are not applied in old ones. Then we get back into the same trouble of major upgrades while the user just wanted to have security updates. -- Demelier David From owner-freebsd-ports@freebsd.org Thu Jun 22 14:39:07 2017 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 385A5D8DB75 for ; Thu, 22 Jun 2017 14:39:07 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (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 C0F8B7D62B for ; Thu, 22 Jun 2017 14:39:06 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from zero-gravitas.local (unknown [85.199.232.226]) (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 DD5F7C535 for ; Thu, 22 Jun 2017 14:39:02 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/DD5F7C535; dkim=none; dkim-atps=neutral Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> From: Matthew Seaman Message-ID: <775ba90e-a811-4cc8-a729-bdc0dad7774c@FreeBSD.org> Date: Thu, 22 Jun 2017 15:38:53 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="QMndI0ReTmjIFbm7pRU04EHUFxs0i9SVG" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 14:39:07 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --QMndI0ReTmjIFbm7pRU04EHUFxs0i9SVG Content-Type: multipart/mixed; boundary="JLqxmnnXNFb3MpKsn8CJl6j8KlCWJSH1K"; protected-headers="v1" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: <775ba90e-a811-4cc8-a729-bdc0dad7774c@FreeBSD.org> Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> In-Reply-To: --JLqxmnnXNFb3MpKsn8CJl6j8KlCWJSH1K Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017/06/22 15:03, scratch65535@att.net wrote: > Why don't the same choices apply here? What am I missing? Two things: 1) It's progress in the development of the FreeBSD base system that drives the release cycle. The general state of the ports does not exert much influence on release frequency -- nor should it. 2) Even if we could scrape up enough people to support however many branches you are proposing, remember they are all volunteers. It's hard enough getting people to maintain the existing quarterly branches as it is, and those are relatively short lived so that most merges from head are pretty trivial. People really aren't going to want to do essentially repetitive merges to branches where everything else is up to X years older than head. Which would make it both tedious and frequently difficult to do. Tedious and difficult generally means "you need to pay someone to do that". Which means you need a commercial setup to generate the money to pay all those wages. Which means you -- the end user -- get to pay for the provision of those specially maintained package sets. Now, if you think you have a viable business case for maintaining essentially a static snapshot-plus-security-fixes of the ports and supplying packages generated from it, by all means go ahead and try offering that as a commercial service. I doubt you'll succeed though -- a number of other people[*] have been down that path, and they usually give up fairly early because the market just won't support it at the mome= nt. Cheers, Matthew [*] These guys most recently: http://www.xinuos.com/menu-products/openserver-10 They're still going, but I haven't heard of much activity from them for the last year or so. --JLqxmnnXNFb3MpKsn8CJl6j8KlCWJSH1K-- --QMndI0ReTmjIFbm7pRU04EHUFxs0i9SVG 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 iQJ8BAEBCgBmBQJZS9aFXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTni+wQAIrW5XF87qHWrrsSdadU3qzi IavK9zThc4ALsOaToyW5iiqD3TcvahlrP/90XSVu0uacuSMIjrj/DQdQ2wD7KwlL DekpnnDbgTlEwqJe44Dh/T3Nx1XwwlTdqVqfiaVFK4zxb3/zLG2rJuVUGY2T2dZU ZrWBzdVhpr6ptDnV49KLIGS80wI7fPSJ+/R9fix3RQ/Vcy/TKHnEcZtli6nvcWIP 4nm/254+Peq4QxfpukbJj/dhcbMVZL8pn7z10dQM5r915LaSbVjVobe+efmEJSM4 YOPENahLV5nzShLfx9x3oH6xunG2vHrl21DBLGoO4AVmu9Zo1IlsRRcnmgSBB1S3 ZHrbAGha2SmPbhwXKlQn3DdMq5EvOQN6qYMV5XR7101/+WF8/VdFkZMQ7/kdZvzi lPedsK+ATgeHypg1N1yDYe+gQvYcVRVOOrXoCUmX24MGKmwJX17/DpMIXiCyE0Dq +xxYWhvVerurhqfhdof/PYOeNxoJjYvYsuKensF/XFJuSw+cF3Ii+NF8D0LrbErG oDFvDMLIzQcsL3DrD7dc1zS3cCtG4AlBYeXLxYOhKf80JvVUn2bZpOleFtrlO9GG KBy95cpVJMTubhmCE94bVzb/Jp4Qng31zCLCjPKAoNJ3ZtBVWk3kzGrQ6Wi6ED3Q MDLXb6bLh+cOHO4WpRQy =l/ZF -----END PGP SIGNATURE----- --QMndI0ReTmjIFbm7pRU04EHUFxs0i9SVG-- From owner-freebsd-ports@freebsd.org Thu Jun 22 15:20:52 2017 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 BC4F3D8E5DD for ; Thu, 22 Jun 2017 15:20:52 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (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 44FEA7E846 for ; Thu, 22 Jun 2017 15:20:52 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: by mail-lf0-x230.google.com with SMTP id p189so14586721lfe.2 for ; Thu, 22 Jun 2017 08:20:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=/Vukgc3u5+4MhepbFeQwCotPBMb+W/csJFOImo4s9og=; b=A/qFz3jFZZohYFFJVUzvGdfUNzgkAhVG4k+fJuuthFdy3rLM4GpcA25fKJ4+4YmMYj STf6ZvEN/C38wOJzlz0/WqdaiR0FL+ze8loQH8J+Ficj7Oy7DN2TDaTZdHvt01nSA4hB tITjpgI3j6WwlsGmal2Uxn+z2u5wKhq3xIgjm2GUTqAcv54dMaRZ+71QQa0JOobVa8hm LZRrHwnEa7OhTg+dBREfezN5zl9mGMhWuaKgjarv/8xRlqWyyRsbXF+V/pulOLG0YJUw PlcJanH+mZzohktPUnc0cPUrU7tO16TWU5ixxEpur/7/YzNoHvriUuTwUFQ5vhPN0+OK VvKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/Vukgc3u5+4MhepbFeQwCotPBMb+W/csJFOImo4s9og=; b=AGDI416YqdjGC9yYTGZSmaml98TdMI11WPcRIoXPI93uu+V5iDmyUblGhhAmNTLAiH HTqCfTFe3OwqtlPhgCpqxbiENIYZEQrCn3FS+78GQ7KAbVX599iCIaIZnDr/zDJ92WuR k81lIAzhYUMRGM6GNVp7npEKGfAdMyodt0O15SGfuzK80UlGSuo1OBqI6hSQwinmkj1U pajtycHs5rRVmoBZ7ESAxwyfXWJcXmeqjPWBoyvjjtq9XOp0/iXtqdHZBqdq5+4qzkqI gF3WRqV2mPB++04RVF+yFo4vR9m8oFF4h2uQmLZH4abA3CQhEyGfYKhENJr1orwONNPk 4nhA== X-Gm-Message-State: AKS2vOz1XGL1fJAYX6lQLrFmbqRbKZFM2FSubG2kGfY8v5IrKGgbtioX jjHEvbYT7o1DnXIjwOfyDx6Np3sGaM+2 X-Received: by 10.25.162.83 with SMTP id l80mr1276216lfe.68.1498144850072; Thu, 22 Jun 2017 08:20:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.196.88 with HTTP; Thu, 22 Jun 2017 08:20:49 -0700 (PDT) From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= Date: Thu, 22 Jun 2017 17:20:49 +0200 Message-ID: Subject: PR needs care To: FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 15:20:52 -0000 Hi, Can anyone have a look at this? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220212 Thanks in advance. From owner-freebsd-ports@freebsd.org Thu Jun 22 15:25:45 2017 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 29A66D8E795 for ; Thu, 22 Jun 2017 15:25:45 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cdptpa-oedge", Issuer "cdptpa-oedge" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E49757EB75 for ; Thu, 22 Jun 2017 15:25:44 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from [65.186.81.207] ([65.186.81.207:48922] helo=raspberrypi.bildanet.com) by cdptpa-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id D3/71-10880-171EB495; Thu, 22 Jun 2017 15:25:37 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1dO3zE-0000ry-Om for freebsd-ports@freebsd.org; Thu, 22 Jun 2017 11:25:36 -0400 Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> From: Baho Utot Message-ID: <8e69aff9-4288-fe1e-53df-83a0d74fbe82@columbus.rr.com> Date: Thu, 22 Jun 2017 15:26:39 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-RR-Connecting-IP: 107.14.168.6:25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 15:25:45 -0000 On 6/22/2017 10:03 AM, scratch65535@att.net wrote: > [Default] On Thu, 22 Jun 2017 14:18:56 +0200, Baptiste Daroussin > wrote: > >> As usual with such proposal, where do you find the manpower to handle the number >> of branches required (the quarterly branches are already hard to maintain, it is >> only one branch). > Please help me out here, Baptiste, because I'm apparently missing > *something*. > > Out in industry, if you haven't enough people to do a new > high-quality release every N months, and you can't get a > headcount increase, then you cut the release schedule. Can't do > 4 releases a year? Cut back to 2. Still too many? Cut back to > 1. > > The alternatives to cutting the schedule are that (a) people > begin burning out and quitting, (b) quality drops and your > customer base begins abandoning you, or (c) both of the above. > > Why don't the same choices apply here? What am I missing? > _______________________________________________ > I am looking at OpenBSD to replace FreeBSD. They have a more relaxed update schedule and that fits with what I need. I am looking for a system that is very stable and doesn't do the upgrade path for the sake of it being newer. Having a "releng ports" version that goes with a releng version of the OS would be great by me. Linux from scratch does this and it works very well. Why not have the ports system mirror the OS system? Could it not be done by using branches in subversion? Of course if changed it would have to mature out a little. If the laptop that I have under testing pans out I be gone. From owner-freebsd-ports@freebsd.org Thu Jun 22 15:30:22 2017 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 67EC1D8E894 for ; Thu, 22 Jun 2017 15:30:22 +0000 (UTC) (envelope-from tz@FreeBSD.org) Received: from toco-domains.de (mail.toco-domains.de [176.9.39.170]) (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 315C97EC9F for ; Thu, 22 Jun 2017 15:30:21 +0000 (UTC) (envelope-from tz@FreeBSD.org) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id 027711AAF0E0; Thu, 22 Jun 2017 17:30:12 +0200 (CEST) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Baho Utot , freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <8e69aff9-4288-fe1e-53df-83a0d74fbe82@columbus.rr.com> From: Torsten Zuehlsdorff Message-ID: Date: Thu, 22 Jun 2017 17:30:10 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <8e69aff9-4288-fe1e-53df-83a0d74fbe82@columbus.rr.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 15:30:22 -0000 On 22.06.2017 21:26, Baho Utot wrote: > On 6/22/2017 10:03 AM, scratch65535@att.net wrote: >> [Default] On Thu, 22 Jun 2017 14:18:56 +0200, Baptiste Daroussin >> wrote: >> >>> As usual with such proposal, where do you find the manpower to handle >>> the number >>> of branches required (the quarterly branches are already hard to >>> maintain, it is >>> only one branch). >> Please help me out here, Baptiste, because I'm apparently missing >> *something*. >> >> Out in industry, if you haven't enough people to do a new >> high-quality release every N months, and you can't get a >> headcount increase, then you cut the release schedule. Can't do >> 4 releases a year? Cut back to 2. Still too many? Cut back to >> 1. >> >> The alternatives to cutting the schedule are that (a) people >> begin burning out and quitting, (b) quality drops and your >> customer base begins abandoning you, or (c) both of the above. >> >> Why don't the same choices apply here? What am I missing? >> _______________________________________________ >> > > > I am looking at OpenBSD to replace FreeBSD. They have a more relaxed > update schedule and that fits with what I need. Go ahead with whatever fits your needs. But since the ports-tree is a subversion repository it is really easy to maintain the status you want. I do this for various customer and my various server. > I am looking for a system that is very stable and doesn't do the upgrade > path for the sake of it being newer. Which has various downsides. I remember for example various linux LTS distros, which only apply security fixes. I discovered various bugs which stay there for years, because they are not security issues - they just hurt you daily. :D > Having a "releng ports" version that goes with a releng version of the > OS would be great by me. Linux from scratch does this and it works > very well. It really does not work well. In everyday situation this results in "heck we need a new server to get a new version of a needed software, because we need a new linux version". I regularly seeing admins setting up different Ubuntu versions, because at one you have PHP 7 and on the other MySQL 5.7, but not both at the same Ubuntu version. Greetings, Torsten From owner-freebsd-ports@freebsd.org Thu Jun 22 15:53:45 2017 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 AA480D8F221 for ; Thu, 22 Jun 2017 15:53:45 +0000 (UTC) (envelope-from scratch65535@att.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 8A4CB7FAF5 for ; Thu, 22 Jun 2017 15:53:45 +0000 (UTC) (envelope-from scratch65535@att.net) Received: by mailman.ysv.freebsd.org (Postfix) id 898ACD8F220; Thu, 22 Jun 2017 15:53: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 89213D8F21F for ; Thu, 22 Jun 2017 15:53:45 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm2-vm4.access.bullet.mail.bf1.yahoo.com (nm2-vm4.access.bullet.mail.bf1.yahoo.com [216.109.114.91]) (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 4596B7FAF4 for ; Thu, 22 Jun 2017 15:53:44 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1498146618; bh=O6P2G/aELLNt/+Uz2RuRh0DvEoAIqajHV1beqXaBMcA=; h=From:To:Subject:Date:References:In-Reply-To:From:Subject; b=2kd7O3YAcsgx6bWUhsll+wawDlqh741cf5Xkuxz4acG1rGRKz0NoD6/ITNGwh0akgYuy17H1aydOCTj0gblm5/k9bG8weQgbAdfHUG3EoI4TDYGFnYinqXSY++tirU9vRXyAVrLVEgEkYNets0OrcQHBAi5wads5buhLYubLWHA= Received: from [66.196.81.164] by nm2.access.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 15:50:18 -0000 Received: from [98.139.244.51] by tm10.access.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 15:50:18 -0000 Received: from [127.0.0.1] by smtp113.sbc.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 15:50:18 -0000 X-Yahoo-Newman-Id: 262593.29233.bm@smtp113.sbc.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: h30fGsUVM1nxFV.OzZuc6gAVmdRlndjca6AEYCDQFtJg9iW OQ0GyXhWBAFev3FaYRnnxece2B9A.qmHI6j27b9dk3VMRF3g7ygnVjkYGVJn chNoxmO.8e78GoAJB8p3uaHJ7XcZ_i4.VwuffMyqQgZIRNJVEPu1CHZot2Ob utgCO.N8EdoGToIn_JIr8gZaPvBQDRRui5B2BsZryPrfBtbr8jpfJ72jxfPI evfoWgKfecwO6TrnlljAMRXCReul5qPMN9eEUIF3ADbVnSAi2eEnasoi97mz vKpEIunYTLPcW93YIX2cG29qS_ATufw3SzRO5ougrNUNbzA4s7plW73ea5bK Ya3BoCUyEgBCj1GQQVCCMtOITj2hhZtlZ2BYIwBIQwHIWZtG0i.NLIWhONBc Z.Z8_AsHO2oeZQFcyplMOtktgHV4CBLjvPzpfuUqp8rfMyXDE3AooJpjxvhT vZw1iIunDt0do1TTH8d_b7jQC9ixszFsehdo2dGG2F.EKcxREMU7gpshd1gP XMNXTNhcbJnUYigpM59JGdkKg.ElgB3gC6hBS4Zd7fVBthLcYmw5wvUPPSg. K_QvurhvSidZp7hb.rZkG X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: freebsd-ports Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Date: Thu, 22 Jun 2017 11:50:30 -0400 Message-ID: <1tlnkc1l8md98dl3teqoab8ds3jutmvavc@4ax.com> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <775ba90e-a811-4cc8-a729-bdc0dad7774c@FreeBSD.org> In-Reply-To: <775ba90e-a811-4cc8-a729-bdc0dad7774c@FreeBSD.org> X-Mailer: Forte Agent 4.2/32.1118 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 15:53:45 -0000 [Default] On Thu, 22 Jun 2017 15:38:53 +0100, Matthew Seaman wrote: >On 2017/06/22 15:03, scratch65535@att.net wrote: >> Why don't the same choices apply here? What am I missing? > >Two things: > > 1) It's progress in the development of the FreeBSD base system that >drives the release cycle. The general state of the ports does not exert >much influence on release frequency -- nor should it. Still not getting it, I'm afraid. How often does the base system undergo such drastic architecture changes that existing ports won't run under it? I haven't really been monitoring the situation, but I'd guess it's very seldom if only because such an architectural change is a cursëd big job that can hardly ever be justfied. I'd guess that most adults for whom systems are tools not toys are not too dissimilar to me: I want to *use* my tools, not spend time replacing them every quarter or even every year. As long as they do the job and don't compromise the system, they're fine by me. I have apps running under Win7 that were written for W2K (and in one case NT, iirc), and they're just as useful today as they were then. They do the job: why in the name of sanity should I replace them? So where's the point in everyone going mad trying to keep up a quarterly release schedule that serves more as an annoyance than benefit to your customer base? (Do you read the Asterix comics? The one where Asterix and Obelix go to Switzerland is particularly apropos here, I think: the owner of the inn awakens the guests every hour so that they can turn over the hourglass mounted over their bed. What benefit do the guests derive from that? None, of course, but it helps the owner feel in control of things. But the guests are, reasonably, quite upset by the loss of sleep due to his obsessiveness.) > > 2) Even if we could scrape up enough people to support however many >branches you are proposing, remember they are all volunteers. It's hard >enough getting people to maintain the existing quarterly branches as it >is, and those are relatively short lived so that most merges from head >are pretty trivial. People really aren't going to want to do >essentially repetitive merges to branches where everything else is up to >X years older than head. Which would make it both tedious and >frequently difficult to do. Again I'm really not following your logic. There are 2 versions of the base system now in play: 10.3 and 11.0. There are 2 more being developed: 10.4 and 11.1. 10.2 has already been trashed, thus forcing us to upgrade to 10.3 whether we wanted to or not, which in many cases, mine among them, was a "not". I'm sure the same thing will happen with 10.4 and 11.1 and plenty folk will be just as annoyed as we were with 10.2 Let's say you guys don't try to follow that schedule. You do a ports release for (let's say) 10.0 and then 11.0, but not for the other point releases in between. So if someone feels the deep need for 10.1, or 10.2, or 10.3 (or 11.n mutatis mutandis), they'll run 10.0 (or 11.0) ports under it. It's done all the time in industry. If you treat each ports release as a DVD --immutable once shipped--, or as a PROM, where changes can be made but it's a pain in the dupa so you only do it for the emergency case, it seems to me that the pressure has gone down by a factor of 3 or so. So where's the problem in that? 's mise le meas From owner-freebsd-ports@freebsd.org Thu Jun 22 15:53:52 2017 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 8D3FCD8F23B for ; Thu, 22 Jun 2017 15:53:52 +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 672FC7FB17 for ; Thu, 22 Jun 2017 15:53:52 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (124-148-108-84.dyn.iinet.net.au [124.148.108.84]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v5MFrfed059275 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 22 Jun 2017 08:53:44 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> From: Julian Elischer Message-ID: Date: Thu, 22 Jun 2017 23:53:35 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170622141644.yadxdubynuhzygcy@ivaldir.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 15:53:52 -0000 On 22/6/17 10:16 pm, Baptiste Daroussin wrote: > On Thu, Jun 22, 2017 at 10:03:33AM -0400, scratch65535@att.net wrote: >> [Default] On Thu, 22 Jun 2017 14:18:56 +0200, Baptiste Daroussin >> wrote: >> >>> As usual with such proposal, where do you find the manpower to handle the number >>> of branches required (the quarterly branches are already hard to maintain, it is >>> only one branch). >> Please help me out here, Baptiste, because I'm apparently missing >> *something*. >> >> Out in industry, if you haven't enough people to do a new >> high-quality release every N months, and you can't get a >> headcount increase, then you cut the release schedule. Can't do >> 4 releases a year? Cut back to 2. Still too many? Cut back to >> 1. >> >> The alternatives to cutting the schedule are that (a) people >> begin burning out and quitting, (b) quality drops and your >> customer base begins abandoning you, or (c) both of the above. >> >> Why don't the same choices apply here? What am I missing? > We only have 1 quarterly branch at the time :) > > The model with one branch per release will bring it to way more with a > maintenance window way larger (actually it is 3 month making the quarterly > relatively easy to maintain) Yeah but the quarterly branches are relatively useless because they a not sync'd to anything and mean nothing special to anyone. As soon as you sync to one, it's deleted and replaced by a completely different one meaning you have to replace *EVERYTHING*, so one might as well just use head. it's actually easier. > > Best regards, > Bapt From owner-freebsd-ports@freebsd.org Thu Jun 22 15:57:27 2017 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 F16B9D8F372 for ; Thu, 22 Jun 2017 15:57:27 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cdptpa-oedge", Issuer "cdptpa-oedge" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B68E77FCED for ; Thu, 22 Jun 2017 15:57:27 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from [65.186.81.207] ([65.186.81.207:48937] helo=raspberrypi.bildanet.com) by cdptpa-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id A0/82-10880-D98EB495; Thu, 22 Jun 2017 15:56:13 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1dO4Sr-0000t4-5H; Thu, 22 Jun 2017 11:56:13 -0400 Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Torsten Zuehlsdorff , freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <8e69aff9-4288-fe1e-53df-83a0d74fbe82@columbus.rr.com> From: Baho Utot Message-ID: <6f68460a-2fb6-2234-f7c1-0c15ba75a551@columbus.rr.com> Date: Thu, 22 Jun 2017 15:56:09 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-RR-Connecting-IP: 107.14.168.6:25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 15:57:28 -0000 On 6/22/2017 11:30 AM, Torsten Zuehlsdorff wrote: > On 22.06.2017 21:26, Baho Utot wrote: >> On 6/22/2017 10:03 AM, scratch65535@att.net wrote: >>> [Default] On Thu, 22 Jun 2017 14:18:56 +0200, Baptiste Daroussin >>> wrote: >>> >>>> As usual with such proposal, where do you find the manpower to >>>> handle the number >>>> of branches required (the quarterly branches are already hard to >>>> maintain, it is >>>> only one branch). >>> Please help me out here, Baptiste, because I'm apparently missing >>> *something*. >>> >>> Out in industry, if you haven't enough people to do a new >>> high-quality release every N months, and you can't get a >>> headcount increase, then you cut the release schedule. Can't do >>> 4 releases a year? Cut back to 2. Still too many? Cut back to >>> 1. >>> >>> The alternatives to cutting the schedule are that (a) people >>> begin burning out and quitting, (b) quality drops and your >>> customer base begins abandoning you, or (c) both of the above. >>> >>> Why don't the same choices apply here? What am I missing? >>> _______________________________________________ >>> >> >> >> I am looking at OpenBSD to replace FreeBSD. They have a more relaxed >> update schedule and that fits with what I need. > > Go ahead with whatever fits your needs. > > But since the ports-tree is a subversion repository it is really easy > to maintain the status you want. I do this for various customer and my > various server. > >> I am looking for a system that is very stable and doesn't do the >> upgrade path for the sake of it being newer. > > Which has various downsides. I remember for example various linux LTS > distros, which only apply security fixes. I discovered various bugs > which stay there for years, because they are not security issues - > they just hurt you daily. :D > No not really I ran LFS servers and desktops for 10 years >> Having a "releng ports" version that goes with a releng version of >> the OS would be great by me. Linux from scratch does this and it >> works very well. > > It really does not work well. In everyday situation this results in > "heck we need a new server to get a new version of a needed software, > because we need a new linux version". > I regularly seeing admins setting up different Ubuntu versions, > because at one you have PHP 7 and on the other MySQL 5.7, but not both > at the same Ubuntu version. BSD != Linux so your comparison is invalid. One could still use releng 11.0 ports with 10.3 OS could they not From owner-freebsd-ports@freebsd.org Thu Jun 22 16:01:30 2017 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 D06D7D8F648 for ; Thu, 22 Jun 2017 16:01:30 +0000 (UTC) (envelope-from tz@FreeBSD.org) Received: from toco-domains.de (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::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 6C9E37FEB2 for ; Thu, 22 Jun 2017 16:01:30 +0000 (UTC) (envelope-from tz@FreeBSD.org) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id 827A11AAF0E0; Thu, 22 Jun 2017 18:01:28 +0200 (CEST) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Baho Utot , freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <8e69aff9-4288-fe1e-53df-83a0d74fbe82@columbus.rr.com> <6f68460a-2fb6-2234-f7c1-0c15ba75a551@columbus.rr.com> From: Torsten Zuehlsdorff Message-ID: Date: Thu, 22 Jun 2017 18:01:25 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <6f68460a-2fb6-2234-f7c1-0c15ba75a551@columbus.rr.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 16:01:30 -0000 On 22.06.2017 21:56, Baho Utot wrote: > > > On 6/22/2017 11:30 AM, Torsten Zuehlsdorff wrote: >> On 22.06.2017 21:26, Baho Utot wrote: >>> On 6/22/2017 10:03 AM, scratch65535@att.net wrote: >>>> [Default] On Thu, 22 Jun 2017 14:18:56 +0200, Baptiste Daroussin >>>> wrote: >>>> >>>>> As usual with such proposal, where do you find the manpower to >>>>> handle the number >>>>> of branches required (the quarterly branches are already hard to >>>>> maintain, it is >>>>> only one branch). >>>> Please help me out here, Baptiste, because I'm apparently missing >>>> *something*. >>>> >>>> Out in industry, if you haven't enough people to do a new >>>> high-quality release every N months, and you can't get a >>>> headcount increase, then you cut the release schedule. Can't do >>>> 4 releases a year? Cut back to 2. Still too many? Cut back to >>>> 1. >>>> >>>> The alternatives to cutting the schedule are that (a) people >>>> begin burning out and quitting, (b) quality drops and your >>>> customer base begins abandoning you, or (c) both of the above. >>>> >>>> Why don't the same choices apply here? What am I missing? >>>> _______________________________________________ >>>> >>> >>> >>> I am looking at OpenBSD to replace FreeBSD. They have a more relaxed >>> update schedule and that fits with what I need. >> >> Go ahead with whatever fits your needs. >> >> But since the ports-tree is a subversion repository it is really easy >> to maintain the status you want. I do this for various customer and my >> various server. >> >>> I am looking for a system that is very stable and doesn't do the >>> upgrade path for the sake of it being newer. >> >> Which has various downsides. I remember for example various linux LTS >> distros, which only apply security fixes. I discovered various bugs >> which stay there for years, because they are not security issues - >> they just hurt you daily. :D > > No not really I ran LFS servers and desktops for 10 years This does not mean that you're hit by the bugs i am. The most recent example is a bug in curl parsing a #. This was introduced via a security fix in Ubuntu and make use of '#' in passwords for htaccess impossible, until you use new curl releases. Which are not available on Ubuntu 16 LTS for some more years. >>> Having a "releng ports" version that goes with a releng version of >>> the OS would be great by me. Linux from scratch does this and it >>> works very well. >> >> It really does not work well. In everyday situation this results in >> "heck we need a new server to get a new version of a needed software, >> because we need a new linux version". >> I regularly seeing admins setting up different Ubuntu versions, >> because at one you have PHP 7 and on the other MySQL 5.7, but not both >> at the same Ubuntu version. > > BSD != Linux so your comparison is invalid. No, that is the point of my comparison. Luckily BSD != Linux and also the various distributions schemes of updates having there up- and downsides. But in such discussions its often that only the own use-case is mentioned. And i want to widen the scope. Greetings, Torsten From owner-freebsd-ports@freebsd.org Thu Jun 22 16:02:02 2017 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 1DD41D8F6AC for ; Thu, 22 Jun 2017 16:02:02 +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 056B37FFBE for ; Thu, 22 Jun 2017 16:02:02 +0000 (UTC) (envelope-from julian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 04DBED8F6AB; Thu, 22 Jun 2017 16:02: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 04893D8F6AA for ; Thu, 22 Jun 2017 16:02: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 DCDAA7FFBD for ; Thu, 22 Jun 2017 16:02:01 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (124-148-108-84.dyn.iinet.net.au [124.148.108.84]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v5MG1pMR059333 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 22 Jun 2017 09:01:54 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: scratch65535@att.net, freebsd-ports References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <775ba90e-a811-4cc8-a729-bdc0dad7774c@FreeBSD.org> <1tlnkc1l8md98dl3teqoab8ds3jutmvavc@4ax.com> From: Julian Elischer Message-ID: <708cbded-8a7b-a60f-c668-32fd9966d1a5@freebsd.org> Date: Fri, 23 Jun 2017 00:01:45 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <1tlnkc1l8md98dl3teqoab8ds3jutmvavc@4ax.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 16:02:02 -0000 On 22/6/17 11:50 pm, scratch65535@att.net wrote: > [Default] On Thu, 22 Jun 2017 15:38:53 +0100, Matthew Seaman > wrote: > >> On 2017/06/22 15:03, scratch65535@att.net wrote: >>> Why don't the same choices apply here? What am I missing? >> Two things: >> >> 1) It's progress in the development of the FreeBSD base system that >> drives the release cycle. The general state of the ports does not exert >> much influence on release frequency -- nor should it. > Still not getting it, I'm afraid. How often does the base > system undergo such drastic architecture changes that existing > ports won't run under it? I haven't really been monitoring the > situation, but I'd guess it's very seldom if only because such an > architectural change is a cursĂ«d big job that can hardly ever be > justfied. > > I'd guess that most adults for whom systems are tools not toys > are not too dissimilar to me: I want to *use* my tools, not > spend time replacing them every quarter or even every year. As > long as they do the job and don't compromise the system, they're > fine by me. I have apps running under Win7 that were written for > W2K (and in one case NT, iirc), and they're just as useful today > as they were then. They do the job: why in the name of sanity > should I replace them? > > So where's the point in everyone going mad trying to keep up a > quarterly release schedule that serves more as an annoyance than > benefit to your customer base? (Do you read the Asterix comics? > The one where Asterix and Obelix go to Switzerland is > particularly apropos here, I think: the owner of the inn awakens > the guests every hour so that they can turn over the hourglass > mounted over their bed. What benefit do the guests derive from > that? None, of course, but it helps the owner feel in control of > things. But the guests are, reasonably, quite upset by the loss > of sleep due to his obsessiveness.) > > >> 2) Even if we could scrape up enough people to support however many >> branches you are proposing, remember they are all volunteers. It's hard >> enough getting people to maintain the existing quarterly branches as it >> is, and those are relatively short lived so that most merges from head >> are pretty trivial. People really aren't going to want to do >> essentially repetitive merges to branches where everything else is up to >> X years older than head. Which would make it both tedious and >> frequently difficult to do. > Again I'm really not following your logic. There are 2 versions > of the base system now in play: 10.3 and 11.0. There are 2 more > being developed: 10.4 and 11.1. 10.2 has already been trashed, > thus forcing us to upgrade to 10.3 whether we wanted to or not, > which in many cases, mine among them, was a "not". I'm sure the > same thing will happen with 10.4 and 11.1 and plenty folk will be > just as annoyed as we were with 10.2 I've had this conversation with ports several times, But the requirements of 'business' is not their interest. In fact i was told several times, "Don't use our quarterly packages, make your own with poudriere". (which makes one wonder "What is the purpose of he quarterlies?) My suggestion is to ignore the existence of the quarterly snapshots as they are neither stable (they change every 3 months out from under you) nor snapshots, (they a re updated randomly a bit at a time. This just doesn't work for what business needs. So the only alternative is to have a SVN mirror, and take your own snapshots, and keep your eye on the security notices. > > Let's say you guys don't try to follow that schedule. You do a > ports release for (let's say) 10.0 and then 11.0, but not for the > other point releases in between. So if someone feels the deep > need for 10.1, or 10.2, or 10.3 (or 11.n mutatis mutandis), > they'll run 10.0 (or 11.0) ports under it. It's done all the > time in industry. If you treat each ports release as a DVD > --immutable once shipped--, or as a PROM, where changes can be > made but it's a pain in the dupa so you only do it for the > emergency case, it seems to me that the pressure has gone down by > a factor of 3 or so. So where's the problem in that? > > 's mise le meas > _______________________________________________ > 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 Thu Jun 22 16:07:53 2017 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 ED7AAD8F92C for ; Thu, 22 Jun 2017 16:07:53 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id CD76880392 for ; Thu, 22 Jun 2017 16:07:53 +0000 (UTC) (envelope-from scratch65535@att.net) Received: by mailman.ysv.freebsd.org (Postfix) id CCA3FD8F929; Thu, 22 Jun 2017 16:07:53 +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 CC25AD8F928 for ; Thu, 22 Jun 2017 16:07:53 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm9-vm5.access.bullet.mail.bf1.yahoo.com (nm9-vm5.access.bullet.mail.bf1.yahoo.com [216.109.114.196]) (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 84D6C80391 for ; Thu, 22 Jun 2017 16:07:53 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1498147501; bh=lOxNg9hIcyA62Bq/cwlvyCTS5wyTXuiCvfB9nah3mkk=; h=From:To:Subject:Date:References:In-Reply-To:From:Subject; b=V+e6y2yUPvTh1pUqfnLpBwYGcGtWGCp9HdvRoR+jzCnK6dPXiEmdvIrIyl9vgBlRa9jTA1L4sTOP6XeKdbniTjUlB1OFZbC8CQeoHZxXBovG2yVQJn0h0sCq0fJUKmXSMo6+3GtIbZjKDtOoPzFBatNrnBiNPwBlOCZPWucvHao= Received: from [66.196.81.160] by nm9.access.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 16:05:01 -0000 Received: from [98.139.221.250] by tm6.access.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 16:05:01 -0000 Received: from [127.0.0.1] by smtp120.sbc.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 16:05:01 -0000 X-Yahoo-Newman-Id: 825108.61395.bm@smtp120.sbc.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: Bxp5vx0VM1mkIQp94U5U4ctWLK4y01JCFRsW2LqEnDW5Gwy t0uv8KlL2BaXcuPShrgrKTUv15.FTCnmFQJv.7kBcw17FPuTwzVJxhUuDCVz amVog3POvDlpZgoJ.n52DPkwY.60BgZWslYEGMcDVjWwSoj3VY7CdIvoO9OF U83ckagHj4jso8uI9u9zeGFTnms4mWXXwTRw4L8ov7t4Hx257.c1tw5Euhw7 LkrRgmLMMp2Xqr2hTxNfenHwtjiT0WlmXjFdiLngkBvqoAAhatY7Cth4zXSF 1y2i6tM3dPeKXTJG6.QIElai_5SCu3wIHO2C3ptQPiV0az_WT8wZZlfyF34G w8wQC9yOHxq1DIgaEjfyqXfd.Xs.TbRA4YGBqsGwst93.Lh7n3uJKnuld8Od 0ZDyoz4tScy4WOrzxriFkefBND9UvxidbYqBbU3tVgXCxGl6n3WM46NuaSRN 92N9fDCdHEXNgmVFiRjHtYGSRNpDU4mFTO16gNIjXZqZLZtf6RE7C9u3RJnS gADZg8Y39vXLilmKSSmo3gwB9nqrpNs.6ZR6KT7jE0U4oAvtCZTQjWw-- X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: freebsd-ports Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Date: Thu, 22 Jun 2017 12:04:44 -0400 Message-ID: <6cqnkcd1ej1dobpcb39ifjs9vdltbln23s@4ax.com> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <8e69aff9-4288-fe1e-53df-83a0d74fbe82@columbus.rr.com> In-Reply-To: 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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 16:07:54 -0000 [Default] On Thu, 22 Jun 2017 17:30:10 +0200, Torsten Zuehlsdorff wrote: >I regularly seeing admins setting up different Ubuntu versions, because >at one you have PHP 7 and on the other MySQL 5.7, but not both at the >same Ubuntu version. Which is one of the nice things about having central development rather than a dozen forks being developed separately. But it still doesn't work perfectly, since we also have some skews like that. From owner-freebsd-ports@freebsd.org Thu Jun 22 16:09:11 2017 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 5EEB3D8F9E2 for ; Thu, 22 Jun 2017 16:09:11 +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 E56CF80450 for ; Thu, 22 Jun 2017 16:09:10 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from zero-gravitas.local (unknown [85.199.232.226]) (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 52588C553 for ; Thu, 22 Jun 2017 16:09:01 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/52588C553; dkim=none; dkim-atps=neutral Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <8e69aff9-4288-fe1e-53df-83a0d74fbe82@columbus.rr.com> <6f68460a-2fb6-2234-f7c1-0c15ba75a551@columbus.rr.com> From: Matthew Seaman Message-ID: <5c99c989-27cd-9456-a526-f08a0b76c0a4@FreeBSD.org> Date: Thu, 22 Jun 2017 17:08:55 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <6f68460a-2fb6-2234-f7c1-0c15ba75a551@columbus.rr.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="PcfM2NxNj7p1lf9sD4gP9xKp0TrTAjRee" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 16:09:11 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --PcfM2NxNj7p1lf9sD4gP9xKp0TrTAjRee Content-Type: multipart/mixed; boundary="sgA9I7LVmBfLQlLBTUMxT4NdTiUtKN32a"; protected-headers="v1" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: <5c99c989-27cd-9456-a526-f08a0b76c0a4@FreeBSD.org> Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <8e69aff9-4288-fe1e-53df-83a0d74fbe82@columbus.rr.com> <6f68460a-2fb6-2234-f7c1-0c15ba75a551@columbus.rr.com> In-Reply-To: <6f68460a-2fb6-2234-f7c1-0c15ba75a551@columbus.rr.com> --sgA9I7LVmBfLQlLBTUMxT4NdTiUtKN32a Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017/06/22 20:56, Baho Utot wrote: > One could still use releng 11.0 ports with 10.3 OS could they not No, not in general. You've got it the wrong way round. You might get away with releng 10.3 ports and 11.0 OS for a while but it will likely cause you grief when you do run afoul of a necessary security update and try and update stuff. Cheers, Matthew --sgA9I7LVmBfLQlLBTUMxT4NdTiUtKN32a-- --PcfM2NxNj7p1lf9sD4gP9xKp0TrTAjRee 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 iQJ8BAEBCgBmBQJZS+udXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnuGAQAJdvy6xj68rkPxgFP63/a4r9 X2DM10plbvkMRcQV2A9HitWgv/q0i3+CJfNGIdW7HnCP7F0ceWN4rDYEQJ8NLott K1u/ozk0yEjkmQ8nUXINFwUuU75KZsRvKsWqqhx21h3Sh7LmXdR9BJLSwdH2CJS6 Pmbii1Q7XAL5+t96Y/oSYbywtrV1N9xq1kuAxZO6a/3s//yCeYs/E1C7X7I2w6nb Nw3empEunRvD21DbWWK/b8yTOhrjcnfp7UtgH+g89Vwb/CMRJvl7v+MrATKs16k1 T+w+cxJm7xgLCoAyly2o9XToQ7kUONLH+FL+8ahiemeDaV2o9R8swGOmEA6Yl+Bk YkPltcAKarUMqaiUGNicrqTjLLfbEWxExDloRrQOc2cv61X/swTttvt/OW46FVv2 WgEqfwgdd15m7BR7laggeK9kFvRTUikeqAyW7C9XHj2aq2bddooINuVPwHoaGrty Lt7II1JnVtMQsPrvdSPUlKjB+DF4vlP1cWlChQ9FC4jqabpC7yQqrC6Tawv5SJV4 b5W0RoiRlUEjrnD3rrD6qKSqJAnttqCLGpW9mVg78cKZT4umYgXnQVfBMgee6iqd KEr1cXmgfNDvaW7biw4J62m4ndm4u+kaC5sCkJqEJ7bprQTUcJb1+Z13mLiuZP0p HRY/aCP9SUht9JBj9LhF =55X8 -----END PGP SIGNATURE----- --PcfM2NxNj7p1lf9sD4gP9xKp0TrTAjRee-- From owner-freebsd-ports@freebsd.org Thu Jun 22 16:18:10 2017 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 54F04D8FBEA for ; Thu, 22 Jun 2017 16:18:10 +0000 (UTC) (envelope-from scratch65535@att.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 33F0D80A86 for ; Thu, 22 Jun 2017 16:18:10 +0000 (UTC) (envelope-from scratch65535@att.net) Received: by mailman.ysv.freebsd.org (Postfix) id 30227D8FBE9; Thu, 22 Jun 2017 16:18:10 +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 2F99BD8FBE8 for ; Thu, 22 Jun 2017 16:18:10 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm20-vm7.access.bullet.mail.bf1.yahoo.com (nm20-vm7.access.bullet.mail.bf1.yahoo.com [216.109.115.118]) (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 DBCE780A85 for ; Thu, 22 Jun 2017 16:18:09 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1498148180; bh=SyvL9sze9/GIu92he61cBhv2OJVAc7NqdEOX+8Pk+xw=; h=From:To:Subject:Date:References:In-Reply-To:From:Subject; b=bRlAk3/EX41CWRTJgkrX7NuzMgY3ICSPsJoPewDnPnGv5Mff1UdVVSNnwku3Hn86TbORAOJuAhOiZp1humdhNPHXkqLWHgImZbnh/GAtAWbYmnSVGvv6IInx3iehRI5Zxi6RELbVc9otKLObwTpL4xGVwp7u6Lhh3Bm+xm3yPNA= Received: from [66.196.81.155] by nm20.access.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 16:16:20 -0000 Received: from [98.139.244.51] by tm1.access.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 16:16:20 -0000 Received: from [127.0.0.1] by smtp113.sbc.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 16:16:20 -0000 X-Yahoo-Newman-Id: 371421.39906.bm@smtp113.sbc.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: dY.r8CUVM1lq..iStZg3wpcoh14fc3LqYHAhJX50HlRbql0 kwM6fCYY1Qym2sJzHbu9LOGH0wbGssnOPuXJqeNhBCu_Odix4OhQ7Eqv6dBH FvBHDyoWOPmBpPJjhjI7H90zKWiM8ybecU4Ss9e9vddorMqTc57H3koGfJGz 22r1Z9VS20McFzhLNw.maXbapJz.o94TSddBcRLtL62TLI1xM9EvwU36xQG_ X7yUMsveYzB87f028ekBwRWOsJd.nOmDZI33RMIFIlVeLQm7EAzUi139CRaX m7ZgW8pokz9kwsAt84Iz4X.qILNmRy9va2d_cdQ2o2_MiCAHosA1admOsnZm ._TWKvWovjRhLYMPQn_7yKDSOSvD7vuXDrJl2qmG05g.KQNav2rRrCr_vuNo iEODQzJfekmZdq62sDaEyjA_TYv0MS.YDNSsPh3.OIe2wvtyHiMzs9nrKEa0 8FyPqSGuMFlQPpqKsdlsTU7WT8_Z18CusUGoSEQSq1RytJJKt30VTmftRCHo VNa2LOWREvpiVzXWDOUQrQy0XiLjxCuOKIwcYtpcCTossB0lyHELKWg-- X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: freebsd-ports Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Date: Thu, 22 Jun 2017 12:16:25 -0400 Message-ID: References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <775ba90e-a811-4cc8-a729-bdc0dad7774c@FreeBSD.org> <1tlnkc1l8md98dl3teqoab8ds3jutmvavc@4ax.com> <708cbded-8a7b-a60f-c668-32fd9966d1a5@freebsd.org> In-Reply-To: <708cbded-8a7b-a60f-c668-32fd9966d1a5@freebsd.org> 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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 16:18:10 -0000 [Default] On Fri, 23 Jun 2017 00:01:45 +0800, Julian Elischer wrote: >I've had this conversation with ports several times, But the requirements >of 'business' is not their interest. In fact i was told several times, >"Don't use our quarterly packages, make your own with poudriere". >(which makes one wonder "What is the purpose of he quarterlies?) Indeed. I can't help feeling that there's something very wrong when people for whom the system is a tool rather than a plaything have to work around the choices made by the "official" developers. Besides your question, I'd add: for whom are the developers developing, if not for those who want a useful tool rather than a hobby? 's mise le meas From owner-freebsd-ports@freebsd.org Thu Jun 22 16:34:20 2017 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 C1A83D90144 for ; Thu, 22 Jun 2017 16:34:20 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id A2AF381431 for ; Thu, 22 Jun 2017 16:34:20 +0000 (UTC) (envelope-from scratch65535@att.net) Received: by mailman.ysv.freebsd.org (Postfix) id 9EA12D90143; Thu, 22 Jun 2017 16:34:20 +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 9C4A1D90142 for ; Thu, 22 Jun 2017 16:34:20 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm16-vm6.access.bullet.mail.bf1.yahoo.com (nm16-vm6.access.bullet.mail.bf1.yahoo.com [216.109.115.53]) (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 47EE481430 for ; Thu, 22 Jun 2017 16:34:19 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1498149153; bh=1hJHXYF9YIJFxouzv5waqwR1uqB7/miAvdHV1yzEWBc=; h=From:To:Subject:Date:References:In-Reply-To:From:Subject; b=mhNXOM29/rxLzCLLgrWKKJs9QPS4dk7ZBUMgK9aaIRgz0XqEM6OzY8q8G0nkILOD7i0APFlCGuaQEIMVeJmSvOVGrGpf2/8hxAZtC/QYjJ+tCWEhLyAYj3GQdYKhRQubMq50i8JUMTWCG7F3jJcjHS67OpLCxrj2xGJqvOUTg9U= Received: from [66.196.81.160] by nm16.access.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 16:32:33 -0000 Received: from [98.139.221.156] by tm6.access.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 16:32:33 -0000 Received: from [127.0.0.1] by smtp116.sbc.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 16:32:33 -0000 X-Yahoo-Newman-Id: 7642.34567.bm@smtp116.sbc.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: TB3C088VM1m2sf__ZsIFqr2LEEBqomcuUa5j0Joje2i20WG GjxpHBQRT.PKrPt16yejVYKL248s9YiaH4bptArrkwM0EkzNGBRoKTefLNb2 5HZ6_whWwfSnGsDJmVEOHFG5Rys8uVsyABzPS7vycheI2zeaI0HfuLSuyN3Z YkR4K0GITmXvrPfjBoDMudsea95RhnmZu0UWMgzYfpeRTVCBeM2l.63P6shH zex4wT8topkxYRdLc8C1EVBNwDQiSSKjTa3JGC0JHs0P2RlShqXHe2Jh6qEQ ztda4ysANdg3Jjxi9lIcrlHR8cVEahKdLJ30z.gb0mTNMJK9S4DMrwwRgRC. _r_c.nP_FEfu5IuDlIwvL1GvDas_88LN6bsEO7W3dZVz4_bUS4s10j.LLM2F Qc4p8C1JbUZstJe1dfNvjSUNTBS51QQz1cHm60JwYz6uFtCsGplPE177.zaV yYfv6h0jsnFUfE9jJTiBTYUwfNxJTxsbaal88skqoyCP_jeFYs7LOf4hP5gL SE5QCgolZmO98qkUOSTrT2QF9fGEFXx4JHkRKMeRJzZiyF3SikHpavA-- X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: freebsd-ports Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Date: Thu, 22 Jun 2017 12:32:45 -0400 Message-ID: <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> In-Reply-To: <20170622141644.yadxdubynuhzygcy@ivaldir.net> 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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 16:34:20 -0000 [Default] On Thu, 22 Jun 2017 16:16:44 +0200, Baptiste Daroussin wrote: >The model with one branch per release will bring it to way more with a >maintenance window way larger It would indeed! Factor of 3, I think. But I'm really not suggesting that, I'm suggesting that a better schedule would be one ports release for v10, one for v11, one for v12, etc. It could be done for n.0 or any of the others. Were it my decision, I'd probably go for n.1, since there might be fewer bugs than in n.0, but the difference might not be significant. My problem is that my industry experience tells me that reducing the frequency of port releases is practically *guaranteed* to be a Really Good Thing for everyone. Yet apparently you and others on the dev team don't like the idea, and no matter how I much I think about it, I haven't been able to understand why you don't. 's mise le meas From owner-freebsd-ports@freebsd.org Thu Jun 22 16:47:22 2017 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 28CD5D905D9 for ; Thu, 22 Jun 2017 16:47:22 +0000 (UTC) (envelope-from lylecorman@gmail.com) Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::241]) (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 B146981B64 for ; Thu, 22 Jun 2017 16:47:21 +0000 (UTC) (envelope-from lylecorman@gmail.com) Received: by mail-wr0-x241.google.com with SMTP id x23so6010425wrb.0 for ; Thu, 22 Jun 2017 09:47:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=BgOXQLb5MOopxaoygqvpPEobqgvFWna9QirXutJzue0=; b=P7I64FwpnwjkH7AL95vAtMwabYOoDlAQTclaMchbjXl6K+CfjgyVPm073tNzCPYgT4 rPFKdjLfrhgUGvYLiq8NAMN1fIp0Osh1HaI5pfpIiiD/XPVtM4U3G6ivYjsaEiwsC6IP GyaEewxIjEyEJaWuUR8ZcSK0pB4uO7KLLnh21TsGuMrbtSfPPcn2C00OYp8G3gyAQYTQ F53ctiInhjfSehoS+3f2NpWBSt047mWSHSLKyW5F3Lt/QIqTURg+4wGzjyQd9aBsetHp Bci/dS59EJDaOqLpQ8hYD3GCF2Ro6yCGnqT3gDk/SZlvf0iwyPSi6xVc+RqbQ073mWpZ FpTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=BgOXQLb5MOopxaoygqvpPEobqgvFWna9QirXutJzue0=; b=ICEkWM8jGrZIsdUfbICUXAAME5GBODNjzrZIwwmCu7E+G/xkllH+fdTiE/xpTNc88t tgSSjVjBwbDHzn3G5fDuLNpuPkXxtWUzmhoOYqiu4v1QysSsALjcT0SUqgAMIzFhDDdG ALSrcz3GO4tCxkd8o13M2b7C3Cnmsi3CU/EDpZslbKhTarj6TNV5bg8KFWq1IIzQ18qj FCoblV3TYU/ptPssYiOILdfCN4k+gQmO1QP2QuS13wDo2Mxeb2P0h8aCaFvcv+Qz+ca1 kk9i8DmHMONELFgzYVAju0gSZJpYMdY8k+z7P5d90CiX5bQBM92HTb4q6hfgkRwhyyDn 3amA== X-Gm-Message-State: AKS2vOxsuLN1eE4MUKHbSGVjIDgOVGrQinE27KvjAbYAVvxawdKeYHpr 34nyE4ms/lUFGcSHNrw= X-Received: by 10.28.92.130 with SMTP id q124mr2472646wmb.21.1498150039694; Thu, 22 Jun 2017 09:47:19 -0700 (PDT) Received: from [192.168.0.36] (cable-178-148-5-95.dynamic.sbb.rs. [178.148.5.95]) by smtp.gmail.com with ESMTPSA id n71sm2118523wrb.62.2017.06.22.09.47.18 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Jun 2017 09:47:19 -0700 (PDT) To: freebsd-ports@freebsd.org From: Rastko P Subject: Thunderbird + Lightning on FreeBSD Message-ID: Date: Thu, 22 Jun 2017 18:47:18 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 16:47:22 -0000 I tried compiling Thunderbird from ports, but it's too big, and there are errors. I'll try to do it some time again, starting clean. But in the mean time... Choosing the macOS extension/add-on format seems to be working for the binary distribution. Just go to Most Popular add-ons, and Ligthning will be greyed-out. Click on the "Add" button, and choose Mac OS X. And it appears to be working. From owner-freebsd-ports@freebsd.org Thu Jun 22 17:45:51 2017 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 AB7D8D917FB for ; Thu, 22 Jun 2017 17:45:51 +0000 (UTC) (envelope-from dave@jetcafe.org) Received: from fedex2.jetcafe.org (fedex2.jetcafe.org [205.147.26.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fedex2.jetcafe.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8D19683FEA for ; Thu, 22 Jun 2017 17:45:51 +0000 (UTC) (envelope-from dave@jetcafe.org) X-Envelope-To: Received: from [205.147.26.4] (hokkshideh.jetcafe.org [205.147.26.4]) by fedex2.jetcafe.org (8.15.2/8.15.2) with ESMTPS id v5MHh1DV081059 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 22 Jun 2017 10:43:02 -0700 (PDT) (envelope-from dave@jetcafe.org) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> From: Dave Hayes Message-ID: Date: Thu, 22 Jun 2017 10:43:01 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1 ( out of 5) ALL_TRUSTED,SHORTCIRCUIT X-Spam-Checker-Version: SpamAssassin version 3.4.1 X-Scanned-By: MIMEDefang 2.78 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 17:45:51 -0000 On 06/22/2017 08:53, Julian Elischer wrote: > Yeah but the quarterly branches are relatively useless because they a > not sync'd to anything and mean nothing special to anyone. They are not useless to me. I maintain a fair number of different package repositories for various purposes. Over a long period of time I've found that trying to build from HEAD is a random crapshoot as to whether everything you want will build without you having to svn random ports back and forth through the revision tree (or patch them yourself), patch your build processes, and/or ask for help (which you often might not get). In contrast, the quarterly branches (so far) have built everything I've wanted cleanly and this has been true for some years. No, the quarterlies are not perfect, but they seem to be closer to perfect than HEAD is. Note that you have to handle the edge cases (recent security patches, revision mismatch, etc) anyway, HEAD or no. I find I have to handle less with the quarterlies because they do generally build cleanly. -- Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< Possession of a system of knowledge, or an interest in it, or in discovering one, shouldn't be assumed to confer any license or capacity to operate it. Individual criticisms of a system, incapacity to operate it, or dissatisfaction with it should not be confused with any shortcoming of the system itself. From owner-freebsd-ports@freebsd.org Thu Jun 22 17:48:12 2017 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 8997DD918BB for ; Thu, 22 Jun 2017 17:48:12 +0000 (UTC) (envelope-from dave@jetcafe.org) Received: from fedex2.jetcafe.org (fedex2.jetcafe.org [205.147.26.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fedex2.jetcafe.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6C75D8412C for ; Thu, 22 Jun 2017 17:48:12 +0000 (UTC) (envelope-from dave@jetcafe.org) X-Envelope-To: Received: from [205.147.26.4] (hokkshideh.jetcafe.org [205.147.26.4]) by fedex2.jetcafe.org (8.15.2/8.15.2) with ESMTPS id v5MHmAUb081374 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 22 Jun 2017 10:48:11 -0700 (PDT) (envelope-from dave@jetcafe.org) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <775ba90e-a811-4cc8-a729-bdc0dad7774c@FreeBSD.org> <1tlnkc1l8md98dl3teqoab8ds3jutmvavc@4ax.com> <708cbded-8a7b-a60f-c668-32fd9966d1a5@freebsd.org> From: Dave Hayes Message-ID: <9b1f115e-c466-5165-7b61-f1de59ce9076@jetcafe.org> Date: Thu, 22 Jun 2017 10:48:10 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1 ( out of 5) ALL_TRUSTED,SHORTCIRCUIT X-Spam-Checker-Version: SpamAssassin version 3.4.1 X-Scanned-By: MIMEDefang 2.78 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 17:48:12 -0000 On 06/22/2017 09:16, scratch65535@att.net wrote: > I can't help feeling that there's something very wrong when > people for whom the system is a tool rather than a plaything have > to work around the choices made by the "official" developers. I'd say this is true no matter what OS you use these days. -- Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< It is only knowledge that will destroy bias. From owner-freebsd-ports@freebsd.org Thu Jun 22 18:43:27 2017 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 40ADCD926DC for ; Thu, 22 Jun 2017 18:43:27 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (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 C4E65145B for ; Thu, 22 Jun 2017 18:43:26 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: by mail-wr0-x232.google.com with SMTP id k67so34903441wrc.2 for ; Thu, 22 Jun 2017 11:43:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:in-reply-to:references:mime-version :content-transfer-encoding; bh=PuzrmHk8z5ljzbT7IpNFloVAbpiY7+i77tjilMGnDME=; b=KeHMisVfoBfwKB8XHj+8ro0gC7ygv37sqZ6zQ1fvEP1FJ1Ff3CcIG2UhgyNoThXoG0 DlnWcarnMokm2PzHjqTa78zKgzSgNKs9NdpiNXFl0i+t9MyKFN/kHqnSB02ZESkP0yTY oxp4jFoFY+vJ48/zXqKDrtUw8SRdc1s/4yquRefTFc1W/gafWl4XFYs7sQqdv4D6NiLU nxgcFzASmvQtIlH1RiH/cjIWmyau6oKweq6RMzzeWySrCbWZGDM4YvgCP8ogEtyRgrU5 chOP83GOq8pEBpc3kBsfPrWjTAOkQu6VJ0SAq/YFSSEZo/WnVh2jwfuX0terg4fhkvKL KR9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=PuzrmHk8z5ljzbT7IpNFloVAbpiY7+i77tjilMGnDME=; b=AxOTFWodw/w3RuBm+05EwjU8IBxyK3IKXDvOWuTjgauwaw2Q4nfiMceyqqYlyNW1ck U3+3UJmzyJiRl/wVV2mDL3K14ANpPHHfwJQw8CfCpf4ubnz3vvowCEQrdQb9x9qGZ95B 0bavkuWj6dVbWTWu+KqahcRuGuu33pOLJZGLhJmASyVkiioxHg2/nhMRZiibGynsuLp6 0YHHmk+XNVeKEzDK75g4TX9BJhkH+YSoV9xEtL2WEbTU9rwu5GiSP7Ie1zUDgdRsNHOs DzGef8hHXxG0X24t+HiPXEZsJRfs1r2yfrPQnNxMyVLv9fBUGkkZyeCPf7RuXOI2/HbN zKiA== X-Gm-Message-State: AKS2vOyO9pbbHjxq6Yn0Xch9UcQnyM7miqFdB/EfdS5h/te1W5X7PahA K9fqsuJC9mQgp3G7/74= X-Received: by 10.223.132.7 with SMTP id 7mr2902544wrf.187.1498157004986; Thu, 22 Jun 2017 11:43:24 -0700 (PDT) Received: from kiwi.home (AStrasbourg-652-1-188-32.w90-40.abo.wanadoo.fr. [90.40.235.32]) by smtp.gmail.com with ESMTPSA id u17sm2099835wma.8.2017.06.22.11.43.22 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 22 Jun 2017 11:43:24 -0700 (PDT) Message-ID: <1498157001.2235.1.camel@gmail.com> Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version From: demelier.david@gmail.com To: freebsd-ports@freebsd.org Date: Thu, 22 Jun 2017 20:43:21 +0200 In-Reply-To: References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.2 (3.24.2-1.fc26) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 18:43:27 -0000 On Thu, 2017-06-22 at 10:43 -0700, Dave Hayes wrote: > They are not useless to me. > > I maintain a fair number of different package repositories for > various > purposes. Over a long period of time I've found that trying to build > from HEAD is a random crapshoot as to whether everything you want > will > build without you having to svn random ports back and forth through > the > revision tree (or patch them yourself), patch your build processes, > and/or ask for help (which you often might not get). > > In contrast, the quarterly branches (so far) have built everything > I've > wanted cleanly and this has been true for some years. No, the > quarterlies are not perfect, but they seem to be closer to perfect > than > HEAD is. > The problem is not if a port will build fine or not. Let me use my example of www/node back. I have built the port www/node in poudriere using this origin (so no version). At the time I've built it it was a 6.x version. When I upgraded my machine, www/node has switched to 7.x version and since this software follows semantic versioning, every application using the 6.x branch may or may not work anymore. And that was my case, etherpad could not start. Fortunately, I had the chance that the port www/node6 existed and I could downgrade. Some people would argue to upgrade etherpad to a version that supports node 7.x but that is not always an option. Hint: how many application are still not python 3 compatible ? :-) Now, I'm in a state where if I pull the ports tree, I must check if www/node6 still exists or I must not upgrade. With releases branches I will be sure that: 1. www/node will *always* be at a 6.x version; 2. www/node will still be supported for the version of the FreeBSD system. Regards, -- David Demelier From owner-freebsd-ports@freebsd.org Thu Jun 22 18:57:52 2017 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 8BF26D9294B for ; Thu, 22 Jun 2017 18:57:52 +0000 (UTC) (envelope-from dave@jetcafe.org) Received: from fedex2.jetcafe.org (fedex2.jetcafe.org [205.147.26.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fedex2.jetcafe.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 45DA91A9C for ; Thu, 22 Jun 2017 18:57:51 +0000 (UTC) (envelope-from dave@jetcafe.org) X-Envelope-To: Received: from [205.147.26.4] (hokkshideh.jetcafe.org [205.147.26.4]) by fedex2.jetcafe.org (8.15.2/8.15.2) with ESMTPS id v5MIvpd2085775 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 22 Jun 2017 11:57:51 -0700 (PDT) (envelope-from dave@jetcafe.org) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <1498157001.2235.1.camel@gmail.com> From: Dave Hayes Message-ID: Date: Thu, 22 Jun 2017 11:57:51 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <1498157001.2235.1.camel@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1 ( out of 5) ALL_TRUSTED,SHORTCIRCUIT X-Spam-Checker-Version: SpamAssassin version 3.4.1 X-Scanned-By: MIMEDefang 2.78 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 18:57:52 -0000 On 06/22/2017 11:43, demelier.david@gmail.com wrote: > Let me use my example of www/node back. I have built the port www/node > in poudriere using this origin (so no version). At the time I've built > it it was a 6.x version. When I upgraded my machine, www/node has > switched to 7.x version and since this software follows semantic > versioning, every application using the 6.x branch may or may not work > anymore. I completely agree that an annoying consequence of what the volunteers are doing with the ports tree. These unwelcome surprises are the bulk of my non-automated work in creating package repositories. Frankly, I also wish this kind of thing would stop. Ultimately my wishes are irrelevant for reasons far far beyond the scope of this thread. > Now, I'm in a state where if I pull the ports tree, I must check if > www/node6 still exists or I must not upgrade. > > With releases branches I will be sure that: > > 1. www/node will *always* be at a 6.x version; > 2. www/node will still be supported for the version of the FreeBSD > system. That sounds reasonable...yet others will likely expect www/node to always be the latest version. Perhaps these others might complain that it is not the latest version and it would be reasonable to have node always be at the latest version. Would you agree that release branches would be unnecessary if somehow you could select the version of node that the ports tree builds via some (as yet unspecified) mechanism? -- Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< If you want to get rid of somebody, just tell them something for their own good. From owner-freebsd-ports@freebsd.org Thu Jun 22 20:00:03 2017 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 0E5DFD936B1 for ; Thu, 22 Jun 2017 20:00:03 +0000 (UTC) (envelope-from andre@drenet.net) Received: from anet3.andregoree.net (anet3.drenet.net [69.87.219.216]) (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 DAD3B3484 for ; Thu, 22 Jun 2017 20:00:01 +0000 (UTC) (envelope-from andre@drenet.net) Received: from localhost (localhost [127.0.0.1]) by anet3.andregoree.net (Postfix) with ESMTP id E9D0FDB3670 for ; Thu, 22 Jun 2017 15:53:45 -0400 (EDT) Received: from anet3.andregoree.net ([127.0.0.1]) by localhost (anet3.andregoree.net [127.0.0.1]) (maiad, port 10024) with ESMTP id 02238-07 for ; Thu, 22 Jun 2017 15:53:45 -0400 (EDT) Received: from mail.drenet.net (localhost [127.0.0.1]) (Authenticated sender: andre@drenet.net) by anet3.andregoree.net (Postfix) with ESMTPA id 8E10ADB34CC for ; Thu, 22 Jun 2017 15:53:45 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 22 Jun 2017 15:53:45 -0400 From: Andre Goree To: freebsd-ports@freebsd.org Subject: Re: NEW APR/APR-Utils In-Reply-To: <20170622130021.GB41229@doctor.nl2k.ab.ca> References: <20170622130021.GB41229@doctor.nl2k.ab.ca> Message-ID: X-Sender: andre@drenet.net User-Agent: Roundcube Webmail/1.2.5 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 20:00:03 -0000 On 2017/06/22 9:00 am, The Doctor wrote: > ARR and APR-utils are up to 1.6.X > > Please update ports accordingly. > > -- > Member - Liberal International This is doctor@@nl2k.ab.ca Ici > doctor@@nl2k.ab.ca > Yahweh, Queen & country!Never Satan President Republic!Beware > AntiChrist rising! > https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on > Atheism > Talk Sense to a fool and he calls you foolish - Euripides > _______________________________________________ > 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" Also, apache2.4 fails to build when ssl=libressl is set it /etc/make.conf, seemingly b/c of apr1 configuration/settings (see below). I've noticed when running make config on devel/apr1, it has only ticks for 'openssl' & 'nss', FWIW. /usr/local/share/apr/build-1/libtool --silent --mode=link cc -O2 -pipe -I/usr/local/include -DLIBICONV_PLUG -fstack-protector -fno-strict-aliasing -L/usr/local/lib/db5 -L/usr/lib -L/usr/local/lib -Wl,-rpath,/usr/local/lib -fstack-protector -o fcgistarter fcgistarter.lo -L/usr/local/lib -R/usr/local/lib $ laprutil-1 -ldb-5.3 -lgdbm -lexpat -L/usr/local/lib -R/usr/local/lib -lapr-1 -lcrypt -lpthread --- ab --- ab.o: In function `main': ab.c:(.text+0xbd9): undefined reference to `SSL_CTX_set_max_proto_version' ab.c:(.text+0xbea): undefined reference to `SSL_CTX_set_min_proto_version' cc: error: linker command failed with exit code 1 (use -v to see invocation) *** [ab] Error code 1 make[4]: stopped in /usr/ports/www/apache24/work/httpd-2.4.26/support 1 error make[4]: stopped in /usr/ports/www/apache24/work/httpd-2.4.26/support *** [all-recursive] Error code 1 make[3]: stopped in /usr/ports/www/apache24/work/httpd-2.4.26/support 1 error make[3]: stopped in /usr/ports/www/apache24/work/httpd-2.4.26/support *** [all-recursive] Error code 1 make[2]: stopped in /usr/ports/www/apache24/work/httpd-2.4.26 1 error make[2]: stopped in /usr/ports/www/apache24/work/httpd-2.4.26 ===> Compilation failed unexpectedly. -- Andre Goree -=-=-=-=-=- Email - andre at drenet.net Website - http://www.drenet.net PGP key - http://www.drenet.net/pubkey.txt -=-=-=-=-=- From owner-freebsd-ports@freebsd.org Thu Jun 22 21:11:29 2017 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 91441D9492E for ; Thu, 22 Jun 2017 21:11:29 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7D30365AAE for ; Thu, 22 Jun 2017 21:11:29 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mailman.ysv.freebsd.org (Postfix) id 7C4F4D9492D; Thu, 22 Jun 2017 21:11:29 +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 7A392D9492C for ; Thu, 22 Jun 2017 21:11:29 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 59C6065AAD for ; Thu, 22 Jun 2017 21:11:28 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 030D9734; Thu, 22 Jun 2017 16:11:28 -0500 (CDT) Date: Thu, 22 Jun 2017 16:11:26 -0500 From: Mark Linimon To: scratch65535@att.net Cc: freebsd-ports Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170622211126.GA6878@lonesome.com> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 21:11:29 -0000 On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65535@att.net wrote: > My problem is that my industry experience tells me that reducing > the frequency of port releases is practically *guaranteed* to be > a Really Good Thing for everyone. I remember before we had the quarterly releases, and people on the mailing lists complained constantly about the ports bits only being available once per release, or rolling with -head. In other words, the exact opposite of what you are suggesting. tl;dr: there is no way to satisfy everyone. mcl From owner-freebsd-ports@freebsd.org Thu Jun 22 22:16:48 2017 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 D8C53D956A6 for ; Thu, 22 Jun 2017 22:16:48 +0000 (UTC) (envelope-from scratch65535@att.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 B86FC676B9 for ; Thu, 22 Jun 2017 22:16:48 +0000 (UTC) (envelope-from scratch65535@att.net) Received: by mailman.ysv.freebsd.org (Postfix) id B44F8D956A5; Thu, 22 Jun 2017 22:16: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 B2240D956A4 for ; Thu, 22 Jun 2017 22:16:48 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm2-vm6.access.bullet.mail.bf1.yahoo.com (nm2-vm6.access.bullet.mail.bf1.yahoo.com [216.109.114.93]) (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 5FE5F676B8 for ; Thu, 22 Jun 2017 22:16:47 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1498169699; bh=6TmVJkn0bRjXRbqs4pMarGBnHdmJUaL7z/S1sbMyvY4=; h=From:To:Subject:Date:References:In-Reply-To:From:Subject; b=mL6zRG5XD/GZK8/IaDyTOBlB/gfcFDWViTd7eCKlPvo6TB8k+mLzM0mH8JqJBccDkb0y0omeBUjPUlmz5ZEneH3in+wh0KlUhFoc6zGWBU9zTcM7ioC4nDuCGElLWS8kL9Yshu0UTrdQa1UueSjdz1OUzQHY9ksOQwXCw59klO8= Received: from [66.196.81.161] by nm2.access.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 22:14:59 -0000 Received: from [98.139.244.51] by tm7.access.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 22:14:59 -0000 Received: from [127.0.0.1] by smtp113.sbc.mail.bf1.yahoo.com with NNFMP; 22 Jun 2017 22:14:59 -0000 X-Yahoo-Newman-Id: 485073.12776.bm@smtp113.sbc.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 3CEfy94VM1lMBUxfpihzEE.5yQ8S2r960NKHw._sQleDIXN 6ec6xndS9DibyolqYeLsnXGxYeHHKWvTLj3DYTEwy54JNrcRz4tJnjwkNbPq XefyeFRnOrGp6FNWM1PQsXrdZHOL1cnPNvrPHJoR6D3XncBTx3t4SHshfvh9 m2Si7__fnUQn3HocZZGj20X2PYQKl6nKJKCYOD55OJt8tb66WUai_dpikX6p tP458giW9RQiiRUH2sdOMe43QjXTK.hkzpV45pQ90j2aICsg6__E.YIQyeTe jFzEyQISbQa2PSKzTd0z_1nn_CROw.860x0twyWoTZMYejC92QtCW8u8Q36o .nIxjRqCZZGcgFAfDouksgn03.s3wKClh2YbVp.kbiNkmyvTXy0LfTgVGgQP gWwFrRP7ZI5VVGbtDwm.Uz.oTfggSK.TLMj._U8EYhrHZyOo8_fJE7MTu6pZ PSBsJx4_pRHJtimXOyHciNBEy3BO.DuADEATMonPDg87Vy4PVva9eT6lZzWF l3ou7MCzV0w.jy8HZwwPeWxAA478EBVvx6WfgRKX_HT9QLYpMejx04VYYD6_ vPJIYpIXgavMJsssULAU2 X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: freebsd-ports Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Date: Thu, 22 Jun 2017 18:15:12 -0400 Message-ID: References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> In-Reply-To: <20170622211126.GA6878@lonesome.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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 22:16:48 -0000 [Default] On Thu, 22 Jun 2017 16:11:26 -0500, Mark Linimon wrote: >On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65535@att.net wrote: >> My problem is that my industry experience tells me that reducing >> the frequency of port releases is practically *guaranteed* to be >> a Really Good Thing for everyone. > >I remember before we had the quarterly releases, and people on the >mailing lists complained constantly about the ports bits only being >available once per release, or rolling with -head. Mark, I can only suppose that those complainers are dilettantes of some sort who believe that having The Latest-And-Greatest Bits is a social-status enhancer. **Nobody** with real work to do ever willingly fools away time "fixing" what isn't broken. That's why there are still millions of XP boxes in daily use despite everything M$ has been able to do to force people to give them up. 's mise le meas From owner-freebsd-ports@freebsd.org Thu Jun 22 22:36:30 2017 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 C3BDBD95BCA for ; Thu, 22 Jun 2017 22:36:30 +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 AAB286801D for ; Thu, 22 Jun 2017 22:36:30 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: by mailman.ysv.freebsd.org (Postfix) id AA00BD95BC7; Thu, 22 Jun 2017 22:36: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 A9A79D95BC6 for ; Thu, 22 Jun 2017 22:36:30 +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 6C8726801B for ; Thu, 22 Jun 2017 22:36:29 +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 152A92847D; Fri, 23 Jun 2017 00:36:21 +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 474C62847B; Fri, 23 Jun 2017 00:36:20 +0200 (CEST) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: scratch65535@att.net, freebsd-ports References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <594C4663.5080209@quip.cz> Date: Fri, 23 Jun 2017 00:36:19 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: 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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 22:36:30 -0000 scratch65535@att.net wrote on 2017/06/23 00:15: > [Default] On Thu, 22 Jun 2017 16:11:26 -0500, Mark Linimon > wrote: > >> On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65535@att.net wrote: >>> My problem is that my industry experience tells me that reducing >>> the frequency of port releases is practically *guaranteed* to be >>> a Really Good Thing for everyone. >> >> I remember before we had the quarterly releases, and people on the >> mailing lists complained constantly about the ports bits only being >> available once per release, or rolling with -head. > > Mark, I can only suppose that those complainers are dilettantes > of some sort who believe that having The Latest-And-Greatest Bits > is a social-status enhancer. **Nobody** with real work to do > ever willingly fools away time "fixing" what isn't broken. And this is where you are so wrong. Ports tree is never in the state where everything works and has no bugs. (and cannot be, because upstreams have bugs) Even if it compiles and installs it does not mean that it is not broken and nobody needs newer version. Just because your needs are different than others doesn't mean others are dilettantes. Miroslav Lachman From owner-freebsd-ports@freebsd.org Thu Jun 22 23:29:26 2017 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 702F6D96B04 for ; Thu, 22 Jun 2017 23:29:26 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cdptpa-oedge", Issuer "cdptpa-oedge" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 355CF6AAC4 for ; Thu, 22 Jun 2017 23:29:25 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from [65.186.81.207] ([65.186.81.207:49146] helo=raspberrypi.bildanet.com) by cdptpa-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id AD/78-10880-43F4C495; Thu, 22 Jun 2017 23:13:56 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1dOBIS-00012p-6u for freebsd-ports@freebsd.org; Thu, 22 Jun 2017 19:13:56 -0400 Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> From: Baho Utot Message-ID: Date: Thu, 22 Jun 2017 19:16:09 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <594C4663.5080209@quip.cz> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-RR-Connecting-IP: 107.14.168.6:25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 23:29:26 -0000 On 6/22/2017 6:36 PM, Miroslav Lachman wrote: > scratch65535@att.net wrote on 2017/06/23 00:15: >> [Default] On Thu, 22 Jun 2017 16:11:26 -0500, Mark Linimon >> wrote: >> >>> On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65535@att.net wrote: >>>> My problem is that my industry experience tells me that reducing >>>> the frequency of port releases is practically *guaranteed* to be >>>> a Really Good Thing for everyone. >>> >>> I remember before we had the quarterly releases, and people on the >>> mailing lists complained constantly about the ports bits only being >>> available once per release, or rolling with -head. >> >> Mark, I can only suppose that those complainers are dilettantes >> of some sort who believe that having The Latest-And-Greatest Bits >> is a social-status enhancer. **Nobody** with real work to do >> ever willingly fools away time "fixing" what isn't broken. > > And this is where you are so wrong. Ports tree is never in the state > where everything works and has no bugs. (and cannot be, because > upstreams have bugs) Even if it compiles and installs it does not mean > that it is not broken and nobody needs newer version. > Just because your needs are different than others doesn't mean others > are dilettantes. > That is just an argument to not do anything, by default. Here is my point, I am a user that installs an OS ( FreeBSD-11.0). Then builds the base from releng-11.0. Followed by building the ports I need. That doesn't give me a usable system always. Should I not be able to do the above and expect a stable system? If not I am running the wrong OS/system. Updates are another monster as I do not want to place my now running system ( finally stable ) and do this all over again. I am not up for that. Hell FreeBSD can not even boot my dual boot system Win7 and FreeBSD 11.0 on zfs raid without going to BIOS and selecting the disk to boot from. No one here could point me to how to set it up using grub as a boot loader! The only information I got was to wing it using half baked information. FreeBSD needs a stable OS followed by a booting method/software followed by a stable ports system. Linux became the custer it has because of the constant change for changes sake. FreeBSD is close behind. That is why I am going to switch to Open BSD as it has "correctness in mind" rather than "I got to have the lastest even if it gets me nothing" mindset. You folks are beating yourself to death trying to keep up when it just is not necessary ( for most cases, although some one will say that they need the latest version of package XYZ ). For instance, what do I gain by using version 11.0 and the ports head, over version 10.0 and the ports head at that time? Well nothing. YMMV. From owner-freebsd-ports@freebsd.org Thu Jun 22 23:47:40 2017 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 B4CDCD974DD for ; Thu, 22 Jun 2017 23:47:40 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6BACB6F876 for ; Thu, 22 Jun 2017 23:47:39 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (x2f7ff2c.dyn.telefonica.de [2.247.255.44]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v5MNSQUM044190 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 22 Jun 2017 23:28:27 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host x2f7ff2c.dyn.telefonica.de [2.247.255.44] claimed to be ultrabook.yoonka.com Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <775ba90e-a811-4cc8-a729-bdc0dad7774c@FreeBSD.org> <1tlnkc1l8md98dl3teqoab8ds3jutmvavc@4ax.com> From: Grzegorz Junka Message-ID: Date: Thu, 22 Jun 2017 23:28:20 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <1tlnkc1l8md98dl3teqoab8ds3jutmvavc@4ax.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2017 23:47:40 -0000 On 22/06/2017 15:50, scratch65535@att.net wrote: > [Default] On Thu, 22 Jun 2017 15:38:53 +0100, Matthew Seaman > wrote: > >> On 2017/06/22 15:03, scratch65535@att.net wrote: >>> Why don't the same choices apply here? What am I missing? >> Two things: >> >> 1) It's progress in the development of the FreeBSD base system that >> drives the release cycle. The general state of the ports does not exert >> much influence on release frequency -- nor should it. > Still not getting it, I'm afraid. How often does the base > system undergo such drastic architecture changes that existing > ports won't run under it? I haven't really been monitoring the > situation, but I'd guess it's very seldom if only because such an > architectural change is a cursĂ«d big job that can hardly ever be > justfied. > > I'd guess that most adults for whom systems are tools not toys > are not too dissimilar to me: I want to *use* my tools, not > spend time replacing them every quarter or even every year. As > long as they do the job and don't compromise the system, they're > fine by me. I have apps running under Win7 that were written for > W2K (and in one case NT, iirc), and they're just as useful today > as they were then. They do the job: why in the name of sanity > should I replace them? > Not sure how you use your tools or in which industry you work. Take front-end development for example. Chrome is releasing a new version every couple of days. Sure, I don't upgrade every release, but when I am developing a website, I want to test using the same version that my customers are using, which is the latest, since Chrome on Windows updates itself automatically. The same with new versions of Firefox. Often new versions of browsers require new versions of libraries to support new features (CSS/JavaScript). That requires new versions of compiler and transpilers. They may, in turn, require an updated version of node or npm. Take server-side development as another example. Erlang is releasing a new version of OTP every couple of weeks. Sure, I don't need a new version when supporting an old application, but I may need one when starting a new application. Especially that many libraries that I am going to use won't support Erlang older than a specific version. A similar story with C++ development, where the standard is being constantly developed and compilers are adding these features every release. Again, you may not need these new features, but a library that you need to use may require the new version. No matter how long you are going to maintain a specific version of ports with locked down versions of applications, there will surely come a time when you will need to upgrade. And for every user that time will be different. The current model is in my opinion the most common denominator - we can't maintain multiple branches with past versions so lets try to properly maintain one with current versions. Grzegorz From owner-freebsd-ports@freebsd.org Fri Jun 23 00:31:55 2017 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 9EA0AD9854E for ; Fri, 23 Jun 2017 00:31:55 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3748270FB6 for ; Fri, 23 Jun 2017 00:31:54 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (p5DC0E955.dip0.t-ipconnect.de [93.192.233.85]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v5N0Vqat045166 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 23 Jun 2017 00:31:52 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host p5DC0E955.dip0.t-ipconnect.de [93.192.233.85] claimed to be ultrabook.yoonka.com Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> From: Grzegorz Junka Message-ID: <19474ced-28cf-917d-4642-cb8a501bd56f@gjunka.com> Date: Fri, 23 Jun 2017 00:31:46 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 00:31:55 -0000 On 22/06/2017 23:16, Baho Utot wrote: > On 6/22/2017 6:36 PM, Miroslav Lachman wrote: >> scratch65535@att.net wrote on 2017/06/23 00:15: >>> [Default] On Thu, 22 Jun 2017 16:11:26 -0500, Mark Linimon >>> wrote: >>> >>>> On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65535@att.net wrote: >>>>> My problem is that my industry experience tells me that reducing >>>>> the frequency of port releases is practically *guaranteed* to be >>>>> a Really Good Thing for everyone. >>>> >>>> I remember before we had the quarterly releases, and people on the >>>> mailing lists complained constantly about the ports bits only being >>>> available once per release, or rolling with -head. >>> >>> Mark, I can only suppose that those complainers are dilettantes >>> of some sort who believe that having The Latest-And-Greatest Bits >>> is a social-status enhancer. **Nobody** with real work to do >>> ever willingly fools away time "fixing" what isn't broken. >> >> And this is where you are so wrong. Ports tree is never in the state >> where everything works and has no bugs. (and cannot be, because >> upstreams have bugs) Even if it compiles and installs it does not >> mean that it is not broken and nobody needs newer version. >> Just because your needs are different than others doesn't mean others >> are dilettantes. >> > > That is just an argument to not do anything, by default. > > Here is my point, I am a user that installs an OS ( FreeBSD-11.0). > Then builds the base from releng-11.0. Followed by building the ports > I need. That doesn't give me a usable system always. Should I not be > able to do the above and expect a stable system? If not I am running > the wrong OS/system. Updates are another monster as I do not want to > place my now running system ( finally stable ) and do this all over > again. I am not up for that. Hell FreeBSD can not even boot my dual > boot system Win7 and FreeBSD 11.0 on zfs raid without going to BIOS > and selecting the disk to boot from. No one here could point me to > how to set it up using grub as a boot loader! The only information I > got was to wing it using half baked information. A user would probably start with precompiled packages. Only power users who know what they are doing would try to compile the packages themselves, and at that point I would expect them to know a thing or two about verifying that they compile and work fine. Grzegorz From owner-freebsd-ports@freebsd.org Fri Jun 23 01:12:59 2017 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 6AD0ED98F30 for ; Fri, 23 Jun 2017 01:12:59 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [207.172.210.101]) (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 11F0D7228C for ; Fri, 23 Jun 2017 01:12:58 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:470:1f07:15ff::1f] (haymarket.m5p.com [IPv6:2001:470:1f07:15ff::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id v5N145hL027930 for ; Thu, 22 Jun 2017 21:04:11 -0400 (EDT) (envelope-from george+freebsd@m5p.com) To: freebsd ports From: George Mitchell Subject: www/libxul Message-ID: <1ed10613-f240-31dd-13e5-7271647869d2@m5p.com> Date: Thu, 22 Jun 2017 21:03:59 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bkX9PE753tk3WHnXHPWAw9fUbnWtfoXV0" X-Spam-Status: No, score=0.2 required=10.0 tests=HELO_MISC_IP, RP_MATCHES_RCVD autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2 (mailhost.m5p.com [IPv6:2001:470:1f07:15ff::f7]); Thu, 22 Jun 2017 21:04:11 -0400 (EDT) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 01:12:59 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --bkX9PE753tk3WHnXHPWAw9fUbnWtfoXV0 Content-Type: multipart/mixed; boundary="QLAfUqel1g8x14V5pHP5XLHJvqxB6HJFE"; protected-headers="v1" From: George Mitchell To: freebsd ports Message-ID: <1ed10613-f240-31dd-13e5-7271647869d2@m5p.com> Subject: www/libxul --QLAfUqel1g8x14V5pHP5XLHJvqxB6HJFE Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable At svn revision 443684. After "make clean extract": work/firefox-45.9.0esr/.mozconfig does not exist. No file under www/libxul contains the string "--enable-jemalloc=3D4". In particular, no patch file in the files directory refers to =2Emozconfig or contains "--enable-jemalloc=3D4". But after "make patch": work/firefox-45.9.0esr/.mozconfig has been created and contains "--enable-jemalloc=3D4". Consequently, the configure script dies at line 26248, complaining that "Option, jemalloc, does not take an argument (4)". I'd love to propose a patch to fix this problem, but I cannot discover for the life of me where the "--enable-jemalloc=3D4" came from. What am I missing? If I make patch, then manually delete the line: ac_add_options --enable-jemalloc=3D4 that mysteriously appeared in .mozconfig and then run configure, all is well. -- George --QLAfUqel1g8x14V5pHP5XLHJvqxB6HJFE-- --bkX9PE753tk3WHnXHPWAw9fUbnWtfoXV0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAllMaP8ACgkQwRES3m+p 4flHFA/9E1Wb/9bG1D7aDVLTxPVtQlbpDyjLEfi1p/TxXo5Q8ObEKfCErsEp6RLY tLt3WeVny5BHg64gXTzQh3clLxSaM6NNYjtJ25TYRtym4VVe92JbegHhk3P0o/MB SzNRSNUCyNabUrPKJzemsHQhCtlRaurh6ihnghBa8U6xizFSuutGaigiqFEeKXgm 76gRI4APKO2sBJyCF+5V3hJiwHc5As/7g9wggCd+Wht56n2EUWtwi2CiwPt32kdl Pl+CzyAcYYtCMLftGBbkfnePKXjlyP9jJU91H5nQjNr+QVGgWSbIAa+qvfh+W7FD P6QPPoV66JGs03dt/rPRk/RYfehJJB2XaPLPzplMl1D/KUWjP0FyP37eOzO6pJr8 vPQF3/eVbAF3qkwjL3MYTnDHqAIT9vGIQSZs06B/HXw7GphTT1X6SwdcvDwPIoVS E5l49Z4qauHrmCv9GN536SGmHwZqxjDiKvvMecd9xyauZ182ZTRSgy6RJABYSZoR +AlwA0w1eHhIxCzN7CgmLuA/QlzKQcQqqG6q7Vd5l3wBt0j7A7sE4H7oH8AGBKkM 8KPFCmsQs3hQrA4xDbmXMh+uCRNfzMFAd2V/XKEDw4oByx7twVVllF1781HhVC8O Tvj5ewmWLA6nq7VdQpfOob4Qms/IAG7S/Z6s+iTmZTNA4zt/65I= =+FYa -----END PGP SIGNATURE----- --bkX9PE753tk3WHnXHPWAw9fUbnWtfoXV0-- From owner-freebsd-ports@freebsd.org Fri Jun 23 01:59:50 2017 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 69D89D99B81 for ; Fri, 23 Jun 2017 01:59:50 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from hermes.heuristicsystems.com.au (hermes.heuristicsystems.com.au [203.41.22.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.heuristicsystems.com.au", Issuer "Heuristic Systems Type 4 Host CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 03B7273243 for ; Fri, 23 Jun 2017 01:59:47 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from [10.0.5.3] (ewsw01.hs [10.0.5.3]) (authenticated bits=0) by hermes.heuristicsystems.com.au (8.15.2/8.15.2) with ESMTPSA id v5N1jdQC026321 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Fri, 23 Jun 2017 11:45:44 +1000 (AEST) (envelope-from dewayne.geraghty@heuristicsystems.com.au) X-Authentication-Warning: b3.hs: Host ewsw01.hs [10.0.5.3] claimed to be [10.0.5.3] Subject: Re: NEW APR/APR-Utils To: freebsd-ports@freebsd.org References: <20170622130021.GB41229@doctor.nl2k.ab.ca> From: Dewayne Geraghty Message-ID: <96a2704f-f59a-e16d-26cf-d796ead498db@heuristicsystems.com.au> Date: Fri, 23 Jun 2017 11:43:14 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 01:59:50 -0000 Andre, I've been down this path a few times and Bernard (who looks after most/all? things related to libressl) does a great job in supporting people like us that build our own packages. Out of frustration of build failures, I applied the patch below, please pay attention to line-breaks. This isn't the best solution as the patches to individual ports as a place holder until the upstream devs do things properly, is the best course. I build 1057 ports (for server use only) successfully, including -rw-r--r-- 1 root wheel 473K Jun 18 19:21 /usr/packages2/K8/All/apr-1.5.2.1.5.4_2.txz ; # libressl Index: /usr/ports/security/libressl/Makefile =================================================================== --- /usr/ports/security/libressl/Makefile (revision 444004) +++ /usr/ports/security/libressl/Makefile (working copy) @@ -13,6 +13,7 @@ LICENSE_FILE= ${WRKSRC}/COPYING CPE_VENDOR= openbsd +CFLAGS+="-O3" OPTIONS_DEFINE= MAN3 NC OPTIONS_DEFAULT= MAN3 NC @@ -35,8 +36,17 @@ INSTALL_TARGET= install-strip TEST_TARGET= check +pre-configure: +.if ${ARCH} == "amd64" + @${REINPLACE_CMD} -e '/define OPENSSL_VERSION_NUMBER/s|OPENSSL_VERSION_NUMBER.*|OPENSSL_VERSION_NUMBER 0x100020bfL|1' ${WRKSRC}/include/openssl/opensslv.h +.endif + +# pre-install: post-install: ${RM} -r ${STAGEDIR}/${PREFIX}/etc/ssl/cert.pem +.if ${ARCH} == "amd64" + @${REINPLACE_CMD} -e '/define OPENSSL_VERSION_NUMBER/s|OPENSSL_VERSION_NUMBER.*|OPENSSL_VERSION_NUMBER 0x100020bfL|1' ${STAGEDIR}${PREFIX}/include/openssl/opensslv.h +.endif post-install-NC-on: ${INSTALL_MAN} ${WRKSRC}/apps/nc/nc.1 ${STAGEDIR}/${PREFIX}/man/man1/nc.1 This should get you over the hump. :) Regards, Dewayne. From owner-freebsd-ports@freebsd.org Fri Jun 23 02:03:14 2017 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 A1573D99DE0 for ; Fri, 23 Jun 2017 02:03:14 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cdptpa-oedge", Issuer "cdptpa-oedge" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 62F117369A for ; Fri, 23 Jun 2017 02:03:13 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from [65.186.81.207] ([65.186.81.207:49231] helo=raspberrypi.bildanet.com) by cdptpa-omsmta02 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 6D/D0-20123-0E67C495; Fri, 23 Jun 2017 02:03:12 +0000 Received: from [192.168.1.143] by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1dODwF-00016x-R9 for freebsd-ports@freebsd.org; Thu, 22 Jun 2017 22:03:11 -0400 Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <19474ced-28cf-917d-4642-cb8a501bd56f@gjunka.com> From: Baho Utot Message-ID: <031b099e-4c70-78fc-206b-54bfcd8fb72d@columbus.rr.com> Date: Thu, 22 Jun 2017 22:03:35 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <19474ced-28cf-917d-4642-cb8a501bd56f@gjunka.com> Content-Language: en-US X-RR-Connecting-IP: 107.14.168.7:25 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 02:03:14 -0000 On 6/22/2017 8:31 PM, Grzegorz Junka wrote: > > On 22/06/2017 23:16, Baho Utot wrote: >> On 6/22/2017 6:36 PM, Miroslav Lachman wrote: >>> scratch65535@att.net wrote on 2017/06/23 00:15: >>>> [Default] On Thu, 22 Jun 2017 16:11:26 -0500, Mark Linimon >>>> wrote: >>>> >>>>> On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65535@att.net wrote: >>>>>> My problem is that my industry experience tells me that reducing >>>>>> the frequency of port releases is practically *guaranteed* to be >>>>>> a Really Good Thing for everyone. >>>>> >>>>> I remember before we had the quarterly releases, and people on the >>>>> mailing lists complained constantly about the ports bits only being >>>>> available once per release, or rolling with -head. >>>> >>>> Mark, I can only suppose that those complainers are dilettantes >>>> of some sort who believe that having The Latest-And-Greatest Bits >>>> is a social-status enhancer. **Nobody** with real work to do >>>> ever willingly fools away time "fixing" what isn't broken. >>> >>> And this is where you are so wrong. Ports tree is never in the state >>> where everything works and has no bugs. (and cannot be, because >>> upstreams have bugs) Even if it compiles and installs it does not >>> mean that it is not broken and nobody needs newer version. >>> Just because your needs are different than others doesn't mean >>> others are dilettantes. >>> >> >> That is just an argument to not do anything, by default. >> >> Here is my point, I am a user that installs an OS ( FreeBSD-11.0). >> Then builds the base from releng-11.0. Followed by building the >> ports I need. That doesn't give me a usable system always. Should I >> not be able to do the above and expect a stable system? If not I am >> running the wrong OS/system. Updates are another monster as I do not >> want to place my now running system ( finally stable ) and do this >> all over again. I am not up for that. Hell FreeBSD can not even >> boot my dual boot system Win7 and FreeBSD 11.0 on zfs raid without >> going to BIOS and selecting the disk to boot from. No one here could >> point me to how to set it up using grub as a boot loader! The only >> information I got was to wing it using half baked information. > > A user would probably start with precompiled packages. Only power > users who know what they are doing would try to compile the packages > themselves, and at that point I would expect them to know a thing or > two about verifying that they compile and work fine. > Grzegorz The pre-compiled packages is what drove me to build the entire system as it gave me a broken system that would not work and upon getting it to function would/**/spontaneous reboot. My hand built packages stopped that. I have built run LFS for 10 years. I created a packaging system using rpm for LFS ( it is on github ) . I worked for turbolinux as a beta tester and worked with the folks that kept KDE3 alive, so I am some one that knows something. I can say from a user stand point ( and previous packager ) that the base packages is nothing but a f'n mess. I still have not cleaned up my desktop system after trying base packages. I was told the only way to fix that was to delete the entire pkg database and reinstall all the packages I had installed. That is just not acceptable. One should be able to just delete the entry of the package in the package database and move on. I was going to build a tool to do just that. I then came across OpenBSD, so I have delayed that until I decide if OpenBSD is a good fit for me. pkgng is almost a beta product at this date. What is wrong with open source projects is this holier that thou attitude, you folks would do well to lose that attitude and start working WITH instead of against the users of your system. They may not always be right but they SHOULD BE AT LEAST HEARD. From owner-freebsd-ports@freebsd.org Fri Jun 23 02:39:59 2017 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 3C3D3D9A805 for ; Fri, 23 Jun 2017 02:39:59 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 27AC8744B4 for ; Fri, 23 Jun 2017 02:39:59 +0000 (UTC) (envelope-from lists@opsec.eu) Received: by mailman.ysv.freebsd.org (Postfix) id 23E80D9A804; Fri, 23 Jun 2017 02:39: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 236AFD9A803 for ; Fri, 23 Jun 2017 02:39:59 +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 DCD48744B3 for ; Fri, 23 Jun 2017 02:39:58 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dOEVn-0007cv-0U; Fri, 23 Jun 2017 04:39:55 +0200 Date: Fri, 23 Jun 2017 04:39:54 +0200 From: Kurt Jaeger To: scratch65535@att.net Cc: freebsd-ports Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170623023954.GA29157@home.opsec.eu> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> 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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 02:39:59 -0000 Hi! > Mark, I can only suppose that those complainers are dilettantes > of some sort who believe that having The Latest-And-Greatest Bits > is a social-status enhancer. **Nobody** with real work to do > ever willingly fools away time "fixing" what isn't broken. There's a blog post from one of the folks that explains the idea behind that 'fast update' mode of operations, and yes, he's doing real work. http://blog.koehntopp.info/index.php/1776-rolling-out-patches-and-changes-often-and-fast/ -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-ports@freebsd.org Fri Jun 23 03:29:59 2017 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 3CD70D9B2E6 for ; Fri, 23 Jun 2017 03:29:59 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.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 242AE75B12 for ; Fri, 23 Jun 2017 03:29:58 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dOFHw-000N7n-Jo; Thu, 22 Jun 2017 21:29:40 -0600 Date: Thu, 22 Jun 2017 21:29:40 -0600 From: The Doctor To: Dewayne Geraghty Cc: freebsd-ports@freebsd.org Subject: Re: NEW APR/APR-Utils Message-ID: <20170623032940.GA85792@doctor.nl2k.ab.ca> References: <20170622130021.GB41229@doctor.nl2k.ab.ca> <96a2704f-f59a-e16d-26cf-d796ead498db@heuristicsystems.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <96a2704f-f59a-e16d-26cf-d796ead498db@heuristicsystems.com.au> User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 03:29:59 -0000 On Fri, Jun 23, 2017 at 11:43:14AM +1000, Dewayne Geraghty wrote: > Andre, > I've been down this path a few times and Bernard (who looks after > most/all? things related to libressl) does a great job in supporting > people like us that build our own packages. > > Out of frustration of build failures, I applied the patch below, please > pay attention to line-breaks. > > This isn't the best solution as the patches to individual ports as a > place holder until the upstream devs do things properly, is the best > course. I build 1057 ports (for server use only) successfully, including > -rw-r--r-- 1 root wheel 473K Jun 18 19:21 > /usr/packages2/K8/All/apr-1.5.2.1.5.4_2.txz ; # libressl > > > Index: /usr/ports/security/libressl/Makefile > =================================================================== > --- /usr/ports/security/libressl/Makefile (revision 444004) > +++ /usr/ports/security/libressl/Makefile (working copy) > @@ -13,6 +13,7 @@ > LICENSE_FILE= ${WRKSRC}/COPYING > > CPE_VENDOR= openbsd > +CFLAGS+="-O3" > > OPTIONS_DEFINE= MAN3 NC > OPTIONS_DEFAULT= MAN3 NC > @@ -35,8 +36,17 @@ > INSTALL_TARGET= install-strip > TEST_TARGET= check > > +pre-configure: > +.if ${ARCH} == "amd64" > + @${REINPLACE_CMD} -e '/define > OPENSSL_VERSION_NUMBER/s|OPENSSL_VERSION_NUMBER.*|OPENSSL_VERSION_NUMBER > 0x100020bfL|1' ${WRKSRC}/include/openssl/opensslv.h > +.endif > + > +# pre-install: > post-install: > ${RM} -r ${STAGEDIR}/${PREFIX}/etc/ssl/cert.pem > +.if ${ARCH} == "amd64" > + @${REINPLACE_CMD} -e '/define > OPENSSL_VERSION_NUMBER/s|OPENSSL_VERSION_NUMBER.*|OPENSSL_VERSION_NUMBER > 0x100020bfL|1' ${STAGEDIR}${PREFIX}/include/openssl/opensslv.h > +.endif > > post-install-NC-on: > ${INSTALL_MAN} ${WRKSRC}/apps/nc/nc.1 > ${STAGEDIR}/${PREFIX}/man/man1/nc.1 > > This should get you over the hump. :) > Regards, Dewayne. Will this work for the 1.6.X ? > _______________________________________________ > 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" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism Talk Sense to a fool and he calls you foolish - Euripides From owner-freebsd-ports@freebsd.org Fri Jun 23 03:58:25 2017 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 A25F6D9B883 for ; Fri, 23 Jun 2017 03:58:25 +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 7C9ED76688 for ; Fri, 23 Jun 2017 03:58:25 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (124-148-108-84.dyn.iinet.net.au [124.148.108.84]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v5N3wKmG062023 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 22 Jun 2017 20:58:23 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> From: Julian Elischer Message-ID: <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> Date: Fri, 23 Jun 2017 11:58:14 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <594C4663.5080209@quip.cz> Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 03:58:25 -0000 On 23/6/17 6:36 am, Miroslav Lachman wrote: > scratch65535@att.net wrote on 2017/06/23 00:15: >> [Default] On Thu, 22 Jun 2017 16:11:26 -0500, Mark Linimon >> wrote: >> >>> On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65535@att.net wrote: >>>> My problem is that my industry experience tells me that reducing >>>> the frequency of port releases is practically *guaranteed* to be >>>> a Really Good Thing for everyone. >>> >>> I remember before we had the quarterly releases, and people on the >>> mailing lists complained constantly about the ports bits only being >>> available once per release, or rolling with -head. >> >> Mark, I can only suppose that those complainers are dilettantes >> of some sort who believe that having The Latest-And-Greatest Bits >> is a social-status enhancer. **Nobody** with real work to do >> ever willingly fools away time "fixing" what isn't broken. > > And this is where you are so wrong. Ports tree is never in the state > where everything works and has no bugs. (and cannot be, because > upstreams have bugs) Even if it compiles and installs it does not > mean that it is not broken and nobody needs newer version. > Just because your needs are different than others doesn't mean > others are dilettantes. The usage of the word dilettante can have negative connotations but he is in essential facts correct. I have spent 30 years on BSD systems in industry, and we almost NEVER want the latest and greatest (except at project start time). What we want is: A "recent" starting point for our next project/upgrade to start from and an ongoing version of that, which will get critical fixes only for at LEAST 2 years, probably 5. The key here is the *_*critical fixes only*_* part. We do NOT want: A new version of perl, python, ssh, shell openssl (*), apache, named, etc. etc. The less changes the better. Basically if it doesn't have a CVE number or it isn't actually completely broken, then don't upgrade it in that branch. We'll fix it ourselves if we need it bad enough (and feed back changes if we know it would be taken). (*) From my experience, the best way to cope with openssl is to have everything link with the system openssl and issue security upgrades to the base OS that upgrades that when there is a need. (this may change, but it's been my experience so far). The recent starting point doesn't even need to be 100.00% working. What we will do here is mirror it and from the mirror, put it into our own source control branch/tree where we will add our own changes to fix/tailor what we need. We will then keep merging in fixes from upstream. which usually will not collide with our private changes/fixes. From that we generate our required packages. From our perspective, a yearly branch (6 months would be 'ideal' but 12 would work) that gets only *critical *fixes would be wonderful. Remember that from the time when a product major release is planned to when it comes out is usually 6 to 12 months lead time. So when it hits the customer's racks, the packages were usually generated somewhere mid-cycle and are already 6 months old. We will not be replacing them on the customer premises machine until they elect to do/purchase an upgrade / patch release. which may be in a year or two. Certainly for a minor update it is rarely less than 6 months. It'd have to be a heartbleed scale security issue to get customers to do an upgrade earlier. > > Miroslav Lachman > _______________________________________________ > 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 Jun 23 04:21:01 2017 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 40D38D9BF77 for ; Fri, 23 Jun 2017 04:21:01 +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 2747176E0C for ; Fri, 23 Jun 2017 04:21:01 +0000 (UTC) (envelope-from julian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 266A1D9BF76; Fri, 23 Jun 2017 04:21:01 +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 25E53D9BF75 for ; Fri, 23 Jun 2017 04:21:01 +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 09CCB76E0B for ; Fri, 23 Jun 2017 04:21:00 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (124-148-108-84.dyn.iinet.net.au [124.148.108.84]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v5N4KfFq062106 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 22 Jun 2017 21:20:45 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Kurt Jaeger , scratch65535@att.net Cc: freebsd-ports References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <20170623023954.GA29157@home.opsec.eu> From: Julian Elischer Message-ID: <856b02db-26b2-91c5-acc6-f62fc99af49e@freebsd.org> Date: Fri, 23 Jun 2017 12:20:35 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170623023954.GA29157@home.opsec.eu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 04:21:01 -0000 On 23/6/17 10:39 am, Kurt Jaeger wrote: > Hi! > >> Mark, I can only suppose that those complainers are dilettantes >> of some sort who believe that having The Latest-And-Greatest Bits >> is a social-status enhancer. **Nobody** with real work to do >> ever willingly fools away time "fixing" what isn't broken. > There's a blog post from one of the folks that explains the > idea behind that 'fast update' mode of operations, and yes, > he's doing real work. > > http://blog.koehntopp.info/index.php/1776-rolling-out-patches-and-changes-often-and-fast/ > That is ONE kind of installation. It only works if you are talking about a software module that is either dynamically delivered (think web apps that are downloaded every time they are run) or at lear often redelivered. (say, a personal system that gets automatic upgrades, a-la slack on OS-X (they seem to have anew version every week or two) It DOES NOT WORK when th most you can upgrade a customer system is once a year or once every two years. That kind of installation basically "follows head". It doesn't need ANY branches. So quarterly branches are of no use to them either. They are a minority of all commercial users, and a completely non existent part of appliance manufacturers, (because you can't do it that way unless you only have 2 customers (*)). * and even then, the customers may only allow you to upgrade every so often. For example Bank of America only allow their FreeBSD machines to be upgraded after a several month testing and burn-in period on a parallel test system with real data and dummy users, and that can obviously only happen on a yearly scale as it costs a lot to do. (ask Devin about the details..it's been a while since I worked on their stuff but I know it's still similar). To be useful any branch must: 1/ not make unneeded changes, but DO include all/most CRITICAL changes. 2/ stay around and be buildable for at least 3 years, preferably 5. Note that a company can take care of point 2 themselves to some extent by mirroring etc. but they probably don't have the expertise to handle all if the critical (security) patches part of the picture. I will add that such users would help their own case by fixing such issues and feeding the changes back to their branches upstream, thus helping maintain the branch. Maybe we could have a system of "corporate sponsors" for these branches. From owner-freebsd-ports@freebsd.org Fri Jun 23 04:23:51 2017 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 99235D9BFE6 for ; Fri, 23 Jun 2017 04:23:51 +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 58AB2770C9 for ; Fri, 23 Jun 2017 04:23:50 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (124-148-108-84.dyn.iinet.net.au [124.148.108.84]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v5N4Ninp062126 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 22 Jun 2017 21:23:47 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Dave Hayes , freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <1498157001.2235.1.camel@gmail.com> From: Julian Elischer Message-ID: Date: Fri, 23 Jun 2017 12:23:39 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 04:23:51 -0000 On 23/6/17 2:57 am, Dave Hayes wrote: > On 06/22/2017 11:43, demelier.david@gmail.com wrote: >> Let me use my example of www/node back. I have built the port www/node >> in poudriere using this origin (so no version). At the time I've built >> it it was a 6.x version. When I upgraded my machine, www/node has >> switched to 7.x version and since this software follows semantic >> versioning, every application using the 6.x branch may or may not work >> anymore. > > I completely agree that an annoying consequence of what the > volunteers are doing with the ports tree. These unwelcome surprises > are the bulk of my non-automated work in creating package repositories. > > Frankly, I also wish this kind of thing would stop. Ultimately my > wishes are irrelevant for reasons far far beyond the scope of this > thread. > >> Now, I'm in a state where if I pull the ports tree, I must check if >> www/node6 still exists or I must not upgrade. >> >> With releases branches I will be sure that: >> >> 1. www/node will *always* be at a 6.x version; >> 2. www/node will still be supported for the version of the FreeBSD >> system. > > That sounds reasonable...yet others will likely expect www/node to > always be the latest version. Perhaps these others might complain > that it is not the latest version and it would be reasonable to have > node always be at the latest version. then at install they should set their packages to follow head, and ignore the branches. > > Would you agree that release branches would be unnecessary if > somehow you could select the version of node that the ports tree > builds via some (as yet unspecified) mechanism? From owner-freebsd-ports@freebsd.org Fri Jun 23 04:28:20 2017 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 5C42DD9C094 for ; Fri, 23 Jun 2017 04:28:20 +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 40C6C771EE for ; Fri, 23 Jun 2017 04:28:20 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (124-148-108-84.dyn.iinet.net.au [124.148.108.84]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v5N4SFG7062141 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 22 Jun 2017 21:28:19 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <775ba90e-a811-4cc8-a729-bdc0dad7774c@FreeBSD.org> <1tlnkc1l8md98dl3teqoab8ds3jutmvavc@4ax.com> From: Julian Elischer Message-ID: <2a455ad3-4918-8599-144a-7cee4449fa90@freebsd.org> Date: Fri, 23 Jun 2017 12:28:10 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 04:28:20 -0000 On 23/6/17 7:28 am, Grzegorz Junka wrote: > > On 22/06/2017 15:50, scratch65535@att.net wrote: >> [Default] On Thu, 22 Jun 2017 15:38:53 +0100, Matthew Seaman >> wrote: >> >>> On 2017/06/22 15:03, scratch65535@att.net wrote: >>>> Why don't the same choices apply here? What am I missing? >>> Two things: >>> >>> 1) It's progress in the development of the FreeBSD base system that >>> drives the release cycle. The general state of the ports does not >>> exert >>> much influence on release frequency -- nor should it. >> Still not getting it, I'm afraid. How often does the base >> system undergo such drastic architecture changes that existing >> ports won't run under it? I haven't really been monitoring the >> situation, but I'd guess it's very seldom if only because such an >> architectural change is a cursĂ«d big job that can hardly ever be >> justfied. >> >> I'd guess that most adults for whom systems are tools not toys >> are not too dissimilar to me: I want to *use* my tools, not >> spend time replacing them every quarter or even every year. As >> long as they do the job and don't compromise the system, they're >> fine by me. I have apps running under Win7 that were written for >> W2K (and in one case NT, iirc), and they're just as useful today >> as they were then. They do the job: why in the name of sanity >> should I replace them? >> > > Not sure how you use your tools or in which industry you work. Take > front-end development for example. here lies the crux of the problem. FreeBSD is often not a front-end software module. It is often used to provision off-line (from a management/administrative perspective) systems. Front end or personal systems can be upgraded day by day. Real products such as routers, proxies, gateways, accounting systems, firewalls etc. can NOT be upgraded every day. you are lucky if the customer allows you to do it once a year. > Chrome is releasing a new version every couple of days. Sure, I > don't upgrade every release, but when I am developing a website, I > want to test using the same version that my customers are using, > which is the latest, since Chrome on Windows updates itself > automatically. The same with new versions of Firefox. Often new > versions of browsers require new versions of libraries to support > new features (CSS/JavaScript). That requires new versions of > compiler and transpilers. They may, in turn, require an updated > version of node or npm. > > Take server-side development as another example. Erlang is releasing > a new version of OTP every couple of weeks. Sure, I don't need a new > version when supporting an old application, but I may need one when > starting a new application. Especially that many libraries that I am > going to use won't support Erlang older than a specific version. > > A similar story with C++ development, where the standard is being > constantly developed and compilers are adding these features every > release. Again, you may not need these new features, but a library > that you need to use may require the new version. > > No matter how long you are going to maintain a specific version of > ports with locked down versions of applications, there will surely > come a time when you will need to upgrade. And for every user that > time will be different. The current model is in my opinion the most > common denominator - we can't maintain multiple branches with past > versions so lets try to properly maintain one with current versions. > > Grzegorz > _______________________________________________ > 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 Jun 23 04:32:01 2017 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 03FF9D9C20E for ; Fri, 23 Jun 2017 04:32:01 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from hermes.heuristicsystems.com.au (hermes.heuristicsystems.com.au [203.41.22.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.heuristicsystems.com.au", Issuer "Heuristic Systems Type 4 Host CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 312B4774AB for ; Fri, 23 Jun 2017 04:31:59 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from [10.0.5.3] (ewsw01.hs [10.0.5.3]) (authenticated bits=0) by hermes.heuristicsystems.com.au (8.15.2/8.15.2) with ESMTPSA id v5N4WIYq021111 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 23 Jun 2017 14:32:27 +1000 (AEST) (envelope-from dewayne.geraghty@heuristicsystems.com.au) X-Authentication-Warning: b3.hs: Host ewsw01.hs [10.0.5.3] claimed to be [10.0.5.3] Subject: Re: NEW APR/APR-Utils To: The Doctor Cc: freebsd-ports@freebsd.org References: <20170622130021.GB41229@doctor.nl2k.ab.ca> <96a2704f-f59a-e16d-26cf-d796ead498db@heuristicsystems.com.au> <20170623032940.GA85792@doctor.nl2k.ab.ca> From: Dewayne Geraghty Message-ID: Date: Fri, 23 Jun 2017 14:29:49 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <20170623032940.GA85792@doctor.nl2k.ab.ca> Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 04:32:01 -0000 Rightly or wrongly I haven't tested with apr-1.6. I pretty much adhere to the versions within /usr/ports. Only when there's a CVE do I break ranks - and usually after I've filed a PR for the (security) issue to be addressed. Sometimes the maintainers' need to have their attention drawn to available updates, which benefits everyone. Unfortunately the PR mechanism is the only tracking mechanism (or poker, depending on your perspective) available to us. From owner-freebsd-ports@freebsd.org Fri Jun 23 04:39:50 2017 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 ACFCBD9C2BB for ; Fri, 23 Jun 2017 04:39:50 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 874F077642; Fri, 23 Jun 2017 04:39:50 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id D4E80734; Thu, 22 Jun 2017 23:39:48 -0500 (CDT) Date: Thu, 22 Jun 2017 23:39:47 -0500 From: Mark Linimon To: Julian Elischer Cc: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170623043947.GA8922@lonesome.com> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 04:39:50 -0000 On Fri, Jun 23, 2017 at 11:58:14AM +0800, Julian Elischer wrote: > What we want is: > A "recent" starting point for our next project/upgrade to start from > and an ongoing version of that, which will get critical fixes only for > at LEAST 2 years, probably 5. > The key here is the *_*critical fixes only*_* part. And how much is that worth to you and/or your company? I mean, honestly. You constantly criticize the volunteers for not doing what you need. Well _need_, to me, implies the existence of some kind of incentive. I can state to you, flatly, that "a feeling of a job well done" isn't _sufficient incentive_ to do professional-level QA. There's a reason people get _paid to do it_: it's hard, long, tedious, unrewarding work, and it never ends. Clearly, relying on _volunteers_ to do professional-level QA isn't working out for you. Thus, IMVVHO, at this point, to get what you _need_, you need to get out your checkbook and provide a _financial_ incentive. In my experience, with the volunteers that we have, we can barely keep things afloat as it is. It's sufficiently hard to recruit people, and burnout is high -- especially given the grief we take. (I won't even start on how even "critical fixes" can drag in the need to update dependencies, which then conflict with each other, and so on and so forth, and thus even "critical fixes" aren't trivial.) Summary: you are providing negative incentive to the ports crew, with no upside for them, and you can't understand why it doesn't work. tl;dr: you want us to be RedHat but with no paid employees. mcl From owner-freebsd-ports@freebsd.org Fri Jun 23 04:49:59 2017 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 C9368D9C556 for ; Fri, 23 Jun 2017 04:49:59 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ACB9777AF1; Fri, 23 Jun 2017 04:49:59 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 12DDDFD0; Fri, 23 Jun 2017 04:49:59 +0000 (UTC) From: Jan Beich To: George Mitchell Cc: freebsd ports Subject: Re: www/libxul References: <1ed10613-f240-31dd-13e5-7271647869d2@m5p.com> Date: Fri, 23 Jun 2017 06:49:46 +0200 In-Reply-To: <1ed10613-f240-31dd-13e5-7271647869d2@m5p.com> (George Mitchell's message of "Thu, 22 Jun 2017 21:03:59 -0400") Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 04:49:59 -0000 George Mitchell writes: > Consequently, the configure script dies at line 26248, complaining > that "Option, jemalloc, does not take an argument (4)". Sorry for the bustage. It should be fixed now. https://svnweb.freebsd.org/changeset/ports/444163 From owner-freebsd-ports@freebsd.org Fri Jun 23 05:22:27 2017 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 9D5E0D9CC03 for ; Fri, 23 Jun 2017 05:22:27 +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 7B8B478749 for ; Fri, 23 Jun 2017 05:22:27 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (124-148-108-84.dyn.iinet.net.au [124.148.108.84]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v5N5MLwS062359 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 22 Jun 2017 22:22:24 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Mark Linimon Cc: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> <20170623043947.GA8922@lonesome.com> From: Julian Elischer Message-ID: <3a428572-039c-79ed-8804-41e5fef4df99@freebsd.org> Date: Fri, 23 Jun 2017 13:22:16 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170623043947.GA8922@lonesome.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 05:22:27 -0000 On 23/6/17 12:39 pm, Mark Linimon wrote: > On Fri, Jun 23, 2017 at 11:58:14AM +0800, Julian Elischer wrote: >> What we want is: >> A "recent" starting point for our next project/upgrade to start from >> and an ongoing version of that, which will get critical fixes only for >> at LEAST 2 years, probably 5. >> The key here is the *_*critical fixes only*_* part. > And how much is that worth to you and/or your company? glad you asked. If we had such a setup it would probably be worth a good part of a person's salary. Since we have had to do without it, we have workarounds in place that took a lot of work to make. But we are now running a parallel system where we are taking snapshots of head and using them. The downside is that we don't have the resources to follow all the Security issues so we are forced to do cross-revision upgrades sometimes where for example all the packages we install were compiled from a tree that approximates 10.3 ports, but the openssl package is from a source tree that is much newer. We enjoy this about as much as having our corporate wisdom teeth pulled out but it's forced on us. In the near future we will be taking a new snapshot for the next release. What branch and revision of the ports tree wil be snapshotted is still not decided, If there were a suitable first-half-2017 stable branch we'd take that for sure, then we'd follow it, merging changes in, and probably feeding fixes back. Since there are no "security patch only" branches, What we will probably end up doing is snapshotting head and crossing our fingers hoping that we notice any relevant vulnerabilities and have the time to work out a fix. Of course If there is no easy patch, we may have to do single-package upgrades, which is usually only painless for a short time after the snapshot, because the Makefile infrastructure keeps changing. > > I mean, honestly. You constantly criticize the volunteers for not doing > what you need. Well _need_, to me, implies the existence of some kind > of incentive. I can state to you, flatly, that "a feeling of a job well > done" isn't _sufficient incentive_ to do professional-level QA. There's > a reason people get _paid to do it_: it's hard, long, tedious, unrewarding > work, and it never ends. > > Clearly, relying on _volunteers_ to do professional-level QA isn't working > out for you. > > Thus, IMVVHO, at this point, to get what you _need_, you need to get out > your checkbook and provide a _financial_ incentive. In my experience, > with the volunteers that we have, we can barely keep things afloat as > it is. It's sufficiently hard to recruit people, and burnout is high > -- especially given the grief we take. > > (I won't even start on how even "critical fixes" can drag in the need > to update dependencies, which then conflict with each other, and so on > and so forth, and thus even "critical fixes" aren't trivial.) > > Summary: you are providing negative incentive to the ports crew, with > no upside for them, and you can't understand why it doesn't work. > > tl;dr: you want us to be RedHat but with no paid employees. > > mcl > From owner-freebsd-ports@freebsd.org Fri Jun 23 05:23:36 2017 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 24168D9CC90 for ; Fri, 23 Jun 2017 05:23:36 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0F3BE78827 for ; Fri, 23 Jun 2017 05:23:36 +0000 (UTC) (envelope-from lists@opsec.eu) Received: by mailman.ysv.freebsd.org (Postfix) id 0B8C8D9CC8F; Fri, 23 Jun 2017 05:23:36 +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 0B2D2D9CC8E for ; Fri, 23 Jun 2017 05:23:36 +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 C1E6B78825; Fri, 23 Jun 2017 05:23:35 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dOH4A-0007qx-Pm; Fri, 23 Jun 2017 07:23:34 +0200 Date: Fri, 23 Jun 2017 07:23:34 +0200 From: Kurt Jaeger To: Julian Elischer Cc: freebsd-ports Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170623052334.GC29157@home.opsec.eu> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <20170623023954.GA29157@home.opsec.eu> <856b02db-26b2-91c5-acc6-f62fc99af49e@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <856b02db-26b2-91c5-acc6-f62fc99af49e@freebsd.org> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 05:23:36 -0000 Hi! > > There's a blog post from one of the folks that explains the > > idea behind that 'fast update' mode of operations, and yes, > > he's doing real work. > > http://blog.koehntopp.info/index.php/1776-rolling-out-patches-and-changes-often-and-fast/ > That is ONE kind of installation. Well, there's the thinking that in the not-to-far future, everything is connected, and you'll need to be able to update at any time because of whatever security/threat that IT ecosystem throws at you. > It DOES NOT WORK when th most you can upgrade a customer system is > once a year or once every two years. The 'other side' of the debate thinks: Well, if they think this is the way to do it, they have a problem and need to change their procedures. The viewpoint is: That system can start debating with the next worm/trojan coming along, but that won't help. The assumption is: everything is connected/on the internet, and not even voluntarily. Think connected cars, IoT etc. > I will add that such users would help their own case by fixing such > issues and feeding the changes back to their branches upstream, > thus helping maintain the branch. Maybe we could have a system of > "corporate sponsors" for these branches. Given the state of fundraising in open source, I doubt that this will be viable. -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-ports@freebsd.org Fri Jun 23 05:36:38 2017 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 11074D9CEF9 for ; Fri, 23 Jun 2017 05:36:38 +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 EB23A78BAB for ; Fri, 23 Jun 2017 05:36:37 +0000 (UTC) (envelope-from julian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id E6C31D9CEF8; Fri, 23 Jun 2017 05:36: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 E653CD9CEF7 for ; Fri, 23 Jun 2017 05:36:37 +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 BFA3578BAA for ; Fri, 23 Jun 2017 05:36:37 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (124-148-108-84.dyn.iinet.net.au [124.148.108.84]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v5N5aWms062404 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 22 Jun 2017 22:36:35 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Kurt Jaeger Cc: freebsd-ports References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <20170623023954.GA29157@home.opsec.eu> <856b02db-26b2-91c5-acc6-f62fc99af49e@freebsd.org> <20170623052334.GC29157@home.opsec.eu> From: Julian Elischer Message-ID: <85832c4b-fa02-d205-7296-0b48c186c9a9@freebsd.org> Date: Fri, 23 Jun 2017 13:36:26 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170623052334.GC29157@home.opsec.eu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 05:36:38 -0000 On 23/6/17 1:23 pm, Kurt Jaeger wrote: > Hi! > >>> There's a blog post from one of the folks that explains the >>> idea behind that 'fast update' mode of operations, and yes, >>> he's doing real work. >>> http://blog.koehntopp.info/index.php/1776-rolling-out-patches-and-changes-often-and-fast/ >> That is ONE kind of installation. > Well, there's the thinking that in the not-to-far future, everything > is connected, and you'll need to be able to update at any time > because of whatever security/threat that IT ecosystem throws at you. > >> It DOES NOT WORK when th most you can upgrade a customer system is >> once a year or once every two years. > The 'other side' of the debate thinks: Well, if they think this > is the way to do it, they have a problem and need to change > their procedures. > > The viewpoint is: That system can start debating with the next > worm/trojan coming along, but that won't help. The assumption > is: everything is connected/on the internet, and not even > voluntarily. > > Think connected cars, IoT etc. > >> I will add that such users would help their own case by fixing such >> issues and feeding the changes back to their branches upstream, >> thus helping maintain the branch. Maybe we could have a system of >> "corporate sponsors" for these branches. > Given the state of fundraising in open source, I doubt that this > will be viable. My personal experience is that if it were put in the form of an annual s subscription, most mid sized corporate finance offices wouldn't blink at $20k if they thought it was an important part of their product. (that's the key) Some wouldn't blink at 50K. ("the software is free but we need to help pay for people to do real work to keep it safe, it'll save us (some fraction of) a full time person"). The problem is that such a set of sponsored branches does not exist so knowing who'd sign up and who would't is just guesswork, and the companies have made "alternative arrangements" whether that means somewhat forgoing the ports tree (e.g Vicor) or building an infrastructure around ports head ( e.g. Panzura), or having some other snapshotting system ( e.g Ironport/Cisco) From owner-freebsd-ports@freebsd.org Fri Jun 23 06:07:42 2017 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 D579BD9D4BD for ; Fri, 23 Jun 2017 06:07:42 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id BAB6A79727 for ; Fri, 23 Jun 2017 06:07:42 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mailman.ysv.freebsd.org (Postfix) id B041BD9D4BC; Fri, 23 Jun 2017 06:07: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 AFE1AD9D4BB for ; Fri, 23 Jun 2017 06:07:42 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 903CE79726; Fri, 23 Jun 2017 06:07:41 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 4E97384E; Fri, 23 Jun 2017 01:07:35 -0500 (CDT) Date: Fri, 23 Jun 2017 01:07:34 -0500 From: Mark Linimon To: Julian Elischer Cc: Kurt Jaeger , freebsd-ports Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170623060734.GA9391@lonesome.com> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <20170623023954.GA29157@home.opsec.eu> <856b02db-26b2-91c5-acc6-f62fc99af49e@freebsd.org> <20170623052334.GC29157@home.opsec.eu> <85832c4b-fa02-d205-7296-0b48c186c9a9@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <85832c4b-fa02-d205-7296-0b48c186c9a9@freebsd.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 06:07:42 -0000 On Fri, Jun 23, 2017 at 01:36:26PM +0800, Julian Elischer wrote: > The problem is that such a set of sponsored branches does not exist so > knowing who'd sign up and who would't is just guesswork And that's why neither myself or the other people who have in the past considered such a business have gone into it. I rejected it as "a fantastic way to work hard and lose tons of money". I've had enough of those in my career, thanks. mcl From owner-freebsd-ports@freebsd.org Fri Jun 23 06:09:29 2017 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 577D2D9D578 for ; Fri, 23 Jun 2017 06:09:29 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 32F4179808; Fri, 23 Jun 2017 06:09:28 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 0424184E; Fri, 23 Jun 2017 01:09:28 -0500 (CDT) Date: Fri, 23 Jun 2017 01:09:26 -0500 From: Mark Linimon To: Julian Elischer Cc: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170623060926.GB9391@lonesome.com> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> <20170623043947.GA8922@lonesome.com> <3a428572-039c-79ed-8804-41e5fef4df99@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3a428572-039c-79ed-8804-41e5fef4df99@freebsd.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 06:09:29 -0000 You didn't read (or ignored) the last half of my post. Whatever. I'll go back to what I was doing before, e.g., cleaning up other people's messes. Your first two guesses of "what type of commit bits made the messes" don't count. mcl From owner-freebsd-ports@freebsd.org Fri Jun 23 08:26:16 2017 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 B4943D9F3CE for ; Fri, 23 Jun 2017 08:26:16 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::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 361577C76A for ; Fri, 23 Jun 2017 08:26:16 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: by mail-wr0-x229.google.com with SMTP id r103so55482798wrb.0 for ; Fri, 23 Jun 2017 01:26:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:in-reply-to:references:mime-version :content-transfer-encoding; bh=hHLQtP9fIu3nDA+1iQVhpu330HHP/+AOnHftyWOnTpQ=; b=mrpyT/FbkkWibVJf57VsD4amYy+iQ/AKX78/ozd6s9W4nDyMKR6NwJHzl/sHf/Rone 71avJ1w00+JWs2+vSA4I5+ZQCpoqh/JN50CfhSCd/vWDXe3CICzLLA0jiARYhMUWmzJ1 6dqi9qMqrG+RXb2g6qrlY6PH0/k10BZORQHFf2/S6/UH2pEVNCH6GNBn0/1JxJi3insX Jwa1CUXmQzoRxGf7mgcXN8a5UHFKXUnEf/VP6zdy4H8GwCvCuWfrXOdAPcdVxmmFGbnH S3wifOrMon7inei53m76Lx6mWDNQ6/Kgi/u0RVBrraZX1z60L8Md7nuv/ws6fMvTKdV/ T6ow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=hHLQtP9fIu3nDA+1iQVhpu330HHP/+AOnHftyWOnTpQ=; b=qaICJyZvR+lBqLJGbwU2CtKua8N4HIWEpv0BO4z3cs8gWH2nH2p7SGdtCv7axDgs7R knR0KFcmXJT2it2PYuUaQhTnKsRmEpVSirM9OdVHdUFnTYAjUFbw8XxmHwORPIP1amOJ pEJ9/VhOHVWxiOijiith+38eYjKbsfx8ZCD7tKWwCfPKHyZiMSIGLiWFEqbMDlUsM4sy cg2GL4Gdl4dyenKzaKHXtW7E0e+9wHzvp6HHbEfhbouDjmcyyIbnZ4gwE7G0hd5m4OZt DdnlGMWvIz5aeX6qkxCt4VkYFzJUATpaZMUxaM0XYAalkzJPH6bDM+oi3EPxg7k0KK3B dDbg== X-Gm-Message-State: AKS2vOxcHfDEWXda4V1Hg6KlldA/ckxhdZ6vASg47Se/K62laWCEDWl3 G26AhndTncMUmQiyuOM= X-Received: by 10.223.171.181 with SMTP id s50mr5081839wrc.177.1498206374331; Fri, 23 Jun 2017 01:26:14 -0700 (PDT) Received: from 15.2.0.10.rev.sfr.net (9.128.158.77.rev.sfr.net. [77.158.128.9]) by smtp.gmail.com with ESMTPSA id j13sm8316101wra.56.2017.06.23.01.26.13 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 23 Jun 2017 01:26:13 -0700 (PDT) Message-ID: <1498206372.2506.1.camel@gmail.com> Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version From: demelier.david@gmail.com To: freebsd-ports@freebsd.org Date: Fri, 23 Jun 2017 10:26:12 +0200 In-Reply-To: References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <1498157001.2235.1.camel@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.2 (3.24.2-1.fc26) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 08:26:16 -0000 On Thu, 2017-06-22 at 11:57 -0700, Dave Hayes wrote: > Would you agree that release branches would be unnecessary if > somehow > you could select the version of node that the ports tree builds via > some > (as yet unspecified) mechanism? I've also think about that but I'm not sure if it's easier than having frozen release branches. Release branches won't have many maintenance except individual bug fixes when security advisories are found. No backport, no updates. On the other hand, having to deal case-by-case for which ports should have version is very hard and complex. It's the case of some of them, node, postgresql, apache. But then we will have thousands of ports to add just to provides different versions. Cheers, -- David Demelier From owner-freebsd-ports@freebsd.org Fri Jun 23 08:31:27 2017 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 609A3D9F559 for ; Fri, 23 Jun 2017 08:31:27 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::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 DD7DD7C8F4 for ; Fri, 23 Jun 2017 08:31:26 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: by mail-wr0-x235.google.com with SMTP id 77so55627469wrb.1 for ; Fri, 23 Jun 2017 01:31:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:in-reply-to:references:mime-version :content-transfer-encoding; bh=REgW+YzMQXH8sNY/lfKwHCQEHRIX8Hqg75oYK85CGCg=; b=EVIcHtZTRrNSenkuislchPEqKFGLMlW31VBNSdnjmMcoxvXYQdDohilWbRM1ZVWGpq 8C3p7OLl2hB225fI3qWODb5Dgf2LE+jAoQW8jr73KVshdDCMM5OvbUUdncdLizUWyOeO +SsZWZq6/zvySLn0pc+5j2vSenwQA6bn4fMf8RRrCXDsUUie3NqQFWWgn/CrymutWM7H UeLunkj5OYHb0crXTEx09fuHMh6V4s771NWC/buzWKm8K3M5QuQywnhT3/WujwqizTYr n63XGPc84dsQkJV87ltg1kWAY4VGEqRAZb4TVJD2j2XKrCbThp+FF8jkWB5oEH/I6sVT GJAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=REgW+YzMQXH8sNY/lfKwHCQEHRIX8Hqg75oYK85CGCg=; b=dMEMR6MZnhhGa+70dDkocz6TjPNyQMSySF0pcYavcQhq6ifSftqGf5oE5sBBwDrWTQ iHBVW0jaAbamPVeQutr1ZAzKjqmTJuvaP6nm7E+gb2uBB4yZFnnCDOK0K6XDBXypHmbV cX0K+owflBSfWx3Ek7nUJoiy0B9xeKgODBjyzng6dbl8yqARJDdqw6WVVSfWfd7UQ6OP LKpQwvLT2bwvN7CDeG24VDv6t8Tp8g//36ZbzwanNxD/jdE85pXldHgr/ZqcFBNhybZA SatZIuUskcYmumjhq4Nkbp7TqVFc/JmoeQ/d+AM6icCJx34sPTECzP8zxEMqJ5VaN96/ 3ORQ== X-Gm-Message-State: AKS2vOzWj8Tp9teH2Yed0u4SP7+oGzbrlknPse+XmGG7xmj9ei0CDG4w 392XMyg+PqIyE3cGLZw= X-Received: by 10.28.94.144 with SMTP id s138mr4676083wmb.32.1498206684947; Fri, 23 Jun 2017 01:31:24 -0700 (PDT) Received: from 15.2.0.10.rev.sfr.net (9.128.158.77.rev.sfr.net. [77.158.128.9]) by smtp.gmail.com with ESMTPSA id z75sm3394965wmz.8.2017.06.23.01.31.23 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 23 Jun 2017 01:31:24 -0700 (PDT) Message-ID: <1498206683.2506.2.camel@gmail.com> Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version From: demelier.david@gmail.com To: freebsd-ports@freebsd.org Date: Fri, 23 Jun 2017 10:31:23 +0200 In-Reply-To: <19474ced-28cf-917d-4642-cb8a501bd56f@gjunka.com> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <19474ced-28cf-917d-4642-cb8a501bd56f@gjunka.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.2 (3.24.2-1.fc26) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 08:31:27 -0000 On Fri, 2017-06-23 at 00:31 +0000, Grzegorz Junka wrote: > A user would probably start with precompiled packages. Only power > users > who know what they are doing would try to compile the packages > themselves, and at that point I would expect them to know a thing or > two > about verifying that they compile and work fine. Precompiled packages are updated as well nowadays. From owner-freebsd-ports@freebsd.org Fri Jun 23 08:38:32 2017 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 5D465D9F6F2 for ; Fri, 23 Jun 2017 08:38:32 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: from mx.irealone.hr (xoth.irealone.hr [136.243.79.146]) (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 18D947CE46 for ; Fri, 23 Jun 2017 08:38:31 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mx.irealone.hr (Postfix, from userid 58) id 6F3264586; Fri, 23 Jun 2017 10:38:27 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on postfix.xoth.irealone.hr X-Spam-Level: X-Spam-Status: No, score=-101.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, LOCAL_WL_002 autolearn=ham autolearn_force=no version=3.4.1 Received: from mail.irealone.com (unknown [10.0.0.10]) by mx.irealone.hr (Postfix) with ESMTP id EE9574582 for ; Fri, 23 Jun 2017 10:38:26 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 23 Jun 2017 10:38:26 +0200 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Organization: Acheron Media In-Reply-To: <1498206372.2506.1.camel@gmail.com> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <1498157001.2235.1.camel@gmail.com> <1498206372.2506.1.camel@gmail.com> Message-ID: <00d078be50a83b6e18ef20bfe76e30ca@acheronmedia.hr> X-Sender: vlad-fbsd@acheronmedia.com User-Agent: Roundcube Webmail/1.2.5 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 08:38:32 -0000 On 2017-06-23 10:26, demelier.david@gmail.com wrote: > > Release branches won't have many maintenance except individual bug > fixes when security advisories are found. No backport, no updates. Nothing prevents the maintainers from doing exactly that right now. But you see, there are two kinds of ports in the tree: 1) ports where upstream maintains a concept of LTS 2) ports that mix bug, security fixes and new features in even point.point releases For some (all?) major production software like Apache, nginx, PHP, PostgreSQL, MySQL (I think?), Postfix, Dovecot2, etc... #1 applies. So for serious production servers this should be easy to maintain as the upstream is doing that in the first place. The problem is then with ports of type #2. And there's lots of them. Gentoo portage can easily maintain "stable" ports because portage doesn't have a single Makefile, it has multiple .ebuild files so multiple versions are available under ONE port name, and bumping the version while keeping previous ones available is literally just a matter of making a copy of the latest .ebuild and fixing the version in it like we do with PORTVERSION. On FreeBSD that's impossible and often ports are separated and version baked into the port name. Like www/node from the original post of this thread. But again, that's all doable without having to introduce new infrastructure. The ports tree as is can be maintained like this and quarterly repos would NOT be required. All it's needed is for maintainers to keep a stable version and a latest version. There's already plenty of ports done like that, otoh postfix and postfix-current, nginx and nginx-devel, etc... Because the BIGGEST problem in maintaining separate "stable" or LTS branches is BACKPORTING fixes for ports in the #2 category, ie. those that mix new features with fixes, so you have to CHERRY PICK only the fix and BACKPORT it to your "stable" branch. And that's even more work often introducing NEW bugs. BTW, the problem of the original post could've been avoided if the user only read UPDATING which clearly stated that www/node becomes 7 and previous node (6) becomes www/node6. (20161207) entry. -- Vlad K. From owner-freebsd-ports@freebsd.org Fri Jun 23 08:47:49 2017 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 65111D9F9C1 for ; Fri, 23 Jun 2017 08:47:49 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (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 EA95E7D3BD for ; Fri, 23 Jun 2017 08:47:48 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: by mail-wr0-x242.google.com with SMTP id 77so10819588wrb.3 for ; Fri, 23 Jun 2017 01:47:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:in-reply-to:references:mime-version :content-transfer-encoding; bh=X3Dl4oJqH9xePoh27M6/tCvdr4BfMdohCUXNGvyN318=; b=s/LB8ca7VqpZ9ipp2LNXc6vdGcvD6Qsu9xHGMizS+Hu95NC0jDy7kiwUjb2IaH0Vvs XaTnh9Lq1j0TRh1uvGyBTvAw+Vi5GRDTZneQU/u265R3TPLRBgCMfdAFWQtWSm3MKEcm GfKFF4eQEYIkAnHUZ7nNrW6RC1K/xd9QFw1pEEBueK3UFhlfJitvlV34JnTI/YFrI1Rm v9jH4hQCFVmcpKXHj6Iux69U5XtFMOzF5zj3JrrMueH3mLq4qlUyfeovQ6DC2+qWEjFz xHl4674wyHoDj/iUI6j4WQG1VP9t8qjBAWR+/2kHmVrZubDC3PGgwhtTDYqmT1cYRY58 bK7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=X3Dl4oJqH9xePoh27M6/tCvdr4BfMdohCUXNGvyN318=; b=MwiLJ2AaSTRx4WXCOy5FqVrbudOgV6QX28tcn+ALSjg1VqDnOeWYTGbWGHw2YccO5y NtRyo6kdwptEixu3IPFIxp4MUQjhBNy2wlbit71RT4Wwd+C+6fleTpiocE2BGHwa2KMM V/70VhnWEvIbj7q2dKNdkneYEQBsceQMIILvpi9Kh8GOFGIeZ5++gofhn0TOMhxW/V/4 pXACszsGYgCkr7bjD3XUjJzycBu3npkwlwtghhef2le1QT66clzlJhMG5Tp9UJpgFtls w9UvV/ly4vTU6bXO4QUs72JagYHaAu2k13GWYAIvk8VNgh2+Hu4cE81UWI6t8Dsf3A7/ Flxw== X-Gm-Message-State: AKS2vOzXl6WLHh0gF1M8YdcPuknkYGXdRpR2ZFth5Zs6/JgokX8EIBky yYW6RsXiMpM5lyZMSGM= X-Received: by 10.28.158.206 with SMTP id h197mr4518027wme.110.1498207667045; Fri, 23 Jun 2017 01:47:47 -0700 (PDT) Received: from 15.2.0.10.rev.sfr.net (9.128.158.77.rev.sfr.net. [77.158.128.9]) by smtp.gmail.com with ESMTPSA id l12sm5017170wrc.46.2017.06.23.01.47.46 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 23 Jun 2017 01:47:46 -0700 (PDT) Message-ID: <1498207665.2506.4.camel@gmail.com> Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version From: demelier.david@gmail.com To: freebsd-ports@freebsd.org Date: Fri, 23 Jun 2017 10:47:45 +0200 In-Reply-To: <20170622211126.GA6878@lonesome.com> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.2 (3.24.2-1.fc26) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 08:47:49 -0000 On Thu, 2017-06-22 at 16:11 -0500, Mark Linimon wrote: > On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65535@att.net wrote: > > My problem is that my industry experience tells me that reducing > > the frequency of port releases is practically *guaranteed* to be > > a Really Good Thing for everyone. > > I remember before we had the quarterly releases, and people on the > mailing lists complained constantly about the ports bits only being > available once per release, or rolling with -head. > Quarterly branches do not solve anything. A user installs a machine on March, it uses 2017Q1. Then in April an additional software must be installed, as we are in April, 2017Q2 is available so two choices: a. the user keeps 2017Q1 but won't have any security fixes as it is not maintained anymore; possibly having security flaws. b. the user switches to 2017Q2, this tree will probably have major upgrades and possibly breaking existing stuff. To me, quarterly branches are completely useless as they are not maintained enough in time. Replacing them with release branches would solve everything explained in this thread. Regards, -- David Demelier From owner-freebsd-ports@freebsd.org Fri Jun 23 08:53:49 2017 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 7957AD9FC2A for ; Fri, 23 Jun 2017 08:53:49 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) 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 399DB7D761 for ; Fri, 23 Jun 2017 08:53:48 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3wvC0p5nB8zb56; Fri, 23 Jun 2017 10:53:46 +0200 (CEST) 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 9YFazv5Rrs8N; Fri, 23 Jun 2017 10:53:45 +0200 (CEST) Received: from tommy.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Fri, 23 Jun 2017 10:53:45 +0200 (CEST) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: demelier.david@gmail.com, freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <1498157001.2235.1.camel@gmail.com> <1498206372.2506.1.camel@gmail.com> From: Guido Falsi Message-ID: <666bfe8c-f27d-2c11-2a4a-07da43bb7931@FreeBSD.org> Date: Fri, 23 Jun 2017 10:53:44 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <1498206372.2506.1.camel@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 08:53:49 -0000 On 06/23/17 10:26, demelier.david@gmail.com wrote: > On Thu, 2017-06-22 at 11:57 -0700, Dave Hayes wrote: >> Would you agree that release branches would be unnecessary if >> somehow >> you could select the version of node that the ports tree builds via >> some >> (as yet unspecified) mechanism? > > I've also think about that but I'm not sure if it's easier than having > frozen release branches. I usually stay away from this kind of threads, but I'd like to point out a very simple concept that has not been expressed. The ports tree repository is fully open source, available via subversion from the FreeBSD project and also mirrored on github. There is absolutely nothing stopping you(and anyone with time, skill and willingness to help you) from starting your fork from whichever source and using whatever tool you prefer, creating the branches you're describing. If your model works fine I'm quite sure the FreeBSD community and project will be quite happy to embrace it. As stated, the FreeBSD project (core, portmgr and committers) perceive a manpower problem in relation to implementing what you describe. In this thread it has been stated that such a manpower problem does not really exist. I cannot think of a better way to show there actually is no manpower problem than creating a working example of such a workflow maintained by just a few people with little effort, as you said repeatedly. On other hand demanding and/or insisting that others implement your idea when they clearly disagree with you is not very constructive. In relation to the suggestion of a stable or release ports branch: I'd also like a ports branch where things are merged only when really needed, some kind of "stable" branch. I don't like the release way you describe, but maybe it could actually work as an option, but I too see the manpower problem. An actual working proof of concept like I described above is the only thing that would persuade me I'm wrong about that. (I could try to help with such an experiment but I don't know how much time I could really spare for it) -- Guido Falsi From owner-freebsd-ports@freebsd.org Fri Jun 23 08:56:54 2017 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 59ED5D9FD41 for ; Fri, 23 Jun 2017 08:56:54 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from mail.abinet.ru (mail.abinet.ru [84.52.119.162]) by mx1.freebsd.org (Postfix) with ESMTP id 1C23B7D92A for ; Fri, 23 Jun 2017 08:56:53 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from sphinx.abinet.ru (unknown [192.168.2.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 8789B5F10 for ; Fri, 23 Jun 2017 08:51:17 +0000 (UTC) To: freebsd-ports@freebsd.org From: abi Subject: [SAMBA] and file content caching Message-ID: Date: Fri, 23 Jun 2017 11:51:15 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=abinet.ru; s=dkim; t=1498207878; h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding; bh=EOvcG7v+e0uk6V6g6TwVNBPu/n+jzn5Ji9OkP0kzimQ=; b=EP+MbL6q9bv9lvSJksqIxAAgNUJm1UKdxNA29mP/Oh0veutDNuSGXPfJoRYUO5FnoSzn8C qYxBahRFVG/9dyI2N/HOpRQ4/d23mEHCJjbsXQD+tZ7RLtTypEe0GEIt50RwpuBt/FRN1t I2L+0w1gsQp7iCNaxHFwUmgLa2JLqq8= X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 08:56:54 -0000 Hello, I need to organize file exchange between between daemon and windows program. Daemon is sitting in jail, windows - in bhyve, both on the same host. Daemon is writing lines into file, windows program reads them. The obvious choose was to install samba46 into jail and provide share to windows. I opened 445 port, so I suppose I use SMB2. However, looks like file contents are cached on windows site. After line inserted on FreeBSD side I see outdated file in windows for quite amount of time. (maybe, it's minute!). Is this due to inotify not available on FreeBSD ? I found this article and set setting to 0, but they are not affecting the issue https://technet.microsoft.com/en-us/library/ff686200(v=ws.10).aspx I ticked FAM option for samba, can it be bug into it ? Suggestions are welcome. I never expected that I'd hit issue in so simple task, it's so frustrating =/ From owner-freebsd-ports@freebsd.org Fri Jun 23 09:04:58 2017 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 95AECDA02C3 for ; Fri, 23 Jun 2017 09:04:58 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (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 3F2C17E000 for ; Fri, 23 Jun 2017 09:04:58 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from ox-dell39.ox.adestra.com (unknown [85.199.232.226]) (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 2D979C64F for ; Fri, 23 Jun 2017 09:04:56 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/2D979C64F; dkim=none; dkim-atps=neutral Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <1498207665.2506.4.camel@gmail.com> From: Matthew Seaman Message-ID: <051a31cc-8904-a633-e6da-1fbf8380c07c@freebsd.org> Date: Fri, 23 Jun 2017 10:04:40 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <1498207665.2506.4.camel@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="lpMv28KEOCvrck7P54h0ntKRgAxCQQfBl" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 09:04:58 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --lpMv28KEOCvrck7P54h0ntKRgAxCQQfBl Content-Type: multipart/mixed; boundary="x5sRd4KRVT2GhshspEeMrOXX9bH7HidgR"; protected-headers="v1" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: <051a31cc-8904-a633-e6da-1fbf8380c07c@freebsd.org> Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <1498207665.2506.4.camel@gmail.com> In-Reply-To: <1498207665.2506.4.camel@gmail.com> --x5sRd4KRVT2GhshspEeMrOXX9bH7HidgR Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 06/23/17 09:47, demelier.david@gmail.com wrote: > On Thu, 2017-06-22 at 16:11 -0500, Mark Linimon wrote: >> On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65535@att.net wrote: >>> My problem is that my industry experience tells me that reducing >>> the frequency of port releases is practically *guaranteed* to be >>> a Really Good Thing for everyone. >> >> I remember before we had the quarterly releases, and people on the >> mailing lists complained constantly about the ports bits only being >> available once per release, or rolling with -head. >> >=20 > Quarterly branches do not solve anything. >=20 > A user installs a machine on March, it uses 2017Q1. Then in April an > additional software must be installed, as we are in April, 2017Q2 is > available so two choices: >=20 > a. the user keeps 2017Q1 but won't have any security fixes as it is not= > maintained anymore; possibly having security flaws. >=20 > b. the user switches to 2017Q2, this tree will probably have major > upgrades and possibly breaking existing stuff. >=20 > To me, quarterly branches are completely useless as they are not > maintained enough in time. Replacing them with release branches would > solve everything explained in this thread. Just responding to a message in this thread at random, and not specifically directed at the person whose message I'm replying to. This thread is exactly the sort of sterile argument that the brand new FCP process was invented to handle. https://github.com/freebsd/fcp Read the fcp-0000.md document for details on how the process works. If sufficient people really do want to change the way the ports are branched, then write a proposal. You're going to need to think about it carefully, and consider the needs of all ports users, not just your own specific case. Plus it will need to be achievable with the resources available. If you can get enough people behind your proposal to swing a vote by core, then changes will happen. Cheers, Matthew --x5sRd4KRVT2GhshspEeMrOXX9bH7HidgR-- --lpMv28KEOCvrck7P54h0ntKRgAxCQQfBl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEGfFU7L8RLlBUTj8wAFE/EOCp5OcFAllM2agACgkQAFE/EOCp 5Od+Dw//eaZUo1PGMBZWBpEdcW/XYBFETuF7MQ7PCAjx0APtnOky6wVvYLWy/gky yhgVDCaWwbIemqOoau2mGTTkCF9jali5mR//8rkhswKyJgGCv9wY2GHKjF1Mt9Zy S7C3BqZv/o5vlXXiG0z8vf8glbFhuxPorChXUe0DWiNLg/ORdzgapbtA7xmBGN5M NftC6TzyB5PMpcpO6d3ObIDgueO5PbVknEciccEVNdgRfRriqVLW9qXkhzDUlYYF furlACBIMKzhnkggkSwlArwUKZYNHY9Wm2FKJQfhyhbzKzb4KUUlV1zQzPrCig8U L9lfDBPpeHGcqTZtItAX8OFRyWEoY2NWfyuK+VC8nKJPoOxbh+f1R/Fwr82RPWib eoYinh8sZnn0u22LVAfbNnzusi1mHlX7WucbJHnveV0pXNRK6qx5rAf7dLlIeT4g gAOJQ6J0gJFMxGWsAivtBuxuUFtoNDcggplW71Pg23IcElT41yTamAyR5qPYuESG V34XY6NEspyTwvaFWaF09bXrMUEDMk+teibTmwuPcD+GeyjroS16QIFzwbMYF3c+ 53xlfZdREUWq13AR3+Frw/kOJO5oPD0I65JZWc+BwTt15/x6CbDL8Sr8dD+QQ4IM S/B1Bit2hff0VBTXz61qjTeKMYtLC5n5Ar0H57Sq9n8c96Celog= =b8It -----END PGP SIGNATURE----- --lpMv28KEOCvrck7P54h0ntKRgAxCQQfBl-- From owner-freebsd-ports@freebsd.org Fri Jun 23 09:35:06 2017 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 AB5CBDA0923 for ; Fri, 23 Jun 2017 09:35:06 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::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 27E957EE24 for ; Fri, 23 Jun 2017 09:35:06 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: by mail-wr0-x22f.google.com with SMTP id k67so57360637wrc.2 for ; Fri, 23 Jun 2017 02:35:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:in-reply-to:references:mime-version :content-transfer-encoding; bh=JxZC4FCOnlbUMJZmWSWA5e/yExJ5z8CFWYzSRmJrY1Y=; b=dsuNlmQxfHfg/Zfr/l3aHf17AtwwT4gVm8sBb+9cWHH8mUqlOS07HFIHyPNzmtTfLH vJtOfL8mHo9m8YUSukfVSRy0VEOgzpOp+C02j7BDFMohduboE25LK8EPtONFsR5htSj/ mey6OzQDbI2xSDORjCd0aWptm/fCTraWOPwvaKK6w3uU5X+BbFdHR/yoVNWQroaGfTTe YJTXmyoC6JQtWbrXeupDpk1BRLFCztqcpCo4ughGsrF4JkGzXX00pEE6Jqre1Pi4QzTr N+PCes9TiHjZhDkhMiZhHuHZ/9HkWH3ACS9Fd7YQnTV2IpVPcSULr8D7VPOxjjJvLWNM n81A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=JxZC4FCOnlbUMJZmWSWA5e/yExJ5z8CFWYzSRmJrY1Y=; b=svCmpHHWKkaev80FZZmG5rE8EKvWiJwa0HgD6UOWUnD+4svB4T6B65AMKf8cWuwcJe ymzc7I/cSTnw5gQYmBW1S+5eMYJpZHitX7Mbg+kx9UcVsBHycGfg4ZpgqHdQEgaZi9Tw lOyNmbvMycRc27dZUCLwwas86NbDFV1mGb1KhKZk+Ld77IDUwMJCtqPyhpwVlaFvyR6R 9V0tQqrHkiAWXaO2wF9DQYG9r2labLiBjOWh58xTHAKJr8MSG/P3sL4WbMLXxUROYLES UQfdIWq2voCQ6pfmG/KfWv4M5ndUC05ADhFQlUiCK6HDbBBRqh9xm+Y8eWugbC83WWcH tQuA== X-Gm-Message-State: AKS2vOyk/MSmw57lh6Iv+qE3yUtUAEf5JCC4IXUdig+HbZV2F4KWjZHO 6qA3248KW+DPvVI4oFE= X-Received: by 10.223.155.150 with SMTP id d22mr4749093wrc.193.1498210503258; Fri, 23 Jun 2017 02:35:03 -0700 (PDT) Received: from 15.2.0.10.rev.sfr.net (9.128.158.77.rev.sfr.net. [77.158.128.9]) by smtp.gmail.com with ESMTPSA id c71sm3441736wmh.21.2017.06.23.02.35.02 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 23 Jun 2017 02:35:02 -0700 (PDT) Message-ID: <1498210501.2506.6.camel@gmail.com> Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version From: demelier.david@gmail.com To: freebsd-ports@freebsd.org Date: Fri, 23 Jun 2017 11:35:01 +0200 In-Reply-To: <00d078be50a83b6e18ef20bfe76e30ca@acheronmedia.hr> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <1498157001.2235.1.camel@gmail.com> <1498206372.2506.1.camel@gmail.com> <00d078be50a83b6e18ef20bfe76e30ca@acheronmedia.hr> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.2 (3.24.2-1.fc26) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 09:35:06 -0000 On Fri, 2017-06-23 at 10:38 +0200, Vlad K. wrote: > But again, that's all doable without having to introduce new > infrastructure. The ports tree as is can be maintained like this and > quarterly repos would NOT be required. All it's needed is for > maintainers to keep a stable version and a latest version. There's > already plenty of ports done like that, otoh postfix and > postfix-current, nginx and nginx-devel, etc... Yes but again if not all ports follow this system, we still have the problem of having potential major upgrades. > Because the BIGGEST problem in maintaining separate "stable" or LTS > branches is BACKPORTING fixes for ports in the #2 category, ie. > those > that mix new features with fixes, so you have to CHERRY PICK only > the > fix and BACKPORT it to your "stable" branch. And that's even more > work > often introducing NEW bugs. Release branches do not need backports. > BTW, the problem of the original post could've been avoided if the > user > only read UPDATING which clearly stated that www/node becomes 7 and > previous node (6) becomes www/node6. (20161207) entry. Completely off topic, if you upgrade the ports tree, you should update all your packages as doing partial upgrades is even worse (shared library rebuilds for instance). From owner-freebsd-ports@freebsd.org Fri Jun 23 09:47:50 2017 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 1340CDA0B25 for ; Fri, 23 Jun 2017 09:47:50 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: from mx.irealone.hr (xoth.irealone.hr [136.243.79.146]) (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 C08D97F2A6 for ; Fri, 23 Jun 2017 09:47:48 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mx.irealone.hr (Postfix, from userid 58) id F0D44460E; Fri, 23 Jun 2017 11:47:43 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on postfix.xoth.irealone.hr X-Spam-Level: X-Spam-Status: No, score=-101.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, LOCAL_WL_002 autolearn=ham autolearn_force=no version=3.4.1 Received: from mail.irealone.com (unknown [10.0.0.10]) by mx.irealone.hr (Postfix) with ESMTP id 4575F460A for ; Fri, 23 Jun 2017 11:47:43 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 23 Jun 2017 11:47:43 +0200 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Organization: Acheron Media In-Reply-To: <1498210501.2506.6.camel@gmail.com> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <1498157001.2235.1.camel@gmail.com> <1498206372.2506.1.camel@gmail.com> <00d078be50a83b6e18ef20bfe76e30ca@acheronmedia.hr> <1498210501.2506.6.camel@gmail.com> Message-ID: X-Sender: vlad-fbsd@acheronmedia.com User-Agent: Roundcube Webmail/1.2.5 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 09:47:50 -0000 On 2017-06-23 11:35, demelier.david@gmail.com wrote: > > Release branches do not need backports. I think we have different concepts of "backport" here. I'm not talking about backports as defined by debian backports repository. I'm talking about taking a piece of code from NEWER version and turning it into a patch for OLDER version. Unless you mean that release branches would get no fixes, period? That's.... well, "svn checkout" and don't touch it ever again :) That's the only way to deal with security/bug fixes for ports that mix new features (that may break things) with fixes, when they release a new version. Either that, or you simply bump the version and get both the fixes AND new features.... but that's what's being done with QUARTERLY now, and we're back to square one. -- Vlad K. From owner-freebsd-ports@freebsd.org Fri Jun 23 09:58:28 2017 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 BBF84DA0D5A for ; Fri, 23 Jun 2017 09:58:28 +0000 (UTC) (envelope-from yasu@utahime.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 A871D7F653 for ; Fri, 23 Jun 2017 09:58:28 +0000 (UTC) (envelope-from yasu@utahime.org) Received: by mailman.ysv.freebsd.org (Postfix) id A4DC0DA0D59; Fri, 23 Jun 2017 09:58:28 +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 A2BB0DA0D58 for ; Fri, 23 Jun 2017 09:58:28 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 6F09A7F652 for ; Fri, 23 Jun 2017 09:58:27 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 0286E117EF; Fri, 23 Jun 2017 18:52:27 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id AEE372684C; Fri, 23 Jun 2017 18:52:27 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 6A2582684B; Fri, 23 Jun 2017 18:52:27 +0900 (JST) Date: Fri, 23 Jun 2017 18:52:16 +0900 (JST) Message-Id: <20170623.185216.1085042003932437920.yasu@utahime.org> To: ports@FreeBSD.org Subject: PR commit request From: Yasuhiro KIMURA X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 09:58:28 -0000 Dear committers, Would someone please commit following 2 PRs? Bug 213187 - graphics/xface.el: simplify makefile and plist https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213187 Bug 213328 - japanese/mecab-ipadic: Add LICENSE and etc. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213328 Best regards. --- Yasuhiro KIMURA From owner-freebsd-ports@freebsd.org Fri Jun 23 11:48:49 2017 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 0F9E6DA290F for ; Fri, 23 Jun 2017 11:48:49 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id DB72082317 for ; Fri, 23 Jun 2017 11:48:48 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mailman.ysv.freebsd.org (Postfix) id D7B98DA290E; Fri, 23 Jun 2017 11:48: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 D56C4DA290D for ; Fri, 23 Jun 2017 11:48:48 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::241]) (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 8267F82315 for ; Fri, 23 Jun 2017 11:48:48 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wr0-x241.google.com with SMTP id 77so11934064wrb.3 for ; Fri, 23 Jun 2017 04:48:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=W6cVU9HzknTFF0LoSJf2tALXE08USfxgp78lwClMGfc=; b=MAI8cFrJZeHPqFvHDVufBjhA6sp2Nsql0o/BppMT4svOfo3U1JjCS7A+HFFf5NPzKK OjNG5HLDGDB0UNFmt+UptSP4Kbi1WFQTx4hK3IALO5MTL+FffToV21IpyZHQF7sZN2bC CApvNCXD07F24+ilHvql4EmRG5NV/f5Jy45bnV59IGtF26MeEZg32Zbl+yh2DR3mNYEC eZfhWhAJ4TPvl2S4GIyc9FzPS3dvCBydBowkwYT6Xpc3ngVDTcBcrSsONwl1efBW2/CC 6umE4GuFxyD1GyoZGAG2MY8AHiHHBDajf0EwvnhWvldkDIYAzwEMd1TV1C1z6mOn1uiE vYHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=W6cVU9HzknTFF0LoSJf2tALXE08USfxgp78lwClMGfc=; b=rFpOqyiot6v15AIy2jFfZWxeBGBs11jeGRI6UEtccBknrmFmybCakpIDDFUMDJGhLq 5GOixKfn+e/WSHCCBShoDPZvhjhiyRqqpXuEOovK6DTgBDzqL0AFeplqu2/1ILkKhGTX gBlG2kXg8/O0yusY5hdN5niAK2CmkByc9VMEzn14izqpI1kOtq4NkWpiDoxAi+HyOnG9 BMHoZsLXkl0vNLWHYmcWSpAJmB41sXh6p+iwhyAh8caeFz15rFF71gcNKRtA/KZ2fuxg vuSDHAnfFTrDRHCGJIFpRY+U+ou6NPZ63YDJXLcR4xbxnrwYda99ezUxYdWsHZN7PVsm jj0w== X-Gm-Message-State: AKS2vOwpT8BnER5GmyW11S68UsXu7GiS4aV8A9SvrIDWIpVU4u0GGAh6 uJj/Bj5jxm9AoO4r X-Received: by 10.28.6.77 with SMTP id 74mr5098275wmg.96.1498218525837; Fri, 23 Jun 2017 04:48:45 -0700 (PDT) Received: from gumby.homeunix.com ([81.17.24.158]) by smtp.gmail.com with ESMTPSA id p87sm7454110wma.2.2017.06.23.04.48.44 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 23 Jun 2017 04:48:45 -0700 (PDT) Date: Fri, 23 Jun 2017 12:48:42 +0100 From: RW To: ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170623124842.20fc0120@gumby.homeunix.com> In-Reply-To: <031b099e-4c70-78fc-206b-54bfcd8fb72d@columbus.rr.com> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <19474ced-28cf-917d-4642-cb8a501bd56f@gjunka.com> <031b099e-4c70-78fc-206b-54bfcd8fb72d@columbus.rr.com> X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) 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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 11:48:49 -0000 On Thu, 22 Jun 2017 22:03:35 -0400 Baho Utot wrote: > The pre-compiled packages is what drove me to build the entire system > as it gave me a broken system that would not work and upon getting it > to function would/**/spontaneous reboot. My hand built packages > stopped that. > > I have built run LFS for 10 years. I created a packaging system > using rpm for LFS ( it is on github ) . I worked for turbolinux as a > beta tester and worked with the folks that kept KDE3 alive, so I am > some one that knows something. And yet you do seem quite exceptionally accident prone. From owner-freebsd-ports@freebsd.org Fri Jun 23 12:01:43 2017 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 747A9DA32C8 for ; Fri, 23 Jun 2017 12:01:43 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.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 5B0EC82C9F for ; Fri, 23 Jun 2017 12:01:43 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dONHF-0007dB-83; Fri, 23 Jun 2017 06:01:29 -0600 Date: Fri, 23 Jun 2017 06:01:29 -0600 From: The Doctor To: Dewayne Geraghty Cc: freebsd-ports@freebsd.org Subject: Re: NEW APR/APR-Utils Message-ID: <20170623120129.GA25500@doctor.nl2k.ab.ca> References: <20170622130021.GB41229@doctor.nl2k.ab.ca> <96a2704f-f59a-e16d-26cf-d796ead498db@heuristicsystems.com.au> <20170623032940.GA85792@doctor.nl2k.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 12:01:43 -0000 On Fri, Jun 23, 2017 at 02:29:49PM +1000, Dewayne Geraghty wrote: > Rightly or wrongly I haven't tested with apr-1.6. I pretty much adhere > to the versions within /usr/ports. Only when there's a CVE do I break > ranks - and usually after I've filed a PR for the (security) issue to be > addressed. > > Sometimes the maintainers' need to have their attention drawn to > available updates, which benefits everyone. > > Unfortunately the PR mechanism is the only tracking mechanism (or poker, > depending on your perspective) available to us. > Looks like some habits do not die. Disappointed that 1.6 does not account for Libressl. > _______________________________________________ > 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" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism Talk Sense to a fool and he calls you foolish - Euripides From owner-freebsd-ports@freebsd.org Fri Jun 23 12:04:02 2017 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 1E7B5DA33BD for ; Fri, 23 Jun 2017 12:04:02 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id F17E082EF1 for ; Fri, 23 Jun 2017 12:04:01 +0000 (UTC) (envelope-from scratch65535@att.net) Received: by mailman.ysv.freebsd.org (Postfix) id ED9E9DA33BC; Fri, 23 Jun 2017 12:04:01 +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 ED120DA33BB for ; Fri, 23 Jun 2017 12:04:01 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm2-vm9.access.bullet.mail.bf1.yahoo.com (nm2-vm9.access.bullet.mail.bf1.yahoo.com [216.109.114.82]) (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 B3CD282EF0 for ; Fri, 23 Jun 2017 12:04:01 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1498219336; bh=gu+o0DULmZtyvwPbkdfmR/JH1VmmcjzdW2pt4A5iPgM=; h=From:To:Subject:Date:References:In-Reply-To:From:Subject; b=ODIptjm+f4xd6KMCeFjEIY++sZYAbU2Kt86A560BuFDIbxa9Ykpk1bZqEHHWliSXbpc0jq1rnw3OATilZ6eym3oIbULJYZLGJXIdIo6fykTBN+wRBCK5HETlh3iunk7/3BvbBpXG0LWaUxvnTZWPxAhLINE+Vl6N2Enr4szshPw= Received: from [66.196.81.160] by nm2.access.bullet.mail.bf1.yahoo.com with NNFMP; 23 Jun 2017 12:02:16 -0000 Received: from [98.139.221.250] by tm6.access.bullet.mail.bf1.yahoo.com with NNFMP; 23 Jun 2017 12:02:16 -0000 Received: from [127.0.0.1] by smtp120.sbc.mail.bf1.yahoo.com with NNFMP; 23 Jun 2017 12:02:16 -0000 X-Yahoo-Newman-Id: 779596.11535.bm@smtp120.sbc.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: h2..Zi0VM1m2b8wx.noMErcQBAzAQ_4QUoB9MiV6equPZmI nhP_SMZBXioiomhsVrMHqFkunvrDdjYfTxXQry.NdwnafW2qIH.HJf_zD4PR V8sRTepFfOA6Pfr1R3AUe0sgLgS1.CJHqkkrtaBNt9qPpaS5.x5IAlvmmcOu GwdCvPs5DusHZFVPy8cFl5fuh17NTZDJbPuMi4bBAXsKk38ERrPhPc9byFV0 ARCfJec4..Yn8vnGp54hVj5V62UXNr6xZxQL_ybk_RR0sBKXQFXKJxcczRuF pwPx85L6S9LOERcCbWdIxNJ99Or1jqUHO4Z21XaSp5xiaGCcTUWCfSNPMNJQ oHoz5tHKP.HMvBIhptBEOoAZjsH19eQJHmArGfIFczjfWPOU0xyX8XQ7L61b lQud0IrxVV_5unDL9N9aFiqPxOalvL5A1WU5tyq3g8nlOtoFXR4aGzo9.pwT Nhi.VE.7Ue9W_xyYsGqoQlQWUI3fJqEA_.hEx3mdKmP2kupXivndYbLs53b7 V.WNB5A3e84fK1YgzQgW_RL7KDgQW_xPRzlrQncqSdl4pVbAwL5zCYwoOdKa pHpHHinp6ElZNzK9L9JLh X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: freebsd-ports Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Date: Fri, 23 Jun 2017 08:02:29 -0400 Message-ID: <6mupkc5v5oclrd721pssousokmgtqkvfao@4ax.com> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> In-Reply-To: <594C4663.5080209@quip.cz> 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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 12:04:02 -0000 On Fri, 23 Jun 2017 00:36:19 +0200, Miroslav Lachman <000.fbsd@quip.cz> wrote: >scratch65535@att.net wrote on 2017/06/23 00:15: >> [Default] On Thu, 22 Jun 2017 16:11:26 -0500, Mark Linimon >> wrote: >> >>> On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65535@att.net wrote: >>>> My problem is that my industry experience tells me that reducing >>>> the frequency of port releases is practically *guaranteed* to be >>>> a Really Good Thing for everyone. >>> >>> I remember before we had the quarterly releases, and people on the >>> mailing lists complained constantly about the ports bits only being >>> available once per release, or rolling with -head. >> >> Mark, I can only suppose that those complainers are dilettantes >> of some sort who believe that having The Latest-And-Greatest Bits >> is a social-status enhancer. **Nobody** with real work to do >> ever willingly fools away time "fixing" what isn't broken. > >And this is where you are so wrong. Ports tree is never in the state >where everything works and has no bugs. (and cannot be, because >upstreams have bugs) Even if it compiles and installs it does not mean >that it is not broken and nobody needs newer version. >Just because your needs are different than others doesn't mean others >are dilettantes. How often have you bought all new versions of the software you use, Miroslav, even though the versions you replaced still worked fine? I'd bet that you've never done that, and never will: you're an adult, and have more important uses for your time and money. How often do you look around your flat or house for something to "fix" even though everthing works well enough? I'd bet not often, if ever -- you probably always have so much real work to do that you worry you'll never get it all done if you live to be 120. There are individuals who claim to "need" the latest Mercedes or Ferrari, or a bigger yacht, or a chalet in Switzerland. But that kind of "need" isn't on the same level as someone's need for a place to live, or a way to get to work, or medical care for their kids. Similarly, few people constantly "need" the latest software. Even if the new release has a feature that will make their work easier, the release after that one is not likely to have *another* such feature. Nearly all adults can do their computer-based work just fine without ever having the Latest-And-Greatest hardware and software. Those who claim they simply *must* always have bleeding-edge kit are kidding someone. Or delusional. From owner-freebsd-ports@freebsd.org Fri Jun 23 12:33:02 2017 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 0D142DA3CE8 for ; Fri, 23 Jun 2017 12:33:02 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cdptpa-oedge", Issuer "cdptpa-oedge" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C3EB383C1A for ; Fri, 23 Jun 2017 12:33:01 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from [65.186.81.207] ([65.186.81.207:49526] helo=raspberrypi.bildanet.com) by cdptpa-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id D9/1B-10880-B7A0D495; Fri, 23 Jun 2017 12:32:59 +0000 Received: from [192.168.1.143] (helo=desktop.example.com) by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1dONlj-0001KZ-CZ for freebsd-ports@freebsd.org; Fri, 23 Jun 2017 08:32:59 -0400 Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <19474ced-28cf-917d-4642-cb8a501bd56f@gjunka.com> <031b099e-4c70-78fc-206b-54bfcd8fb72d@columbus.rr.com> <20170623124842.20fc0120@gumby.homeunix.com> From: Baho Utot Message-ID: <190dac52-bae4-0568-c9a8-02ac0b548731@columbus.rr.com> Date: Fri, 23 Jun 2017 08:32:59 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170623124842.20fc0120@gumby.homeunix.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-RR-Connecting-IP: 107.14.168.6:25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 12:33:02 -0000 On 06/23/17 07:48, RW via freebsd-ports wrote: > On Thu, 22 Jun 2017 22:03:35 -0400 > Baho Utot wrote: > > >> The pre-compiled packages is what drove me to build the entire system >> as it gave me a broken system that would not work and upon getting it >> to function would/**/spontaneous reboot. My hand built packages >> stopped that. >> >> I have built run LFS for 10 years. I created a packaging system >> using rpm for LFS ( it is on github ) . I worked for turbolinux as a >> beta tester and worked with the folks that kept KDE3 alive, so I am >> some one that knows something. > > And yet you do seem quite exceptionally accident prone. Oh gee more insults, is that all you have? I guess that is encourgement for me to help FreeBSD. NOT. I see many posts about FreeBSD needing help and new help leaving just as fast. I wonder why when there is no incentive to work with others how that works. Ya name calling helps. From owner-freebsd-ports@freebsd.org Fri Jun 23 12:54:30 2017 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 3F0AFDA43B0 for ; Fri, 23 Jun 2017 12:54:30 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 16AE4847B9 for ; Fri, 23 Jun 2017 12:54:30 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 15DCFDA43AF; Fri, 23 Jun 2017 12:54: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 1552EDA43AE for ; Fri, 23 Jun 2017 12:54:30 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (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 99059847B8 for ; Fri, 23 Jun 2017 12:54:29 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: by mail-wr0-x242.google.com with SMTP id k67so12335066wrc.1 for ; Fri, 23 Jun 2017 05:54:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=o3+MW/ZaRhB4gLkUE5VYKlUJs9uOSRzzkIwJN7S0Mjs=; b=ENzZKfN8wKRImohK8v0aT4tNlb/MCDzeJBTh3Ts6jnRVa+UISKr3MXsdQAj3+jZYxy ME67JtgHoigWmFvPzthIyX0FFoEnfE5R8/qQ1UWdNIk0jb6saqLU9jZ7Vt0BvmErDG6W VGi9Zsuta+6YXUkOzsfJXzmUZnL9SmZsOYaauNS0Wwg0kq3HPd1rGFoW8hzS7vtBJeiF NIltZhIB57VGTd4gqPfIJpbizx/GuU6JuNiwEC67ATqGor0ZjNUyZOcTOszVHLWm2LYp S5cRvWftPQKQnLT0WVn54NMbNgjqhvnmgq+5Dm3iIZeKV4raD27hkdy4Fqst5zc9MxMJ RAyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=o3+MW/ZaRhB4gLkUE5VYKlUJs9uOSRzzkIwJN7S0Mjs=; b=jdEo0xkYgo0MD9qqJtcKicP85ppatYBvvrJ1NBKQ+08HMdvDW4WO+wH/0WL4ud33Sd ZfcrGaJqmvmJTtNfW7qKRQgD/tDZZG0LE+njkBnp8lrKCkiBfaRSxd+KIj33UcXaT2B3 ERXH9qgf6NDYFiDngwiElJ1Tw0HZiugPRkiWpjf1AqgIgGVb/vn+bwjd0Bxe5JdAIcqp fFMboRifEL6zp9s+e1aoEiE5lM89NeQChB/qO4YNV1u0uUq/O75dyAfuAKbv/zJYRyEG yTw5T353vbIZPh++AqrnYHgCfH6Ae1tmL0wUL3ylKC+4NA2QxZ7dABiGu8H2jUwq1PUI UwrQ== X-Gm-Message-State: AKS2vOza0YpEqG82czrGdcHpvSe1//6W4gGkPpxG9lvcS7luqIv70F1J 5jHZfXMaDNYmjA== X-Received: by 10.223.139.70 with SMTP id v6mr6206127wra.97.1498222467632; Fri, 23 Jun 2017 05:54:27 -0700 (PDT) Received: from gmail.com (tao.xtaz.uk. [2001:8b0:fe33::10]) by smtp.gmail.com with ESMTPSA id t70sm5135090wmd.1.2017.06.23.05.54.26 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 23 Jun 2017 05:54:27 -0700 (PDT) Date: Fri, 23 Jun 2017 13:54:25 +0100 From: Matt Smith To: scratch65535@att.net Cc: freebsd-ports Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170623125424.GA10691@gmail.com> Mail-Followup-To: Matt Smith , scratch65535@att.net, freebsd-ports References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <6mupkc5v5oclrd721pssousokmgtqkvfao@4ax.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <6mupkc5v5oclrd721pssousokmgtqkvfao@4ax.com> User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 12:54:30 -0000 On Jun 23 08:02, scratch65535@att.net wrote: >On Fri, 23 Jun 2017 00:36:19 +0200, Miroslav Lachman ><000.fbsd@quip.cz> wrote: > >>scratch65535@att.net wrote on 2017/06/23 00:15: >>> [Default] On Thu, 22 Jun 2017 16:11:26 -0500, Mark Linimon >>> wrote: >>> >>>> On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65535@att.net wrote: >>>>> My problem is that my industry experience tells me that reducing >>>>> the frequency of port releases is practically *guaranteed* to be >>>>> a Really Good Thing for everyone. >>>> >>>> I remember before we had the quarterly releases, and people on the >>>> mailing lists complained constantly about the ports bits only being >>>> available once per release, or rolling with -head. >>> >>> Mark, I can only suppose that those complainers are dilettantes >>> of some sort who believe that having The Latest-And-Greatest Bits >>> is a social-status enhancer. **Nobody** with real work to do >>> ever willingly fools away time "fixing" what isn't broken. >> >>And this is where you are so wrong. Ports tree is never in the state >>where everything works and has no bugs. (and cannot be, because >>upstreams have bugs) Even if it compiles and installs it does not mean >>that it is not broken and nobody needs newer version. >>Just because your needs are different than others doesn't mean others >>are dilettantes. > >How often have you bought all new versions of the software you >use, Miroslav, even though the versions you replaced still worked >fine? I'd bet that you've never done that, and never will: >you're an adult, and have more important uses for your time and >money. > >How often do you look around your flat or house for something to >"fix" even though everthing works well enough? I'd bet not >often, if ever -- you probably always have so much real work to >do that you worry you'll never get it all done if you live to be >120. > >There are individuals who claim to "need" the latest Mercedes or >Ferrari, or a bigger yacht, or a chalet in Switzerland. But that >kind of "need" isn't on the same level as someone's need for a >place to live, or a way to get to work, or medical care for their >kids. > >Similarly, few people constantly "need" the latest software. Even >if the new release has a feature that will make their work >easier, the release after that one is not likely to have >*another* such feature. Nearly all adults can do their >computer-based work just fine without ever having the >Latest-And-Greatest hardware and software. Those who claim they >simply *must* always have bleeding-edge kit are kidding someone. >Or delusional. >_______________________________________________ Can we stop suggesting that everybody in the world wants a stable release that doesn't frequently change, or that people who want to use the latest versions of software are delusional please? I use FreeBSD *precisely* because it mostly keeps up with the latest stable versions of things. I have postfix 3.2, pgsql 9.6, nginx 1.13, libressl 2.5 etc. It's usually impossible to do this with linux unless you install things directly from source. I upgrade my ports/packages via poudriere every single day which mostly just takes 2 minutes of my time as usually that results in maybe one or two packages being updated at a time. I see this as a positive thing rather than doing one massive huge upgrade every 3 months. If I see that a package is going to have a major version upgrade then I say no and cancel the update until I have a spare half hour or so later in the day. Then I will spend the time seeing what the differences are and changing my config etc as appropriate. I actually like this way of working and it suits me fine. I enjoy learning the ins and outs of new software. If everybody had the attitude of never spending time doing major version updates then we would all be in the python3 verses python 2 situation where virtually nobody is writing python3 code. I'm not going to argue against what you guys are asking for, each to their own, you have your own requirements and that's fair enough. But I just wanted to make a point that the way that FreeBSD currently does it is not "nobody wants it done this way". At least one person does thanks. -- Matt From owner-freebsd-ports@freebsd.org Fri Jun 23 13:11:52 2017 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 C526FDA478B for ; Fri, 23 Jun 2017 13:11:52 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cdptpa-oedge", Issuer "cdptpa-oedge" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 830CB84F45 for ; Fri, 23 Jun 2017 13:11:51 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from [65.186.81.207] ([65.186.81.207:49543] helo=raspberrypi.bildanet.com) by cdptpa-omsmta02 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 82/49-20123-6931D495; Fri, 23 Jun 2017 13:11:50 +0000 Received: from [192.168.1.143] (helo=desktop.example.com) by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1dOONJ-0001Lj-UT for freebsd-ports@freebsd.org; Fri, 23 Jun 2017 09:11:49 -0400 Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <1498157001.2235.1.camel@gmail.com> <1498206372.2506.1.camel@gmail.com> <666bfe8c-f27d-2c11-2a4a-07da43bb7931@FreeBSD.org> From: Baho Utot Message-ID: Date: Fri, 23 Jun 2017 09:11:49 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <666bfe8c-f27d-2c11-2a4a-07da43bb7931@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-RR-Connecting-IP: 107.14.168.7:25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 13:11:52 -0000 On 06/23/17 04:53, Guido Falsi wrote: > On 06/23/17 10:26, demelier.david@gmail.com wrote: >> On Thu, 2017-06-22 at 11:57 -0700, Dave Hayes wrote: >>> Would you agree that release branches would be unnecessary if >>> somehow >>> you could select the version of node that the ports tree builds via >>> some >>> (as yet unspecified) mechanism? >> >> I've also think about that but I'm not sure if it's easier than having >> frozen release branches. > > I usually stay away from this kind of threads, but I'd like to point out > a very simple concept that has not been expressed. > > The ports tree repository is fully open source, available via subversion > from the FreeBSD project and also mirrored on github. There is > absolutely nothing stopping you(and anyone with time, skill and > willingness to help you) from starting your fork from whichever source > and using whatever tool you prefer, creating the branches you're > describing. > > If your model works fine I'm quite sure the FreeBSD community and > project will be quite happy to embrace it. > > As stated, the FreeBSD project (core, portmgr and committers) perceive a > manpower problem in relation to implementing what you describe. In this > thread it has been stated that such a manpower problem does not really > exist. I cannot think of a better way to show there actually is no > manpower problem than creating a working example of such a workflow > maintained by just a few people with little effort, as you said repeatedly. > > On other hand demanding and/or insisting that others implement your idea > when they clearly disagree with you is not very constructive. > > In relation to the suggestion of a stable or release ports branch: > > I'd also like a ports branch where things are merged only when really > needed, some kind of "stable" branch. I don't like the release way you > describe, but maybe it could actually work as an option, but I too see > the manpower problem. An actual working proof of concept like I > described above is the only thing that would persuade me I'm wrong about > that. > > (I could try to help with such an experiment but I don't know how much > time I could really spare for it) > Ok, since you are taking the lead on this...... When do we start? Where shall I post my repository to? And updates? Should the start be for the 12.0 branch or should earlier? I can start on packaging the base system some time August is that ok with you and will it fit your schedule? From owner-freebsd-ports@freebsd.org Fri Jun 23 14:03:39 2017 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 0D380DA549D for ; Fri, 23 Jun 2017 14:03:39 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DEA691F70; Fri, 23 Jun 2017 14:03:38 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 1C9FC734; Fri, 23 Jun 2017 09:03:37 -0500 (CDT) Date: Fri, 23 Jun 2017 09:03:36 -0500 From: Mark Linimon To: Julian Elischer Cc: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170623140335.GA10886@lonesome.com> References: <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> <20170623043947.GA8922@lonesome.com> <3a428572-039c-79ed-8804-41e5fef4df99@freebsd.org> <20170623060926.GB9391@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170623060926.GB9391@lonesome.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 14:03:39 -0000 On Fri, Jun 23, 2017 at 01:09:26AM -0500, Mark Linimon wrote: > I'll go back to what I was doing before This was an unkind comment and I should not have made it. My apologies to all. mcl From owner-freebsd-ports@freebsd.org Fri Jun 23 14:08:10 2017 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 1769CDA552E for ; Fri, 23 Jun 2017 14:08:10 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [207.172.210.101]) (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 AD11B209A; Fri, 23 Jun 2017 14:08:09 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:470:1f07:15ff::1f] (haymarket.m5p.com [IPv6:2001:470:1f07:15ff::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id v5NE6jqD036071; Fri, 23 Jun 2017 10:06:51 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Subject: Re: www/libxul To: Jan Beich Cc: freebsd ports References: <1ed10613-f240-31dd-13e5-7271647869d2@m5p.com> From: George Mitchell Message-ID: <9244985a-f7ac-3554-9dd6-ed1273f38a5f@m5p.com> Date: Fri, 23 Jun 2017 10:06:45 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Sj0hsSdoOLLapx8lUVQgrhtN2MqQTVeQ7" X-Spam-Status: No, score=0.2 required=10.0 tests=HELO_MISC_IP, RP_MATCHES_RCVD autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2 (mailhost.m5p.com [IPv6:2001:470:1f07:15ff::f7]); Fri, 23 Jun 2017 10:06:52 -0400 (EDT) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 14:08:10 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Sj0hsSdoOLLapx8lUVQgrhtN2MqQTVeQ7 Content-Type: multipart/mixed; boundary="0H4PaDqFCGRko2FIxj6Ju9lrkU51wqPHs"; protected-headers="v1" From: George Mitchell To: Jan Beich Cc: freebsd ports Message-ID: <9244985a-f7ac-3554-9dd6-ed1273f38a5f@m5p.com> Subject: Re: www/libxul References: <1ed10613-f240-31dd-13e5-7271647869d2@m5p.com> In-Reply-To: --0H4PaDqFCGRko2FIxj6Ju9lrkU51wqPHs Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 06/23/17 00:49, Jan Beich wrote: > George Mitchell writes: >=20 >> Consequently, the configure script dies at line 26248, complaining >> that "Option, jemalloc, does not take an argument (4)". >=20 > Sorry for the bustage. It should be fixed now. >=20 > https://svnweb.freebsd.org/changeset/ports/444163 > [...] (conks self on forehead, mutters:) "remember to check /usr/ports/Mk for stuff that magically appears from nowhere." Thanks for the quick fix! It works now. -- George --0H4PaDqFCGRko2FIxj6Ju9lrkU51wqPHs-- --Sj0hsSdoOLLapx8lUVQgrhtN2MqQTVeQ7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAllNIHUACgkQwRES3m+p 4fnSzw/9GMvu5vE0WsYsLR923PcwjuuzvvFJIK2qSDQUO1oXaF9vo1uICjhbPNhy S+RyZKr8z4FXNl02Xj2XpHvdYG4iv1/S/HlZdvFQ0FKa6YN8d0kAPRyk89HFZnZp IMbgSiO4WHBwUO2Tfw0xlQcqnuWJZpLRX1Vls9DeMtJcucTUJHaCSUfzsbI8PK5N HK4hzc50wvmnE7wSSJIJVgsbvdLT/jVnTfctlXMuNb4vrdZz/s2gLH9I8EMZWKdk YP8kjTpFzJoQheI1X4RZV4I6vJj0NTHn0H3SGEPT4VWrHxZ4g2Kq9eo7DzJu/AXL x/5P3Ufs2DG7ni6EKZI2VZ6w+M/uV/IHClIDTJbvuRq8GPC9iHpS/dAq2xArKCsd 6XmlPCWeNLMvd/50raChUJfAIgETLe8+jgLQtLU/DUX3ORN9NqEJ73cPatWBOdVs PbIwk7GTf8mVugLBdHd1xi9uLTmfx6Jwyy5Mt3PD3pTHWDnth/6peWA2oyfzcwks WAuESTGhkrxyK+PNRYANdlcj0TBFvlA3HfpcnY1HNDFH387ZUqRvTVdrC+G0oMBo l6qabytyg7fsA54l6juaTNIBKw96d2FpJbHStd0qG4fVPM4x0qRw0Td19ajfRN+V 3tr67iI83oC0zPHLkkcOaeFb/qKxD4jwB34jsnT9GK+gCCjyvUk= =RWnl -----END PGP SIGNATURE----- --Sj0hsSdoOLLapx8lUVQgrhtN2MqQTVeQ7-- From owner-freebsd-ports@freebsd.org Fri Jun 23 14:30:43 2017 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 419A5DA5ABD for ; Fri, 23 Jun 2017 14:30:43 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) 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 C84572AC1 for ; Fri, 23 Jun 2017 14:30:42 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3wvLTW3h68zb56; Fri, 23 Jun 2017 16:30:39 +0200 (CEST) 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 9o4-jRIqJ-ot; Fri, 23 Jun 2017 16:30:37 +0200 (CEST) Received: from marvin.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Fri, 23 Jun 2017 16:30:37 +0200 (CEST) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Baho Utot , freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <1498157001.2235.1.camel@gmail.com> <1498206372.2506.1.camel@gmail.com> <666bfe8c-f27d-2c11-2a4a-07da43bb7931@FreeBSD.org> From: Guido Falsi Message-ID: Date: Fri, 23 Jun 2017 16:30:37 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 14:30:43 -0000 On 06/23/17 15:11, Baho Utot wrote: > > > On 06/23/17 04:53, Guido Falsi wrote: >> On 06/23/17 10:26, demelier.david@gmail.com wrote: >>> On Thu, 2017-06-22 at 11:57 -0700, Dave Hayes wrote: >>>> Would you agree that release branches would be unnecessary if >>>> somehow >>>> you could select the version of node that the ports tree builds via >>>> some >>>> (as yet unspecified) mechanism? >>> >>> I've also think about that but I'm not sure if it's easier than having >>> frozen release branches. >> >> I usually stay away from this kind of threads, but I'd like to point >> out a very simple concept that has not been expressed. >> >> The ports tree repository is fully open source, available via >> subversion from the FreeBSD project and also mirrored on github. There >> is absolutely nothing stopping you(and anyone with time, skill and >> willingness to help you) from starting your fork from whichever source >> and using whatever tool you prefer, creating the branches you're >> describing. >> >> If your model works fine I'm quite sure the FreeBSD community and >> project will be quite happy to embrace it. >> >> As stated, the FreeBSD project (core, portmgr and committers) perceive >> a manpower problem in relation to implementing what you describe. In >> this thread it has been stated that such a manpower problem does not >> really exist. I cannot think of a better way to show there actually is >> no manpower problem than creating a working example of such a workflow >> maintained by just a few people with little effort, as you said >> repeatedly. >> >> On other hand demanding and/or insisting that others implement your >> idea when they clearly disagree with you is not very constructive. >> >> In relation to the suggestion of a stable or release ports branch: >> >> I'd also like a ports branch where things are merged only when really >> needed, some kind of "stable" branch. I don't like the release way you >> describe, but maybe it could actually work as an option, but I too see >> the manpower problem. An actual working proof of concept like I >> described above is the only thing that would persuade me I'm wrong >> about that. >> >> (I could try to help with such an experiment but I don't know how much >> time I could really spare for it) >> > > Ok, since you are taking the lead on this...... Since when "help with" is a synonym of "lead this effort"? > > When do we start? >> Where shall I post my repository to? > > And updates? > > Should the start be for the 12.0 branch or should earlier? > > I can start on packaging the base system some time August is that ok > with you and will it fit your schedule? I'm curious to know which paragraph is the sarcasm especially directed at, if the first or the last, in parenthesis and meant at giving hand if someone else has a clear plan. I can't see me leading an effort I clearly stated I don't think has many chances. Maybe I was not perfectly clear. -- Guido Falsi From owner-freebsd-ports@freebsd.org Fri Jun 23 14:34:01 2017 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 4CE36DA5C49 for ; Fri, 23 Jun 2017 14:34:01 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) 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 E1C642DF0 for ; Fri, 23 Jun 2017 14:34:00 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3wvLYL65pFzb56 for ; Fri, 23 Jun 2017 16:33:58 +0200 (CEST) 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 lxJpeXMjJefh for ; Fri, 23 Jun 2017 16:33:57 +0200 (CEST) Received: from marvin.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA for ; Fri, 23 Jun 2017 16:33:57 +0200 (CEST) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <1498157001.2235.1.camel@gmail.com> <1498206372.2506.1.camel@gmail.com> <666bfe8c-f27d-2c11-2a4a-07da43bb7931@FreeBSD.org> From: Guido Falsi Message-ID: Date: Fri, 23 Jun 2017 16:33:56 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <666bfe8c-f27d-2c11-2a4a-07da43bb7931@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 14:34:01 -0000 On 06/23/17 10:53, Guido Falsi wrote: > On 06/23/17 10:26, demelier.david@gmail.com wrote: >> On Thu, 2017-06-22 at 11:57 -0700, Dave Hayes wrote: >>> Would you agree that release branches would be unnecessary if >>> somehow >>> you could select the version of node that the ports tree builds via >>> some >>> (as yet unspecified) mechanism? >> >> I've also think about that but I'm not sure if it's easier than having >> frozen release branches. > > I usually stay away from this kind of threads, but I'd like to point out > a very simple concept that has not been expressed. > > The ports tree repository is fully open source, available via subversion > from the FreeBSD project and also mirrored on github. There is > absolutely nothing stopping you(and anyone with time, skill and > willingness to help you) from starting your fork from whichever source > and using whatever tool you prefer, creating the branches you're > describing. > > If your model works fine I'm quite sure the FreeBSD community and > project will be quite happy to embrace it. > > As stated, the FreeBSD project (core, portmgr and committers) perceive a > manpower problem in relation to implementing what you describe. In this > thread it has been stated that such a manpower problem does not really > exist. I cannot think of a better way to show there actually is no > manpower problem than creating a working example of such a workflow > maintained by just a few people with little effort, as you said repeatedly. > > On other hand demanding and/or insisting that others implement your idea > when they clearly disagree with you is not very constructive. > > In relation to the suggestion of a stable or release ports branch: > > I'd also like a ports branch where things are merged only when really > needed, some kind of "stable" branch. I don't like the release way you > describe, but maybe it could actually work as an option, but I too see > the manpower problem. An actual working proof of concept like I > described above is the only thing that would persuade me I'm wrong about > that. > > (I could try to help with such an experiment but I don't know how much > time I could really spare for it) > I'll rephrase that to avoid further confusion: (If such an effort is started with a clear idea and program, which I don't have on such a project, I can try to participate as manpower to it, even though I can't dedicate much time to it) -- Guido Falsi From owner-freebsd-ports@freebsd.org Fri Jun 23 14:56:12 2017 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 11C2ADA627D for ; Fri, 23 Jun 2017 14:56:12 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cdptpa-oedge", Issuer "cdptpa-oedge" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BB53B365C for ; Fri, 23 Jun 2017 14:56:11 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from [65.186.81.207] ([65.186.81.207:49613] helo=raspberrypi.bildanet.com) by cdptpa-omsmta03 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 9C/9D-21563-90C2D495; Fri, 23 Jun 2017 14:56:09 +0000 Received: from [192.168.1.143] (helo=desktop.example.com) by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1dOQ0H-0001Q0-C0; Fri, 23 Jun 2017 10:56:09 -0400 Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Guido Falsi , freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <1498157001.2235.1.camel@gmail.com> <1498206372.2506.1.camel@gmail.com> <666bfe8c-f27d-2c11-2a4a-07da43bb7931@FreeBSD.org> From: Baho Utot Message-ID: <16b4645e-58d5-e142-2e03-4f2620dbed89@columbus.rr.com> Date: Fri, 23 Jun 2017 10:56:09 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-RR-Connecting-IP: 107.14.168.88:25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 14:56:12 -0000 On 06/23/17 10:30, Guido Falsi wrote: > On 06/23/17 15:11, Baho Utot wrote: >> >> >> On 06/23/17 04:53, Guido Falsi wrote: >>> On 06/23/17 10:26, demelier.david@gmail.com wrote: >>>> On Thu, 2017-06-22 at 11:57 -0700, Dave Hayes wrote: >>>>> Would you agree that release branches would be unnecessary if >>>>> somehow >>>>> you could select the version of node that the ports tree builds via >>>>> some >>>>> (as yet unspecified) mechanism? >>>> >>>> I've also think about that but I'm not sure if it's easier than having >>>> frozen release branches. >>> >>> I usually stay away from this kind of threads, but I'd like to point >>> out a very simple concept that has not been expressed. >>> >>> The ports tree repository is fully open source, available via >>> subversion from the FreeBSD project and also mirrored on github. There >>> is absolutely nothing stopping you(and anyone with time, skill and >>> willingness to help you) from starting your fork from whichever source >>> and using whatever tool you prefer, creating the branches you're >>> describing. >>> >>> If your model works fine I'm quite sure the FreeBSD community and >>> project will be quite happy to embrace it. >>> >>> As stated, the FreeBSD project (core, portmgr and committers) perceive >>> a manpower problem in relation to implementing what you describe. In >>> this thread it has been stated that such a manpower problem does not >>> really exist. I cannot think of a better way to show there actually is >>> no manpower problem than creating a working example of such a workflow >>> maintained by just a few people with little effort, as you said >>> repeatedly. >>> >>> On other hand demanding and/or insisting that others implement your >>> idea when they clearly disagree with you is not very constructive. >>> >>> In relation to the suggestion of a stable or release ports branch: >>> >>> I'd also like a ports branch where things are merged only when really >>> needed, some kind of "stable" branch. I don't like the release way you >>> describe, but maybe it could actually work as an option, but I too see >>> the manpower problem. An actual working proof of concept like I >>> described above is the only thing that would persuade me I'm wrong >>> about that. >>> >>> (I could try to help with such an experiment but I don't know how much >>> time I could really spare for it) >>> >> >> Ok, since you are taking the lead on this...... > > Since when "help with" is a synonym of "lead this effort"? > >> >> When do we start? >>> Where shall I post my repository to? >> >> And updates? >> >> Should the start be for the 12.0 branch or should earlier? >> >> I can start on packaging the base system some time August is that ok >> with you and will it fit your schedule? > > I'm curious to know which paragraph is the sarcasm especially directed > at, if the first or the last, in parenthesis and meant at giving hand if > someone else has a clear plan. I can't see me leading an effort I > clearly stated I don't think has many chances. Maybe I was not perfectly > clear. > I have faith in you... you can do this...when do we start? From owner-freebsd-ports@freebsd.org Fri Jun 23 15:47:39 2017 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 ADC74DA7026 for ; Fri, 23 Jun 2017 15:47:39 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 64CAE65404 for ; Fri, 23 Jun 2017 15:47:38 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (x2f7f051.dyn.telefonica.de [2.247.240.81]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v5NFla2m061568 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 23 Jun 2017 15:47:36 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host x2f7f051.dyn.telefonica.de [2.247.240.81] claimed to be ultrabook.yoonka.com Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> From: Grzegorz Junka Message-ID: <5eabe1d2-85a3-f7eb-a1ab-dc5552eb70fe@gjunka.com> Date: Fri, 23 Jun 2017 15:47:30 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 15:47:39 -0000 On 23/06/2017 03:58, Julian Elischer wrote: > On 23/6/17 6:36 am, Miroslav Lachman wrote: >> scratch65535@att.net wrote on 2017/06/23 00:15: >>> [Default] On Thu, 22 Jun 2017 16:11:26 -0500, Mark Linimon >>> wrote: >>> >>>> On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65535@att.net wrote: >>>>> My problem is that my industry experience tells me that reducing >>>>> the frequency of port releases is practically *guaranteed* to be >>>>> a Really Good Thing for everyone. >>>> >>>> I remember before we had the quarterly releases, and people on the >>>> mailing lists complained constantly about the ports bits only being >>>> available once per release, or rolling with -head. >>> >>> Mark, I can only suppose that those complainers are dilettantes >>> of some sort who believe that having The Latest-And-Greatest Bits >>> is a social-status enhancer. **Nobody** with real work to do >>> ever willingly fools away time "fixing" what isn't broken. >> >> And this is where you are so wrong. Ports tree is never in the state >> where everything works and has no bugs. (and cannot be, because >> upstreams have bugs) Even if it compiles and installs it does not >> mean that it is not broken and nobody needs newer version. >> Just because your needs are different than others doesn't mean others >> are dilettantes. > > The usage of the word dilettante can have negative connotations but he > is in essential facts correct. > > I have spent 30 years on BSD systems in industry, and we almost NEVER > want the latest and greatest (except at project start time). > What we want is: > A "recent" starting point for our next project/upgrade to start from > and an ongoing version of that, which will get critical fixes only for > at LEAST 2 years, probably 5. > The key here is the *_*critical fixes only*_* part. > > We do NOT want: > A new version of perl, python, ssh, shell openssl (*), apache, > named, etc. etc. > The less changes the better. Basically if it doesn't have a CVE > number or it isn't actually completely broken, > then don't upgrade it in that branch. > We'll fix it ourselves if we need it bad enough (and feed back > changes if we know it would be taken). > > (*) From my experience, the best way to cope with openssl is to have > everything link with > the system openssl and issue security upgrades to the base OS that > upgrades that when there is a need. > (this may change, but it's been my experience so far). > > The recent starting point doesn't even need to be 100.00% working. > What we will do here is mirror it and from the mirror, put it into our > own source control branch/tree where we will add our own changes to > fix/tailor what we need. > We will then keep merging in fixes from upstream. which usually will > not collide with our private changes/fixes. > From that we generate our required packages. > From our perspective, a yearly branch (6 months would be 'ideal' but > 12 would work) that gets only *critical *fixes would be wonderful. > Remember that from the time when a product major release is planned to > when it comes out is usually 6 to 12 months lead time. > So when it hits the customer's racks, the packages were usually > generated somewhere mid-cycle and are already 6 months old. > We will not be replacing them on the customer premises machine until > they elect to do/purchase an upgrade / patch release. > which may be in a year or two. Certainly for a minor update it is > rarely less than 6 months. > It'd have to be a heartbleed scale security issue to get customers to > do an upgrade earlier. Can't you just create the branch yourself? It's open source. You just clone it and can keep it in Github for free. Then you can apply security patches to just the applications you need yourself. If it's too difficult you can hire people to apply just specific patches. With Github pull requests it's deadly easy. I am sure that if you asked maintainers to do the patching for a financial incentive they would mind doing it. Grzegorz From owner-freebsd-ports@freebsd.org Fri Jun 23 17:16:04 2017 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 50E11DA8B16 for ; Fri, 23 Jun 2017 17:16:04 +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 2B88A68786 for ; Fri, 23 Jun 2017 17:16:03 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (124-148-108-84.dyn.iinet.net.au [124.148.108.84]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v5NHFkFK065789 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 23 Jun 2017 10:15:50 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: "Vlad K." , freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <1498157001.2235.1.camel@gmail.com> <1498206372.2506.1.camel@gmail.com> <00d078be50a83b6e18ef20bfe76e30ca@acheronmedia.hr> From: Julian Elischer Message-ID: Date: Sat, 24 Jun 2017 01:15:40 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <00d078be50a83b6e18ef20bfe76e30ca@acheronmedia.hr> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 17:16:04 -0000 On 23/6/17 4:38 pm, Vlad K. wrote: > On 2017-06-23 10:26, demelier.david@gmail.com wrote: >> >> Release branches won't have many maintenance except individual bug >> fixes when security advisories are found. No backport, no updates. > > Nothing prevents the maintainers from doing exactly that right now. > But you see, there are two kinds of ports in the tree: > > 1) ports where upstream maintains a concept of LTS > 2) ports that mix bug, security fixes and new features in even > point.point releases > > For some (all?) major production software like Apache, nginx, PHP, > PostgreSQL, MySQL (I think?), Postfix, Dovecot2, etc... #1 applies. > So for serious production servers this should be easy to maintain as > the upstream is doing that in the first place. > > The problem is then with ports of type #2. And there's lots of them. > > Gentoo portage can easily maintain "stable" ports because portage > doesn't have a single Makefile, it has multiple .ebuild files so > multiple versions are available under ONE port name, and bumping the > version while keeping previous ones available is literally just a > matter of making a copy of the latest .ebuild and fixing the version > in it like we do with PORTVERSION. This is why I think our Makefile should be split up into two parts. One of which has the interface to the rest of the ports and one of which specifies what to download and things that are specific to a given version. then hopefully you could update the second without changing the first. Harder to do than say, I know, but I have faced htat challenge soo often, in fact i have it right now. I need a new azure-agent, in a 10.3 world, where I can not update any other packages/ports. > > On FreeBSD that's impossible and often ports are separated and > version baked into the port name. Like www/node from the original > post of this thread. > > But again, that's all doable without having to introduce new > infrastructure. The ports tree as is can be maintained like this and > quarterly repos would NOT be required. All it's needed is for > maintainers to keep a stable version and a latest version. There's > already plenty of ports done like that, otoh postfix and > postfix-current, nginx and nginx-devel, etc... > > Because the BIGGEST problem in maintaining separate "stable" or LTS > branches is BACKPORTING fixes for ports in the #2 category, ie. > those that mix new features with fixes, so you have to CHERRY PICK > only the fix and BACKPORT it to your "stable" branch. And that's > even more work often introducing NEW bugs. > > BTW, the problem of the original post could've been avoided if the > user only read UPDATING which clearly stated that www/node becomes 7 > and previous node (6) becomes www/node6. (20161207) entry. > > > > From owner-freebsd-ports@freebsd.org Fri Jun 23 17:24:15 2017 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 46965DA8D41 for ; Fri, 23 Jun 2017 17:24:15 +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 1769C68C6D for ; Fri, 23 Jun 2017 17:24:14 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (124-148-108-84.dyn.iinet.net.au [124.148.108.84]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v5NHO90a065830 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 23 Jun 2017 10:24:12 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Grzegorz Junka , freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> <5eabe1d2-85a3-f7eb-a1ab-dc5552eb70fe@gjunka.com> From: Julian Elischer Message-ID: Date: Sat, 24 Jun 2017 01:24:03 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <5eabe1d2-85a3-f7eb-a1ab-dc5552eb70fe@gjunka.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 17:24:15 -0000 On 23/6/17 11:47 pm, Grzegorz Junka wrote: > > On 23/06/2017 03:58, Julian Elischer wrote: >> On 23/6/17 6:36 am, Miroslav Lachman wrote: >>> scratch65535@att.net wrote on 2017/06/23 00:15: >>>> [Default] On Thu, 22 Jun 2017 16:11:26 -0500, Mark Linimon >>>> wrote: >>>> >>>>> On Thu, Jun 22, 2017 at 12:32:45PM -0400, scratch65535@att.net >>>>> wrote: >>>>>> My problem is that my industry experience tells me that reducing >>>>>> the frequency of port releases is practically *guaranteed* to be >>>>>> a Really Good Thing for everyone. >>>>> >>>>> I remember before we had the quarterly releases, and people on the >>>>> mailing lists complained constantly about the ports bits only being >>>>> available once per release, or rolling with -head. >>>> >>>> Mark, I can only suppose that those complainers are dilettantes >>>> of some sort who believe that having The Latest-And-Greatest Bits >>>> is a social-status enhancer. **Nobody** with real work to do >>>> ever willingly fools away time "fixing" what isn't broken. >>> >>> And this is where you are so wrong. Ports tree is never in the >>> state where everything works and has no bugs. (and cannot be, >>> because upstreams have bugs) Even if it compiles and installs it >>> does not mean that it is not broken and nobody needs newer version. >>> Just because your needs are different than others doesn't mean >>> others are dilettantes. >> >> The usage of the word dilettante can have negative connotations but >> he is in essential facts correct. >> >> I have spent 30 years on BSD systems in industry, and we almost >> NEVER want the latest and greatest (except at project start time). >> What we want is: >> A "recent" starting point for our next project/upgrade to start from >> and an ongoing version of that, which will get critical fixes only >> for at LEAST 2 years, probably 5. >> The key here is the *_*critical fixes only*_* part. >> >> We do NOT want: >> A new version of perl, python, ssh, shell openssl (*), apache, >> named, etc. etc. >> The less changes the better. Basically if it doesn't have a CVE >> number or it isn't actually completely broken, >> then don't upgrade it in that branch. >> We'll fix it ourselves if we need it bad enough (and feed back >> changes if we know it would be taken). >> >> (*) From my experience, the best way to cope with openssl is to >> have everything link with >> the system openssl and issue security upgrades to the base OS that >> upgrades that when there is a need. >> (this may change, but it's been my experience so far). >> >> The recent starting point doesn't even need to be 100.00% working. >> What we will do here is mirror it and from the mirror, put it into >> our own source control branch/tree where we will add our own >> changes to fix/tailor what we need. >> We will then keep merging in fixes from upstream. which usually >> will not collide with our private changes/fixes. >> From that we generate our required packages. >> From our perspective, a yearly branch (6 months would be 'ideal' >> but 12 would work) that gets only *critical *fixes would be wonderful. >> Remember that from the time when a product major release is planned >> to when it comes out is usually 6 to 12 months lead time. >> So when it hits the customer's racks, the packages were usually >> generated somewhere mid-cycle and are already 6 months old. >> We will not be replacing them on the customer premises machine >> until they elect to do/purchase an upgrade / patch release. >> which may be in a year or two. Certainly for a minor update it is >> rarely less than 6 months. >> It'd have to be a heartbleed scale security issue to get customers >> to do an upgrade earlier. > > Can't you just create the branch yourself? It's open source. You > just clone it and can keep it in Github for free. Then you can apply > security patches to just the applications you need yourself. If it's > too difficult you can hire people to apply just specific patches. > With Github pull requests it's deadly easy. I am sure that if you > asked maintainers to do the patching for a financial incentive they > would mind doing it. I actually explained it.. We do not have the people who understand all those ports. if there is a port hat gets a fix, one assumes there is a maintainer who at least understands that port a bit. I would feel more comfortable if they made the fix. Having said that I do think tat we do need to pony up some cash at some stage.. and many others should too if we want to have something like this. I've said this elsewhere. > > Grzegorz > _______________________________________________ > 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 Jun 23 20:59:38 2017 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 82DBBD89C99 for ; Fri, 23 Jun 2017 20:59:38 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C84673FEE for ; Fri, 23 Jun 2017 20:59:37 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com ([10.70.6.2]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v5NKxYJ7065903 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 23 Jun 2017 20:59:34 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host [10.70.6.2] claimed to be ultrabook.yoonka.com Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <19474ced-28cf-917d-4642-cb8a501bd56f@gjunka.com> <031b099e-4c70-78fc-206b-54bfcd8fb72d@columbus.rr.com> <20170623124842.20fc0120@gumby.homeunix.com> <190dac52-bae4-0568-c9a8-02ac0b548731@columbus.rr.com> From: Grzegorz Junka Message-ID: Date: Fri, 23 Jun 2017 20:59:34 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <190dac52-bae4-0568-c9a8-02ac0b548731@columbus.rr.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 20:59:38 -0000 On 23/06/2017 12:32, Baho Utot wrote: > > > On 06/23/17 07:48, RW via freebsd-ports wrote: >> On Thu, 22 Jun 2017 22:03:35 -0400 >> Baho Utot wrote: >> >> >>> The pre-compiled packages is what drove me to build the entire system >>> as it gave me a broken system that would not work and upon getting it >>> to function would/**/spontaneous reboot. My hand built packages >>> stopped that. >>> >>> I have built run LFS for 10 years. I created a packaging system >>> using rpm for LFS ( it is on github ) . I worked for turbolinux as a >>> beta tester and worked with the folks that kept KDE3 alive, so I am >>> some one that knows something. >> >> And yet you do seem quite exceptionally accident prone. > > Oh gee more insults, is that all you have? > > I guess that is encourgement for me to help FreeBSD. NOT. > > I see many posts about FreeBSD needing help and new help leaving just > as fast. I wonder why when there is no incentive to work with others > how that works. Ya name calling helps. I think you explained well enough what changes/improvements in maintaining of the ports tree you would like to see. Can you be more precise what help and from whom you would need in order to implement it? Grzegorz From owner-freebsd-ports@freebsd.org Fri Jun 23 21:09:14 2017 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 9E891D89F6F for ; Fri, 23 Jun 2017 21:09:14 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2A0D0744D7 for ; Fri, 23 Jun 2017 21:09:13 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com ([10.70.6.2]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v5NL9B6p066055 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 23 Jun 2017 21:09:11 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host [10.70.6.2] claimed to be ultrabook.yoonka.com Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> <5eabe1d2-85a3-f7eb-a1ab-dc5552eb70fe@gjunka.com> From: Grzegorz Junka Message-ID: <6d35f70b-17f2-d864-68ed-a3637cdc9fbf@gjunka.com> Date: Fri, 23 Jun 2017 21:09:11 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 21:09:14 -0000 >> Can't you just create the branch yourself? It's open source. You just >> clone it and can keep it in Github for free. Then you can apply >> security patches to just the applications you need yourself. If it's >> too difficult you can hire people to apply just specific patches. >> With Github pull requests it's deadly easy. I am sure that if you >> asked maintainers to do the patching for a financial incentive they >> would mind doing it. > I actually explained it.. We do not have the people who understand > all those ports. > if there is a port hat gets a fix, one assumes there is a maintainer > who at least understands that port a bit. > I would feel more comfortable if they made the fix. > Having said that I do think tat we do need to pony up some cash at > some stage.. and many others should too > if we want to have something like this. I've said this elsewhere. Fine. Considering that maintainers already apply patches to the latest quarterly branch. If there were to be OS version branches, it would mean that maintainers apart from what they are doing now would additionally need to apply selected patches to those OS version branches? Considering there would be, say, 3 latest version branches, and that 30% of the patches that go to the latest branch would need to also be ported to the OS version branches, that would roughly mean twice as much work as today? Grzegorz From owner-freebsd-ports@freebsd.org Fri Jun 23 21:36:49 2017 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 C3B11D8A6F6 for ; Fri, 23 Jun 2017 21:36:49 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (hades.sorbs.net [72.12.213.40]) by mx1.freebsd.org (Postfix) with ESMTP id A7A3E75A27; Fri, 23 Jun 2017 21:36:49 +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 <0OS000CA4SE4ER00@hades.sorbs.net>; Fri, 23 Jun 2017 14:44:29 -0700 (PDT) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Julian Elischer , freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> From: Michelle Sullivan Message-id: <5f1a71bb-abd4-6e89-f6c9-37527eba3239@sorbs.net> Date: Fri, 23 Jun 2017 23:36:46 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 In-reply-to: <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 21:36:49 -0000 Julian Elischer wrote: > > (*) From my experience, the best way to cope with openssl is to have > everything link with > the system openssl and issue security upgrades to the base OS that > upgrades that when there is a need. > (this may change, but it's been my experience so far). Agree on previous parts of your message but have to say 'no' here... Ports OpenSSL is the way to go.. because of the FreeBSD policy "we won't change the ABI" one of the reasons for no having 9.4 was OpenSSL 0.9.8 was EoLd and there were/are bugs unpatched.... Thing is its a perfect example of why OpenSSL should not be bundled into the OS... but then you can't rely on the ports system because of the drive to change it. Rock and a hard place comes to mind... Problem is you have @freebsd.org email holder saying, "we don't get paid for this so we'll do it our way... pay us to do it your way or do it yourself" vs the users, that are shouting, "come on guys we can't keep up, we need stability, we're not using this as a desktop here".... And both sides are diametrically opposed and steadfast to the point of zealous-ism... -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-ports@freebsd.org Fri Jun 23 21:40:29 2017 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 F26EED8A7CA for ; Fri, 23 Jun 2017 21:40:29 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: from mx.irealone.hr (xoth.irealone.hr [136.243.79.146]) (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 A166875B2F for ; Fri, 23 Jun 2017 21:40:29 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mx.irealone.hr (Postfix, from userid 58) id D36094B88; Fri, 23 Jun 2017 23:40:20 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on postfix.xoth.irealone.hr X-Spam-Level: X-Spam-Status: No, score=-101.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, LOCAL_WL_002 autolearn=ham autolearn_force=no version=3.4.1 Received: from mail.irealone.com (unknown [10.0.0.10]) by mx.irealone.hr (Postfix) with ESMTP id 3276C4B80 for ; Fri, 23 Jun 2017 23:40:19 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 23 Jun 2017 23:40:19 +0200 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Organization: Acheron Media In-Reply-To: <6d35f70b-17f2-d864-68ed-a3637cdc9fbf@gjunka.com> References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> <5eabe1d2-85a3-f7eb-a1ab-dc5552eb70fe@gjunka.com> <6d35f70b-17f2-d864-68ed-a3637cdc9fbf@gjunka.com> Message-ID: <63e5c4e30a60d51c5a068177b9483206@acheronmedia.hr> X-Sender: vlad-fbsd@acheronmedia.com User-Agent: Roundcube Webmail/1.2.5 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 21:40:30 -0000 On 2017-06-23 23:09, Grzegorz Junka wrote: > > Fine. Considering that maintainers already apply patches to the latest > quarterly branch. If there were to be OS version branches, it would > mean that maintainers apart from what they are doing now would > additionally need to apply selected patches to those OS version > branches? "OS version branches" would be a complete waste of time and resources, and it would remove some level of separation/independence between the base and ports. The crux of the problem here is so called "stable ports", not necessarily tying them to the life cycle of a base release. It doesn't make sense to tie version of a port to the base release. Especially with the new releng support schedule that would mean 5 years per major version which is quite a lot. RHEL/CentOS achieve that with: 1. paid maintainers 2. far less packages to maintain 3. strictly supported set of enabled features/packages Even Canonical is supporting far less packages in their Ubuntu "Universe" (officially supported repo), while tens of thousands of other packages are "Community support". So that's two ecosystems with vastly more users and contributors. They're also ecosystems with strict policies in place so "volunteer time" excuse does not apply, the maintainers are expected to do certain things and to it as the policy prescribes it. From what I gather, something like this would be impossible in FreeBSD because nobody is "required" to do anything, "we're all volunteers" I've been told. Another part of such a policy is commitment to maintain the package for the duration of release (in Debian/Ubuntu), to the extent of packages being removed if the maintainer is not committing as promised (which usually happens during freezes of next stable). So the only solution is to maintain stable ports for the duration of their upstream life cycle. The problem was with node, so fine, support www/node6 for as long as upstream supports it. Anything else would require tremendous amount of work to cherry pick and backport from a codebase that is increasingly changing and making it much more difficult with each upstream release. if "www/node" is not obvious enough to mean latest node, then rename it to node-latest. As in this case (the original post of this thread), reading UPDATING would've sufficed to avoid any problems. Another example is Roundcube. We have bumped roundcube to 1.2 last year. Personally I balked at this and kept 1.1 around in my local tree until I properly tested 1.2. Another example was irssi that was bumped from 0.8.x to 1.x (and in quarterly even, and approved by ports-secteam!), breaking some plugins in the process. But, given that example, under this new "stable ports" regime, there would be mail/roundcube11, mail/roundcube12 etc... Especially since the upstream continues LTS of older versions. Again, nothing prevents the maintainers from doing it right now. No special project or repo is needed except the maintainers' will and time to do so, which is obviously lacking. And I'll join the concerns expressed earlier, about people who are not familiar with a port, maintaining it. I've seen that cause breakages, because the committer doing the change does not understand the port, and am vehemently against it. -- Vlad K. From owner-freebsd-ports@freebsd.org Fri Jun 23 21:53:42 2017 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 DDE01D8AF61 for ; Fri, 23 Jun 2017 21:53:42 +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 C9DF876296 for ; Fri, 23 Jun 2017 21:53:42 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: by mailman.ysv.freebsd.org (Postfix) id C92FDD8AF60; Fri, 23 Jun 2017 21:53: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 C8A0CD8AF5F for ; Fri, 23 Jun 2017 21:53:42 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (hades.sorbs.net [72.12.213.40]) by mx1.freebsd.org (Postfix) with ESMTP id AD7E576295 for ; Fri, 23 Jun 2017 21:53:42 +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 <0OS000CAAT68ER00@hades.sorbs.net> for ports@freebsd.org; Fri, 23 Jun 2017 15:01:21 -0700 (PDT) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Matt Smith , scratch65535@att.net, freebsd-ports References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <6mupkc5v5oclrd721pssousokmgtqkvfao@4ax.com> <20170623125424.GA10691@gmail.com> From: Michelle Sullivan Message-id: <76e3845a-d05c-7c1a-b548-31381252fe45@sorbs.net> Date: Fri, 23 Jun 2017 23:53:37 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 In-reply-to: <20170623125424.GA10691@gmail.com> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 21:53:43 -0000 Matt Smith wrote: > > I use FreeBSD *precisely* because it mostly keeps up with the latest > stable versions of things. I have postfix 3.2, pgsql 9.6, nginx 1.13, > libressl 2.5 etc. It's usually impossible to do this with linux unless > you install things directly from source. And me I came to FreeBSD because it was security conscious but not latest and greatest or nothing... well not strictly true, P Vixie forced me into trying it.. but I changed from Linux to FreeBSD across my entire product because of stability... which doesn't exist in the same way now (and hasn't since 2013ish).. Running postfix 2.9, pgsql 9.4 (8.4 in some places but they are top priority to upgrade if I can keep up with security issues everywhere else) openssl 1.0.2 and Apache 2.4 (.26 just upgraded myself)... > > I upgrade my ports/packages via poudriere every single day which > mostly just takes 2 minutes of my time as usually that results in > maybe one or two packages being updated at a time. I see this as a > positive thing rather than doing one massive huge upgrade every 3 months. Currently have 87 servers located across 7 continents, all in production processing incoming spam at the millions per day, and serving DNS requests at a rate of over 70,000 queries per second (averaged over a week)... you can't just f**k with that. Patches have to be evaluated, tested, built and regression tested.... -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-ports@freebsd.org Sat Jun 24 05:38:52 2017 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 3DC9BD983EC for ; Sat, 24 Jun 2017 05:38:52 +0000 (UTC) (envelope-from martin@waschbuesch.de) 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 1F91A841AD for ; Sat, 24 Jun 2017 05:38:52 +0000 (UTC) (envelope-from martin@waschbuesch.de) Received: by mailman.ysv.freebsd.org (Postfix) id 1E0F8D983EB; Sat, 24 Jun 2017 05:38:52 +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 1D838D983EA for ; Sat, 24 Jun 2017 05:38:52 +0000 (UTC) (envelope-from martin@waschbuesch.de) Received: from relay01.waschbuesch.it (relay01.waschbuesch.it [IPv6:2a00:cba0:0:100::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.waschbuesch.it", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CFFF6841AC for ; Sat, 24 Jun 2017 05:38:51 +0000 (UTC) (envelope-from martin@waschbuesch.de) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=waschbuesch.de; s=dkim; h=Message-Id:In-Reply-To:To:References:Date:Subject :Mime-Version:Content-Transfer-Encoding:Content-Type:From:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=kM6wyRx1ndau4xVqpQi2Fqy6DPhpElSlzxdL0AjcOvA=; b=bZAUt1hdwuAwdr3MW3wxlFo2GC GRrlR/77fiQHlD8rfR0Y9ytqamy16SBbPeOed3eVYhl4N66NYZzj+h852vFvtxX+GD1FVaocjtWQy iOWjOVIkPapbx5t5SOvp3rP3cEMHfpOvWCKMEm2Ob4SShZUVlNlB/gl1ssmvhBB3Pg4E=; Received: by relay01.waschbuesch.it with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim) (envelope-from ) id 1dOdmS-00029v-61 for ports@freebsd.org; Sat, 24 Jun 2017 05:38:48 +0000 From: =?utf-8?Q?Martin_Waschb=C3=BCsch?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Date: Sat, 24 Jun 2017 07:38:48 +0200 References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <6mupkc5v5oclrd721pssousokmgtqkvfao@4ax.com> <20170623125424.GA10691@gmail.com> <76e3845a-d05c-7c1a-b548-31381252fe45@sorbs.net> To: ports@freebsd.org In-Reply-To: <76e3845a-d05c-7c1a-b548-31381252fe45@sorbs.net> Message-Id: <4B124329-E0E7-4A49-9A6D-A4E2251C2AAE@waschbuesch.de> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2017 05:38:52 -0000 > Am 23.06.2017 um 23:53 schrieb Michelle Sullivan : >=20 > Matt Smith wrote: >>=20 >> I use FreeBSD *precisely* because it mostly keeps up with the latest = stable versions of things. I have postfix 3.2, pgsql 9.6, nginx 1.13, = libressl 2.5 etc. It's usually impossible to do this with linux unless = you install things directly from source. >=20 > And me I came to FreeBSD because it was security conscious but not = latest and greatest or nothing... well not strictly true, P Vixie forced = me into trying it.. but I changed from Linux to FreeBSD across my entire = product because of stability... which doesn't exist in the same way now = (and hasn't since 2013ish).. FWIW, personally, I never perceived statements about FreeBSD's stability = to extend beyond the scope of the (complete) OS itself. I always regarded ports very much as a convenience. pkg even more so. >> I upgrade my ports/packages via poudriere every single day which = mostly just takes 2 minutes of my time as usually that results in maybe = one or two packages being updated at a time. I see this as a positive = thing rather than doing one massive huge upgrade every 3 months. > Currently have 87 servers located across 7 continents, all in = production processing incoming spam at the millions per day, and serving = DNS requests at a rate of over 70,000 queries per second (averaged over = a week)... you can't just f**k with that. Patches have to be evaluated, = tested, built and regression tested.... My personal conclusion is that if I need to ensure that issues = (especially security fixes) are dealt with in a timely manner then I = have to do the patching, testing, evaluating, etc. myself. After all, even if all that was thoroughly done by upstream, port = maintainer, etc., who=E2=80=99s to say my specific setup and config = won=E2=80=99t bring issues to light their testing didn=E2=80=99t? Just my two cents.= From owner-freebsd-ports@freebsd.org Sat Jun 24 07:35:30 2017 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 8A2ACD99CAC for ; Sat, 24 Jun 2017 07:35:30 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "dnvrco-oedge-vip.email.rr.com", Issuer "dnvrco-oedge-vip.email.rr.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A971EEE for ; Sat, 24 Jun 2017 07:35:29 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:56942] helo=localhost) by dnvrco-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id ED/02-03935-A361E495; Sat, 24 Jun 2017 07:35:22 +0000 Date: Sat, 24 Jun 2017 07:35:18 +0000 Message-ID: From: "Thomas Mueller" To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> <5eabe1d2-85a3-f7eb-a1ab-dc5552eb70fe@gjunka.com> <6d35f70b-17f2-d864-68ed-a3637cdc9fbf@gjunka.com> <63e5c4e30a60d51c5a068177b9483206@acheronmedia.hr> Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version X-RR-Connecting-IP: 107.14.64.6:25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2017 07:35:30 -0000 from Vlad K: > On 2017-06-23 23:09, Grzegorz Junka wrote: > > Fine. Considering that maintainers already apply patches to the latest > > quarterly branch. If there were to be OS version branches, it would > > mean that maintainers apart from what they are doing now would > > additionally need to apply selected patches to those OS version > > branches? > "OS version branches" would be a complete waste of time and resources, and it > would remove some level of separation/independence between the base and ports. > The crux of the problem here is so called "stable ports", not necessarily > tying them to the life cycle of a base release. It doesn't make sense to tie > version of a port to the base release. Especially with the new releng support > schedule that would mean 5 years per major version which is quite a lot. (snip) I personally can't see the rationale of many OS version branches of ports: far too much work. I had the thought of something like that for (NetBSD) pkgsrc: a very tall order, considering that pkgsrc has been ported to many OSes besides NetBSD. Imagine a separate branch of pkgsrc for every version and branch of NetBSD, FreeBSD, Linux, etc. I only follow the current branch of FreeBSD ports and pkgsrc, though now I have also become interested in pkgsrc-synth. Tom From owner-freebsd-ports@freebsd.org Sat Jun 24 09:28:13 2017 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 7E13ED9B5F5 for ; Sat, 24 Jun 2017 09:28:13 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (vps.rulingia.com [103.243.244.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C938037C4 for ; Sat, 24 Jun 2017 09:28:11 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp59-167-167-3.static.internode.on.net [59.167.167.3]) by vps.rulingia.com (8.15.2/8.15.2) with ESMTPS id v5O9Rq3N087151 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sat, 24 Jun 2017 19:28:00 +1000 (AEST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id v5O9Ri8n069507 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 24 Jun 2017 19:27:45 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id v5O9RiAP069506 for freebsd-ports@freebsd.org; Sat, 24 Jun 2017 19:27:44 +1000 (AEST) (envelope-from peter) Date: Sat, 24 Jun 2017 19:27:44 +1000 From: Peter Jeremy To: freebsd-ports@freebsd.org Subject: security/libressl not API-compatible with OpenSSL, breaks www/apache24 Message-ID: <20170624092744.GA69225@server.rulingia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS" Content-Disposition: inline X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2017 09:28:13 -0000 --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In , libressl-2.5.4 specifies #define OPENSSL_VERSION_NUMBER 0x20000000L but doesn't provide an API compatible with OpenSSL. In particular, it's missing (at least) SSL_CTX_set_max_proto_version() and SSL_CTX_set_min_proto_version(), which were added in OpenSSL 1.1.0. This breaks (at least) apache-2.4 which includes the code: #if OPENSSL_VERSION_NUMBER >=3D 0x10100000L SSL_CTX_set_max_proto_version(ssl_ctx, max_prot); SSL_CTX_set_min_proto_version(ssl_ctx, min_prot); #endif Does anyone have a suggestion, other than switching from LibreSSL back to OpenSSL? --=20 Peter Jeremy --qMm9M+Fa2AknHoGS Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJZTjCQXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs0fOMP/0XUy5l28y3rBKRQsFNN6T/w wPvorpwn9jkYMxaB/A8vfI8ofdXXN2yvcEqWriff3Yq0AwsgbU+DHy1DqWSEmJVo MKAVbMUJMoS7g0FOsqO0nijf1Zrz2NlQJeVeg/G2qKJdbcBwLYGZdLz+TrM1ynUD mMTdrEtl3CWsRaLJvZZn+HldRq059hC5gbVMcNqJMV+Lc5wiUcOmo2/tcBf+aQqx i12mW5gN3TGfiPlH2gKuWg7vAyDyPqBSmkxD5Lg29XLHKdITJS4mLGOfpbeWljES VjgjmC3CVJiO8uthzreGf5wT3mlN/XKPU07VJRHFK+tKdALBQeLCgWot7QL51fgB jTvnM/zZgipFdA4QZaaZz+xJGJsPBtu4pNdr7ttzU3Bnl1prE3Q2gTiZhAMqEOQE xqCQ25e1sZ8lQ5q7+bZP/JbRWbw2ndATKnAXSoY9IbGSOrzQM2TH4ekL2ROnA6H5 4QBOyZxq7nRXglRpbG0LwnCDuxJtnCKN0XC59rt2I3dTqFNXKsV9i4PErRC5w/Nc lK1Ysg6nkdbiPM4eeU0ucaMaEfInwBrCE8a3fMsG0EuU+sakmANmIWDussXVKOLL bZsdL8V0ZbkH/2/6gK0scOssZ5isxLrvhpPOetPnnvIFsHNJVBnaz+JR3D9qreVZ fZx9itiS8sWqx17oHGhs =gjG3 -----END PGP SIGNATURE----- --qMm9M+Fa2AknHoGS-- From owner-freebsd-ports@freebsd.org Sat Jun 24 11:19:08 2017 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 3F49DD9C955 for ; Sat, 24 Jun 2017 11:19:08 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D9FCF65E5A for ; Sat, 24 Jun 2017 11:19:07 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from crayon2.yoonka.com (crayon2.yoonka.com [10.70.7.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v5OBIx7q083179 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sat, 24 Jun 2017 11:18:59 GMT (envelope-from list1@gjunka.com) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <20170622121856.haikphjpvr6ofxn3@ivaldir.net> <20170622141644.yadxdubynuhzygcy@ivaldir.net> <4jrnkcpurfmojfdnglqg5f97sohcuv56sv@4ax.com> <20170622211126.GA6878@lonesome.com> <594C4663.5080209@quip.cz> <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> <5eabe1d2-85a3-f7eb-a1ab-dc5552eb70fe@gjunka.com> <6d35f70b-17f2-d864-68ed-a3637cdc9fbf@gjunka.com> <63e5c4e30a60d51c5a068177b9483206@acheronmedia.hr> From: Grzegorz Junka Message-ID: <8948545b-5269-8a0e-3f92-9dfd02f227c1@gjunka.com> Date: Sat, 24 Jun 2017 11:18:59 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2017 11:19:08 -0000 >>> Fine. Considering that maintainers already apply patches to the latest >>> quarterly branch. If there were to be OS version branches, it would >>> mean that maintainers apart from what they are doing now would >>> additionally need to apply selected patches to those OS version >>> branches? >> "OS version branches" would be a complete waste of time and resources, and it >> would remove some level of separation/independence between the base and ports. >> The crux of the problem here is so called "stable ports", not necessarily >> tying them to the life cycle of a base release. It doesn't make sense to tie >> version of a port to the base release. Especially with the new releng support >> schedule that would mean 5 years per major version which is quite a lot. > (snip) > > I personally can't see the rationale of many OS version branches of ports: far too much work. > > I had the thought of something like that for (NetBSD) pkgsrc: a very tall order, considering that pkgsrc has been ported to many OSes besides NetBSD. > > Imagine a separate branch of pkgsrc for every version and branch of NetBSD, FreeBSD, Linux, etc. > > I only follow the current branch of FreeBSD ports and pkgsrc, though now I have also become interested in pkgsrc-synth. > > Tom > Are there any advantages of using pkg instead of pkgsrc on FreeBSD? Instead of having branches by OS version, would having ports LTS branches independent of the base system be a better solution? Grzegorz From owner-freebsd-ports@freebsd.org Sat Jun 24 11:27:46 2017 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 6744CD9CB11 for ; Sat, 24 Jun 2017 11:27:46 +0000 (UTC) (envelope-from bruno@clisp.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 4ED2C661AF for ; Sat, 24 Jun 2017 11:27:46 +0000 (UTC) (envelope-from bruno@clisp.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4B2A9D9CB10; Sat, 24 Jun 2017 11:27:46 +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 48FECD9CB0F for ; Sat, 24 Jun 2017 11:27:46 +0000 (UTC) (envelope-from bruno@clisp.org) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AFD6F661AE; Sat, 24 Jun 2017 11:27:45 +0000 (UTC) (envelope-from bruno@clisp.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1498303662; l=2159; s=domk; d=clisp.org; h=Content-Type:Content-Transfer-Encoding:MIME-Version:Date:Subject:To: From; bh=DbEU3zgqxcFaHhXTeKhMFB2P33Ul7Ipwm+IHsTxdtQQ=; b=shvhuXBE/X27/+HQHClM0/Zk/LJ46NtxR2qOjrOchMKoOcIf+2K4pfMTPbdYPMDd4y eHeqgp30UgTUGJXrJ+8jRvSqrRbVgiCGKjPLRBlGXB8JmUXrHjsuyiCsZkE4OejCRQ/B boyR1NhqqaHuwjQxjGRA2FYecJWv6ma4qDhng= X-RZG-AUTH: :Ln4Re0+Ic/6oZXR1YgKryK8brksyK8dozXDwHXjf9hj/zDNRavM45naK X-RZG-CLASS-ID: mo00 Received: from bruno.haible.de (dslb-088-068-035-046.088.068.pools.vodafone-ip.de [88.68.35.46]) by smtp.strato.de (RZmta 41.0 DYNA|AUTH) with ESMTPSA id K02987t5OBRgUzp (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Sat, 24 Jun 2017 13:27:42 +0200 (CEST) From: Bruno Haible To: ports@freebsd.org, linimon@freebsd.org Subject: GNU libffcall 1.13 is released Date: Sat, 24 Jun 2017 13:27:42 +0200 Message-ID: <22704200.OLI8sAPmL0@omega> User-Agent: KMail/5.1.3 (Linux/4.4.0-81-generic; KDE/5.18.0; x86_64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2017 11:27:46 -0000 Hi, GNU libffcall 1.13 is released. You find the download link at the homepage https://www.gnu.org/software/libffcall/ New in 1.13: * The license has been changed from GPLv2 to GPLv2+. * Added support for the following platforms: (Previously, a build on these platforms failed.) - x86_64: Mac OS X 64-bit. - x86_64: Solaris 64-bit. - x86_64: Linux with x32 ABI: CC="gcc -mx32". - arm: Linux 32-bit, without hardware floats. - arm64: Linux 64-bit. - s390x: Linux 64-bit. - powerpc: AIX 64-bit. - mips: IRIX 6.5 with CC="cc -32". - sparc: Solaris 64-bit. * Fixed support for the following platforms: (Previously, a build on these platforms appeared to succeed but was buggy.) - x86_64: Linux. - arm: Linux 32-bit, with hardware floats. - powerpc: Linux 64-bit. - mips: Linux with CC="gcc -mabi=32". - mips: Linux with CC="gcc -mabi=n32". - mips: Linux with CC="gcc -mabi=64". - mips: IRIX 6.5 with CC="gcc -mabi=n32". - s390: Linux. - sparc: Linux 64-bit. - ia64: Linux. - hppa: HP-UX 32-bit. * Verified support for the following platforms: (A build on these platforms worked and still works.) - i386: Linux, Solaris, Mac OS X. - powerpc: Linux 32-bit. - powerpc: AIX 32-bit. - powerpc: MacOS X. - mips: IRIX 6.5 with CC="cc -n32". - sparc: Solaris 32-bit. - sparc: Linux 32-bit: CC="gcc -m32". - alpha: Linux. * Support for a security feature: On Linux and FreeBSD platforms, linking with the libffcall libraries no longer causes the stack to become executable. According to [1][2], you are packaging libffcall for FreeBSD. I invite you to upgrade to version 1.13. With it, you can remove the BROKEN_* lines from [2]. Also, you will no longer need patch-avcall_avcall-sparc64.S [3]. NOTE! Libffcall is usually packaged as a non-shared library. If so, you need to rebuild the packages that depend on it (in particular, GNU clisp). Best regards, Bruno [1] http://www.freshports.org/devel/ffcall [2] https://svnweb.freebsd.org/ports/head/devel/ffcall/Makefile?revision=439720&view=markup [3] https://svnweb.freebsd.org/ports/head/devel/ffcall/files/ From owner-freebsd-ports@freebsd.org Sat Jun 24 12:24:42 2017 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 1CE23D9DED8 for ; Sat, 24 Jun 2017 12:24:42 +0000 (UTC) (envelope-from amutu@amutu.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id E75B467877 for ; Sat, 24 Jun 2017 12:24:41 +0000 (UTC) (envelope-from amutu@amutu.com) Received: by mailman.ysv.freebsd.org (Postfix) id E3742D9DED7; Sat, 24 Jun 2017 12:24:41 +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 E306BD9DED6 for ; Sat, 24 Jun 2017 12:24:41 +0000 (UTC) (envelope-from amutu@amutu.com) Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::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 9E60A67876 for ; Sat, 24 Jun 2017 12:24:41 +0000 (UTC) (envelope-from amutu@amutu.com) Received: by mail-oi0-x234.google.com with SMTP id p66so37075032oia.0 for ; Sat, 24 Jun 2017 05:24:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amutu-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pDOpqFQItLlcIiKTkkioUgLq6BuE82umN/N/cEXBqz8=; b=gPBhKKcmtiZQjqPf2jGmKUKrnHmeDtzGwh2KiYzveSoQoVTWjP3Kge3pN+qypwiK+J WfIQFEswEA6Nx5wx7jlWqceKx3sROpHoTNtWlzHtCNoRqE0E/UrLfIhZ+zA8xV227eXK k4A9lRNIXRtu86LnsNYn58crQfaq0VsHxMcsvim+um/u8yhmtIBSqRigD/owCSdGKlss tAcp+d8Ib4ZgI+l55MSVFYJV+LjJ+buD7LeCZgNo9nxrNOvPMGDGlR4A0Y5l3q28C718 y4Li3TbNxvLrhNO4+nyWF97ZRQATtgvPl8sQmy50Fkul9ftVdyCylg7QmRzn7TkTrOWv 7X8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pDOpqFQItLlcIiKTkkioUgLq6BuE82umN/N/cEXBqz8=; b=szaA2j8apGLFxQ4onzAIEFU+KYfIE3izveY5MNatTCOciTZm1wZ0n3AOb5mTQgEJDg WOhQKyhDZn1uJJCHkhPtX2Wf6H2kKfcnoWUNZEcUzmTXQfnvgvoNPGWsTg9ZmCaNhMlL kCD1fSlGrNj+H4uY7iDu5XRjZIc1qC+Om/naBzNCvXXtsS8PV9oecYY/UROTwejwhKco v5YBKsnIA5oQ/ONMQh7zn2TDv+pLaNwt0kDPUBjqNttfy6DCCKTpEmFCv5v9SUXXBmz3 m3c90mOQrT+OnJV6ynLlgiMKhZ8pp+WPz/IyIqRcHlPvFMS29Y1juFVfRWKJqv0xRThd uzZQ== X-Gm-Message-State: AKS2vOwZZfzPDbIdNTubpyxe0B7I4cnGmqTYTr6gnTPMg8xyJu8lNezE WNPuG2KErmyiHhs4Un69VA== X-Received: by 10.202.79.11 with SMTP id d11mr5267966oib.101.1498307080676; Sat, 24 Jun 2017 05:24:40 -0700 (PDT) Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com. [209.85.218.50]) by smtp.gmail.com with ESMTPSA id f200sm3478684oih.5.2017.06.24.05.24.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 24 Jun 2017 05:24:40 -0700 (PDT) Received: by mail-oi0-f50.google.com with SMTP id p187so37225333oif.3; Sat, 24 Jun 2017 05:24:40 -0700 (PDT) X-Received: by 10.202.104.144 with SMTP id o16mr7481417oik.158.1498307079761; Sat, 24 Jun 2017 05:24:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.133.136 with HTTP; Sat, 24 Jun 2017 05:24:19 -0700 (PDT) In-Reply-To: <22704200.OLI8sAPmL0@omega> References: <22704200.OLI8sAPmL0@omega> From: Jov Date: Sat, 24 Jun 2017 20:24:19 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: GNU libffcall 1.13 is released To: Bruno Haible Cc: FreeBSD Ports Mailing List , linimon@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2017 12:24:42 -0000 Hi Bruno, Thanks for your work=EF=BC=81I submitted an update PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220250,and add you to t= he CC list. Jov 2017-06-24 19:27 GMT+08:00 Bruno Haible : > Hi, > > GNU libffcall 1.13 is released. You find the download link at the homepag= e > https://www.gnu.org/software/libffcall/ > > New in 1.13: > > * The license has been changed from GPLv2 to GPLv2+. > > * Added support for the following platforms: > (Previously, a build on these platforms failed.) > - x86_64: Mac OS X 64-bit. > - x86_64: Solaris 64-bit. > - x86_64: Linux with x32 ABI: CC=3D"gcc -mx32". > - arm: Linux 32-bit, without hardware floats. > - arm64: Linux 64-bit. > - s390x: Linux 64-bit. > - powerpc: AIX 64-bit. > - mips: IRIX 6.5 with CC=3D"cc -32". > - sparc: Solaris 64-bit. > > * Fixed support for the following platforms: > (Previously, a build on these platforms appeared to succeed but was > buggy.) > - x86_64: Linux. > - arm: Linux 32-bit, with hardware floats. > - powerpc: Linux 64-bit. > - mips: Linux with CC=3D"gcc -mabi=3D32". > - mips: Linux with CC=3D"gcc -mabi=3Dn32". > - mips: Linux with CC=3D"gcc -mabi=3D64". > - mips: IRIX 6.5 with CC=3D"gcc -mabi=3Dn32". > - s390: Linux. > - sparc: Linux 64-bit. > - ia64: Linux. > - hppa: HP-UX 32-bit. > > * Verified support for the following platforms: > (A build on these platforms worked and still works.) > - i386: Linux, Solaris, Mac OS X. > - powerpc: Linux 32-bit. > - powerpc: AIX 32-bit. > - powerpc: MacOS X. > - mips: IRIX 6.5 with CC=3D"cc -n32". > - sparc: Solaris 32-bit. > - sparc: Linux 32-bit: CC=3D"gcc -m32". > - alpha: Linux. > > * Support for a security feature: On Linux and FreeBSD platforms, linking > with > the libffcall libraries no longer causes the stack to become executable= . > > > According to [1][2], you are packaging libffcall for FreeBSD. > > I invite you to upgrade to version 1.13. > With it, you can remove the BROKEN_* lines from [2]. > Also, you will no longer need patch-avcall_avcall-sparc64.S [3]. > > NOTE! Libffcall is usually packaged as a non-shared library. If so, you > need > to rebuild the packages that depend on it (in particular, GNU clisp). > > Best regards, > > Bruno > > [1] http://www.freshports.org/devel/ffcall > [2] https://svnweb.freebsd.org/ports/head/devel/ffcall/ > Makefile?revision=3D439720&view=3Dmarkup > [3] https://svnweb.freebsd.org/ports/head/devel/ffcall/files/ > > _______________________________________________ > 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 Sat Jun 24 14:34:46 2017 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 94A59D9FB6B for ; Sat, 24 Jun 2017 14:34:46 +0000 (UTC) (envelope-from adamw@adamw.org) Received: from apnoea.adamw.org (apnoea.adamw.org [104.225.5.94]) (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 6CD5C6E6D3 for ; Sat, 24 Jun 2017 14:34:45 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id 164f573a TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sat, 24 Jun 2017 08:34:38 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: security/libressl not API-compatible with OpenSSL, breaks www/apache24 From: Adam Weinberger In-Reply-To: <20170624092744.GA69225@server.rulingia.com> Date: Sat, 24 Jun 2017 08:34:36 -0600 Cc: freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <9EF3C3B9-AB6A-4A1A-8AED-1D674CCECF60@adamw.org> References: <20170624092744.GA69225@server.rulingia.com> To: Peter Jeremy X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2017 14:34:46 -0000 > On 24 Jun, 2017, at 3:27, Peter Jeremy wrote: >=20 > In , libressl-2.5.4 specifies > #define OPENSSL_VERSION_NUMBER 0x20000000L > but doesn't provide an API compatible with OpenSSL. In particular, > it's missing (at least) SSL_CTX_set_max_proto_version() and > SSL_CTX_set_min_proto_version(), which were added in OpenSSL 1.1.0. > This breaks (at least) apache-2.4 which includes the code: > #if OPENSSL_VERSION_NUMBER >=3D 0x10100000L > SSL_CTX_set_max_proto_version(ssl_ctx, max_prot); > SSL_CTX_set_min_proto_version(ssl_ctx, min_prot); > #endif >=20 > Does anyone have a suggestion, other than switching from LibreSSL back = to > OpenSSL? >=20 > --=20 > Peter Jeremy Try changing it to #if OPENSSL_VERSION_NUMBER >=3D 0x10100000L && = !defined(LIBRESSL_VERSION_NUMBER) # Adam --=20 Adam Weinberger adamw@adamw.org https://www.adamw.org From owner-freebsd-ports@freebsd.org Sat Jun 24 15:07:43 2017 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 4D759DA0480 for ; Sat, 24 Jun 2017 15:07:43 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) Received: from tatiana.utanet.at (tatiana.utanet.at [IPv6:2001:938:1337:25::25:46]) (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 0E0DB6F509 for ; Sat, 24 Jun 2017 15:07:43 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=utanet.at; s=rev1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Subject:References:To; bh=bNeaVP7L+XnRo5bYJHMUXPwD1TQ6el5A5rbryMxcS3o=; b=BPe8othm1zFz1ocHGtb/rGhd0FsvpCfwgKB8rszq1B9w23bEUFZ9t2dD7i+UOoyX4lL8alJyBS6GfF85cgKidkwdDjrCqhVL7h5o2WSK4hOgtE+3RnlA9d8PasgmHyq6NDYumXNtAgq8lH9AIUifjWEWQMnaQPHztt1qjkHC7Uw=; Received: from paris.xoc.tele2net.at ([213.90.36.7]) by tatiana.utanet.at with esmtp (Exim 4.80) (envelope-from ) id 1dOmey-00084m-6t for freebsd-ports@freebsd.org; Sat, 24 Jun 2017 17:07:40 +0200 Received: from 188-23-8-224.adsl.highway.telekom.at ([188.23.8.224] helo=[10.0.0.93]) by paris.xoc.tele2net.at with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1dOmey-0004Nk-4q for freebsd-ports@freebsd.org; Sat, 24 Jun 2017 17:07:40 +0200 To: freebsd-ports@freebsd.org References: <20170624092744.GA69225@server.rulingia.com> Subject: Re: security/libressl not API-compatible with OpenSSL, breaks www/apache24 From: Walter Schwarzenfeld Message-ID: <93d1f104-cd1a-3654-754e-c5616bce8fb2@utanet.at> Date: Sat, 24 Jun 2017 17:07:33 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <20170624092744.GA69225@server.rulingia.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-TELE2-Authenticated-As: cf62768e218b4d81d95cc5390f1bd9dfc8b05683 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2017 15:07:43 -0000 There is a working patch: https://bz.apache.org/bugzilla/show_bug.cgi?id=61184 From owner-freebsd-ports@freebsd.org Sat Jun 24 20:47:28 2017 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 094EDDA55EE for ; Sat, 24 Jun 2017 20:47:28 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-sn1nam04olkn082a.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe4c::82a]) (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 BA5E4787B4 for ; Sat, 24 Jun 2017 20:47:27 +0000 (UTC) (envelope-from carmel_ny@outlook.com) 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=O8eKRXPc+XnqumofKqBDWmRXup9VJrIHL1bHO9yhgFw=; b=XenayTW4edpF8kiuBpqdJHqVrszWedPc5jNPw3FfuKJJiGnG6QNh6NnKe7omAjcu0DW02y2V1yDkC+9mBiSMGUhmF4JUsAiX9iODCwzxyWInk12z50kza1Tsg34sZ9WT4/EXHeLf32DxCqzO9Xgr60A8dNiYfbUx43sbQaXwxtk3j28SAOqPPSwS+sHVdmj/3/JiS7OJah+rl07y+DN966sJbg2xr9QQEKS1AItQi81W87fcwS3og8ePBjJLcApjmB/DjtT4HJFEaWYb4ZfN4haUnOP+6JbVnmfZWXX6ygmx0Czq4I8OCM3nwWOPhyrDiTL2ssfHAf4d73QWidmPwA== Received: from SN1NAM04FT006.eop-NAM04.prod.protection.outlook.com (10.152.88.52) by SN1NAM04HT203.eop-NAM04.prod.protection.outlook.com (10.152.89.49) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1178.14; Sat, 24 Jun 2017 20:47:11 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com (10.152.88.54) by SN1NAM04FT006.mail.protection.outlook.com (10.152.88.166) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1199.9 via Frontend Transport; Sat, 24 Jun 2017 20:47:11 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) by BN6PR2001MB1730.namprd20.prod.outlook.com ([10.172.31.146]) with mapi id 15.01.1199.017; Sat, 24 Jun 2017 20:47:11 +0000 From: Carmel NY To: FreeBSD Ports CC: "sf@maxempire.com" Subject: clamav-unofficial-sigs Thread-Topic: clamav-unofficial-sigs Thread-Index: AQHS7SsNAVqxvVnapEWJevxyuaJmpQ== Date: Sat, 24 Jun 2017 20:47:11 +0000 Message-ID: Reply-To: FreeBSD Ports Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=outlook.com; x-incomingtopheadermarker: OriginalChecksum:8A619E3417F084C072D73608D8ACAEEA5712D2B6E98CE500D08C443E472FF0DF; UpperCasedChecksum:8E2C074C6939D84A1694BF11CB3E12927734AE3C174EC586C74D79296829C0C0; SizeAsReceived:7121; Count:45 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [TnVWgLdvzTU5PIGZRrPJyabEuJV5SBo7] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; SN1NAM04HT203; 7:mn9vvPUJ9zwCAZLMNz+4o1ODVBkWuHApV50GgKS/0K7tUHmhMR5bDmgAyQYV7RRAmSwtBptOEAbgvGxkoKt/o2wVgQoom3k0oE0H/4vgip/ubtalcM2iNzIRv3WUI0SlDMGm6+0jvWg4ZMieuvPwz3yC5LGcc8spVuUZF/3B9nGveLoBUyuDis+3BQofsjfKwXtgpvCENGWSAk17TWObZLuZ+GuG1Fmjf6hiPOzpNDEvEFIJb+giskYOMm8PQs68Rsj+Kx+MQQiQjaHiGlzutX4gt1RCneNyCK6pOPo+R8dM1ZWyYapNsmTkt51/KUvBEHf03n/rb52KufP2rOKB5c/VzqMYSJt9stfnrfDctbvWgB50dh6WfPU5RG5w2lj5s1k2gJjHJqi9LqzsAd5shQWE3dirctfSKleC9f6m1lXENEDRyu2aSxXbWn2EvSnSHeNl5NPZFAqHNMRvyi6Vp4UNpzufF2KqareAL/t4g2UNLvoQBTj0XdkNhbaMlbwQBdnC4KBOmbTXGlMN6NJoAExnHmd440Do3BXZQm//jz9s0/C8C8FLqAgaznBB5LSE+HTecRkK6gdrD8xSOjGO48LH20427vccDhHs2ocNMkEydoGD8xCo3/mxcl4y7Ouf0/1lIXQGBbNfGgGbswDZbVuf71FDFSn4RaapXmNFMrNa5L8dlXgLzA0rZbzdwyDRSEp03oKILMxaz3QixxfOokbdmjxyeEMZIVMhVt5rWezBFYdEjKQLOCG8a9xJIG0PgfSulVdQcyAxaimvhCirDA== x-incomingheadercount: 45 x-eopattributedmessage: 0 x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:SN1NAM04HT203; H:BN6PR2001MB1730.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: 6cc30787-c537-44f1-d15f-08d4bb422fe0 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045)(300000504095)(300135200095)(300000505095)(300135600095); SRVR:SN1NAM04HT203; x-ms-traffictypediagnostic: SN1NAM04HT203: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:SN1NAM04HT203; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:SN1NAM04HT203; x-forefront-prvs: 03484C0ABF spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-ID: <2620892219BFBE4D8CEF85D1A36F4EBA@namprd20.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Jun 2017 20:47:11.7987 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM04HT203 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2017 20:47:28 -0000 The port version of "clamav-unofficial-sigs" is 5.3.2; however a newer version 5.6.2 is available. The port version is quite old. Are there any plans to update the port? --=20 Carmel From owner-freebsd-ports@freebsd.org Sat Jun 24 21:15:46 2017 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 49903DA5E26 for ; Sat, 24 Jun 2017 21:15:46 +0000 (UTC) (envelope-from bob@eager.cx) Received: from kipling.tavi.co.uk (kipling.tavi.co.uk [81.187.145.130]) by mx1.freebsd.org (Postfix) with ESMTP id 053437932C for ; Sat, 24 Jun 2017 21:15:45 +0000 (UTC) (envelope-from bob@eager.cx) Received: from kipling.tavi.co.uk (localhost [127.0.0.1]) by kipling.tavi.co.uk (Postfix) with ESMTP id 5FC63892BE for ; Sat, 24 Jun 2017 22:15:44 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=eager.cx; h=date:from:to :subject:message-id:mime-version:content-type :content-transfer-encoding; s=selector1; bh=NlfBOU/oYugIbI2PJGVG YnD8ehA=; b=Gnp25IrwzZnmlEgMizWhvDEBDr3FJtWXznjaMAa0WcHUKXBNtNxP F98wJiXjNDIEoC1Ppht8q0nQDhdy28BGAr9KH1q1XYAKp7kxIe2XODy1Sko31ySR XazIKD9vbm29EtOjadew7MWNpmLO5Xx1LGRGzDTc1kojOzpIdwWjJ/0= Received: from raksha.tavi.co.uk (raksha.tavi.co.uk [81.187.145.139]) (Authenticated sender: rde@tavi.co.uk) by kipling.tavi.co.uk (Postfix) with ESMTPA id 6A007892BB for ; Sat, 24 Jun 2017 22:15:43 +0100 (BST) Date: Sat, 24 Jun 2017 22:15:43 +0100 From: Bob Eager To: freebsd-ports@freebsd.org Subject: Easytag crashes with SIGABRT - stack overflow Message-ID: <20170624220439.3f884d4d@raksha.tavi.co.uk> X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; i386-portbld-freebsd11.0) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAMFBMVEUwXjFLc0vD0cS7y7zw9PDZ4tkWSRaVrZZ+m39qi2tXfVj////7+/utwK4IPggAOAAJUUA7AAABKklEQVQ4jWPYjQMwDFYJp0NKEKCNJmEf9h8CsimXiL2e33s3/e7F7K2Cs3f3dCMkQkMKj4YuCY3K3iR+e7fMaiSjvkX0/5cFGrWpe2uLzOpaExUVqMS/8PX/Re5ey960OLBTZpFA8+IlSBKPQ92zNyUUBsosN58uIY0k8f+/ONCoYytkVuhWzVwNkYiYbqk5M3NmOVBi41YZ8RsGF7shEtFb5KJ3r969CyixM7OTPeFUxG2IxLO8/9/SvqXlc+/x3h295YzLlj2nIRJQj//nRvc5TEIal8RsXBLVuCQwIgoq/u80DomP6HEOk/iOS+IJLonZOCT+ReOQ+Lkbh0QKLonbOCR+7MYhsRqHBJrVcIl/1TgklqKLQyQ+tGKIgyQOqXpjig94diZRAgAXmDX6jyWafAAAAABJRU5ErkJggg====== 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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2017 21:15:46 -0000 Before I submit an actual bug report, I wanted advice as to whether I'm doing something silly! I've been using Easytag for about 3 years now. All has been fine. I recently upgraded from 10.3-RELEASE to 11.0-STABLE. I also updated the ports (built locally). Easytag now crashes as soon as I try to look at an album. SIGABRT - and a kernel message about stack overflow. I've tried increasing the stack size (via sysctl and reboot) by 50%, and there is no change. Am I missing something? -- Bob From owner-freebsd-ports@freebsd.org Sat Jun 24 21:55:01 2017 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 35BC5DA662A for ; Sat, 24 Jun 2017 21:55:01 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::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 CE9EB7A4BC for ; Sat, 24 Jun 2017 21:55:00 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wr0-x233.google.com with SMTP id r103so107219797wrb.0 for ; Sat, 24 Jun 2017 14:55:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=u9wifrLnZDeWiFCFlgxvjk/+tDl+7qyAx+hbH4QP9eI=; b=eBbRQ243gmZ4G99EI6bOpxaNYL3QIIuy3Xcz61IWbqEbVSD/Q6mu4DQgpolE64fORr +4dDCbNsbr4/5oIObE3rqCEsQe25wRdbjxc8LIn2zIE1LRwf1a0t7N39d8FCmjZhwN78 rFnzMlAKlqcEp9ta9NbARxJxhG8pO3MnnoAa0nfuc38xHJxHq/l9AOVSlpz3H6QoseT9 PnHxAo4y0uL5/D2UG5pXK3kM1A9J3+Q/KToaQAgq4CzGKFHvKduHlfhIY9zE4WcRbX6U RDA0Ujh0El1YNlJVSXBaoAFhY0CH1q28MZkS6uI8PODVc5nakiIZKxUzj8sMgDK5ahAj xStQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=u9wifrLnZDeWiFCFlgxvjk/+tDl+7qyAx+hbH4QP9eI=; b=nkLJtW1M0b2ur4wGfpMF7avKDUFMSufnThU1AfUmKNg7fQTWJHRkxa96ROCgb1P/wy 2CZLrXZpTqampjP/fUHhZFohaAxJg0ME0WinjhlyW+qTVZUns4fAX8bn4k6vUrzueV9s v2pp++qybZ1WSeyF7ufc6Na4NGWuOajNJKRSC5ygnjqrOExAd9AUPsppEIGp112oxEXz L6fJNywLnxNeDFSpgqtRlD7GVyLx3JtWYbZpzZh1JPEXerTY/DxziM2AMjvFLzp/JuLP oysAyK2C98wxMyk2YM+ScMmyNQuZi/j5eTfYIHZPO5pvaH0ogf70jQ5Qw3P+JsanogDh y52w== X-Gm-Message-State: AKS2vOwNN9ox44lRg5UJG9sC9gusZwsSCQKm+splRnBzlUAl9S+mOgaj XrRRwwdShd050L7bwW67dg== X-Received: by 10.223.169.169 with SMTP id b38mr2486427wrd.126.1498341298330; Sat, 24 Jun 2017 14:54:58 -0700 (PDT) Received: from [10.10.1.111] ([185.97.61.15]) by smtp.gmail.com with ESMTPSA id l12sm10391029wrc.46.2017.06.24.14.54.56 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 24 Jun 2017 14:54:57 -0700 (PDT) Subject: Re: Easytag crashes with SIGABRT - stack overflow To: freebsd-ports@freebsd.org References: <20170624220439.3f884d4d@raksha.tavi.co.uk> From: Steven Hartland Message-ID: Date: Sat, 24 Jun 2017 22:54:56 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170624220439.3f884d4d@raksha.tavi.co.uk> Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2017 21:55:01 -0000 amd64 or i386? On 24/06/2017 22:15, Bob Eager wrote: > Before I submit an actual bug report, I wanted advice as to whether I'm > doing something silly! > > I've been using Easytag for about 3 years now. All has been fine. > > I recently upgraded from 10.3-RELEASE to 11.0-STABLE. I also updated > the ports (built locally). > > Easytag now crashes as soon as I try to look at an album. SIGABRT - and > a kernel message about stack overflow. I've tried increasing the stack > size (via sysctl and reboot) by 50%, and there is no change. > > Am I missing something? > From owner-freebsd-ports@freebsd.org Sat Jun 24 22:09:07 2017 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 CBB14DA6A7C for ; Sat, 24 Jun 2017 22:09:07 +0000 (UTC) (envelope-from rde@tavi.co.uk) Received: from kipling.tavi.co.uk (kipling.tavi.co.uk [81.187.145.130]) by mx1.freebsd.org (Postfix) with ESMTP id 816327A964 for ; Sat, 24 Jun 2017 22:09:07 +0000 (UTC) (envelope-from rde@tavi.co.uk) Received: from kipling.tavi.co.uk (localhost [127.0.0.1]) by kipling.tavi.co.uk (Postfix) with ESMTP id 02E98892BE for ; Sat, 24 Jun 2017 23:09:05 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=tavi.co.uk; h=date:from:to :subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=selector1; bh=VVegI+E fgi/7vCL4HAQJH594f1U=; b=l8nqcyZjsT1f4RKQNRJXjjd0y7yOQgLenjQxfxe JG7FOGlhZPNHut3jxDOvJxUlB43FaW8/0BOtadKeHC9/ShBzo5cn1upOGKOnhlpF WcWUF+dz9BWaM2G/adYenPGHNL50x+V+bA+3AZ67yfm3XBQ/KMF8livZDQ0vFrt1 AqxI= Received: from raksha.tavi.co.uk (raksha.tavi.co.uk [81.187.145.139]) (Authenticated sender: rde@tavi.co.uk) by kipling.tavi.co.uk (Postfix) with ESMTPA id A8C27892BB for ; Sat, 24 Jun 2017 23:09:04 +0100 (BST) Date: Sat, 24 Jun 2017 23:09:04 +0100 From: Bob Eager To: freebsd-ports@freebsd.org Subject: Re: Easytag crashes with SIGABRT - stack overflow Message-ID: <20170624230904.59dbb423@raksha.tavi.co.uk> In-Reply-To: References: <20170624220439.3f884d4d@raksha.tavi.co.uk> X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; i386-portbld-freebsd11.0) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAMFBMVEUwXjFLc0vD0cS7y7zw9PDZ4tkWSRaVrZZ+m39qi2tXfVj////7+/utwK4IPggAOAAJUUA7AAABKklEQVQ4jWPYjQMwDFYJp0NKEKCNJmEf9h8CsimXiL2e33s3/e7F7K2Cs3f3dCMkQkMKj4YuCY3K3iR+e7fMaiSjvkX0/5cFGrWpe2uLzOpaExUVqMS/8PX/Re5ey960OLBTZpFA8+IlSBKPQ92zNyUUBsosN58uIY0k8f+/ONCoYytkVuhWzVwNkYiYbqk5M3NmOVBi41YZ8RsGF7shEtFb5KJ3r969CyixM7OTPeFUxG2IxLO8/9/SvqXlc+/x3h295YzLlj2nIRJQj//nRvc5TEIal8RsXBLVuCQwIgoq/u80DomP6HEOk/iOS+IJLonZOCT+ReOQ+Lkbh0QKLonbOCR+7MYhsRqHBJrVcIl/1TgklqKLQyQ+tGKIgyQOqXpjig94diZRAgAXmDX6jyWafAAAAABJRU5ErkJggg====== 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.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jun 2017 22:09:07 -0000 Sorry, I always leave something out! i386 On Sat, 24 Jun 2017 22:54:56 +0100 Steven Hartland wrote: > amd64 or i386? > > On 24/06/2017 22:15, Bob Eager wrote: > > Before I submit an actual bug report, I wanted advice as to whether > > I'm doing something silly! > > > > I've been using Easytag for about 3 years now. All has been fine. > > > > I recently upgraded from 10.3-RELEASE to 11.0-STABLE. I also updated > > the ports (built locally). > > > > Easytag now crashes as soon as I try to look at an album. SIGABRT - > > and a kernel message about stack overflow. I've tried increasing > > the stack size (via sysctl and reboot) by 50%, and there is no > > change. > > > > Am I missing something? > > > > _______________________________________________ > 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"