From owner-freebsd-ports@freebsd.org Sun Jun 25 00:55: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 57C7BDA8C31 for ; Sun, 25 Jun 2017 00:55:11 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-43.reflexion.net [208.70.210.43]) (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 1CB317DDF1 for ; Sun, 25 Jun 2017 00:55:10 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 27488 invoked from network); 25 Jun 2017 00:55:08 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 25 Jun 2017 00:55:08 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.1) with SMTP; Sat, 24 Jun 2017 20:55:08 -0400 (EDT) Received: (qmail 22288 invoked from network); 25 Jun 2017 00:55:08 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 25 Jun 2017 00:55:08 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id AEB10EC86E7; Sat, 24 Jun 2017 17:55:07 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work Message-Id: <6FD738D6-F163-4BC5-8E6E-A9B9F35595CD@dsl-only.net> Date: Sat, 24 Jun 2017 17:55:07 -0700 Cc: Pedro Giffuni , Gerald Pfeifer To: re@FreeBSD.org, FreeBSD-STABLE Mailing List , FreeBSD Toolchain , FreeBSD Ports 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: Sun, 25 Jun 2017 00:55:11 -0000 The following is based mostly on an extraction from a private exchange in which a question was asked and my answer was unsettling: incompatibilities within the 11.* family. I would not normally send to re but doing so was explicitly mentioned. Hopefully this example is reasonable for doing that. Aspect #0: what is broken currently (and in the future?) within the 11.* family? lang/gcc* packages built on release/11.0.1/ to not work fully on stable/11/ or on the drafts of release/11.1.0/ . (I leave releng/11.*/'s implicit.) -r313194 in head and was describied with: > Define the vm_ooffset_t and vm_pindex_t types as machine-independend. >=20 > The types are for the byte offset and page index in vm object. They > are similar to off_t, which is defined as 64bit MI integer. Using MI > definitions will allow to provide consistent MD values of vm > object-related maximum sizes. The known issue is the generation of header dependencies in the lang/gcc* builds on release/11.0.1/ that when used on stable/11/ or release/11.0.1/ generate reports like: = /usr/local/lib/gcc5/gcc/x86_64-portbld-freebsd11.0/5.4.0/include-fixed/sys= /types.h:266:9: error: '__vm_ooffset_t' does not name a type typedef __vm_ooffset_t vm_ooffset_t; ^ = /usr/local/lib/gcc5/gcc/x86_64-portbld-freebsd11.0/5.4.0/include-fixed/sys= /types.h:268:9: error: '__vm_pindex_t' does not name a type typedef __vm_pindex_t vm_pindex_t; ^ *** [CoinFactorization2.lo] Error code 1 Unfortunately UPDATING was not updated for head/'s -r313194 (2017-Feb-4) --nor for stable/11/'s -r313574 (2017-Feb-11), the MFC. (No MFC was made to stable/10/ or to release/10.3.0 as far as I found.) (These changes predate the INO64 issue in head/ . Head ends up with more issues than I'm dealing with here.) Aspect #1: what 11.* version builds the pre-built packages targeting 11.* and the apparent consequences (given the vm_ooffset_t and vm_pindex_t changes and the lang/gcc* build behavior) This is the unsettling part for pre-built packages: incompatibilities within the 11.* family for the lang/gcc* packages. = http://portsmon.freebsd.org/portoverview.py?category=3D%3Bamng&portname=3D= gcc5&wildcard=3D shows categories for builds for 8.4 9.3 10.1 10.3 11.0 head (Nothing for stable/*/ .) But the 10.3 rows show no package builds. I would guess that they start once 10.1 stops (approximately). So it may be that 11.1 will not get package builds until 11.0 stops (approximately). If so unless lang/gcc* are changed to bootstrap differently they will configure to match release/11.0.1/ and will not be compatible with the vm_ooffset_t and vm_pindex_t changes in stable/11/ and release/11.1.0/ . But as I understand updating how the lang/gcc* builds work to remove such dependencies is under investigation. I do not know any timing relative to release/11.1.0/ if my understanding is right. Until then (if I was right): Unless there are separate packages made for targeting release/11.0.1/ vs. release/11.1.0/ it is not obvious when lang/gcc* packages will be generally compatible with various folks choices about what to install as the system version within the release/11.*/ and stable/11/ family. This would likely be true even if they were built on release/11.1.0/ : then release/11.0.1/ likely would have compatibility problems. The ABI versioning does not cover the specific issues involved based on how vm_ooffset_t and vm_pindex_t were changed and what the lang/gcc* builds do relative to such changes. Yet there is incompatibility for some fairly-significant-usage ports. Aspect #2: stable/10/ and release/10.4.0/ Just covered for completeness: I do not see a MFC of -r313194 to stable/10/ : its sys/sys/types.h dates back to 2015-Oct-10. So it looks like 10.x has a permanent difference in this area: 10.x continues to get separate lang/gcc* package builds from 11.x and later. No problem for this context as far as I know. Note: To simplify I choose to not be explicit about what authors wrote what original text. If that becomes an issue, it is correctable. Blame me for any errors in the above. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Sun Jun 25 02:54: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 10A26D87784 for ; Sun, 25 Jun 2017 02:54:13 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::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 8AA5C8135C for ; Sun, 25 Jun 2017 02:54:12 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-wr0-x230.google.com with SMTP id c11so110856957wrc.3 for ; Sat, 24 Jun 2017 19:54:12 -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=6bdcVjdTzUZgX9jfdHRUIUJ+cPrBeeQSEgtC6R76sz4=; b=GfKPIg3CpKlSS65zhGyTatWM7W9pB/iopLrFALsBCTX18j+gJiUn+i1R9dC9+mSvle atrQM3VLXQI9l/9fOl2vQFShP7Zdol2ja2Y4hUxG/0IAlaKNlhvyNUrHQB32NdTzbsSi hSeO5Lx7QjSRiYkMV64IUgQOihKlvjYCTLOcOqKe5xElaZKK2hdJCrEyHPB1CGwZZDV4 V+jDQ9sTviGEbbcfXFHcksfJhJjIRsJ5QBErfAsDEFo49ZpxcUMlxlW6nyAbW5QCg4lB bk+P4wapdOHH0nmQBnkXrVSCoNDVGMzzSs3w/JPo83Z3Uklc/BJAIb/J2jY8bs25BOCC SsMQ== 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=6bdcVjdTzUZgX9jfdHRUIUJ+cPrBeeQSEgtC6R76sz4=; b=hrGQdAW76qWxawrSzRaz+meZspvTmfAH2ZsWIpqNwHWOtmGwncrm7FEJGWKYDV+DTJ mIgw5Xn8/X8nE45az7rWampFP44TrFrzZv/R/a8LZqDioe8rMLjEApSaBxsO7AtrZ/jx bX54AhuMSKZChTYETCKIeun3v3uPDtFVNjzylW0L+n82k3i+ztgrJPhLp3rifH3KUeVN OYmcB8FYiUAnoBu8FIKux+PKN2lpT1dAqs4McWujZnAiwpG+kstX3jKap4wxSvrpuXCt 7+hokVGVgyQTd9d9RG3Pya3HoyJ3NWHWSXV9YWG6Pg9wvZZNsC70UhSWWVpuOxE4UhD1 FV1A== X-Gm-Message-State: AKS2vOyBt9fPabwvKddvYpEl2HmT5szaPqOzuJdwS68UonaTzdcBUXFJ cPacdHXPyA1hy5w5rSd0czR20BLNwzkr30w= X-Received: by 10.80.168.132 with SMTP id k4mr11537369edc.156.1498359250893; Sat, 24 Jun 2017 19:54:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.186.175 with HTTP; Sat, 24 Jun 2017 19:54:10 -0700 (PDT) From: Ben Woods Date: Sun, 25 Jun 2017 10:54:10 +0800 Message-ID: Subject: pkg(8) fails to upgrade to different branches of software To: FreeBSD ports 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: Sun, 25 Jun 2017 02:54:13 -0000 Hi everyone, The recent change of postgresql default version from 9.3 to 9.5 in r444116 required pkg to replace any postgresql93-* packages with postgresql95-* packages, and also reinstall any ports which changed their dependency from the 93 version to the 95 version. This did not succeed automatically with "pkg upgrade -y" as can be seen below. I realise the UPDATING entry explained to first remove the old packages and then install the new packages, but I would like to ask if there is a way this can be improved so it works automatically, and if there is a plan in place to improve this? This problem appears to have 2 issues: 1. pkg is not recognising the CONFLICTS when initially determining the upgrade path (they are specified in the master port databases/postgresql92-server/Makefile) 2. once the packages have been fetched and pkg notices the file conflict, the solver does not decide to remove the pkg with the lower version # pkg upgrade -y Updating FreeBSD-ports repository catalogue... FreeBSD-ports repository is up to date. All repositories are up to date. Checking for upgrades (8 candidates): ........ done Processing candidates (8 candidates): ........ done The following 9 package(s) will be affected (of 0 checked): New packages to be INSTALLED: postgresql95-client: 9.5.7 [FreeBSD-ports] Installed packages to be UPGRADED: vim: 8.0.0642 -> 8.0.0670 [FreeBSD-ports] qt5-script: 5.7.1_1 -> 5.7.1_2 [FreeBSD-ports] llvm40: 4.0.1.r1_5 -> 4.0.1 [FreeBSD-ports] libreoffice: 5.3.3_2 -> 5.3.4 [FreeBSD-ports] gutenprint: 5.2.12_1 -> 5.2.12_2 [FreeBSD-ports] freebsd-release-manifests: 20170617 -> 20170624 [FreeBSD-ports] Installed packages to be REINSTALLED: rubygem-pg-0.21.0 [FreeBSD-ports] (direct dependency changed: postgresql95-client) gimp-gutenprint-5.2.12 [FreeBSD-ports] (direct dependency changed: perl5) Number of packages to be installed: 1 Number of packages to be upgraded: 6 Number of packages to be reinstalled: 2 The process will require 10 MiB more space. 370 MiB to be downloaded. [1/9] Fetching vim-8.0.0670.txz: .......... done [2/9] Fetching rubygem-pg-0.21.0.txz: .......... done [3/9] Fetching qt5-script-5.7.1_2.txz: .......... done [4/9] Fetching llvm40-4.0.1.txz: .......... done [5/9] Fetching libreoffice-5.3.4.txz: .......... done [6/9] Fetching gutenprint-5.2.12_2.txz: .......... done [7/9] Fetching gimp-gutenprint-5.2.12.txz: .......... done [8/9] Fetching freebsd-release-manifests-20170624.txz: ... done [9/9] Fetching postgresql95-client-9.5.7.txz: .......... done Checking integrity... done (1 conflicting) - postgresql95-client-9.5.7 [FreeBSD-ports] conflicts with postgresql93-client-9.3.17 [installed] on /usr/local/bin/clusterdb Checking integrity... done (0 conflicting) Conflicts with the existing packages have been found. One more solver iteration is needed to resolve them. The following 12 package(s) will be affected (of 0 checked): New packages to be INSTALLED: postgresql95-client: 9.5.7 [FreeBSD-ports] Installed packages to be UPGRADED: gutenprint: 5.2.12_1 -> 5.2.12_2 [FreeBSD-ports] vim: 8.0.0642 -> 8.0.0670 [FreeBSD-ports] qt5-script: 5.7.1_1 -> 5.7.1_2 [FreeBSD-ports] llvm40: 4.0.1.r1_5 -> 4.0.1 [FreeBSD-ports] libreoffice: 5.3.3_2 -> 5.3.4 [FreeBSD-ports] freebsd-release-manifests: 20170617 -> 20170624 [FreeBSD-ports] Installed packages to be REINSTALLED: pkg-1.10.1 [FreeBSD-ports] rubygem-pg-0.21.0 [FreeBSD-ports] (direct dependency changed: postgresql95-client) gimp-gutenprint-5.2.12 [FreeBSD-ports] (direct dependency changed: perl5) Number of packages to be installed: 1 Number of packages to be upgraded: 6 Number of packages to be reinstalled: 3 The process will require 10 MiB more space. 3 MiB to be downloaded. [1/12] Fetching pkg-1.10.1.txz: .......... done [1/12] Fetching postgresql93-client-9.3.17.txz: .......... done [1/12] Deinstalling postgresql93-client-9.3.17... Deleting files for postgresql93-client-9.3.17: .......... done [1/12] Upgrading gutenprint from 5.2.12_1 to 5.2.12_2... Extracting gutenprint-5.2.12_2: .......... done [1/12] Installing postgresql95-client-9.5.7... Extracting postgresql95-client-9.5.7: .......... done Installing postgresql93-client-9.3.17... pkg: postgresql93-client-9.3.17 conflicts with postgresql95-client-9.5.7 (installs files into the same place). Problematic file: /usr/local/bin/clusterdb Note that this appears to effectively remove the old postgresql93-client port, so a subsequent pkg run succeeds: # pkg info | grep postgres postgresql95-client-9.5.7 PostgreSQL database (client) rubygem-postgres_ext-3.0.0 PostgreSQL data types extension for ActiveRecord # pkg upgrade Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating FreeBSD-ports repository catalogue... FreeBSD-ports repository is up to date. All repositories are up to date. Checking for upgrades (7 candidates): 100% Processing candidates (7 candidates): 100% Checking integrity... done (0 conflicting) The following 7 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: vim: 8.0.0642 -> 8.0.0670 [FreeBSD-ports] qt5-script: 5.7.1_1 -> 5.7.1_2 [FreeBSD-ports] llvm40: 4.0.1.r1_5 -> 4.0.1 [FreeBSD-ports] libreoffice: 5.3.3_2 -> 5.3.4 [FreeBSD-ports] freebsd-release-manifests: 20170617 -> 20170624 [FreeBSD-ports] Installed packages to be REINSTALLED: rubygem-pg-0.21.0 [FreeBSD-ports] (direct dependency changed: postgresql95-client) gimp-gutenprint-5.2.12 [FreeBSD-ports] (direct dependency changed: perl5) Number of packages to be upgraded: 5 Number of packages to be reinstalled: 2 Proceed with this action? [y/N]: y [1/7] Upgrading vim from 8.0.0642 to 8.0.0670... [1/7] Extracting vim-8.0.0670: 100% You may need to manually remove /usr/local/etc/vim/vimrc if it is no longer needed. [2/7] Reinstalling rubygem-pg-0.21.0... [2/7] Extracting rubygem-pg-0.21.0: 100% [3/7] Upgrading qt5-script from 5.7.1_1 to 5.7.1_2... [3/7] Extracting qt5-script-5.7.1_2: 100% [4/7] Upgrading llvm40 from 4.0.1.r1_5 to 4.0.1... [4/7] Extracting llvm40-4.0.1: 100% [5/7] Upgrading libreoffice from 5.3.3_2 to 5.3.4... [5/7] Extracting libreoffice-5.3.4: 100% [6/7] Reinstalling gimp-gutenprint-5.2.12... [6/7] Extracting gimp-gutenprint-5.2.12: 100% [7/7] Upgrading freebsd-release-manifests from 20170617 to 20170624... [7/7] Extracting freebsd-release-manifests-20170624: 100% # Regards, Ben -- From: Benjamin Woods woodsb02@gmail.com From owner-freebsd-ports@freebsd.org Sun Jun 25 06:23:33 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 BE1A8D8A8E1 for ; Sun, 25 Jun 2017 06:23:33 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.226]) (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 97510C38 for ; Sun, 25 Jun 2017 06:23:33 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:42459] helo=localhost) by dnvrco-omsmta03 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id B7/46-01815-DD65F495; Sun, 25 Jun 2017 06:23:26 +0000 Date: Sun, 25 Jun 2017 06:23:24 +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> <8948545b-5269-8a0e-3f92-9dfd02f227c1@gjunka.com> Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version X-RR-Connecting-IP: 107.14.64.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: Sun, 25 Jun 2017 06:23:33 -0000 > > 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 It looks like you might have misunderstood something I said about pkgsrc. I use pkg with FreeBSD ports on FreeBSD, but my interest in pkgsrc and pkgsrc-synth is for NetBSD. Working with pkgsrc on NetBSD convinces me that they need to import portupgrade and/or portmaster from FreeBSD, maybe synth will be better? Pkgsrc is awkward dealing with packages whose names have changes or branched. Ports LTS branches, is that Long Term Service? I don't really understand that question. Tom From owner-freebsd-ports@freebsd.org Sun Jun 25 07:39: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 92E71D8B83A for ; Sun, 25 Jun 2017 07:39:45 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7E4E427A7 for ; Sun, 25 Jun 2017 07:39:45 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: by mailman.ysv.freebsd.org (Postfix) id 7A601D8B839; Sun, 25 Jun 2017 07:39: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 7811CD8B838 for ; Sun, 25 Jun 2017 07:39:45 +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 EF68827A6 for ; Sun, 25 Jun 2017 07:39:44 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=UTF-8; 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 <0OS30048BEYVU200@hades.sorbs.net> for ports@freebsd.org; Sun, 25 Jun 2017 00:47:21 -0700 (PDT) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: =?UTF-8?Q?Martin_Waschb=c3=bcsch?= , ports@freebsd.org 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> <4B124329-E0E7-4A49-9A6D-A4E2251C2AAE@waschbuesch.de> From: Michelle Sullivan Message-id: Date: Sun, 25 Jun 2017 09:39:12 +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: <4B124329-E0E7-4A49-9A6D-A4E2251C2AAE@waschbuesch.de> 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, 25 Jun 2017 07:39:45 -0000 Martin Waschbüsch wrote: >> Am 23.06.2017 um 23:53 schrieb Michelle Sullivan : >> >> 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).. > FWIW, personally, I never perceived statements about FreeBSD's stability to extend beyond the scope of the (complete) OS itself. There in lies a problem.. Something happened, now the OS is not as stable, as for a 'installed the CD how long before a reboot' is it, but how often do we *have* to upgrade because of a security issue.. seems like every 5 minutes now... ports (some of them) do form part of the OS... if the ports tree stops working on older versions of the OS then you *have* to upgrade. > I always regarded ports very much as a convenience. pkg even more so. I don't consider pkg at all. Ports are partly. > >>> 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. Mostly agreed... depends on your definition of 'do the patching yourself'.. if you mean taking patches applying them yourself, then yes 100% agree, if you mean developing the patch yourself in whole or in part... no. > After all, even if all that was thoroughly done by upstream, port maintainer, etc., who’s to say my specific setup and config won’t bring issues to light their testing didn’t? 100% with you. -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-ports@freebsd.org Sun Jun 25 07:49: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 07C7ED8BAE3 for ; Sun, 25 Jun 2017 07:49:12 +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 C33412B4F for ; Sun, 25 Jun 2017 07:49:11 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dP2IA-000DoS-0I; Sun, 25 Jun 2017 09:49:10 +0200 Date: Sun, 25 Jun 2017 09:49:09 +0200 From: Kurt Jaeger To: FreeBSD Ports Cc: "sf@maxempire.com" Subject: Re: clamav-unofficial-sigs Message-ID: <20170625074909.GF29157@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: Sun, 25 Jun 2017 07:49:12 -0000 Hi! > 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? Have you tried to provide a patch ? It's structure changed a little bit, so it does not simply works in the ports framework. -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-ports@freebsd.org Sun Jun 25 09:50: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 E2EF9D8D68E for ; Sun, 25 Jun 2017 09:50:38 +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 CEA94655A7 for ; Sun, 25 Jun 2017 09:50:38 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id CDAA5D8D68C; Sun, 25 Jun 2017 09:50:38 +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 CB795D8D68B for ; Sun, 25 Jun 2017 09:50:38 +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 BDBDD655A6 for ; Sun, 25 Jun 2017 09:50:38 +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 v5P9ocYP025092 for ; Sun, 25 Jun 2017 09:50:38 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v5P9ocAm025091; Sun, 25 Jun 2017 09:50:38 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201706250950.v5P9ocAm025091@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: Sun, 25 Jun 2017 09:50:38 +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: Sun, 25 Jun 2017 09:50:39 -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/groovy | 2.4.8 | 2.4.12 ------------------------------------------------+-----------------+------------ 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 Sun Jun 25 10:23: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 26C72D8E098 for ; Sun, 25 Jun 2017 10:23:44 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-oln040092007035.outbound.protection.outlook.com [40.92.7.35]) (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 DAA0366345 for ; Sun, 25 Jun 2017 10:23:43 +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=qwO0uG6iHe8dSW+SN/OhATyJhHkZRjzraTHuTeaLq+s=; b=bQdTEvG8XiTdZH+Ps58etnEfmJpDFOjelYR7EAc8b2LC9164nCzql4+GZGEceBpptzy32mEKhd4VAJrMJWoM+Agnrx7xaPzOuk0t/wfG7Ww2s9hUsVI+EjSrtxf1zKl2mj8sIu3w1N6/kTBY/BYDSLj1DetC9j3wV04onkKrNjMl1xO+Xth5+HhO9rq29UB9gwgMNY/82LtwU+ui2f03jz9NMWSdIMTVwc0vlKVMxdLabM2Pbf153cG1YEelL/sBQJ8QYflCql00EF/i/CFQptaQywXLHQ8pLA+jC9zo+eIPpYPIw4UytKzQxV35EOYpq0V21fafLXmRX3diNrLvrg== Received: from CO1NAM03FT041.eop-NAM03.prod.protection.outlook.com (10.152.80.59) by CO1NAM03HT014.eop-NAM03.prod.protection.outlook.com (10.152.80.122) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1199.9; Sun, 25 Jun 2017 10:23:41 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com (10.152.80.59) by CO1NAM03FT041.mail.protection.outlook.com (10.152.81.163) 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; Sun, 25 Jun 2017 10:23:41 +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; Sun, 25 Jun 2017 10:23:40 +0000 From: Carmel NY To: FreeBSD Ports CC: "sf@maxempire.com" Subject: Re: clamav-unofficial-sigs Thread-Topic: clamav-unofficial-sigs Thread-Index: AQHS7SsNAVqxvVnapEWJevxyuaJmpQ== Date: Sun, 25 Jun 2017 10:23:40 +0000 Message-ID: References: <20170625074909.GF29157@home.opsec.eu> In-Reply-To: <20170625074909.GF29157@home.opsec.eu> 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:8C4B5BB2CCCD4D7E0E6E38954894861372E1A1FB87B8386137A1CBCD708F00E3; UpperCasedChecksum:9297E18E2027CE5A2042A4FF4CB897E6DC6BA31F6FD6FC22D517500CD2AD109D; SizeAsReceived:7314; Count:47 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [ICtABOpA1xUrS6u+J6j04y8muIurU5XF] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; CO1NAM03HT014; 7:1XMCHxQ1qz8kMcXWNCpFDrzWwj4Z4TNMAA9Fj9thD5v0Mlutb7kHl5xCpXSmCaUErF8C1eYyPlMONBnThs+40gTT67TKeeBH8R3IxH8MuwD86FhslVv4pKnihBmkOsRuIGncW2KxLB+O+6RVkbxnu06ARY4BrjZf4vUFsg3YuQlNbI5cPYUMV6PMz7wpfpKhGfMpNy9AFj5k8GpaxPpI7C6U2cbwlpWHP/YGAWGUrvT5FeU2L9NkAZ6yoLpfBl8aapaGnrE2aU8uE9s9fT06YvlLgD1zQA0X7+VrEnZLZ0wmdVY4Qnp/Ad66Mj9P/g7HXhmLro22qVzYh5W4DfsUgQbpMA+V0Rq01C/ABRKtSLqBpQCOl91xkjNXsbEGa7g9K4bQ/Twfc0jnnq7yhAGsNj6nRmQDqZCMkosOqUpbfPhsiGj9vhTYwTOsy0WpmQ21a22W2lbZ3DlFC2geeRLbbd/WbWH82bKFp/yrw8lK4xEg1OmrPgiFlib/dsSVkoDwNzPney5GdIkUKP+Ph6pmsgqxpZcWaq0iAtS216GciiPYfNssrHWs9xFbnW3loFKEfZi9B75zYK66z4QY5KX1Byix6gMba5xOLbEBh+Aj/qRWKjlelwU19+fW1A23o6BCR88f4tV6UBzy29psluLpkfqtISjNFpl8xrTmd76x8oJm5+BCzjbk38Wh4FViFN5e5VgD+4HnV1x6jCapInDMLavMRKKx+jjBc1blkoN9smTVYdTFw6gET1cAt4yh3AoX6wIctUg6nNCW/Gz2y/Vo9Q== x-incomingheadercount: 47 x-eopattributedmessage: 0 x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:CO1NAM03HT014; H:BN6PR2001MB1730.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: 6b5ff04a-5ce7-43f1-9c30-08d4bbb43fab 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)(300000506067)(300135500095); SRVR:CO1NAM03HT014; x-ms-traffictypediagnostic: CO1NAM03HT014: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:CO1NAM03HT014; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CO1NAM03HT014; x-forefront-prvs: 034902F5BC 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: 25 Jun 2017 10:23:40.7975 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1NAM03HT014 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, 25 Jun 2017 10:23:44 -0000 On Sun, 25 Jun 2017 09:49:09 +0200, Kurt Jaeger stated: >Hi! > >> 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 > >Have you tried to provide a patch ? It's structure changed a little >bit, so it does not simply works in the ports framework.=20 Could you elaborate on what "does not simply works in the ports framework" refers to? Thanks! --=20 Carmel From owner-freebsd-ports@freebsd.org Sun Jun 25 10:24: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 92050D8E107 for ; Sun, 25 Jun 2017 10:24:51 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-oln040092008074.outbound.protection.outlook.com [40.92.8.74]) (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 3A018663F2 for ; Sun, 25 Jun 2017 10:24:50 +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=szlJlNhm+D++zuysybpDwQ6nr4C/eiSOq5IC4861TX0=; b=AVmWJ9QG3ToKJJXo169DfjlY907d3ObtyARBxOaqB0OMWFZEqa4Ofit1TA3ZTRi/kBj6BEG2rkuopkyWTiPn7Hg6k3ioome8gkMpGfJxPwcAvU0xbs948v+4nSjkzs9FsBy9uvHjZH2Lpomks6rLKuwUaWEeL9BD99Qnm0mcHQvhMEJ0fN9OHnDbJKRX8EDceIBGvu7pFJntmt99Oxo7SkrLrnK5XrRwgzcT+zr1QywKDg80QReH5ZMk2vaykRmUU/9ccNUuraU4LdWEUvR0BE4M5LyIaAB+lqei+rGpITQ4bVkBJLzbGgBQYQYDOd4qX0E+VyMx3FEsJ+ntGhOR5A== Received: from CO1NAM03FT041.eop-NAM03.prod.protection.outlook.com (10.152.80.53) by CO1NAM03HT155.eop-NAM03.prod.protection.outlook.com (10.152.80.230) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1199.9; Sun, 25 Jun 2017 10:24:48 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com (10.152.80.59) by CO1NAM03FT041.mail.protection.outlook.com (10.152.81.163) 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; Sun, 25 Jun 2017 10:24:49 +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; Sun, 25 Jun 2017 10:24:48 +0000 From: Carmel NY To: FreeBSD Ports CC: "sf@maxempire.com" Subject: "clamav-unofficial-sigs" error message Thread-Topic: "clamav-unofficial-sigs" error message Thread-Index: AQHS7Z1FHL0OrckEqU2LLgg1eJhAog== Date: Sun, 25 Jun 2017 10:24:48 +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:C3435FFAE605B27CD35A1E070634A93C4CA8227B3E3A48BEA8044C47887E5F21; UpperCasedChecksum:FFF1BF1A8E52BFBC68858595E8A074FAA4E86F6F13BC99CFBB8A141D62EA3CE0; SizeAsReceived:7146; Count:45 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [KySJZlYqYdxEd85UYA6cXAd8n4QUp9oT] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; CO1NAM03HT155; 7:mRe7pvRcdO8xrKm8kktkH3TMZmje2R6ylmRJ/q9AUtnxf5kq4QT3TldxKCO2t2QMCqeBIIcIAYI/P3teIiQHSH7RR9fCf6XTx9V7sMbvZM9fHMw9maqLf5if/EQSt/Edf0s6MLqZZe0GGLyZjaIlFyrM0J7oLT3p/YFvE6l7hYXGy5P4TwG7ThulGjKxvxU34kRHwu9Uq2OtocQkUyrlOuTOEBt8n9pCxX+f02W0E52BXqXnMhy/zLqUsanivVbelqbFrfOUcCB6L15RlJrAsTdocE5dOy+eLEsWuv1Z+PnmXu9/uAEe3mT1HMao+8o2TCrD4rp7Eg+Vv8ZdayV3Fub5dPxEReBfgU5U4bunHOm8DfnPBsS17Jk4Wdcpb5vn2NDqDsQzyKw/sv77V9jXtotxMXuSr42pIsu0bTg4nKut/HacE5I9E+lu+pyXaV3lZO/CFDjC9XQwFIA0W/ab435U7Yb70SctNzKnAaaFYjq16tA5xnYGBAbCg+aGZtlfnUuWj9cNB9/LZSnzZ2f7FLm5recjbSqBQxjSLdwhhDPr/htsGsuAYm81iAiACtXwWPo/5xjas7Nh3r89tQGWFgPEoNijN8T9KCbNSqqp4+DHQbUtsZ50lbG28NIBTYo0OCGljQiGLw+oSqdMzY8fUm5E39qoO7kzkfgUN15JHcW/64JI1s3/aygL9LA42O0aBbWSxhRBAtqOMNZuIpNDdip4sBnnGXKpsuAZIEXKKhpWSXe+Cb9gXUaguQdKWuwR9tJiyNA6CwPstO9e+mBlRw== x-incomingheadercount: 45 x-eopattributedmessage: 0 x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:CO1NAM03HT155; H:BN6PR2001MB1730.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: acc33159-efe0-4288-939d-08d4bbb46809 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)(300000506067)(300135500095); SRVR:CO1NAM03HT155; x-ms-traffictypediagnostic: CO1NAM03HT155: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:CO1NAM03HT155; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CO1NAM03HT155; x-forefront-prvs: 034902F5BC 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: 25 Jun 2017 10:24:48.5472 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1NAM03HT155 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, 25 Jun 2017 10:24:51 -0000 I recently installed clamav-unofficial-sigs via the ports system. The port version is quite old,v5.3.2, while the current version is v5.6.2. In any case, I am receiving the following error message repeatedly:=20 Jun 24 15:45:00 ERROR: clamscan binary (clamscan_bin) not found This is the full log from the last 12 hours or so: Jun 24 15:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 16:38:57 Preparing Databases Jun 24 16:38:58 Sanesecurity Database File Updates Jun 24 16:38:58 2 hours have not yet elapsed since the last sanesecurity up= date check Jun 24 16:38:58 No update check was performed at this time Jun 24 16:38:58 Next check will be performed in approximately 0 hour(s), 53= minute(s) Jun 24 16:38:58 SecuriteInfo Database File Updates Jun 24 16:38:58 4 hours have not yet elapsed since the last SecuriteInfo up= date check Jun 24 16:38:58 No update check was performed at this time Jun 24 16:38:58 Next check will be performed in approximately 2 hour(s), 53= minute(s) Jun 24 16:38:58 linuxmalwaredetect Database File Updates Jun 24 16:38:58 6 hours have not yet elapsed since the last linux malware d= etect update check Jun 24 16:38:58 No update check was performed at this time Jun 24 16:38:58 Next check will be performed in approximately 4 hour(s), 53= minute(s) Jun 24 16:38:58 MalwarePatrol Database File Update Jun 24 16:38:58 24 hours have not yet elapsed since the last MalwarePatrol = download Jun 24 16:38:58 No database download was performed at this time Jun 24 16:38:58 Next download will be performed in approximately 22 hour(s)= , 53 minute(s) Jun 24 16:38:58 Setting permissions and ownership Jun 24 16:38:58 No updates detected, ClamAV databases were not reloaded Jun 24 16:38:58 Issue tracker : https://github.com/extremeshok/clamav-unoff= icial-sigs/issues Jun 24 16:38:59 New version : v5.6.2 @ https://github.com/extremeshok/clama= v-unofficial-sigs Jun 24 16:38:59 Powered By https://eXtremeSHOK.com =20 Jun 24 16:41:07 Preparing Databases Jun 24 16:41:08 Sanesecurity Database File Updates Jun 24 16:41:08 2 hours have not yet elapsed since the last sanesecurity up= date check Jun 24 16:41:08 No update check was performed at this time Jun 24 16:41:08 Next check will be performed in approximately 0 hour(s), 50= minute(s) Jun 24 16:41:08 SecuriteInfo Database File Updates Jun 24 16:41:08 4 hours have not yet elapsed since the last SecuriteInfo up= date check Jun 24 16:41:08 No update check was performed at this time Jun 24 16:41:08 Next check will be performed in approximately 2 hour(s), 50= minute(s) Jun 24 16:41:08 linuxmalwaredetect Database File Updates Jun 24 16:41:08 6 hours have not yet elapsed since the last linux malware d= etect update check Jun 24 16:41:08 No update check was performed at this time Jun 24 16:41:08 Next check will be performed in approximately 4 hour(s), 50= minute(s) Jun 24 16:41:08 MalwarePatrol Database File Update Jun 24 16:41:08 24 hours have not yet elapsed since the last MalwarePatrol = download Jun 24 16:41:08 No database download was performed at this time Jun 24 16:41:08 Next download will be performed in approximately 22 hour(s)= , 50 minute(s) Jun 24 16:41:08 Setting permissions and ownership Jun 24 16:41:08 No updates detected, ClamAV databases were not reloaded Jun 24 16:41:08 Issue tracker : https://github.com/extremeshok/clamav-unoff= icial-sigs/issues Jun 24 16:41:08 New version : v5.6.2 @ https://github.com/extremeshok/clama= v-unofficial-sigs Jun 24 16:41:08 Powered By https://eXtremeSHOK.com =20 Jun 24 16:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 17:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 18:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 19:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 20:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 21:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 22:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 24 23:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 25 00:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 25 01:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 25 02:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 25 03:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 25 04:45:00 ERROR: clamscan binary (clamscan_bin) not found Jun 25 05:45:00 ERROR: clamscan binary (clamscan_bin) not found I have no idea what the problem is. --=20 Carmel From owner-freebsd-ports@freebsd.org Sun Jun 25 15:17: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 919F1D939DA for ; Sun, 25 Jun 2017 15:17:48 +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 51829731C1 for ; Sun, 25 Jun 2017 15:17:47 +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=8G6ockboWJIJnO7veRHreo7Rk8AqTKrX9VlcP3OpYzw=; b=YIcSHJMwRzLwIjML2IovGdJYvF dfzq3NSuBYLooRyUeORh0WN1iyfDFsLDjXQjVM7LRsAC7V1YzC7pDHA8CbMCYMAe7OmwyZZOncKhB To9cSXUKJGHER0mDypcrwE4DNyyWj6I61pQKLSZGg9U1lrvHsTDL5ci8E+3aexd+h9Mk=; Received: by relay01.waschbuesch.it with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim) (envelope-from ) id 1dP9IG-000HG9-5v for freebsd-ports@freebsd.org; Sun, 25 Jun 2017 15:17:44 +0000 From: =?utf-8?Q?Martin_Waschb=C3=BCsch?= Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: "clamav-unofficial-sigs" error message Date: Sun, 25 Jun 2017 17:17:44 +0200 References: To: FreeBSD Ports In-Reply-To: Message-Id: 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: Sun, 25 Jun 2017 15:17:48 -0000 > Am 25.06.2017 um 12:24 schrieb Carmel NY : >=20 > I recently installed clamav-unofficial-sigs via the ports system. The > port version is quite old,v5.3.2, while the current version is v5.6.2. > In any case, I am receiving the following error message repeatedly:=20 >=20 > Jun 24 15:45:00 ERROR: clamscan binary (clamscan_bin) not found >=20 > This is the full log from the last 12 hours or so: >=20 > Jun 24 15:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 16:38:57 Preparing Databases > Jun 24 16:38:58 Sanesecurity Database File Updates > Jun 24 16:38:58 2 hours have not yet elapsed since the last = sanesecurity update check > Jun 24 16:38:58 No update check was performed at this time > Jun 24 16:38:58 Next check will be performed in approximately 0 = hour(s), 53 minute(s) > Jun 24 16:38:58 SecuriteInfo Database File Updates > Jun 24 16:38:58 4 hours have not yet elapsed since the last = SecuriteInfo update check > Jun 24 16:38:58 No update check was performed at this time > Jun 24 16:38:58 Next check will be performed in approximately 2 = hour(s), 53 minute(s) > Jun 24 16:38:58 linuxmalwaredetect Database File Updates > Jun 24 16:38:58 6 hours have not yet elapsed since the last linux = malware detect update check > Jun 24 16:38:58 No update check was performed at this time > Jun 24 16:38:58 Next check will be performed in approximately 4 = hour(s), 53 minute(s) > Jun 24 16:38:58 MalwarePatrol Database File Update > Jun 24 16:38:58 24 hours have not yet elapsed since the last = MalwarePatrol download > Jun 24 16:38:58 No database download was performed at this time > Jun 24 16:38:58 Next download will be performed in approximately 22 = hour(s), 53 minute(s) > Jun 24 16:38:58 Setting permissions and ownership > Jun 24 16:38:58 No updates detected, ClamAV databases were not = reloaded > Jun 24 16:38:58 Issue tracker : = https://github.com/extremeshok/clamav-unofficial-sigs/issues > Jun 24 16:38:59 New version : v5.6.2 @ = https://github.com/extremeshok/clamav-unofficial-sigs > Jun 24 16:38:59 Powered By https://eXtremeSHOK.com =20 > Jun 24 16:41:07 Preparing Databases > Jun 24 16:41:08 Sanesecurity Database File Updates > Jun 24 16:41:08 2 hours have not yet elapsed since the last = sanesecurity update check > Jun 24 16:41:08 No update check was performed at this time > Jun 24 16:41:08 Next check will be performed in approximately 0 = hour(s), 50 minute(s) > Jun 24 16:41:08 SecuriteInfo Database File Updates > Jun 24 16:41:08 4 hours have not yet elapsed since the last = SecuriteInfo update check > Jun 24 16:41:08 No update check was performed at this time > Jun 24 16:41:08 Next check will be performed in approximately 2 = hour(s), 50 minute(s) > Jun 24 16:41:08 linuxmalwaredetect Database File Updates > Jun 24 16:41:08 6 hours have not yet elapsed since the last linux = malware detect update check > Jun 24 16:41:08 No update check was performed at this time > Jun 24 16:41:08 Next check will be performed in approximately 4 = hour(s), 50 minute(s) > Jun 24 16:41:08 MalwarePatrol Database File Update > Jun 24 16:41:08 24 hours have not yet elapsed since the last = MalwarePatrol download > Jun 24 16:41:08 No database download was performed at this time > Jun 24 16:41:08 Next download will be performed in approximately 22 = hour(s), 50 minute(s) > Jun 24 16:41:08 Setting permissions and ownership > Jun 24 16:41:08 No updates detected, ClamAV databases were not = reloaded > Jun 24 16:41:08 Issue tracker : = https://github.com/extremeshok/clamav-unofficial-sigs/issues > Jun 24 16:41:08 New version : v5.6.2 @ = https://github.com/extremeshok/clamav-unofficial-sigs > Jun 24 16:41:08 Powered By https://eXtremeSHOK.com =20 > Jun 24 16:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 17:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 18:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 19:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 20:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 21:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 22:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 24 23:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 25 00:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 25 01:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 25 02:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 25 03:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 25 04:45:00 ERROR: clamscan binary (clamscan_bin) not found > Jun 25 05:45:00 ERROR: clamscan binary (clamscan_bin) not found =46rom what I can see, the clamav-unofficial-sigs port works. It = determines if there are updates or whether you have checked recently, so = that you do not inadvertently dos the signature servers. What is NOT working, apparently, is clamav. Did you install clamav via = ports? If it is installed, what is the clamscan_bin variable set to in = /usr/local/etc/clamav-unofficial-sigs/master.conf file? It needs to be set to the correct path, for instance = /usr/local/bin/clamscan. The correct path on your setup can be = determined using 'which clamscan' Best, Martin= From owner-freebsd-ports@freebsd.org Sun Jun 25 15:32: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 F27E5D9405D for ; Sun, 25 Jun 2017 15:32:15 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from anny.lostinspace.de (anny.lostinspace.de [IPv6:2001:608:a02::33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B8E0173C56 for ; Sun, 25 Jun 2017 15:32:15 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from server.idefix.lan (aftr-88-217-181-92.dynamic.mnet-online.de [88.217.181.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: idefix@fechner.net) by anny.lostinspace.de (Postfix) with ESMTPSA id 98751BF8FDC for ; Sun, 25 Jun 2017 17:32:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=fechner.net; s=default; t=1498404732; bh=7lt0aFl0NmwTpEH5pWFBOiABCDr466K7bzhWOLi08Mg=; h=To:From:Subject:Date; b=FX3V8409G32KK0WUHo9q0JDxNurCb32Xcvr3nWIz8rMsmtyw/nVRwLVU61lptt6BG Si3UpFgLI2aYa++BMwDV+kLvRbKWCVpgl+gfokPVo9AYoAbK8AmpSbc6OM5J91At5A mIK1YCBhUyUiR+Jt3YfjtAaaDy38lTyw+fmmlyOY= Received: from [192.168.0.151] (aftr-88-217-181-92.dynamic.mnet-online.de [88.217.181.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by server.idefix.lan (Postfix) with ESMTPSA id 2B82DCB6069 for ; Sun, 25 Jun 2017 17:32:12 +0200 (CEST) To: FreeBSD Ports From: Matthias Fechner Subject: Which license should be used for as-id Message-ID: <477d11d2-01f0-2bb3-95fc-73aaf1671982@fechner.net> Date: Sun, 25 Jun 2017 17:32:11 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 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: Sun, 25 Jun 2017 15:32:16 -0000 Dear all, which LICENSE tag in ports should be used if the package as the license "AS IS"? Thanks Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook From owner-freebsd-ports@freebsd.org Sun Jun 25 15:32:23 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 5D9FAD94096 for ; Sun, 25 Jun 2017 15:32:23 +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 DEFF073CA8 for ; Sun, 25 Jun 2017 15:32:22 +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 v5PFWDSV009884 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sun, 25 Jun 2017 15:32:13 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> <8948545b-5269-8a0e-3f92-9dfd02f227c1@gjunka.com> From: Grzegorz Junka Message-ID: Date: Sun, 25 Jun 2017 15:32:13 +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: Sun, 25 Jun 2017 15:32:23 -0000 >> 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 > It looks like you might have misunderstood something I said about pkgsrc. > > I use pkg with FreeBSD ports on FreeBSD, but my interest in pkgsrc and pkgsrc-synth is for NetBSD. > > Working with pkgsrc on NetBSD convinces me that they need to import portupgrade and/or portmaster from FreeBSD, maybe synth will be better? > > Pkgsrc is awkward dealing with packages whose names have changes or branched. > > Ports LTS branches, is that Long Term Service? I don't really understand that question. > > Tom > First question: Sorry, I used a mental shortcut without explaining. I imagined that because both pkg and pkgsrc support FreeBSD, the effort of maintaining both could be combined, and pkgsrc seemed to be superior since it also supports other OSes. I also assumed that that has been considered before. So, because pkg hasn't been replaced by pkgsrc, there must be some advantages of using pkg on FreeBSD as opposed to using pkgsrc. My question was about these. LTS indeed is Long Term Support. In short, there is a branch (or branches) not tied to any specific OS release but can be dependent on a specific OS release (e.g. 11.0 as minimum) in which application versions don't change as often as in the current branch. It would mostly incorporate security fixes. Now, a question if the versions shouldn't change for the duration of the LTS branch or if small version changes are allowed is a secondary issue. What I am trying to determine if having that branch/es would fulfil the requirement of many people on this list of having a more stable ports tree (where branches by OS versions was one of the proposed solutions). Grzegorz From owner-freebsd-ports@freebsd.org Sun Jun 25 16:16: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 C75C2D94E78 for ; Sun, 25 Jun 2017 16:16:31 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-oln040092005017.outbound.protection.outlook.com [40.92.5.17]) (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 81AB875102 for ; Sun, 25 Jun 2017 16:16:30 +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=6NPALxnliLIJ45huf0+AWr2LrJ9ilzF7GbN6hWXS6qc=; b=Vsz0mXItTb4xCxnH8W9N6QvJ3iPoIfGqPqQtdUYXez9xUwG+P3HVsgR00fBnKQ6GOAVaaJ7DPR1UQRdDA0fj4p9kVZYNZgb0QRGMtyMwkOCq9/drYzoqR3IElsqbe/qxZAiKpfaEQT6a/VGAcbYKmcja94wqmavzRAxcs+PpA6V+iHcODdxLpI1+c0wMoTLqbK1sMTevpLaCUFcQbzaLxQ6MQaPXDr3ma6nKR5td/hwQBIB+cHt/DVYW5Faz9bj0SVepa8b6jwR2MMWpFGsGMqTBrQYq76/StXHYu8Z3RO/xzi1TbwOPA8RZTrnHt9TWfSlfHEVIq6qq9BJ+su7pvg== Received: from SN1NAM02FT002.eop-nam02.prod.protection.outlook.com (10.152.72.55) by SN1NAM02HT063.eop-nam02.prod.protection.outlook.com (10.152.72.203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1178.14; Sun, 25 Jun 2017 16:16:29 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com (10.152.72.56) by SN1NAM02FT002.mail.protection.outlook.com (10.152.72.94) 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; Sun, 25 Jun 2017 16:16:29 +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; Sun, 25 Jun 2017 16:16:29 +0000 From: Carmel NY To: FreeBSD Ports CC: "sf@maxempire.com" Subject: Re: "clamav-unofficial-sigs" error message Thread-Topic: "clamav-unofficial-sigs" error message Thread-Index: AQHS7Z1FHL0OrckEqU2LLgg1eJhAog== Date: Sun, 25 Jun 2017 16:16:29 +0000 Message-ID: References: In-Reply-To: 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:6ED0908275D54B90BC382874EC7A9947DE1B83F4C8DE09FDEECB780AB3B43B16; UpperCasedChecksum:A18E1996F3D834B5505F85CBF9843F303985081174F57D84529EA810BA7CE697; SizeAsReceived:7375; Count:47 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [sgw1WZxYr7V6hCRCGUsI+xaNkpcNE4iZ] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; SN1NAM02HT063; 7:1YrNBJKMYF5snSi126FpKBImmESA9UQolrwAnyBeWHBt/NiByN+VuzYJmqw0B7lm88UPMMaP9HzTab8epQbYpy0TFNDvArFmw7UDV3vfIHnb5G/pjkvHwSsVQr7fIUrnQoyk+gAUEZgsaTSIplanFbDBzRt0i5nFzNpv9uB2R96itPPkwh+b5pANd/CQknELIXNYYRfNfXKFrpY+tlvjhO5HAx6BXVEiN+LfYB2Uf/XwBVZ+EitJW/NOJtf57ybzYIXOQCf+QgrAMxVMWauHpCwJwFXnMz8SL4omi8d6buR3+aTnCcOLuI8ZGEl/ZgPisJfVLuBEpAEo+TpN8FfhmLSiYqEyFyidAnRlPHyf5phIHMSV46DhBQ+JZHS5jbonlHHEtJuQ62p0b/hsv5QtM8KTG3afWTOHIqNbfEovupr71kvJnzTp7uG8FUu1ned0/B9axGrMEIMqfXdczx2zViQdb7ekIT918odvzCkCrMSXyY2MPwVYaIPnU/2BggGn1PgP0cCed3HLJxUcDQkYUCq04tA9o+lRHSSAbzvKMwEZOwInIX//VUUOA0xLme+Js75vkOQboZI80vkeZCXQbkwTtXFy0OBHqReMPS/Z6ixn+1bfCFePlKej42yRb8JthEFTK+W8LsJd5QFDQEcGwPBtlc+g9gUWGH5LoxKEWwz7R4bJovfZVTKEYNnx6VSS1N4SRSIOIEqYOa2uDpVAAymERhhqCOkutSKn5pN4nzgtfpodYO0XvnZyLnTeTDNST7EyYMeDnuPCCVUsg8CsPQ== x-incomingheadercount: 47 x-eopattributedmessage: 0 x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:SN1NAM02HT063; H:BN6PR2001MB1730.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: f969f23c-37c7-4b04-1d2d-08d4bbe58932 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:SN1NAM02HT063; x-ms-traffictypediagnostic: SN1NAM02HT063: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:SN1NAM02HT063; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:SN1NAM02HT063; x-forefront-prvs: 034902F5BC spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-ID: <3E1B929B5FF4C14380DC18BB07E2453E@namprd20.prod.outlook.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jun 2017 16:16:29.8237 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM02HT063 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, 25 Jun 2017 16:16:31 -0000 T24gU3VuLCAyNSBKdW4gMjAxNyAxNzoxNzo0NCArMDIwMCwgTWFydGluIFdhc2NoYsO8c2NoIHN0 YXRlZDoNCg0KPkZyb20gd2hhdCBJIGNhbiBzZWUsIHRoZSBjbGFtYXYtdW5vZmZpY2lhbC1zaWdz IHBvcnQgd29ya3MuIEl0DQo+ZGV0ZXJtaW5lcyBpZiB0aGVyZSBhcmUgdXBkYXRlcyBvciB3aGV0 aGVyIHlvdSBoYXZlIGNoZWNrZWQgcmVjZW50bHksDQo+c28gdGhhdCB5b3UgZG8gbm90IGluYWR2 ZXJ0ZW50bHkgZG9zIHRoZSBzaWduYXR1cmUgc2VydmVycy4gV2hhdCBpcw0KPk5PVCB3b3JraW5n LCBhcHBhcmVudGx5LCBpcyBjbGFtYXYuIERpZCB5b3UgaW5zdGFsbCBjbGFtYXYgdmlhIHBvcnRz Pw0KPklmIGl0IGlzIGluc3RhbGxlZCwgd2hhdCBpcyB0aGUgY2xhbXNjYW5fYmluIHZhcmlhYmxl IHNldCB0bw0KPmluIC91c3IvbG9jYWwvZXRjL2NsYW1hdi11bm9mZmljaWFsLXNpZ3MvbWFzdGVy LmNvbmYgZmlsZT8gSXQgbmVlZHMgdG8NCj5iZSBzZXQgdG8gdGhlIGNvcnJlY3QgcGF0aCwgZm9y IGluc3RhbmNlIC91c3IvbG9jYWwvYmluL2NsYW1zY2FuLiBUaGUNCj5jb3JyZWN0IHBhdGggb24g eW91ciBzZXR1cCBjYW4gYmUgZGV0ZXJtaW5lZCB1c2luZyAnd2hpY2ggY2xhbXNjYW4nDQoNCkZy b20gdGhlICJtYXN0ZXIuY29uZiIgZmlsZToNCg0KIyBDdXN0b20gQ29tbWFuZCBQYXRocywgdGhl c2UgYXJlIGRldGVjdGVkIHdpdGggdGhlIHdoaWNoIGNvbW1hbmQgd2hlbg0Kbm90IHNldC4NCg0K Q2xhbXNjYW4gd2FzIGNvbW1lbnRlZCBvdXQ7IGhvd2V2ZXIsIHRoZSBkZWZhdWx0IHNldHRpbmcg d2FzDQp0byAvdXNyL2Jpbi9jbGFtc2Nhbg0KDQpGcm9tIHdoYXQgSSBjYW4gZmlndXJlIG91dCwg dGhlICJ3aGljaCIgY29tbWFuZCB3b3JrZWQgZmluZSBvdXRzaWRlIG9mDQphIENST04gam9iLCBi dXQgd2FzIGZhaWxpbmcgd2hlbiBjbGFtYXYtdW5vZmZpY2lhbC1zaWdzLnNoIHdhcyBydW4gdmlh DQpDUk9OLiBJIHVuY29tbWVudGVkIHRoZSAiY2xhbXNjYW4iIHNldHRpbmcgYW5kIHNldCBpdCB0 byBwb2ludCB0byB0aGUNCmNvcnJlY3QgbG9jYXRpb24uIE5vdyBpdCB3b3JrcyBjb3JyZWN0bHku DQoNClRoaXMgaXMgcHJvYmFibHkgYSBidWcsIGJ1dCBJIGFtIG5vdCBnb2luZyB0byB3YXN0ZSBt eSB0aW1lIHJlcG9ydGluZw0KaXQuIFRoZSBwb3J0cyB2ZXJzaW9uIG9mIHRoaXMgcHJvZ3JhbSBp cyB2ZXJ5IG9sZC4gVGhlcmUgaGF2ZSBiZWVuIGZpdmUNCm5ld2VyIHZlcnNpb25zIHNpbmNlIGl0 cyByZWxlYXNlLiBObyBkb3VidCB0aGlzIHByb2JsZW0gaGFzIGJlZW4NCmNvcnJlY3RlZC4NCg0K LS0gDQpDYXJtZWwNCg== From owner-freebsd-ports@freebsd.org Sun Jun 25 17:10: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 83F60D95C17 for ; Sun, 25 Jun 2017 17:10:08 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: from mail-wr0-f176.google.com (mail-wr0-f176.google.com [209.85.128.176]) (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 21BA9766A5 for ; Sun, 25 Jun 2017 17:10:07 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-wr0-f176.google.com with SMTP id 77so124362693wrb.1 for ; Sun, 25 Jun 2017 10:10:07 -0700 (PDT) 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; bh=MScPZ7H9Nn9ZMF41uFLI5s9v9sW5kBKR+OzzHeWg7ac=; b=VMhG/Et0rWSFJyARTZTM5GGb6xyBAUXAqaQ9AP+BqzBMVTgSgxEX0FCRedhQiXnOnQ gkm5eSNmC/oPYfUiurdkoFw9Y2jhv6qvo2V2OxLNQ7mGk3sz07wcM9PGspxEIP2HWrMF HG4XUg5ufoA0d6Vgyrk2Qw+dpkTRjc53gse5bisStSB7g0YD8wlI3YP/yy/cN2EZ/7IL 1swaxtErJ62sHPUFZ2HA4NyuRrpa06gnRoXYNY2mXNg0wL8FPpvdPwSrXpKP2aMfadeW JE8n0ZCLZGfZSAIO6ChiIK2xfp9vagmwiwqjXKK8VSipxvb9qrm+LqmxCaYz0JHp2sSL 79cA== X-Gm-Message-State: AKS2vOyHUZgc6bRDyhA3VA1SGCmbeiRvRtFmiBTHkukzn1E0LirOLUuU MZgDu0pp8KKECVNQC/4= X-Received: by 10.223.129.134 with SMTP id 6mr11320909wra.77.1498410599631; Sun, 25 Jun 2017 10:09:59 -0700 (PDT) Received: from ?IPv6:2601:646:c402:f051:a236:9fff:fe30:1726? ([2601:646:c402:f051:a236:9fff:fe30:1726]) by smtp.gmail.com with ESMTPSA id 143sm75123wmo.11.2017.06.25.10.09.58 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 25 Jun 2017 10:09:58 -0700 (PDT) To: freebsd-ports@FreeBSD.org From: Richard Gallamore Subject: USE_GCC usage Message-ID: Date: Sun, 25 Jun 2017 10:09:53 -0700 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-sha512; protocol="application/pgp-signature"; boundary="t7kRoWDsIdX2ujLdQpCtGG7VejUEjU5gW" 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, 25 Jun 2017 17:10:08 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --t7kRoWDsIdX2ujLdQpCtGG7VejUEjU5gW Content-Type: multipart/mixed; boundary="7pf9BVlbGCbEFhf21KmLF7UbwRn3qdtGs"; protected-headers="v1" From: Richard Gallamore To: freebsd-ports@FreeBSD.org Message-ID: Subject: USE_GCC usage --7pf9BVlbGCbEFhf21KmLF7UbwRn3qdtGs Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US When using USE_GCC=3D 5+, errors occur because this USE only sets build and run time dependency, and not lib dependency. Error: /usr/local/bin/ann_in is linked to /usr/local/lib/gcc5/libgfortran= =2Eso.3 from lang/gcc but it is not declared as a dependency Error: /usr/local/bin/ann_in is linked to /usr/local/lib/gcc5/libquadmath= =2Eso.0 from lang/gcc but it is not declared as a dependency Error: /usr/local/bin/c81merge is linked to /usr/local/lib/gcc5/libstdc++= =2Eso.6 from lang/gcc but it is not declared as a dependency Error: /usr/local/bin/c81merge is linked to /usr/local/lib/gcc5/libgcc_s.= so.1 from lang/gcc but it is not declared as a dependency Should this be considered a false positive? or should USE_GCC also add a LIB_DEPEND to ports? Thanks, Richard Gallamore=20 --7pf9BVlbGCbEFhf21KmLF7UbwRn3qdtGs-- --t7kRoWDsIdX2ujLdQpCtGG7VejUEjU5gW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEy0bsZFuhj198rL2mO+r3F2iiCM8FAllP7mNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldENC NDZFQzY0NUJBMThGNUY3Q0FDQkRBNjNCRUFGNzE3NjhBMjA4Q0YACgkQO+r3F2ii CM9kPgf/XD2N3Da3R3miGFeUmlQfSRrXx0KnqH52QHz/9UQM2DsydWRhoV1BDRby abYMmcQm47c9WxdMHcSNaioGKyagvMtV1m7C46AdSrBtuvQBfp20GHJ1BpBFytvf MrxXBSSrvwR0vMPK0YXO+FU2Hg0Eobupd1F9Vb8xeLgqr4LoRzpwgLYBavhe0wbb /S2Gx0+/FWzyN1pGXjZNZjgCFNZB6NE3n237z9CM55UU9eu51H752dzq9Nora4pD ulOS3cc4izUzPmyn+zazIWyCcefZrgXH4B5KptBDCq3TfG1e7+EsKIn28SVOrLRF AcFEN1f6DWwCWvYNEuYm+oiTOLTRAw== =Dh3Z -----END PGP SIGNATURE----- --t7kRoWDsIdX2ujLdQpCtGG7VejUEjU5gW-- From owner-freebsd-ports@freebsd.org Sun Jun 25 19:39: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 DDE01D98B45 for ; Sun, 25 Jun 2017 19:39:00 +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 2EB5F7B7A4 for ; Sun, 25 Jun 2017 19:38:58 +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 v5PJceN8062460 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 26 Jun 2017 05:38:46 +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 v5PJcXnn073153 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 26 Jun 2017 05:38:33 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id v5PJcX96073152; Mon, 26 Jun 2017 05:38:33 +1000 (AEST) (envelope-from peter) Date: Mon, 26 Jun 2017 05:38:33 +1000 From: Peter Jeremy To: Walter Schwarzenfeld Cc: freebsd-ports@freebsd.org Subject: Re: security/libressl not API-compatible with OpenSSL, breaks www/apache24 Message-ID: <20170625193833.GB69225@server.rulingia.com> References: <20170624092744.GA69225@server.rulingia.com> <93d1f104-cd1a-3654-754e-c5616bce8fb2@utanet.at> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="/NkBOFFp2J2Af1nK" Content-Disposition: inline In-Reply-To: <93d1f104-cd1a-3654-754e-c5616bce8fb2@utanet.at> 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: Sun, 25 Jun 2017 19:39:01 -0000 --/NkBOFFp2J2Af1nK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2017-Jun-24 17:07:33 +0200, Walter Schwarzenfeld wrote: >There is a working patch: >https://bz.apache.org/bugzilla/show_bug.cgi?id=3D61184 Thanks for that. It works nicely but is significantly more involved than I thought. --=20 Peter Jeremy --/NkBOFFp2J2Af1nK Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJZUBE4XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs0oUIP/0NMHBeAy6jz9oSCsRaC/y1N nbhsdXSCZGANhTTImYSHPdDXxYpDghtlfxnz0Gd8zIYyeYCaBn5yg/6oEo79ybM4 ACysefN7WfKiM3WMBFXMxie9cQdDkFUnPT2431OSelyvRRVCW7VsyEmiPap/DF01 +yk2EDzKdwztdxwcTEEvwdBVMZxMQ0ZefYoUqt1tkL/tCe+oaMttoxy8gwmMejRb h/sDjIsdGyoLKDecFRiSu0VwTjsj6R7OgqVTjVjbq3q0okSrk4zFLRFocSMTi5NE VqBbzrkHhLjqeRfS2ZaNRx9SxJWpmw5GNFfAGtYdYGSiEk7PGdVIb5dnWIk+1j3I HjeDzs5VLrri/bAIa0G8yo/hy73w576UEQrPhikga5GQ95ERvy4fX9E/tlpYPAEA sC1MI7lKTuTCgkhe61nLZ1cc0p3fIEODti1BVP1tvu3xjCTESkX7XFJnu23m3k0E 35HxO4i5cPoyLvVYge3FsOxU0a5aLml8sjtExDoHF4VR0x1aX4CTdjpkti3oYhfp Kv5336fKgwg51MkrjH8TK09CrQP1b2vYIIPzcLxv0ZAul8AUBhbOwh5T0RzzQtZ2 tMTRANc55JA0Bf5UIjb5C2X21Zqb2L3sLBXe0mcIesmKZOOXxCmbMSaDd1/VkEzD IqqdJyRl4yMsuqbW88gm =KQZW -----END PGP SIGNATURE----- --/NkBOFFp2J2Af1nK-- From owner-freebsd-ports@freebsd.org Sun Jun 25 22:32:41 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 30ED6D9BAD9 for ; Sun, 25 Jun 2017 22:32:41 +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 01CCE80310 for ; Sun, 25 Jun 2017 22:32:40 +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 v5PMWXvT054695 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 25 Jun 2017 15:32:34 -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> <1498206372.2506.1.camel@gmail.com> <666bfe8c-f27d-2c11-2a4a-07da43bb7931@FreeBSD.org> From: Dave Hayes Message-ID: <1f37fffa-4b86-0480-d0ec-1357fc43e930@jetcafe.org> Date: Sun, 25 Jun 2017 15:32:33 -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: <666bfe8c-f27d-2c11-2a4a-07da43bb7931@FreeBSD.org> 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: Sun, 25 Jun 2017 22:32:41 -0000 On 06/23/2017 01:53, Guido Falsi wrote: > If your model works fine I'm quite sure the FreeBSD community and > project will be quite happy to embrace it. ... > 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. The fallacy in your suggestion to "do it yourself" is that the others who are actually working and committing on ports are far more efficient at implementing these ideas than the rest of us. I've never seen someone who says "do it yourself if you want it different" actually take into account that the expertise and experience of the people currently doing it result in a far lower manpower cost, sometimes by orders of magnitude. Thus, in some cases, people demand or insist because they want something they either cannot accomplish themselves, or cannot accomplish in the limited time they have. As far as I have observed, you can't even -pay- the ports experts to do something you might want. If you do not have this time or expertise, the only recourses left are: demand, insist, request, plead, or attempt to logically convince. As I see it, the emotions you see people expressing don't come as much from "not having their own way" as it does from being forced to adopt someone else's way. Looking at just that idea, the situation is not really that much different from using Microsoft and Apple; you take what they give you or go use something else. I think there's a general perception that open source is not supposed to be like that so much, but I think we all know differently here. To be absolutely clear, I'm not demanding or insisting on anything here out of ports maintainers or FreeBSD. I can and do support myself, when I am able. I'm merely pointing out ideas which may not be immediately visible to the people in this thread. -- Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< In a dream, Nasrudin saw himself being counted out coins. When there were nine silver pieces in his hand, the invisible donor stopped giving them. Nasrudin shouted, "I must have ten!" so loudly that he woke himself up. Finding all the money gone he closed his eyes again and said. "All right, then, give them back. I'll take the nine." From owner-freebsd-ports@freebsd.org Mon Jun 26 02:09: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 42EC9D9ECC1 for ; Mon, 26 Jun 2017 02:09:26 +0000 (UTC) (envelope-from amutu@amutu.com) Received: from mail-ot0-x22e.google.com (mail-ot0-x22e.google.com [IPv6:2607:f8b0:4003:c0f::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 08EDE8D6 for ; Mon, 26 Jun 2017 02:09:25 +0000 (UTC) (envelope-from amutu@amutu.com) Received: by mail-ot0-x22e.google.com with SMTP id y47so59627259oty.0 for ; Sun, 25 Jun 2017 19:09:25 -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=2piOuW3nceJeygNGIsrjlbJDfK2b82S57ZeyPyY8a3M=; b=CWwZ1fF+8iFyLf86vGdnAXu3UuW+T/2EqJDav45PdHvW2L+5WT2TOAFCRPSMO2KvcS R20SJ3J889wuFMBOG01MhAVrhcnmgayGHCFZkFdHgN+Z5/VKJU7FnTR8osEBodQAJLdR itXrJNGbimveHxzjQKttcnJpSZePgWozkIrYYpikJ7zJTm+kO9GSvjtBwTMLJTlNCIbk 9BGRvRlv0zSPC4WY8VYS5UcqYFuE8tcU33N+Z2BS0oTVKw+JU6csVTPwXxqMfMWQ6hLC cA0bwuok6X7pLPAA2V8rgfCJJo6Ze3dQjDRW6H5t8MoC9C+M0I87i3BYvnyXYxpVrIuM Dk9g== 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=2piOuW3nceJeygNGIsrjlbJDfK2b82S57ZeyPyY8a3M=; b=qF92CoWhgp3H4XxWE5vSKqZXg2IDq86ZIuOjiZX1tetadWy88kDc1ymCOMyhHS916r gOmmfqrVIh+Ard3ljEWZOsaTgT5AmGrgjqrbRqIUJDMIG0bVntRAhTKqGR/N1Gd9UYAx O2/2hccVLm2u179GeEgk8oYCPldAX+faILvhdql4JnN4F2yPloH6IG3+HZ5di+RJ25Np LtWJIrabwmzN+p2hdTgGcHhHmh43r0QrtsgCJYrjLnJ8oDptDTt5Ybrc/IweB+SxlNsy ebAdN9ZPlol1883turoK94smube8fnVdx5bgC7mpx2LRgvCrjmKQPVozGFk0mPb4RJx8 W08A== X-Gm-Message-State: AKS2vOwM6ddrGYYLO+IqIHox828wZyvH/NsX6I35KFiQBmUAeK6Q+bsT YWims/4c3TJITSJt X-Received: by 10.157.12.171 with SMTP id b40mr9276060otb.98.1498442965216; Sun, 25 Jun 2017 19:09:25 -0700 (PDT) Received: from mail-ot0-f170.google.com (mail-ot0-f170.google.com. [74.125.82.170]) by smtp.gmail.com with ESMTPSA id d83sm5801276oic.19.2017.06.25.19.09.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 25 Jun 2017 19:09:24 -0700 (PDT) Received: by mail-ot0-f170.google.com with SMTP id y47so59627120oty.0; Sun, 25 Jun 2017 19:09:24 -0700 (PDT) X-Received: by 10.157.43.116 with SMTP id f49mr9658340otd.140.1498442964413; Sun, 25 Jun 2017 19:09:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.133.136 with HTTP; Sun, 25 Jun 2017 19:09:04 -0700 (PDT) In-Reply-To: References: From: Jov Date: Mon, 26 Jun 2017 10:09:04 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: USE_GCC usage To: Richard Gallamore Cc: FreeBSD Ports 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, 26 Jun 2017 02:09:26 -0000 Thanks, Richard.This is a problem I met when update port science/mbdyn to 1.7.2. But the old version 1.7.1 also has this problem. Note this only happen when DEVELOPER=yes set in /etc/make.conf and in the Q/A tests: ====> Running Q/A tests (stage-qa) Error: /usr/local/bin/ann_in is linked to /usr/local/lib/gcc5/libgfortran.so.3 from lang/gcc but it is not declared as a dependency Error: /usr/local/bin/ann_in is linked to /usr/local/lib/gcc5/libquadmath.so.0 from lang/gcc but it is not declared as a dependency Error: /usr/local/bin/c81merge is linked to /usr/local/lib/gcc5/libstdc++.so.6 from lang/gcc but it is not declared as a dependency Error: /usr/local/bin/c81merge is linked to /usr/local/lib/gcc5/libgcc_s.so.1 from lang/gcc but it is not declared as a dependency 2017-06-26 1:09 GMT+08:00 Richard Gallamore : > When using USE_GCC= 5+, errors occur because this USE only sets > build and run time dependency, and not lib dependency. > > Error: /usr/local/bin/ann_in is linked to /usr/local/lib/gcc5/libgfortran.so.3 > from lang/gcc but it is not declared as a dependency > Error: /usr/local/bin/ann_in is linked to /usr/local/lib/gcc5/libquadmath.so.0 > from lang/gcc but it is not declared as a dependency > Error: /usr/local/bin/c81merge is linked to /usr/local/lib/gcc5/libstdc++.so.6 > from lang/gcc but it is not declared as a dependency > Error: /usr/local/bin/c81merge is linked to /usr/local/lib/gcc5/libgcc_s.so.1 > from lang/gcc but it is not declared as a dependency > > Should this be considered a false positive? or should USE_GCC > also add a LIB_DEPEND to ports? > > > Thanks, > Richard Gallamore > > > From owner-freebsd-ports@freebsd.org Mon Jun 26 07:27:47 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 3B785DA3609 for ; Mon, 26 Jun 2017 07:27:47 +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 C4C796A7DD for ; Mon, 26 Jun 2017 07:27:46 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3wx0y15qwFzb56; Mon, 26 Jun 2017 09:27:37 +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 6kbOYHAnGaYC; Mon, 26 Jun 2017 09:27:35 +0200 (CEST) Received: from marvin.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Mon, 26 Jun 2017 09:27:35 +0200 (CEST) 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> <1498206372.2506.1.camel@gmail.com> <666bfe8c-f27d-2c11-2a4a-07da43bb7931@FreeBSD.org> <1f37fffa-4b86-0480-d0ec-1357fc43e930@jetcafe.org> From: Guido Falsi Message-ID: <417811ff-d808-8574-47c4-efab470af91b@FreeBSD.org> Date: Mon, 26 Jun 2017 09:27:34 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <1f37fffa-4b86-0480-d0ec-1357fc43e930@jetcafe.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: Mon, 26 Jun 2017 07:27:47 -0000 On 06/26/17 00:32, Dave Hayes wrote: > On 06/23/2017 01:53, Guido Falsi wrote: >> If your model works fine I'm quite sure the FreeBSD community and >> project will be quite happy to embrace it. > ... >> 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. > > The fallacy in your suggestion to "do it yourself" is that the others > who are actually working and committing on ports are far more efficient > at implementing these ideas than the rest of us. > > I've never seen someone who says "do it yourself if you want it > different" actually take into account that the expertise and experience > of the people currently doing it result in a far lower manpower cost, > sometimes by orders of magnitude. I only partly agree with what you say, but anyway insisting on the mailing lists with individual committers, and defending a general idea ignoring all the details, dismissing the actual problems in the detailed implementation that are raised by committers is not going to get much done. It has also been suggested here to write a full blown, planned and though out proposal to be submitted via the new "FreeBSD Community Process" [1], which could be much more effective. Such a proposal should specify required resources with a decent degree os precision, procedures, tools and instruments needed and also has to address what is to be done in all the corner cases that can be foreseen too(providing examples of such corner cases is besides the point here, but there are many). I think is someone really wants something different from the ports tree than what is provided now the effort to exactly describe it is the only viable way to get something done. > > To be absolutely clear, I'm not demanding or insisting on anything here > out of ports maintainers or FreeBSD. I can and do support myself, when I > am able. I'm merely pointing out ideas which may not be immediately > visible to the people in this thread. The what you need to do, being a full blown implementation too much for a single person, is write out a complete proposal and submit it for review. A general idea for a "stable ports branch" or "release ports branches" is too much generic and can attract only criticism, because most committers have already had such generic ideas and dismissed it due to the many problems that would come from it (quarterlies show some of those). But maybe you can build a better proposal which avoids or solves those problems. I'd say the difficult part in such a problem is not in the idea but in the boring details of it's implementation and long term maintenance. [1] https://github.com/freebsd/fcp/blob/master/fcp-0000.md -- Guido Falsi From owner-freebsd-ports@freebsd.org Mon Jun 26 07:30: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 8D714DA36A3 for ; Mon, 26 Jun 2017 07:30:55 +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 501F46A945 for ; Mon, 26 Jun 2017 07:30:54 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3wx11n0rFyzb56; Mon, 26 Jun 2017 09:30:53 +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 Z_oTv5V1jEVZ; Mon, 26 Jun 2017 09:30:51 +0200 (CEST) Received: from marvin.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Mon, 26 Jun 2017 09:30:51 +0200 (CEST) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version From: Guido Falsi To: Dave Hayes , 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> <1f37fffa-4b86-0480-d0ec-1357fc43e930@jetcafe.org> <417811ff-d808-8574-47c4-efab470af91b@FreeBSD.org> Message-ID: Date: Mon, 26 Jun 2017 09:30:51 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <417811ff-d808-8574-47c4-efab470af91b@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: Mon, 26 Jun 2017 07:30:55 -0000 On 06/26/17 09:27, Guido Falsi wrote: > I'd say the difficult part in such a problem is not in the idea but in > the boring details of it's implementation and long term maintenance. > I forgot one important piece of information: Any project that requires full dedication from all committers to a "stable/release ports branch" is bound to be criticized to death and anyway bound to failure (IMHO). Any such proposal should identify some volunteer party with well defined roles. Remember ports work is all volunteer, you can't impose any work on any party! -- Guido Falsi From owner-freebsd-ports@freebsd.org Mon Jun 26 07:43: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 0D0D3DA3B68 for ; Mon, 26 Jun 2017 07:43:46 +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 C359C6E200 for ; Mon, 26 Jun 2017 07:43:45 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dPOgP-000G41-BF; Mon, 26 Jun 2017 09:43:41 +0200 Date: Mon, 26 Jun 2017 09:43:41 +0200 From: Kurt Jaeger To: Dave Hayes Cc: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170626074341.GG29157@home.opsec.eu> 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> <1f37fffa-4b86-0480-d0ec-1357fc43e930@jetcafe.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1f37fffa-4b86-0480-d0ec-1357fc43e930@jetcafe.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: Mon, 26 Jun 2017 07:43:46 -0000 Hi! > Thus, in some cases, people demand or insist because they want something > they either cannot accomplish themselves, or cannot accomplish in the > limited time they have. As far as I have observed, you can't even -pay- > the ports experts to do something you might want. You can discuss the general idea with the foundation. Then give them the money they estimate for the feature. They'll easily find folks doing it. It just won't be cheap. I guesstimate that you need at least 2 person-years to implement a working scheme that works within the current framework. -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-ports@freebsd.org Mon Jun 26 07:46:47 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 F1243DA3C91 for ; Mon, 26 Jun 2017 07:46:47 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.shmhost.net (unknown [IPv6:2a01:4f8:a0:51d6::108: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 B80866E2F0 for ; Mon, 26 Jun 2017 07:46:47 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.homeoffice.local (ipservice-092-208-050-076.092.208.pools.vodafone-ip.de [92.208.50.76]) by host64.shmhost.net (Postfix) with ESMTPSA id 792A785D22; Mon, 26 Jun 2017 09:46:45 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version From: Franco Fichtner In-Reply-To: <20170626074341.GG29157@home.opsec.eu> Date: Mon, 26 Jun 2017 09:46:44 +0200 Cc: Dave Hayes , freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <27AACE2B-0B4A-4B7C-8600-B37AE18CC02E@lastsummer.de> 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> <1f37fffa-4b86-0480-d0ec-1357fc43e930@jetcafe.org> <20170626074341.GG29157@home.opsec.eu> To: Kurt Jaeger X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at host64.shmhost.net X-Virus-Status: Clean 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, 26 Jun 2017 07:46:48 -0000 > On 26. Jun 2017, at 9:43 AM, Kurt Jaeger wrote: >=20 >> Thus, in some cases, people demand or insist because they want = something=20 >> they either cannot accomplish themselves, or cannot accomplish in the=20= >> limited time they have. As far as I have observed, you can't even = -pay-=20 >> the ports experts to do something you might want. >=20 > You can discuss the general idea with the foundation. Then give them > the money they estimate for the feature. They'll easily find folks = doing it. > It just won't be cheap. How about this: add more volunteers to begin with, more free resources = for any useful work. With the right project leadership it'll do great. :) Cheers, Franco= From owner-freebsd-ports@freebsd.org Mon Jun 26 09:43: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 B9F68DA5E27 for ; Mon, 26 Jun 2017 09:43:38 +0000 (UTC) (envelope-from sf@maxempire.com) Received: from oblak.markonjezic.com (oblak.markonjezic.com [78.31.66.29]) (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 82357718BF for ; Mon, 26 Jun 2017 09:43:38 +0000 (UTC) (envelope-from sf@maxempire.com) Received: from oblak.markonjezic.com (localhost [127.0.0.1]) by oblak.markonjezic.com (Postfix) with ESMTP id 1C4982580256; Mon, 26 Jun 2017 11:37:29 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Mon, 26 Jun 2017 11:37:29 +0200 From: Marko Njezic To: FreeBSD Ports Cc: Carmel NY Subject: Re: "clamav-unofficial-sigs" error message Organization: MAX Interactive corp. In-Reply-To: References: Message-ID: <2d83549761090d819114c1c281b03594@njezic.com> X-Sender: sf@maxempire.com User-Agent: Roundcube Webmail 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, 26 Jun 2017 09:43:38 -0000 On 2017-06-25 18:16, Carmel NY wrote: > On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated: > >> From what I can see, the clamav-unofficial-sigs port works. It >> determines if there are updates or whether you have checked recently, >> so that you do not inadvertently dos the signature servers. What is >> NOT working, apparently, is clamav. Did you install clamav via ports? >> If it is installed, what is the clamscan_bin variable set to >> in /usr/local/etc/clamav-unofficial-sigs/master.conf file? It needs to >> be set to the correct path, for instance /usr/local/bin/clamscan. The >> correct path on your setup can be determined using 'which clamscan' > > From the "master.conf" file: > > # Custom Command Paths, these are detected with the which command when > not set. > > Clamscan was commented out; however, the default setting was > to /usr/bin/clamscan > > From what I can figure out, the "which" command worked fine outside of > a CRON job, but was failing when clamav-unofficial-sigs.sh was run via > CRON. I uncommented the "clamscan" setting and set it to point to the > correct location. Now it works correctly. > > This is probably a bug, but I am not going to waste my time reporting > it. The ports version of this program is very old. There have been five > newer versions since its release. No doubt this problem has been > corrected. The error message that you're getting has nothing to do with the version of the script that's available from the ports collection. Contrary to what you think, you would get the same error message with the latest version of the script (clamscan binary detection has remained exactly the same). You obviously did not set up PATH variable correctly for script invoking by cron daemon. On a side note, you mentioned that you edited "master.conf" file. As I wrote in pkg-message, all user configuration changes should go in file "user.conf" file, in order to make updating the script easier. As far as updating the port to the latest version is concerned, the development of the script appeared to be on halt since there were no updates from august last year until march this year and now it is quiet once again. The original script ended up being abandoned and I'm more cautious this time, so that I don't end up wasting my time. -- Regards, Marko Njezic - mr.maX @ MAX Interactive corp. Personal: http://www.markonjezic.com/ From owner-freebsd-ports@freebsd.org Mon Jun 26 10:11: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 9F12EDA6409 for ; Mon, 26 Jun 2017 10:11:12 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 86E84722F7 for ; Mon, 26 Jun 2017 10:11:12 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 86431DA6407; Mon, 26 Jun 2017 10:11:12 +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 85F4ADA6406 for ; Mon, 26 Jun 2017 10:11:12 +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 7809D722F6 for ; Mon, 26 Jun 2017 10:11:12 +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 v5QABCcu083599 for ; Mon, 26 Jun 2017 10:11:12 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v5QABCvl083598; Mon, 26 Jun 2017 10:11:12 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201706261011.v5QABCvl083598@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: Mon, 26 Jun 2017 10:11:12 +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: Mon, 26 Jun 2017 10:11:12 -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 ------------------------------------------------+-----------------+------------ editors/latexila | 3.22.1 | 3.24.2 ------------------------------------------------+-----------------+------------ games/angband | 4.0.5 | 4.1.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 Mon Jun 26 10:42:21 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 A0A51DA6A5F for ; Mon, 26 Jun 2017 10:42:21 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) 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 55B4773261 for ; Mon, 26 Jun 2017 10:42:21 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from [192.168.0.111] (port-212-202-156-99.static.qsc.de [212.202.156.99]) by toco-domains.de (Postfix) with ESMTPA id 128E01AAF068; Mon, 26 Jun 2017 12:42:19 +0200 (CEST) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: David Demelier , freebsd-ports@freebsd.org References: From: Torsten Zuehlsdorff Message-ID: <2f23f3d0-dcb1-dc12-eb9f-c8966a10f5f7@toco-domains.de> Date: Mon, 26 Jun 2017 09:24:17 +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; 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: Mon, 26 Jun 2017 10:42:21 -0000 Aloha David, > 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. The discussions did go on for a while, but lets get more technical. While i can understand your use case, it raises various questions: - How should be EOL-Software handled? For example PHP 5.6, Typo3 7, PostgreSQL 9.2 and many more will expire long before FreeBSD 11 expires but are still valid (or even default version) when created. Since the versions are frozen, how should - at least- security issues handled? [Yes, i read that a user can switch at its own risk to another branch, but lets assume he is very fine with the version (because i have such customer)] - How should be new dependencies handled? GitLab for example sometimes *requieres* updates of its dependencies in order to fix security issues. - Same as above: how should be dropped dependencies handled? In worst case we need to maintain them for nearly 5 years, but nobody (should) use them - How to resolve conflicts? I mentioned GitLab above and now realize, that sometimes the GitLab update breaks for example www/redmine because it depends at other versions than GitLab. - Where do get the fixes from? We have around 26.000 ports which needs fixes in worst case - How to handle for example security issues only fixed through an update? Which such a long time between "updates" it gets very very hard to port/get/write patches in fast developing software. Wordpress or Gitlab are typical examples with thousands of lines in code-changes every update - How to make the customer clear, that complains about the software (old, outdated, missing features, unresolved bugs, etc) are intentional? - Where to archive the distfiles? Sometimes upstream completely remove them from everywhere they can. And last: how to make updates from FreeBSD version to version easier? Many user already have problems with single major updates. From my experiences in Windows or Ubuntu LTS usages with such or very similar version handling: the update, even of the OS, is pushed as far away as possible, because of the big amount of work required, since everything needs to checked/updated/changed. I have a hard time to image, that is handled in another way by you. So if you can me give more insight about your use-case i would be happy to read it for a better understanding. I have various customer requiring (and paying for) very old software (for example still PHP 5.3). So i know some of there motivations, which boils every time down to "its to expensive to upgrade our software" [but they don't mean expensive in money]. So maybe we can make something happen. Greetings, Torsten From owner-freebsd-ports@freebsd.org Mon Jun 26 11:26: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 39B85DA784B for ; Mon, 26 Jun 2017 11:26:42 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from NAM04-BN3-obe.outbound.protection.outlook.com (mail-oln040092009103.outbound.protection.outlook.com [40.92.9.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C94FA745F6 for ; Mon, 26 Jun 2017 11:26:40 +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=mpi3fv9DjkE/c1eIFrKewPm7ldKpiESZ8PLc3h13Qag=; b=WkynlmMu17YWy0GKb0KeI9PZAEsvw9UmWxtCjMi0OF/jVd35jDjPnnjrWrL49WbuyzMn5DcD1zoyrmhAln2YBFjHzOo33R7cEBhoQjziDPwn5CWrzQGEXk1lRrEBLt6iWFka61qQvqfpcUHlHXGfwNq+XIxSh114g/oPRaP6Jk4gyyoQSb9V+uBf4H0UsTicRVOgwaXDkSnWEiIQoPvppeIW477EiUzdr789UNDUNTgYNosf8BUMMX1OEWngVjD6FD0M5cyzZ8s75OUO5ESSa3a1+CZmAKMukur/I1kBMzvcTWj/lWkYM6YiVTQCF1ibKH3Wv9o+nWwXLb6tXRvn8w== Received: from SN1NAM04FT028.eop-NAM04.prod.protection.outlook.com (10.152.88.57) by SN1NAM04HT201.eop-NAM04.prod.protection.outlook.com (10.152.89.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1178.14; Mon, 26 Jun 2017 11:26:39 +0000 Received: from BN6PR2001MB1730.namprd20.prod.outlook.com (10.152.88.51) by SN1NAM04FT028.mail.protection.outlook.com (10.152.88.113) 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; Mon, 26 Jun 2017 11:26:39 +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.019; Mon, 26 Jun 2017 11:26:39 +0000 From: Carmel NY To: FreeBSD Ports CC: "sf@maxempire.com" Subject: Re: "clamav-unofficial-sigs" error message Thread-Topic: "clamav-unofficial-sigs" error message Thread-Index: AQHS7Z1FHL0OrckEqU2LLgg1eJhAog== Date: Mon, 26 Jun 2017 11:26:39 +0000 Message-ID: References: <2d83549761090d819114c1c281b03594@njezic.com> In-Reply-To: <2d83549761090d819114c1c281b03594@njezic.com> 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:5A3A9A4717B732CCF899C2E2E76696F32C385664FDE36C2AB9785496846136C2; UpperCasedChecksum:5C5171DE116A0C4DE33B3C77B65EAB7F8D5C1A46AF8161856B4D5899B0E4BE10; SizeAsReceived:7500; Count:47 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [DkoT2TEpK8qEWnxMqL/AcOe1VylGdjPC] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; SN1NAM04HT201; 7:IzoZuA3aQ4mwlwj2BMviTayUHLl72n597Oh5pLjezr8bDJc6sNIaDm+yLeiu95+yq8mAfH2k6pRpuH9f5UxixfYjOwFTb7g30eBUHY/hjYPbY8TJMA+A9BalJlJ6iEqB1Va2I9/GTbjFeT6Yx5HOYfoMfgusun4I08uR/mu2iDeVUZebF9laKF1L81GW5HoMdqeXyM+lf2lTo8a4MnR0FUdhOduNvQXY38J23TPmTdrtp7EIzjHyy3VV+LmjL9dAePZPUbOtZTGVd0j2uafo/GB55v4hQ9v8ZSFlxjtBft8L7tR862Suy1QSQYaBTNlNQ/7UnGFJk178ziuFfK+tED7CFNXrG3McvNrqgPclWo2FlG3s+txda41cThvcH/SmoA3uTO14DZDPwRaGFVtLu86/FtHKLXkDcU0p1NvPAzCW9X0rx6EBHZDqZ3xFj7PVzHVX2TuDpKEr6QpFWBbpm/FtdCrbcMwZbWfQLKBNRFvzBA8JkVU8cu6SylyZe9dx2BcDuLf7hye2vLcDAZUTGoKaddMyLm6GWNw9nkytPpAQJZEVTWH4dz4FfFet4u8QETSnLpLoH73TKUfMtV6Ca28h6+El0klbYKM3M2BH4gMv5iJNgIIYAvMQr1tLuv1d2YAXTzGuFCJJDGQeNb9QoiRPsj2+XycWSXB/KkibuRB34o7D+k2H/ll42wNIvjYbakw/wfQLg0HWrnfwMPaXq3NkQPDyXJrRDvgqYi1u20h+nlpSswR6m73qLZGUFR6Lt7cqcqfMBxzJVfsSJejvyA== x-incomingheadercount: 47 x-eopattributedmessage: 0 x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:SN1NAM04HT201; H:BN6PR2001MB1730.namprd20.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: b7ab993e-7b8a-4977-b07e-08d4bc8635e1 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)(300000506067)(300135500095); SRVR:SN1NAM04HT201; x-ms-traffictypediagnostic: SN1NAM04HT201: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:SN1NAM04HT201; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:SN1NAM04HT201; x-forefront-prvs: 0350D7A55D spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jun 2017 11:26:39.4517 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM04HT201 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, 26 Jun 2017 11:26:42 -0000 T24gTW9uLCAyNiBKdW4gMjAxNyAxMTozNzoyOSArMDIwMCwgTWFya28gTmplemljIHN0YXRlZDoN Cg0KPk9uIDIwMTctMDYtMjUgMTg6MTYsIENhcm1lbCBOWSB3cm90ZToNCj4+IE9uIFN1biwgMjUg SnVuIDIwMTcgMTc6MTc6NDQgKzAyMDAsIE1hcnRpbiBXYXNjaGLDvHNjaCBzdGF0ZWQ6DQo+PiAg IA0KPj4+IEZyb20gd2hhdCBJIGNhbiBzZWUsIHRoZSBjbGFtYXYtdW5vZmZpY2lhbC1zaWdzIHBv cnQgd29ya3MuIEl0DQo+Pj4gZGV0ZXJtaW5lcyBpZiB0aGVyZSBhcmUgdXBkYXRlcyBvciB3aGV0 aGVyIHlvdSBoYXZlIGNoZWNrZWQNCj4+PiByZWNlbnRseSwgc28gdGhhdCB5b3UgZG8gbm90IGlu YWR2ZXJ0ZW50bHkgZG9zIHRoZSBzaWduYXR1cmUNCj4+PiBzZXJ2ZXJzLiBXaGF0IGlzIE5PVCB3 b3JraW5nLCBhcHBhcmVudGx5LCBpcyBjbGFtYXYuIERpZCB5b3UNCj4+PiBpbnN0YWxsIGNsYW1h diB2aWEgcG9ydHM/IElmIGl0IGlzIGluc3RhbGxlZCwgd2hhdCBpcyB0aGUNCj4+PiBjbGFtc2Nh bl9iaW4gdmFyaWFibGUgc2V0IHRvDQo+Pj4gaW4gL3Vzci9sb2NhbC9ldGMvY2xhbWF2LXVub2Zm aWNpYWwtc2lncy9tYXN0ZXIuY29uZiBmaWxlPyBJdCBuZWVkcw0KPj4+IHRvIGJlIHNldCB0byB0 aGUgY29ycmVjdCBwYXRoLCBmb3INCj4+PiBpbnN0YW5jZSAvdXNyL2xvY2FsL2Jpbi9jbGFtc2Nh bi4gVGhlIGNvcnJlY3QgcGF0aCBvbiB5b3VyIHNldHVwDQo+Pj4gY2FuIGJlIGRldGVybWluZWQg dXNpbmcgJ3doaWNoIGNsYW1zY2FuJyAgDQo+PiANCj4+IEZyb20gdGhlICJtYXN0ZXIuY29uZiIg ZmlsZToNCj4+IA0KPj4gIyBDdXN0b20gQ29tbWFuZCBQYXRocywgdGhlc2UgYXJlIGRldGVjdGVk IHdpdGggdGhlIHdoaWNoIGNvbW1hbmQNCj4+IHdoZW4gbm90IHNldC4NCj4+IA0KPj4gQ2xhbXNj YW4gd2FzIGNvbW1lbnRlZCBvdXQ7IGhvd2V2ZXIsIHRoZSBkZWZhdWx0IHNldHRpbmcgd2FzDQo+ PiB0byAvdXNyL2Jpbi9jbGFtc2Nhbg0KPj4gDQo+PiBGcm9tIHdoYXQgSSBjYW4gZmlndXJlIG91 dCwgdGhlICJ3aGljaCIgY29tbWFuZCB3b3JrZWQgZmluZSBvdXRzaWRlDQo+PiBvZiBhIENST04g am9iLCBidXQgd2FzIGZhaWxpbmcgd2hlbiBjbGFtYXYtdW5vZmZpY2lhbC1zaWdzLnNoIHdhcw0K Pj4gcnVuIHZpYSBDUk9OLiBJIHVuY29tbWVudGVkIHRoZSAiY2xhbXNjYW4iIHNldHRpbmcgYW5k IHNldCBpdCB0bw0KPj4gcG9pbnQgdG8gdGhlIGNvcnJlY3QgbG9jYXRpb24uIE5vdyBpdCB3b3Jr cyBjb3JyZWN0bHkuDQo+PiANCj4+IFRoaXMgaXMgcHJvYmFibHkgYSBidWcsIGJ1dCBJIGFtIG5v dCBnb2luZyB0byB3YXN0ZSBteSB0aW1lIHJlcG9ydGluZw0KPj4gaXQuIFRoZSBwb3J0cyB2ZXJz aW9uIG9mIHRoaXMgcHJvZ3JhbSBpcyB2ZXJ5IG9sZC4gVGhlcmUgaGF2ZSBiZWVuDQo+PiBmaXZl IG5ld2VyIHZlcnNpb25zIHNpbmNlIGl0cyByZWxlYXNlLiBObyBkb3VidCB0aGlzIHByb2JsZW0g aGFzIGJlZW4NCj4+IGNvcnJlY3RlZC4gIA0KPg0KPlRoZSBlcnJvciBtZXNzYWdlIHRoYXQgeW91 J3JlIGdldHRpbmcgaGFzIG5vdGhpbmcgdG8gZG8gd2l0aCB0aGUNCj52ZXJzaW9uIG9mIHRoZSBz Y3JpcHQgdGhhdCdzIGF2YWlsYWJsZSBmcm9tIHRoZSBwb3J0cyBjb2xsZWN0aW9uLg0KPg0KPkNv bnRyYXJ5IHRvIHdoYXQgeW91IHRoaW5rLCB5b3Ugd291bGQgZ2V0IHRoZSBzYW1lIGVycm9yIG1l c3NhZ2Ugd2l0aCANCj50aGUgbGF0ZXN0IHZlcnNpb24gb2YgdGhlIHNjcmlwdCAoY2xhbXNjYW4g YmluYXJ5IGRldGVjdGlvbiBoYXMNCj5yZW1haW5lZCBleGFjdGx5IHRoZSBzYW1lKS4gWW91IG9i dmlvdXNseSBkaWQgbm90IHNldCB1cCBQQVRIIHZhcmlhYmxlDQo+Y29ycmVjdGx5IGZvciBzY3Jp cHQgaW52b2tpbmcgYnkgY3JvbiBkYWVtb24uDQoNClRoaXMgaXMgdGhlIGRlZmF1bHQgc2V0dGlu ZzoNCg0KIyBDdXN0b20gQ29tbWFuZCBQYXRocywgdGhlc2UgYXJlIGRldGVjdGVkIHdpdGggdGhl IHdoaWNoIGNvbW1hbmQgd2hlbg0Kbm90IHNldA0KIyB1bmFtZV9iaW49Ii91c3IvYmluL3VuYW1l Ig0KIyBjbGFtc2Nhbl9iaW49Ii91c3IvYmluL2NsYW1zY2FuIg0KIyByc3luY19iaW49Ii91c3Iv YmluL3JzeW5jIg0KIyB3Z2V0X2Jpbj0iL3Vzci9iaW4vd2dldCINCiMgY3VybF9iaW49Ii91c3Iv YmluL2N1cmwiDQojIGdwZ19iaW49Ii91c3IvYmluL2dwZyINCg0KSSBvbmx5IG5lZWRlZCB0byB1 bmNvbW1lbnQgYW5kIGNoYW5nZSB0aGUgImNsYW1zY2FuX2JpbiIgc2V0dGluZyB0byBnZXQNCml0 IHdvcmtpbmcgY29ycmVjdGx5IHdoZW4gcnVuIHZpYSBDUk9OLiBTaW5jZSB0aGUgb3RoZXIgc2V0 dGluZ3MgYXJlDQpub3QgY29ycmVjdCBmb3IgYSBGcmVlQlNEIHN5c3RlbSwgeWV0IHN0aWxsIHdv cmssIEkgZG8gYmVsaWV2ZSBpdCBpcyBhDQpidWcgb2Ygc29tZSBzb3J0cy4gSG93ZXZlciwgaXQg aXMgbm90IHdvcnRoIGFyZ3VpbmcgYWJvdXQuDQoNCj5PbiBhIHNpZGUgbm90ZSwgeW91IG1lbnRp b25lZCB0aGF0IHlvdSBlZGl0ZWQgIm1hc3Rlci5jb25mIiBmaWxlLiBBcyBJIA0KPndyb3RlIGlu IHBrZy1tZXNzYWdlLCBhbGwgdXNlciBjb25maWd1cmF0aW9uIGNoYW5nZXMgc2hvdWxkIGdvIGlu IGZpbGUgDQo+InVzZXIuY29uZiIgZmlsZSwgaW4gb3JkZXIgdG8gbWFrZSB1cGRhdGluZyB0aGUg c2NyaXB0IGVhc2llci4NCj4NCj5BcyBmYXIgYXMgdXBkYXRpbmcgdGhlIHBvcnQgdG8gdGhlIGxh dGVzdCB2ZXJzaW9uIGlzIGNvbmNlcm5lZCwgdGhlIA0KPmRldmVsb3BtZW50IG9mIHRoZSBzY3Jp cHQgYXBwZWFyZWQgdG8gYmUgb24gaGFsdCBzaW5jZSB0aGVyZSB3ZXJlIG5vIA0KPnVwZGF0ZXMg ZnJvbSBhdWd1c3QgbGFzdCB5ZWFyIHVudGlsIG1hcmNoIHRoaXMgeWVhciBhbmQgbm93IGl0IGlz DQo+cXVpZXQgb25jZSBhZ2Fpbi4gVGhlIG9yaWdpbmFsIHNjcmlwdCBlbmRlZCB1cCBiZWluZyBh YmFuZG9uZWQgYW5kIEknbQ0KPm1vcmUgY2F1dGlvdXMgdGhpcyB0aW1lLCBzbyB0aGF0IEkgZG9u J3QgZW5kIHVwIHdhc3RpbmcgbXkgdGltZS4NCg0KSSBhbSBub3Qgc3VyZSB3aGF0IHRoYXQgaXMg c3VwcG9zZWQgdG8gbWVhbi4gVGhlIHBvc3RmaXggInN0YWJsZSINCnZlcnNpb24gaXMgb25seSB1 cGRhdGVkIGFwcHJveGltYXRlbHkgb25jZSBhIHllYXIuIEEgcHJvZ3JhbSBkb2VzIG5vdA0KaGF2 ZSB0byBiZSB1cGRhdGVkIGV2ZXJ5ICJYIiBudW1iZXIgb2YgZGF5cyB0byBiZSBhY3RpdmVseSBk ZXZlbG9wZWQuDQpJbiBhbnkgY2FzZSwgdGhlcmUgaGF2ZSBiZWVuIGZpdmUgbmV3IHZlcnNpb25z IHJlbGVhc2VkIHNpbmNlIHRoZSBvbmUNCmluIHRoZSBwb3J0cyBzeXN0ZW0gd2FzIHJlbGVhc2Vk LiBDZXJ0YWlubHkgdGhhdCB3b3VsZCBzZWVtIHRvIGluZGljYXRlDQp0aGF0IHNvbWV0aGluZyB3 YXMgaGFwcGVuaW5nIHdpdGggdGhlIGFwcGxpY2F0aW9uLg0KDQotLSANCkNhcm1lbA0KDQoNCg== From owner-freebsd-ports@freebsd.org Mon Jun 26 12:14: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 D12E8DA9021 for ; Mon, 26 Jun 2017 12:14:15 +0000 (UTC) (envelope-from sf@maxempire.com) Received: from oblak.markonjezic.com (oblak.markonjezic.com [78.31.66.29]) (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 7BE2376389 for ; Mon, 26 Jun 2017 12:14:14 +0000 (UTC) (envelope-from sf@maxempire.com) Received: from oblak.markonjezic.com (localhost [127.0.0.1]) by oblak.markonjezic.com (Postfix) with ESMTP id E685C2580256 for ; Mon, 26 Jun 2017 14:14:11 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Mon, 26 Jun 2017 14:14:11 +0200 From: Marko Njezic To: FreeBSD Ports Subject: Re: "clamav-unofficial-sigs" error message Organization: MAX Interactive corp. In-Reply-To: References: <2d83549761090d819114c1c281b03594@njezic.com> Message-ID: X-Sender: sf@maxempire.com User-Agent: Roundcube Webmail 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, 26 Jun 2017 12:14:15 -0000 On 2017-06-26 13:26, Carmel NY wrote: > On Mon, 26 Jun 2017 11:37:29 +0200, Marko Njezic stated: > >> On 2017-06-25 18:16, Carmel NY wrote: >>> On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated: >>> >>>> From what I can see, the clamav-unofficial-sigs port works. It >>>> determines if there are updates or whether you have checked >>>> recently, so that you do not inadvertently dos the signature >>>> servers. What is NOT working, apparently, is clamav. Did you >>>> install clamav via ports? If it is installed, what is the >>>> clamscan_bin variable set to >>>> in /usr/local/etc/clamav-unofficial-sigs/master.conf file? It needs >>>> to be set to the correct path, for >>>> instance /usr/local/bin/clamscan. The correct path on your setup >>>> can be determined using 'which clamscan' >>> >>> From the "master.conf" file: >>> >>> # Custom Command Paths, these are detected with the which command >>> when not set. >>> >>> Clamscan was commented out; however, the default setting was >>> to /usr/bin/clamscan >>> >>> From what I can figure out, the "which" command worked fine outside >>> of a CRON job, but was failing when clamav-unofficial-sigs.sh was >>> run via CRON. I uncommented the "clamscan" setting and set it to >>> point to the correct location. Now it works correctly. >>> >>> This is probably a bug, but I am not going to waste my time reporting >>> it. The ports version of this program is very old. There have been >>> five newer versions since its release. No doubt this problem has been >>> corrected. >> >> The error message that you're getting has nothing to do with the >> version of the script that's available from the ports collection. >> >> Contrary to what you think, you would get the same error message with >> the latest version of the script (clamscan binary detection has >> remained exactly the same). You obviously did not set up PATH variable >> correctly for script invoking by cron daemon. > > This is the default setting: > > # Custom Command Paths, these are detected with the which command when > not set > # uname_bin="/usr/bin/uname" > # clamscan_bin="/usr/bin/clamscan" > # rsync_bin="/usr/bin/rsync" > # wget_bin="/usr/bin/wget" > # curl_bin="/usr/bin/curl" > # gpg_bin="/usr/bin/gpg" > > I only needed to uncomment and change the "clamscan_bin" setting to get > it working correctly when run via CRON. Since the other settings are > not correct for a FreeBSD system, yet still work, I do believe it is a > bug of some sorts. However, it is not worth arguing about. You did not set up PATH variable correctly in your crontab. This is not a bug in the script. Also, master.conf and os.conf files should not be modified, or you will end up with old versions of those files when updating to a new version of the port. All user changes should be placed in user.conf (this is mentioned in both pkg-message and ports/UPDATING). >> On a side note, you mentioned that you edited "master.conf" file. As I >> wrote in pkg-message, all user configuration changes should go in file >> "user.conf" file, in order to make updating the script easier. >> >> As far as updating the port to the latest version is concerned, the >> development of the script appeared to be on halt since there were no >> updates from august last year until march this year and now it is >> quiet once again. The original script ended up being abandoned and I'm >> more cautious this time, so that I don't end up wasting my time. > > I am not sure what that is supposed to mean. The postfix "stable" > version is only updated approximately once a year. A program does not > have to be updated every "X" number of days to be actively developed. > In any case, there have been five new versions released since the one > in the ports system was released. Certainly that would seem to indicate > that something was happening with the application. That means exactly what I wrote. I don't want to waste my time, if forked version also ends up being abandoned. -- Regards, Marko Njezic - mr.maX @ MAX Interactive corp. Personal: http://www.markonjezic.com/ From owner-freebsd-ports@freebsd.org Mon Jun 26 13:54: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 B3513D87E30 for ; Mon, 26 Jun 2017 13:54:59 +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 9C9137A653 for ; Mon, 26 Jun 2017 13:54:59 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: by mailman.ysv.freebsd.org (Postfix) id 9BBF9D87E2E; Mon, 26 Jun 2017 13:54: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 9B3DED87E2C for ; Mon, 26 Jun 2017 13:54:59 +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 61E9A7A652 for ; Mon, 26 Jun 2017 13:54:58 +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 E4CE028436; Mon, 26 Jun 2017 15:54:49 +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 0C94828432; Mon, 26 Jun 2017 15:54:49 +0200 (CEST) Subject: Re: sysutils/tmux - strange behaviour with new version 2.4 / 2.5 To: v@fatpipi.com Cc: FreeBSD Ports References: <5919E2CE.5010109@quip.cz> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <59511228.1010104@quip.cz> Date: Mon, 26 Jun 2017 15:54:48 +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=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: Mon, 26 Jun 2017 13:54:59 -0000 Vanilla Hsu wrote on 2017/05/16 01:37: > I got the same problem too, but after update to 2.5-rc2, all issues gone. > > maybe you can try to update to 2.5-rc2 (2.5 not yet released) by yourself. Opening this again. I downgraded to 2.3 in the meantime but I had a hope that 2.5 will be fine - it is not. Event final 2.5 exhibits the same symptoms as 2.4 on my machines and doesn't show innocent lines of text file. Does 2.5 work for you or anybody else without issues? What is you tmux.conf? (I tried it with empty but still have this problem) Miroslav Lachman > 2017-05-16 1:18 GMT+08:00 Miroslav Lachman <000.fbsd@quip.cz > >: > > I noticed some strange behaviours with Tmux 2.4. > If I run "cat /path/to/somefile.txt" sometimes part of file is > missing in the output (no special characters in this text file, it > is log of "pkg upgrade") > > And I thing some key presses are interpreted differently. (in Vim) > > I know that nobody can solve this without more details... so I am > just asking if I am alone or somebody else have this problem too? From owner-freebsd-ports@freebsd.org Mon Jun 26 14:10: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 A6BADD883B7; Mon, 26 Jun 2017 14:10:44 +0000 (UTC) (envelope-from papowell@astart.com) Received: from astart2.astart.com (wsip-72-214-30-30.sd.sd.cox.net [72.214.30.30]) (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 77D877AD24; Mon, 26 Jun 2017 14:10:43 +0000 (UTC) (envelope-from papowell@astart.com) Received: from laptop_103.private (localhost [127.0.0.1]) by astart2.astart.com (8.14.9/8.14.9) with ESMTP id v5QE0j8X082701; Mon, 26 Jun 2017 07:00:46 -0700 (PDT) (envelope-from papowell@astart.com) Reply-To: papowell@astart.com Subject: Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work References: <6FD738D6-F163-4BC5-8E6E-A9B9F35595CD@dsl-only.net> To: freebsd-ports@freebsd.org Cc: Gerald Pfeifer , Dimitry Andric , Konstantin Belousov , freebsd-stable@freebsd.org, Jung-uk Kim , "papowell@astart.com" , Ian Cameron From: Patrick Powell Organization: Astart Technologies Message-ID: <9b7cf494-1a81-4151-92fe-4a3305b17cb1@astart.com> Date: Mon, 26 Jun 2017 07:00:45 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <6FD738D6-F163-4BC5-8E6E-A9B9F35595CD@dsl-only.net> Content-Type: text/plain; charset=windows-1252; 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: Mon, 26 Jun 2017 14:10:44 -0000 I have reported this problem - see email to freebsd-stable Re: GCC + FreeBSD 11.0 Stable - stat.h does not have vm_ooffset_t definition Here is part of the discussion: On Sat, 29 Apr 2017, Dimitry Andric wrote: > This is because gcc's fixincludes process makes copies of certain system > headers (in this case, /usr/include/sys/types.h) with slight > modifications. Then, it places the directory containing the modified > headers at the front of the include search path. So far so good. > > Now, whenever sys/types.h is updated, as happened with the vm_ooffset_t > change, the header in gcc's own preferred directory might not match the > definitions which are expected, leading to compilation errors. >> If the port/package is builts from scratch, does this trigger the >> problem? > Yes, basically you need to rebuild all gcc ports from scratch, whenever > you update any system header that matches gcc's list of files it wants > to modify. That, or run the fixinc.sh script in ./libexec/gcc/$TARGETTRIPLET/$VERSION/install-tools/fixinc.sh. The proposed patch would help with that, but still require a manual run, hence my original question. On Sun, 30 Apr 2017, Konstantin Belousov wrote: > Am I right that Jung-uk fix replaces vm_ooffset_t and vm_pindex_t with > explicit int64_t and uint64_t use, as the course of action for gcc > fixincludes step ? If yes, I completely disagree. > > The change blocks any future changes to the type that might occur in the > base system, for the code compiled by gcc. End result might be as bad > as mismatched ABI, in the worst case. Okay, thanks for your feedback. > With all of the above, IMO most sane way to fix problems is to > rename fixincludes directory to some name which is ignored by gcc, > e.g. include-fixed -> include-fixed.saved. This can be done as > post-installation step in the ports. This is what I figured, too, and plan on giving a try. It probably warrants an -exp run to be on the safe side. On Sun, 30 Apr 2017, Dimitry Andric wrote: > I agree, it would be best to avoid storing any copies of system headers > completely. > > Maybe the port can have an option FIX_INCLUDES, which defaults to off? > I am not sure if there is anybody that really wants these 'fixed' > headers, though. There are two infrastructure improvements for the (current) GCC ports (orthogonal to a few simpler things I've been simplifying today in older ports) that I'd like to conclude first, otherwise there'll be too many balls in the air. (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218475 is the last hold-off on the first of them, in case anyone can give this a try. It is on my list to pursue directly afterwards, then. (Luckily this only hits with most -CURRENT versions of FreeBSD and older packages only.) Gerald On 06/24/17 17:55, Mark Millard wrote: > The following is based mostly on an extraction from a > private exchange in which a question was asked and my > answer was unsettling: incompatibilities within the > 11.* family. I would not normally send to re but doing > so was explicitly mentioned. Hopefully this example is > reasonable for doing that. > > > Aspect #0: what is broken currently (and in the future?) > within the 11.* family? > > lang/gcc* packages built on release/11.0.1/ to not work > fully on stable/11/ or on the drafts of > release/11.1.0/ . (I leave releng/11.*/'s implicit.) > > -r313194 in head and was describied with: > >> Define the vm_ooffset_t and vm_pindex_t types as machine-independend. >> >> The types are for the byte offset and page index in vm object. They >> are similar to off_t, which is defined as 64bit MI integer. Using MI >> definitions will allow to provide consistent MD values of vm >> object-related maximum sizes. > The known issue is the generation of header dependencies > in the lang/gcc* builds on release/11.0.1/ that when > used on stable/11/ or release/11.0.1/ generate reports > like: > > /usr/local/lib/gcc5/gcc/x86_64-portbld-freebsd11.0/5.4.0/include-fixed/sys/types.h:266:9: error: '__vm_ooffset_t' does not name a type > typedef __vm_ooffset_t vm_ooffset_t; > ^ > /usr/local/lib/gcc5/gcc/x86_64-portbld-freebsd11.0/5.4.0/include-fixed/sys/types.h:268:9: error: '__vm_pindex_t' does not name a type > typedef __vm_pindex_t vm_pindex_t; > ^ > *** [CoinFactorization2.lo] Error code 1 > > Unfortunately UPDATING was not updated > for head/'s -r313194 (2017-Feb-4) --nor for > stable/11/'s -r313574 (2017-Feb-11), the MFC. > (No MFC was made to stable/10/ or to > release/10.3.0 as far as I found.) > > (These changes predate the INO64 issue in head/ . > Head ends up with more issues than I'm dealing > with here.) > > > Aspect #1: what 11.* version builds the pre-built packages > targeting 11.* and the apparent consequences > (given the vm_ooffset_t and vm_pindex_t changes > and the lang/gcc* build behavior) > > This is the unsettling part for pre-built > packages: incompatibilities within the 11.* > family for the lang/gcc* packages. > > http://portsmon.freebsd.org/portoverview.py?category=%3Bamng&portname=gcc5&wildcard= > > shows categories for builds for > > 8.4 > 9.3 > 10.1 > 10.3 > 11.0 > head > > (Nothing for stable/*/ .) > > But the 10.3 rows show no package > builds. I would guess that they > start once 10.1 stops > (approximately). > > So it may be that 11.1 will not > get package builds until 11.0 > stops (approximately). > > If so unless lang/gcc* are changed > to bootstrap differently they will > configure to match release/11.0.1/ > and will not be compatible with the > vm_ooffset_t and vm_pindex_t changes > in stable/11/ and release/11.1.0/ . > > But as I understand updating how the > lang/gcc* builds work to remove such > dependencies is under investigation. > I do not know any timing relative to > release/11.1.0/ if my understanding > is right. > > Until then (if I was right): > > Unless there are separate packages made for > targeting release/11.0.1/ vs. release/11.1.0/ > it is not obvious when lang/gcc* packages > will be generally compatible with various > folks choices about what to install as the > system version within the release/11.*/ > and stable/11/ family. This would likely > be true even if they were built on > release/11.1.0/ : then release/11.0.1/ > likely would have compatibility problems. > > The ABI versioning does not cover the specific > issues involved based on how vm_ooffset_t and > vm_pindex_t were changed and what the > lang/gcc* builds do relative to such changes. > Yet there is incompatibility for some > fairly-significant-usage ports. > > > Aspect #2: stable/10/ and release/10.4.0/ > > Just covered for completeness: > > I do not see a MFC of -r313194 to stable/10/ : > its sys/sys/types.h dates back to 2015-Oct-10. > So it looks like 10.x has a permanent difference > in this area: 10.x continues to get separate > lang/gcc* package builds from 11.x and later. > No problem for this context as far as I know. > > > > > Note: To simplify I choose to not be explicit > about what authors wrote what original text. > If that becomes an issue, it is correctable. > > Blame me for any errors in the above. > > === > Mark Millard > markmi at dsl-only.net > > _______________________________________________ > 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" > -- Patrick Powell Astart Technologies papowell@astart.com 1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting Cell 858-518-7581 FAX 858-751-2435 Web: papowell at astart dot com From owner-freebsd-ports@freebsd.org Mon Jun 26 15:32: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 A07B8D8A0C9 for ; Mon, 26 Jun 2017 15:32:19 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 51D157D7F0; Mon, 26 Jun 2017 15:32:19 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 75517BDC89; Mon, 26 Jun 2017 17:32:16 +0200 (CEST) Received: from ogg.in.absolight.net (ogg.in.absolight.net [79.143.241.239]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by prod2.absolight.net (Postfix) with ESMTPSA id 37A74BDC85; Mon, 26 Jun 2017 17:32:16 +0200 (CEST) Subject: Re: USE_GCC usage To: Richard Gallamore , freebsd-ports@FreeBSD.org References: From: Mathieu Arnold Organization: Absolight / The FreeBSD Foundation Message-ID: Date: Mon, 26 Jun 2017 17:32:14 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="UNFm3nMjkk7D62HHFUqJb1tnHsg3ERAS2" 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, 26 Jun 2017 15:32:19 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --UNFm3nMjkk7D62HHFUqJb1tnHsg3ERAS2 Content-Type: multipart/mixed; boundary="XUPLdNR3HkrqiCrTqNjtpiQm17CSD0aXp"; protected-headers="v1" From: Mathieu Arnold To: Richard Gallamore , freebsd-ports@FreeBSD.org Message-ID: Subject: Re: USE_GCC usage References: In-Reply-To: --XUPLdNR3HkrqiCrTqNjtpiQm17CSD0aXp Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: fr Le 25/06/2017 =C3=A0 19:09, Richard Gallamore a =C3=A9crit : > When using USE_GCC=3D 5+, errors occur because this USE only sets > build and run time dependency, and not lib dependency. > > Error: /usr/local/bin/ann_in is linked to /usr/local/lib/gcc5/libgfortr= an.so.3 from lang/gcc but it is not declared as a dependency > Error: /usr/local/bin/ann_in is linked to /usr/local/lib/gcc5/libquadma= th.so.0 from lang/gcc but it is not declared as a dependency > Error: /usr/local/bin/c81merge is linked to /usr/local/lib/gcc5/libstdc= ++.so.6 from lang/gcc but it is not declared as a dependency > Error: /usr/local/bin/c81merge is linked to /usr/local/lib/gcc5/libgcc_= s.so.1 from lang/gcc but it is not declared as a dependency > > Should this be considered a false positive? or should USE_GCC > also add a LIB_DEPEND to ports? This is quite strange. lang/gcc does not provide any of those libraries. lang/gcc is a metapackage, the only thing it does is depend on the lang/gccXX you asked for, and it provide symlinks: # pkg info -l lang/gcc gcc-5.4.0_2: /usr/local/bin/g++ /usr/local/bin/gcc /usr/local/bin/gfortran # ls -l $(pkg info -ql lang/gcc) lrwxr-xr-x 1 root wheel 4 29 mai 15:21 /usr/local/bin/g++@ -> g++5 lrwxr-xr-x 1 root wheel 4 29 mai 15:21 /usr/local/bin/gcc@ -> gcc5 lrwxr-xr-x 1 root wheel 9 29 mai 15:21 /usr/local/bin/gfortran@ -> gfortran5 --=20 Mathieu Arnold --XUPLdNR3HkrqiCrTqNjtpiQm17CSD0aXp-- --UNFm3nMjkk7D62HHFUqJb1tnHsg3ERAS2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJZUSj/XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IsWIQALYscznHhwXNm2JZzAv0a9mN 8iWZssEdCPe2GuEtjdleqo1UsSawsZ/f8KPOpaVy747lUul97SqzuFCPjHPvpxK4 sjC3LYN5X9Kjm0Lc60LUlPsbdiL7aAG84yi9JisXGhEHTFl41KrM7XheIpqclb3d 1Md0wTDxrrxbJOdVQwgIVMJ+3r06xRCw5Nq/CreHUTWBMYbxTU+Dw8/PSAxwIe/j nuCZO5Z9UZ0itAqPG3JiFyr8jD9+N8bd52temGALe7UObhXefIL2k6OR5fkybcOC Ag0hnPEexcsR+wzVfZNmi1FsNJFV2KzIPH3bZJvYC879lbnrZL7zc6dN4Rw7WU6+ 5Y1aGN5ilucouMaG/mYpHkdRRzhMyszq4wwuPw0kKz9T0MhRQqoHmJ6zQqjMRLZZ 5GoO3rTjjlyLs27QVkNWgu6/kLzcTrFJ1pGMgye/oD5ODUagG75qIikHDkOU3hIF Sw/JnIBH0Ydhis8QN0C77wHlqDqHM15ZjH3PBil8N0LzRIJoB0ewJ5QqmKCb/DNC wH2CerfULm6qT5CJ+8KLDbEi2OYJL8oP0DjEWEPKQRF6U4H39pPjynNcmWKAulv3 ZJ1NrMOo/gPcqQy9wh+AYY1X3omGaakSXCQoKlqrYotT1+1N9FzpUJ+KI5KIyggS zdCQyUXL95tMR8tRvQpO =mX+L -----END PGP SIGNATURE----- --UNFm3nMjkk7D62HHFUqJb1tnHsg3ERAS2-- From owner-freebsd-ports@freebsd.org Mon Jun 26 18:55: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 7E152D8E762; Mon, 26 Jun 2017 18:55:53 +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 61CEA8419F; Mon, 26 Jun 2017 18:55:52 +0000 (UTC) (envelope-from andre@drenet.net) Received: from localhost (localhost [127.0.0.1]) by anet3.andregoree.net (Postfix) with ESMTP id 1D6D2DB3670; Mon, 26 Jun 2017 14:55: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 68767-10; Mon, 26 Jun 2017 14:55:44 -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 40CAEDB34CC; Mon, 26 Jun 2017 14:55:44 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 26 Jun 2017 14:55:44 -0400 From: Andre Goree To: Dewayne Geraghty Cc: freebsd-ports@freebsd.org, owner-freebsd-ports@freebsd.org Subject: Re: NEW APR/APR-Utils In-Reply-To: <96a2704f-f59a-e16d-26cf-d796ead498db@heuristicsystems.com.au> References: <20170622130021.GB41229@doctor.nl2k.ab.ca> <96a2704f-f59a-e16d-26cf-d796ead498db@heuristicsystems.com.au> 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: Mon, 26 Jun 2017 18:55:53 -0000 On 2017/06/22 9:43 pm, 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. > _______________________________________________ > 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" Though I'm late seeing this, thank you for this reply! I'll try out this patch -- 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 Mon Jun 26 19:12: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 28FA8D8EBE7 for ; Mon, 26 Jun 2017 19:12:31 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-10.reflexion.net [208.70.210.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D809F849CC for ; Mon, 26 Jun 2017 19:12:30 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 6335 invoked from network); 26 Jun 2017 19:05:49 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 26 Jun 2017 19:05:49 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.1) with SMTP; Mon, 26 Jun 2017 15:05:49 -0400 (EDT) Received: (qmail 11654 invoked from network); 26 Jun 2017 19:05:48 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 26 Jun 2017 19:05:48 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 0DF63EC86E7; Mon, 26 Jun 2017 12:05:48 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work From: Mark Millard In-Reply-To: <6FD738D6-F163-4BC5-8E6E-A9B9F35595CD@dsl-only.net> Date: Mon, 26 Jun 2017 12:05:47 -0700 Cc: FreeBSD-STABLE Mailing List , FreeBSD Toolchain , FreeBSD Ports , Pedro Giffuni , Gerald Pfeifer Content-Transfer-Encoding: quoted-printable Message-Id: References: <6FD738D6-F163-4BC5-8E6E-A9B9F35595CD@dsl-only.net> To: papowell@astart.com 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: Mon, 26 Jun 2017 19:12:31 -0000 Top post on one point. . . Patrick Powell papowell at astart.com wrote on Mon Jun 26 14:10:44 UTC = 2017 (He was quoting Gerald. I was also part of some earlier discussions.) > (Luckily this only hits with most -CURRENT versions of FreeBSD and > older packages only.) >=20 > Gerald Unfortunately this part is false if it is about the vm_ooffset_t and vm_pindex_t issue: stable/11/ and release/11.1.0/ also have the vm_ooffset_t and vm_pindex_t issue vs. lang/gcc* packages built by release/11.0.1/ . The issue is not limited to head (12) at this point: Installing a gcc* package built by release/11.0.1/ fails now for stable/11/ and the drafs oft release/11.1.0/ . Anyone progressing to one of those has to build the lang/gcc* of interest from source under the newer system context. (Mixing source builds and package builds is discouraged as I understand.) I'm not claiming which specific handling needs to be made. But the vm_ooffset_t and vm_pindex_t changes did not even make the UPDATING notes. Right now things look to have the worst combination for lang/gcc* when release/11.1.0/ becomes official: lang/gcc* 's break without notification or suggestion of a workaround. =3D=3D=3D Mark Millard markmi at dsl-only.net On 2017-Jun-24, at 5:55 PM, Mark Millard wrote: The following is based mostly on an extraction from a private exchange in which a question was asked and my answer was unsettling: incompatibilities within the 11.* family. I would not normally send to re but doing so was explicitly mentioned. Hopefully this example is reasonable for doing that. Aspect #0: what is broken currently (and in the future?) within the 11.* family? lang/gcc* packages built on release/11.0.1/ to not work fully on stable/11/ or on the drafts of release/11.1.0/ . (I leave releng/11.*/'s implicit.) -r313194 in head and was describied with: > Define the vm_ooffset_t and vm_pindex_t types as machine-independend. >=20 > The types are for the byte offset and page index in vm object. They > are similar to off_t, which is defined as 64bit MI integer. Using MI > definitions will allow to provide consistent MD values of vm > object-related maximum sizes. The known issue is the generation of header dependencies in the lang/gcc* builds on release/11.0.1/ that when used on stable/11/ or release/11.0.1/ generate reports like: = /usr/local/lib/gcc5/gcc/x86_64-portbld-freebsd11.0/5.4.0/include-fixed/sys= /types.h:266:9: error: '__vm_ooffset_t' does not name a type typedef __vm_ooffset_t vm_ooffset_t; ^ = /usr/local/lib/gcc5/gcc/x86_64-portbld-freebsd11.0/5.4.0/include-fixed/sys= /types.h:268:9: error: '__vm_pindex_t' does not name a type typedef __vm_pindex_t vm_pindex_t; ^ *** [CoinFactorization2.lo] Error code 1 Unfortunately UPDATING was not updated for head/'s -r313194 (2017-Feb-4) --nor for stable/11/'s -r313574 (2017-Feb-11), the MFC. (No MFC was made to stable/10/ or to release/10.3.0 as far as I found.) (These changes predate the INO64 issue in head/ . Head ends up with more issues than I'm dealing with here.) Aspect #1: what 11.* version builds the pre-built packages targeting 11.* and the apparent consequences (given the vm_ooffset_t and vm_pindex_t changes and the lang/gcc* build behavior) This is the unsettling part for pre-built packages: incompatibilities within the 11.* family for the lang/gcc* packages. = http://portsmon.freebsd.org/portoverview.py?category=3D%3Bamng&portname=3D= gcc5&wildcard=3D shows categories for builds for 8.4 9.3 10.1 10.3 11.0 head (Nothing for stable/*/ .) But the 10.3 rows show no package builds. I would guess that they start once 10.1 stops (approximately). So it may be that 11.1 will not get package builds until 11.0 stops (approximately). If so unless lang/gcc* are changed to bootstrap differently they will configure to match release/11.0.1/ and will not be compatible with the vm_ooffset_t and vm_pindex_t changes in stable/11/ and release/11.1.0/ . But as I understand updating how the lang/gcc* builds work to remove such dependencies is under investigation. I do not know any timing relative to release/11.1.0/ if my understanding is right. Until then (if I was right): Unless there are separate packages made for targeting release/11.0.1/ vs. release/11.1.0/ it is not obvious when lang/gcc* packages will be generally compatible with various folks choices about what to install as the system version within the release/11.*/ and stable/11/ family. This would likely be true even if they were built on release/11.1.0/ : then release/11.0.1/ likely would have compatibility problems. The ABI versioning does not cover the specific issues involved based on how vm_ooffset_t and vm_pindex_t were changed and what the lang/gcc* builds do relative to such changes. Yet there is incompatibility for some fairly-significant-usage ports. Aspect #2: stable/10/ and release/10.4.0/ Just covered for completeness: I do not see a MFC of -r313194 to stable/10/ : its sys/sys/types.h dates back to 2015-Oct-10. So it looks like 10.x has a permanent difference in this area: 10.x continues to get separate lang/gcc* package builds from 11.x and later. No problem for this context as far as I know. Note: To simplify I choose to not be explicit about what authors wrote what original text. If that becomes an issue, it is correctable. Blame me for any errors in the above. =3D=3D=3D Mark Millard markmi at dsl-only.net _______________________________________________ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to = "freebsd-toolchain-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Mon Jun 26 19:34: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 858B5D8F649 for ; Mon, 26 Jun 2017 19:34:04 +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 3115F76F for ; Mon, 26 Jun 2017 19:34:03 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from [10.70.7.20] (crayon2.yoonka.com [10.70.7.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v5QJXtUm037210 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 26 Jun 2017 19:33:55 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host crayon2.yoonka.com [10.70.7.20] claimed to be [10.70.7.20] Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: freebsd-ports@freebsd.org References: <2f23f3d0-dcb1-dc12-eb9f-c8966a10f5f7@toco-domains.de> From: Grzegorz Junka Message-ID: <77c15a0a-fde0-b240-803e-b369ebf0b897@gjunka.com> Date: Mon, 26 Jun 2017 19:33:50 +0000 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: <2f23f3d0-dcb1-dc12-eb9f-c8966a10f5f7@toco-domains.de> Content-Type: text/plain; charset=iso-8859-2; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB 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, 26 Jun 2017 19:34:04 -0000 On 26/06/2017 07:24, Torsten Zuehlsdorff wrote: > Aloha David, > >> 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. > > The discussions did go on for a while, but lets get more technical. > While i can understand your use case, it raises various questions: > > - How should be EOL-Software handled? For example PHP 5.6, Typo3 7, > PostgreSQL 9.2 and many more will expire long before FreeBSD 11 > expires but are still valid (or even default version) when created. > Since the versions are frozen, how should - at least- security issues > handled? > [Yes, i read that a user can switch at its own risk to another branch, > but lets assume he is very fine with the version (because i have such > customer)] > > - How should be new dependencies handled? GitLab for example sometimes > *requieres* updates of its dependencies in order to fix security issues. > > - Same as above: how should be dropped dependencies handled? In worst > case we need to maintain them for nearly 5 years, but nobody (should) > use them > > - How to resolve conflicts? I mentioned GitLab above and now realize, > that sometimes the GitLab update breaks for example www/redmine > because it depends at other versions than GitLab. > > - Where do get the fixes from? We have around 26.000 ports which needs > fixes in worst case > > - How to handle for example security issues only fixed through an > update? Which such a long time between "updates" it gets very very > hard to port/get/write patches in fast developing software. Wordpress > or Gitlab are typical examples with thousands of lines in code-changes > every update > > - How to make the customer clear, that complains about the software > (old, outdated, missing features, unresolved bugs, etc) are intentional? > > - Where to archive the distfiles? Sometimes upstream completely remove > them from everywhere they can. > > And last: how to make updates from FreeBSD version to version easier? > Many user already have problems with single major updates. From my > experiences in Windows or Ubuntu LTS usages with such or very similar > version handling: the update, even of the OS, is pushed as far away as > possible, because of the big amount of work required, since everything > needs to checked/updated/changed. > > I have a hard time to image, that is handled in another way by you. So > if you can me give more insight about your use-case i would be happy > to read it for a better understanding. > > I have various customer requiring (and paying for) very old software > (for example still PHP 5.3). So i know some of there motivations, > which boils every time down to "its to expensive to upgrade our > software" [but they don't mean expensive in money]. So maybe we can > make something happen. I understand a stable ports branch would be required by specific applications (of the FreeBSD system), e.g. data centers, bespoke private solutions, home servers. Therefore not all 26.000 ports would need to be security-patched. In fact, I believe it would be viable to determine a thousand or two of ports mostly used in those environments and commit to patch only those. Even RedHat, which is a model example, doesn't commit to maintain all packages, just a selected set of them. In the similar fashion to having Tier 1, Tier 2 and Tier 3 supported platforms for FreeBSD, we could start small with a just a handful of ports in a stable LTS (Long Term Support) branch. Develop processes around maintaining them, get some feedback about the effort of applying only security fixes, then add more ports as required or as viable from the resources point of view. How does that sound? Grzegorz From owner-freebsd-ports@freebsd.org Mon Jun 26 19:37: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 E8D50D8FD00 for ; Mon, 26 Jun 2017 19:37:32 +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 AAF9A1663 for ; Mon, 26 Jun 2017 19:37:32 +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 v5QJbVJ0030349 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 26 Jun 2017 12:37:31 -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> <1498206372.2506.1.camel@gmail.com> <666bfe8c-f27d-2c11-2a4a-07da43bb7931@FreeBSD.org> <1f37fffa-4b86-0480-d0ec-1357fc43e930@jetcafe.org> <417811ff-d808-8574-47c4-efab470af91b@FreeBSD.org> From: Dave Hayes Message-ID: Date: Mon, 26 Jun 2017 12:37:31 -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: <417811ff-d808-8574-47c4-efab470af91b@FreeBSD.org> 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: Mon, 26 Jun 2017 19:37:33 -0000 On 06/26/2017 00:27, Guido Falsi wrote: > I only partly agree with what you say, but anyway insisting on the > mailing lists with individual committers, and defending a general idea > ignoring all the details, dismissing the actual problems in the detailed > implementation that are raised by committers is not going to get much done. I agree that empirical evidence would suggest this to be true. > It has also been suggested here to write a full blown, planned and > though out proposal to be submitted via the new "FreeBSD Community > Process" [1], which could be much more effective. Perhaps. I'm more of a 'get stuff done' kind of person than an RFC writer myself, but I'd like to see someone take a shot at it. > I'd say the difficult part in such a problem is not in the idea but in > the boring details of it's implementation and long term maintenance. Actually I see the difficult part as how to solve the conflicting needs of this community. There appear to be two ideas: bleeding edge ports and stable ports. These are somewhat mutually exclusive and exacerbated by the need for security patches for the latter. I "solve" this problem by using quarterlies and running builds often, but it's not necessarily the best way. I'd personally envision a "version" knob for ports, so you could explicitly specify the exact version of software you wanted to build; kind of like the options knobs are now. The work involved in making each value of that knob actually build is probably prohibitive, but it would allow various people to focus on the versions that matter to them. This would also limit discussions like these to specific support for specific ports, but those happen anyway so at least this particular discussion would become moot. -- Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< A generous person may not have wisdom. Unlike others, this person has the means to gain wisdom. From owner-freebsd-ports@freebsd.org Mon Jun 26 19:48: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 96385D902E7 for ; Mon, 26 Jun 2017 19:48:18 +0000 (UTC) (envelope-from martin@waschbuesch.de) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7D6F9313C for ; Mon, 26 Jun 2017 19:48:18 +0000 (UTC) (envelope-from martin@waschbuesch.de) Received: by mailman.ysv.freebsd.org (Postfix) id 79EC8D902E6; Mon, 26 Jun 2017 19:48:18 +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 7993FD902E5 for ; Mon, 26 Jun 2017 19:48:18 +0000 (UTC) (envelope-from martin@waschbuesch.de) Received: from relay02.waschbuesch.it (relay02.waschbuesch.it [IPv6:2a00:cba0:0:100::2]) (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 39048313B for ; Mon, 26 Jun 2017 19:48:18 +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=To:Date:Message-Id: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:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=20QNK0i94PvHZ/GbbKG5sGhqYSiJBGoNS/9pIvABghk=; b=O8We9ccgea2XQtVavvgGfknCC1 3gI72gej/oip4xSnIZFgQnzGfMB2GNqXh9wIDxXzT3csQUHPjsqKjeRJLPYQ51C9wDYZ+uhhIxC/U 7lRLAjtHsqkjx2al/o4qhx1X5VOHGv63V24Jmuwh8H9PVKgAAKNQckpVATh/16rdSc2g=; Received: by relay02.waschbuesch.it with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim) (envelope-from ) id 1dPZzb-0001gy-7Y for ports@freebsd.org; Mon, 26 Jun 2017 19:48:15 +0000 From: =?utf-8?Q?Martin_Waschb=C3=BCsch?= Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: PRs in need of some TLC Message-Id: Date: Mon, 26 Jun 2017 21:48:14 +0200 To: ports@freebsd.org 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: Mon, 26 Jun 2017 19:48:18 -0000 Hi all, could someone have a look at these PRs (they are linked) and provide = some tender loving care? ;-) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220177 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220190 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220191 Thanks!! Martin From owner-freebsd-ports@freebsd.org Mon Jun 26 20:56: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 0E6DAD91DB5 for ; Mon, 26 Jun 2017 20:56:18 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C9A6D663A6 for ; Mon, 26 Jun 2017 20:56:17 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6EFD4209E7 for ; Mon, 26 Jun 2017 16:56:16 -0400 (EDT) Received: from web6 ([10.202.2.216]) by compute7.internal (MEProxy); Mon, 26 Jun 2017 16:56:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=skunkwerks.at; h=content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=yapGRGDTLBVcwToq3MBFHkYpb5 EJjdZKztFjN7hQVjU=; b=eMbql7Kd1IUUUXp205vQXIZW4MQKtsUv3miHxNgcZg iJh2eD+SSpwG/AV1gzgR0wey+GX6Pe69U0gtRN2uAE1+Vu4iOiXgnU0PpV1CHYw8 UOH2EqGAnIYkAiVk8IWKZSVUxvyI0GOkOIZZl9BMM9Rggm542qCizt/fkbEnQTy4 E= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=yapGRG DTLBVcwToq3MBFHkYpb5EJjdZKztFjN7hQVjU=; b=Op0XCa0wg2b2+k82bp7TME r4hUmyO2tOW4S3TsF4ZbP3YuBGgAXg6bPS1cIU5wajYp6Xa5W/xXElkPEoi8qi7j Y5tDcfe++FiPl/c6E6Ob91UqLVBpj82iY0uVwsi9aqqCrv49SjYeuqiBwOPen2mK PClSjcdcYzy1rDs8VmJrviYE4+TxQd4pTTfvcRZw2tc8A8CWvK/H8dh1MRheYIAB 6+C/35kvt4QPTvFpNUyf4hqYErj0Qi6CEuXRau6JcYagWnSkUrlhEZfl3b06Es32 1aIvYsiSX1uu0dAZGKvZaicj79HyPfTg4PjK4ymBRmHGthchixqrxK7KdlCYj3DA == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 3E4BA48004; Mon, 26 Jun 2017 16:56:16 -0400 (EDT) Message-Id: <1498510576.2460221.1022036680.14803A9C@webmail.messagingengine.com> From: Dave Cottlehuber To: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-d58a65ab In-Reply-To: <1356218856.2207512.1497961262380@mail.yahoo.com> Date: Mon, 26 Jun 2017 22:56:16 +0200 Subject: Re: perl problem References: <1356218856.2207512.1497961262380.ref@mail.yahoo.com> <1356218856.2207512.1497961262380@mail.yahoo.com> Importance: high X-Priority: 1 (High) 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, 26 Jun 2017 20:56:18 -0000 On Tue, 20 Jun 2017, at 14:21, Jeffrey Bouquet via freebsd-ports wrote: > 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 This is a very google-able error message. TLDR your perl bits need to be consistently compiled - you can't mix and match. When your perl version gets bumped you'll need to rebuild all your locally compiled packages, incl any local dependencies. The FreeBSD project 12.0-CURRENT binary packages are updated most weeks I think; what leads you to believe they are not? > and binaries fail with 'fstat' or 'stat' errors Is it possible that you have a 12.0-CURRENT from prior to the ino64 updates, and are trying to install binary packages from after that point in time? For most of the last year its been possible to get away with this, but not this time - a `uname -a` would probably confirm that. If that's the case, your 12.0-CURRENT needs to be CURRENT, so if you really need to, the 11.0 bits into an 11.0 jail and not on the host system. Background: https://lists.freebsd.org/pipermail/freebsd-current/2017-April/065687.html https://lists.freebsd.org/pipermail/freebsd-current/2017-May/066114.html https://svnweb.freebsd.org/base/head/UPDATING?view=markup&pathrev=318792#l54 Either way a bit more specific information (kernel version, your package repo, your ports tree svn revision) will help us narrow things down for you. I have tried mixing home-grown ports & FreeBSD packages . before; it always bit me in the end. If you have the build capacity, use poudriere and let it keep things consistent for you A+ Dave From owner-freebsd-ports@freebsd.org Mon Jun 26 22: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 6201FD931EC for ; Mon, 26 Jun 2017 22:34:01 +0000 (UTC) (envelope-from grog@lemis.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4B64768EE2 for ; Mon, 26 Jun 2017 22:34:01 +0000 (UTC) (envelope-from grog@lemis.com) Received: by mailman.ysv.freebsd.org (Postfix) id 4799BD931EB; Mon, 26 Jun 2017 22:34: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 4717FD931EA for ; Mon, 26 Jun 2017 22:34:01 +0000 (UTC) (envelope-from grog@lemis.com) Received: from www.lemis.com (www.lemis.com [208.86.226.86]) by mx1.freebsd.org (Postfix) with ESMTP id 24D9D68EE1 for ; Mon, 26 Jun 2017 22:34:00 +0000 (UTC) (envelope-from grog@lemis.com) Received: from eureka.lemis.com (www.lemis.com [208.86.226.86]) by www.lemis.com (Postfix) with ESMTP id EBC091B72807; Mon, 26 Jun 2017 22:33:58 +0000 (UTC) Received: by eureka.lemis.com (Postfix, from userid 1004) id B05764494B3; Tue, 27 Jun 2017 08:33:57 +1000 (AEST) Date: Tue, 27 Jun 2017 08:33:57 +1000 From: Greg 'groggy' Lehey To: Martin =?iso-8859-1?Q?Waschb=FCsch?= Cc: ports@freebsd.org Subject: Re: PRs in need of some TLC Message-ID: <20170626223357.GB4010@eureka.lemis.com> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CUfgB8w4ZwR/yMy5" Content-Disposition: inline In-Reply-To: Organization: The FreeBSD Project Phone: +61-3-5346-1370, +61-3-5309-0418 Mobile: 0401 265 606. Use only as instructed. WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 User-Agent: Mutt/1.6.1 (2016-04-27) 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, 26 Jun 2017 22:34:01 -0000 --CUfgB8w4ZwR/yMy5 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Monday, 26 June 2017 at 21:48:14 +0200, Martin Waschb=FCsch wrote: > Hi all, > > could someone have a look at these PRs (they are linked) and provide > some tender loving care? ;-) > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220177 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220190 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220191 If you say which ports are involved, you're more likely to get attention. Greg -- Sent from my desktop computer. Finger grog@FreeBSD.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA --CUfgB8w4ZwR/yMy5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAllRi9UACgkQIubykFB6QiNO0gCeNa7Vzvfej0vCGnjXEr23xwXN SvoAoJcWLrXSccs8WRuuFaMeeoVH7XF2 =N5aG -----END PGP SIGNATURE----- --CUfgB8w4ZwR/yMy5-- From owner-freebsd-ports@freebsd.org Mon Jun 26 22:56: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 5CE34D93991 for ; Mon, 26 Jun 2017 22:56:02 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4ACD76AE3C for ; Mon, 26 Jun 2017 22:56:02 +0000 (UTC) (envelope-from lists@opsec.eu) Received: by mailman.ysv.freebsd.org (Postfix) id 4A0F4D9398F; Mon, 26 Jun 2017 22:56: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 49A51D9398E for ; Mon, 26 Jun 2017 22:56:02 +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 135B16AE3B for ; Mon, 26 Jun 2017 22:56:02 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dPcvN-000HOD-RZ; Tue, 27 Jun 2017 00:56:05 +0200 Date: Tue, 27 Jun 2017 00:56:05 +0200 From: Kurt Jaeger To: Martin =?iso-8859-1?Q?Waschb=FCsch?= Cc: ports@freebsd.org Subject: Re: PRs in need of some TLC Message-ID: <20170626225605.GA65214@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: Mon, 26 Jun 2017 22:56:02 -0000 Hi! > could someone have a look at these PRs (they are linked) and provide some tender loving care? ;-) > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220177 This is missing a patch, isn't it ? > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220190 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220191 If possible, provide a link to the changelog ? -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-ports@freebsd.org Tue Jun 27 02:35: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 4EBD8D9ABD3 for ; Tue, 27 Jun 2017 02:35:16 +0000 (UTC) (envelope-from baristandpadang@kemenperin.go.id) Received: from mailgate.kemenperin.go.id (mail.kemenperin.go.id [202.47.80.99]) (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 DE5BC755B1 for ; Tue, 27 Jun 2017 02:35:15 +0000 (UTC) (envelope-from baristandpadang@kemenperin.go.id) Received: from localhost (localhost [127.0.0.1]) by mailgate.kemenperin.go.id (Postfix) with ESMTP id CE9C43041BD for ; Tue, 27 Jun 2017 09:35:11 +0700 (WIB) Received: from mailgate.kemenperin.go.id ([127.0.0.1]) by localhost (mailgate.kemenperin.go.id [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id fSCuC1wBOK0A for ; Tue, 27 Jun 2017 09:35:11 +0700 (WIB) Received: from localhost (localhost [127.0.0.1]) by mailgate.kemenperin.go.id (Postfix) with ESMTP id 5C9D83041FD for ; Tue, 27 Jun 2017 09:35:11 +0700 (WIB) DKIM-Filter: OpenDKIM Filter v2.8.4 mailgate.kemenperin.go.id 5C9D83041FD DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kemenperin.go.id; s=3298A942-BBC6-11E3-B333-483736368EC2; t=1498530911; bh=BR9a6w4maQOtAPzwFR0/j/F3sFu5Pes7gNerB9b49zk=; h=Content-Type:MIME-Version:Subject:To:From:Date:Reply-To: Message-Id; b=JjwMxpu68vtcTSqUOM1pengGqpyxAraaluaRE73qu9BRjDHMDI9kudC0+uqTyjVu/ S/DUfKlSYnz89ng/ADeThbNIznrMN/94OQQY72F0YiMMUZiXlSP4Umhj99hhE2wU4X pi3k9n+8raiWNG85bjLqjuZ3bkSo2Sv+ecZetPXk= X-Virus-Scanned: amavisd-new at kemenperin.go.id Received: from mailgate.kemenperin.go.id ([127.0.0.1]) by localhost (mailgate.kemenperin.go.id [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id tMylHUuB7nWR for ; Tue, 27 Jun 2017 09:35:11 +0700 (WIB) Received: from [10.200.0.1] (unknown [88.103.120.177]) by mailgate.kemenperin.go.id (Postfix) with ESMTPSA id 50019304088 for ; Tue, 27 Jun 2017 09:35:03 +0700 (WIB) MIME-Version: 1.0 Subject: E-mail account blacklisted To: freebsd-ports@freebsd.org From: "Technical Support" Date: Tue, 27 Jun 2017 04:34:59 +0200 Reply-To: marmar@yahoo.com Message-Id: <20170627023510.50019304088@mailgate.kemenperin.go.id> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Description: Mail message body 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, 27 Jun 2017 02:35:16 -0000 Your Account Has Been Blacklisted! Your account has been Blacklisted due to system error CODE: REF-6192-041= 7 . You will not be able to send or receive emails from certain IP location= s or Email Service Providers. If you would like to continue using your emai= l address, please re-validate your mailbox = Verify Your Account Now YOU WILL COMPLETELY LOSE YOUR EMAIL ADDRESS IF NO ACTION IS TAKEN. Sincerely, Mail Team! Inc =A92017 All Rights Reserved From owner-freebsd-ports@freebsd.org Tue Jun 27 06:47: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 23B71DA28FD for ; Tue, 27 Jun 2017 06:47:18 +0000 (UTC) (envelope-from nicolas@welcome.critsend.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 096D97E262 for ; Tue, 27 Jun 2017 06:47:18 +0000 (UTC) (envelope-from nicolas@welcome.critsend.com) Received: by mailman.ysv.freebsd.org (Postfix) id 08E64DA28FC; Tue, 27 Jun 2017 06:47:18 +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 088CADA28FB for ; Tue, 27 Jun 2017 06:47:18 +0000 (UTC) (envelope-from nicolas@welcome.critsend.com) Received: from sender3.welcome.critsend.com (sender3.welcome.critsend.com [212.83.152.244]) (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 B21FF7E261 for ; Tue, 27 Jun 2017 06:47:17 +0000 (UTC) (envelope-from nicolas@welcome.critsend.com) Received: from sender1.welcome.critsend.com (localhost.localdomain [127.0.0.1]) by sender1.welcome.critsend.com (Postfix) with ESMTP id 225639BA86E for ; Tue, 27 Jun 2017 06:45:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=messaging-master.net; i=@messaging-master.net; q=dns/txt; s=critsend2; t=1498545914; h=X-Critsend-Id : X-Event-Ack : From : To : Subject : MIME-Version : Content-Transfer-Encoding : X-Priority : Message-ID : List-Unsubscribe : Precedence : Content-Type; bh=ZHWZBIDRCvp2R3ARVF27+gNU8+98XnlWMSlCGv0w1bo=; b=mSsk4aZDNSZAakYX+M71nQhHCep9u73Nk3PQ6nvrWgay4CRNgJsIgGW47OPsmQ9DpaL+05d63HmKnmwXEfHhN3/y0LfpK+MH+Jylae/WBcW1D7mlm1YeOHOtrsdXENMWATUDV168+tVqRN59GNsNXlT8me6mJIaylUBQlK1F4ms= X-Critsend-Id: 1cdc66d488787fe99830d7e52381d3 X-Event-Ack: Yes From: "Apple" To: ports@FreeBSD.org Subject: Your Account Has Been Disabled X-Priority: 3 Message-ID: <4+paav3s6rblbdadcg4edrfarr5gnpzd3dspewawtja67l53wwzpz4celbk7qn3rzrqf2wjxthkapq7yaczr6ekdvgj7xk2p4t3lmi5u7ik4akww6r4kwmj7bxoof3mlfbm3k6vgxoe3l2qwlomiopebpdzqsie===+1196438@welcome.critsend.com> Precedence: bulk Date: Tue, 27 Jun 2017 06:45:14 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jun 2017 06:47:18 -0000 From owner-freebsd-ports@freebsd.org Tue Jun 27 07:37: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 213B5DA3884 for ; Tue, 27 Jun 2017 07:37:38 +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 ED77E7FA52 for ; Tue, 27 Jun 2017 07:37:36 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:63222] helo=localhost) by dnvrco-omsmta03 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 61/E4-01815-93B02595; Tue, 27 Jun 2017 07:37:30 +0000 Date: Tue, 27 Jun 2017 07:37:22 +0000 Message-ID: <61.E4.01815.93B02595@dnvrco-omsmta03> 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> <8948545b-5269-8a0e-3f92-9dfd02f227c1@gjunka.com> <310d8cf4-3549-aca7-5666-b3496707917e@heuristicsystems.com.au> Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version X-RR-Connecting-IP: 107.14.64.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: Tue, 27 Jun 2017 07:37:38 -0000 from Dewayne Geraghty: > Synth is very good. It builds upon pkg and is way less complicated that > poudriere. > Unfortunately John Marino was unceremoniously removed from committing to > FreeBSD, and its is uncertain whether he'll continue to support synth on > FreeBSD. (He supports DragonflyBSD. :) I remember reading about this falling-out. Are others in FreeBSD ports taking over and continuing support and updates for synth? Does John Marino still support NetBSD pkgsrc with synth? It seems NetBSD pkgsrc people are not catching on, preferring to stay with the clumsy pkgsrc tools: creatures of habit, reluctant to change. I tried the live/installation DragonFlyBSD USB-stick image, but it had problems: no Internet access, drivers missing or nonworking, and my last try didn't boot. Also it couldn't (previous tries) mount any FreeBSD or NetBSD partition, and FreeBSD and NetBSD couldn't mount/read the DragonFlyBSD USB stick even with UFS as opposed to Hammer file system. Tom From owner-freebsd-ports@freebsd.org Tue Jun 27 07:46: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 B5E93DA3B53 for ; Tue, 27 Jun 2017 07:46:53 +0000 (UTC) (envelope-from martin@waschbuesch.de) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 91ACF7FF3F for ; Tue, 27 Jun 2017 07:46:53 +0000 (UTC) (envelope-from martin@waschbuesch.de) Received: by mailman.ysv.freebsd.org (Postfix) id 91162DA3B52; Tue, 27 Jun 2017 07:46: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 90B92DA3B50 for ; Tue, 27 Jun 2017 07:46:53 +0000 (UTC) (envelope-from martin@waschbuesch.de) Received: from relay02.waschbuesch.it (relay02.waschbuesch.it [IPv6:2a00:cba0:0:100::2]) (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 52C777FF3E for ; Tue, 27 Jun 2017 07:46:53 +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=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To: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=e1GZVdR2vHLWQlVJ6NwVbYbi9YWq9fJHvgER5WFaoRw=; b=E/aky6Ic8ZhYJRzeETVFIHlKD sY0Knxf8rONJ9pJB2s+oM/e0Rfbz7SxE1VKjz2m3vS5TH+3yWIUSEfm4W9pzd/yLbhKAdGMHes2cJ hI4HL21IcZ2FZczCOgfIJq09LrlZ0xDlITa8Ovdgsl2SPPfIV9rEixjp2qyh9nUkLAK98=; Received: by relay02.waschbuesch.it with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim) (envelope-from ) id 1dPlCz-0009Qf-6Y; Tue, 27 Jun 2017 07:46:49 +0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: PRs in need of some TLC From: =?utf-8?Q?Martin_Waschb=C3=BCsch?= In-Reply-To: <20170626225605.GA65214@home.opsec.eu> Date: Tue, 27 Jun 2017 09:46:48 +0200 Cc: Kurt Jaeger Content-Transfer-Encoding: quoted-printable Message-Id: References: <20170626225605.GA65214@home.opsec.eu> To: ports@freebsd.org 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: Tue, 27 Jun 2017 07:46:53 -0000 > Am 27.06.2017 um 00:56 schrieb Kurt Jaeger : >=20 > Hi! >=20 >> could someone have a look at these PRs (they are linked) and provide = some tender loving care? ;-) >>=20 >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220177 >=20 > This is missing a patch, isn't it ? You=E2=80=99re right. I am sorry. But it seems you created one. Thanks = for that. >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220190 >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220191 >=20 > If possible, provide a link to the changelog ? I added links to the respective Changelog. Thanks, Martin= From owner-freebsd-ports@freebsd.org Tue Jun 27 07: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 7CC2FDA3BEE for ; Tue, 27 Jun 2017 07:47:50 +0000 (UTC) (envelope-from martin@waschbuesch.de) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6263D80007 for ; Tue, 27 Jun 2017 07:47:50 +0000 (UTC) (envelope-from martin@waschbuesch.de) Received: by mailman.ysv.freebsd.org (Postfix) id 61BF3DA3BEC; Tue, 27 Jun 2017 07:47: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 614D8DA3BEB for ; Tue, 27 Jun 2017 07:47:50 +0000 (UTC) (envelope-from martin@waschbuesch.de) Received: from relay02.waschbuesch.it (relay02.waschbuesch.it [IPv6:2a00:cba0:0:100::2]) (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 21BAB80006; Tue, 27 Jun 2017 07:47:50 +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=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To: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=j1AxY+Tht32gUA7Ur+f2vQ03pmjANok/6ykqZ9gYwjc=; b=Qnf5oUK2O//UOwIpjg+K69RQ/ pXHolwR2kut474b8H/qDr6iILKfs4nvV0rwSUFkPf5KzUFBztHAhFhtoPOTAw3bVfBxLiB86BH7DH B1bumPoWvVQf2KcUChht2tfoO9VEen78yU1ySRif6pgvzvJ7MzOpS+O+wyUOsZmOK/fEc=; Received: by relay02.waschbuesch.it with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim) (envelope-from ) id 1dPlDw-0009Qf-7f; Tue, 27 Jun 2017 07:47:48 +0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: PRs in need of some TLC From: =?utf-8?Q?Martin_Waschb=C3=BCsch?= In-Reply-To: <20170626223357.GB4010@eureka.lemis.com> Date: Tue, 27 Jun 2017 09:47:48 +0200 Cc: Greg 'groggy' Lehey Content-Transfer-Encoding: quoted-printable Message-Id: References: <20170626223357.GB4010@eureka.lemis.com> To: ports@freebsd.org 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: Tue, 27 Jun 2017 07:47:50 -0000 > Am 27.06.2017 um 00:33 schrieb Greg 'groggy' Lehey : >=20 > On Monday, 26 June 2017 at 21:48:14 +0200, Martin Waschb=C3=BCsch = wrote: >> Hi all, >>=20 >> could someone have a look at these PRs (they are linked) and provide >> some tender loving care? ;-) >>=20 >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220177 >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220190 >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220191 >=20 > If you say which ports are involved, you're more likely to get > attention. Good point, Greg. Thanks. I=E2=80=99ll keep it in mind for next time.= From owner-freebsd-ports@freebsd.org Tue Jun 27 10:08: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 53D1CDA63A7 for ; Tue, 27 Jun 2017 10:08:36 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E51328438A for ; Tue, 27 Jun 2017 10:08:34 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (pD9FA95B6.dip0.t-ipconnect.de [217.250.149.182]) (authenticated bits=128) by land.berklix.org (8.15.2/8.15.2) with ESMTPSA id v5RA85Jm009530 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 27 Jun 2017 10:08:09 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id v5RA8Srt025731 for ; Tue, 27 Jun 2017 12:08:29 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id v5RA8GUf099489 for ; Tue, 27 Jun 2017 12:08:28 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201706271008.v5RA8GUf099489@fire.js.berklix.net> to: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ In-reply-to: Your message "Tue, 27 Jun 2017 07:37:22 -0000." <61.E4.01815.93B02595@dnvrco-omsmta03> Date: Tue, 27 Jun 2017 12:08:16 +0200 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, 27 Jun 2017 10:08:36 -0000 "Thomas Mueller" wrote: > from Dewayne Geraghty: > > > Synth is very good. It builds upon pkg and is way less complicated that > > poudriere. I dont know the relative dependencies counts for both synth & poudriere, but I suspect synth is bigger ? ( I have a messed up current here where loads of ports break, I tried to build synth to then recover other ports, but synth broke deep, building some gcc, & I have a working poudriere.) If one has a good stable platform, then a nice maintainer that does chroot/jail elegantly with lots of features is probably attractive, & dependency count not a worry. But if one stands on a broken system & needs to recover, some simple stock cc & sh tool/procedure with no dependencies is attractive, even if one has to coble something ones self. Cheers, Julian -- Julian Stacey, Computer Consultant, BSD Linux Unix Systems Engineer Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable. http://berklix.eu/brexit/#700k_stolen_votes From owner-freebsd-ports@freebsd.org Tue Jun 27 10:09: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 34B20DA64AB for ; Tue, 27 Jun 2017 10:09:30 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1FB608457F for ; Tue, 27 Jun 2017 10:09:30 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1F1EADA64A9; Tue, 27 Jun 2017 10:09: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 1ECE4DA64A8 for ; Tue, 27 Jun 2017 10:09:30 +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 10DF28457E for ; Tue, 27 Jun 2017 10:09:30 +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 v5RA9T7U041983 for ; Tue, 27 Jun 2017 10:09:29 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v5RA9THR041982; Tue, 27 Jun 2017 10:09:29 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201706271009.v5RA9THR041982@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: Tue, 27 Jun 2017 10:09:29 +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: Tue, 27 Jun 2017 10:09:30 -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 ------------------------------------------------+-----------------+------------ math/giacxcas | 1.2.2-57 | 1.2.3-53 ------------------------------------------------+-----------------+------------ 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 Tue Jun 27 11:06: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 6BCD3DA76D4 for ; Tue, 27 Jun 2017 11:06:34 +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 588F01869 for ; Tue, 27 Jun 2017 11:06:34 +0000 (UTC) (envelope-from lists@opsec.eu) Received: by mailman.ysv.freebsd.org (Postfix) id 57C93DA76D3; Tue, 27 Jun 2017 11:06:34 +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 5737FDA76D2 for ; Tue, 27 Jun 2017 11:06:34 +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 1E4801868 for ; Tue, 27 Jun 2017 11:06:34 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dPoKH-000JJt-FE; Tue, 27 Jun 2017 13:06:33 +0200 Date: Tue, 27 Jun 2017 13:06:33 +0200 From: Kurt Jaeger To: Martin =?iso-8859-1?Q?Waschb=FCsch?= Cc: ports@freebsd.org Subject: Re: PRs in need of some TLC Message-ID: <20170627110633.GB65214@home.opsec.eu> References: <20170626225605.GA65214@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jun 2017 11:06:34 -0000 Hi! > >> could someone have a look at these PRs (they are linked) and provide some tender loving care? ;-) > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220177 > > > > This is missing a patch, isn't it ? > You're right. I am sorry. But it seems you created one. Thanks for that. Yes. I'm no user of that port, so: Can you test if the patch works and add it to the PR ? > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220190 > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220191 > > > > If possible, provide a link to the changelog ? > > I added links to the respective Changelog. Thanks! -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-ports@freebsd.org Tue Jun 27 13:26:09 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 43EC9DAA976 for ; Tue, 27 Jun 2017 13:26:09 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm11-vm5.access.bullet.mail.bf1.yahoo.com (nm11-vm5.access.bullet.mail.bf1.yahoo.com [216.109.114.228]) (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 F0F2166232 for ; Tue, 27 Jun 2017 13:26:08 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1498569856; bh=ImQx8nkoYTpIJUbSi7KeB6u27473gr+mFu8Y5gopONw=; h=From:To:Cc:Subject:Date:References:In-Reply-To:From:Subject; b=MBNBa0Pab+bDGMSE6ZlNiC5Lunl0Lp1zJTBWf6CjYWw8roP7IsaGwgStze34UPIHTskeRd8a7k6UJNKviu8mgxGGpuO/1h77pDAnTpXBDI9g/5usGD1OslceXxgq3X6a/TszpCTyiS6VWxIMnH7uLkEDqn9wiLBfx1nQUtB756g= Received: from [66.196.81.162] by nm11.access.bullet.mail.bf1.yahoo.com with NNFMP; 27 Jun 2017 13:24:16 -0000 Received: from [98.139.244.51] by tm8.access.bullet.mail.bf1.yahoo.com with NNFMP; 27 Jun 2017 13:24:16 -0000 Received: from [127.0.0.1] by smtp113.sbc.mail.bf1.yahoo.com with NNFMP; 27 Jun 2017 13:24:16 -0000 X-Yahoo-Newman-Id: 755098.8223.bm@smtp113.sbc.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: LkBc7UgVM1mTAl0xr1febCc7ogdLigmsuTzNWohn1p4Kauv jSsc9A3G7ENuX4VZCkBQLIaxI5GtoETUI3F2Oly8ubpd2_FcFSU7XtcSfN7F mOtiMNSkcL1W3ErBgGbKWAtgE3zfpNq7kYB52N_wBPFHQjM8MEpKkzZLqzJh 6B3WYoX4slkbaRvEwkfJJdb8C0g_pwXbBiFr7fE6OpK4fGLMqkpZQPfejjyP bwToF6IaowAZYcahDaurScM_pTXTKwF0LkxTw0NznIfzSPy9wZlbJjqCeOYR T3T7RpAO0McESM.ab82rVwTHJxu3r506TI51.hBPlEW4v9gSCcZquY8fnEgG Tk2LiKxJ.VcttJes3JQBjlx6ZesT6zA9eJc1vftSaT0g32A1z0tWxXrKOxwu SmUnx8945AyK5xnBXPdSGjfpttPc4IXA3s2BO6Pr84xM.TP__II3xVQ.9mjG LQzuzXYekTVpLKrPGReFQJ5Nirvj_qUdYp69zTPKPKD9lS7lA749wLUZIwML B5D69TpWCRFt.JxZjf7u4.rL51B_Edff.rKIWNP.HW2oBrINo4ZB3Uw-- X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: Grzegorz Junka Cc: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Date: Tue, 27 Jun 2017 09:24:31 -0400 Message-ID: References: <2f23f3d0-dcb1-dc12-eb9f-c8966a10f5f7@toco-domains.de> <77c15a0a-fde0-b240-803e-b369ebf0b897@gjunka.com> In-Reply-To: <77c15a0a-fde0-b240-803e-b369ebf0b897@gjunka.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: Tue, 27 Jun 2017 13:26:09 -0000 [Default] On Mon, 26 Jun 2017 19:33:50 +0000, Grzegorz Junka wrote: >we could >start small with a just a handful of ports in a stable LTS (Long Term >Support) branch. Develop processes around maintaining them, get some >feedback about the effort of applying only security fixes, then add more >ports as required or as viable from the resources point of view. How >does that sound? It sounds excellent, at least to me. How many platform roles are seen as fbsd's metier? Firewall? Already handled. Specialist workstations such as sound/video editing? Maybe. I don't know enough about that to have an opinion. Servers. No question. That's always been freebsd's best thing. The number of ports to build a server-of-all-work is not large. Unnecessarily complex and a source of uncontrolled errors, yes, but not really *large* qua large. From owner-freebsd-ports@freebsd.org Tue Jun 27 15:39:05 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 5203DD883B2 for ; Tue, 27 Jun 2017 15:39:05 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001: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 1CCA16EE88 for ; Tue, 27 Jun 2017 15:39:05 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by mail-io0-x234.google.com with SMTP id r36so19863914ioi.1 for ; Tue, 27 Jun 2017 08:39:05 -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=Uev4vb1OZy1x9gXnIn2hL8p1ps8WPeaS1H5xh9cX4a4=; b=tcrMv7Si8dn/ItRnd/eB1bEcEYqBMAMzMJZhAm+ixSUos3AofncQNLGhXqFj00gfVq pCN4J5fsOqVcNBlOe1j9oQ+y3LL7N78TzBykNg4dbNKsqhZTsHWLWB6rorDA8nMKBXsg A3MZ0+6quDNINl7+XkRBPbBwlG/IuOE+P/jfP5UQ91Wztqfo9N3W01C7yu98jANQbaGj fe9d7PdOFG8TPz7l+QwTXDGiuu2QJfs6F13Y0+dyUyCHDGbSxDt66BdVySbNCrsU16dS pES0fbuv0fMS+5Bh7AhH1oyEic2v+oKccQuom/TvekxfDfvnTcOYC1qudNe24e3rJfGe VQfw== 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=Uev4vb1OZy1x9gXnIn2hL8p1ps8WPeaS1H5xh9cX4a4=; b=Z7ZnD4dPeWdK/JX+rvqgWDoViQuTmsTAw9F+vLxkx4HPqMRZmqXI6l9zD3gVZFPc7l /qM4Ywsok90gufSwesNvQdsGjzGIuAzPfh+uLpPHBonq/Gm/0sm2Z4p6ZtChCiDssgUS ZHv3ddJnbURZuZdUJL3lgz5Pegt8sezyeaMyN+xP162JfD1wIFSc3Mjin4z6p3wuojUt xRX3azO7BX7/Ff5kW3o0MiZOPUP3Hma6awb7VWVL3xL9LRh9cxexkUmRyBRIBID1DEqH DjEf8NBtgaLwjPx+RiFYPp5ol6U1bdMrZFKLYQqOJl5c8N6n/HpGdg8WiH5swXOJB7xf Z8mw== X-Gm-Message-State: AKS2vOyKecUM9e2iiZrmoTk4L3W5pKhCU3ZHuk/8teeXCLaAjHO6lxYT zsK9saHRjBkPsEgrL8wVR9/VXnrUGQ== X-Received: by 10.107.59.84 with SMTP id i81mr6538726ioa.72.1498577944406; Tue, 27 Jun 2017 08:39:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.41.73 with HTTP; Tue, 27 Jun 2017 08:39:04 -0700 (PDT) From: Aryeh Friedman Date: Tue, 27 Jun 2017 11:39:04 -0400 Message-ID: Subject: best way to handle GCC version detection To: FreeBSD Ports ML 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: Tue, 27 Jun 2017 15:39:05 -0000 I have port I maintain that compiles fine under GCC 5 (or lower) but barfs on GCC 6. A small modification will make it compile under 6 but the very same modification makes it incompatible with 5. What is the best way to handle this and still allow USE_GCC=any ? -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-ports@freebsd.org Tue Jun 27 16:12: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 CA3F6D8912B for ; Tue, 27 Jun 2017 16:12:00 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90D51703C2 for ; Tue, 27 Jun 2017 16:12:00 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [IPv6:2001:470:7a58::6d32:3606:9326:9078] (unknown [IPv6:2001:470:7a58:0:6d32:3606:9326:9078]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 03054325C7; Tue, 27 Jun 2017 18:11:56 +0200 (CEST) From: Dimitry Andric Message-Id: <507D01C5-ADE6-4078-A985-954598C0F363@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_B71976AC-EBD7-4126-9A27-6D42225A029A"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: best way to handle GCC version detection Date: Tue, 27 Jun 2017 18:11:49 +0200 In-Reply-To: Cc: FreeBSD Ports ML To: Aryeh Friedman References: 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: Tue, 27 Jun 2017 16:12:00 -0000 --Apple-Mail=_B71976AC-EBD7-4126-9A27-6D42225A029A Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 27 Jun 2017, at 17:39, Aryeh Friedman wrote: > > I have port I maintain that compiles fine under GCC 5 (or lower) but barfs > on GCC 6. A small modification will make it compile under 6 but the very > same modification makes it incompatible with 5. What is the best way to > handle this and still allow USE_GCC=any ? Something like: #if __GNUC__ <= 5 ...foo... #else ...bar... #endif could maybe work? -Dimitry --Apple-Mail=_B71976AC-EBD7-4126-9A27-6D42225A029A 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----- Version: GnuPG/MacGPG2 v2.0.30 iEYEARECAAYFAllSg8wACgkQsF6jCi4glqOEZACg097l+F64vVRb+2mBMhqplT56 0eQAn02R+eOfFkyMmhLVH6bfL20NHBay =3DB8 -----END PGP SIGNATURE----- --Apple-Mail=_B71976AC-EBD7-4126-9A27-6D42225A029A-- From owner-freebsd-ports@freebsd.org Tue Jun 27 16:29: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 927A0D89FD8 for ; Tue, 27 Jun 2017 16:29:32 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from anny.lostinspace.de (anny.lostinspace.de [IPv6:2001:608:a02::33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5850F72CEF for ; Tue, 27 Jun 2017 16:29:32 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from server.idefix.lan (aftr-185-17-205-21.dynamic.mnet-online.de [185.17.205.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: idefix@fechner.net) by anny.lostinspace.de (Postfix) with ESMTPSA id 71CB9C0A4B0 for ; Tue, 27 Jun 2017 18:29:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=fechner.net; s=default; t=1498580970; bh=Z5dV0WcuFKssOgDiyqV2QdZN85QSaWHvRSvxK3+JcRY=; h=To:From:Subject:Date; b=S7KaB3Ihl88oqDFqFYf3q9lOvRwGgk/TjXcj2j1Yn9En0mdWol2gzTb1uIhIj8GLl J4GsxWQ9iSsQ5WmMcK1xTiVRlea5qkR3hh5epKXyyWQIeytuv/1V3Jb4KtnjpTKgnR 8EZ05G6vM8sLoaKSvhWGBwYh993uVsZnyNKR6rAw= Received: from [192.168.0.151] (aftr-185-17-205-21.dynamic.mnet-online.de [185.17.205.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by server.idefix.lan (Postfix) with ESMTPSA id 0339DCCCA64 for ; Tue, 27 Jun 2017 18:29:29 +0200 (CEST) To: FreeBSD Ports ML From: Matthias Fechner Subject: Should a package restart on upgrade itself Message-ID: Date: Tue, 27 Jun 2017 18:29:24 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 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: Tue, 27 Jun 2017 16:29:32 -0000 Dear all, it is always a pain if pkg upgrade a lot of packages to restart all services to make sure update/security fixes are applied to all running services. Is there an option in pkg that it restart services automatically or is it OK if I would add a post-install script to the packages (I maintain) that will include a "service foo restart"? What is best practice here? Thanks Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook From owner-freebsd-ports@freebsd.org Tue Jun 27 16:32: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 E8E2FD8A211 for ; Tue, 27 Jun 2017 16:32:32 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.shmhost.net (unknown [IPv6:2a01:4f8:a0:51d6::108: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 B461473153 for ; Tue, 27 Jun 2017 16:32:32 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.homeoffice.local (ipservice-092-208-063-038.092.208.pools.vodafone-ip.de [92.208.63.38]) by host64.shmhost.net (Postfix) with ESMTPSA id A2CAB84151; Tue, 27 Jun 2017 18:32:21 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Should a package restart on upgrade itself From: Franco Fichtner In-Reply-To: Date: Tue, 27 Jun 2017 18:32:22 +0200 Cc: FreeBSD Ports ML Content-Transfer-Encoding: 7bit Message-Id: References: To: Matthias Fechner X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at host64.shmhost.net X-Virus-Status: Clean 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, 27 Jun 2017 16:32:33 -0000 Hi Matthias, As far as I know, pkg package scripts' runaway processes are reaped since a few versions, so you can't restart from there anymore. Maybe there is a way to detach correctly, I don't know. Cheers, Franco > On 27. Jun 2017, at 6:29 PM, Matthias Fechner wrote: > > Dear all, > > it is always a pain if pkg upgrade a lot of packages to restart all > services to make sure update/security fixes are applied to all running > services. > > Is there an option in pkg that it restart services automatically or is > it OK if I would add a post-install script to the packages (I maintain) > that will include a "service foo restart"? > > What is best practice here? > > > Thanks > Matthias > > -- > > "Programming today is a race between software engineers striving to > build bigger and better idiot-proof programs, and the universe trying to > produce bigger and better idiots. So far, the universe is winning." -- > Rich Cook > > _______________________________________________ > 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 27 16:35: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 76A58D8A29A for ; Tue, 27 Jun 2017 16:35:03 +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 54BCA73228; Tue, 27 Jun 2017 16:35:03 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 9B162A4D3; Tue, 27 Jun 2017 16:35:02 +0000 (UTC) Date: Tue, 27 Jun 2017 18:35:02 +0200 From: Baptiste Daroussin To: Matthias Fechner Cc: FreeBSD Ports ML Subject: Re: Should a package restart on upgrade itself Message-ID: <20170627163502.u2m4trqccbkri63j@ivaldir.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3x77s4hpnh5fjcnu" 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: Tue, 27 Jun 2017 16:35:03 -0000 --3x77s4hpnh5fjcnu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 27, 2017 at 06:29:24PM +0200, Matthias Fechner wrote: > Dear all, >=20 > it is always a pain if pkg upgrade a lot of packages to restart all > services to make sure update/security fixes are applied to all running > services. >=20 > Is there an option in pkg that it restart services automatically or is > it OK if I would add a post-install script to the packages (I maintain) > that will include a "service foo restart"? >=20 > What is best practice here? >=20 A package self upgrading might cause issues: plugins not yet updated (hi dovecot), or services requiring an upgrade procedure. So activating a self restart of the service by default is a bad idea. service -R command can simplify the procedure for the admin given it restar= ts all services already started. Another option is to activate an option of pkg(8) off by default: HANDLE_RC_SCRIPTS =3D true; in /usr/local/etc/pkg.conf which will automatically restart the services on upgrade. In the futur it is planed to move this into a trigger (executed at the end = of the entire upgrade process) which will solve the "dovecot" issue, but not t= he one where upgrading requires a procedure. Best regards, Bapt --3x77s4hpnh5fjcnu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAllSiTMACgkQY4mL3PG3 Plr+BRAAsBQvA2X/sKgET7C7Z8zeV6SRRuW7ssJ+W7zcvjGVyiyFq5co3bMWxP6J DtbLr9eTag9620Duic/e8S68cJWkb/47l2QoP1SOFQEkIaxAslNOcsnHsZBHUi7M IcM2ZyU/nOipo9xXA8754M5lNoyougkyegp4pNmyNzgMpNw7vmgMAlgJgPf0WzgQ THhNlWIbRI53NnECrHz/EpvCY3A6tKuYDtrCFDGz1fxysufCXXTGMOV56ohZOVcy s/UwhkZFBT+T6tRYDMlrUw2BFoSg73KlbJkD6juKX4xjOG3w6h9/bNmqOw3UJM27 qXMQqFJh61XDhDH5P+qiJ7FCvdkuHK18+EbI3H4AxrGcCNqLG59RLEXUufrVeKrN VG8TGLXgqi5LvjvXA3cTAw4veUEZ38p5eNbZSwyHJxl5UITtuEjW5vOWYYnBkLVO 6UkbqnYWykJUB4aZvVA8z6l9jPotU3W2x4qdLzZbcXMYnTYSiALYwyto5UA1Bcoz kedL8MGHiLk3EdNenTmGhkeCUg7u8pX7vm4nNqqUNeiqNLxrbKcshjKDatIUg0HP Lv5IObWrm7XiHdGkKAlLinhqj0jP+9vT1SEj/IFOH94mQRa5awEirVTZuR1LjfKZ Luaqrg1YatFI960IS0OkCaN93SM8X2vYSS/EfuvHKJH4Owm1j0Y= =u446 -----END PGP SIGNATURE----- --3x77s4hpnh5fjcnu-- From owner-freebsd-ports@freebsd.org Tue Jun 27 16:50: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 0C0ACD8A945 for ; Tue, 27 Jun 2017 16:50:38 +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 C6155739E0 for ; Tue, 27 Jun 2017 16:50:36 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mx.irealone.hr (Postfix, from userid 58) id D6F6889E7; Tue, 27 Jun 2017 18:50: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 4701989E3 for ; Tue, 27 Jun 2017 18:50:26 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 27 Jun 2017 18:50:26 +0200 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: Should a package restart on upgrade itself Organization: Acheron Media In-Reply-To: <20170627163502.u2m4trqccbkri63j@ivaldir.net> References: <20170627163502.u2m4trqccbkri63j@ivaldir.net> Message-ID: <4aad148bce4cfc626dea0d31bd62be41@acheronmedia.com> 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: Tue, 27 Jun 2017 16:50:38 -0000 On 2017-06-27 18:35, Baptiste Daroussin wrote: > > In the futur it is planed to move this into a trigger (executed at the > end of > the entire upgrade process) which will solve the "dovecot" issue, but > not the > one where upgrading requires a procedure. Will this cover libraries as well? Eg. Libre/Open SSL upgrades, restart all services that depend on it? Meanwhile, there's "lsop": https://www.freshports.org/sysutils/lsop/ -- Vlad K. From owner-freebsd-ports@freebsd.org Tue Jun 27 16:54:47 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 1D3CBD8ABCE for ; Tue, 27 Jun 2017 16:54:47 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C614873E07 for ; Tue, 27 Jun 2017 16:54:45 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v5RGsXhL029860; Tue, 27 Jun 2017 16:54:33 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v5RGsXX5029859; Tue, 27 Jun 2017 09:54:33 -0700 (PDT) (envelope-from david) Date: Tue, 27 Jun 2017 09:54:33 -0700 From: David Wolfskill To: Matthias Fechner Cc: FreeBSD Ports ML Subject: Re: Should a package restart on upgrade itself Message-ID: <20170627165433.GR1241@albert.catwhisker.org> Reply-To: freebsd-ports@freebsd.org References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Wjspmq6N72sNzV6w" 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: Tue, 27 Jun 2017 16:54:47 -0000 --Wjspmq6N72sNzV6w Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 27, 2017 at 06:29:24PM +0200, Matthias Fechner wrote: > Dear all, >=20 > it is always a pain if pkg upgrade a lot of packages to restart all > services to make sure update/security fixes are applied to all running > services. >=20 > Is there an option in pkg that it restart services automatically or is > it OK if I would add a post-install script to the packages (I maintain) > that will include a "service foo restart"? >=20 > What is best practice here? > .... I do not claim that this is "best practice." But what I do, during my weekly updates of my "production" systems (at home) is: * "Clone" the active slice to the other slice. * Build the world & suitable kernels on the build machine. * Mount /usr/src and /usr/obj from the build machine. * Set DESTDIR to a suitable directory on the other slice. * make installkernel ${DESTDIR} && \ mergemaster -U -u 0022 -p && \ make installworld ${DESTDIR} && \ mergemaster -F -U -u 0022 -i && \=20 make delete-old ${DESTDIR} * reboot from the other slice. * Mount /usr/src and /usr/obj from the build machine. * Stop all services that depend on 3rd-party software (ports/packages). * pkg upgrade * make delete-old-libs * reboot (I elided a few minor embellishments; the above are the essential steps.) It seems to work for me. Peace, david --=20 David H. Wolfskill david@catwhisker.org I look forward to voting against Trump again at the earliest opportunity. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --Wjspmq6N72sNzV6w Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJZUo3JXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XCnIH/3y6AR9SSrKtOxY9y4VEWPPs nepmTkFCuiU2GC4978GUTe/eLFbAgbAcidVtxeUCrjkdbfQ05mKUaVZaHoVHsPiD fv1b2zIjvSLEcjjpAwz6sgODE3hC2u7YSEun40FW74oiZekNqOoMj595ninutLh7 NRVQBglmM7xUfZbKopK4jo9HAlcbTAHLZ1DV90dDs+W8FCPWcQsyAdj8GSUFRaWM wH+QVJN7pTXkOqejrF8c8ABIgsiXo4TcMJa3aNBs1ztugMh7C02tJUGhIZgIlUZv fg8BMMzCZLrnNPDqRqJun0suC9a/08Dq2/Q+UvQTUAfLfc/oMowyEnggDFG0KuE= =phbw -----END PGP SIGNATURE----- --Wjspmq6N72sNzV6w-- From owner-freebsd-ports@freebsd.org Tue Jun 27 17:32: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 79E59D8BCD5 for ; Tue, 27 Jun 2017 17:32:59 +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 3DD4075C46 for ; Tue, 27 Jun 2017 17:32:58 +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 52A8928432; Tue, 27 Jun 2017 19:32:49 +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 DAFFD2840C; Tue, 27 Jun 2017 19:32:47 +0200 (CEST) Subject: Re: Should a package restart on upgrade itself To: Matthias Fechner , FreeBSD Ports ML References: From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <595296BF.3040906@quip.cz> Date: Tue, 27 Jun 2017 19:32:47 +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: Tue, 27 Jun 2017 17:32:59 -0000 Matthias Fechner wrote on 2017/06/27 18:29: > Dear all, > > it is always a pain if pkg upgrade a lot of packages to restart all > services to make sure update/security fixes are applied to all running > services. > > Is there an option in pkg that it restart services automatically or is > it OK if I would add a post-install script to the packages (I maintain) > that will include a "service foo restart"? > > What is best practice here? Please don't do this. Some ports did this in the past and this was really a pain during larger upgrades. It sometimes leave services stopped (hi MySQL). The same bad practice is disabling / enabling Apache modules on upgrade. pkg upgrade should just do it's work - upgrade packages on disk. But manipulating config files and restart of services is up to me - the Administrator (or my tools). It would be nice to have some kind of "hooks" in pkg, which can be used to notify deployment tools that some services should be (re)started, or do restart in some simpler environment if user allows this (setup hooks for service restart). But is must not be done automatically for individual ports / packages even if maintainer thinks it is Good Idea (tm) Miroslav Lachman From owner-freebsd-ports@freebsd.org Tue Jun 27 17:45: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 AFACBD8C3E5 for ; Tue, 27 Jun 2017 17:45:38 +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 94CC676718 for ; Tue, 27 Jun 2017 17:45: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 AAA2AF54; Tue, 27 Jun 2017 12:45:35 -0500 (CDT) Date: Tue, 27 Jun 2017 12:45:34 -0500 From: Mark Linimon To: scratch65535@att.net Cc: Grzegorz Junka , freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170627174534.GA29356@lonesome.com> References: <2f23f3d0-dcb1-dc12-eb9f-c8966a10f5f7@toco-domains.de> <77c15a0a-fde0-b240-803e-b369ebf0b897@gjunka.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: Tue, 27 Jun 2017 17:45:38 -0000 On Tue, Jun 27, 2017 at 09:24:31AM -0400, scratch65535@att.net wrote: > The number of ports to build a server-of-all-work is not large. Now the problem is getting people to agree on exactly what that subset is. If there is interest, I can provide the examples and code I use whenever I start up a new machine here at the house, e.g. powerpc64, sparc64, etc. And we'll see how close to agreement people can get. (Yes, I'm quite skeptical.) > Unnecessarily complex and a source of uncontrolled errors, yes, One person's "unnecessary" is another person's "necessary". > Specialist workstations such as sound/video editing? Maybe. You'll immediately go from a few hundred ports to a few thousand ports. No one has ever done the work on "most minimal set of dependencies" in the ports tree -- and that's because it's hard work. Add to that the fact that the technology has never supported partial checkouts and it complicates things. tl;dr: I do have long-time experience building subsets of the ports tree and in my experience it's harder than people think, once you get beyond a few dozen targets. mcl From owner-freebsd-ports@freebsd.org Tue Jun 27 17:56:37 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 DD66CD8C9AA for ; Tue, 27 Jun 2017 17:56:37 +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 BFEA2772F9 for ; Tue, 27 Jun 2017 17:56:37 +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 7BBFEF54; Tue, 27 Jun 2017 12:56:36 -0500 (CDT) Date: Tue, 27 Jun 2017 12:56:35 -0500 From: Mark Linimon To: Thomas Mueller Cc: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170627175635.GB29356@lonesome.com> References: <09384577-ed7e-d142-43f3-0a08f5d21056@freebsd.org> <5eabe1d2-85a3-f7eb-a1ab-dc5552eb70fe@gjunka.com> <6d35f70b-17f2-d864-68ed-a3637cdc9fbf@gjunka.com> <63e5c4e30a60d51c5a068177b9483206@acheronmedia.hr> <8948545b-5269-8a0e-3f92-9dfd02f227c1@gjunka.com> <310d8cf4-3549-aca7-5666-b3496707917e@heuristicsystems.com.au> <61.E4.01815.93B02595@dnvrco-omsmta03> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <61.E4.01815.93B02595@dnvrco-omsmta03> 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: Tue, 27 Jun 2017 17:56:38 -0000 On Tue, Jun 27, 2017 at 07:37:22AM +0000, Thomas Mueller wrote: > It seems NetBSD pkgsrc people are not catching on, preferring to stay > with the clumsy pkgsrc tools: creatures of habit, reluctant to change. Remember that NetBSD runs on dozens of targets*, of which only two support Ada AFAIK. mcl * http://ftp.netbsd.org/pub/NetBSD/NetBSD-7.1/ From owner-freebsd-ports@freebsd.org Tue Jun 27 18:12: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 CAEDFD8D19B for ; Tue, 27 Jun 2017 18:12:06 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from anny.lostinspace.de (anny.lostinspace.de [IPv6:2001:608:a02::33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8FE0D77BCE for ; Tue, 27 Jun 2017 18:12:06 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from server.idefix.lan (aftr-185-17-205-21.dynamic.mnet-online.de [185.17.205.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: idefix@fechner.net) by anny.lostinspace.de (Postfix) with ESMTPSA id DA939B755C7 for ; Tue, 27 Jun 2017 20:12:04 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=fechner.net; s=default; t=1498587125; bh=KSUqkGcnGjnIXvwcd8kY5m1iopiGYLuEoepmJ7mfycc=; h=Subject:To:References:From:Date:In-Reply-To; b=AOLb8ECK7BNpp1S8rclM8fdp9Ablmipc2KGv8qGW0AcxXKRxHgxbB3dxKQg6jiBPd Fx75T45IX0jpGiTxMRQRF3Z2cvFd5spmTs8+PwNCyQztkx6UfmOvc5oIYgdL98AHL6 jHJJa/C88Dl48MU0RHsr9yY3wCgc4q0EVYpvFK0Y= Received: from [192.168.0.151] (aftr-185-17-205-21.dynamic.mnet-online.de [185.17.205.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by server.idefix.lan (Postfix) with ESMTPSA id 4FC80CD3301 for ; Tue, 27 Jun 2017 20:12:04 +0200 (CEST) Subject: Re: Should a package restart on upgrade itself To: freebsd-ports@freebsd.org References: <20170627163502.u2m4trqccbkri63j@ivaldir.net> <4aad148bce4cfc626dea0d31bd62be41@acheronmedia.com> From: Matthias Fechner Message-ID: Date: Tue, 27 Jun 2017 20:11:59 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <4aad148bce4cfc626dea0d31bd62be41@acheronmedia.com> Content-Type: text/plain; charset=utf-8 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: Tue, 27 Jun 2017 18:12:06 -0000 Am 27.06.2017 um 18:50 schrieb Vlad K.: > Will this cover libraries as well? Eg. Libre/Open SSL upgrades, > restart all services that depend on it? > > Meanwhile, there's "lsop": thanks for this tool, that is indeed very helpful. Maybe it is a good idea if pkg collects the information from each package what should be restarted if: HANDLE_RC_SCRIPTS = true; is set. In this case it is the responsibility of the package maintainer to mark which service should be started if it was upgraded. And then do a single bulk restart operation at the end of the complete upgrade. Gruß Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook From owner-freebsd-ports@freebsd.org Tue Jun 27 18:36: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 4A7D5D8D975 for ; Tue, 27 Jun 2017 18:36:31 +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 11D0278810 for ; Tue, 27 Jun 2017 18:36:30 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mx.irealone.hr (Postfix, from userid 58) id BE5838A87; Tue, 27 Jun 2017 20:36: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 736DB8A83 for ; Tue, 27 Jun 2017 20:36:27 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 27 Jun 2017 20:36:27 +0200 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: Should a package restart on upgrade itself Organization: Acheron Media In-Reply-To: References: <20170627163502.u2m4trqccbkri63j@ivaldir.net> <4aad148bce4cfc626dea0d31bd62be41@acheronmedia.com> Message-ID: <77b3c4e0b39e561fc808ce42c7983c2c@acheronmedia.com> 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: Tue, 27 Jun 2017 18:36:31 -0000 Also worth noting is that if you build your pkg repo with Poudriere (and I'm guessing Synth), as it rebuilds ALL packages in the dependency chain, it's easy to see, on each bulk run, which of the packages with services are or could be affected (because their packages are rebuilt), and should therefore be restarted. That at least is how we do it for our servers. -- Vlad K. From owner-freebsd-ports@freebsd.org Tue Jun 27 19:08:09 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 04D6AD8E0A7 for ; Tue, 27 Jun 2017 19:08:09 +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 B6D2A79538 for ; Tue, 27 Jun 2017 19:08:08 +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 DBB6528472; Tue, 27 Jun 2017 21:08:04 +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 B80F428453; Tue, 27 Jun 2017 21:08:03 +0200 (CEST) Subject: Re: Should a package restart on upgrade itself To: Matthias Fechner , freebsd-ports@freebsd.org References: <20170627163502.u2m4trqccbkri63j@ivaldir.net> <4aad148bce4cfc626dea0d31bd62be41@acheronmedia.com> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <5952AD13.6090700@quip.cz> Date: Tue, 27 Jun 2017 21:08:03 +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=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: Tue, 27 Jun 2017 19:08:09 -0000 Matthias Fechner wrote on 2017/06/27 20:11: > Am 27.06.2017 um 18:50 schrieb Vlad K.: >> Will this cover libraries as well? Eg. Libre/Open SSL upgrades, >> restart all services that depend on it? >> >> Meanwhile, there's "lsop": > > thanks for this tool, that is indeed very helpful. > > Maybe it is a good idea if pkg collects the information from each > package what should be restarted if: > > HANDLE_RC_SCRIPTS = true; > > is set. > In this case it is the responsibility of the package maintainer to mark which service should be started if it was upgraded. > And then do a single bulk restart operation at the end of the complete upgrade. It is not so easy to handle this on maintainer side. For example we have one machine with PHP + Apache + Lighttpd. If some PHP extension is reinstalled, what should be restarted and how maintainer should know it? Is Apache using PHP? Is Lighttpd using PHP? Are there php-fpm running PHP? Just because there is some package it doesn't mean it uses PHP and should be restarted. It depends on configuration made by sysadmin. Sometimes the setup is so complex that it is better to let this on admins decision and not some automagick guess. Miroslav Lachman From owner-freebsd-ports@freebsd.org Tue Jun 27 19:08: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 D9074D8E16E for ; Tue, 27 Jun 2017 19:08:59 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 421D179620 for ; Tue, 27 Jun 2017 19:08:58 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 23483 invoked by uid 89); 27 Jun 2017 19:08:50 -0000 Received: from unknown (HELO ?100.83.202.69?) (mg@grem.de@109.43.0.37) by mail.grem.de with ESMTPA; 27 Jun 2017 19:08:50 -0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Should a package restart on upgrade itself From: Michael Gmelin X-Mailer: iPhone Mail (14F89) In-Reply-To: Date: Tue, 27 Jun 2017 21:08:49 +0200 Cc: freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20170627163502.u2m4trqccbkri63j@ivaldir.net> <4aad148bce4cfc626dea0d31bd62be41@acheronmedia.com> To: Matthias Fechner 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, 27 Jun 2017 19:09:00 -0000 > On 27. Jun 2017, at 20:11, Matthias Fechner wrote: >=20 >> Am 27.06.2017 um 18:50 schrieb Vlad K.: >> Will this cover libraries as well? Eg. Libre/Open SSL upgrades, >> restart all services that depend on it? >>=20 >> Meanwhile, there's "lsop":=20 >=20 > thanks for this tool, that is indeed very helpful. >=20 > Maybe it is a good idea if pkg collects the information from each > package what should be restarted if: >=20 > HANDLE_RC_SCRIPTS =3D true; >=20 > is set. > In this case it is the responsibility of the package maintainer to mark wh= ich service should be started if it was upgraded. > And then do a single bulk restart operation at the end of the complete upg= rade. As default behavior this is not good for admins - you really want to be able= to control when a service restarts, especially when running many services, d= oing multiple updates etc. -m >=20 > Gru=C3=9F > Matthias >=20 > --=20 >=20 > "Programming today is a race between software engineers striving to > build bigger and better idiot-proof programs, and the universe trying to > produce bigger and better idiots. So far, the universe is winning." -- > Rich Cook >=20 > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Tue Jun 27 19:12:41 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 83398D8E3FD for ; Tue, 27 Jun 2017 19:12:41 +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 4558F79AF5 for ; Tue, 27 Jun 2017 19:12:40 +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 C809E28473; Tue, 27 Jun 2017 21:12:38 +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 2C3A728435; Tue, 27 Jun 2017 21:12:38 +0200 (CEST) Subject: Re: Should a package restart on upgrade itself To: "Vlad K." , freebsd-ports@freebsd.org References: <20170627163502.u2m4trqccbkri63j@ivaldir.net> <4aad148bce4cfc626dea0d31bd62be41@acheronmedia.com> <77b3c4e0b39e561fc808ce42c7983c2c@acheronmedia.com> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <5952AE26.6090504@quip.cz> Date: Tue, 27 Jun 2017 21:12:38 +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: <77b3c4e0b39e561fc808ce42c7983c2c@acheronmedia.com> 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: Tue, 27 Jun 2017 19:12:41 -0000 Vlad K. wrote on 2017/06/27 20:36: > > Also worth noting is that if you build your pkg repo with Poudriere (and > I'm guessing Synth), as it rebuilds ALL packages in the dependency > chain, it's easy to see, on each bulk run, which of the packages with > services are or could be affected (because their packages are rebuilt), > and should therefore be restarted. That at least is how we do it for our > servers. And this is another problem. Poudriere always rebuild whole dependency chain but if package version stays the same then pkg upgrade will not upgrade all packages in chain but just the one with different version number. If OpenSSL was upgraded but Apache (depending on OpenSSL from ports) was not upgraded it is hard to say "restart Apache" from some pkg magick. So again sysadmin must know what and when to restart. Miroslav Lachman From owner-freebsd-ports@freebsd.org Tue Jun 27 19:18: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 284D9D8E50D for ; Tue, 27 Jun 2017 19:18:30 +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 E1BD479C2B for ; Tue, 27 Jun 2017 19:18:29 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mx.irealone.hr (Postfix, from userid 58) id 744488AEC; Tue, 27 Jun 2017 21:18: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 1FB068AE8 for ; Tue, 27 Jun 2017 21:18:27 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 27 Jun 2017 21:18:27 +0200 From: "Vlad K." To: freebsd-ports@freebsd.org Subject: Re: Should a package restart on upgrade itself Organization: Acheron Media In-Reply-To: <5952AE26.6090504@quip.cz> References: <20170627163502.u2m4trqccbkri63j@ivaldir.net> <4aad148bce4cfc626dea0d31bd62be41@acheronmedia.com> <77b3c4e0b39e561fc808ce42c7983c2c@acheronmedia.com> <5952AE26.6090504@quip.cz> 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: Tue, 27 Jun 2017 19:18:30 -0000 On 2017-06-27 21:12, Miroslav Lachman wrote: > > And this is another problem. Poudriere always rebuild whole dependency > chain but if package version stays the same then pkg upgrade will not > upgrade all packages in chain but just the one with different version > number. Which is my point. pkg might not upgrade postgresql96-server because the version of THAT package didn't change, but you'll see in the output of Poudriere bulk that postgresql96-server was rebuilt because, say, libxml was updated or rebuilt because, in turn, some of its own dependency updated. That's why Poudriere's bulk output is the best list to check what you might want to restart, IMHO. -- Vlad K. From owner-freebsd-ports@freebsd.org Tue Jun 27 20:56: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 853F4D903C7 for ; Tue, 27 Jun 2017 20:56:52 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm22-vm2.access.bullet.mail.bf1.yahoo.com (nm22-vm2.access.bullet.mail.bf1.yahoo.com [216.109.115.145]) (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 4B9307CF45 for ; Tue, 27 Jun 2017 20:56:51 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1498596800; bh=Xp3tDs/HSFtWBoUXOiVWi6TtJ8j1jzolGRNfdkR72Qs=; h=From:To:Cc:Subject:Date:References:In-Reply-To:From:Subject; b=asz+viZCM+7nD+LofMQOU8+qlF/jUEqO/12zkPXm3nbx84uMEBKzlWSjb9P3QvGAGtimoCymXQb4+OAOemFBPSSq8z+d/zLImOqOQIQW/WTwcUu2kIO8aRn3qL79MKcvYHBv+uuKC/J6A43I5Ijq/Xv4dx0jHVCX5VmNmcMx9LI= Received: from [66.196.81.155] by nm22.access.bullet.mail.bf1.yahoo.com with NNFMP; 27 Jun 2017 20:53:20 -0000 Received: from [98.139.244.52] by tm1.access.bullet.mail.bf1.yahoo.com with NNFMP; 27 Jun 2017 20:53:20 -0000 Received: from [127.0.0.1] by smtp114.sbc.mail.bf1.yahoo.com with NNFMP; 27 Jun 2017 20:53:20 -0000 X-Yahoo-Newman-Id: 488313.41541.bm@smtp114.sbc.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: uU4vdkUVM1nAqeSoS0X1jktNgHdAScPkt4zafgKI0Wz5XYx 9q.zNgOkOx6h.HT7_9Or5B5VFNo3TYzeDE7BaZ0DOPadHPk58fgP8wsQ57iD mnVvdNIkZWMoV6KzLAs6akxaSXZfjHYrrg7et_rxWWwAkf4NDQQ3dDnXbQA3 RZk84soUtIs3pPzrioJlRAOpxZLd8oFR7IAnZya_yFQsnwLUOuT1axd25fF1 Bv9dwxWXUCYfLUi9J5ldIpH5tc7tpUJUrpHpxPw9u7kJ83h7GsBBYWEdDEsn IcgS0OAW4SaSV8w6Jak7gDbFFhxp7A46QmOJWqAVsvvVznzmCqf8ImyWXRpS ImKM1H4q.jiEZmAJAQ8ec_AU9FXGWbKVOVtXO905mwdkF1M7U3Q8HRLPuz6_ 3v6z5iLG2YRvBzNGrXLzQRI1j8xKaHBUqxbwKVWK3mc8nmdYbCj5sdHFl9hQ ..ZicKcMOoi8nFnMgZvVHmqYcUq5mZscn.DJDgFz5kIuafJlXTml34UaUe_l EqfSAZ2YnanDWusxPqPqKDPAeJbM3vgBwbC1Uqpr3RXpxbtQT2nuA5NtCUuJ I.xBwCEAW7g9Wa_btFWo_ X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: Mark Linimon Cc: Grzegorz Junka , freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Date: Tue, 27 Jun 2017 16:53:36 -0400 Message-ID: References: <2f23f3d0-dcb1-dc12-eb9f-c8966a10f5f7@toco-domains.de> <77c15a0a-fde0-b240-803e-b369ebf0b897@gjunka.com> <20170627174534.GA29356@lonesome.com> In-Reply-To: <20170627174534.GA29356@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: Tue, 27 Jun 2017 20:56:52 -0000 [Default] On Tue, 27 Jun 2017 12:45:34 -0500, Mark Linimon wrote: >On Tue, Jun 27, 2017 at 09:24:31AM -0400, scratch65535@att.net wrote: >> The number of ports to build a server-of-all-work is not large. > >Now the problem is getting people to agree on exactly what that >subset is. Since that's what I integrate for my dev use, I'd be happy to take a zero'th-order cut at defining it, if nobody else wants to. > >If there is interest, I can provide the examples and code I use >whenever I start up a new machine here at the house, e.g. powerpc64, >sparc64, etc. And we'll see how close to agreement people can get. Sounds good t'me! > >(Yes, I'm quite skeptical.) > >> Unnecessarily complex and a source of uncontrolled errors, yes, > >One person's "unnecessary" is another person's "necessary". By "unnecessary", Mark, I mean the fact that the bits are not controlled locally, and thus potentially change from moment to moment such that it's impossible to guarantee that two people building the same app with the same options on two different days, or even hours, will get the same result. Switching to a central repository model, where the bits are fetched from around the globe only once per cycle, sanitised, and thereafter read only from the repository, would drop the number of file-not-founds and wrong-versions down pretty close to zero. > >> Specialist workstations such as sound/video editing? Maybe. > >You'll immediately go from a few hundred ports to a few thousand ports. > I'm happy to take your word for it, because I've no clue. I wonder whether the most important subset could be determined by survey. Any views on that? >No one has ever done the work on "most minimal set of dependencies" >in the ports tree -- and that's because it's hard work. Add to that >the fact that the technology has never supported partial checkouts >and it complicates things. No argument from me! IMO a big contributor to the problem is that the bits haven't been normalised and integrated into libraries. So the process is frankensteinean: odds and bobs dredged up wherever they can be found and stuck together in hope that they'll cooperate. Just looking at the stuff that goes into Firefox made my blood run cold, and completely explained (fsvo explained) where all the problems come from with that app. > >tl;dr: I do have long-time experience building subsets of the ports >tree and in my experience it's harder than people think, once you >get beyond a few dozen targets. I don't doubt that even slightly. But I do think the magnitude could be at least reduced by moving toward normalised bits. From owner-freebsd-ports@freebsd.org Tue Jun 27 21:02: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 CAC3FD90596 for ; Tue, 27 Jun 2017 21:02: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.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 A20AA7D2E2 for ; Tue, 27 Jun 2017 21:02:56 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:60944] helo=localhost) by dnvrco-omsmta02 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id EE/2B-03057-CB7C2595; Tue, 27 Jun 2017 21:01:49 +0000 Date: Tue, 27 Jun 2017 21:01:39 +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> <8948545b-5269-8a0e-3f92-9dfd02f227c1@gjunka.com> <310d8cf4-3549-aca7-5666-b3496707917e@heuristicsystems.com.au> <61.E4.01815.93B02595@dnvrco-omsmta03> <20170627175635.GB29356@lonesome.com> Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version X-RR-Connecting-IP: 107.14.64.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: Tue, 27 Jun 2017 21:02:57 -0000 from Mark Linimon: > Remember that NetBSD runs on dozens of targets*, of which only two support > Ada AFAIK. > mcl > * http://ftp.netbsd.org/pub/NetBSD/NetBSD-7.1/ I follow http://releng.netbsd.org/cgi-bin/builds.cgi which shows 72 targets for HEAD, 67 targets for netbsd-7 and netbsd-8, 60 targets for netbsd-6. Ada, developed by the US Department of Defense, was not originally for amd64 and i386. A large part of the problem is that building Ada requires a preexisting GNAT. Full GCC suite includes Ada, and is capable of cross-compilation, raising the possibility of building for other targets. I can not say with authority which targets would succeed. Dragonlace.net shows a port for FreeBSD aarch64. Tom From owner-freebsd-ports@freebsd.org Tue Jun 27 23:09:17 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 5218BD92225 for ; Tue, 27 Jun 2017 23:09:17 +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 299578076D for ; Tue, 27 Jun 2017 23:09:16 +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 0287F166; Tue, 27 Jun 2017 18:09:09 -0500 (CDT) Date: Tue, 27 Jun 2017 18:09:07 -0500 From: Mark Linimon To: Thomas Mueller Cc: freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170627230907.GA30811@lonesome.com> References: <6d35f70b-17f2-d864-68ed-a3637cdc9fbf@gjunka.com> <63e5c4e30a60d51c5a068177b9483206@acheronmedia.hr> <8948545b-5269-8a0e-3f92-9dfd02f227c1@gjunka.com> <310d8cf4-3549-aca7-5666-b3496707917e@heuristicsystems.com.au> <61.E4.01815.93B02595@dnvrco-omsmta03> <20170627175635.GB29356@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: Tue, 27 Jun 2017 23:09:17 -0000 On Tue, Jun 27, 2017 at 09:01:39PM +0000, Thomas Mueller wrote: > raising the possibility of building for other targets. Which is very much not hardly even the same as "they are being resistant to change". In fact, about as far away from it as is possible to get. "techinically possible" != "feasible in the immediate future". I feel like I'm repeating myself in this thread, again. mcl From owner-freebsd-ports@freebsd.org Tue Jun 27 23:16: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 96968D924CE for ; Tue, 27 Jun 2017 23:16:03 +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 617AB80B7D for ; Tue, 27 Jun 2017 23:16:03 +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 24A1A166; Tue, 27 Jun 2017 18:16:02 -0500 (CDT) Date: Tue, 27 Jun 2017 18:16:01 -0500 From: Mark Linimon To: scratch65535@att.net Cc: Grzegorz Junka , freebsd-ports@freebsd.org Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Message-ID: <20170627231600.GB30811@lonesome.com> References: <2f23f3d0-dcb1-dc12-eb9f-c8966a10f5f7@toco-domains.de> <77c15a0a-fde0-b240-803e-b369ebf0b897@gjunka.com> <20170627174534.GA29356@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: Tue, 27 Jun 2017 23:16:03 -0000 On Tue, Jun 27, 2017 at 04:53:36PM -0400, scratch65535@att.net wrote: > Since that's what I integrate for my dev use, I'd be happy to > take a zero'th-order cut at defining it, if nobody else wants to. Fine. See http://www.lonesome.com/FreeBSD/poudriere/subsets/ for what I use. I'm not particularly interested in maintaining it as a general set of files, but if someone can build on it, fine. > By "unnecessary", Mark, I mean the fact that the bits are not > controlled locally, and thus potentially change from moment to > moment such that it's impossible to guarantee that two people > building the same app with the same options on two different > days, or even hours, will get the same result. I don't understand this. The distinfo mechanism is the solution for this problem for released code. If people are relying on "whatever is in git at the moment" to mean "release", well then that's upstream not understanding what is meant by "release". Either educated them or fork their code and become the new upstream. > Switching to a central repository model, where the bits are > fetched from around the globe only once per cycle, sanitised, and > thereafter read only from the repository, would drop the number > of file-not-founds and wrong-versions down pretty close to zero. Again, I simply don't understand this. > >No one has ever done the work on "most minimal set of dependencies" > >in the ports tree -- and that's because it's hard work. Add to that > >the fact that the technology has never supported partial checkouts > >and it complicates things. > > No argument from me! IMO a big contributor to the problem is > that the bits haven't been normalised and integrated into > libraries. So the process is frankensteinean: odds and bobs > dredged up wherever they can be found and stuck together in hope > that they'll cooperate. And this is where the hard work lies. By comparison, defining "which ports are canonical" is easy. IMHO. mcl From owner-freebsd-ports@freebsd.org Tue Jun 27 23:54: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 D06F0D93232 for ; Tue, 27 Jun 2017 23:54:51 +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 77051822A7 for ; Tue, 27 Jun 2017 23:54:51 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (x527179db.dyn.telefonica.de [82.113.121.219]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id v5RNseSU064978 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Tue, 27 Jun 2017 23:54:43 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host x527179db.dyn.telefonica.de [82.113.121.219] claimed to be ultrabook.yoonka.com Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Cc: freebsd-ports@freebsd.org References: <2f23f3d0-dcb1-dc12-eb9f-c8966a10f5f7@toco-domains.de> <77c15a0a-fde0-b240-803e-b369ebf0b897@gjunka.com> <20170627174534.GA29356@lonesome.com> From: Grzegorz Junka Message-ID: <51fbf1f5-8d7c-3e3a-1bf2-e9e2ca6156a4@gjunka.com> Date: Tue, 27 Jun 2017 23:54: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: <20170627174534.GA29356@lonesome.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: Tue, 27 Jun 2017 23:54:51 -0000 On 27/06/2017 17:45, Mark Linimon wrote: > On Tue, Jun 27, 2017 at 09:24:31AM -0400, scratch65535@att.net wrote: >> The number of ports to build a server-of-all-work is not large. > Now the problem is getting people to agree on exactly what that > subset is. I think this part is fairly easy. We can start with ports for which maintainers agree to provide security fixes to the stable branch or artificially limit the number and ask people to vote for their favourites. Another point for consideration is to firstly consider ports with smaller amount of dependencies so that there is less work in maintaining them. > No one has ever done the work on "most minimal set of dependencies" > in the ports tree -- and that's because it's hard work. Add to that > the fact that the technology has never supported partial checkouts > and it complicates things. Yes, but you need to start somewhere. Otherwise it will remain as occasional rant. Clearly starting with 26,000 isn't an option. Then starting with small number of ports and learning how to overcome these difficulties is best we can do. > tl;dr: I do have long-time experience building subsets of the ports > tree and in my experience it's harder than people think, once you > get beyond a few dozen targets. > I think the hardest part is to agree on a set that is not too difficult to maintain but still useful so that people will try to actually install systems using them. Grzegorz From owner-freebsd-ports@freebsd.org Wed Jun 28 06:30: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 DF149D996C6 for ; Wed, 28 Jun 2017 06:30:52 +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 AD81A684AA for ; Wed, 28 Jun 2017 06:30:51 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:27062] helo=localhost) by dnvrco-omsmta03 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id C4/3F-01815-A1D43595; Wed, 28 Jun 2017 06:30:50 +0000 Date: Wed, 28 Jun 2017 06:30:39 +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> <8948545b-5269-8a0e-3f92-9dfd02f227c1@gjunka.com> <310d8cf4-3549-aca7-5666-b3496707917e@heuristicsystems.com.au> <61.E4.01815.93B02595@dnvrco-omsmta03> <20170627175635.GB29356@lonesome.com> <20170627230907.GA30811@lonesome.com> Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version X-RR-Connecting-IP: 107.14.64.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: Wed, 28 Jun 2017 06:30:53 -0000 from Mark Linimon: > On Tue, Jun 27, 2017 at 09:01:39PM +0000, Thomas Mueller wrote: > > raising the possibility of building for other targets. > Which is very much not hardly even the same as "they are being resistant > to change". In fact, about as far away from it as is possible to get. > "techinically possible" != "feasible in the immediate future". > I feel like I'm repeating myself in this thread, again. > mcl A lot of pkgsrc users, perheps the majority, use architecture either i386 or amd64 (I have no statistics). FreeBSD also supports many architectures, not as many as NetBSD, but some where there is no Ada compiler, and no LLVM/clang either. Some of the architectures supported by NetBSD are near-extinct now, acorn26 for one, and would not be prime targets for pkgsrc development, nobody is going to care about lack of an Ada compiler. Tom From owner-freebsd-ports@freebsd.org Wed Jun 28 07:37: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 53961D9ACEB for ; Wed, 28 Jun 2017 07:37:39 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) 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 1156B6E3B9 for ; Wed, 28 Jun 2017 07:37:38 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id AF4D41AAF058; Wed, 28 Jun 2017 09:37:35 +0200 (CEST) Subject: Re: Should a package restart on upgrade itself To: Matthias Fechner , FreeBSD Ports ML References: From: Torsten Zuehlsdorff Message-ID: <9192e422-deb0-e87e-93e7-30a7eeabe136@toco-domains.de> Date: Wed, 28 Jun 2017 09:37:32 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.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-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, 28 Jun 2017 07:37:39 -0000 On 27.06.2017 18:29, Matthias Fechner wrote: > Dear all, > > it is always a pain if pkg upgrade a lot of packages to restart all > services to make sure update/security fixes are applied to all running > services. > > Is there an option in pkg that it restart services automatically or is > it OK if I would add a post-install script to the packages (I maintain) > that will include a "service foo restart"? Since the number of services is limited i do in such scenarios you described (or in doubt) a simple: # service -R Greetings, Torsten From owner-freebsd-ports@freebsd.org Wed Jun 28 08:18: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 C0457D9B9E7 for ; Wed, 28 Jun 2017 08:18:45 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 761646F31A for ; Wed, 28 Jun 2017 08:18:44 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3wyFzw3Dvdzb56; Wed, 28 Jun 2017 10:18:36 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=mail; t=1498637914; x=1500452315; bh=bM/m5oFY+cex6j Bh3jVMn7E5O5BZZXEFYL2VG8zBZGk=; b=EQQC1NrpfvvemqHz4o9wI75VpHWNtP 8R/5bWCVHUHOpJeOIqC8iEARaAaGl0DENJ6RXneoryLTKajU7fNXlol3WF8Rddya vnwPIjNh84Ey4+nqADOO1dWkKLH2i5LACQJorET8Zx87znRO7UhdWinzn+LO83A7 t302J1uSD+b9E= 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 p-rOlkB1b88t; Wed, 28 Jun 2017 10:18:34 +0200 (CEST) Received: from marvin.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Wed, 28 Jun 2017 10:18:34 +0200 (CEST) Subject: Re: Should a package restart on upgrade itself To: Miroslav Lachman <000.fbsd@quip.cz>, Matthias Fechner , FreeBSD Ports ML References: <595296BF.3040906@quip.cz> From: Guido Falsi Message-ID: <2678b33c-78c9-5e34-3ae6-434e1f176518@madpilot.net> Date: Wed, 28 Jun 2017 10:18:33 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <595296BF.3040906@quip.cz> 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, 28 Jun 2017 08:18:45 -0000 On 06/27/17 19:32, Miroslav Lachman wrote: > Matthias Fechner wrote on 2017/06/27 18:29: >> Dear all, >> >> it is always a pain if pkg upgrade a lot of packages to restart all >> services to make sure update/security fixes are applied to all running >> services. >> >> Is there an option in pkg that it restart services automatically or is >> it OK if I would add a post-install script to the packages (I maintain) >> that will include a "service foo restart"? >> >> What is best practice here? > > Please don't do this. > Some ports did this in the past and this was really a pain during larger > upgrades. It sometimes leave services stopped (hi MySQL). > I subscribe to this comment. I also got burned in the past by this behavior(which luckily is no more present). I'd like to also comment that pkg should just do it's work, managing packages, if you want to automate system maintenance, there are specific tools for that (like puppet, ansible, cfengine, chef...and others I can't name right away). Coding parts of software configuration management in pkg is not a good idea IMHO. -- Guido Falsi From owner-freebsd-ports@freebsd.org Wed Jun 28 09:08: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 DAA41D9CCB1 for ; Wed, 28 Jun 2017 09:08:54 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) 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 A3CC67113E for ; Wed, 28 Jun 2017 09:08:54 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from [192.168.0.111] (port-212-202-156-99.static.qsc.de [212.202.156.99]) by toco-domains.de (Postfix) with ESMTPA id 1C18E1AAF0ED; Wed, 28 Jun 2017 11:08:47 +0200 (CEST) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: scratch65535@att.net, Grzegorz Junka Cc: freebsd-ports@freebsd.org References: <2f23f3d0-dcb1-dc12-eb9f-c8966a10f5f7@toco-domains.de> <77c15a0a-fde0-b240-803e-b369ebf0b897@gjunka.com> From: Torsten Zuehlsdorff Message-ID: <2605c21d-7e4a-a877-78b1-7455e0afa408@toco-domains.de> Date: Wed, 28 Jun 2017 08:58:59 +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; 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, 28 Jun 2017 09:08:54 -0000 On 27.06.2017 15:24, scratch65535@att.net wrote: > [Default] On Mon, 26 Jun 2017 19:33:50 +0000, Grzegorz Junka > wrote: > >> we could >> start small with a just a handful of ports in a stable LTS (Long Term >> Support) branch. Develop processes around maintaining them, get some >> feedback about the effort of applying only security fixes, then add more >> ports as required or as viable from the resources point of view. How >> does that sound? > > It sounds excellent, at least to me. > > How many platform roles are seen as fbsd's metier? > > Firewall? Already handled. > > Specialist workstations such as sound/video editing? Maybe. I > don't know enough about that to have an opinion. > > Servers. No question. That's always been freebsd's best thing. > The number of ports to build a server-of-all-work is not large. > Unnecessarily complex and a source of uncontrolled errors, yes, > but not really *large* qua large. It really depends. For example only www/gitlab needed 400 ports (!) and its a while i checked. Without a defined list of supported software this is only wishing ;) Greetings, Torsten From owner-freebsd-ports@freebsd.org Wed Jun 28 09:08: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 735A6D9CCAD for ; Wed, 28 Jun 2017 09:08:54 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) 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 21CCF7113D for ; Wed, 28 Jun 2017 09:08:53 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from [192.168.0.111] (port-212-202-156-99.static.qsc.de [212.202.156.99]) by toco-domains.de (Postfix) with ESMTPA id 9D1801AAF0AD; Wed, 28 Jun 2017 11:08:46 +0200 (CEST) Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version To: Grzegorz Junka , freebsd-ports@freebsd.org References: <2f23f3d0-dcb1-dc12-eb9f-c8966a10f5f7@toco-domains.de> <77c15a0a-fde0-b240-803e-b369ebf0b897@gjunka.com> From: Torsten Zuehlsdorff Message-ID: Date: Wed, 28 Jun 2017 08:56:51 +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: <77c15a0a-fde0-b240-803e-b369ebf0b897@gjunka.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: Wed, 28 Jun 2017 09:08:54 -0000 On 26.06.2017 21:33, Grzegorz Junka wrote: > On 26/06/2017 07:24, Torsten Zuehlsdorff wrote: >> Aloha David, >> >>> 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. >> >> The discussions did go on for a while, but lets get more technical. >> While i can understand your use case, it raises various questions: >> >> - How should be EOL-Software handled? For example PHP 5.6, Typo3 7, >> PostgreSQL 9.2 and many more will expire long before FreeBSD 11 >> expires but are still valid (or even default version) when created. >> Since the versions are frozen, how should - at least- security issues >> handled? >> [Yes, i read that a user can switch at its own risk to another branch, >> but lets assume he is very fine with the version (because i have such >> customer)] >> >> - How should be new dependencies handled? GitLab for example sometimes >> *requieres* updates of its dependencies in order to fix security issues. >> >> - Same as above: how should be dropped dependencies handled? In worst >> case we need to maintain them for nearly 5 years, but nobody (should) >> use them >> >> - How to resolve conflicts? I mentioned GitLab above and now realize, >> that sometimes the GitLab update breaks for example www/redmine >> because it depends at other versions than GitLab. >> >> - Where do get the fixes from? We have around 26.000 ports which needs >> fixes in worst case >> >> - How to handle for example security issues only fixed through an >> update? Which such a long time between "updates" it gets very very >> hard to port/get/write patches in fast developing software. Wordpress >> or Gitlab are typical examples with thousands of lines in code-changes >> every update >> >> - How to make the customer clear, that complains about the software >> (old, outdated, missing features, unresolved bugs, etc) are intentional? >> >> - Where to archive the distfiles? Sometimes upstream completely remove >> them from everywhere they can. >> >> And last: how to make updates from FreeBSD version to version easier? >> Many user already have problems with single major updates. From my >> experiences in Windows or Ubuntu LTS usages with such or very similar >> version handling: the update, even of the OS, is pushed as far away as >> possible, because of the big amount of work required, since everything >> needs to checked/updated/changed. >> >> I have a hard time to image, that is handled in another way by you. So >> if you can me give more insight about your use-case i would be happy >> to read it for a better understanding. >> >> I have various customer requiring (and paying for) very old software >> (for example still PHP 5.3). So i know some of there motivations, >> which boils every time down to "its to expensive to upgrade our >> software" [but they don't mean expensive in money]. So maybe we can >> make something happen. > > I understand a stable ports branch would be required by specific > applications (of the FreeBSD system), e.g. data centers, bespoke private > solutions, home servers. Therefore not all 26.000 ports would need to be > security-patched. In fact, I believe it would be viable to determine a > thousand or two of ports mostly used in those environments and commit to > patch only those. Yes, but even with a subset of the ports-tree neither of the above problems is addressed! > Even RedHat, which is a model example, doesn't commit to maintain all > packages, just a selected set of them. In the similar fashion to having > Tier 1, Tier 2 and Tier 3 supported platforms for FreeBSD, we could > start small with a just a handful of ports in a stable LTS (Long Term > Support) branch. Develop processes around maintaining them, get some > feedback about the effort of applying only security fixes, then add more > ports as required or as viable from the resources point of view. How > does that sound? This didn't address any of the issues mentioned above. Nor from other threads. But to be clear: since i already do such things (on a much smaller scale) i have no problem with this idea. But since i'm already get paid and know the work behind it, i wont do it for free. Even do setup a minimal QA infrastructure needs money and maintenance and just build-tests are not enough. Greetings, Torsten From owner-freebsd-ports@freebsd.org Wed Jun 28 10:23: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 23DA5D9E408; Wed, 28 Jun 2017 10:23:49 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) (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 E558373560; Wed, 28 Jun 2017 10:23:48 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (localhost [127.0.0.1]) by ainaz.pair.com (Postfix) with ESMTP id 686653F56A; Wed, 28 Jun 2017 06:23:41 -0400 (EDT) Received: from [192.168.1.109] (unknown [202.188.138.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id 811703F569; Wed, 28 Jun 2017 06:23:24 -0400 (EDT) Date: Wed, 28 Jun 2017 18:21:59 +0800 User-Agent: K-9 Mail for Android In-Reply-To: References: <6FD738D6-F163-4BC5-8E6E-A9B9F35595CD@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work To: Mark Millard ,papowell@astart.com CC: FreeBSD-STABLE Mailing List , FreeBSD Toolchain , FreeBSD Ports , Pedro Giffuni , Gerald Pfeifer From: Gerald Pfeifer Message-ID: <82A991B0-FD8B-457F-8483-D61AE5E6D6F6@pfeifer.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: Wed, 28 Jun 2017 10:23:49 -0000 Hi everyone, I am testing a patch for gcc5-devel right now that will disable fixinclude= s (or rather its fixed files) being packaged=2E Should that work fine for you, I will push this back to gcc5 the following= days=2E That said, the change that triggered this is what I would expect on CURREN= T, not STABLE (and hence hoped we'd have more time for this change)=2E My Internet connectivity right now is only slightly above pigeon speed, so= sorry for any delays=2E Gerald From owner-freebsd-ports@freebsd.org Wed Jun 28 10:24: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 7DA3ED9E554 for ; Wed, 28 Jun 2017 10:24:38 +0000 (UTC) (envelope-from andyf@andyit.com.au) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 64A4673741 for ; Wed, 28 Jun 2017 10:24:38 +0000 (UTC) (envelope-from andyf@andyit.com.au) Received: by mailman.ysv.freebsd.org (Postfix) id 6105AD9E551; Wed, 28 Jun 2017 10:24:38 +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 60B25D9E550 for ; Wed, 28 Jun 2017 10:24:38 +0000 (UTC) (envelope-from andyf@andyit.com.au) Received: from alpine.spintel.net.au (alpine.spintel.net.au [IPv6:2407:e400:1::b]) (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 04BA57373F for ; Wed, 28 Jun 2017 10:24:38 +0000 (UTC) (envelope-from andyf@andyit.com.au) Received: from drunkfish.andyit.com.au (unknown [210.1.210.40]) by alpine.spintel.net.au (Postfix) with ESMTPS id A1EEE4C2B65 for ; Wed, 28 Jun 2017 20:24:24 +1000 (AEST) Received: from snuggles.andyit.com.au (snuggles.andyit.com.au [172.22.2.2]) by drunkfish.andyit.com.au (8.15.2/8.15.2) with ESMTP id v5SAONpY070395 for ; Wed, 28 Jun 2017 20:24:23 +1000 (AEST) (envelope-from andyf@andyit.com.au) Message-ID: <595383D7.70704@andyit.com.au> Date: Wed, 28 Jun 2017 20:24:23 +1000 From: Andy Farkas User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120614 Thunderbird/13.0 MIME-Version: 1.0 To: ports@freebsd.org Subject: 'pkg version' strangeness - No valid entries found 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: Wed, 28 Jun 2017 10:24:38 -0000 root# cd /usr/ports root# make index Generating INDEX-11 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- . . . --- describe.x11-toolkits --- --- describe.x11-wm --- make_index: /usr/ports/archivers/atool: no entry for /usr/ports/:lang/perl5.22 Done. root# root# pkg version -v pkg: No valid entries found in '/usr/ports/INDEX-11' root# root# make index Generating INDEX-11 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- --- describe.astro --- --- describe.audio --- --- describe.benchmarks --- ^Z Suspended root# root# pkg version -v ImageMagick-6.9.6.4_1,1 < needs updating (port has 6.9.8.9,1) ORBit2-2.14.19_2 = up-to-date with port OpenEXR-2.2.0_7 = up-to-date with port . . . zenity-3.18.0 = up-to-date with port zip-3.0_1 = up-to-date with port zziplib-0.13.62_2 = up-to-date with port root# root# fg make index . . . ..and after it finishes I get 'No valid entries' error again for 'pkg version' Anyone know what's going on and/or how to fix? "no entry for /usr/ports/:lang/perl5.22/" looks suspect... -andyf From owner-freebsd-ports@freebsd.org Wed Jun 28 11: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 EE6A4D9F6B7 for ; Wed, 28 Jun 2017 11:21:43 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D8F0E74FDE for ; Wed, 28 Jun 2017 11:21:43 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id D8547D9F6B4; Wed, 28 Jun 2017 11:21:43 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7FDCD9F6B2 for ; Wed, 28 Jun 2017 11:21:43 +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 CA39F74FDC for ; Wed, 28 Jun 2017 11:21:43 +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 v5SBLhKR040407 for ; Wed, 28 Jun 2017 11:21:43 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v5SBLhtq040406; Wed, 28 Jun 2017 11:21:43 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201706281121.v5SBLhtq040406@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: Wed, 28 Jun 2017 11:21:43 +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: Wed, 28 Jun 2017 11:21:44 -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 ------------------------------------------------+-----------------+------------ emulators/mame | 0.166 | mame0187 ------------------------------------------------+-----------------+------------ emulators/mess | 0.166 | mame0187 ------------------------------------------------+-----------------+------------ math/giacxcas | 1.2.2-57 | 1.2.3-55 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Wed Jun 28 12:01:47 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 59D4CDA0961 for ; Wed, 28 Jun 2017 12:01:47 +0000 (UTC) (envelope-from adamw@adamw.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 4616A763B1 for ; Wed, 28 Jun 2017 12:01:47 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3B19DDA0960; Wed, 28 Jun 2017 12:01:47 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AB11DA095F for ; Wed, 28 Jun 2017 12:01:47 +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 9A9C0763AE for ; Wed, 28 Jun 2017 12:01:46 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id 7075da3a TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 28 Jun 2017 06:01:39 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: 'pkg version' strangeness - No valid entries found From: Adam Weinberger In-Reply-To: <595383D7.70704@andyit.com.au> Date: Wed, 28 Jun 2017 06:01:38 -0600 Cc: ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <6F66E187-08D9-4C2F-866B-9102A09ACC93@adamw.org> References: <595383D7.70704@andyit.com.au> To: Andy Farkas 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: Wed, 28 Jun 2017 12:01:47 -0000 > On 28 Jun, 2017, at 4:24, Andy Farkas wrote: >=20 >=20 > root# cd /usr/ports > root# make index > Generating INDEX-11 - please wait..--- describe.accessibility --- > --- describe.arabic --- > --- describe.archivers --- > . > . > . > --- describe.x11-toolkits --- > --- describe.x11-wm --- > make_index: /usr/ports/archivers/atool: no entry for = /usr/ports/:lang/perl5.22 > Done. > root# > root# pkg version -v > pkg: No valid entries found in '/usr/ports/INDEX-11' > root# > root# make index > Generating INDEX-11 - please wait..--- describe.accessibility --- > --- describe.arabic --- > --- describe.archivers --- > --- describe.astro --- > --- describe.audio --- > --- describe.benchmarks --- > ^Z > Suspended > root# > root# pkg version -v > ImageMagick-6.9.6.4_1,1 < needs updating (port has = 6.9.8.9,1) > ORBit2-2.14.19_2 =3D up-to-date with port > OpenEXR-2.2.0_7 =3D up-to-date with port > . > . > . > zenity-3.18.0 =3D up-to-date with port > zip-3.0_1 =3D up-to-date with port > zziplib-0.13.62_2 =3D up-to-date with port > root# > root# fg > make index > . > . > . >=20 > ..and after it finishes I get 'No valid entries' error again for 'pkg = version' >=20 > Anyone know what's going on and/or how to fix? >=20 > "no entry for /usr/ports/:lang/perl5.22/" looks suspect... It may be a typo in your make.conf. If you have DEFAULT_VERSIONS+=3D perl5=3Dlang/perl5.22 It should be DEFAULT_VERSIONS+=3D perl5=3D5.22 # Adam --=20 Adam Weinberger adamw@adamw.org https://www.adamw.org From owner-freebsd-ports@freebsd.org Wed Jun 28 12:08: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 5D946DA0C80 for ; Wed, 28 Jun 2017 12:08:45 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0CF3E7672E; Wed, 28 Jun 2017 12:08:44 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v5SC8hTF040655; Wed, 28 Jun 2017 12:08:43 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v5SC8htm040654; Wed, 28 Jun 2017 05:08:43 -0700 (PDT) (envelope-from david) Date: Wed, 28 Jun 2017 05:08:43 -0700 From: David Wolfskill To: freebsd-ports@freebsd.org Subject: math/R: Build failure after PORTREVISION for shlib change Message-ID: <20170628120843.GG1241@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="DtJW00gg9Uj+27As" 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: Wed, 28 Jun 2017 12:08:45 -0000 --DtJW00gg9Uj+27As Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Running: FreeBSD g1-227.catwhisker.org 11.1-BETA3 FreeBSD 11.1-BETA3 #383 r320438M/= 320450:1100514: Wed Jun 28 03:56:53 PDT 2017 root@g1-227.catwhisker.org= :/common/S1/obj/usr/src/sys/CANARY amd64 with /usr/ports working copy: g1-227(11.1)[4] svn info /usr/ports/ Path: /usr/ports Working Copy Root Path: /usr/ports URL: file:///svn/freebsd/ports/head Relative URL: ^/head Repository Root: file:///svn/freebsd/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 444562 Node Kind: directory Schedule: normal Last Changed Author: jbeich Last Changed Rev: 444562 Last Changed Date: 2017-06-28 02:58:37 -0700 (Wed, 28 Jun 2017) (Repo is a local mirror, updated overnight.) After updating all other installed ports and setting 'MAKE_JOBS_UNSAFE=3Dyes', I tried (again) for math/R and databases/R-cran-DBI; math/R fails: =2E.. making xmalloc.d from xmalloc.c gcc5 -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG = -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp = -fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -Wl,-rpath=3D/usr/local= /lib/gcc5 -isystem /usr/local/include -fno-strict-aliasing -flto -fvisibili= ty=3Dhidden -c regcomp.c -o regcomp.o gcc5 -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG = -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp = -fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -Wl,-rpath=3D/usr/local= /lib/gcc5 -isystem /usr/local/include -fno-strict-aliasing -flto -fvisibili= ty=3Dhidden -c regerror.c -o regerror.o gcc5 -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG = -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp = -fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -Wl,-rpath=3D/usr/local= /lib/gcc5 -isystem /usr/local/include -fno-strict-aliasing -flto -fvisibili= ty=3Dhidden -c regexec.c -o regexec.o gcc5 -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG = -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp = -fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -Wl,-rpath=3D/usr/local= /lib/gcc5 -isystem /usr/local/include -fno-strict-aliasing -flto -fvisibili= ty=3Dhidden -c tre-ast.c -o tre-ast.o gcc5 -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG = -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp = -fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -Wl,-rpath=3D/usr/local= /lib/gcc5 -isystem /usr/local/include -fno-strict-aliasing -flto -fvisibili= ty=3Dhidden -c tre-compile.c -o tre-compile.o gcc5 -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG = -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp = -fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -Wl,-rpath=3D/usr/local= /lib/gcc5 -isystem /usr/local/include -fno-strict-aliasing -flto -fvisibili= ty=3Dhidden -c tre-match-approx.c -o tre-match-approx.o gcc5 -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG = -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp = -fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -Wl,-rpath=3D/usr/local= /lib/gcc5 -isystem /usr/local/include -fno-strict-aliasing -flto -fvisibili= ty=3Dhidden -c tre-match-backtrack.c -o tre-match-backtrack.o gcc5 -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG = -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp = -fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -Wl,-rpath=3D/usr/local= /lib/gcc5 -isystem /usr/local/include -fno-strict-aliasing -flto -fvisibili= ty=3Dhidden -c tre-match-parallel.c -o tre-match-parallel.o gcc5 -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG = -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp = -fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -Wl,-rpath=3D/usr/local= /lib/gcc5 -isystem /usr/local/include -fno-strict-aliasing -flto -fvisibili= ty=3Dhidden -c tre-mem.c -o tre-mem.o gcc5 -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG = -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp = -fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -Wl,-rpath=3D/usr/local= /lib/gcc5 -isystem /usr/local/include -fno-strict-aliasing -flto -fvisibili= ty=3Dhidden -c tre-parse.c -o tre-parse.o gcc5 -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG = -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp = -fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -Wl,-rpath=3D/usr/local= /lib/gcc5 -isystem /usr/local/include -fno-strict-aliasing -flto -fvisibili= ty=3Dhidden -c tre-stack.c -o tre-stack.o gcc5 -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG = -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp = -fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -Wl,-rpath=3D/usr/local= /lib/gcc5 -isystem /usr/local/include -fno-strict-aliasing -flto -fvisibili= ty=3Dhidden -c xmalloc.c -o xmalloc.o /usr/local/bin/gcc-ar5 -cr libtre.a regcomp.o regerror.o regexec.o tre-ast.= o tre-compile.o tre-match-approx.o tre-match-backtrack.o tre-match-parallel= =2Eo tre-mem.o tre-parse.o tre-stack.o xmalloc.o ar: unrecognized option `--plugin' usage: ar -d [-Tjsvz] archive file ... ar -m [-Tjsvz] archive file ... ar -m [-Tabijsvz] position archive file ... ar -p [-Tv] archive [file ...] ar -q [-TcDjsUvz] archive file ... ar -r [-TcDjsUuvz] archive file ... ar -r [-TabcDijsUuvz] position archive file ... ar -s [-jz] archive ar -t [-Tv] archive [file ...] ar -x [-CTouv] archive [file ...] ar -V *** Error code 64 Stop. make[6]: stopped in /common/ports/math/R/work/R-3.4.0/src/extra/tre *** Error code 1 [and things don't improve after that.] Poking around, I see: g1-227(11.1)[3] pkg which /usr/local/bin/gcc-ar5 /usr/local/bin/gcc-ar5 was installed by package gcc5-5.4.0_2 I confess I don't really see (from the command listed) how gcc-ar5 thought it was being told to use the '--plugin' option, but ... . Most recent update to the math/R port was to the Makefile: ------------------------------------------------------------------------ r444463 | sunpoet | 2017-06-27 06:46:53 -0700 (Tue, 27 Jun 2017) | 11 lines Update devel/readline to 7.0 patch 3 - Bump PORTREVISION for shlib change Changes: https://cnswww.cns.cwru.edu/php/chet/readline/CHANGES https://lists.gnu.org/archive/html/bug-bash/2016-09/msg0010= 7.html https://lists.gnu.org/archive/html/bug-readline/2017-01/msg= 00002.html Differential Revision: https://reviews.freebsd.org/D11172 PR: 219947 Exp-run by: antoine ------------------------------------------------------------------------ Suggestions for getting math/R (and, I presume, databases/R-cran-DBI) to build? Thanks! Peace, david --=20 David H. Wolfskill david@catwhisker.org I look forward to voting against Trump again at the earliest opportunity. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --DtJW00gg9Uj+27As Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJZU5xLXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XGbwH/0Src3JbaHqCDq+Tzk6/OH5b fgixTz+ZsJljQNVBDj1IayO2bwO+odD03zLsT8YDhRXR+jFAzeTLVjo9JZ8NYgBt htPsRfi0Gu0snCqyjCSiGIy2LVyzLkN0bL7nfTEvT8WpaDBgD2f61pk+ETKpHVpx t0Nzq6DHnAoQhlcj7pfvljDSbIHXnT9jHV2l56RcRMfARNDPzpNfUWlYV43SdbUb qEWQQrSBU2vJgkBEu+PHgNxKZPnBDcBUkR2aaUxD55+aBBhEMCZG2YSxrwZ+p9pd DpIWB5hMGO+z4SfabiYXV1cZ5jntTxjjQGAfkjQJwC2I44RaCOrs9HB1/jnR7Qo= =D0E9 -----END PGP SIGNATURE----- --DtJW00gg9Uj+27As-- From owner-freebsd-ports@freebsd.org Wed Jun 28 12:20: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 2DD80DA1047 for ; Wed, 28 Jun 2017 12:20:31 +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 0C29B76D9E for ; Wed, 28 Jun 2017 12:20:31 +0000 (UTC) (envelope-from scratch65535@att.net) Received: by mailman.ysv.freebsd.org (Postfix) id 0B6B8DA1046; Wed, 28 Jun 2017 12:20:31 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0AEF4DA1045 for ; Wed, 28 Jun 2017 12:20:31 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm7.access.bullet.mail.bf1.yahoo.com (nm7.access.bullet.mail.bf1.yahoo.com [216.109.114.69]) (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 C552376D9D for ; Wed, 28 Jun 2017 12:20:30 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1498652325; bh=QSRKwiN7TSNybKjVMCdRsQwh1lRP4Ui9HvVPfksspFc=; h=From:To:Cc:Subject:Date:References:In-Reply-To:From:Subject; b=ymMH4bC4xI2e82A6ZGBpRDQfP0ZtSnLg476gQOQrPWN3kbIImoA+H4t7gs0LIguKknG2jjf9wmGvS4tiYhGRzZgFcALAX88ehbNtCp5AuTs6YqIR9DIbrGIAv/XVldvQVt+leySw6MkzYhfsT4/JOD1F4c8yAvREDHvaqG1NM4Y= Received: from [66.196.81.161] by nm7.access.bullet.mail.bf1.yahoo.com with NNFMP; 28 Jun 2017 12:18:45 -0000 Received: from [98.139.244.52] by tm7.access.bullet.mail.bf1.yahoo.com with NNFMP; 28 Jun 2017 12:18:45 -0000 Received: from [127.0.0.1] by smtp114.sbc.mail.bf1.yahoo.com with NNFMP; 28 Jun 2017 12:18:45 -0000 X-Yahoo-Newman-Id: 803420.57375.bm@smtp114.sbc.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: E4i7ppAVM1mA64NXod.IciTKY07uv28mcCHy7zkeZ0ndDxR IcrrHiipYkZw9ys63G8HzWxzJRVerJajo12LLscjriUg3LzhETD6TvSJVFdc quK2gipNTKSLMNpCdzz9SwayqSOfpXay_4geBa5O7eIdDRZIeCbfmozAIFxL avySWW44FFhN7Pny2dFuOfnw2P0LtIKS55hrKvqgsCXpHNR5.ybXqP2Rgrm_ y8SnxlHryiWkdmRTUic4oKucd7GyoTA0iWBCz1.HsKgHp5k_4BW5qcodTNZ8 wAT7HrmPONRd9IHADlGRwXjxfT2cyVeJdou4gNoUIftf96hltTkIqdlGi7v2 QzedWElU9gpBWRxFxV2P_9uMTXEQZ8ulChc5Oh_1FonzIkDeQsK4keBLzVhw Ei33jQf87VBnlO.GQaPK_fc_yZxFigzzoCLOZXX.pcGFphOYcRg3aQfnNSy5 29RUCWHwo9NaQpM6EQMq4Lt0NJyVmTSA2djBIodcP53QE07rmn3RR.8Mv4Je OyrAXD9DcnML0xKxFZDgGf6KhDdsWjnZpbG0wiRi07nFNqqDIoJtLxlFLS9h ua02155rAhDRudEtbrzhn X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: Mark Linimon Cc: freebsd-ports Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Date: Wed, 28 Jun 2017 08:19:01 -0400 Message-ID: References: <2f23f3d0-dcb1-dc12-eb9f-c8966a10f5f7@toco-domains.de> <77c15a0a-fde0-b240-803e-b369ebf0b897@gjunka.com> <20170627174534.GA29356@lonesome.com> <20170627231600.GB30811@lonesome.com> In-Reply-To: <20170627231600.GB30811@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: Wed, 28 Jun 2017 12:20:31 -0000 On Tue, 27 Jun 2017 18:16:01 -0500, Mark Linimon wrote: >On Tue, Jun 27, 2017 at 04:53:36PM -0400, scratch65535@att.net wrote: >> Since that's what I integrate for my dev use, I'd be happy to >> take a zero'th-order cut at defining it, if nobody else wants to. > >Fine. See http://www.lonesome.com/FreeBSD/poudriere/subsets/ for what >I use. I'm not particularly interested in maintaining it as a general >set of files, but if someone can build on it, fine. Okay, I'll hae a keik. > >> By "unnecessary", Mark, I mean the fact that the bits are not >> controlled locally, and thus potentially change from moment to >> moment such that it's impossible to guarantee that two people >> building the same app with the same options on two different >> days, or even hours, will get the same result. > >I don't understand this. > >The distinfo mechanism is the solution for this problem for released >code. > >If people are relying on "whatever is in git at the moment" to >mean "release", well then that's upstream not understanding what >is meant by "release". Either educated them or fork their code >and become the new upstream. No, I'm talking about how when trying to build a port, even if using only the defaults, the process often fails to run to completion. And the failure is nearly always because some glop of bits being fetched from godknowswhere.edu has gone missing, or has been upped and is now the wrong version as far as the makefile is concerned, or has some other problem. Since I believe that 90% or more of our maintainers are conscientious and build at least the default config, I can only suppose, when the make fails, that somebody over at godknowswhere.edu decided to do something ad-hoc, and that "something" broke the build. This happens so often that I don't even try to build from ports any more ---my own work already supplies more craziness than I can use. > >> Switching to a central repository model, where the bits are >> fetched from around the globe only once per cycle, sanitised, and >> thereafter read only from the repository, would drop the number >> of file-not-founds and wrong-versions down pretty close to zero. > >Again, I simply don't understand this. If we controlled the bits from which ports were built, then nobody (I hope!!) would be changing them in an ad-hoc way, which *should* make every build run to completion without file-not-found etc. > >> >No one has ever done the work on "most minimal set of dependencies" >> >in the ports tree -- and that's because it's hard work. Add to that >> >the fact that the technology has never supported partial checkouts >> >and it complicates things. >> >> No argument from me! IMO a big contributor to the problem is >> that the bits haven't been normalised and integrated into >> libraries. So the process is frankensteinean: odds and bobs >> dredged up wherever they can be found and stuck together in hope >> that they'll cooperate. > >And this is where the hard work lies. > >By comparison, defining "which ports are canonical" is easy. > >IMHO. I can only repeat that you'll get no argument from me! But that's the basic advantage of libraries: do the hard work once, benefit from it forever (fsvo "once" and "forever"). Or do the work forever, and benefit each time only once. From owner-freebsd-ports@freebsd.org Wed Jun 28 12:46: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 8699EDA1D0E for ; Wed, 28 Jun 2017 12:46:25 +0000 (UTC) (envelope-from andyf@andyit.com.au) Received: from alpine.spintel.net.au (alpine.spintel.net.au [IPv6:2407:e400:1::b]) (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 2C335780D6 for ; Wed, 28 Jun 2017 12:46:25 +0000 (UTC) (envelope-from andyf@andyit.com.au) Received: from drunkfish.andyit.com.au (unknown [210.1.210.40]) by alpine.spintel.net.au (Postfix) with ESMTPS id 62FCE4C2B00 for ; Wed, 28 Jun 2017 22:46:18 +1000 (AEST) Received: from snuggles.andyit.com.au (snuggles.andyit.com.au [172.22.2.2]) by drunkfish.andyit.com.au (8.15.2/8.15.2) with ESMTP id v5SCkHsk070772 for ; Wed, 28 Jun 2017 22:46:17 +1000 (AEST) (envelope-from andyf@andyit.com.au) Message-ID: <5953A519.9080500@andyit.com.au> Date: Wed, 28 Jun 2017 22:46:17 +1000 From: Andy Farkas User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120614 Thunderbird/13.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: 'pkg version' strangeness - No valid entries found References: <595383D7.70704@andyit.com.au> <6F66E187-08D9-4C2F-866B-9102A09ACC93@adamw.org> In-Reply-To: <6F66E187-08D9-4C2F-866B-9102A09ACC93@adamw.org> Content-Type: text/plain; charset=us-ascii; 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, 28 Jun 2017 12:46:25 -0000 On 28/06/2017 22:01, Adam Weinberger wrote: > > It may be a typo in your make.conf. > > If you have > DEFAULT_VERSIONS+= perl5=lang/perl5.22 > It should be > DEFAULT_VERSIONS+= perl5=5.22 > > # Adam > root# cat /etc/make.conf cat: /etc/make.conf: No such file or directory -andyf From owner-freebsd-ports@freebsd.org Wed Jun 28 14:45: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 3FE26DA3A5A for ; Wed, 28 Jun 2017 14:45:36 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-23.reflexion.net [208.70.210.23]) (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 E738A7BDBB for ; Wed, 28 Jun 2017 14:45:35 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 6933 invoked from network); 28 Jun 2017 14:38:54 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 28 Jun 2017 14:38:54 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.1) with SMTP; Wed, 28 Jun 2017 10:38:54 -0400 (EDT) Received: (qmail 25256 invoked from network); 28 Jun 2017 14:38:54 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 28 Jun 2017 14:38:54 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 8936BEC9004; Wed, 28 Jun 2017 07:38:53 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work From: Mark Millard In-Reply-To: <82A991B0-FD8B-457F-8483-D61AE5E6D6F6@pfeifer.com> Date: Wed, 28 Jun 2017 07:38:52 -0700 Cc: papowell@astart.com, FreeBSD-STABLE Mailing List , FreeBSD Toolchain , FreeBSD Ports , Pedro Giffuni Content-Transfer-Encoding: quoted-printable Message-Id: References: <6FD738D6-F163-4BC5-8E6E-A9B9F35595CD@dsl-only.net> <82A991B0-FD8B-457F-8483-D61AE5E6D6F6@pfeifer.com> To: Gerald Pfeifer 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: Wed, 28 Jun 2017 14:45:36 -0000 On 2017-Jun-28, at 3:21 AM, Gerald Pfeifer wrote: > I am testing a patch for gcc5-devel right now that will disable = fixincludes (or rather its fixed files) being packaged. >=20 > Should that work fine for you, I will push this back to gcc5 the = following days. >=20 > That said, the change that triggered this is what I would expect on = CURRENT, not STABLE (and hence hoped we'd have more time for this = change). >=20 > My Internet connectivity right now is only slightly above pigeon = speed, so sorry for any delays. Thanks! Some notes: A primary test is building lang/gcc5-devel under release/11.0.1 and then using it under stable/11 or some draft of release/11.1.0 . It looks like the the lang/gcc5-devel build still creates and uses the headers that go in include-fixed/ but that they are removed from $(STAGEDIR}${TARGLIB} 's tree before installation or packaging. So, if I understand right, lang/gcc5-devel itself still does use the adjusted headers to produce its own materials but when lang/gcc5-devel is used later it does not. Definitely something to be testing since it is a mix overall. Is some form of exp-like run needed that tries to force use of a release/11.0.1 built lang/gcc5-devel (-r444563) to build other things under, say, stable/11 or some draft of release/11.1.0 ? Is this odd combination even possible currently? A normal exp-run on release/11.0.1 without a system version switch being involved also seems appropriate. The same could be said of an exp-run based on a release/11.1.0 draft for both building lang/gcc5-devel and using it to build other things. I had hoped that the Linux =46rom Scratch technique of doing: sed -i 's@\./fixinc\.sh@-c true@' gcc/Makefile.in (or an equivalent) before gcc/Makefile.in is used would allow lang/gcc5-devel to use the same headers in its build that the installed compiler would then use to produce other code --by avoiding generating most of the adjusted files in the first place. But I guess that did not work out. Eventually most of the lang/gcc* 's will need whatever technique is used. Some, such as lang/gcc6-aux, need more done because of binary bootstrap materials being downloaded and used and so the build of lang/gcc6-aux gets the problem and fails before staging happens: the binary-bootstrap materials need to avoid the adjusted headers that they currently contain. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Wed Jun 28 15:11: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 81AB3DA4341 for ; Wed, 28 Jun 2017 15:11:49 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from anny.lostinspace.de (anny.lostinspace.de [IPv6:2001:608:a02::33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 44CAF7CBE6 for ; Wed, 28 Jun 2017 15:11:49 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from server.idefix.lan (aftr-88-217-181-241.dynamic.mnet-online.de [88.217.181.241]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: idefix@fechner.net) by anny.lostinspace.de (Postfix) with ESMTPSA id 3DFACC0E11D for ; Wed, 28 Jun 2017 17:11:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=fechner.net; s=default; t=1498662707; bh=CWy4Ll/cYJt2WCCiNyxtel0HFQInPK8fpfDGhvSBRu4=; h=Subject:To:References:From:Date:In-Reply-To; b=MGn3WK5O2+kgTq+foJPwoP7aTVnqVfc05Df2eiboAkhiOe6SGlYXe3pZKobOE+8yL uI/fFQV9bi5VERiQacCNf9kyQJudYM56+iTrHECymMaJqMzJtuGaFZWBJRZvwuEl+f 5YvJXOd9vNICmLBeGN8iA4w3Bo7bszTfVrzzrAeU= Received: from [192.168.0.151] (aftr-88-217-181-241.dynamic.mnet-online.de [88.217.181.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by server.idefix.lan (Postfix) with ESMTPSA id E77A4CDA68A for ; Wed, 28 Jun 2017 17:11:44 +0200 (CEST) Subject: Re: Should a package restart on upgrade itself To: freebsd-ports@freebsd.org References: <20170627163502.u2m4trqccbkri63j@ivaldir.net> <4aad148bce4cfc626dea0d31bd62be41@acheronmedia.com> <77b3c4e0b39e561fc808ce42c7983c2c@acheronmedia.com> <5952AE26.6090504@quip.cz> From: Matthias Fechner Message-ID: Date: Tue, 27 Jun 2017 22:53:50 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 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: Wed, 28 Jun 2017 15:11:49 -0000 Am 27.06.2017 um 21:18 schrieb Vlad K.: > Which is my point. pkg might not upgrade postgresql96-server because > the version of THAT package didn't change, but you'll see in the > output of Poudriere bulk that postgresql96-server was rebuilt because, > say, libxml was updated or rebuilt because, in turn, some of its own > dependency updated. > > That's why Poudriere's bulk output is the best list to check what you > might want to restart, IMHO. > thanks for all your feedback. So I will stick on manually restarting services which require it and lsop is really helpfull therefor. Gruß Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook From owner-freebsd-ports@freebsd.org Wed Jun 28 19:52: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 57E65DA8FC0 for ; Wed, 28 Jun 2017 19:52:03 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2BEE0759; Wed, 28 Jun 2017 19:52:02 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v5SJptqe044579; Wed, 28 Jun 2017 19:51:55 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v5SJptBQ044578; Wed, 28 Jun 2017 12:51:55 -0700 (PDT) (envelope-from david) Date: Wed, 28 Jun 2017 12:51:55 -0700 From: David Wolfskill To: Joseph Mingrone Cc: freebsd-ports@freebsd.org Subject: Re: math/R: Build failure after PORTREVISION for shlib change Message-ID: <20170628195155.GC1241@albert.catwhisker.org> References: <20170628120843.GG1241@albert.catwhisker.org> <86y3sbdhvx.fsf@phe.ftfl.ca> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="y6IdC9+/ilDqdjNX" Content-Disposition: inline In-Reply-To: <86y3sbdhvx.fsf@phe.ftfl.ca> 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: Wed, 28 Jun 2017 19:52:03 -0000 --y6IdC9+/ilDqdjNX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 28, 2017 at 04:36:18PM -0300, Joseph Mingrone wrote: > Hi David, >=20 > So far I haven't been able to reproduce any problems in an > 11.0-RELEASE-p1 jail. Could you send your list of port options? If I > can't reproduce any issues with the same options turned on, I will ask > you for a full build log. >=20 > Joseph Thanks for taking a look. g1-227(11.1)[2] make -C /usr/ports/math/R showconfig =3D=3D=3D> The following configuration options are available for R-3.4.0_1: ICU=3Don: Unicode support via ICU INFO=3Don: GNU info manuals LDOUBLE=3Don: Long double data type LETTER=3Don: US letter paper LIBR=3Don: Shared R library MEMPROF=3Doff: Memory profiling via Rprofmem() and tracemem() NLS=3Don: Native Language Support RPROF=3Don: R profiling via Rprof() X11=3Don: X11 graphics device =3D=3D=3D=3D> Require GCC LTO=3Don: Use Link Time Optimization OPENMP=3Don: Parallel processing support via OpenMP =3D=3D=3D=3D> Require X11 GHOSTSCRIPT=3Don: Graphics device for bitmap files via Ghostscript JPEG=3Don: JPEG graphics device CAIROPANGO=3Don: Cairo graphics device and Pango multi-language text PNG=3Don: PNG graphics device TCLTK=3Don: Tcl/Tk GUI toolkit support TEXDOCS=3Don: Build/Install TeX-dependent documentation files TIFF=3Don: TIFF image format support =3D=3D=3D=3D> Options available for the single BLAS: you have to select exa= ctly one of them ATLAS=3Doff: ATLAS BLAS implementation OPENBLAS=3Doff: OpenBLAS BLAS implementation NETLIB=3Doff: Netlib BLAS implementation RBLAS=3Don: Use R-bundled BLAS implementation =3D=3D=3D> Use 'make config' to modify these settings g1-227(11.1)[3]=20 I also placed both "normal" and gzipped copies of the typescript =66rom the (multiple) portmaster runs in ; see R.log (or R.log.gz). (I had run portmaster; it built a few things, tried math/R & died. I re-started portmaster, eliding math/R, but portmaster found it anyway... though it didn't show up in the list until several other ports were built successfully. I then tried again, skipping both math/R and databases/R-cran-DBI; all of the specified ports built OK. Then I tried just math/R & databases/R-cran-DBI; those failed (as before). I then specified 'MAKE_JOBS_UNSAFE=3Dyes' in /etc/make.conf & tried the laast run again; still failed. Each time, I appended to the typescript.) Just in case it's relevant, as /usr/local/bin/gcc-ar5 is from gcc5-5.4.0_2: g1-227(11.1)[5] make -C /usr/ports/lang/gcc5 showconfig =3D=3D=3D> The following configuration options are available for gcc5-5.4.0= _2: BOOTSTRAP=3Don: Build using a full bootstrap GRAPHITE=3Doff: Support for Graphite loop optimizations JAVA=3Don: Java platform support =3D=3D=3D> Use 'make config' to modify these settings Peace, david --=20 David H. Wolfskill david@catwhisker.org Do Congress's recent actions on health care qualify as "terrorist acts?" See http://www.catwhisker.org/~david/publickey.gpg for my public key. --y6IdC9+/ilDqdjNX Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJZVAjbXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XBv4IANQEL3D6gMfk69TMi/x73448 6RGNg4K9kOE4dDsDS/QZe48EG2iieVuEE2oAxAGyeomfR6mH0Ju0yYWUa1J+cgVW HbWFIGD4A5gHFQjgvz6useOvS+KNWa9oayKWBHtmEugsUDf9SXMcRxfh5CyOvE/w 0kJu2H4hrIQq1b+3z18w1cXUEhqC3wKShEUm6x85rhfDVKy5di71DPU5iDT+7CTc r+6q6IGfEi3YZazSwpekYO0ifX+hbbajYktZrN/vd2xhbT8efS/8E5lB0thH9l9h ZIzILfbhKJ7UlYsF/+7mywAjN3dgnWmvUuGNCMGYdyPudPMPgSpMSfkIeaPztkk= =czsx -----END PGP SIGNATURE----- --y6IdC9+/ilDqdjNX-- From owner-freebsd-ports@freebsd.org Wed Jun 28 21:05: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 2EA02DA9D15 for ; Wed, 28 Jun 2017 21:05:16 +0000 (UTC) (envelope-from dirk.meyer@dinoex.sub.org) Received: from uucp.dinoex.sub.de (uucp.dinoex.sub.de [IPv6:2001:1440:5001:1::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "uucp.dinoex.sub.de", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A38C0273B for ; Wed, 28 Jun 2017 21:05:15 +0000 (UTC) (envelope-from dirk.meyer@dinoex.sub.org) Received: from uucp.dinoex.sub.de (uucp.dinoex.sub.de [194.45.71.2]) by uucp.dinoex.sub.de (8.15.2/8.14.9) with ESMTPS id v5SL50ES033196 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 28 Jun 2017 23:05:00 +0200 (CEST) (envelope-from dirk.meyer@dinoex.sub.org) X-MDaemon-Deliver-To: Received: from bamd10.dinoex.sub.de (dinoex@localhost) by uucp.dinoex.sub.de (8.15.2/8.14.9/Submit) with BSMTP id v5SL50rI033176 for ; Wed, 28 Jun 2017 23:05:00 +0200 (CEST) (envelope-from dirk.meyer@dinoex.sub.org) To: freebsd-ports@freebsd.org Message-ID: From: dirk.meyer@dinoex.sub.org (Dirk Meyer) Organization: privat Subject: Re: [RFC] Why FreeBSD ports should have branches by OS version Date: Wed, 28 Jun 2017 23:02:59 +0200 X-Mailer: Dinoex 1.79 References: <61.E4.01815.93B02595@dnvrco-omsmta03> <201706271008.v5RA8GUf099489@fire.js.berklix.net> X-Gateway: ZCONNECT bamd10.dinoex.sub.de [UNIX/Connect 0.94] X-PGP-Fingerprint: 44 16 EC 0A D3 3A 4F 28 8A 8A 47 93 F1 CF 2F 12 X-Copyright: (C) Copyright 2001 by Dirk Meyer -- All rights reserved. X-PGP-Key-Avail: mailto:pgp-public-keys@keys.de.pgp.net Subject:GET 0x331CDA5D X-ZC-VIA: 20170628000000S+2@dinoex.sub.org X-Milter: Spamilter (Reciever: uucp.dinoex.sub.de; Sender-ip: 194.45.71.2; Sender-helo: uucp.dinoex.sub.de; ) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (uucp.dinoex.sub.de [194.45.71.2]); Wed, 28 Jun 2017 23:05:01 +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: Wed, 28 Jun 2017 21:05:16 -0000 Hallo Julian H. Stacey, > But if one stands on a broken system & needs to recover, some simple > stock cc & sh tool/procedure with no dependencies is attractive, even if > one has to coble something ones self. I agree. maybe you like to try: $ less /usr/ports/ports-mgmt/pkg_jail/files/README kind regards Dirk - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany - [dirk.meyer@dinoex.sub.org],[dirk.meyer@guug.de],[dinoex@FreeBSD.org] From owner-freebsd-ports@freebsd.org Wed Jun 28 21:09:35 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 74389DA9E3C for ; Wed, 28 Jun 2017 21:09:35 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: from mail-qk0-f171.google.com (mail-qk0-f171.google.com [209.85.220.171]) (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 39A8E29A0 for ; Wed, 28 Jun 2017 21:09:34 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: by mail-qk0-f171.google.com with SMTP id p21so61686899qke.3 for ; Wed, 28 Jun 2017 14:09:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=8/0t1JGMM4NNHiQAJxQ9nLBFH9BGoTBsL2wd4sqgtOU=; b=FEsG+PjjruLAgS1R1AtzlPVMr4SFu10s7aEbdih8F1cXrTCXGjI567ex7/JNA9vfUK o85OhR2GkbD81ToxB0RCIyyBC/I1WWavSctXhv/9KrojFr4glYAhjcDo8cjlAURy1P1v FiB+BTEPoYf6Q29PVBEwgugQBl7PXmDXFBWrb29WHIzrK8bDsBqijbOfvPIcrcA8kjRK PvHDY6CQylTYeZi8JLwKE2irrMb41vLet6JNtpNDocPtipgFXdFIUCSAqGnrWknIY7hb Xe7yRn0MNvNiYyfAbi4+hrQ5KHo9nzqphKnXEk3MJcaOLGG4D+JRypqgEUp5t0/n8nfd sr6w== X-Gm-Message-State: AKS2vOwWmdjRczT55EBmgbKCm0gFLDHllxWzu1iqeWILHpeZZ0Sy5y/k gpnSfUSPztgkdzj8FadQuQ== X-Received: by 10.55.146.133 with SMTP id u127mr15191713qkd.17.1498678580862; Wed, 28 Jun 2017 12:36:20 -0700 (PDT) Received: from phe.ftfl.ca.ftfl.ca (hlfxns017vw-142-68-134-140.dhcp-dynamic.fibreop.ns.bellaliant.net. [142.68.134.140]) by smtp.gmail.com with ESMTPSA id j17sm2331840qta.49.2017.06.28.12.36.19 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 28 Jun 2017 12:36:19 -0700 (PDT) From: Joseph Mingrone To: David Wolfskill Cc: freebsd-ports@freebsd.org Subject: Re: math/R: Build failure after PORTREVISION for shlib change References: <20170628120843.GG1241@albert.catwhisker.org> Date: Wed, 28 Jun 2017 16:36:18 -0300 In-Reply-To: <20170628120843.GG1241@albert.catwhisker.org> (David Wolfskill's message of "Wed, 28 Jun 2017 05:08:43 -0700") Message-ID: <86y3sbdhvx.fsf@phe.ftfl.ca> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jun 2017 21:09:35 -0000 --=-=-= Content-Type: text/plain Hi David, So far I haven't been able to reproduce any problems in an 11.0-RELEASE-p1 jail. Could you send your list of port options? If I can't reproduce any issues with the same options turned on, I will ask you for a full build log. Joseph --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEVbCTpybDiFVxIrrVNqQMg7DW754FAllUBTJfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDU1 QjA5M0E3MjZDMzg4NTU3MTIyQkFENTM2QTQwQzgzQjBENkVGOUUACgkQNqQMg7DW 757Dqg//azeXO2s05lQVMCnKO/uVl+oK4Imis6Bcv0Sah3hRSZVFtnZmmkSq5XsU 3YtQXZ67663zm2SIQoe8uMtav3tqgQZhf/APazoN5icRSM36NpuOEhTg0GmC6BD8 /vkVkQkrvq4FIqMt6IJvqO7Ze8sdQRliYXNUB4xFFWlQz/7SjvjrTd6zOSjH+d3X Gs1NenA7drB9b9N7/PWYB6xSTgi+7Jv98W7U2fdtCfzmB6WIiBKd4xLttnVwLmKR WXFvXddBhPJsiU0UeECldAkcTaENi6Vn+nahWe73e5R9HhDYwcR86wqhIk3+BED2 8kFp1+F5oAGt2L1jlt+NLmk1B852dO2WFFZhhBmeZwtRGGMPfvm54MbEd9eUJhBd oGWL6qIFh/l0ovHkFvNqlGFnUOdzvXgj/iUUNbI451XVLwLXbVc7I1jBtl/HXi1m fprWU6JJ1B2hbUoAtVoVsIWHxBRovT6vGlX/bCHBgadYhg0u5/GmgCyJLgUvMNWR Pt8MwbN24zpFeDEP1WVXB37xF5ItUdQ3zOmZs1VjEGpJaUx032bkFm3dNn4Ez2/7 Lo6tke9I8ItURiuLXpPGRzEkP2igKJJC0McWV9LNYswzNrTJiHZYYrPnR9fJjMs9 FH/LQ+Jird5CTrrNYUaYjFE8OFoVNGK6jz9E1Y2LgVmsGji5ewY= =XSgl -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-ports@freebsd.org Wed Jun 28 23:25:37 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 81BDED869AF; Wed, 28 Jun 2017 23:25:37 +0000 (UTC) (envelope-from helen.koike@collabora.com) Received: from bhuna.collabora.co.uk (bhuna.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e3e3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "bhuna.collabora.co.uk", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F04F65F78; Wed, 28 Jun 2017 23:25:31 +0000 (UTC) (envelope-from helen.koike@collabora.com) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: koike) with ESMTPSA id 0DB0A260868 To: freebsd-ports@freebsd.org, freebsd-cloud@freebsd.org, swills@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org From: Helen Koike Subject: review of google-compute-engine: better quality of the GCE image Message-ID: <7cb3a2dc-7353-9ade-5e70-4538db90083f@collabora.com> Date: Wed, 28 Jun 2017 20:25:20 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 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, 28 Jun 2017 23:25:37 -0000 Hi, In order to increase the quality of the FreeBSD image for the Google Cloud Engine platform, having the package google-compute-engine would enable several features that allows the machine to be controlled by the GCE tools (web console or gcloud) and other security features, so FreeBSD wouldn't stay behind the other distributions on this. I would really appreciate if anyone could review this package so it can be included in the FreeBSD ports, please, see more details in the link below: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219687 Thanks LN Koike From owner-freebsd-ports@freebsd.org Thu Jun 29 02:44: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 EA273D8E426 for ; Thu, 29 Jun 2017 02:44:39 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-15.reflexion.net [208.70.210.15]) (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 9FBC671662 for ; Thu, 29 Jun 2017 02:44:39 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 16932 invoked from network); 29 Jun 2017 02:44:37 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 29 Jun 2017 02:44:37 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.1) with SMTP; Wed, 28 Jun 2017 22:44:37 -0400 (EDT) Received: (qmail 6968 invoked from network); 29 Jun 2017 02:44:37 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 29 Jun 2017 02:44:37 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id F0799EC8AEE; Wed, 28 Jun 2017 19:44:36 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: /usr/ports -r444615 (e.g.) & head -r320458 (e.g.): sysutils/u-boot-pine64 build fails for arch/arm/dts/pine64_plus.dtb source handling error (gic in a64.dtsi) Message-Id: <746945FA-AFCD-40FE-AF7E-875B89EC1B4A@dsl-only.net> Date: Wed, 28 Jun 2017 19:44:36 -0700 To: Emmanuel Vadot , freebsd-arm , FreeBSD Toolchain , FreeBSD Ports 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: Thu, 29 Jun 2017 02:44:40 -0000 Is the below a BSDL vs. GPL DTS issue? In my attempt to build sysutils/u-boot-pine64 I got: OBJCOPY u-boot.srec OBJCOPY u-boot-nodtb.bin start=3D$(aarch64-none-elf-nm u-boot | grep __rel_dyn_start | cut -f 1 = -d ' '); end=3D$(aarch64-none-elf-nm u-boot | grep __rel_dyn_end | cut = -f 1 -d ' '); tools/relocate-rela u-boot-nodtb.bin 0x4a000000 $start = $end SYM u-boot.sym DTC arch/arm/dts/pine64_plus.dtb Error at arch/arm/dts/.pine64_plus.dtb.dts.tmp:533:27: Expected unit = address gic: interrupt-controller@{ ^ Error at arch/arm/dts/.pine64_plus.dtb.dts.tmp:533:27: Failed to find = root node /. gic: interrupt-controller@{ ^ Failed to parse tree. gmake[3]: *** [scripts/Makefile.lib:299: arch/arm/dts/pine64_plus.dtb] = Error 1 gmake[2]: *** [dts/Makefile:36: arch-dtbs] Error 2 gmake[1]: *** [Makefile:821: dts/dt.dtb] Error 2 gmake[1]: *** Waiting for unfinished jobs.... gmake[1]: Leaving directory = '/usr/obj/portswork/usr/ports/sysutils/u-boot-pine64/work/u-boot-2016.05' Looking at the gic part of the source. . . # more = /usr/obj/portswork/usr/ports/sysutils/u-boot-pine64/work/u-boot-2016.05/ar= ch/arm/dts/a64.dtsi . . . gic: interrupt-controller@{ compatible =3D "arm,gic-400"; interrupt-controller; #interrupt-cells =3D <3>; #address-cells =3D <0>; reg =3D <0x01C81000 0x1000>, <0x01C82000 0x2000>, <0x01C84000 0x2000>, <0x01C86000 0x2000>; interrupts =3D ; }; I'll be trying 3 other u-boot-*'s so I may have more to report later. =3D=3D=3D Mark Millard markmi@dsl-only.net From owner-freebsd-ports@freebsd.org Thu Jun 29 03:52:21 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 1ECB4D90B09 for ; Thu, 29 Jun 2017 03:52:21 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-15.reflexion.net [208.70.210.15]) (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 C1AB573B1C for ; Thu, 29 Jun 2017 03:52:19 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 19856 invoked from network); 29 Jun 2017 03:52:18 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 29 Jun 2017 03:52:18 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.1) with SMTP; Wed, 28 Jun 2017 23:52:18 -0400 (EDT) Received: (qmail 19926 invoked from network); 29 Jun 2017 03:52:18 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 29 Jun 2017 03:52:18 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id D7686EC8A8B; Wed, 28 Jun 2017 20:52:17 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: /usr/ports -r444615 (e.g.) & head -r320458 (e.g.): sysutils/u-boot-pine64 build fails for arch/arm/dts/pine64_plus.dtb source handling error (gic in a64.dtsi) From: Mark Millard In-Reply-To: <746945FA-AFCD-40FE-AF7E-875B89EC1B4A@dsl-only.net> Date: Wed, 28 Jun 2017 20:52:17 -0700 Cc: freebsd-arm , FreeBSD Toolchain , FreeBSD Ports Content-Transfer-Encoding: quoted-printable Message-Id: <51D64AB6-5E0A-4210-B3B1-CB236F1C9B39@dsl-only.net> References: <746945FA-AFCD-40FE-AF7E-875B89EC1B4A@dsl-only.net> To: Emmanuel Vadot 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: Thu, 29 Jun 2017 03:52:21 -0000 On 2017-Jun-28, at 7:44 PM, Mark Millard wrote: > Is the below a BSDL vs. GPL DTS issue? >=20 > In my attempt to build sysutils/u-boot-pine64 I got: >=20 > OBJCOPY u-boot.srec > OBJCOPY u-boot-nodtb.bin > start=3D$(aarch64-none-elf-nm u-boot | grep __rel_dyn_start | cut -f 1 = -d ' '); end=3D$(aarch64-none-elf-nm u-boot | grep __rel_dyn_end | cut = -f 1 -d ' '); tools/relocate-rela u-boot-nodtb.bin 0x4a000000 $start = $end > SYM u-boot.sym > DTC arch/arm/dts/pine64_plus.dtb > Error at arch/arm/dts/.pine64_plus.dtb.dts.tmp:533:27: Expected unit = address > gic: interrupt-controller@{ > ^ > Error at arch/arm/dts/.pine64_plus.dtb.dts.tmp:533:27: Failed to find = root node /. > gic: interrupt-controller@{ > ^ > Failed to parse tree. > gmake[3]: *** [scripts/Makefile.lib:299: arch/arm/dts/pine64_plus.dtb] = Error 1 > gmake[2]: *** [dts/Makefile:36: arch-dtbs] Error 2 > gmake[1]: *** [Makefile:821: dts/dt.dtb] Error 2 > gmake[1]: *** Waiting for unfinished jobs.... > gmake[1]: Leaving directory = '/usr/obj/portswork/usr/ports/sysutils/u-boot-pine64/work/u-boot-2016.05' >=20 >=20 >=20 > Looking at the gic part of the source. . . >=20 > # more = /usr/obj/portswork/usr/ports/sysutils/u-boot-pine64/work/u-boot-2016.05/ar= ch/arm/dts/a64.dtsi > . . . > gic: interrupt-controller@{ > compatible =3D "arm,gic-400"; > interrupt-controller; > #interrupt-cells =3D <3>; > #address-cells =3D <0>; >=20 > reg =3D <0x01C81000 0x1000>, > <0x01C82000 0x2000>, > <0x01C84000 0x2000>, > <0x01C86000 0x2000>; > interrupts =3D (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_HIGH)>; > }; >=20 >=20 >=20 > I'll be trying 3 other u-boot-*'s so I may have more to > report later. The other 3 that I tried worked fine: Installation of sysutils/u-boot-rpi2 (u-boot-rpi2-2015.04) Installation of sysutils/u-boot-rpi3 (u-boot-rpi3-2017.01) Installation of sysutils/u-boot-sinovoip-bpi-m3 = (u-boot-sinovoip-bpi-m3-2016.05) So this may be unique to a64.dtsi and its lack of hexadecimal digits after the "@" in what I quoted. Still, sysutils/u-boot-pine64 used to build. So it may be a BSDL vs. GPL DTS issue as far as the handling of the notation goes. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Thu Jun 29 05:41: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 E04DDD93569 for ; Thu, 29 Jun 2017 05:41:52 +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 CD1A376BCD for ; Thu, 29 Jun 2017 05:41:52 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: by mailman.ysv.freebsd.org (Postfix) id CC7C7D93567; Thu, 29 Jun 2017 05:41: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 CC12ED93564 for ; Thu, 29 Jun 2017 05:41:52 +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 A263476BCC for ; Thu, 29 Jun 2017 05:41:52 +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 v5T5cYcG082793 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 28 Jun 2017 22:38:34 -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: What to do when the port fails in poudriere with "Too many open files" ? Message-ID: <3566c5e1-ec79-e5f6-8d70-2cfa446a3e9a@rawbw.com> Date: Wed, 28 Jun 2017 22:38:33 -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: Thu, 29 Jun 2017 05:41:53 -0000 I have the port that builds fine without poudriere, but in poudriere it always fails with "Too many open files". This happens during the Java build. Where is the limit set in jail? /etc/login.conf doesn't have any limit. What to do in such case? Maybe there is some way to tell Java to limit the number of open files? Yuri From owner-freebsd-ports@freebsd.org Thu Jun 29 07:48: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 30D54D95C93; Thu, 29 Jun 2017 07:48:29 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 39DBA79D93; Thu, 29 Jun 2017 07:48:27 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id fa60e2d4; Thu, 29 Jun 2017 09:48:18 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=QjgwgoXTXTe6gY8byXiDbnv1dNQ=; b=SPG/qNdrasbslzMLNDPU1lBRVfNO t5bEsEbTF0wjmyRjv5BLRGw1nvebl0abDsdaute43aPw0GOtzFXUWSorVe3YPf/v dqAn70iNb0BvT+D1VgvyRtBUdx7op98cVSwK9fcgvGerq5qlKlMyA43eDUfjKCGQ Ti6vOIA6VmejVUg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=VNwERX/USSLTVMecPM2D/GG0lZi/C5u29kh+2UeWU+sL/Wu0R3kP3gik AhISmLw0kGS+6nmVWXODBdlovS1bQA2PaaoxMcrJr1Wc/v3xPVd9JNXXg8PPi6V3 XugOvZAx+xhK4D+d1PSF8d8EHyiVEi5Yn0vfRG4xO1cVYW79O1w= Received: from arcadia (evadot.gandi.net [217.70.181.36]) by mail.blih.net (OpenSMTPD) with ESMTPSA id e90134af TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Thu, 29 Jun 2017 09:48:18 +0200 (CEST) Date: Thu, 29 Jun 2017 09:48:18 +0200 From: Emmanuel Vadot To: Mark Millard Cc: Emmanuel Vadot , freebsd-arm , FreeBSD Toolchain , FreeBSD Ports Subject: Re: /usr/ports -r444615 (e.g.) & head -r320458 (e.g.): sysutils/u-boot-pine64 build fails for arch/arm/dts/pine64_plus.dtb source handling error (gic in a64.dtsi) Message-Id: <20170629094818.9c851cde402d80b2de30dc55@bidouilliste.com> In-Reply-To: <51D64AB6-5E0A-4210-B3B1-CB236F1C9B39@dsl-only.net> References: <746945FA-AFCD-40FE-AF7E-875B89EC1B4A@dsl-only.net> <51D64AB6-5E0A-4210-B3B1-CB236F1C9B39@dsl-only.net> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; amd64-portbld-freebsd12.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: Thu, 29 Jun 2017 07:48:29 -0000 Hello Mark, On Wed, 28 Jun 2017 20:52:17 -0700 Mark Millard wrote: > On 2017-Jun-28, at 7:44 PM, Mark Millard wrote: > > > Is the below a BSDL vs. GPL DTS issue? > > > > In my attempt to build sysutils/u-boot-pine64 I got: > > > > OBJCOPY u-boot.srec > > OBJCOPY u-boot-nodtb.bin > > start=$(aarch64-none-elf-nm u-boot | grep __rel_dyn_start | cut -f 1 -d ' '); end=$(aarch64-none-elf-nm u-boot | grep __rel_dyn_end | cut -f 1 -d ' '); tools/relocate-rela u-boot-nodtb.bin 0x4a000000 $start $end > > SYM u-boot.sym > > DTC arch/arm/dts/pine64_plus.dtb > > Error at arch/arm/dts/.pine64_plus.dtb.dts.tmp:533:27: Expected unit address > > gic: interrupt-controller@{ > > ^ > > Error at arch/arm/dts/.pine64_plus.dtb.dts.tmp:533:27: Failed to find root node /. > > gic: interrupt-controller@{ > > ^ > > Failed to parse tree. > > gmake[3]: *** [scripts/Makefile.lib:299: arch/arm/dts/pine64_plus.dtb] Error 1 > > gmake[2]: *** [dts/Makefile:36: arch-dtbs] Error 2 > > gmake[1]: *** [Makefile:821: dts/dt.dtb] Error 2 > > gmake[1]: *** Waiting for unfinished jobs.... > > gmake[1]: Leaving directory '/usr/obj/portswork/usr/ports/sysutils/u-boot-pine64/work/u-boot-2016.05' > > > > > > > > Looking at the gic part of the source. . . > > > > # more /usr/obj/portswork/usr/ports/sysutils/u-boot-pine64/work/u-boot-2016.05/arch/arm/dts/a64.dtsi > > . . . > > gic: interrupt-controller@{ > > compatible = "arm,gic-400"; > > interrupt-controller; > > #interrupt-cells = <3>; > > #address-cells = <0>; > > > > reg = <0x01C81000 0x1000>, > > <0x01C82000 0x2000>, > > <0x01C84000 0x2000>, > > <0x01C86000 0x2000>; > > interrupts = > (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_HIGH)>; > > }; > > Yes the node is wrong but if gpl dtc can handle that maybe we should to, I'll try to find time to fix that. > > > > I'll be trying 3 other u-boot-*'s so I may have more to > > report later. > > The other 3 that I tried worked fine: > > Installation of sysutils/u-boot-rpi2 (u-boot-rpi2-2015.04) > Installation of sysutils/u-boot-rpi3 (u-boot-rpi3-2017.01) > Installation of sysutils/u-boot-sinovoip-bpi-m3 (u-boot-sinovoip-bpi-m3-2016.05) > > So this may be unique to a64.dtsi and its lack of > hexadecimal digits after the "@" in what I quoted. > > Still, sysutils/u-boot-pine64 used to build. So it may > be a BSDL vs. GPL DTS issue as far as the handling of > the notation goes. > > === > Mark Millard > markmi at dsl-only.net I also a patch waiting for comment on the u-boot mailing list that add the possibility to specify which dtc to use, this will be needed for the next u-boot for arm64 board as it uses 'incbin' directive which bsd dtc doesn't support yet (David is looking into it). Anyway, new u-boot should be out around july 10th so I'll update the port right after. Thanks for reporting. -- Emmanuel Vadot From owner-freebsd-ports@freebsd.org Thu Jun 29 08:00: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 00E20D96341 for ; Thu, 29 Jun 2017 08:00:30 +0000 (UTC) (envelope-from matt.xtaz@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 CEF587A41C for ; Thu, 29 Jun 2017 08:00:29 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id CE10ED9633E; Thu, 29 Jun 2017 08:00: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 CDAD6D96339 for ; Thu, 29 Jun 2017 08:00:29 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::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 598ED7A41B for ; Thu, 29 Jun 2017 08:00:29 +0000 (UTC) (envelope-from matt.xtaz@gmail.com) Received: by mail-wm0-x242.google.com with SMTP id y5so954489wmh.3 for ; Thu, 29 Jun 2017 01:00: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=RH4VJGkBcDh1b28FHD6M/xFXvTyfSHD01YIypCFPnZc=; b=qb01W5QtRNPoeT4tfb3lXJmgwhGCgf39kUUIMNT2XS8/DjqqdjCUL+Ny5oG9tzMPBN JMGO2mPmgMjon+HZd9KbClu23b4c8on3tKyIrKVuPl1e2W3SgR3W/MVwaYfSG/Cxvzoy I9a5Ea7gkr72nUnsJhKcoPqmOQ9k4fiaO4gkBLx4iwqnWDkrrAD8+GCs8efNEh4zmQdQ JUUSINcI8mQr7YGCIBz/by5Ruwb2LgWMc3qHZ1rsv7va0/Kh6z3/uQUdhJnosgF39CgK 411WRAQ9adaduwUYTTQaRa8/eUzgqpBV5L8TXQTyBjdxju+12U0MGbS+L5COCsqFj0Kv B3Sw== 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=RH4VJGkBcDh1b28FHD6M/xFXvTyfSHD01YIypCFPnZc=; b=HCTw7o2i7XJAKjXmx9AnAq+qnd7h5U8kz9TYqq+uaEUSJ+A+dJYdi3ZII7mW1qmKix K98PW7UWLxI3Rf2YcdeCLzgWHPIiaIIlj/HQV5Dvu91vQ7UO1yl9DEszgOirOi8XSjHP qc2bqOtHQ/CtFIbIcIS8JsG8ydIKrqTttPdwNolw1BbbcjOruAo1TWsbD1vX8vmo2lGF yIuV0hDqJz6yEp6KJzssQTJh8FTEhTZ63XiYyl1jjPD7CP2t+zoMwM3OP/iOHk65mIX3 qzjtNyqNFbCsOghdmjUrQr011RXKP9Y0jMHGYpGdhJ6CPS1RbnCRGWHfegOBoqtR+qYA pRaA== X-Gm-Message-State: AKS2vOz9I+nd/o8qlBQDU4zG+lxKGGH3fGjdKZHVHYITjsogtFjaj5zO u8mJbH5tlhOANg== X-Received: by 10.28.56.198 with SMTP id f189mr9794780wma.88.1498723227592; Thu, 29 Jun 2017 01:00:27 -0700 (PDT) Received: from gmail.com (tao.xtaz.uk. [2001:8b0:fe33::10]) by smtp.gmail.com with ESMTPSA id q137sm678126wmd.32.2017.06.29.01.00.27 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 29 Jun 2017 01:00:27 -0700 (PDT) Date: Thu, 29 Jun 2017 09:00:24 +0100 From: Matt Smith To: Yuri Cc: "ports@freebsd.org" Subject: Re: What to do when the port fails in poudriere with "Too many open files" ? Message-ID: <20170629080023.GA4442@gmail.com> Mail-Followup-To: Matt Smith , Yuri , "ports@freebsd.org" References: <3566c5e1-ec79-e5f6-8d70-2cfa446a3e9a@rawbw.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <3566c5e1-ec79-e5f6-8d70-2cfa446a3e9a@rawbw.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: Thu, 29 Jun 2017 08:00:30 -0000 On Jun 28 22:38, Yuri wrote: >I have the port that builds fine without poudriere, but in poudriere >it always fails with "Too many open files". > >This happens during the Java build. > > >Where is the limit set in jail? /etc/login.conf doesn't have any limit. > >What to do in such case? Maybe there is some way to tell Java to limit >the number of open files? > > >Yuri > I would take a look at /usr/local/etc/poudriere.conf at the MAX_FILES setting. -- Matt From owner-freebsd-ports@freebsd.org Thu Jun 29 10:10: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 16C8DD98D60; Thu, 29 Jun 2017 10:10:59 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) (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 E2A0C7E4FB; Thu, 29 Jun 2017 10:10:58 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (localhost [127.0.0.1]) by ainaz.pair.com (Postfix) with ESMTP id A7BCB3F4D9; Thu, 29 Jun 2017 06:10:56 -0400 (EDT) Received: from [192.168.1.102] (unknown [202.188.138.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id D30993F4D5; Thu, 29 Jun 2017 06:10:37 -0400 (EDT) Date: Thu, 29 Jun 2017 18:10:16 +0800 User-Agent: K-9 Mail for Android In-Reply-To: References: <6FD738D6-F163-4BC5-8E6E-A9B9F35595CD@dsl-only.net> <82A991B0-FD8B-457F-8483-D61AE5E6D6F6@pfeifer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work To: Mark Millard CC: papowell@astart.com, FreeBSD-STABLE Mailing List , FreeBSD Toolchain , FreeBSD Ports , Pedro Giffuni From: Gerald Pfeifer Message-ID: 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, 29 Jun 2017 10:10:59 -0000 Am 28=2E Juni 2017 22:38:52 GMT+08:00 schrieb Mark Millard : >A primary test is building lang/gcc5-devel under release/11=2E0=2E1 >and then using it under stable/11 or some draft of release/11=2E1=2E0 =2E Thank you, Mark=2E Let me know how it went=2E In the meantime I'll prepare= the change for gcc5 itself=2E >It looks like the the lang/gcc5-devel build still creates and >uses the headers that go in include-fixed/ but that they are >removed from $(STAGEDIR}${TARGLIB} 's tree before installation >or packaging=2E > >So, if I understand right, lang/gcc5-devel itself still does use >the adjusted headers to produce its own materials but when >lang/gcc5-devel is used later it does not=2E Definitely >something to be testing since it is a mix overall=2E I am not worried about that since that should not cause any binary incompa= tibilities (ABI)=2E The problem we encountered was about source code and AP= I in a wide sense of that term=2E >Is some form of exp-like run needed that tries to force use >of a release/11=2E0=2E1 built lang/gcc5-devel (-r444563) to build >other things under, say, stable/11 or some draft of >release/11=2E1=2E0 ? Is this odd combination even possible >currently? I am not aware of it, and while originally I was thinking to request an -e= xp run (after the GCC version update which is dragging due to broken ports)= , time is not on our side and the change should be low risk=2E > [altermative approach] But I guess that did not work out=2E Not with my current level of connectivity and my notebook a dead brick on = top of that=2E And my preference is to still build, but stow away (unless e= xplicitly requested to keep)=2E >Eventually most of the lang/gcc* 's will need whatever >technique is used=2E Yes, agreed=2E Version 5 is most important since it's the default; then 6;= 4=2Ex is for retro computing fans ;-), so 7 will then be next=2E Gerald From owner-freebsd-ports@freebsd.org Thu Jun 29 10: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 8C982D9905C for ; Thu, 29 Jun 2017 10:18:10 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7735E7E9D1 for ; Thu, 29 Jun 2017 10:18:10 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 769CDD99059; Thu, 29 Jun 2017 10: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 764A1D99057 for ; Thu, 29 Jun 2017 10:18:10 +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 680B37E9D0 for ; Thu, 29 Jun 2017 10:18:10 +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 v5TAIAgp093598 for ; Thu, 29 Jun 2017 10:18:10 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v5TAIAXp093597; Thu, 29 Jun 2017 10:18:10 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201706291018.v5TAIAXp093597@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, 29 Jun 2017 10:18:10 +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, 29 Jun 2017 10:18:10 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ graphics/gmt | 4.5.15 | 4.5.16 ------------------------------------------------+-----------------+------------ multimedia/lives | 2.8.4 | 2.8.7 ------------------------------------------------+-----------------+------------ print/mpage | 2.5.6 | 2.5.7 ------------------------------------------------+-----------------+------------ 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 29 10:56: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 8CA67D99C35 for ; Thu, 29 Jun 2017 10:56:02 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-15.reflexion.net [208.70.210.15]) (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 3F0547FBE5 for ; Thu, 29 Jun 2017 10:56:01 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 3100 invoked from network); 29 Jun 2017 11:00:14 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 29 Jun 2017 11:00:14 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.1) with SMTP; Thu, 29 Jun 2017 06:56:00 -0400 (EDT) Received: (qmail 18968 invoked from network); 29 Jun 2017 10:56:00 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 29 Jun 2017 10:56:00 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id A1C33EC7B46; Thu, 29 Jun 2017 03:55:59 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work From: Mark Millard In-Reply-To: Date: Thu, 29 Jun 2017 03:55:59 -0700 Cc: papowell@astart.com, FreeBSD-STABLE Mailing List , FreeBSD Toolchain , FreeBSD Ports , Pedro Giffuni Content-Transfer-Encoding: quoted-printable Message-Id: References: <6FD738D6-F163-4BC5-8E6E-A9B9F35595CD@dsl-only.net> <82A991B0-FD8B-457F-8483-D61AE5E6D6F6@pfeifer.com> To: Gerald Pfeifer 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: Thu, 29 Jun 2017 10:56:02 -0000 On 2017-Jun-29, at 3:10 AM, Gerald Pfeifer = wrote: > Am 28. Juni 2017 22:38:52 GMT+08:00 schrieb Mark Millard : >> A primary test is building lang/gcc5-devel under release/11.0.1 >> and then using it under stable/11 or some draft of release/11.1.0 . >=20 > Thank you, Mark. Let me know how it went. In the meantime I'll prepare = the change for gcc5 itself. I'm not currently set up to run more than head on any of amd64, powerpc64, powerpc, aarch64, or armv6/7 (which are all I target). And I'm in the middle of attempting a fairly large jump to head -r320458 on those. (powerpc 32-bit and 64-bit just failed for libc++ time-usage compiling now that 32-bit has 64-bit time_t, including in world32/lib32 contexts for powerpc64.) It will likely be a while before I manage to have a 11.x context (without losing my head contexts), much less examples from all "my" 5 TARGET_ARCH's. (Given past wchar_t type handling problems (e.g.) for gcc targeting powerpc family members I think it should be checked.) I'll have to find and set up disks: I do not even have such handy/ready at the moment. [I got into this area by being asked questions, not by my direct use of release/11.0.1 , stable/11 , or a draft of release/11.1.0 .] I'll let you know when I have some test results but others may get some before I do. > . . . >> Eventually most of the lang/gcc* 's will need whatever >> technique is used. >=20 > Yes, agreed. Version 5 is most important since it's the default; then = 6; 4.x is for retro computing fans ;-), so 7 will then be next. [In my normal/head environment I'm switching to lang/gcc7-devel for gcc (from lang/gcc6 ) but I'm odd that way.] =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Thu Jun 29 15:40:05 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 72CFAD9FC3C for ; Thu, 29 Jun 2017 15:40:05 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: from mail-qt0-f174.google.com (mail-qt0-f174.google.com [209.85.216.174]) (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 385EB64046 for ; Thu, 29 Jun 2017 15:40:04 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: by mail-qt0-f174.google.com with SMTP id r30so77628524qtc.0 for ; Thu, 29 Jun 2017 08:40:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:message-id :user-agent:mime-version; bh=EwCRnclrYwLqjla2MuYbOgLuPZN93HW5tsMSvt9hZOc=; b=EzhCj8Eh2dsK8SVCUsXq5p6Be623NKeqFDqB9XV9ykR59tO+9okQ6eNG0R0wp+B0z0 83q1yjr5jplWnyBGPcOeB/CgbM2lwqaFGN+gfgONpcdOI6V4v71sKZLVX4eL/+G4Berz OBqAhz4AXyBq/3CUr2rIQ5+7L37VpXMqqfuEttDv4xOXINHgCdhzfI50gjpeqvrZBAYP s3zMz9BIJKAMZwLpmEyzlKBhXreVuI3p+h31XCgEE3udjA0/+UW781+iXKWrE5z5zCrr lUsw+NZ9GZ6js1iRZi2fRjTIftVpC+b/LE2XV5QkJji6Z29JYNBQC0FsrTKmgdAA26Mw BCVw== X-Gm-Message-State: AKS2vOz8Bkz1R/avbgfkLRfULUiDQBARnDNTP+VaXWzh+D6oxGTZfN+E AFDsrmUU+1Sb64Vh9Zad4A== X-Received: by 10.200.53.151 with SMTP id k23mr21599065qtb.104.1498750798249; Thu, 29 Jun 2017 08:39:58 -0700 (PDT) Received: from phe.ftfl.ca.ftfl.ca (hlfxns017vw-142-68-134-140.dhcp-dynamic.fibreop.ns.bellaliant.net. [142.68.134.140]) by smtp.gmail.com with ESMTPSA id w8sm4452659qtb.53.2017.06.29.08.39.56 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 29 Jun 2017 08:39:57 -0700 (PDT) From: Joseph Mingrone To: David Wolfskill Cc: freebsd-ports@freebsd.org Subject: Re: math/R: Build failure after PORTREVISION for shlib change References: <20170628120843.GG1241@albert.catwhisker.org> <86y3sbdhvx.fsf@phe.ftfl.ca> <20170628195155.GC1241@albert.catwhisker.org> Date: Thu, 29 Jun 2017 12:39:50 -0300 Message-ID: <86lgoa9515.fsf@phe.ftfl.ca> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jun 2017 15:40:05 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable David Wolfskill writes: > g1-227(11.1)[2] make -C /usr/ports/math/R showconfig > =3D=3D=3D> The following configuration options are available for R-3.4.0_= 1: > ICU=3Don: Unicode support via ICU > INFO=3Don: GNU info manuals > LDOUBLE=3Don: Long double data type > LETTER=3Don: US letter paper > LIBR=3Don: Shared R library > MEMPROF=3Doff: Memory profiling via Rprofmem() and tracemem() > NLS=3Don: Native Language Support > RPROF=3Don: R profiling via Rprof() > X11=3Don: X11 graphics device > =3D=3D=3D=3D> Require GCC > LTO=3Don: Use Link Time Optimization > OPENMP=3Don: Parallel processing support via OpenMP > =3D=3D=3D=3D> Require X11 > GHOSTSCRIPT=3Don: Graphics device for bitmap files via Ghostscript > JPEG=3Don: JPEG graphics device > CAIROPANGO=3Don: Cairo graphics device and Pango multi-language text > PNG=3Don: PNG graphics device > TCLTK=3Don: Tcl/Tk GUI toolkit support > TEXDOCS=3Don: Build/Install TeX-dependent documentation files > TIFF=3Don: TIFF image format support > =3D=3D=3D=3D> Options available for the single BLAS: you have to select e= xactly one of them > ATLAS=3Doff: ATLAS BLAS implementation > OPENBLAS=3Doff: OpenBLAS BLAS implementation > NETLIB=3Doff: Netlib BLAS implementation > RBLAS=3Don: Use R-bundled BLAS implementation > =3D=3D=3D> Use 'make config' to modify these settings > g1-227(11.1)[3]=20 With those options, the build succeeds in an 11.0-RELEASE-p1 jail. http://pkg.awarnach.mathstat.dal.ca/data/11amd64-default/2017-06-28_16h53m4= 8s/logs/R-3.4.0_2.log > Just in case it's relevant, as /usr/local/bin/gcc-ar5 is from gcc5-5.4.0_= 2: > g1-227(11.1)[5] make -C /usr/ports/lang/gcc5 showconfig > =3D=3D=3D> The following configuration options are available for gcc5-5.4= .0_2: > BOOTSTRAP=3Don: Build using a full bootstrap > GRAPHITE=3Doff: Support for Graphite loop optimizations > JAVA=3Don: Java platform support > =3D=3D=3D> Use 'make config' to modify these settings Everything matches. The successful build in poudriere even has the same line that generates the error for you. /usr/local/bin/gcc-ar5 -cr libtre.a regcomp.o regerror.o regexec.o tre-ast.= o tre-compile.o tre-match-approx.o tre-match-backtrack.o tre-match-parallel= .o tre-mem.o tre-parse.o tre-stack.o xmalloc.o Could you have something in your environment or in make.conf that's causing a problem? Joseph --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEVbCTpybDiFVxIrrVNqQMg7DW754FAllVH0dfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDU1 QjA5M0E3MjZDMzg4NTU3MTIyQkFENTM2QTQwQzgzQjBENkVGOUUACgkQNqQMg7DW 7551qA//UuH/ka60iEcZBQDdzGQc3rpPNXoh7CxtySNYVseK9OW9I2dweUPmInk9 4jMoFGl5ChlUVsbRXiQjsptSaJIrZ85P15y+b76m0hv/Brsam+7Yx61J5Dok11pM sO60SlzRbMOrsXoifF741rXN85q6pQED1qU5Ct9Vhv2nr9M9r4Lb773A5E5vnxIH KOPV8gmLIxMJ4k/326s2Vf78TSiHxvyBhgW82iERRZgGwEDfrSbUrpcU00+DImpp no0rbDuLSHghbCGZqmRF6jLLDUiDSoNdMLRJSL6xVb9vYGcCPjNiCxGxqTiLING5 WDyUd+GK9VA7QKHNvWxtBEV8yztbes69WhKei1EexuunW9osV4wQaTqyPCXKCbIu Egl7y25fJNe63ob6vl2ziSzJ7irZykfYqJ2G2JJNrIpG8LNka644bX1KLRE+KrB5 aCwU8vdI2z8TcRX5hsh1mBLqUbKbRYNnyn1CYBy54S3NnnvlurP0QHkYPGi/gnXv LqMMTVzifYppIVS4hWbcWxLu8aXSAKNWp2K+geoQY/i4Pic02EUIZn7nZIpyI0Ij IoUSHA/kt6XD0L0fRR8ozL5uU/j0xMpCJaTRfY/5eXbdjLRgjLYxRlReT6cYaGEJ jVUJENWVXTgkNBjsJ9vWRGv/7baqrawElKZomLG7hxKvmBVRnjY= =mnVF -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-ports@freebsd.org Thu Jun 29 15:45: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 31BB3D9FF2B for ; Thu, 29 Jun 2017 15:45:45 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D840264635; Thu, 29 Jun 2017 15:45:44 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v5TFjgPC056466; Thu, 29 Jun 2017 15:45:42 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v5TFjgju056465; Thu, 29 Jun 2017 08:45:42 -0700 (PDT) (envelope-from david) Date: Thu, 29 Jun 2017 08:45:42 -0700 From: David Wolfskill To: Joseph Mingrone Cc: freebsd-ports@freebsd.org Subject: Re: math/R: Build failure after PORTREVISION for shlib change Message-ID: <20170629154542.GI1241@albert.catwhisker.org> References: <20170628120843.GG1241@albert.catwhisker.org> <86y3sbdhvx.fsf@phe.ftfl.ca> <20170628195155.GC1241@albert.catwhisker.org> <86lgoa9515.fsf@phe.ftfl.ca> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="aca4q5SZ1DcD6eE6" Content-Disposition: inline In-Reply-To: <86lgoa9515.fsf@phe.ftfl.ca> 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, 29 Jun 2017 15:45:45 -0000 --aca4q5SZ1DcD6eE6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 29, 2017 at 12:39:50PM -0300, Joseph Mingrone wrote: > ... > Everything matches. The successful build in poudriere even has the same > line that generates the error for you. I may try ktracing the build.... > /usr/local/bin/gcc-ar5 -cr libtre.a regcomp.o regerror.o regexec.o tre-as= t.o tre-compile.o tre-match-approx.o tre-match-backtrack.o tre-match-parall= el.o tre-mem.o tre-parse.o tre-stack.o xmalloc.o >=20 > Could you have something in your environment or in make.conf that's > causing a problem? g1-227(11.1)[1] grep -v '^#' /etc/make.conf NET_SNMP_SYS_CONTACT=3D"david@catwhisker.org" NET_SNMP_SYS_LOCATION=3D"variable" NET_SNMP_LOGFILE=3D/var/log/snmpd.log NET_SNMP_PERSISTENTDIR=3D/var/net-snmp SENDMAIL_MC=3D/etc/mail/laptop.mc WITH_BSD_JDK=3DTRUE WITHOUT_RUNTIME_CPUDETECTION=3D YES WITHOUT_CJK=3D YES NO_SUID_XSERVER=3DYES DEFAULT_VERSIONS+=3Dlinux=3Dc6 INSTALL_AS_NCFTP=3Dyes OPTIONS_SET=3DOPTIMIZED_CFLAGS DEFAULT_VERSIONS+=3D perl5=3D5.24 FORCE_PKG_REGISTER=3D YES PKG_NOCOMPRESS=3D1 g1-227(11.1)[2]=20 > Joseph I'll be trying a poudriere run Saturday morning, and will report anything "interesting." Thanks! Peace, david --=20 David H. Wolfskill david@catwhisker.org Do Congress's recent actions on health care qualify as "terrorist acts?" See http://www.catwhisker.org/~david/publickey.gpg for my public key. --aca4q5SZ1DcD6eE6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJZVSCmXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4X+7YIAMJjqKoeqhYwJV4CP1W1BTkX NoQ9Bkzv4n46zwSpNR5Ojrl2y6n93Hp2XFr5M563ZcK/TgOWd6ImdVCZyavJauyP ieKqY8+VmFF+ZeFTY4pn51bNjS5nUmjnk1iv5olhghSJZ+NF1xvpkWJ2H5rLHu7q 7YbERVaA5RbJi/FJnNkwfcy/raBmq8AriCLn5m5VU+OmvIBVRYwR8dLZ3rMUQLWu C75x/KmtrEsAa2w8ecvjznfW/bUDrkxaaJeGHprJmvP9++oy6Uk2rnHNkU1DptEi NLZgLQHPTS60jiOrAYeIgXbn4WNmhjEnQnc9VNxgJiLpnD72Rs484Y4NBnO0cvw= =rj37 -----END PGP SIGNATURE----- --aca4q5SZ1DcD6eE6-- From owner-freebsd-ports@freebsd.org Thu Jun 29 22:23:41 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 9A0BEDA6C08 for ; Thu, 29 Jun 2017 22:23:41 +0000 (UTC) (envelope-from susan.mullins@universalmicrodatazone.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 570CF75F27 for ; Thu, 29 Jun 2017 22:23:41 +0000 (UTC) (envelope-from susan.mullins@universalmicrodatazone.com) Received: by mailman.ysv.freebsd.org (Postfix) id 51BB8DA6C06; Thu, 29 Jun 2017 22:23: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 515D0DA6C05 for ; Thu, 29 Jun 2017 22:23:41 +0000 (UTC) (envelope-from susan.mullins@universalmicrodatazone.com) Received: from IND01-BO1-obe.outbound.protection.outlook.com (mail-bo1ind01on0139.outbound.protection.outlook.com [104.47.101.139]) (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 5BC3975F1F for ; Thu, 29 Jun 2017 22:23:39 +0000 (UTC) (envelope-from susan.mullins@universalmicrodatazone.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT2155663.onmicrosoft.com; s=selector1-universalmicrodatazone-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=p/d9JiDE1ORR8JWLEuWo7uCJp3hAG5ve0o13wNrVKIw=; b=oAj9D/wcATINshTVMMW7QgDHb9UiyntqPQglersSOXdMFBmQcCDkIztRshMXw5Xwv4OlbIxwDTca/aQZ5rzkkJLz5RDJRDGGrZIGsGs7nImsPzYoURUy+7YUDvnN4tOMgRfXQ85yEvEUv8/HWuZyridxOq3JlBzDRw/DEt0XPjw= Received: from BMXPR01MB0616.INDPRD01.PROD.OUTLOOK.COM (10.174.215.10) by BMXPR01MB0614.INDPRD01.PROD.OUTLOOK.COM (10.174.215.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1220.11; Thu, 29 Jun 2017 22:23:36 +0000 Received: from BMXPR01MB0616.INDPRD01.PROD.OUTLOOK.COM ([10.174.215.10]) by BMXPR01MB0616.INDPRD01.PROD.OUTLOOK.COM ([10.174.215.10]) with mapi id 15.01.1220.015; Thu, 29 Jun 2017 22:23:36 +0000 From: Susan Mullins To: "ports@freebsd.org" Subject: Re: New Healthcare Industry Email List 2017 Thread-Topic: Re: New Healthcare Industry Email List 2017 Thread-Index: AdLxJgtrKeFl0RrrSpybiMeCCArGAw== Date: Thu, 29 Jun 2017 22:21:51 +0000 Message-ID: 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=universalmicrodatazone.com; x-originating-ip: [122.172.38.81] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BMXPR01MB0614; 7:3IKWeRWjPSQf0kIlyP7i8RzQO2niR6hDT6UN5GdGvqNvHKkNUxWXcnBQdrz0/00mb5C3mfTPmHJew44szbrdtty2Zt/GZmjJucLFOYdj+CIloeYHvcV5BeEGeqmxplTqhyj4XsA53ficK8yV6LdNzWJXyF7ZquRwoHWc1k0dbXwaZ1J50dSjh2TKFBI+l3rxRVZd0rJH85mEM3joQsnxykhhff/2fLTRV10YXO113u3ja8Mw47QkH5K2HHIMAc78bflzeVY6ueeiQH6NvQTr6ZOJYDYv7PoKpudbVEshttbLscJfkzoosxifVyamTIY/RFkFXRvRNwfArMFo2o2dF8ndXH582vS6USJFGUh4xwjvqfnkXk/77deKQpvWKi/1UTKP0Eqq9F+yZLayX8CuDEps9Aw8q0ne8izmlJEjtH2F0I6wDFtOxk+K96MDwoace0Tpol/v5CfWrwWvp3+2oBaSg6F3273AlQZiaZ9HWnuNl/N5Q1STk/sU357+vEYx97IDpgq7mVc6caUkyXdr6Z/eKNhJKWQush7ahG6Jd75fDUXNxtm6pIEwrdHU9EeQ9OsJ349Stl2/li+pX8AfLeYghYx1i4oqmQ/5lV0ou/E8nkxnnsr8BzVHQrUm3FeowmO4oxsqoVZlmnU04hqFLHi0v+KX4nw1fnD9CIK9BvSJrVNDVoSGQ9j9TnIP58UNKTdSmNAXvmbRGHTvvgqJ0lnAfmQZx65Lh0Mng82f9XwXH84x8cnw4wzFsgr6rI3BL7XYcz/cDIkLbrgRnUroa6DgXRizrL1bhGT6foS+f+0= x-ms-office365-filtering-correlation-id: bd536a0c-5218-43a9-d56c-08d4bf3d7c23 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(2017052603031)(201703131423075)(201702281549075)(201702085551020)(201702085553020)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BMXPR01MB0614; x-ms-traffictypediagnostic: BMXPR01MB0614: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(151999592597050)(26388249023172)(236129657087228)(48057245064654)(148574349560750)(21748063052155); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(3002001)(93006095)(93001095)(10201501046)(6041248)(20161123564025)(20161123555025)(20161123560025)(2016111802025)(20161123562025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6043046)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BMXPR01MB0614; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BMXPR01MB0614; x-forefront-prvs: 0353563E2B x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39840400002)(39850400002)(39400400002)(39410400002)(39450400003)(84964002)(51414003)(106356001)(50986999)(8676002)(1730700003)(81166006)(9326002)(2351001)(9476002)(66066001)(7736002)(86362001)(33656002)(53936002)(54356999)(8936002)(2900100001)(6246003)(110136004)(38730400002)(14454004)(478600001)(790700001)(6116002)(102836003)(3846002)(5630700001)(5640700003)(6436002)(55016002)(6506006)(6306002)(9686003)(54896002)(3280700002)(3660700001)(2906002)(25786009)(74316002)(5660300001)(7696004)(77096006)(229853002)(2501003)(6916009)(6666003)(189998001)(8913002); DIR:OUT; SFP:1102; SCL:1; SRVR:BMXPR01MB0614; H:BMXPR01MB0616.INDPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; MLV:ovr; PTR:InfoNoRecords; LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: universalmicrodatazone.com X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jun 2017 22:21:51.2426 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 1df3d8de-cd72-488a-af19-7a73d2a00038 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BMXPR01MB0614 Content-Type: text/plain; charset="us-ascii" 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, 29 Jun 2017 22:23:41 -0000 Hi, I trust this email finds you well. We have the New Healthcare Industry Email List 2017 with emails, and comple= te Contact information List Contains: Name, Company's Name, Phone Number, Fax Number, Title, Email= address, Complete Mailing Address, Company revenue, size, Web address etc. Our Specialties: * Anesthesiologists, Cardiologist, Cardiovascular Disease, Registered N= urse Anesthetists * Chiropractor, Dentist, Dermatology, Diagnostic Radiology, Doctor of D= ental Surgery * Doctor of Medicine, Emergency Medicine, Family Medicine, Gastroentero= logy, General Dentistry * General Practice, General Surgery, Internal Medicine, Marriage & Fami= ly Therapist, * Medical Director, Naturopathic Medicine, Nephrology, Neurology, Nurse= , Nurse Practitioner * Obstetrics & Gynaecologist, Occupational Therapist, Oncology, Ophthal= mology * Optometrist, Orthopaedic Surgery, Orthopedics, Otolaryngology, Pathol= ogy, Paediatrician * Physical Medicine & Rehabilitation, Physical Therapist, Physician, Ph= ysician Assistant * Podiatry, Psychiatry, Psychologist, Pulmonary Disease, Radiology, Reg= istered Nurse * Social Worker, Speech-Language Pathologist, Surgery, Urology, Veterin= arian, Massage Therapist If this sounds of any value, please specify your requirement in detail so t= hat I can share a few Healthcare professionals' business contacts just for = your review. I look forward to hearing from you soon. Kind Regards, Elina Lopez Demand Generation Specialist If you do not wish to receive future emails from us, please reply as "o= pt-out" From owner-freebsd-ports@freebsd.org Fri Jun 30 00:59:05 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 B4C35DA947C; Fri, 30 Jun 2017 00:59:05 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) (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 827407A131; Fri, 30 Jun 2017 00:59:05 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (localhost [127.0.0.1]) by ainaz.pair.com (Postfix) with ESMTP id 47A943F4D9; Thu, 29 Jun 2017 20:58:58 -0400 (EDT) Received: from [192.168.1.108] (unknown [202.188.138.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id 65C463F4D5; Thu, 29 Jun 2017 20:58:41 -0400 (EDT) Date: Fri, 30 Jun 2017 08:58:21 +0800 User-Agent: K-9 Mail for Android In-Reply-To: References: <6FD738D6-F163-4BC5-8E6E-A9B9F35595CD@dsl-only.net> <82A991B0-FD8B-457F-8483-D61AE5E6D6F6@pfeifer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work To: Mark Millard CC: papowell@astart.com, FreeBSD-STABLE Mailing List , FreeBSD Toolchain , FreeBSD Ports , Pedro Giffuni From: Gerald Pfeifer Message-ID: 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, 30 Jun 2017 00:59:05 -0000 Am 29=2E Juni 2017 18:55:59 GMT+08:00 schrieb Mark Millard : >I'm not currently set up to run more than head on >any of amd64, powerpc64, powerpc, aarch64, or armv6/7 >(which are all I target)=2E And I'm in the middle of >attempting a fairly large jump to head -r320458 on >those=2E Oh, then I had misunderstood your previous mail=2E No worries, I'll gently= proceed then=2E I expect to update gcc5 in the next 24 hours=2E >[In my normal/head environment I'm switching to lang/gcc7-devel >for gcc (from lang/gcc6 ) but I'm odd that way=2E] The compiler should be fine, it's a number of ports that are not (even blo= cking the move from GCC 5 to 6 as default)=2E Gerald From owner-freebsd-ports@freebsd.org Fri Jun 30 03:40: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 995D9D870F9 for ; Fri, 30 Jun 2017 03:40:39 +0000 (UTC) (envelope-from amutu@amutu.com) Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 613887E1F4 for ; Fri, 30 Jun 2017 03:40:39 +0000 (UTC) (envelope-from amutu@amutu.com) Received: by mail-oi0-x22a.google.com with SMTP id l130so27521201oib.1 for ; Thu, 29 Jun 2017 20:40:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amutu-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=XgbclpvScgAyU84snsd1Hn6aRMqUfRF9L0mH2vqSfXY=; b=xcsvkJFQzSfG6df9i+iQ1eJ9ASORrUhEo9I2kcisL4xQ31C6ZhxFZ2GJfsIgeyj1ej Fkm9PWC5CAlwn/wWpWA0c8SV+wU4RsjwEbu2LsZyPuQ92DbqU6TUgmKAUVwerqtfCPUK KQNscEjNX+MEyEf18OOwQWqg6joucKGs44xawih0QEAl3A0AhZWQetai3KFtNnE2Vx0o hB4Omqb8UYGpSdNOUrI33GpNdJMK6rrK8Q9gMRiIFge1lRPbI1YQn9Y7ePEjYg9kOk9V rvtmuzIRUS5I28SDBLatg64UmU9JAFCFzzs7QIVPlkoePaifeT272tbWA0/OTiOUvOyg z0DA== 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=XgbclpvScgAyU84snsd1Hn6aRMqUfRF9L0mH2vqSfXY=; b=OLfVvFFBNccquWDQ2+hXTXTskfO1OAHXWM3JBw+zFG4EMj3SctV7Yfyj0C2oaLL60v h2LxDfSSM1GFuv4EW2qdkvhUYzvO+1OPXjlqiTv2FIh/VEjKXEd9n8Om62sD9oSJpMmb 6E9l5t1HbMJy0H0qmmJ6Cc5NIM+iiVzSOehxIX6K82/DbBkW8BxBBYGv1TuzQTpGsRRF yjC0Mp7jbWSrq2GOGhkhHvJq7m0gEMoF2dSh9VgnVQhr5Cy2slEqESuLfWkE64/g8DKm 2db842B187cCIzAC7BOu/hmSKqOjWpzpPvABr6dpcq6qdsc5Ii8W1/+krRpU+A5sIERV RLfg== X-Gm-Message-State: AKS2vOxSGXKgaE795is8aKISs8GTn4KqCZEZ7ez37fHgoE7yb+WUVSqI BmA1ukj+zfSzRSMm4QthVA== X-Received: by 10.202.168.130 with SMTP id r124mr11586761oie.91.1498794038388; Thu, 29 Jun 2017 20:40:38 -0700 (PDT) Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com. [209.85.218.52]) by smtp.gmail.com with ESMTPSA id x20sm8349164oix.33.2017.06.29.20.40.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Jun 2017 20:40:37 -0700 (PDT) Received: by mail-oi0-f52.google.com with SMTP id 191so869088oii.2; Thu, 29 Jun 2017 20:40:37 -0700 (PDT) X-Received: by 10.202.84.214 with SMTP id i205mr7228051oib.158.1498794037574; Thu, 29 Jun 2017 20:40:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.133.136 with HTTP; Thu, 29 Jun 2017 20:40:17 -0700 (PDT) From: Jov Date: Fri, 30 Jun 2017 11:40:17 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: PostgreSQL related NEW PORTS need committers To: freebsd-database@freebsd.org, 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: Fri, 30 Jun 2017 03:40:39 -0000 =E2=80=8B=E2=80=8B Hi hackers, I ported some PostgreSQL related tools/extensions to FreeBSD several weeks ago=EF=BC=8Cthe PR links are as follows. All of them passed portlint and te= sted by poudriere testport. Review, comment=EF=BC=8Ctest or commit all are welco= me=EF=BC=8CI really hope some of them can be committed before Q3 quarterly branch cut.Thanks very much=EF=BC=81 pgloader3, Replace of pgloader2 as pgloader2 is not maintained: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219165 postgres-xl,Scalable open source PostgreSQL-based database cluster: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219164 orafce, Oracle's compatibility functions and packages for PostgreSQL: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219616 zhparser,PostgreSQL extension for full-text search of Chinese: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219649 tds_fdw, PostgreSQL foreign data wrapper to connect to MS SQLserver and Sybase: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219671 pg_repack, Reorganize tables in PostgreSQL databases with minimal locks.Replace of pg_reorg as it is not maintained: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219679 plpgsql_check, PostgreSQL extension to check PL/pgSQL code: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219680 pgformatter,PostgreSQL SQL syntax beautifier: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219681 ip4r=EF=BC=88not new port=EF=BC=8Cupdate to 2.2=EF=BC=89: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219766 Regard Jov From owner-freebsd-ports@freebsd.org Fri Jun 30 07:38: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 AEA67D8AA80; Fri, 30 Jun 2017 07:38:59 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) 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 78B5283C39; Fri, 30 Jun 2017 07:38:59 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id C97441AAF058; Fri, 30 Jun 2017 09:38:55 +0200 (CEST) Subject: Re: PostgreSQL related NEW PORTS need committers To: Jov , freebsd-database@freebsd.org, FreeBSD Ports References: From: Torsten Zuehlsdorff Message-ID: Date: Fri, 30 Jun 2017 09:38:52 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US 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: Fri, 30 Jun 2017 07:38:59 -0000 On 30.06.2017 05:40, Jov wrote: > ​​ > Hi hackers, > I ported some PostgreSQL related tools/extensions to FreeBSD several weeks > ago，the PR links are as follows. All of them passed portlint and tested > by poudriere testport. Review, comment，test or commit all are welcome，I > really hope some of them can be committed before Q3 quarterly branch > cut.Thanks very much！ > > pgloader3, Replace of pgloader2 as pgloader2 is not maintained: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219165 > > postgres-xl,Scalable open source PostgreSQL-based database cluster: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219164 There is already someone assigned to. > orafce, Oracle's compatibility functions and packages for PostgreSQL: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219616 I'm taking it. > zhparser,PostgreSQL extension for full-text search of Chinese: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219649 I'm taking it. (BTW: is there something similar for Japanese?) > tds_fdw, PostgreSQL foreign data wrapper to connect to MS SQLserver and > Sybase: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219671 > > pg_repack, Reorganize tables in PostgreSQL databases with minimal > locks.Replace of pg_reorg as it is not maintained: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219679 > > plpgsql_check, PostgreSQL extension to check PL/pgSQL code: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219680 > > pgformatter,PostgreSQL SQL syntax beautifier: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219681 I'm taking all 4. I will work through the PRs next week. > ip4r（not new port，update to 2.2）: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219766 This one is already assigned. Greetings, Torsten From owner-freebsd-ports@freebsd.org Fri Jun 30 10:37: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 D0102D8DE0C for ; Fri, 30 Jun 2017 10:37:04 +0000 (UTC) (envelope-from amutu@amutu.com) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::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 898343D2C for ; Fri, 30 Jun 2017 10:37:04 +0000 (UTC) (envelope-from amutu@amutu.com) Received: by mail-oi0-x22f.google.com with SMTP id p187so88299229oif.3 for ; Fri, 30 Jun 2017 03:37:04 -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=L8zYBHjMdgHZ20kQJkmP1yWlMkiztOR+YDsTemBoYmM=; b=i5vou6yeBpKSYAF1rVdoVb5TiSrNwZG7FJjijDbL8Qr02eX0LD3qBrM6HVKf7iq1i9 zZ2ckpKmhmIEDjzoMQ1/xeW2bzjnLGqSoL85urOzMN/Y0zhZjeMzAtGaeQQOoRZ9GkZo ThxWT3G3QA/Z2kMRTz94l/MmQ6mo+5xQm79od5pfgDCwY+b4uqhcoOYhWtJveamXM1bT vhm0uKm/e9/wXm21Jv3epLPYIuXgnLsUP/setWV3hE37szsDncHbEll0UNvYJ/PwnIGD J1A9s1k2C6O+W6ckU/HZ9XNr3323sUpyPEQ/PrS1AgURw6d8kN95QNN0xM6UtimrX96+ Auwg== 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=L8zYBHjMdgHZ20kQJkmP1yWlMkiztOR+YDsTemBoYmM=; b=J4U6/Ao7n7EKgCydfXXZ139HwxahN3xm8Z/JDdoowGFTPRxKS4+6BdGtmBfD8CFX8c wBXpisoYwRYXsDtg5jN7D/OokBik5pMOjkF3ZCoSnym8Twqp0B0y/JRn3WGVahcSblbN 5va1GJpVyL4798F2WEMEGhTFVZOqeuW8PUrhnd4brd7icwR4nFLNXLn75Z/uI4Sr1lH7 LDwstnbeYdhZt3Ob8FPm8dR8GhB0DwTMeO1DL+qzIVs/dug0uzdJkgD4REtn5iYEoyeE hMZZmt193JHsmnyiTuArCZYpgmJa1Fspx9Jp1NwZRpKy68XR3vTSVV6j/dUkJRy+EoSo 4heA== X-Gm-Message-State: AKS2vOxazZreMkKCbdBd7dtViAytom5efa/WDngIkyPfNMvyVA/uWN1C xKhaqmNK+Mwl1rzS3082yw== X-Received: by 10.202.175.142 with SMTP id y136mr12624802oie.132.1498819023560; Fri, 30 Jun 2017 03:37:03 -0700 (PDT) Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com. [209.85.218.41]) by smtp.gmail.com with ESMTPSA id n189sm1639209oih.0.2017.06.30.03.37.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Jun 2017 03:37:03 -0700 (PDT) Received: by mail-oi0-f41.google.com with SMTP id 191so6751727oii.2; Fri, 30 Jun 2017 03:37:02 -0700 (PDT) X-Received: by 10.202.84.214 with SMTP id i205mr8177794oib.158.1498819022669; Fri, 30 Jun 2017 03:37:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.133.136 with HTTP; Fri, 30 Jun 2017 03:36:42 -0700 (PDT) In-Reply-To: References: From: Jov Date: Fri, 30 Jun 2017 18:36:42 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: PostgreSQL related NEW PORTS need committers To: Torsten Zuehlsdorff Cc: freebsd-database@freebsd.org, 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: Fri, 30 Jun 2017 10:37:04 -0000 Hi Torsten, Thanks for your taking these PRs! miwi@ took Pgloader3 and postgresql-xl a month ago,but there was not progress since he took it at 2017-05-13.ip4r is auto assigned to its maintainer tobez@ but no progress since 2017-06-04.I will ping them after a while.Thank you very much! For Japanese, I do not know if there is similar FTS plugin for PostgreSQL. PG is more popular than MySQL in Japan, maybe someone in Japan know more information. Regard, Jov 2017-06-30 15:38 GMT+08:00 Torsten Zuehlsdorff : > On 30.06.2017 05:40, Jov wrote: > >> =E2=80=8B=E2=80=8B >> Hi hackers, >> I ported some PostgreSQL related tools/extensions to FreeBSD several >> weeks >> ago=EF=BC=8Cthe PR links are as follows. All of them passed portlint and= tested >> by poudriere testport. Review, comment=EF=BC=8Ctest or commit all are we= lcome=EF=BC=8CI >> really hope some of them can be committed before Q3 quarterly branch >> cut.Thanks very much=EF=BC=81 >> >> pgloader3, Replace of pgloader2 as pgloader2 is not maintained: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219165 >> >> postgres-xl,Scalable open source PostgreSQL-based database cluster: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219164 >> > > There is already someone assigned to. > > orafce, Oracle's compatibility functions and packages for PostgreSQL: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219616 >> > > I'm taking it. > > zhparser,PostgreSQL extension for full-text search of Chinese: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219649 >> > > I'm taking it. (BTW: is there something similar for Japanese?) > > tds_fdw, PostgreSQL foreign data wrapper to connect to MS SQLserver and >> Sybase: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219671 >> >> pg_repack, Reorganize tables in PostgreSQL databases with minimal >> locks.Replace of pg_reorg as it is not maintained: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219679 >> >> plpgsql_check, PostgreSQL extension to check PL/pgSQL code: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219680 >> >> pgformatter,PostgreSQL SQL syntax beautifier: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219681 >> > > I'm taking all 4. I will work through the PRs next week. > > ip4r=EF=BC=88not new port=EF=BC=8Cupdate to 2.2=EF=BC=89: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219766 >> > > This one is already assigned. > > Greetings, > Torsten > _______________________________________________ > freebsd-database@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-database > To unsubscribe, send any mail to "freebsd-database-unsubscribe@freebsd.or= g > " From owner-freebsd-ports@freebsd.org Fri Jun 30 16:08: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 C392DD94F07 for ; Fri, 30 Jun 2017 16:08:07 +0000 (UTC) (envelope-from bsdports@cloudzeeland.nl) Received: from ares.cloudzeeland.nl (cloudzeeland.xs4all.nl [83.161.133.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloudzeeland.nl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 86365737C6; Fri, 30 Jun 2017 16:08:06 +0000 (UTC) (envelope-from bsdports@cloudzeeland.nl) Received: from ares.cloudzeeland.nl (unknown [10.10.10.32]) by ares.cloudzeeland.nl (Postfix) with ESMTP id 23A054FAD1CC; Fri, 30 Jun 2017 18:04:48 +0200 (CEST) Received: from [10.10.10.34] (styx.zeeland24.nl [82.176.127.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by ares.cloudzeeland.nl (Postfix) with ESMTPSA id D6B284FAD1A7; Fri, 30 Jun 2017 18:04:47 +0200 (CEST) To: FreeBSD Ports ML , cpm@FreeBSD.org From: Jos Chrispijn Subject: Vulnerability Message-ID: <6d826a0d-b54c-ef9d-88d3-bdf4f159c434@cloudzeeland.nl> Date: Fri, 30 Jun 2017 18:04:49 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: nl X-Virus-Scanned: ClamAV using ClamSMTP on ares.cloudzeeland.nl 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, 30 Jun 2017 16:08:07 -0000 Dear port maintainer, Just to let you know that I ran into the following vulenerability report: libgcrypt-1.7.7 is vulnerable: libgcrypt -- side-channel attack on RSA secret keys CVE: CVE-2017-7526 WWW:https://vuxml.FreeBSD.org/freebsd/ed3bf433-5d92-11e7-aa14-e8e0b747a45a.html Could you send out a port update? Thanks in advance! Keep up the good work, Jos Chrispijn From owner-freebsd-ports@freebsd.org Fri Jun 30 16:18: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 E02C2D95309 for ; Fri, 30 Jun 2017 16:18:49 +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 7263874083; Fri, 30 Jun 2017 16:18:49 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id 18bde91e TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Fri, 30 Jun 2017 10:18:42 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Vulnerability From: Adam Weinberger In-Reply-To: <6d826a0d-b54c-ef9d-88d3-bdf4f159c434@cloudzeeland.nl> Date: Fri, 30 Jun 2017 10:18:40 -0600 Cc: FreeBSD Ports ML , cpm@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <6d826a0d-b54c-ef9d-88d3-bdf4f159c434@cloudzeeland.nl> To: Jos Chrispijn 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: Fri, 30 Jun 2017 16:18:50 -0000 > On 30 Jun, 2017, at 10:04, Jos Chrispijn = wrote: >=20 > Dear port maintainer, >=20 > Just to let you know that I ran into the following vulenerability = report: >=20 > libgcrypt-1.7.7 is vulnerable: > libgcrypt -- side-channel attack on RSA secret keys > CVE: CVE-2017-7526 > = WWW:https://vuxml.FreeBSD.org/freebsd/ed3bf433-5d92-11e7-aa14-e8e0b747a45a= .html >=20 > Could you send out a port update? Thanks in advance! >=20 > Keep up the good work, > Jos Chrispijn Hi Jos, See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220382 It's in the exp-run queue. # Adam --=20 Adam Weinberger adamw@adamw.org https://www.adamw.org From owner-freebsd-ports@freebsd.org Fri Jun 30 16:23:21 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 328D0D95631 for ; Fri, 30 Jun 2017 16:23:21 +0000 (UTC) (envelope-from cjpm@gmx.es) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8D41C74550 for ; Fri, 30 Jun 2017 16:23:19 +0000 (UTC) (envelope-from cjpm@gmx.es) Received: from [80.39.219.97] by 3capp-mailcom-bs01.server.lan (via HTTP); Fri, 30 Jun 2017 18:23:10 +0200 MIME-Version: 1.0 Message-ID: From: "Carlos Jacobo Puga Medina" To: freebsd-ports@freebsd.org Subject: Re: Vulnerability Content-Type: text/plain; charset=UTF-8 Date: Fri, 30 Jun 2017 18:23:10 +0200 Importance: normal Sensitivity: Normal X-Priority: 3 X-Provags-ID: V03:K1:fG8fyCEdCo5zjM1fGumnRUf3cpDWHlMt/OfIs280jN+ RUKLV2F0xivB3bVjG+Ico1L6wMQlBvyp5w5xXd9PF5+SJkSEFn HEr447hpmdYFOxmWDLXC1dcf++JZAGlHyth7B5KJCTHbamDfBK AuI83DQg2tG7fosp20LZbvfTW+/zv5R4BrGcwiVOJni7F4QDDU s2Tsh8oi1XeQe99XRG1hO2qI+DEWPIbgDHLvt1hVQ+owLmh7t4 Zf2WGghG3ZPnmEUXKca2akk9eLTOyu7AFTp1IHt5ArRdvhHTzJ owAagizCWdqUGx+qgnZlY+oyi2N X-UI-Out-Filterresults: notjunk:1;V01:K0:tvDQrW+gScE=:PI07h+V6SPFgtr+DKMqZBl sJWTXtT+Cslfrgtj5S5JPgJmY1yqA5bO5oqCxsfA24J6OS5Ihr6mLH35k+jU88pZhqUprAyXn DlW7mVAYODzMDSWvwXGuQ9OA85BO+eVjHuGAdBL0Qoxd82pfFJK0CB7r7X5X5SdBUN0qPyKrV 5pteRpJgrZ5nJV0M/PVYlNm0fxj8ZCXBM/S3VR1PtSIbhlyZYqV577+AF64+NUcQ07zjW6ITM P/3ixSz32E9MdGvCvNp5cWqD7kpGc+/twP4fT2iy0lnEbCvRZHxraCEZUDBSDBGeJg5dXxKsQ CtPcumK/NrqlUSv3rywsio0Gjm+EBPf6HUJ0ey7f4FiF0mhJRlPzdBF6lQvfvDXQqLykdjBqP MXI3s2I0fBJ+oMl2TMBNiSRcbC5TgWypOjZuIX+LjS9iWziwnmhg+tgoXj3JWTkYC6pmo63iu 1BkCYlRciA== 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, 30 Jun 2017 16:23:21 -0000 Hi, > Enviar: viernes 30 de junio de 2017 a las 18:04 > De: "Jos Chrispijn" > Para: "FreeBSD Ports ML" , cpm@FreeBSD.org > Asunto: Vulnerability > > Dear port maintainer, > > Just to let you know that I ran into the following vulenerability report: > > libgcrypt-1.7.7 is vulnerable: > libgcrypt -- side-channel attack on RSA secret keys > CVE: CVE-2017-7526 > WWW:https://vuxml.FreeBSD.org/freebsd/ed3bf433-5d92-11e7-aa14-e8e0b747a45a.html > > Could you send out a port update? Thanks in advance! > I have submitted a patch to update libgcrypt to 1.7.8 (still pending for an exp-run) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220382 You can grab the patch, apply and build the port. > Keep up the good work, > Jos Chrispijn > > Kind regards, -- Carlos Jacobo Puga Medina From owner-freebsd-ports@freebsd.org Sat Jul 1 05:53:21 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 2238DD91F10 for ; Sat, 1 Jul 2017 05:53:21 +0000 (UTC) (envelope-from bsdports@cloudzeeland.nl) Received: from ares.cloudzeeland.nl (cloudzeeland.xs4all.nl [83.161.133.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloudzeeland.nl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D62717A4A9 for ; Sat, 1 Jul 2017 05:53:20 +0000 (UTC) (envelope-from bsdports@cloudzeeland.nl) Received: from ares.cloudzeeland.nl (unknown [10.10.10.32]) by ares.cloudzeeland.nl (Postfix) with ESMTP id B75284FAD1CC; Sat, 1 Jul 2017 07:53:15 +0200 (CEST) Received: from [10.10.10.34] (styx.zeeland24.nl [82.176.127.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by ares.cloudzeeland.nl (Postfix) with ESMTPSA id 759194FAD1A9; Sat, 1 Jul 2017 07:53:15 +0200 (CEST) Subject: Re: Vulnerability To: Carlos Jacobo Puga Medina , freebsd-ports@freebsd.org References: From: Jos Chrispijn Message-ID: Date: Sat, 1 Jul 2017 07:53:18 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Language: nl X-Virus-Scanned: ClamAV using ClamSMTP on ares.cloudzeeland.nl 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, 01 Jul 2017 05:53:21 -0000 Op 30-6-2017 om 18:23 schreef Carlos Jacobo Puga Medina: > I have submitted a patch to update libgcrypt to 1.7.8 (still pending > for an exp-run) > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220382 > > You can grab the patch, apply and build the port. Thanks Carlos, appreciate your support. ./Jos From owner-freebsd-ports@freebsd.org Sat Jul 1 05:51:41 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 9DE92D91C79 for ; Sat, 1 Jul 2017 05:51:41 +0000 (UTC) (envelope-from bsdports@cloudzeeland.nl) Received: from ares.cloudzeeland.nl (cloudzeeland.xs4all.nl [83.161.133.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloudzeeland.nl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B4737A30D; Sat, 1 Jul 2017 05:51:40 +0000 (UTC) (envelope-from bsdports@cloudzeeland.nl) Received: from ares.cloudzeeland.nl (unknown [10.10.10.32]) by ares.cloudzeeland.nl (Postfix) with ESMTP id DE8694FAD1CC; Sat, 1 Jul 2017 07:51:35 +0200 (CEST) Received: from [10.10.10.34] (styx.zeeland24.nl [82.176.127.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by ares.cloudzeeland.nl (Postfix) with ESMTPSA id 3D6544FAD1A9; Sat, 1 Jul 2017 07:51:35 +0200 (CEST) Subject: Re: Vulnerability To: Adam Weinberger Cc: FreeBSD Ports ML , cpm@FreeBSD.org References: <6d826a0d-b54c-ef9d-88d3-bdf4f159c434@cloudzeeland.nl> From: Jos Chrispijn Message-ID: <0b0b7c3a-78d4-e75e-7448-e06be349bcf7@cloudzeeland.nl> Date: Sat, 1 Jul 2017 07:51:37 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Language: nl X-Virus-Scanned: ClamAV using ClamSMTP on ares.cloudzeeland.nl 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, 01 Jul 2017 05:51:41 -0000 Hi Adam, Op 30-6-2017 om 18:18 schreef Adam Weinberger: > See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220382 > It's in the exp-run queue. > > Thanks - I saw it too but there is a question mark behind it. For a total nub on ports like me, I will definitely check what such a page exactly means and what it says about notices/planned version updates. Best regards, Jos Chrispijn From owner-freebsd-ports@freebsd.org Sat Jul 1 09:38: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 30AF2DA712C for ; Sat, 1 Jul 2017 09:38:45 +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 1C6C77FD22 for ; Sat, 1 Jul 2017 09:38:45 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1B7F0DA712A; Sat, 1 Jul 2017 09:38: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 19392DA7129 for ; Sat, 1 Jul 2017 09:38:45 +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 0AF8A7FD21 for ; Sat, 1 Jul 2017 09:38:45 +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 v619ciZt089161 for ; Sat, 1 Jul 2017 09:38:44 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id v619cid2089160; Sat, 1 Jul 2017 09:38:44 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201707010938.v619cid2089160@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: Sat, 1 Jul 2017 09:38:44 +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: Sat, 01 Jul 2017 09:38:45 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ graphics/opencollada | 1.6.47 | v1.6.56 ------------------------------------------------+-----------------+------------ multimedia/vdr | 1.7.29 | 2.3.8 ------------------------------------------------+-----------------+------------ science/py-pyteomics | 3.4.1 | 3.4.2 ------------------------------------------------+-----------------+------------ 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 Sat Jul 1 15:34: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 C117CD8C833 for ; Sat, 1 Jul 2017 15:34:30 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 93C446571C; Sat, 1 Jul 2017 15:34:29 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v61FYSKf085380; Sat, 1 Jul 2017 15:34:28 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v61FYSQS085379; Sat, 1 Jul 2017 08:34:28 -0700 (PDT) (envelope-from david) Date: Sat, 1 Jul 2017 08:34:28 -0700 From: David Wolfskill To: Joseph Mingrone Cc: freebsd-ports@freebsd.org Subject: Re: math/R: Build failure after PORTREVISION for shlib change Message-ID: <20170701153428.GY1241@albert.catwhisker.org> References: <20170628120843.GG1241@albert.catwhisker.org> <86y3sbdhvx.fsf@phe.ftfl.ca> <20170628195155.GC1241@albert.catwhisker.org> <86lgoa9515.fsf@phe.ftfl.ca> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="GGtmmZw9yuSW4z2l" Content-Disposition: inline In-Reply-To: <86lgoa9515.fsf@phe.ftfl.ca> 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, 01 Jul 2017 15:34:30 -0000 --GGtmmZw9yuSW4z2l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 29, 2017 at 12:39:50PM -0300, Joseph Mingrone wrote: > ... > With those options, the build succeeds in an 11.0-RELEASE-p1 jail. > http://pkg.awarnach.mathstat.dal.ca/data/11amd64-default/2017-06-28_16h53= m48s/logs/R-3.4.0_2.log > ...=20 > Everything matches. The successful build in poudriere even has the same > line that generates the error for you. >=20 > /usr/local/bin/gcc-ar5 -cr libtre.a regcomp.o regerror.o regexec.o tre-as= t.o tre-compile.o tre-match-approx.o tre-match-backtrack.o tre-match-parall= el.o tre-mem.o tre-parse.o tre-stack.o xmalloc.o >=20 > Could you have something in your environment or in make.conf that's > causing a problem? > .... As expected, further attempts to build math/R on my laptop have continued to fail as before -- and as mentioned, I ran a poudriere run, where building the package for math/R worked. That said, the line in the poudriere log that corresponds to the failing invocation is a bit different in my case. (I found a couple of small options differences, such as paper size; I don't believe those have anything to do with the observed differences, but I've corrected them for tomorrow's poudriere run.) The line in the failing case (with the immediately preceding line for context): =2E.. gcc5 -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG = -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp= -fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -Wl,-rpath=3D/usr/loca= l/lib/gcc5 -isystem /usr/local/include -fno-strict-aliasing -flto -fvisibil= ity=3Dhidden -c xmalloc.c -o xmalloc.o /usr/local/bin/gcc-ar5 -cr libtre.a regcomp.o regerror.o regexec.o tre-ast.= o tre-compile.o tre-match-approx.o tre-match-backtrack.o tre-match-parallel= =2Eo tre-mem.o tre-parse.o tre-stack.o xmalloc.o ar: unrecognized option `--plugin' and in the successful poudriere run: =2E.. cc -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG -I= /usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fpic -O= 2 -pipe -DLIBICONV_PLUG -fstack-protector -isystem /usr/local/include -fno= -strict-aliasing -fvisibility=3Dhidden -c xmalloc.c -o xmalloc.o /usr/local/bin/ar -cr libtre.a regcomp.o regerror.o regexec.o tre-ast.o tre= -compile.o tre-match-approx.o tre-match-backtrack.o tre-match-parallel.o tr= e-mem.o tre-parse.o tre-stack.o xmalloc.o Looking (on the laptop) at plausible "ar" executables in /usr/local/bin, I see: g1-227(12.0-C)[3] (cd /usr/local/bin && ls -lTi gcc-ar* ar) 1850562 -r-xr-xr-x 2 root wheel 6368928 Mar 23 05:10:40 2017 ar 1850780 -r-xr-xr-x 2 root wheel 25728 May 1 05:47:28 2017 gcc-ar49 1846261 -r-xr-xr-x 2 root wheel 26192 Jun 30 04:57:30 2017 gcc-ar5 g1-227(12.0-C)[4]=20 Apparently "ar" was installed by binutils-2.28,1, while the gcc-ar* were installed by gcc49-4.9.4_3 and gcc5-5.4.0_2, respectively. Weird. Peace, david --=20 David H. Wolfskill david@catwhisker.org Congratulations on the sesquicentennial, Canada! :-) See http://www.catwhisker.org/~david/publickey.gpg for my public key. --GGtmmZw9yuSW4z2l Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJZV8EEXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XRBEH/i5/iGdUpBcUNkckq+n1Be13 BxfeCBEYEswd8rsHCu3u+B8j5VCDVfJIQD2NAgT+N4K6R1SWy2uxy4YBZ5uFOOt/ 9Avb4MnN3+H75votFJUSarC8UhvRiQ+5QU+2Dwv3GbgbIE0ALjjStct/aFwY2ivF Y2/Xekq08VttjN0Iu0rxd9ez6893ZCKupVc6TiS7BmwI6tv7owqKRRuiDvHBfOWj HAWUjYIhlakfW/Yh/jzYJYwDWkC7ytIgeBY+CMJA+YpGZrbwLbZGW8gN2IDYcoPI WXatI4lt9ROsSkUDD4eVrve3+MKXpC9P3MOlX2F4sSG/0fx9cpPG5PNdJcnihLU= =Hz33 -----END PGP SIGNATURE----- --GGtmmZw9yuSW4z2l-- From owner-freebsd-ports@freebsd.org Sat Jul 1 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 DDF63D92ED0; Sat, 1 Jul 2017 21:15:52 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::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 6AEA372F89; Sat, 1 Jul 2017 21:15:52 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by mail-wm0-x241.google.com with SMTP id y5so13717585wmh.3; Sat, 01 Jul 2017 14:15:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:to:cc:reply-to:from:subject:message-id:date:user-agent :mime-version; bh=+jDGwE+AKCooE2eZxq3V6+VOtwXkdn56KYq/VHipmAQ=; b=abB7LzMBzHvU6zcAapFyxdP2EC3mgHpb548JJwTN4Avs1kzQFdvFGKzXGS1NuEvKRC 4ojR7qt9QUuculDr/teW7OiIMBWXEBNiEqlQASyomi5QEsCtO/tF3uq4l2VDKBpqn7HU EvvrRDh1dnoRhvIIvQDJkWd1D9gApKyt6/IPgbxvfzIwZF22hPY7VGzb8vAkP1vry8As c9JnEpp2TbpOcnpvUoUMPmWHl5Mo2qcg71Unzcf4SGz/pcLRoyJUMIGh3SGY5fcuKN0U Lm7mGVKvHX8gm/p9jI7/IYBzvlqJXxEgwzH06E6Bbrtu2GOns5HDRM2vpWj2+pw+IjX6 E4IQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:to:cc:reply-to:from:subject:message-id :date:user-agent:mime-version; bh=+jDGwE+AKCooE2eZxq3V6+VOtwXkdn56KYq/VHipmAQ=; b=LR7wDLqBthjXxAPx/F9omFKjFcNdjUb6rDGWaKjgOw9yqUjHySLIklX7/Sro9iXm1C 47zFux9f9dobOmxIn56VG+EBaYYjGl8Krce4IqomYBmEBO5R/c0QYDEXfC1zS33NoPO4 fnC2HNKAyWH6tK5HHsI4GOfqJ3pOJp8C1id3shSsiQfJuG+/rti6jHibaNdYMJDcqPM4 H4eXOULqn6BYiWWXNN22xKFLard2RKAvMKZSpshAowa3FeaexerLX/w30h3Qtw/A4u+r gpozhczI7MEUvr4/JDrFZ4jisXHD2z/dE9CI6jYUzCw1Jp6lUWtxYuRsaCEJFaOFRAQK GoVA== X-Gm-Message-State: AKS2vOzVnqmEAly8YdbT4PyXyDlKHLUIkrY+VkOVoBIakOZjQwPJP0Gi 9WR5SLDF6WIYoixJ8fw= X-Received: by 10.80.171.28 with SMTP id s28mr9454767edc.146.1498943750530; Sat, 01 Jul 2017 14:15:50 -0700 (PDT) Received: from ?IPv6:2001:980:d7ed:1:3265:ecff:fe8f:d3ec? ([2001:980:d7ed:1:3265:ecff:fe8f:d3ec]) by smtp.googlemail.com with ESMTPSA id w49sm4248883eda.61.2017.07.01.14.15.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 01 Jul 2017 14:15:49 -0700 (PDT) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= To: freebsd ports Cc: freebsd-ports-announce@freebsd.org, ports-developers@FreeBSD.org Reply-To: freebsd ports From: =?UTF-8?Q?Ren=c3=a9_Ladan?= Subject: New 2017Q3 branch Message-ID: Date: Sat, 1 Jul 2017 23:15:37 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="5vKvEv6ex3tNKAiHSJrFsGW7M1vcmepaa" 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, 01 Jul 2017 21:15:53 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --5vKvEv6ex3tNKAiHSJrFsGW7M1vcmepaa Content-Type: multipart/mixed; boundary="OqJwMuJ5ub4o1JnL7HdXrjrxISMKcRpox"; protected-headers="v1" From: =?UTF-8?Q?Ren=c3=a9_Ladan?= Reply-To: freebsd ports To: freebsd ports Cc: freebsd-ports-announce@freebsd.org, ports-developers@FreeBSD.org Message-ID: Subject: New 2017Q3 branch --OqJwMuJ5ub4o1JnL7HdXrjrxISMKcRpox Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Hi, The 2017Q3 branch has been created. It means that the next update on the quarterly packages will be on the 2017Q3 branch. A lot of things happened in the last three months: - pkg 1.10.1 - New USES: cargo, groff, meson - Default version of PostgreSQL switched from 9.3 to 9.5 - Default version of Python 3 switched from 3.5 to 3.6 - Firefox 54.0.1 - Firefox-esr 52.2.1 - Chromium 59.0.3071.115 - Ruby 2.2.7 and 2.3.4 - default generator for USES=3Dcmake ports has been switched to ninja Next quarterly package builds will start on June 2nd, 01:00 UTC and should be available on your closest mirrors few days later. For those stat nerds out there, here's what happened during the last 3 months on head: Number of commits: 7102 Number of committers: 171 Most active committers: 2457 sunpoet 309 amdmi3 252 miwi 186 jrm 181 antoine 155 bapt 151 jbeich 135 kwm 122 olgeni 114 linimon Diffstat: 17826 files changed, 300281 insertions(+), 260178 deletions(-) and on the 2017Q2 branch: Number of commits: 282 Number of committers: 54 Most active committers: 62 jbeich 24 feld 18 riggs 11 sunpoet 10 mat 9 rakuco 8 tz 8 miwi 8 brnrd 8 adamw Diffstat: 2909 files changed, 25534 insertions(+), 17588 deletions(-) Regards, Ren=C3=A9 Ladan --OqJwMuJ5ub4o1JnL7HdXrjrxISMKcRpox-- --5vKvEv6ex3tNKAiHSJrFsGW7M1vcmepaa Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+zdFyG8V6O2sgTL82ClOw7vE19UFAllYEQQACgkQ2ClOw7vE 19UuQgf+Ls+ncSSgM00WlamwK4VKWY+yJTDlAsWTbiyE5Zd49kcVeLz/jUjDiO0Z EDNOARl0w1caaEh0FO9GLk2mfv6aRM3NqHkmbbAc04oLQZ3s7ePokfpPmIdq88Wp zYw5F2O+Whx0MOk0vWbExZKpW8NsvKzvSWVY82sbGXEYjlDUtB+gzlfH3TQVlg2U WRV9x2v3IJIq/X1AfInaMSIfyS+fFPWVyolfcEe1CeWEci1va0b3aavDNmrR2OKE DA1dTE16C8lteYcOtK/jc0+HgigzQDOVxD0ZkDz3z/XVmk17IpX8AjzEKz/2H+vd Ne576CTTtWeUzKis7QyahGjX/2dHug== =8MGO -----END PGP SIGNATURE----- --5vKvEv6ex3tNKAiHSJrFsGW7M1vcmepaa-- From owner-freebsd-ports@freebsd.org Sat Jul 1 21:17: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 F12B8D92F8C for ; Sat, 1 Jul 2017 21:17:25 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thebighonker.lerctr.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D005873112 for ; Sat, 1 Jul 2017 21:17:25 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Content-Type:MIME-Version:Subject:In-Reply-To:Message-ID:To:From :Date:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=O/SvqJyegQvTGYqA6cjaDfVOLLTDaOgrdTSMJ1G/qRg=; b=dukVFllEABy9S7z9h9pjHlU45X WlUI2S0DHZI8twf9TmgqGWy8SkMsg6V9MOL6Bbv3vaj/bctmBDF6JnM5DPqDkqpHAAjCDHbrAu+Pu OBOxwTP2a1UdkX2AtbstZz9waO4RR4rNXNwEp/dgtHF4FdpFxQuRFIkNLyRdS2j9pSHo=; Received: from 66-87-121-186.pools.spcsdns.net ([66.87.121.186]:3434 helo=[30.129.69.186]) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dRPlc-000Ogz-Qq for freebsd-ports@freebsd.org; Sat, 01 Jul 2017 16:17:25 -0500 Date: Sat, 1 Jul 2017 16:17:11 -0500 From: Larry Rosenman To: freebsd ports Message-ID: <4be4ff27-843b-441d-9dbe-67201067f74c@localhost> In-Reply-To: Subject: Re: New 2017Q3 branch MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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: Sat, 01 Jul 2017 21:17:26 -0000 =20 =20 June 3 is long ago. Itym July 3 =20 =20 =20 =20 =20 =20 =20 =20 > =20 > On Jul 1, 2017 at 4:15 PM, wrote: > =20 > =20 > Hi, The 2017Q3 branch has been created. It means that the next update = on the quarterly packages will be on the 2017Q3 branch. A lot of things h= appened in the last three months: - pkg 1.10.1 - New USES: cargo, groff, = meson - Default version of PostgreSQL switched from 9.3 to 9.5 - Default = version of Python 3 switched from 3.5 to 3.6 - =46irefox 54.0.1 - =46iref= ox-esr 52.2.1 - Chromium 59.0.3071.115 - Ruby 2.2.7 and 2.3.4 - default g= enerator for USES=3Dcmake ports has been switched to ninja Next quarterly= package builds will start on June 2nd, 01:00 UTC and should be available= on your closest mirrors few days later. =46or those stat nerds out there= , here's what happened during the last 3 months on head: Number of commit= s: 7102 Number of committers: 171 Most active committers: 2457 sunpoet 30= 9 amdmi3 252 miwi 186 jrm 181 antoine 155 bapt 151 jbeich 135 kwm 122 olg= eni 114 linimon Diffstat: 17826 files changed, 300281 insertions(+), 2601= 78 deletions(-) and on the 2017Q2 branch: Number of commits: 282 Number o= f committers: 54 Most active committers: 62 jbeich 24 feld 18 riggs 11 su= npoet 10 mat 9 rakuco 8 tz 8 miwi 8 brnrd 8 adamw Diffstat: 2909 files ch= anged, 25534 insertions(+), 17588 deletions(-) Regards, Ren=C3=A9 Ladan =20 > =20 From owner-freebsd-ports@freebsd.org Sat Jul 1 21:38: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 76610D9344F for ; Sat, 1 Jul 2017 21:38:36 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F1F93739C6 for ; Sat, 1 Jul 2017 21:38:35 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id w126so137151785wme.0 for ; Sat, 01 Jul 2017 14:38:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=93KUJvDnRL7d7MYCwDnNA+avOD1SVj1ghQUeCcsUV08=; b=pYjBpJmIjTmHzhJCkRWmv3YANtAuXSJMqA73JlcBf5jUwaa+5yS1eERulU+J/xp3sm hom3oT4qkBMeVEmEXiJUOboIi7ccIuGTZnPGvXgyNHD5CvMFPc86c+zGvJe0cCvKZUYK BXXZ1sy9UjjhDp415A4NY8SviL9eKl8JitZM3VAFIuts77vmwvxQnnR8N/0hrfIOHTpd P85oQHn42Q3ebsc0oJNCUbQL7Jft5LzcMGYCIlkWOEsxGNjXwdKvr1PeC6EbGLvBjAIL TTJ1U0a8gaZefiBW34uj/wis7g59L85ouxOenUQ6kigk8XoXE0wXebWzvlrOQNyIMPyS GYUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=93KUJvDnRL7d7MYCwDnNA+avOD1SVj1ghQUeCcsUV08=; b=aZovmDpZYy3g6xMhT4r5jNHAOQgI7fur4YlJza0nSIicvpUBdf1ftz+HuGzM3TuoAi Xt64ppiVoqCZy33aIddgZiDoVmrzk6FUPdAjjHgqpCS0Dy1Z6/bH79w6ULLX8cGpzpcZ BkVXjm4XJEddgsHNU2wVYFJNVPgN6K6r/SExGwTbQkn6DkOoiQgrcln1Uv6Ib72pDp58 RB92oaPuje4a2AHvs4uaUrsFKh4eFzqRysc2wTOHF2K/zv7YepXes368sxQ4SoFOCoxn sx2bz9uEOyvYjBcR6yZDb8I9YGtxNElMyV25F+H2AWsDk2Vfcu2FGFm4sQYCCx3+Pd28 4/3w== X-Gm-Message-State: AKS2vOzTkWf8Bv1B2oc4F/wyx3Yktr/7wrxvn9MPG65FS4PFHLG4Xk7L 62IbACEuq2S4fKf9HpM= X-Received: by 10.80.134.217 with SMTP id 25mr9936624edu.73.1498945114262; Sat, 01 Jul 2017 14:38:34 -0700 (PDT) Received: from ?IPv6:2001:980:d7ed:1:3265:ecff:fe8f:d3ec? ([2001:980:d7ed:1:3265:ecff:fe8f:d3ec]) by smtp.googlemail.com with ESMTPSA id q10sm4189994eda.25.2017.07.01.14.38.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 01 Jul 2017 14:38:33 -0700 (PDT) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Subject: Re: New 2017Q3 branch To: Larry Rosenman , freebsd ports References: <4be4ff27-843b-441d-9dbe-67201067f74c@localhost> From: =?UTF-8?Q?Ren=c3=a9_Ladan?= Message-ID: Date: Sat, 1 Jul 2017 23:38:33 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <4be4ff27-843b-441d-9dbe-67201067f74c@localhost> Content-Type: text/plain; charset=utf-8 Content-Language: en-US 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: Sat, 01 Jul 2017 21:38:36 -0000 On 01-07-2017 23:17, Larry Rosenman wrote: > > > June 3 is long ago. Itym July 3 > [..snipped unreadable original :( ...] Ah yes, July 2nd will be when the new packages will start building. Thanks for catching this. René From owner-freebsd-ports@freebsd.org Sat Jul 1 22:36:41 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 BD950D94497 for ; Sat, 1 Jul 2017 22:36:41 +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 426B9752D4; Sat, 1 Jul 2017 22:36:40 +0000 (UTC) (envelope-from adamw@adamw.org) Received: by apnoea.adamw.org (OpenSMTPD) with ESMTPSA id befa35aa TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sat, 1 Jul 2017 16:36:34 -0600 (MDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: New 2017Q3 branch From: Adam Weinberger In-Reply-To: Date: Sat, 1 Jul 2017 16:36:32 -0600 Cc: Larry Rosenman , freebsd ports Content-Transfer-Encoding: quoted-printable Message-Id: <2E51384D-1681-4DC2-9FF6-6754884E85CD@adamw.org> References: <4be4ff27-843b-441d-9dbe-67201067f74c@localhost> To: =?utf-8?Q?Ren=C3=A9_Ladan?= 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, 01 Jul 2017 22:36:41 -0000 > On 1 Jul, 2017, at 15:38, Ren=C3=A9 Ladan wrote: >=20 > On 01-07-2017 23:17, Larry Rosenman wrote: >>=20 >>=20 >> June 3 is long ago. Itym July 3 >>=20 > [..snipped unreadable original :( ...] >=20 > Ah yes, July 2nd will be when the new packages will start building. > Thanks for catching this. I was looking forward to a whole year of no package build failure = notices. # Adam --=20 Adam Weinberger adamw@adamw.org https://www.adamw.org