From owner-freebsd-ports@freebsd.org Sun Dec 11 01:15:50 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B142C65313 for ; Sun, 11 Dec 2016 01:15:50 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C81A2989 for ; Sun, 11 Dec 2016 01:15:49 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-vk0-x234.google.com with SMTP id 137so26279437vkl.0 for ; Sat, 10 Dec 2016 17:15:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=F2D47RPyI0P1hPGQvLNBL6sZ28fQOPvqaB/11lCv0Ic=; b=g57DXklPu6EdUs3QsirXKZZ/Ell70jFRcvMPZUoFRYuyFxbE5JLFLMM6USXyljmePk tNBpftZthKO9UDG/+oV68n2UG7THJ5CvtyEKg4njmKqW0JdNF2brpFyp2eA74jYYdJEj qJHfmkJQd+HqZTcKvQNY8FMURBji2yAylC/KjHUfx0PIsIhUW0OkrUmuTMKxfv4r5R/e jdtX8YT4Cjx4cArCfrk+R999An8YGzzACMgV/iyVPXlw7XSGcIfY3KvbiaCy1jAxF2Vr W8DdGvYnYoLXyjYcz5wXBETt/MriqxmHg1KKWIjNGQuLRB+3uRErH6OS9qTIE14ysbaz psgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=F2D47RPyI0P1hPGQvLNBL6sZ28fQOPvqaB/11lCv0Ic=; b=lXTcdLi5YdI2Yy8NtDDSnusobBPp74z5VwDQuBL+Mho/haE1fXq9G/HxAionEleaW8 rko8vnM7g4yWN6HJF/NxyfABTLiLwyksOasI4dq+KW2CKPAfhPUL1Pu1jglv//d1QAPG ONYx2Url2qxXyvSWS0cUkgR1CeZUSHrt0RhjlxiAW3mJKACS4y5mAHolKlxMGcnNxFYb Thhy0nyLeeR0ieMfBJGSpHwkjhgZmAgRPFfAaXw8BS0lWXTaUvNa1xaE/vuBWU62sGL3 NZG/OzY0x3dl9gGDdHe1BqR6MpOekedsfqUjltRc1QwUkItaiCI5TJmi5CAEf3UXpFeQ PAUg== X-Gm-Message-State: AKaTC01lgTtuArH010DHviKkhTpczmGL5KtuDifyG2EZ19weDK1EElrMgSvA+fmR3VqVXUPpVbAtrmE+luWVnw== X-Received: by 10.31.237.131 with SMTP id l125mr34174762vkh.56.1481418948962; Sat, 10 Dec 2016 17:15:48 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.106.66 with HTTP; Sat, 10 Dec 2016 17:15:48 -0800 (PST) In-Reply-To: <5D167804-D5FF-4799-9260-D900D2A8B7F3@kreme.com> References: <86zik4nr4l.wl-herbert@mailbox.org> <5D167804-D5FF-4799-9260-D900D2A8B7F3@kreme.com> From: Kevin Oberman Date: Sat, 10 Dec 2016 17:15:48 -0800 X-Google-Sender-Auth: 7ZRwghgrXeD_GIR_EDt-u0wrszU Message-ID: Subject: Re: pkg 1.9.4 To: "@lbutlr" Cc: 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: Sun, 11 Dec 2016 01:15:50 -0000 On Sat, Dec 10, 2016 at 12:55 PM, @lbutlr wrote: > On 10 Dec 2016, at 01:08, Herbert J. Skuhra wrote: > > Lewis Butler write: > >> Got this when trying to update to pkg-1.9.4 > >> /bin/sh ../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. > -I.. -I../compat -DWITH_SSL -Wno-pointer-sign -shared -O2 -pipe > -Wno-error -fstack-protector -fno-strict-aliasing -Wall > -Wno-unused-function -D_BSD_SOURCE -DINET6=1 -MT > libfetch/libfetch_la-common.lo -MD -MP -MF libfetch/.deps/libfetch_la-common.Tpo > -c -o libfetch/libfetch_la-common.lo `test -f 'libfetch/common.c' || echo > './'`libfetch/common.c > >> libtool: compile: cc -DHAVE_CONFIG_H -I. -I.. -I../compat -DWITH_SSL > -Wno-pointer-sign -O2 -pipe -Wno-error -fstack-protector > -fno-strict-aliasing -Wall -Wno-unused-function -D_BSD_SOURCE -DINET6=1 -MT > libfetch/libfetch_la-common.lo -MD -MP -MF libfetch/.deps/libfetch_la-common.Tpo > -c libfetch/common.c -fPIC -DPIC -o libfetch/.libs/libfetch_la-common.o > >> libfetch/common.c:52:10: fatal error: 'openssl/x509v3.h' file not found > >> #include > >> ^ > >> 1 error generated. > >> *** [libfetch/libfetch_la-common.lo] Error code 1 > >> > >> make[6]: stopped in /usr/ports/ports-mgmt/pkg/work/pkg-1.9.4/external > > > > Does this file exist on your system? > > > > /usr/include/openssl/x509v3.h > > No > > > /usr/local/include/openssl/x509v3.h > > Yes. > > # ls -ls /usr/local/include/openssl/x509v3.h > 80 -rw-r--r-- 1 root wheel 40389 Dec 9 17:50 > /usr/local/include/openssl/x509v3.h > > > What's in your /etc/make.conf? > > DEFAULT_VERSIONS+=linux=f10 > DEFAULT_VERSIONS+=ssl=openssl > > > Does it work if you do: > > > > # make clean > > # make __MAKE_CONF=/dev/null > > No. > > libfetch/common.c:52:10: fatal error: 'openssl/x509v3.h' file not found > #include > ^ > 1 error generated. > *** [libfetch/libfetch_la-common.lo] Error code 1 While I can pretty much guess, what is in /etc/src.conf? -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-ports@freebsd.org Sun Dec 11 02:35:21 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A312C6F858 for ; Sun, 11 Dec 2016 02:35:21 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-162.reflexion.net [208.70.211.162]) (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 D5672B17 for ; Sun, 11 Dec 2016 02:35:20 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 30445 invoked from network); 11 Dec 2016 02:08:39 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 11 Dec 2016 02:08:39 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.20.0) with SMTP; Sat, 10 Dec 2016 21:08:47 -0500 (EST) Received: (qmail 14695 invoked from network); 11 Dec 2016 02:08:47 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 11 Dec 2016 02:08:47 -0000 Received: from [192.168.1.118] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id C089EEC91E6; Sat, 10 Dec 2016 18:08:38 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?] From: Mark Millard In-Reply-To: <487153E5-EF53-4960-9364-23992D7E0F76@dsl-only.net> Date: Sat, 10 Dec 2016 18:08:38 -0800 Cc: Dimitry Andric , svn-ports-head@freebsd.org, FreeBSD Ports Content-Transfer-Encoding: quoted-printable Message-Id: References: <86C72DB2-B9ED-4512-A88C-BD1D9A23806F@dsl-only.net> <9D54F0CC-F38C-4CCE-BC33-25C1457BD44B@FreeBSD.org> <5C936BA8-6941-431A-B05F-31030816F85C@dsl-only.net> <487153E5-EF53-4960-9364-23992D7E0F76@dsl-only.net> To: Gerald Pfeifer X-Mailer: Apple Mail (2.3251) 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, 11 Dec 2016 02:35:21 -0000 [Top post of example lack of lang/gcc6-devel vs. lan/gcc6 substitutability. Context /usr/ports/ at -r428325 (other than a few specially controlled items.] After installing lang/gcc6-devel something else indirectly forced lang/gcc6 to try to build. The attempt failed with: Installing gcc6-6.2.0... pkg-static: gcc6-6.2.0 conflicts with gcc6-devel-6.2.1.s20161201 = (installs files into the same place). Problematic file: = /usr/local/bin/x86_64-portbld-freebsd12.0-c++6 *** Error code 70 Stop. make[1]: stopped in /usr/ports/lang/gcc6 *** Error code 1 The specific example turns out to be. . . emulators/virtualbox-ose-additions leads to: =3D=3D=3D>>> The following actions will be taken if you choose to = proceed: Upgrade virtualbox-ose-additions-5.1.8 to = virtualbox-ose-additions-5.1.10 Install devel/kBuild Install lang/gcc6 Install textproc/flex and lang/gcc6 tries to build during devel/kBuild and the 3 non-lang/gcc6 items above have: # grep -i gcc emulators/virtualbox-ose-additions/Makefile = devel/kBuild/Makefile textproc/flex/Makefile=20 emulators/virtualbox-ose-additions/Makefile:CONFIGURE_ARGS+=3D = --nofatal --with-gcc=3D"${CC}" --with-g++=3D"${CXX}" emulators/virtualbox-ose-additions/Makefile: @${ECHO} 'VBOX_GCC_std =3D= -std=3Dc++11' >> ${WRKSRC}/LocalConfig.kmk emulators/virtualbox-ose-additions/Makefile: @${ECHO} = 'VBOX_GCC_Wno-unused-parameter =3D -Wno-unused-parameter' >> \ devel/kBuild/Makefile:USE_GCC=3D any devel/kBuild/Makefile: ${REINPLACE_CMD} -e 's|gcc|${CC}|g' $$f = ; \ In a context with: # pkg info | grep -i gcc gcc6-devel-6.2.1.s20161201 GNU Compiler Collection 6 powerpc64-gcc-6.2.0 Cross GNU Compiler Collection for = powerpc64 powerpc64-xtoolchain-gcc-0.1 Pre seeded toolchain to cross build = FreeBSD base # more /etc/make.conf=20 WANT_QT_VERBOSE_CONFIGURE=3D1 # DEFAULT_VERSIONS+=3Dperl5=3D5.24 WRKDIRPREFIX=3D/usr/obj/portswork WITH_DEBUG=3D WITH_DEBUG_FILES=3D MALLOC_PRODUCTION=3D So apparently lang/gcc6-devel can not substitute for lang/gcc6 automatically. Now that devel/powerpc64-gcc is 6.2.0 based it and lang/gcc6 may also conflict (I do not know yet: build in progress). =3D=3D=3D Mark Millard markmi at dsl-only.net Older material: On 2016-Nov-26, at 4:16 PM, Mark Millard wrote: > On 2016-Nov-25, at 11:47 PM, Gerald Pfeifer = wrote: >=20 >> On Fri, 25 Nov 2016, Mark Millard wrote: >>> I wonder if that leaves lang/gcc and lang/gcc49 as conflicting. >>=20 >> Yes, these two ports conflict for the time being, and are properly >> marked as such. >>=20 >> (And I am looking for a more elegant approach going forward, in=20 >> particular when we move into GCC 5 territory where, based on input=20 >> from Tijl and others, we now distinguish between lang/gcc5 and=20 >> lang/gcc5-devel.) >=20 > That explains why I've only had lang/gcc5 vs. devel/powerpc64-gcc > conflicts at times: devel/powerpc64-gcc is not treated as a 3rd > alternative to lang/gcc5-devel and lang/gcc5 and it overlaps with > lang/gcc5 when the .x part of the versions (of .x.y) happen to be > the same. >=20 > [Long ago it was devel/powerpc64-gcc and lang/gcc49 conflicts.] >=20 > devel/powerpc64-gcc is currently a gcc5 variant. I actually > install and use devel/powerpc64-xtoolchain-gcc and its > devel/powerpc64-gcc on the powerpc64 contexts that I have. (This > requires a staging-failure workaround.) I learned to avoid > having lang/gcc5 (in more modern times). Sounds like I could > have lang/gcc5-devel without conflicts. >=20 > I use devel/powerpc64-gcc for "self hosted cross builds" in order > to have a modern libc++ based powerpc64 environment without > requiring actual cross builds. [I've never gotten lib32 to > work under this technique so I build without it.] >=20 >>> But luckily so far I've not picked to build anything that built >>> lang/gcc. Or, more likely(?), if some gcc is already installed it >>> is used instead if lang/gcc is not installed yet. >>=20 >> Correct. If lang/gcc49 or lang/gcc is installed, either of the >> two is picked up; if a newer version is installed and USE_GCC=3Dyes >> or USE_GCC=3DX.Y+ are requested (and the installed version is newer), >> that one is used. >>=20 >> Nothing to do with luck on your side, Mark. Rather, design and=20 >> implementation in the Ports Collection. :-) >>=20 >> Gerald >=20 >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Sun Dec 11 02:40:18 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 453EEC6F97B for ; Sun, 11 Dec 2016 02:40:18 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (mail.covisp.net [65.121.55.42]) (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 3057EC0F for ; Sun, 11 Dec 2016 02:40:17 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (localhost [127.0.0.1]) by mail.covisp.net (Postfix) with ESMTP id 3tbqvP2mBGzvBRM; Sat, 10 Dec 2016 19:40:17 -0700 (MST) X-Virus-Scanned: amavisd-new at covisp.net Received: from mail.covisp.net ([127.0.0.1]) by mail.covisp.net (mail.covisp.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oQ-ZRBbuMeMY; Sat, 10 Dec 2016 19:40:12 -0700 (MST) From: "@lbutlr" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: pkg 1.9.4 Date: Sat, 10 Dec 2016 19:40:11 -0700 References: <86zik4nr4l.wl-herbert@mailbox.org> <5D167804-D5FF-4799-9260-D900D2A8B7F3@kreme.com> To: freebsd-ports@freebsd.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3259) 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, 11 Dec 2016 02:40:18 -0000 On 10 Dec 2016, at 18:15, Kevin Oberman wrote: > While I can pretty much guess, what is in /etc/src.conf? I do not have /etc/src.conf # locate src.conf /usr/share/man/man5/src.conf.5.gz # From owner-freebsd-ports@freebsd.org Sun Dec 11 03:08:36 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0ABA3C652FA for ; Sun, 11 Dec 2016 03:08:36 +0000 (UTC) (envelope-from gkreme@gmail.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B869E1C22 for ; Sun, 11 Dec 2016 03:08:35 +0000 (UTC) (envelope-from gkreme@gmail.com) Received: by mail-io0-x233.google.com with SMTP id h30so120778159iod.2 for ; Sat, 10 Dec 2016 19:08:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=SZ6X9S1rCbZYPMqzLXnE6HDXiQYSAoLMnoazMcz6T3k=; b=qMoRSxNUze2EMXlc2kxzJD79wCOSAeteHgbmKv96ZNUNTfXy6YA2/sXs1S274P8+Fi 1sZ9yb99vL9CEtC5zaStHYz0kRuI2Yz2KJAJ7eaOxg/ZgAfu88DQDOY3q0p+QagCQxWH D9/si1qlyQ4XcsndnDftGYUbKHgFvujOr/IgS6+EtFbRjyldXm1CvFbs8y+Bd5gDL0ob pCMZqj4DNzsaoo4bKFcL7nHSN+8cpG+LMMTi4G4erTwIrOMntoTmjKn3nlBVhGAw8nQ3 MnNdg4G37s9XyU6UKiFRQJYkX7q4COlJcBm+p4PdyVm++fTFSAkwiiQSA0IWbYTM8fAb ToSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=SZ6X9S1rCbZYPMqzLXnE6HDXiQYSAoLMnoazMcz6T3k=; b=ZpxD1aSAHJAW7IiS+gg0YH8lKP0FRl3nMhXHqQ+VOWnI5z1Nn58fwXWL0fqe8UJKRk lib8wbAHxi+BPERubTMFP/Q43dbzAaSY3Pg8Wl5GQeulUgCnRyHtPm1kc8VQaaUbAEko gdq7P+OAYhgXGFZOewPvKXqBbuKyHoWB417uI1BTd980J5Ki2xNN0nDJpUt02jXwaau3 4E6kCGGQzBRqHX3DUbu3CZmeH3bb+xc9N+3wOgwOEP/UW19vE4VcCyph/pwRkpk6nGA5 ZaKEXjloO/DSBl+21UKC80yZyo0ZwotWyqHBmCjSz+TQAwqMDJwIFgbgi1uqzoKZd2Kq ZFeA== X-Gm-Message-State: AKaTC03qiiT3WlP+0fGhUmLzQZL9Fd3iNCZ8botz6ui3mYQAZghvDCkODw1nqdWf+Z9ZJA== X-Received: by 10.36.242.1 with SMTP id j1mr4746596ith.5.1481425713680; Sat, 10 Dec 2016 19:08:33 -0800 (PST) Received: from [10.0.0.11] (23-24-150-141-static.hfc.comcastbusiness.net. [23.24.150.141]) by smtp.gmail.com with ESMTPSA id p71sm17294888ioe.33.2016.12.10.19.08.32 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 10 Dec 2016 19:08:32 -0800 (PST) From: Lewis Butler Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: [Solved?] Re: pkg 1.9.4 Date: Sat, 10 Dec 2016 20:08:31 -0700 References: To: freebsd-ports@freebsd.org In-Reply-To: Message-Id: <028983C3-14C1-4112-9D38-17E8C6D5BC49@gmail.com> X-Mailer: Apple Mail (2.3259) 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, 11 Dec 2016 03:08:36 -0000 On 09 Dec 2016, at 17:43, Lewis Butler wrote: > Got this when trying to update to pkg-1.9.4 >=20 > /bin/sh ../libtool --tag=3DCC --mode=3Dcompile cc -DHAVE_CONFIG_H = -I. -I.. -I../compat -DWITH_SSL -Wno-pointer-sign -shared -O2 -pipe = -Wno-error -fstack-protector -fno-strict-aliasing -Wall = -Wno-unused-function -D_BSD_SOURCE -DINET6=3D1 -MT = libfetch/libfetch_la-common.lo -MD -MP -MF = libfetch/.deps/libfetch_la-common.Tpo -c -o = libfetch/libfetch_la-common.lo `test -f 'libfetch/common.c' || echo = './'`libfetch/common.c > libtool: compile: cc -DHAVE_CONFIG_H -I. -I.. -I../compat -DWITH_SSL = -Wno-pointer-sign -O2 -pipe -Wno-error -fstack-protector = -fno-strict-aliasing -Wall -Wno-unused-function -D_BSD_SOURCE -DINET6=3D1 = -MT libfetch/libfetch_la-common.lo -MD -MP -MF = libfetch/.deps/libfetch_la-common.Tpo -c libfetch/common.c -fPIC -DPIC = -o libfetch/.libs/libfetch_la-common.o > libfetch/common.c:52:10: fatal error: 'openssl/x509v3.h' file not = found > #include I created the directory /usr/include/openssl/ cd /usr/include/openssl ln -s /usr/local/include/openssl/* . then I was able to make pkg. Not sure why, but = /usr/local/library/openssl seemed to be where openssl was installed but = the packages are looking for /usr/library/openssl. I'm sure this is not the preferred way to do this. There is also an openssl-1.0.1p folder in /usr/include/ with rather old = files in it. I plan on moving it aside and seeing what happens. From owner-freebsd-ports@freebsd.org Sun Dec 11 09:39:31 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A122C72C4E; Sun, 11 Dec 2016 09:39:31 +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 68FB218A4; Sun, 11 Dec 2016 09:39:30 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from anthias (vie-188-118-249-201.dsl.sil.at [188.118.249.201]) (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 08EE93F530; Sun, 11 Dec 2016 04:39:27 -0500 (EST) Date: Sun, 11 Dec 2016 10:39:26 +0100 (CET) From: Gerald Pfeifer To: Mark Millard , vbox@FreeBSD.org cc: Dimitry Andric , svn-ports-head@freebsd.org, freebsd-ports@freebsd.org Subject: Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?] In-Reply-To: Message-ID: References: <86C72DB2-B9ED-4512-A88C-BD1D9A23806F@dsl-only.net> <9D54F0CC-F38C-4CCE-BC33-25C1457BD44B@FreeBSD.org> <5C936BA8-6941-431A-B05F-31030816F85C@dsl-only.net> <487153E5-EF53-4960-9364-23992D7E0F76@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2016 09:39:31 -0000 Hi Mark, On Sat, 10 Dec 2016, Mark Millard wrote: > [Top post of example lack of lang/gcc6-devel vs. lan/gcc6 > substitutability. Context /usr/ports/ at -r428325 (other > than a few specially controlled items.] I had another look, and lang/gcc6 and lang/gcc6-devel really are substitutable in what they provide. > After installing lang/gcc6-devel something else indirectly > forced lang/gcc6 to try to build. The attempt failed with: That means that "something else indirectly forc[ing] lang/gcc6" is what appears to be going on here. I double checked Mk/bsd.gcc.mk and failed to find anything (which also would be surprising given no other reports in the last decade). vbox@, any ideas? Gerald > The specific example turns out to be. . . > > emulators/virtualbox-ose-additions leads to: > > ===>>> The following actions will be taken if you choose to proceed: > Upgrade virtualbox-ose-additions-5.1.8 to virtualbox-ose-additions-5.1.10 > Install devel/kBuild > Install lang/gcc6 > Install textproc/flex > > and lang/gcc6 tries to build during devel/kBuild and the 3 > non-lang/gcc6 items above have: > > # grep -i gcc emulators/virtualbox-ose-additions/Makefile devel/kBuild/Makefile textproc/flex/Makefile > emulators/virtualbox-ose-additions/Makefile:CONFIGURE_ARGS+= --nofatal --with-gcc="${CC}" --with-g++="${CXX}" > emulators/virtualbox-ose-additions/Makefile: @${ECHO} 'VBOX_GCC_std = -std=c++11' >> ${WRKSRC}/LocalConfig.kmk > emulators/virtualbox-ose-additions/Makefile: @${ECHO} 'VBOX_GCC_Wno-unused-parameter = -Wno-unused-parameter' >> \ > devel/kBuild/Makefile:USE_GCC= any > devel/kBuild/Makefile: ${REINPLACE_CMD} -e 's|gcc|${CC}|g' $$f ; \ > > In a context with: > > # pkg info | grep -i gcc > gcc6-devel-6.2.1.s20161201 GNU Compiler Collection 6 > powerpc64-gcc-6.2.0 Cross GNU Compiler Collection for powerpc64 > powerpc64-xtoolchain-gcc-0.1 Pre seeded toolchain to cross build FreeBSD base > > # more /etc/make.conf > WANT_QT_VERBOSE_CONFIGURE=1 > # > DEFAULT_VERSIONS+=perl5=5.24 > WRKDIRPREFIX=/usr/obj/portswork > WITH_DEBUG= > WITH_DEBUG_FILES= > MALLOC_PRODUCTION= > > > So apparently lang/gcc6-devel can not substitute for lang/gcc6 > automatically. > > > > Now that devel/powerpc64-gcc is 6.2.0 based it and lang/gcc6 may also > conflict (I do not know yet: build in progress). > > > > === > Mark Millard > markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Sun Dec 11 09:39:57 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4734BC72CC4 for ; Sun, 11 Dec 2016 09:39:57 +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 0FF481948; Sun, 11 Dec 2016 09:39:57 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.homeoffice.local (ipservice-092-217-062-255.092.217.pools.vodafone-ip.de [92.217.62.255]) by host64.shmhost.net (Postfix) with ESMTPSA id 6D07382815; Sun, 11 Dec 2016 10:39:54 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: net/haproxy 1.7.0 : libressl support From: Franco Fichtner In-Reply-To: Date: Sun, 11 Dec 2016 10:39:53 +0100 Cc: Luca Pizzamiglio , FreeBSD Ports , Bernard Spil Content-Transfer-Encoding: quoted-printable Message-Id: <2A11D916-CC3A-4BD8-8830-77C6D3E7E521@lastsummer.de> References: <2C9DA2D0-81DD-40B3-9E43-FE5338D80844@gmail.com> To: Dmitry Sivachenko X-Mailer: Apple Mail (2.3251) 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: Sun, 11 Dec 2016 09:39:57 -0000 > On 9 Dec 2016, at 11:51 AM, Dmitry Sivachenko = wrote: >=20 > If they reject it and refuse to support libressl for some reason, we = will not add your patches too, because this is not something = FreeBSD-specific. Strongswan developers said similar things. Unfortunately, we have very good support of LibreSSL in the FreeBSD ports tree since 2015. No reason to flush this down the toilet, not yet anyway if the patches work. We used to have this patch, it still fixes strongswan, likely fixes haproxy 1.7: https://github.com/opnsense/ports/commit/7e8ea59cabc I brought this up with LibreSSL developers, some other users from different BSD projects noted this needs fixing too. We're not there yet, but we can find a solution if everyone does their part in embracing choice for users. :) Cheers, Franco= From owner-freebsd-ports@freebsd.org Sun Dec 11 10:55:10 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7BD38C71294 for ; Sun, 11 Dec 2016 10:55:10 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-169.reflexion.net [208.70.211.169]) (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 3FAA51956 for ; Sun, 11 Dec 2016 10:55:09 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 14352 invoked from network); 11 Dec 2016 10:56:02 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 11 Dec 2016 10:56:02 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.20.0) with SMTP; Sun, 11 Dec 2016 05:55:19 -0500 (EST) Received: (qmail 15600 invoked from network); 11 Dec 2016 10:55:19 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 11 Dec 2016 10:55:19 -0000 Received: from [192.168.1.118] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 3AFA0EC7977; Sun, 11 Dec 2016 02:55:07 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?] From: Mark Millard In-Reply-To: Date: Sun, 11 Dec 2016 02:55:06 -0800 Cc: vbox@FreeBSD.org, Dimitry Andric , svn-ports-head@freebsd.org, freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <86C72DB2-B9ED-4512-A88C-BD1D9A23806F@dsl-only.net> <9D54F0CC-F38C-4CCE-BC33-25C1457BD44B@FreeBSD.org> <5C936BA8-6941-431A-B05F-31030816F85C@dsl-only.net> <487153E5-EF53-4960-9364-23992D7E0F76@dsl-only.net> To: Gerald Pfeifer X-Mailer: Apple Mail (2.3251) 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, 11 Dec 2016 10:55:10 -0000 On 2016-Dec-11, at 1:39 AM, Gerald Pfeifer = wrote: > Hi Mark, >=20 > On Sat, 10 Dec 2016, Mark Millard wrote: >> [Top post of example lack of lang/gcc6-devel vs. lan/gcc6 >> substitutability. Context /usr/ports/ at -r428325 (other >> than a few specially controlled items.] >=20 > I had another look, and lang/gcc6 and lang/gcc6-devel really are > substitutable in what they provide. >=20 >> After installing lang/gcc6-devel something else indirectly >> forced lang/gcc6 to try to build. The attempt failed with: >=20 > That means that "something else indirectly forc[ing] lang/gcc6" is > what appears to be going on here. I double checked Mk/bsd.gcc.mk > and failed to find anything (which also would be surprising given > no other reports in the last decade). >=20 > vbox@, any ideas? >=20 > Gerald Hi Gerald, I reported already that devel/kBuild/Makefile has in its Makefile: USE_GCC=3D any and devel/kBuild is what causes the lang/gcc* build. (I reported more than that but it is the part relevant here.) Additional information (gained later) is that if I "pkg delete gcc6-devel" then instead of devel/kBuild trying to install lang/gcc6 it tries to install lang/gcc (no number). If I clean that out and put back lang/gcc6-devel and try again it goes back to trying to install lang/gcc6 . It appears to be picking up that a gcc is installed when lang/gcc6-devel and that it is is version 6 based but then it looks for lang/gcc6 specifically but does not find it and so tries to install lang/gcc6. Its identification of the version is not enough to identify what specific gcc port to look for but it only looks for the one possible source to satisfy the dependency --and not finding that specific port it then tries to install that specific port that it did not find. By contrast when no lang/gcc* is present (none installed) because I've also deleted lang/gcc6-devel it goes for the default gcc rather than a more specific version: lang/gcc . This varying behavior might give a clue about what to look for in the USE_GCC=3Dany mechanism. Side notes: On powerpc64 I was able to install both devel/powerpc64-gcc (with work around for the fact that it is not a true cross compiler in this context so 6 files do not stage right) and lang/gcc6 and no conflict was reported. The mentioned workaround for my context is: # more ~/powerpc64-gcc_fixup.sh=20 #!/bin/sh cp -ax = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/.build/gcc/gcov = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/bin/= powerpc64-unknown-freebsd12.0-gcov cp -ax = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/.build/gcc/gcov-tool= = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/bin/= powerpc64-unknown-freebsd12.0-gcov-tool gzip -c = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/gcc-*/gcc/doc/cpp.1 = > = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/= man1/powerpc64-unknown-freebsd12.0-cpp.1.gz gzip -c = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/.build/gcc/doc/g++.1= > = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/= man1/powerpc64-unknown-freebsd12.0-g++.1.gz gzip -c = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/.build/gcc/doc/gcc.1= > = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/= man1/powerpc64-unknown-freebsd12.0-gcc.1.gz gzip -c = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/gcc-*/gcc/doc/gcov.1= > = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/= man1/powerpc64-unknown-freebsd12.0-gcov.1.gz after which I use -C with portmaster to let it continue now that it can find the 6 files when it tries to. There are other issues in how things are operating and I'll not look into them until after I've gotten some sleep (or even later then that). =3D=3D=3D Mark Millard markmi at dsl-only.net > The specific example turns out to be. . . >=20 > emulators/virtualbox-ose-additions leads to: >=20 > =3D=3D=3D>>> The following actions will be taken if you choose to = proceed: > Upgrade virtualbox-ose-additions-5.1.8 to = virtualbox-ose-additions-5.1.10 > Install devel/kBuild > Install lang/gcc6 > Install textproc/flex >=20 > and lang/gcc6 tries to build during devel/kBuild and the 3 > non-lang/gcc6 items above have: >=20 > # grep -i gcc emulators/virtualbox-ose-additions/Makefile = devel/kBuild/Makefile textproc/flex/Makefile=20 > emulators/virtualbox-ose-additions/Makefile:CONFIGURE_ARGS+=3D = --nofatal --with-gcc=3D"${CC}" --with-g++=3D"${CXX}" > emulators/virtualbox-ose-additions/Makefile: @${ECHO} 'VBOX_GCC_std = =3D -std=3Dc++11' >> ${WRKSRC}/LocalConfig.kmk > emulators/virtualbox-ose-additions/Makefile: @${ECHO} = 'VBOX_GCC_Wno-unused-parameter =3D -Wno-unused-parameter' >> \ > devel/kBuild/Makefile:USE_GCC=3D any > devel/kBuild/Makefile: ${REINPLACE_CMD} -e 's|gcc|${CC}|g' = $$f ; \ >=20 > In a context with: >=20 > # pkg info | grep -i gcc > gcc6-devel-6.2.1.s20161201 GNU Compiler Collection 6 > powerpc64-gcc-6.2.0 Cross GNU Compiler Collection for = powerpc64 > powerpc64-xtoolchain-gcc-0.1 Pre seeded toolchain to cross build = FreeBSD base >=20 > # more /etc/make.conf=20 > WANT_QT_VERBOSE_CONFIGURE=3D1 > # > DEFAULT_VERSIONS+=3Dperl5=3D5.24 > WRKDIRPREFIX=3D/usr/obj/portswork > WITH_DEBUG=3D > WITH_DEBUG_FILES=3D > MALLOC_PRODUCTION=3D >=20 >=20 > So apparently lang/gcc6-devel can not substitute for lang/gcc6 > automatically. >=20 >=20 >=20 > Now that devel/powerpc64-gcc is 6.2.0 based it and lang/gcc6 may also > conflict (I do not know yet: build in progress). >=20 >=20 >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Sun Dec 11 12:40:04 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C58DCC702FB; Sun, 11 Dec 2016 12:40:04 +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 A41741572; Sun, 11 Dec 2016 12:40:04 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from anthias (vie-188-118-249-201.dsl.sil.at [188.118.249.201]) (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 BAE683F531; Sun, 11 Dec 2016 07:40:01 -0500 (EST) Date: Sun, 11 Dec 2016 13:40:00 +0100 (CET) From: Gerald Pfeifer To: Mark Millard cc: vbox@FreeBSD.org, Dimitry Andric , svn-ports-head@freebsd.org, freebsd-ports@freebsd.org Subject: Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?] In-Reply-To: Message-ID: References: <86C72DB2-B9ED-4512-A88C-BD1D9A23806F@dsl-only.net> <9D54F0CC-F38C-4CCE-BC33-25C1457BD44B@FreeBSD.org> <5C936BA8-6941-431A-B05F-31030816F85C@dsl-only.net> <487153E5-EF53-4960-9364-23992D7E0F76@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2016 12:40:04 -0000 On Sun, 11 Dec 2016, Mark Millard wrote: > I reported already that devel/kBuild/Makefile has in its > Makefile: > > USE_GCC= any > > and devel/kBuild is what causes the lang/gcc* build. (I > reported more than that but it is the part relevant here.) I had read that, and I di investigate. USE_GCC=any is the equivalent of USE_GCC=4.2+, and lang/gcc6 and lang/gcc6-devel should both meet this requirement. (In general, do not use a gcc*-devel port unless you really want or need to, though; use the corresponding gcc* port instead.) > Additional information (gained later) is that if I "pkg delete > gcc6-devel" then instead of devel/kBuild trying to install lang/gcc6 > it tries to install lang/gcc (no number). That works as designed. USE_GCC=yes defaults to lang/gcc. USE_GCC=any tries to use an existing GCC system compiler and lang/gcc by default if none is present. > If I clean that out and put back lang/gcc6-devel and try again it > goes back to trying to install lang/gcc6 . That is a little odd. It means gcc6 from lang/gcc6-devel is found and identified as a suitable version of GCC. Then Mk/bsd.gcc.mk adds BUILD_DEPENDS+= gcc6:lang/gcc6 when it resolves USE_GCC=any. That should not trigger and pull in lang/gcc6, though, as long as gcc6 is found. > It appears to be picking up that a gcc is installed when > lang/gcc6-devel and that it is is version 6 based but then > it looks for lang/gcc6 specifically but does not find it > and so tries to install lang/gcc6. Its identification of the > version is not enough to identify what specific gcc port > to look for but it only looks for the one possible source > to satisfy the dependency --and not finding that specific > port it then tries to install that specific port that it > did not find. That's pretty close. It finds the gcc6 binary and hence settles on GCC 6 as the compiler to use, but when resolving dependencies then it apparently does not find the gcc6 binary (or does, and something triggers a full rebuild regardless with lang/gcc6 instead of the original lang/gcc6-devel). Do you, by any chance, have some non-standard settings that would trigger such an unconditional rebuild? In general, for ports work lang/gcc is the one to use, and lang/gccX over lang/gccX-devel. Somehow it feels your setup adds layers of shaky, untested and non-standard elements on top of each other. As far as lang/gcc* ports are concerned, I believe the best use of our time will be moving lang/gcc from GCC 4.9 (where it finally got to) to GCC 5. Gerald From owner-freebsd-ports@freebsd.org Sun Dec 11 18:00:13 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06FD8C72AC9 for ; Sun, 11 Dec 2016 18:00:13 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::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 914081BEC for ; Sun, 11 Dec 2016 18:00:12 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id a197so32202211wmd.0 for ; Sun, 11 Dec 2016 10:00:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=9ag9x7QO/kr+1MDQLNkvKxlzoRCy3jPdqmrxG30TOGU=; b=X50RR+nit5ctt9h1imHFH9FAFY/V2bRsNAkQfX95nNQmk6Z+iul8hiExGOnd4mpTeO /QqLCG45i6RtJQrNBUu1KA5Lq69wQj+lthLKR6FdpnXTgF9os0KUFtaKWQwEh6xkqYk1 Sj8hxEaXzgAzaJU3p0L2F17T2hpToj6ScfaIL0/T5CqIPcJP6Nin+iV1qj3YbD/VTf/3 knn4/LGii2YtSXmRkat8a48f/dfrLdZtslhbbLPagCRn/XUA4+QJK9KQA6Pmbw0sm449 97xpoGk+9i1IOaFvohgek4kYpDh2X7pULJqWfx+Hm265QnvwcGB+Se1AQALa045soRAu PuQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=9ag9x7QO/kr+1MDQLNkvKxlzoRCy3jPdqmrxG30TOGU=; b=WXv2pWyv4FnA3YM5eLgOEXQE8qMT57Y2J9I2xgIm/bRBdvlPZ2H9g61u/98EpQegwY EJYftexO+FmselTAXxbSuFwCilg0RBwBK4wjXBivq8PXAWlHr3SLJVRpBsXNxvqBzA3a WFVAPGuoCJ5e76veCTJjt7Bv02HkolQSGAVvbmhEy2C/ZqWcr4CqVxy/ouvFjlMDwGHG QKmWNCrluc7FX5BrUI/IPhXGnavwA1Y50iV+KIWb6WmcvcgdNlXmGXsJjM7pRDsv+jVZ 6id+nsePmYH295DbqqO53VkSEOu25q3UQ5F/KzRlw4ByO9tEPqiyyDk6JvKygLSRiSBL FjBw== X-Gm-Message-State: AKaTC01hGL86AJnCU+fw2MsTuRHkinP+0m1q/UM5aeGzwqhWOgG8HclB7leH1qcvSvgfdLIfFO+PDF4v/6xSbA== X-Received: by 10.25.221.208 with SMTP id w77mr5398322lfi.39.1481479210446; Sun, 11 Dec 2016 10:00:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.17.224 with HTTP; Sun, 11 Dec 2016 10:00:09 -0800 (PST) In-Reply-To: References: From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= Date: Sun, 11 Dec 2016 19:00:09 +0100 Message-ID: Subject: Re: Help with C++, gcc4.9 and libstdc++ To: Rainer Hurling Cc: FreeBSD Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2016 18:00:13 -0000 On Tue, Nov 29, 2016 at 9:28 PM, Fernando Apestegu=C3=ADa wrote: > El 29 nov. 2016 18:58, "Rainer Hurling" escribi=C3=B3: >> >> Hi Fernando, >> >> Am 29.11.2016 um 17:50 schrieb Fernando Apestegu=C3=ADa: >> > I maintain a port written mostly in C++ (cad/openvsp). >> > >> > This port used to compile fine in 11 and 10.x in both i386 and amd64. >> > Since Nov 22nd I'm receiving a pkg-fallout for this port in 10.1. The >> > port fails with this message: >> > >> > undefined reference to `__cxa_throw_bad_array_new_length' >> > >> > I assume the source of the problem is defaulting to gcc 4.9 in the >> > ports and it seems to be related to libstdc++ >> > >> > I use USES=3Dcompiler:gcc-c++11-lib in the Makefile since some c++11 >> > features are required. Any idea of why this could be failing to link?. >> > What puzzles me is that it compiles fine with gcc 4.9 in 10.2. >> > >> > Thanks in advance. Until that time comes, I would like to send an update but I'm having some problems with it. I need a c++11 lib but I need gcc < 4.9 for the port to compile on 10.1 (in < 10.x it doesn't build due to the lack of certain math functions and in > 10.2 it compiles nicely). I've been playing around with USE_GCC =3D 4.8 to no luck. How can I specify both, gcc 4.8 specifically and still getting all the work behing the gcc-c++11-lib ARG? Thanks in advance. >> >> this also happens with a few other ports, and is described in >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214863 >> >> As far, as I understand, a patch with a workaround will be committed in >> the next time. > > Thanks for the info! > >> >> HTH, >> Rainer From owner-freebsd-ports@freebsd.org Sun Dec 11 22:38:37 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19BF0C72455 for ; Sun, 11 Dec 2016 22:38:37 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm14-vm9.access.bullet.mail.gq1.yahoo.com (nm14-vm9.access.bullet.mail.gq1.yahoo.com [216.39.63.252]) (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 E309E1720 for ; Sun, 11 Dec 2016 22:38:36 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1481495754; bh=X1P63P6gFtjXj3ry6qhixSJaEwnmPcTzIKwSYVvnx7U=; h=From:To:Subject:Date:References:In-Reply-To:From:Subject; b=4oK4cuH8QjRHejpASRzIO/jVehlEFtqTuhEooml+HQDRMl/a3//43aNrbBBETbpuOAWhCZu3wTaY2jsVldeHcttcqSNPjp2EI+QSXPrP3UXRd8gah1z1+WtWsw4qZp21HyMNMef3w2672Flcqea+dCvfaXCngs3SGluOCXwhNFM= Received: from [216.39.60.169] by nm14.access.bullet.mail.gq1.yahoo.com with NNFMP; 11 Dec 2016 22:35:54 -0000 Received: from [67.195.23.147] by tm5.access.bullet.mail.gq1.yahoo.com with NNFMP; 11 Dec 2016 22:35:54 -0000 Received: from [127.0.0.1] by smtp119.sbc.mail.gq1.yahoo.com with NNFMP; 11 Dec 2016 22:35:54 -0000 X-Yahoo-Newman-Id: 444889.14680.bm@smtp119.sbc.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 4t8bqU4VM1mIksynz6eUNrIc.qBRxXxbufRuRluRRChYGbo 1ewBmg49iwZzduW3PtP2REKq1RBEdm3ahPDrLBZ5SFB.aS.90Gm5lUIxPbiK PclUW0mYI_30yBu1z2QJv8h2DlSjhzqRLAZhmDmCZXV.ArvLjc6CdMxXhgTT fCXU.CZuTPrv1PVF2I63ysJzlzFVsAXT0GxRbFD2JmboReuBp19f1fzMYM5c r4Lkg_uRs.GDmJHuBlE7xbJDiuXT7gU9guIDWC4aS6w.49d7czjfcOw9HpnA aaUakepvpdCF.rtHy9zUNsdJmiVZTD4U9tPKfvBBiV24kENcOtbPujbVM.Rb JgP0GmSLHhgzsizBZyPFm7s3urBtfdc1EW4vmyUck4uzc.dZwSW_ZqmokCAX TjbzR74aIOHvQeSim7W.3Ut7PuFzYjUpN738ohROvxXaXiDHKDaaFWHI.lrS Ll5rmdraL4zpvdfv5gqqkgnyOl7gosPNwar81qg_Dk_My3ii0cfL.bPd1pol vcNl.pcVrmrfNGE4ttPerdEERkYQMM966vc7dmpTKI36j9siDwutH53w- X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: freebsd-ports@FreeBSD.org Subject: Re: The ports collection has some serious issues Date: Sun, 11 Dec 2016 17:35:54 -0500 Message-ID: References: <20161208085926.GC2691@gmail.com> In-Reply-To: <20161208085926.GC2691@gmail.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: Sun, 11 Dec 2016 22:38:37 -0000 I have to admit that I avoid ports if at all possible because I've hardly ever been able to do a build that ran to completion. There's always some piece of code that's missing and can't be found, or is the wrong version, et lengthy cetera. I've never done release engineering, but I honestly can't imagine how some of the stuff that makes its way into the ports tree ever got past QA. It would get someone sacked if it happened in industry. If the dev schedule would SLOW DOWN and the commitment switched to quality from the current emphasis on frequency, with separate trees for alpha-, beta-, and real release-quality, fully-vetted code, the ports system might become usable again. From owner-freebsd-ports@freebsd.org Sun Dec 11 22:59:40 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D404C72BB8 for ; Sun, 11 Dec 2016 22:59:40 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-165.reflexion.net [208.70.211.165]) (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 E38B0118 for ; Sun, 11 Dec 2016 22:59:39 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 24453 invoked from network); 11 Dec 2016 23:00:32 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 11 Dec 2016 23:00:32 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.20.0) with SMTP; Sun, 11 Dec 2016 17:59:49 -0500 (EST) Received: (qmail 3551 invoked from network); 11 Dec 2016 22:59:49 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 11 Dec 2016 22:59:49 -0000 Received: from [192.168.1.118] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 4BA6BEC8A8B; Sun, 11 Dec 2016 14:59:37 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?] From: Mark Millard In-Reply-To: Date: Sun, 11 Dec 2016 14:59:36 -0800 Cc: vbox@FreeBSD.org, Dimitry Andric , svn-ports-head@freebsd.org, freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <86C72DB2-B9ED-4512-A88C-BD1D9A23806F@dsl-only.net> <9D54F0CC-F38C-4CCE-BC33-25C1457BD44B@FreeBSD.org> <5C936BA8-6941-431A-B05F-31030816F85C@dsl-only.net> <487153E5-EF53-4960-9364-23992D7E0F76@dsl-only.net> To: Gerald Pfeifer X-Mailer: Apple Mail (2.3251) 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, 11 Dec 2016 22:59:40 -0000 [After "BUILD_DEPENDS+=3D gcc6:lang/gcc6" below shows that portmaster does not do what you indicate the build environment should do. The beginning is not essential material.] On 2016-Dec-11, at 4:40 AM, Gerald Pfeifer = wrote: > On Sun, 11 Dec 2016, Mark Millard wrote: >> I reported already that devel/kBuild/Makefile has in its >> Makefile: >>=20 >> USE_GCC=3D any >>=20 >> and devel/kBuild is what causes the lang/gcc* build. (I >> reported more than that but it is the part relevant here.) >=20 > I had read that, and I di investigate. It was just setup material (context) for what followed. I had no doubt that you had looked into what I'd reported. > USE_GCC=3Dany is the equivalent of USE_GCC=3D4.2+, and lang/gcc6 and > lang/gcc6-devel should both meet this requirement. >=20 > (In general, do not use a gcc*-devel port unless you really want=20 > or need to, though; use the corresponding gcc* port instead.) In genreal I have avoided *-devel's but with with -r428312 having updated the likes of devel/powerpc64-gcc and devel/amd64-gcc and such to be 6.2.0 based I was exploring what combinations of 6.2.0 installations were compatible vs. not. Historically on, e.g., powerpc64, devel/powerpc64-gcc and the matching lang/gcc* by version conflicted so I picked an alternate lang/gcc* if a devel/powerpc64-gcc updated to match what I already had from lang/gcc* . >> Additional information (gained later) is that if I "pkg delete=20 >> gcc6-devel" then instead of devel/kBuild trying to install lang/gcc6=20= >> it tries to install lang/gcc (no number). >=20 > That works as designed. USE_GCC=3Dyes defaults to lang/gcc. = USE_GCC=3Dany=20 > tries to use an existing GCC system compiler and lang/gcc by default = if=20 > none is present. Understood. >> If I clean that out and put back lang/gcc6-devel and try again it=20 >> goes back to trying to install lang/gcc6 . >=20 > That is a little odd. It means gcc6 from lang/gcc6-devel is found > and identified as a suitable version of GCC. Yep: odd. > Then Mk/bsd.gcc.mk adds >=20 > BUILD_DEPENDS+=3D gcc6:lang/gcc6 >=20 > when it resolves USE_GCC=3Dany. >=20 > That should not trigger and pull in lang/gcc6, though, as long > as gcc6 is found. You are wrong relative to portmaster: it uses (from "sh -x" output, including for its relevant recursive uses): # pkg query %n-%v lang/gcc6 as its test and ends up with am empty response that it interprets as needs-installation. By contrast: # pkg query %n-%v lang/gcc6-devel gcc6-devel-6.2.1.s20161201 gives a match and would be classified as installed. The sh -x output that is relevant: + pm_cd /usr/ports/lang/gcc6 + builtin cd /usr/ports/lang/gcc6 + grep -ql ^CONFLICTS Makefile + origin=3Dlang/gcc6 + iport_from_origin lang/gcc6 + local sn dir + [ -n yes ] + pkg query %n-%v lang/gcc6 + return 1 + iport=3D'' + check_exclude lang/gcc6 + [ -n '' ] + return 0 + [ -n '' -a -n '' ] + [ -n '' -a -n '' ] + [ -n '' ] + check_interactive lang/gcc6 + [ -n '' ] + return 0 + update_port lang/gcc6 + local deps + [ -n '' ] + [ -z '' ] + echo '=3D=3D=3D>>> Launching child to install lang/gcc6' =3D=3D=3D>>> Launching child to install lang/gcc6 + dep_of_deps=3D2 + [ -n pm_first_pass ] + [ ! '(' -n '' -a -n '' ')' ] + num_of_deps=3D2 + deps=3D'(2/2)' + term_printf ' >> devel/kBuild >> lang/gcc6 (2/2)' + echo -e '\n=3D=3D=3D>>> emulators/virtualbox-ose-additions >> = devel/kBuild >> lang/gcc6 (2/2)' =3D=3D=3D>>> emulators/virtualbox-ose-additions >> devel/kBuild >> = lang/gcc6 (2/2) + [ -n '' ] + printf '\033]0;portmaster: emulators/virtualbox-ose-additions >> = devel/kBuild >> lang/gcc6 (2/2)\007' ESC]0;portmaster: emulators/virtualbox-ose-additions >> devel/kBuild >> = lang/gcc6 (2/2)^G+ [ -n doing_dep_check -o '(' -n '' -a -n pm_first_pass = ')' ] + unset NO_DEP_UPDATES + [ -z '' -o -n pm_first_pass ] + sh -x /usr/local/sbin/portmaster -D -K lang/gcc6 + trap trap_exit INT >> It appears to be picking up that a gcc is installed when >> lang/gcc6-devel and that it is is version 6 based but then >> it looks for lang/gcc6 specifically but does not find it >> and so tries to install lang/gcc6. Its identification of the >> version is not enough to identify what specific gcc port >> to look for but it only looks for the one possible source >> to satisfy the dependency --and not finding that specific >> port it then tries to install that specific port that it >> did not find. >=20 > That's pretty close. It finds the gcc6 binary and hence settles > on GCC 6 as the compiler to use, but when resolving dependencies > then it apparently does not find the gcc6 binary (or does, and > something triggers a full rebuild regardless with lang/gcc6 instead=20 > of the original lang/gcc6-devel). See above for what portmaster really does. > Do you, by any chance, have some non-standard settings that would > trigger such an unconditional rebuild? I try to be as standard as I can given that I experiment with clang targeting powerpc64 and powerpc and other such oddities and that I want rather current C++ language/library standards. =20 > In general, for ports work lang/gcc is the one to use, and lang/gccX=20= > over lang/gccX-devel. Relative to lang/gcc vs. lang/gcc* . . . A) devel/powerpc64-gcc and devel/amd64-gcc and the like updated to 6.2.0 at -r428312 . and: B) I want the more current C++ status. Historically I have avoided lang/gcc*-devel . But when devel/*-gcc's update versions I tend to experiment with what combinations conflict for installation vs. what combinations to not. > Somehow it feels your setup adds layers of shaky, untested and > non-standard elements on top of each other. Nope. As stands across /usr/src/ and /usr/ports/ I have around 19 patched files. I do tend to have KERNCONF files that include the standard ones and then change a few things. For ports I try to get by with /etc/make.file having: WANT_QT_VERBOSE_CONFIGURE=3D1 # DEFAULT_VERSIONS+=3Dperl5=3D5.24 WRKDIRPREFIX=3D/usr/obj/portswork WITH_DEBUG=3D WITH_DEBUG_FILES=3D MALLOC_PRODUCTION=3D But the binutils vintage problems for powerpc64 (system and head ports) and such lead me to do more for the contexts in which I deal with those. I tend to have powerpc64 and powerpc patches because of my experimenting with clang targeting them and that the standard powerpc64 build does not boot PowerMac G5's reliably. Some patches are ones that someone has requested that I try, usually relative to something that I've reported. I also have ones that work around problems so I can see if there is more to report.=20 > As far as lang/gcc* ports are concerned, I believe the best use > of our time will be moving lang/gcc from GCC 4.9 (where it finally > got to) to GCC 5. The only place that I've been using lang/gcc49 was on powerpc64 for my self-hosted libc++ based powerpc64 system builds: For buildworld buildkernel I used: 0) lang/gcc49 analogously to the clang system compiler 1) devel/powerpc64-sxtoolchain-gcc anlogously to a cross compiler toolchain. This was via SRC_CONF_ENV file content to control what was used. > Gerald =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Sun Dec 11 23:11:29 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BDC0C73168; Sun, 11 Dec 2016 23:11:29 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C16AB9E; Sun, 11 Dec 2016 23:11:28 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 31590125; Sun, 11 Dec 2016 17:11:22 -0600 (CST) Date: Sun, 11 Dec 2016 17:11:21 -0600 From: Mark Linimon To: Mark Millard Cc: Gerald Pfeifer , svn-ports-head@freebsd.org, Dimitry Andric , vbox@FreeBSD.org, freebsd-ports@freebsd.org Subject: Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?] Message-ID: <20161211231120.GA30251@lonesome.com> References: <86C72DB2-B9ED-4512-A88C-BD1D9A23806F@dsl-only.net> <9D54F0CC-F38C-4CCE-BC33-25C1457BD44B@FreeBSD.org> <5C936BA8-6941-431A-B05F-31030816F85C@dsl-only.net> <487153E5-EF53-4960-9364-23992D7E0F76@dsl-only.net> 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: Sun, 11 Dec 2016 23:11:29 -0000 On Sun, Dec 11, 2016 at 02:59:36PM -0800, Mark Millard wrote: > I tend to have powerpc64 and powerpc patches because of my > experimenting with clang targeting them and that the standard > powerpc64 build does not boot PowerMac G5's reliably. Is that on 10, 11 or -current? On 10 I remember being able to boot reliably but would get random crashes every few days. That machine has been offline for months, however. mcl From owner-freebsd-ports@freebsd.org Mon Dec 12 00:44:57 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 33B96C6F56E for ; Mon, 12 Dec 2016 00:44:57 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-167.reflexion.net [208.70.211.167]) (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 E71C11231 for ; Mon, 12 Dec 2016 00:44:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 6294 invoked from network); 12 Dec 2016 00:44:55 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 12 Dec 2016 00:44:55 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.20.0) with SMTP; Sun, 11 Dec 2016 19:44:55 -0500 (EST) Received: (qmail 25552 invoked from network); 12 Dec 2016 00:44:55 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 12 Dec 2016 00:44:55 -0000 Received: from [192.168.1.118] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 75D20EC8FDE; Sun, 11 Dec 2016 16:44:54 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?] From: Mark Millard In-Reply-To: <20161211231120.GA30251@lonesome.com> Date: Sun, 11 Dec 2016 16:44:53 -0800 Cc: Gerald Pfeifer , svn-ports-head@freebsd.org, Dimitry Andric , vbox@FreeBSD.org, freebsd-ports@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: References: <86C72DB2-B9ED-4512-A88C-BD1D9A23806F@dsl-only.net> <9D54F0CC-F38C-4CCE-BC33-25C1457BD44B@FreeBSD.org> <5C936BA8-6941-431A-B05F-31030816F85C@dsl-only.net> <487153E5-EF53-4960-9364-23992D7E0F76@dsl-only.net> <20161211231120.GA30251@lonesome.com> To: Mark Linimon X-Mailer: Apple Mail (2.3251) 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, 12 Dec 2016 00:44:57 -0000 On 2016-Dec-11, at 3:11 PM, Mark Linimon wrote: > On Sun, Dec 11, 2016 at 02:59:36PM -0800, Mark Millard wrote: >> I tend to have powerpc64 and powerpc patches because of my >> experimenting with clang targeting them and that the standard >> powerpc64 build does not boot PowerMac G5's reliably. > > Is that on 10, 11 or -current? Note: My powerpc64 and powerpc experiments have been targeted to exploring having/using a modern context on these processors. I only use gcc 4.2.1 for the TARGET_ARCH=powerpc kernel. I've used more modern gcc's and/or clang for the buildworld's and the powerpc64 buildkernel . I've seen the problem on all 3 and I've used the patch on all 3. Note that the TARGET_ARCH=powerpc builds had no problem booting the G5's, only TARGET_ARCH=powerpc64 did. So I only patched powerpc64. (I've no evidence that the patch would be appropriate on non-PowerMac powerpc64 contexts: these comments are limited in scope.) I no longer actively use 10. I was using 11 once I started testing use of clang 3.8.0 for targeting powerpc64 and powerpc --until I switched to testing clang 3.9.0 and so switched to 12. I'm told that the amount of ram changes how likely the PowerMac G5 boot failures are for TARGET_ARCH=powerpc64. My experience with 8GByte, 12 GByte, and 16 GByte would suggest that this is true: less often on 8GByte than on 16 GByte, for example. The same for 12 vs. 16 --and these two are both so-called "Quad Core" G5s. But I've seen the problem in all 3 contexts for 10, 11, and 12 absent my patch (or variations of it). Nathan Whitehorn recently came up with the explanation of why my patch helped. I'll not go into all the details unless you care. The summary is that FreeBSD's kernel was handling something during Openfirmware being in use but a special register involved did not have the value that FreeBSD required: it had the old Openfirmware value restored to it instead. The patch avoids that restore so that the FreeBSD value is in place. Nathan has made a stab at removing the live Openfirmware use that is involved in the problem but as of yet I've not been able to boot what he last had me try for this. > On 10 I remember being able to boot reliably but would get random crashes > every few days. That machine has been offline for months, however. I had frequent times of trying a dozen times or more (power-on, power-off, power-on, . . .) to boot various 10.x's on the 16 GByte G5 Quad Core that I mostly used. I figured out the patch during 10's time frame as far as my use goes. I've only tried without the patch a little for later 10.x's, 11, and 12. Once booted odd crashes were comparatively rare so solid judgements about that are problematical for my context as far as observed crashes go: I had no evidence to attribute the cause with and a low frequency. The patched code is also used after booting and so should avoid the specific issue later as well. That does not imply that there could not be other problems: FreeBSD and OpenFirmware are likely still not fully matched, just less likely to crash. I've no such odd after-boot-complete crashes under 11 that I remember --nor with the patch under 10.x . 12 has suddenly shutdown without even a console message once. I build it to go to the ddb> prompt --which it also did not do. I will note that at least one other person has made variations of my patch because they had similar problems booting. (I encouraged some testing of disabling more than I'd disabled.) Other folks have reported having the boot problems but as far as I know have not tried some variant of my patch. (I made the smallest change that I could that changed the behavior: I removed just one instruction for the specific special register.) > mcl === Mark Millard markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Mon Dec 12 02:47:54 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75D7CC7396E for ; Mon, 12 Dec 2016 02:47:54 +0000 (UTC) (envelope-from jankyj@unfs.us) Received: from stig.purplehat.org (stig.purplehat.org [50.243.134.106]) (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 468EB1A51 for ; Mon, 12 Dec 2016 02:47:53 +0000 (UTC) (envelope-from jankyj@unfs.us) Received: from localhost (bill.goatse.unfs.us [50.243.134.106]) by stig.purplehat.org (Postfix) with ESMTP id 9AEE45AD17; Sun, 11 Dec 2016 19:42:14 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=unfs.us; s=mail; t=1481510534; bh=AXNH1+Q6oZg+p29/p47UzHXMgnwxV2oBmibruCWVeKU=; h=Subject:To:References:From:Date:In-Reply-To; b=DzeQmwOK+/aUcKn9WMP+RAQJqPxSHJTAYdGmkXWnZea+z+LAM1Vqgu//BiDozDPJ7 xD+ZIdZxAPXTQ3zr0/9e+A41JLzZtm1F8AZf634V0rB3DIa0eBmLNJ7n5WLUVHINkl w699+OqYK1+Q5DrRI35kTFCjYgrfJ8YS7fvwh69Q= Received: from stig.purplehat.org ([50.243.134.106]) by localhost (stig.purplehat.org [50.243.134.106]) (maiad, port 10024) with ESMTP id 31407-10; Sun, 11 Dec 2016 19:42:12 -0700 (MST) Received: from [10.1.10.30] (unknown [10.1.10.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: jankyj@unfs.us) by stig.purplehat.org (Postfix) with ESMTPSA id 88E555AD07; Sun, 11 Dec 2016 19:42:12 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=unfs.us; s=mail; t=1481510532; bh=AXNH1+Q6oZg+p29/p47UzHXMgnwxV2oBmibruCWVeKU=; h=Subject:To:References:From:Date:In-Reply-To; b=gAxzrejhYwLTTkIEfLr+qlxiStP69qM9HDWf5UY0WIlPAcVm8yBAl9mW1GtucgYxj r4kWaknsLQ8E0g72TdKph4EEfburCrGzCcS28XTBFbDjX4xCuigVYcw7s0lq1oAKHB Bvu+wsjqTqmjvQWp+EZup3ujWn+beY8Us3DqKyOM= Subject: Re: The ports collection has some serious issues To: freebsd-ports@freebsd.org References: <20161208085926.GC2691@gmail.com> From: "Janky Jay, III" Message-ID: Date: Sun, 11 Dec 2016 19:42:07 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="87XE3WsFwuv12dbmRqbpj7Ps44K2Pg2RA" X-Virus-Scanned: Maia Mailguard 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, 12 Dec 2016 02:47:54 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --87XE3WsFwuv12dbmRqbpj7Ps44K2Pg2RA Content-Type: multipart/mixed; boundary="AbA2mMGWPW5lfnbf1ll1wNmIMJMabJT5e"; protected-headers="v1" From: "Janky Jay, III" To: freebsd-ports@freebsd.org Message-ID: Subject: Re: The ports collection has some serious issues References: <20161208085926.GC2691@gmail.com> In-Reply-To: --AbA2mMGWPW5lfnbf1ll1wNmIMJMabJT5e Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hello scratch, On 12/11/2016 03:35 PM, scratch65535@att.net wrote: > I have to admit that I avoid ports if at all possible because > I've hardly ever been able to do a build that ran to completion.=20 > There's always some piece of code that's missing and can't be > found, or is the wrong version, et lengthy cetera. I've never > done release engineering, but I honestly can't imagine how some > of the stuff that makes its way into the ports tree ever got past > QA. It would get someone sacked if it happened in industry. >=20 > If the dev schedule would SLOW DOWN and the commitment switched > to quality from the current emphasis on frequency, with separate > trees for alpha-, beta-, and real release-quality, fully-vetted > code, the ports system might become usable again. This very, VERY rarely happens to me and I use ports *ONLY* in production environments. If you could please provide examples and report the issues to the port maintainer of the ports with issues, that would greatly help this situation. (Please don't take this as an insult or anything other than trying to be helpful...) Simply complaining about it without providing any additional information is certainly not going to improve anything. Being a port maintainer myself, I depend on people reporting any issues they run into in order to provide the most robust and dependable port I can. If people never reported any issues and I had no idea there was an issue with my port, how would I fix it? So, please, PLEASE report any issues with ports that aren't building. It's not too time consuming on your part. Just a simple BUG report and how to re-produce and you're finished. Kind Regards, Janky Jay, III --AbA2mMGWPW5lfnbf1ll1wNmIMJMabJT5e-- --87XE3WsFwuv12dbmRqbpj7Ps44K2Pg2RA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlhODoMACgkQGK3MsUbJZn4kHQCfcPZ3Zr02aX/xx7s9dDpbS0wh wOgAn07RCcGQ2IZj8NVFzHZvLzC9NODk =+0hA -----END PGP SIGNATURE----- --87XE3WsFwuv12dbmRqbpj7Ps44K2Pg2RA-- From owner-freebsd-ports@freebsd.org Mon Dec 12 02:58:10 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC09EC73C02 for ; Mon, 12 Dec 2016 02:58:10 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: from mail.irealone.com (fawn.irealone.com [IPv6:2001:1af8:4010:a07b:10::2]) (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 9B9391E48 for ; Mon, 12 Dec 2016 02:58:10 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mail.irealone.com (Postfix, from userid 1002) id F184A60DF0; Mon, 12 Dec 2016 03:58:06 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=acheronmedia.com; s=mail; t=1481511486; bh=aY1iibLaopbXT0w6I/0kf1jQNqEW6sn809AR8ajWXBc=; h=To:Subject:Date:From:In-Reply-To:References:From; b=Y75lAsJVD8lu0H+FfiiMkwI+4bjYJIR8Zpm92LExClHLt+VW/r+maLsrga4aLeJRb pysfWSULUT0b0Anon7rIIootoDaKOtfIjg1OQLnt0/0z7fZchBMXs2xl6vSwJy18cY Yu62cmYvMuzQ1B90mT7FA4aLJmqr57i0gZhvUZVs= To: freebsd-ports@freebsd.org Subject: Re: The ports collection has some serious issues X-PHP-Originating-Script: 0:rcube.php MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 12 Dec 2016 03:58:06 +0100 From: "Vlad K." Organization: Acheron Media In-Reply-To: References: <20161208085926.GC2691@gmail.com> Message-ID: X-Sender: vlad-fbsd@acheronmedia.com User-Agent: Roundcube Webmail/1.1.7 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, 12 Dec 2016 02:58:11 -0000 On 2016-12-12 03:42, Janky Jay, III wrote: > This very, VERY rarely happens to me and I use ports *ONLY* in > production environments. If you could please provide examples and > report > the issues to the port maintainer of the ports with issues, that would > greatly help this situation. (Please don't take this as an insult or Good advice, but please rather file a bug report on our bugzilla: https://bugs.freebsd.org/bugzilla/enter_bug.cgi?component=Individual%20Port%28s%29&product=Ports%20%26%20Packages Problems reported to maintainers directly cannot be tracked or confirmed by other users. -- Vlad K. From owner-freebsd-ports@freebsd.org Mon Dec 12 03:18:58 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0BD99C7318C for ; Mon, 12 Dec 2016 03:18:58 +0000 (UTC) (envelope-from jankyj@unfs.us) Received: from stig.purplehat.org (stig.purplehat.org [50.243.134.106]) (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 CF05EE1A for ; Mon, 12 Dec 2016 03:18:57 +0000 (UTC) (envelope-from jankyj@unfs.us) Received: from localhost (bill.goatse.unfs.us [50.243.134.106]) by stig.purplehat.org (Postfix) with ESMTP id CF5265A889; Sun, 11 Dec 2016 20:18:56 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=unfs.us; s=mail; t=1481512736; bh=5u8/wRsyx7AoibScFheb51JCckNO3rhdOj7rngQFcbA=; h=Subject:To:References:From:Date:In-Reply-To; b=oJduev5tHA1H2KYA3pg7UE8UGyTxweFbDWq9lozKDuV1BuldWEa9KuFcpxH5fy5Zu 04TJtlywAg/JindkEPYK+ZniINAJGrWfKMffl9VaftYtyPHFV5hVux8S2E39wV3Gkd kUoILysX9SMwkMui2g+bgOzP9onAC+R7ZwzEDZfM= Received: from stig.purplehat.org ([50.243.134.106]) by localhost (stig.purplehat.org [50.243.134.106]) (maiad, port 10024) with ESMTP id 43138-01; Sun, 11 Dec 2016 20:18:55 -0700 (MST) Received: from [10.1.10.30] (unknown [10.1.10.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: jankyj@unfs.us) by stig.purplehat.org (Postfix) with ESMTPSA id E269C5A87B; Sun, 11 Dec 2016 20:18:54 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=unfs.us; s=mail; t=1481512735; bh=5u8/wRsyx7AoibScFheb51JCckNO3rhdOj7rngQFcbA=; h=Subject:To:References:From:Date:In-Reply-To; b=FMbkPaJuBdNO/aUXNoAt6eiZFUzMyN3EgBRph6HqjMztgJYd5ZbOWeK0zNf+N4EI8 cYZM6AcDpLLIztYlQCQmYskDr5LVbn0hMVg+Dp4gUYUGkMkNv+/h06Ez6+1oBfeGy6 j19dpgbYkQhFWSQva1uo1cJSjioXf4IutTh80aho= Subject: Re: The ports collection has some serious issues To: freebsd-ports@freebsd.org References: <20161208085926.GC2691@gmail.com> From: "Janky Jay, III" Message-ID: <570a8877-9e2f-a295-6f8a-5e5f441fe86b@unfs.us> Date: Sun, 11 Dec 2016 20:18:44 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="G7JewiSijQJLO2U5aooXTsRg6Qda163c7" X-Virus-Scanned: Maia Mailguard 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, 12 Dec 2016 03:18:58 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --G7JewiSijQJLO2U5aooXTsRg6Qda163c7 Content-Type: multipart/mixed; boundary="FLI5BtGHsm2OrFoJWBnjAbToh5COr9ngp"; protected-headers="v1" From: "Janky Jay, III" To: freebsd-ports@freebsd.org Message-ID: <570a8877-9e2f-a295-6f8a-5e5f441fe86b@unfs.us> Subject: Re: The ports collection has some serious issues References: <20161208085926.GC2691@gmail.com> In-Reply-To: --FLI5BtGHsm2OrFoJWBnjAbToh5COr9ngp Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Vlad, On 12/11/2016 07:58 PM, Vlad K. wrote: > On 2016-12-12 03:42, Janky Jay, III wrote: >> This very, VERY rarely happens to me and I use ports *ONLY* in >> production environments. If you could please provide examples and repo= rt >> the issues to the port maintainer of the ports with issues, that would= >> greatly help this situation. (Please don't take this as an insult or >=20 > Good advice, but please rather file a bug report on our bugzilla: >=20 > https://bugs.freebsd.org/bugzilla/enter_bug.cgi?component=3DIndividual%= 20Port%28s%29&product=3DPorts%20%26%20Packages >=20 >=20 > Problems reported to maintainers directly cannot be tracked or confirme= d > by other users. >=20 Thanks for the clarification. In my previous response, my recommendation was to report to both the port maintainer as well as file a BUG report. I should have been more clear. Regards, Janky Jay, III --FLI5BtGHsm2OrFoJWBnjAbToh5COr9ngp-- --G7JewiSijQJLO2U5aooXTsRg6Qda163c7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlhOFxUACgkQGK3MsUbJZn6pDgCfT8D103J/Nj68+luuCCaYWJYM J2EAnRKtPzXmMYoi1sCHjgbTdIhYvfzz =k95r -----END PGP SIGNATURE----- --G7JewiSijQJLO2U5aooXTsRg6Qda163c7-- From owner-freebsd-ports@freebsd.org Mon Dec 12 05:05:14 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27F3BC738C4 for ; Mon, 12 Dec 2016 05:05:14 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [185.24.122.233]) (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 D3BE11DC9 for ; Mon, 12 Dec 2016 05:05:13 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (188.29.165.226.threembb.co.uk [188.29.165.226]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id uBC54qqS058914 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 12 Dec 2016 05:04:53 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host 188.29.165.226.threembb.co.uk [188.29.165.226] claimed to be ultrabook.yoonka.com Subject: Re: The ports collection has some serious issues To: freebsd-ports@freebsd.org References: <20161208085926.GC2691@gmail.com> From: Grzegorz Junka Message-ID: <231ebf32-a99f-24ed-9e21-346f453500cb@gjunka.com> Date: Mon, 12 Dec 2016 05:04:44 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; 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, 12 Dec 2016 05:05:14 -0000 On 12/12/2016 02:42, Janky Jay, III wrote: > Hello scratch, > > On 12/11/2016 03:35 PM, scratch65535@att.net wrote: >> I have to admit that I avoid ports if at all possible because >> I've hardly ever been able to do a build that ran to completion. >> There's always some piece of code that's missing and can't be >> found, or is the wrong version, et lengthy cetera. I've never >> done release engineering, but I honestly can't imagine how some >> of the stuff that makes its way into the ports tree ever got past >> QA. It would get someone sacked if it happened in industry. >> >> If the dev schedule would SLOW DOWN and the commitment switched >> to quality from the current emphasis on frequency, with separate >> trees for alpha-, beta-, and real release-quality, fully-vetted >> code, the ports system might become usable again. > This very, VERY rarely happens to me and I use ports *ONLY* in > production environments. If you could please provide examples and report > the issues to the port maintainer of the ports with issues, that would > greatly help this situation. (Please don't take this as an insult or > anything other than trying to be helpful...) Simply complaining about it > without providing any additional information is certainly not going to > improve anything. > > Being a port maintainer myself, I depend on people reporting any issues > they run into in order to provide the most robust and dependable port I > can. If people never reported any issues and I had no idea there was an > issue with my port, how would I fix it? So, please, PLEASE report any > issues with ports that aren't building. It's not too time consuming on > your part. Just a simple BUG report and how to re-produce and you're > finished. > > Kind Regards, > Janky Jay, III > > I second scratch. Building the ports with default options may not be an issue but I am rarely (if ever) able to build all 1000+ selected ports (using poudriere) with the options that I selected. Whenever I can I am raising issues with port maintainer but they very rarely get addressed, at least in timely fashion. Even with just 1000+ ports, if an issue takes a few weeks to resolve (which would be great) it's highly probably that at least one other port gets broken by the time the first issue is resolved. With that approach I would never be able to cleanly build all the ports that I need. So, to make at least some of the build successful, I have to revisit various options and try to disable them to verify which ones will allow me to build the ports successfully. It's not as much a compliant, as I understand it's all done by volunteers in their free time, but it makes me wonder how FreeBSD even gets its current popularity within the industry with such stability. Grzegorz From owner-freebsd-ports@freebsd.org Mon Dec 12 06:36:47 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C832C730F5 for ; Mon, 12 Dec 2016 06:36:47 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [150.101.137.141]) by mx1.freebsd.org (Postfix) with ESMTP id E311D892 for ; Mon, 12 Dec 2016 06:36:46 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ppp121-45-104-245.bras2.adl6.internode.on.net (HELO leader.local) ([121.45.104.245]) by ipmail04.adl6.internode.on.net with ESMTP; 12 Dec 2016 17:01:35 +1030 Subject: Re: The ports collection has some serious issues To: "Janky Jay, III" , freebsd-ports@freebsd.org References: <20161208085926.GC2691@gmail.com> From: Shane Ambler Message-ID: Date: Mon, 12 Dec 2016 17:01:33 +1030 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 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, 12 Dec 2016 06:36:47 -0000 On 12/12/2016 13:12, Janky Jay, III wrote: > Hello scratch, > > On 12/11/2016 03:35 PM, scratch65535@att.net wrote: >> I have to admit that I avoid ports if at all possible because >> I've hardly ever been able to do a build that ran to completion. >> There's always some piece of code that's missing and can't be >> found, or is the wrong version, et lengthy cetera. I've never >> done release engineering, but I honestly can't imagine how some >> of the stuff that makes its way into the ports tree ever got past >> QA. It would get someone sacked if it happened in industry. >> >> If the dev schedule would SLOW DOWN and the commitment switched >> to quality from the current emphasis on frequency, with separate >> trees for alpha-, beta-, and real release-quality, fully-vetted >> code, the ports system might become usable again. Note that there are over 26000 ports, over 1600 port maintainers and hundreds of third party projects get updated every day. While the port maintainers spend a good portion of their spare time trying to keep it building there will be times that some ports fail to build. The HEAD of the ports svn repo is for the cutting edge development, a quarterly branch is created every three months and is only updated to receive security and build or runtime fixes during that time. The quarterly ports has been setup for a couple of years but doesn't seem to be documented well, or it just isn't obvious to find. You can use svn to checkout a stable branch by specifying a branch name, such as ports/branches/2016Q4 instead of ports/head. You can also adjust pkg to use the quarterly ports by changing the pkg repo URL from pkg.FreeBSD.org/${ABI}/latest to pkg.FreeBSD.org/${ABI}/quarterly > This very, VERY rarely happens to me and I use ports *ONLY* in > production environments. If you could please provide examples and report > the issues to the port maintainer of the ports with issues, that would > greatly help this situation. (Please don't take this as an insult or > anything other than trying to be helpful...) Simply complaining about it > without providing any additional information is certainly not going to > improve anything. I would say this rarely happens with the default setup, the more port options you change the more likely it is something will break. -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-ports@freebsd.org Mon Dec 12 07:52:47 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57D5EC73444 for ; Mon, 12 Dec 2016 07:52:47 +0000 (UTC) (envelope-from hvo.pm@xs4all.nl) Received: from ans.signature.nl (ans.signature.nl [149.210.131.160]) by mx1.freebsd.org (Postfix) with ESMTP id 1FEE9125A for ; Mon, 12 Dec 2016 07:52:47 +0000 (UTC) (envelope-from hvo.pm@xs4all.nl) Received: by ans.signature.nl (Postfix, from userid 1001) id 4681D731D01; Mon, 12 Dec 2016 08:52:39 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by ans.signature.nl (Postfix) with ESMTP id 40EEB731D00 for ; Mon, 12 Dec 2016 08:52:39 +0100 (CET) Date: Mon, 12 Dec 2016 08:52:39 +0100 (CET) From: Henk van Oers X-X-Sender: henk@ans.signature.nl To: freebsd-ports@freebsd.org Subject: Re: A Dancer request In-Reply-To: Message-ID: References: <20161210165531.GL2648@home.opsec.eu> <20161210170647.GA74926@home.opsec.eu> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed 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, 12 Dec 2016 07:52:47 -0000 On Sat, 10 Dec 2016, Henk van Oers wrote: > On Sat, 10 Dec 2016, Kurt Jaeger wrote: [...] >> Btw, there's an update to 0.620 ? Is this relevant ? > > Its in the tree now. > > Portscout will dump it on my todo list. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215243 (NB: See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214278 ) -- Henk From owner-freebsd-ports@freebsd.org Mon Dec 12 08:53:50 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E14A3C6C462 for ; Mon, 12 Dec 2016 08:53:50 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) 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 CAF96EE7 for ; Mon, 12 Dec 2016 08:53:50 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: by mailman.ysv.freebsd.org (Postfix) id C7690C6C461; Mon, 12 Dec 2016 08:53: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 C710CC6C45F for ; Mon, 12 Dec 2016 08:53:50 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from mail.mimar.rs (mail1.mimar.rs [193.53.106.128]) (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 88D63EE6 for ; Mon, 12 Dec 2016 08:53:49 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from mail1.mimar.rs (localhost [127.0.1.128]) by mail.mimar.rs (Postfix) with ESMTP id 8ECE69FA8967 for ; Mon, 12 Dec 2016 09:53:40 +0100 (CET) X-Virus-Scanned: amavisd-new at mimar.rs Received: from mail.mimar.rs ([127.0.1.128]) by mail1.mimar.rs (amavis.mimar.rs [127.0.1.128]) (amavisd-new, port 10026) with LMTP id DHMPEBnViZ4C for ; Mon, 12 Dec 2016 09:53:38 +0100 (CET) Received: from efreet.kappastar.com (nat-nat.kappastar.com [193.53.106.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: marko.cupac@mimar.rs) by mail.mimar.rs (Postfix) with ESMTPSA id D42E19FA891B for ; Mon, 12 Dec 2016 09:53:37 +0100 (CET) Date: Mon, 12 Dec 2016 09:53:39 +0100 From: Marko =?UTF-8?B?Q3VwYcSH?= To: ports@FreeBSD.org Subject: ABI changed: 'freebsd:11:x86:64' -> 'freebsd:11:*' Message-ID: <20161212095339.10c415d3@efreet.kappastar.com> Organization: Mimar X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2016 08:53:51 -0000 Hi, I am building my ports in poudriere, and after latest bulk build I see the following when `pkg upgrade' on a client: Installed packages to be REINSTALLED: py27-sphinx-1.4.8 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:11:*') Is this OK? What does it mean? Thank you in advance, --=20 Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupa=C4=87 https://www.mimar.rs/ From owner-freebsd-ports@freebsd.org Mon Dec 12 08:58:45 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EDCD7C6C504 for ; Mon, 12 Dec 2016 08:58:45 +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 DE1DBFF4 for ; Mon, 12 Dec 2016 08:58:45 +0000 (UTC) (envelope-from lists@opsec.eu) Received: by mailman.ysv.freebsd.org (Postfix) id DAA61C6C502; Mon, 12 Dec 2016 08:58: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 D8819C6C501 for ; Mon, 12 Dec 2016 08:58:45 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9A291FF3 for ; Mon, 12 Dec 2016 08:58:45 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cGMRY-000MrQ-NL; Mon, 12 Dec 2016 09:58:44 +0100 Date: Mon, 12 Dec 2016 09:58:44 +0100 From: Kurt Jaeger To: Marko Cupa?? Cc: ports@FreeBSD.org Subject: Re: ABI changed: 'freebsd:11:x86:64' -> 'freebsd:11:*' Message-ID: <20161212085844.GM2648@home.opsec.eu> References: <20161212095339.10c415d3@efreet.kappastar.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161212095339.10c415d3@efreet.kappastar.com> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2016 08:58:46 -0000 Hi! > I am building my ports in poudriere, and after latest bulk build I see > the following when `pkg upgrade' on a client: > > Installed packages to be REINSTALLED: > py27-sphinx-1.4.8 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:11:*') > > Is this OK? What does it mean? Some ports do not contain architecture-specific files (no binaries), so any version (amd64, i386, arm etc) can install the same files. If the maintainer adds a NO_ARCH=yes to the Makefile, the port and package are marked as 'freebsd:11:*'. -- pi@opsec.eu +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Mon Dec 12 09:04:08 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DDD7BC6C9F7 for ; Mon, 12 Dec 2016 09:04:08 +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 CAEF614F2 for ; Mon, 12 Dec 2016 09:04:08 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id CA561C6C9F4; Mon, 12 Dec 2016 09:04:08 +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 CA04BC6C9F3 for ; Mon, 12 Dec 2016 09:04:08 +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 BD5FA14F1 for ; Mon, 12 Dec 2016 09:04:08 +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 uBC94842017544 for ; Mon, 12 Dec 2016 09:04:08 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id uBC948wl017537; Mon, 12 Dec 2016 09:04:08 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201612120904.uBC948wl017537@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, 12 Dec 2016 09:04:08 +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, 12 Dec 2016 09:04:09 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/cdk | 5.0-20160131 | 5.0-20161210 ------------------------------------------------+-----------------+------------ emulators/fs-uae-launcher | 2.4.1 | 2.8.2 ------------------------------------------------+-----------------+------------ finance/moneymanagerex | 1.2.7 | v1.3.0 ------------------------------------------------+-----------------+------------ math/maxima | 5.38.1 | 5.39.0 ------------------------------------------------+-----------------+------------ sysutils/n98-magerun | 1.97.12 | 1.97.27 ------------------------------------------------+-----------------+------------ 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 Dec 12 11:05:33 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 429ADC71FBD for ; Mon, 12 Dec 2016 11:05:33 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from mx1.mailbox.org (mx1.mailbox.org [80.241.60.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.mailbox.org", Issuer "SwissSign Server Silver CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0BD8B194F for ; Mon, 12 Dec 2016 11:05:32 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.mailbox.org (Postfix) with ESMTPS id 8437843DDB; Mon, 12 Dec 2016 12:05:29 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp1.mailbox.org ([80.241.60.240]) by spamfilter02.heinlein-hosting.de (spamfilter02.heinlein-hosting.de [80.241.56.116]) (amavisd-new, port 10030) with ESMTP id 6BD4DpXFyEEF; Mon, 12 Dec 2016 12:05:19 +0100 (CET) Date: Mon, 12 Dec 2016 12:05:17 +0100 Message-ID: <86oa0hcsr6.wl-herbert@mailbox.org> From: "Herbert J. Skuhra" To: freebsd-ports@freebsd.org Cc: Lewis Butler Subject: Re: [Solved?] Re: pkg 1.9.4 In-Reply-To: <028983C3-14C1-4112-9D38-17E8C6D5BC49@gmail.com> References: <028983C3-14C1-4112-9D38-17E8C6D5BC49@gmail.com> MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2016 11:05:33 -0000 Lewis Butler skrev: > > On 09 Dec 2016, at 17:43, Lewis Butler wrote: >> Got this when trying to update to pkg-1.9.4 >> >> /bin/sh ../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I.. -I../compat -DWITH_SSL -Wno-pointer-sign -shared -O2 -pipe -Wno-error -fstack-protector -fno-strict-aliasing -Wall -Wno-unused-function -D_BSD_SOURCE -DINET6=1 -MT libfetch/libfetch_la-common.lo -MD -MP -MF libfetch/.deps/libfetch_la-common.Tpo -c -o libfetch/libfetch_la-common.lo `test -f 'libfetch/common.c' || echo './'`libfetch/common.c >> libtool: compile: cc -DHAVE_CONFIG_H -I. -I.. -I../compat -DWITH_SSL -Wno-pointer-sign -O2 -pipe -Wno-error -fstack-protector -fno-strict-aliasing -Wall -Wno-unused-function -D_BSD_SOURCE -DINET6=1 -MT libfetch/libfetch_la-common.lo -MD -MP -MF libfetch/.deps/libfetch_la-common.Tpo -c libfetch/common.c -fPIC -DPIC -o libfetch/.libs/libfetch_la-common.o >> libfetch/common.c:52:10: fatal error: 'openssl/x509v3.h' file not found >> #include > > I created the directory /usr/include/openssl/ > > cd /usr/include/openssl > ln -s /usr/local/include/openssl/* . You'd better undo this and run 'make buildworld' and 'make installworld' to cleanup the mess. > then I was able to make pkg. Not sure why, but > /usr/local/library/openssl seemed to be where openssl was installed > but the packages are looking for /usr/library/openssl. > > I'm sure this is not the preferred way to do this. > > There is also an openssl-1.0.1p folder in /usr/include/ with rather > old files in it. I plan on moving it aside and seeing what happens. You can try to rename the directory back to openssl and see if 'freebsd-update fetch install' will update the files. If not remove it and do the above. -- Herbert From owner-freebsd-ports@freebsd.org Mon Dec 12 12:48:02 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1EE5DC73DE4 for ; Mon, 12 Dec 2016 12:48:02 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm25-vm1.access.bullet.mail.gq1.yahoo.com (nm25-vm1.access.bullet.mail.gq1.yahoo.com [216.39.63.23]) (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 EF5971974 for ; Mon, 12 Dec 2016 12:48:01 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1481546686; bh=iknfiki9h41fQp+F+q33/Q33ps+hMSficEi4cCef50I=; h=From:To:Subject:Date:References:In-Reply-To:From:Subject; b=zwDKU9xt0gxuei/LSKagcw62DbaXtKCkkGcYX4MHPxiKlhf/Vl0w54x23yJbekp7TW9okacHwwa1/xwUMjpnS4771vCLcD4h8uIrl/zhThdX02eupB3noHMmdUyhQ6BZfSwkX4JJRXbtPdfAo5A4nTsecrpDua5CqHZOkCkrQRU= Received: from [216.39.60.176] by nm25.access.bullet.mail.gq1.yahoo.com with NNFMP; 12 Dec 2016 12:44:46 -0000 Received: from [67.195.22.117] by tm12.access.bullet.mail.gq1.yahoo.com with NNFMP; 12 Dec 2016 12:44:46 -0000 Received: from [127.0.0.1] by smtp112.sbc.mail.gq1.yahoo.com with NNFMP; 12 Dec 2016 12:44:46 -0000 X-Yahoo-Newman-Id: 768893.21879.bm@smtp112.sbc.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: kmHwQyoVM1lxxhtFgUJLnCK0yk5lUf1r3opAczGODhF5sal Gq4tHWjD3.q89x9pSSP8h2Tqm6J2zi1zm9nCUiOQqFfx7NSXJUN0RL5R2y3k lOvykucbraMR4aWOfKi9soXH2ROub4nIYxKQalSLTzmMJv_NxUGmmerCIrcK qWs6jEqLXmy9TDQ.1cvwqeDY4os6mxNF5b1OSeFRmK_qQnqb7pR4QFBwgJiF IAuj0iTC9fkYDthEXTOGAxwdSr8_Jkzq9LdxlnTsN017b7Jlew4hHFBqzZ6t IyVRvvSoO88Y5eE1X09Y.1n5cdw_8cjF24M47MXO62N8RIDnIZfZF8WoiYO7 5lz35ztZFRMKcMLpiPUWi7xyAFG_V4uX2LrBU2K7tyyS3RsgVxNUeREt9Lxg fwDxGfzFXFvb4z8Mk5NWBd7ib40WxiQNTav7v81RqOQEnroWrBaDJ5WMrkcL ogMNux7l8pWLsGDe8EYTJGphS_FHmzIzz_UULpPxP5R3ynQnoW0ZlTjW2Qp1 qjcc1BpjaOVlQJlHyY33XUj2RE5wt1XPvBtvpsYJCbsLw0Dp5iz1CRpS.sou l X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: freebsd-ports Subject: Re: The ports collection has some serious issues Date: Mon, 12 Dec 2016 07:44:47 -0500 Message-ID: <5s3t4c576qeivfr32d2j7u1fm8jkia97jf@4ax.com> References: <20161208085926.GC2691@gmail.com> In-Reply-To: X-Mailer: Forte Agent 4.2/32.1118 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2016 12:48:02 -0000 [Default] On Mon, 12 Dec 2016 17:01:33 +1030, Shane Ambler wrote: >On 12/12/2016 13:12, Janky Jay, III wrote: >> Hello scratch, >> >> On 12/11/2016 03:35 PM, scratch65535@att.net wrote: >>> I have to admit that I avoid ports if at all possible because >>> I've hardly ever been able to do a build that ran to completion. >>> There's always some piece of code that's missing and can't be >>> found, or is the wrong version, et lengthy cetera. I've never >>> done release engineering, but I honestly can't imagine how some >>> of the stuff that makes its way into the ports tree ever got past >>> QA. It would get someone sacked if it happened in industry. >>> >>> If the dev schedule would SLOW DOWN and the commitment switched >>> to quality from the current emphasis on frequency, with separate >>> trees for alpha-, beta-, and real release-quality, fully-vetted >>> code, the ports system might become usable again. > >Note that there are over 26000 ports, over 1600 port maintainers and >hundreds of third party projects get updated every day. While the port >maintainers spend a good portion of their spare time trying to keep it >building there will be times that some ports fail to build. Which, I think you must agree, is a prima facie case for lengthening the release cycle. Too few people trying to do too much work in too little time is a receipe for disaster. I've seen it in industry, where engineering gets tasked with impossible schedules to meet some business plan dreamed up by the suits. Burnout City. After I left the corporate world I used to do QA gigs as a consultant for easy money, and the guys who'd hire me would have a hard time suppressing their irritation because I'd find lots of bugs for which they had no time in their schedule to fix. But if they slipped the schedule, they'd get a rocket from further up the food chain, so it was a no-win for them. > >The HEAD of the ports svn repo is for the cutting edge development, a >quarterly branch is created every three months and is only updated to >receive security and build or runtime fixes during that time. > >The quarterly ports has been setup for a couple of years but doesn't >seem to be documented well, or it just isn't obvious to find. You can >use svn to checkout a stable branch by specifying a branch name, such as >ports/branches/2016Q4 instead of ports/head. You can also adjust pkg to >use the quarterly ports by changing the pkg repo URL from >pkg.FreeBSD.org/${ABI}/latest to pkg.FreeBSD.org/${ABI}/quarterly That's interesting. The ones that break on me are the ones I get from portsnap. Does portsnap tap quarterly or something else? >I would say this rarely happens with the default setup, the more port >options you change the more likely it is something will break. That's WHY I avoid ports. Like Grzegorz, I don't necessarily, or even usually, want the default options. But if my only hope is to build the default version, why not just install the package, if there is one --- it's what I'd get if I built the port, and the package builder has already done all the work I'd have to do. Perhaps The Major Problem currently is that the makefile goes and fetches code chunks from sources that are out of our control. And it's done fresh for *every* individual build, so J. Random Devguy somewhere can decide on the spur of the moment to change his chunk of code, or change where he's keeping it, and suddenly the build breaks because of version skew or FNF. Contrast that with how it would be if the maintainer got one copy of every potential chunk at the beginning of the cycle and stored it in ports so that everyone who builds the port builds against a known-good set of bits. It would be both more stable and faster. But that's not how it's done. Why not? From owner-freebsd-ports@freebsd.org Mon Dec 12 12:56:09 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B025C73FF6 for ; Mon, 12 Dec 2016 12:56:09 +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 D007A1D47 for ; Mon, 12 Dec 2016 12:56:08 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cGQ97-000NCo-MR; Mon, 12 Dec 2016 13:55:57 +0100 Date: Mon, 12 Dec 2016 13:55:57 +0100 From: Kurt Jaeger To: scratch65535@att.net Cc: freebsd-ports Subject: Re: The ports collection has some serious issues Message-ID: <20161212125557.GN2648@home.opsec.eu> References: <20161208085926.GC2691@gmail.com> <5s3t4c576qeivfr32d2j7u1fm8jkia97jf@4ax.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5s3t4c576qeivfr32d2j7u1fm8jkia97jf@4ax.com> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2016 12:56:09 -0000 Hi! > >> On 12/11/2016 03:35 PM, scratch65535@att.net wrote: > >>> I have to admit that I avoid ports if at all possible because > >>> I've hardly ever been able to do a build that ran to completion. [...] > >Note that there are over 26000 ports, over 1600 port maintainers and > >hundreds of third party projects get updated every day. While the port > >maintainers spend a good portion of their spare time trying to keep it > >building there will be times that some ports fail to build. > > Which, I think you must agree, is a prima facie case for > lengthening the release cycle. While I can understand where this comes from, it can be read as "slow down the world, it's too fast" 8-} > Perhaps The Major Problem currently is that the makefile goes and > fetches code chunks from sources that are out of our control. [...] > Contrast that with how it would be if the maintainer got one copy > of every potential chunk at the beginning of the cycle and stored > it in ports so that everyone who builds the port builds against a > known-good set of bits. It would be both more stable and faster. > But that's not how it's done. Why not? As far as I know: The idea was to track upstream, not try to become upstream. Otherwise the changeset (distfiles) repositories would be come much larger to maintain on the FreeBSD side. -- pi@opsec.eu +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Mon Dec 12 13:57:35 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 42681C72113 for ; Mon, 12 Dec 2016 13:57:35 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 1BD7D1E50 for ; Mon, 12 Dec 2016 13:57:35 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 18693C72110; Mon, 12 Dec 2016 13:57:35 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16648C7210F for ; Mon, 12 Dec 2016 13:57:35 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wj0-x242.google.com (mail-wj0-x242.google.com [IPv6:2a00:1450:400c:c01::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 91D901E4F for ; Mon, 12 Dec 2016 13:57:34 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wj0-x242.google.com with SMTP id j10so11735576wjb.3 for ; Mon, 12 Dec 2016 05:57:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=cIAdrtReLcU2wKlaUSEZG2y1TaNXCut1dvWmAbM3p2M=; b=XWXkhrL4v2j9rn2S/ApBdPNu3AVElKGdJ3hqbqHPZVIwWhutGIj/nHX7AHRbFnMWov XfjtrMRDXifYOLAM3AOJlBRZH6+fT5xrl6Uk4Y4J+ov7dphS9FZHSUvrYkr31O77oUuc wS9b87QYRrOg0gqPjPCdJtN0eTo5Mti91jkuvGn+8EZAlnf5jZIvCgjbDKWo98qh1Urr hSCElMCfbWKmBFRZPH32X5rTHLWh0gDcbPcoMjhYm6sK3nGmIexL6HOz4LkHCV8KSrA/ AbdqJnTj4iYRW+rNx79ffWnwyjbWdIL5frd1gfJIjma1AT3Ok7AhNTv6QuVhbkoSj4QK gMCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=cIAdrtReLcU2wKlaUSEZG2y1TaNXCut1dvWmAbM3p2M=; b=WrJnB5UFsCvvXnkCnC5NZwBDTgLiHyJPmguISbBgGBOUYiIJeEd9sl9pLQTyU/Xbfz 5pk7lhbtfUNhu3QIw6jDAb53N4dkA2STpmSjsXVfJSRiKM1oDMsWSHKnpyONmMVZkT3Z PEuMuHazs/Gp433rE61ErVGaowITBaJVJ8b1ClN8F8IsttXXluACTLwpC5LSl4RPu6aw 4iray0k+MFAVFiIhcy7HXIMo5mjpQHxhrp+4LX8uXivWrejvWD9jSq7G6BiTUL3wAhrR vN2A3pf3PreYX293JnNnSwpG5Qve5zOptqv9JLScWxAAOxlAai57R1TSKqz9z3C/7Mza EWcQ== X-Gm-Message-State: AKaTC01hK8loSdU6XdH628VYMobHXkyctvY9XnheA9R+ewRRqPjdWu2Ku9OR0dVYKVe1Tg== X-Received: by 10.194.47.42 with SMTP id a10mr79937781wjn.216.1481551051731; Mon, 12 Dec 2016 05:57:31 -0800 (PST) Received: from gumby.homeunix.com ([81.17.24.158]) by smtp.gmail.com with ESMTPSA id di9sm57309345wjc.37.2016.12.12.05.57.30 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 12 Dec 2016 05:57:30 -0800 (PST) Date: Mon, 12 Dec 2016 13:57:27 +0000 From: RW To: ports@freebsd.org Subject: Re: The ports collection has some serious issues Message-ID: <20161212135727.1c809063@gumby.homeunix.com> In-Reply-To: References: <20161208085926.GC2691@gmail.com> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2016 13:57:35 -0000 On Sun, 11 Dec 2016 19:42:07 -0700 Janky Jay, III wrote: > Hello scratch, > > On 12/11/2016 03:35 PM, scratch65535@att.net wrote: > > I have to admit that I avoid ports if at all possible because > > I've hardly ever been able to do a build that ran to completion. > > There's always some piece of code that's missing and can't be > > found, or is the wrong version, et lengthy cetera. I've never > > done release engineering, but I honestly can't imagine how some > > of the stuff that makes its way into the ports tree ever got past > > QA. It would get someone sacked if it happened in industry. > > > > If the dev schedule would SLOW DOWN and the commitment switched > > to quality from the current emphasis on frequency, with separate > > trees for alpha-, beta-, and real release-quality, fully-vetted > > code, the ports system might become usable again. > > This very, VERY rarely happens to me and I use ports *ONLY* in > production environments. I have a desktop with a lot of server ports installed on it and find that the build problems I have are overwhelmingly desktop related. Even on the desktop I don't find it to be more than an irritation. From owner-freebsd-ports@freebsd.org Mon Dec 12 14:05:59 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA817C72458 for ; Mon, 12 Dec 2016 14:05:59 +0000 (UTC) (envelope-from scratch65535@att.net) Received: from nm18-vm9.access.bullet.mail.gq1.yahoo.com (nm18-vm9.access.bullet.mail.gq1.yahoo.com [216.39.62.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A68CC287 for ; Mon, 12 Dec 2016 14:05:59 +0000 (UTC) (envelope-from scratch65535@att.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1481551455; bh=65yuZcRHFu5UbGTXsVegWYtC/Pbq4Gos3XiulnvYw5M=; h=From:To:Subject:Date:References:In-Reply-To:From:Subject; b=x1G/doFMnZP/Wfl7m9DQAwyOEd+h8a0zXP/S/v9QoSh8phFiyCnJUAerMaMkjJUFhq6XtigbwYunphxyX+21/xIR0pPj2ptrdF3h/L/fXmvdBLA0EoE+8apnyg66aXWjAIoIoWFmvl+DuRy4kD5DdLQSYLNTl0dD9f/84vwZ4rI= Received: from [216.39.60.173] by nm18.access.bullet.mail.gq1.yahoo.com with NNFMP; 12 Dec 2016 14:04:15 -0000 Received: from [67.195.22.118] by tm9.access.bullet.mail.gq1.yahoo.com with NNFMP; 12 Dec 2016 14:04:15 -0000 Received: from [127.0.0.1] by smtp113.sbc.mail.gq1.yahoo.com with NNFMP; 12 Dec 2016 14:04:15 -0000 X-Yahoo-Newman-Id: 737096.31861.bm@smtp113.sbc.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: LddMrr8VM1kzX1elMV_FRWEb1mlpH_sfS7Jg71rYg3.BAMS Vwhx2B2yZxDuUkoJPfBiOz5OZht1SYcnZ3kiYzS.y7ZcSQu2wGyqGCO3MYEa zJsjgXJcN21wC8UYZRQw84c_9ShCbcPT82kXuz25E8qJt4lrLZ.10S.74Y.6 YPiiVQeRXqILMQDmBRWNh_nXvZhoKzUchvSOaJrjyI1vL.XPnLZgn7zzAfEb mKbdy0prXIliECT.C724.uASQ2s2xdHcAjb9OPshdhZS9E5nBSQaZSf1vJT9 d.ggkj3pGRikUpbKYxiVICEei0DuagWtmW1H7x144jVyprSwZpBswPlF7t1u ylKHso2RRWoocZcvtLR3mbY3zE1gD60zaqocf8gLebnPJ3ZzW6otvj8EDF.0 Up.l13rSz4zNkyqwr4PyZ0HZosy._bcvk_tIMEIU_JwICLiT4Ck3pIenqX7s 77E2Ks90c9vqpJH3M5QkRUFb0xZtua9PZC2o5oz2z4Dky8Fc.ff43vsGKSNi 0tqjizaAeCuWde5AryWFlhRTLHxA_6UZmQa5omYzsuUoe0YAK_wf1lRhMsL1 E X-Yahoo-SMTP: pPvqnOaswBBbYZLVYFzvU7GaowLcbNioPp.aF8KvOjZk From: To: freebsd-ports Subject: Re: The ports collection has some serious issues Date: Mon, 12 Dec 2016 09:04:16 -0500 Message-ID: References: <20161208085926.GC2691@gmail.com> <5s3t4c576qeivfr32d2j7u1fm8jkia97jf@4ax.com> <20161212125557.GN2648@home.opsec.eu> In-Reply-To: <20161212125557.GN2648@home.opsec.eu> 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: Mon, 12 Dec 2016 14:05:59 -0000 [Default] On Mon, 12 Dec 2016 13:55:57 +0100, Kurt Jaeger wrote: >Hi! > >> >> On 12/11/2016 03:35 PM, scratch65535@att.net wrote: >> >>> I have to admit that I avoid ports if at all possible because >> >>> I've hardly ever been able to do a build that ran to completion. >[...] >> >Note that there are over 26000 ports, over 1600 port maintainers and >> >hundreds of third party projects get updated every day. While the port >> >maintainers spend a good portion of their spare time trying to keep it >> >building there will be times that some ports fail to build. >> >> Which, I think you must agree, is a prima facie case for >> lengthening the release cycle. > >While I can understand where this comes from, it can be read as >"slow down the world, it's too fast" 8-} Well, that part of the world is under our control, and it's currently not working at all well, so...? > >> Perhaps The Major Problem currently is that the makefile goes and >> fetches code chunks from sources that are out of our control. [...] > >> Contrast that with how it would be if the maintainer got one copy >> of every potential chunk at the beginning of the cycle and stored >> it in ports so that everyone who builds the port builds against a >> known-good set of bits. It would be both more stable and faster. >> But that's not how it's done. Why not? > >As far as I know: The idea was to track upstream, not try to become >upstream. Otherwise the changeset (distfiles) repositories would >be come much larger to maintain on the FreeBSD side. I'm sure that's true. But it's not working, and in fact can't work except by accident because it's uncontrolled. Your point about the distfiles repositories is well-made. How about storing them centrally, then, but only download them to the local boxes for the build. I.e., portsnap would fetch what it fetches now except for distfiles. Then if someone does some build, all the files for the build would be slurped from one of the portsnap.freebsd.org distfile mirrors. And if only the production-quality code were stored centrally--nothing beta or [shudder] alpha, that would drop the storage requirements considerably. I used to be appalled at seeing something being pulled in that was at v0.03 or something similarly horrible. People who like living dangerously with pre-alpha code can get their from the originators, just as they do now. From owner-freebsd-ports@freebsd.org Mon Dec 12 16:11:14 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6AEE2C730BB for ; Mon, 12 Dec 2016 16:11:14 +0000 (UTC) (envelope-from www-data@correios-objs15.endofinternet.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 56212124C for ; Mon, 12 Dec 2016 16:11:14 +0000 (UTC) (envelope-from www-data@correios-objs15.endofinternet.net) Received: by mailman.ysv.freebsd.org (Postfix) id 557D3C730BA; Mon, 12 Dec 2016 16:11:14 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55208C730B9 for ; Mon, 12 Dec 2016 16:11:14 +0000 (UTC) (envelope-from www-data@correios-objs15.endofinternet.net) Received: from correios-objs15.endofinternet.net (correios-objs15.endofinternet.net [13.81.49.225]) by mx1.freebsd.org (Postfix) with ESMTP id 0CD631248 for ; Mon, 12 Dec 2016 16:11:14 +0000 (UTC) (envelope-from www-data@correios-objs15.endofinternet.net) Received: by correios-objs15.endofinternet.net (Postfix, from userid 33) id BFB282CA6E; Mon, 12 Dec 2016 16:10:54 +0000 (UTC) To: ports@freebsd.org Subject: CORREIOS - Tentativa de entrega sem sucesso, Objeto - 4H713472QU X-PHP-Originating-Script: 0:hitshits.php MIME-Version: 1.0 From: CORREIOS Rastreamento de objetos 834063 pmvlicitacao Errors-To: CORREIOS Rastreamento de objetos 834063 pmvlicitacao Reply-To: CORREIOS Rastreamento de objetos 834063 pmvlicitacao X-Mailer: Microsoft Office Outlook, Build 17.551210 Message-Id: <20161212161054.BFB282CA6E@correios-objs15.endofinternet.net> Date: Mon, 12 Dec 2016 16:10:54 +0000 (UTC) Content-Type: text/plain; charset="iso-8859-1" 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, 12 Dec 2016 16:11:14 -0000 From owner-freebsd-ports@freebsd.org Mon Dec 12 16:15:32 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0571BC731A2 for ; Mon, 12 Dec 2016 16:15:32 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C5C6C15E9 for ; Mon, 12 Dec 2016 16:15:31 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id uBCGFLXG022401 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 12 Dec 2016 08:15:25 -0800 (PST) (envelope-from julian@freebsd.org) Subject: Re: The ports collection has some serious issues To: "Vlad K." , freebsd-ports@freebsd.org References: <29bc829f5bdbf18a38218b23ddf3afea@acheronmedia.com> From: Julian Elischer Message-ID: <1e49f0bd-f9e8-8698-0ba7-e9964a9f8c67@freebsd.org> Date: Tue, 13 Dec 2016 00:15:16 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.5.0 MIME-Version: 1.0 In-Reply-To: <29bc829f5bdbf18a38218b23ddf3afea@acheronmedia.com> Content-Type: text/plain; charset=windows-1252; 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, 12 Dec 2016 16:15:32 -0000 On 8/12/2016 6:05 PM, Vlad K. wrote: > On 2016-12-08 06:16, Daniil Berendeev wrote: > > > I mean, they are the FIRST landing point of a change. And the only > QA we ask for that change is a confirmation that poudriere and > portlint have been run, the rest is at liberty of committers how far > they'll go with own testing before they commit. For many, only > builds against -CURRENT or latest -RELEASE are done because it's > very time consuming to test against all supported FreeBSD versions, > and not just versions but various permutations like different > pythons etc... When it comes to some defaults like OpenSSL (or any > kind of dependency on it), all of those tests are required. > > The problem is, FreeBSD doesn't have a STABLE repo that would > receive gradual updates from HEAD as they prove themselves stable. > QUARTERLY != STABLE, it's just a snapshot of whatever state HEAD is > in, with a loose promise the ports in it will receive "security and > bugfixes only" but that's a separate set of issues. The problem I get hit by is that the quarterly packages are deleted immediately on the creation of the next quarterly set. so by definition, when you've spent 3 months getting the quarterly pkg collection reliable and correct, it gets deleted. I think there should be two quarterly pkg collections available at any time: The one we are stabilising, and the previous stable set (called beta and stable or something like that). the stable one is basically read-only except for security fixes. As it is when you get the new quarterly packages, they are straight off head, because the branch was just made. > > There are some solutions and we don't have to NIH or reinvent the > wheel. Just looking at what other open source projects do with, say, > GitHub and continuous integration testing, every pull request gets > an automated test. Why don't we do that? Is it difficult to > implement it? > > I am also convinced that such testing can be automated and a true > "STABLE" repo can be made instead of manual QUARTERLY that breaks > promises. I think this is heading in the right direction.. at the end of the 3 month stabilisation it goes to stable. > >> 8) ports with vulnerabilities. >> They exist in the tree and on build attempt they shout that they won't >> build without DISABLE_VULNERABILITIES=yes. The catch is that there is >> always a bunch of ports with vulnerabilities. So if you are doing a > > That's just a nature of it, and the consequence of VuXML being a > separate port that gets often updated first, as it's better to > announce the vuln before it was fixed. And fixing is bound to > maintainer timeouts, poor issue tracking via Bugzilla, etc... > > > >> I hope that my mail will produce a productive discussion that will >> lead >> to some good decisions for fixing these problems. > > Probably not. I've already posted about issues with head/quarterly, > hoping for a discussion, never happened. Others have complained > about the same problem, but no constructive discussion ensued. Is my > frustration coming through, yet? :) yeah it's not working well at the moment. The procedures could do with some tuning for sure. > > > > > From owner-freebsd-ports@freebsd.org Mon Dec 12 16:21:05 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3E699C733E4 for ; Mon, 12 Dec 2016 16:21:05 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C1F931A0C; Mon, 12 Dec 2016 16:21:04 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id uBCGKvIk022416 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 12 Dec 2016 08:21:01 -0800 (PST) (envelope-from julian@freebsd.org) Subject: Re: The ports collection has some serious issues To: Baptiste Daroussin , Daniil Berendeev References: <20161208122802.5d6dy7hjkkusms7h@ivaldir.etoilebsd.net> Cc: freebsd-ports@FreeBSD.org From: Julian Elischer Message-ID: Date: Tue, 13 Dec 2016 00:20:52 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.5.0 MIME-Version: 1.0 In-Reply-To: <20161208122802.5d6dy7hjkkusms7h@ivaldir.etoilebsd.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2016 16:21:05 -0000 On 8/12/2016 8:28 PM, Baptiste Daroussin wrote: > On Thu, Dec 08, 2016 at 05:16:24AM +0000, Daniil Berendeev wrote: >> Hello guys! >> >> First of all, it's not a hate mail, I appreciate all the work done on >> the system and I enjoy using FreeBSD every day. >> >> But after some recent experience I'd like to point out some problems >> that make using the ports collection uncomfortable and painful. >> >> Some overview before we start: >> * Why I use ports over pkg? >> Because, generally, packages are built with poor default options, for >> example moc isn't able to play .alac/.mod and that's frustrating. > Lot's of work has been done over the last years improve the default options for > general pupose cases. Have you open an issue about that one? but we still need a way to specify "minimum options please" to stop dependency fanout from going too wild. I touched a port last week that required about 200 others, a lot of which would not have been needed for what I would call a common functionality configuration. > > > Have you considered using things like poudriere that would allow you to build > your own repository with your own set of packages and options. > > You will benefit: > - ability to use pkg for your upgrades > - ability to use customize your packages > - safe rebuild process (in case of broken ABI) > > Best regards, > Bapt I'm actually slowly moving to this if I can work out how to specify my own chroot image, and a few other things I need to tweak. (my own sets of patches to add). From owner-freebsd-ports@freebsd.org Mon Dec 12 16:44:05 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDCC6C73253 for ; Mon, 12 Dec 2016 16:44:05 +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 95712D1B; Mon, 12 Dec 2016 16:44:05 +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 CF38228417; Mon, 12 Dec 2016 17:43:56 +0100 (CET) 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 2ADB2284A6; Mon, 12 Dec 2016 17:43:56 +0100 (CET) To: doceng@FreeBSD.org, "freebsd-ports@FreeBSD.org" Subject: FreeBSD Port: print/gsfonts please make Japanese and Chinese fonts optional dependencies From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <584ED3CB.1060500@quip.cz> Date: Mon, 12 Dec 2016 17:43:55 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 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: Mon, 12 Dec 2016 16:44:05 -0000 Hi, we are using Xpdf which depends on Gsfonts and after last update there are a bunch of new dependencies brought by Chinese and Japanese fonts" New packages to be INSTALLED: zh-font-std: 0.0.20090602 zh-arphicttf: 2.11_5 mkfontdir: 1.0.7 mkfontscale: 1.1.2 xproto: 7.0.31 libfontenc: 1.1.3 ja-font-std: 0.0.20130501 ja-font-mplus-ipa: 1.0.20060520.p1_5 ja-font-ipa: 00303_6 We are not using any of these so I think they are useless for us. Can this be made as optional dependency? It can be default ON, we are using own poudriere repo but we are unable to disable them now. Kind regards Miroslav Lachman From owner-freebsd-ports@freebsd.org Mon Dec 12 17:27:10 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC859C7369B for ; Mon, 12 Dec 2016 17:27:10 +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 80EAD14AC for ; Mon, 12 Dec 2016 17:27:10 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cGUNa-000NiE-Sl; Mon, 12 Dec 2016 18:27:10 +0100 Date: Mon, 12 Dec 2016 18:27:10 +0100 From: Kurt Jaeger To: Henk van Oers Cc: freebsd-ports@freebsd.org Subject: Re: A Dancer request Message-ID: <20161212172710.GO2648@home.opsec.eu> References: <20161210165531.GL2648@home.opsec.eu> <20161210170647.GA74926@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: Mon, 12 Dec 2016 17:27:10 -0000 Hi! > [...] > >> Btw, there's an update to 0.620 ? Is this relevant ? > See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215243 > > (NB: See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214278 ) Both done. -- pi@opsec.eu +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Mon Dec 12 17:59:12 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3171C74262 for ; Mon, 12 Dec 2016 17:59:12 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.allbsd.org", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 586E0FF4; Mon, 12 Dec 2016 17:59:12 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail-d.allbsd.org (p2027-ipbf1605funabasi.chiba.ocn.ne.jp [123.225.191.27]) (authenticated bits=56) by mail.allbsd.org (8.15.2/8.15.2) with ESMTPSA id uBCHwlOI015396 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) (Client CN "/OU=GT07882699/OU=See+20www.rapidssl.com/resources/cps+20+28c+2915/OU=Domain+20Control+20Validated+20-+20RapidSSL+28R+29/CN=*.allbsd.org", Issuer "/C=US/O=GeoTrust+20Inc./CN=RapidSSL+20SHA256+20CA+20-+20G3"); Tue, 13 Dec 2016 02:59:08 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from alph.allbsd.org (alph.allbsd.org [192.168.0.10]) by mail-d.allbsd.org (8.15.2/8.15.2) with ESMTPS id uBCHvWn3007568 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 13 Dec 2016 02:57:32 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.allbsd.org (8.15.2/8.15.2) with ESMTPA id uBCHvTc7007565; Tue, 13 Dec 2016 02:57:31 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Tue, 13 Dec 2016 02:57:21 +0900 (JST) Message-Id: <20161213.025721.480726455188804998.hrs@allbsd.org> To: 000.fbsd@quip.cz Cc: doceng@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: FreeBSD Port: print/gsfonts please make Japanese and Chinese fonts optional dependencies From: Hiroki Sato In-Reply-To: <584ED3CB.1060500@quip.cz> References: <584ED3CB.1060500@quip.cz> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.7 on Emacs 25.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Tue_Dec_13_02_57_21_2016_110)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.99 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.4.3 (mail.allbsd.org [133.31.130.32]); Tue, 13 Dec 2016 02:59:09 +0900 (JST) X-Spam-Status: No, score=-99.9 required=13.0 tests=CONTENT_TYPE_PRESENT, QENCPTR1,USER_IN_WHITELIST autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on gatekeeper.allbsd.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, 12 Dec 2016 17:59:12 -0000 ----Security_Multipart(Tue_Dec_13_02_57_21_2016_110)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Miroslav Lachman <000.fbsd@quip.cz> wrote in <584ED3CB.1060500@quip.cz>: 00> Hi, 00> 00> we are using Xpdf which depends on Gsfonts and after last update there 00> are a bunch of new dependencies brought by Chinese and Japanese fonts" 00> 00> New packages to be INSTALLED: 00> zh-font-std: 0.0.20090602 00> zh-arphicttf: 2.11_5 00> mkfontdir: 1.0.7 00> mkfontscale: 1.1.2 00> xproto: 7.0.31 00> libfontenc: 1.1.3 00> ja-font-std: 0.0.20130501 00> ja-font-mplus-ipa: 1.0.20060520.p1_5 00> ja-font-ipa: 00303_6 00> 00> We are not using any of these so I think they are useless for us. Can 00> this be made as optional dependency? It can be default ON, we are 00> using own poudriere repo but we are unable to disable them now. Thank you for your report. This problem should be fixed in the latest print/gsfonts. -- Hiroki ----Security_Multipart(Tue_Dec_13_02_57_21_2016_110)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlhO5QEACgkQTyzT2CeTzy2qdACfcq6GiasukLKsSU10miBTkH2t bsUAnAgy7qGUcEBKH3UJGEq22NxAsbqp =31qE -----END PGP SIGNATURE----- ----Security_Multipart(Tue_Dec_13_02_57_21_2016_110)---- From owner-freebsd-ports@freebsd.org Mon Dec 12 19:18:56 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1FBCAC735DB for ; Mon, 12 Dec 2016 19:18:56 +0000 (UTC) (envelope-from normas12@tuempresaactualizada.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 0EB66CE4 for ; Mon, 12 Dec 2016 19:18:56 +0000 (UTC) (envelope-from normas12@tuempresaactualizada.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0E07DC735DA; Mon, 12 Dec 2016 19:18:56 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0DB3BC735D9 for ; Mon, 12 Dec 2016 19:18:56 +0000 (UTC) (envelope-from normas12@tuempresaactualizada.com) Received: from mail3.tuempresaactualizada.com (mail3.tuempresaactualizada.com [107.150.32.197]) by mx1.freebsd.org (Postfix) with ESMTP id E2C0CCE2 for ; Mon, 12 Dec 2016 19:18:55 +0000 (UTC) (envelope-from normas12@tuempresaactualizada.com) Received: from WIN-JL967LLBK95 (107.150.32.196) by mail3.tuempresaactualizada.com id h9rs1m0our0l for ; Mon, 12 Dec 2016 13:18:49 -0600 (envelope-from ) X-client: DFINE08132 Message-ID: <1292362f75edb4cc613bf6050016b935@tuempresaactualizada.com> From: "=?utf-8?Q?C=C3=B3mo_Proteger_sus_Derechos?=" To: Subject: =?utf-8?Q?Devoluci=C3=B3n_de_Impuestos__-_En_L=C3=ADnea?= Date: Mon, 12 Dec 2016 13:18:48 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 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, 12 Dec 2016 19:18:56 -0000 IA0KDQpFbiBsw61uZWEgeSBlbiBWaXZvIC8gUGFyYSB0b2RvIHN1IEVxdWlwbyBjb24gdW5hIHNv bGEgQ29uZXhpw7NuIA0KDQpEZXZvbHVjacOzbiBkZSBJbXB1ZXN0b3MgWSBMYXMgUmVhY2Npb25l cyBkZSBsYXMgQXV0b3JpZGFkZXMgZmlzY2FsZXMgDQpDw7NtbyBwcm90ZWdlciBzdXMgZGVyZWNo b3MgZW4gbGEgUFJPREVDT04NCjIxIGRlIGRpY2llbWJyZSAtIE9ubGluZSBlbiBWaXZvIC0gMTA6 MDAgYSAxMzowMCB5IGRlIDE1OjAwIGEgMTg6MDAgSHJzICAgICAgIA0KIA0KUmVxdWVyaW1pZW50 b3MgRVhDRVNJVk9TLCBkZXNpc3RpbWllbnRvcyBkZSBkZXZvbHVjaW9uZXMgeSBuZWdhdGl2YXMg ZGUgY29tcGVuc2FjacOzbiBzb24gYWxndW5hcyBkZSBsYXMgaW5qdXN0aWNpYXMgYSBsYXMgcXVl IHNlIGVuZnJlbnRhbiBsb3MgY29udHJpYnV5ZW50ZXMgcXVlLCBlbiBlbCBjYWJhbCBjdW1wbGlt aWVudG8gZGUgc3VzIG9ibGlnYWNpb25lcywgZ2VuZXJhbiBzYWxkb3MgYSBmYXZvciBkZSBpbXB1 ZXN0b3MuDQoNCsKhTm8gc2UgZGVqZSBpbnRpbWlkYXIhIFVzdGVkIHB1ZWRlIHJlY3VwZXJhciBz dXMgaW1wdWVzdG9z4oCmIMKhcGVybywgcGFyYSBlbGxvLCBkZWJlIGNvbnRhciBjb24gbGEgcHJl cGFyYWNpw7NuIGFkZWN1YWRhISANCiJQcmVndW50ZSBwb3IgbnVlc3RyYSBQcm9tb2Npw7NuIE5h dmlkZcOxYSINCg0KDQpUZW1hcmlvOiANCg0KMS4gQ8OzbW8gY29udGVzdGFyIGxvcyByZXF1ZXJp bWllbnRvcyBleGNlc2l2b3MuDQoNCjIuIEPDs21vIGRvY3VtZW50YXIgb3BlcmFjaW9uZXMuDQoN CjMuIEltcGxpY2FjaW9uZXMgeSBzb2xpY2l0dWRlcyBkZSBkZXZvbHVjaW9uLCBjb21wZW5zYWNp w7NuIHkgYXVkaXRvcsOtYXMuDQoNCjQuIExhcyBwcsOhY3RpY2FzIGRlIGF1dG9yaWRhZGVzIGZp c2NhbGVzIHBhcmEgZGlsYXRhciwgbmVnYXIgbyB0ZW5lciBwb3IgZGVzaXN0aWRhcyBsYXMgc29s aWNpdHVkZXMuDQoNCg0KDQouLi7CoVkgbXVjaG8gbcOhcyENCg0KDQogDQrCv1JlcXVpZXJlIGxh IGluZm9ybWFjacOzbiBhIGxhIEJyZXZlZGFkPw0KcmVzcG9uZGEgZXN0ZSBlbWFpbCBjb24gbGEg cGFsYWJyYTogDQpJbXB1ZXN0b3MuDQpjZW50cm8gdGVsZWbDs25pY286IDAxODAwMjEyOTM5My4N Cg0KIA0KDQpMaWMuIFBhbWVsYSBSYW5nZWwNCkNvb3JkaW5hZG9yIGRlIEV2ZW50bw0KDQoNCiAN CsK/RGVtYXNpYWRvcyBtZW5zYWplcyBlbiBzdSBjdWVudGE/IFJlc3BvbmRhIGVzdGUgbWVuc2Fq ZSBpbmRpY2FuZG8gcXVlIHNvbG8gZGVzZWEgcmVjaWJpciBDQUxFTkRBUklPIHkgc8OzbG8gcmVj aWJpcsOhIHVuIGNvcnJlbyBhbCBtZXMuIFNpIGRlc2VhIGNhbmNlbGFyIGxhIHN1c2NyaXBjacOz biwgc29saWNpdGUgc3UgQkFKQS4gDQogDQoNCiANCg0KIA0KDQo= From owner-freebsd-ports@freebsd.org Mon Dec 12 19:23:26 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03EB3C73AE9 for ; Mon, 12 Dec 2016 19:23:26 +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 BB327127B; Mon, 12 Dec 2016 19:23:25 +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 73ACF2849A; Mon, 12 Dec 2016 20:23:22 +0100 (CET) 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 9BDE228498; Mon, 12 Dec 2016 20:23:21 +0100 (CET) Subject: Re: FreeBSD Port: print/gsfonts please make Japanese and Chinese fonts optional dependencies To: Hiroki Sato Cc: doceng@FreeBSD.org, freebsd-ports@FreeBSD.org References: <584ED3CB.1060500@quip.cz> <20161213.025721.480726455188804998.hrs@allbsd.org> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <584EF92A.5050505@quip.cz> Date: Mon, 12 Dec 2016 20:23:22 +0100 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: <20161213.025721.480726455188804998.hrs@allbsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2016 19:23:26 -0000 Hiroki Sato wrote on 2016/12/12 18:57: > Miroslav Lachman <000.fbsd@quip.cz> wrote > in <584ED3CB.1060500@quip.cz>: > > 00> Hi, > 00> > 00> we are using Xpdf which depends on Gsfonts and after last update there > 00> are a bunch of new dependencies brought by Chinese and Japanese fonts" > 00> > 00> New packages to be INSTALLED: > 00> zh-font-std: 0.0.20090602 > 00> zh-arphicttf: 2.11_5 > 00> mkfontdir: 1.0.7 > 00> mkfontscale: 1.1.2 > 00> xproto: 7.0.31 > 00> libfontenc: 1.1.3 > 00> ja-font-std: 0.0.20130501 > 00> ja-font-mplus-ipa: 1.0.20060520.p1_5 > 00> ja-font-ipa: 00303_6 > 00> > 00> We are not using any of these so I think they are useless for us. Can > 00> this be made as optional dependency? It can be default ON, we are > 00> using own poudriere repo but we are unable to disable them now. > > Thank you for your report. This problem should be fixed in the > latest print/gsfonts. Thank you for your quick reply and action! Your work is really appreciated. Miroslav Lachman From owner-freebsd-ports@freebsd.org Mon Dec 12 19:31:36 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CCD70C73FDC for ; Mon, 12 Dec 2016 19:31: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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 69D7D1C86 for ; Mon, 12 Dec 2016 19:31:35 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p5B226F57.dip0.t-ipconnect.de [91.34.111.87]) (authenticated bits=128) by land.berklix.org (8.15.2/8.15.2) with ESMTPA id uBCJVVJl036876; Mon, 12 Dec 2016 19:31:31 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 uBCJVPmx063495; Mon, 12 Dec 2016 20:31:26 +0100 (CET) (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 uBCJV0qO022291; Mon, 12 Dec 2016 20:31:13 +0100 (CET) (envelope-from jhs@berklix.com) Message-Id: <201612121931.uBCJV0qO022291@fire.js.berklix.net> To: Shane Ambler cc: "Janky Jay, III" , freebsd-ports@freebsd.org Subject: Re: The ports collection has some serious issues 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 "Mon, 12 Dec 2016 17:01:33 +1030." Date: Mon, 12 Dec 2016 20:31:00 +0100 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, 12 Dec 2016 19:31:36 -0000 > I would say this rarely happens with the default setup, the more port > options you change the more likely it is something will break. Yes, I now start: cd /var/db/ports; mv * MV/* ; setenv NO_DIALOG=YES Before: cd /usr/ports; make BERKLIX_CLIENT=YES # Uses ports/*/Makefile.local (still innumerable breaks of course on 1200 ports inc deps.) I can re-enable options for a 2nd pass rebuild for the very few ports need it (maybe some better way?). poudriere's `-f' is nice to accept a list. But I havent found a way to build my list yet from my Makefile.local eg cd /usr/ports; make BERKLIX_CLIENT=YES echo_my_category_and_port I'll probably hack bsd.port.mk & bsd.port.subdir.mk ${CATEGORIES}/${PORTNAME} is not quite usable, as eg mail/exmh2 emits "mail tk/exmh". Maybe just `pwd` & strip with sed PORTSDIR ? Cheers, Julian -- Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable. http://berklix.eu/brexit/#stolen_votes From owner-freebsd-ports@freebsd.org Mon Dec 12 20:59:29 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D62E3C732C5 for ; Mon, 12 Dec 2016 20:59:29 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-170.reflexion.net [208.70.211.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 86F2D7E1 for ; Mon, 12 Dec 2016 20:59:28 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 4360 invoked from network); 12 Dec 2016 20:59:32 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 12 Dec 2016 20:59:32 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.20.0) with SMTP; Mon, 12 Dec 2016 15:59:21 -0500 (EST) Received: (qmail 7911 invoked from network); 12 Dec 2016 20:59:21 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 12 Dec 2016 20:59:21 -0000 Received: from [192.168.1.118] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id DD3C1EC90AC; Mon, 12 Dec 2016 12:59:20 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?] From: Mark Millard In-Reply-To: Date: Mon, 12 Dec 2016 12:59:20 -0800 Cc: vbox@FreeBSD.org, Dimitry Andric , svn-ports-head@freebsd.org, FreeBSD Ports Content-Transfer-Encoding: quoted-printable Message-Id: References: <86C72DB2-B9ED-4512-A88C-BD1D9A23806F@dsl-only.net> <9D54F0CC-F38C-4CCE-BC33-25C1457BD44B@FreeBSD.org> <5C936BA8-6941-431A-B05F-31030816F85C@dsl-only.net> <487153E5-EF53-4960-9364-23992D7E0F76@dsl-only.net> To: Gerald Pfeifer X-Mailer: Apple Mail (2.3251) 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, 12 Dec 2016 20:59:29 -0000 [Top post asking if you (Gerald) think portmaster is in error and so if a bugzilla report should be made.] Do you expect that portmaster should instead/also(first) be checking (using the gcc6:lang/gcc6 related example from USE_GCC=3Dany): "pkg query %n-%v gcc6" instead of checking "pkg query %n-%v lang/gcc6"? If yes then a bugzilla report from you (a port maintainer with an example of the issue) may be better than my submitting claims of problems based on a less formal, less complete, less validated knowledge of the intended build environment properties for building ports. I can submit one if you think that is better for some reason. And thanks for all the notes about what I ran into and what you expect should be the case --even if it turned out that at least one official port-building tool did not work that way. (Most of my "knowledge" in the area is inference from the observed behavior of existing code instead of from from reading something indicating the intended properties.) =3D=3D=3D Mark Millard markmi at dsl-only.net On 2016-Dec-11, at 2:59 PM, Mark Millard wrote: [After "BUILD_DEPENDS+=3D gcc6:lang/gcc6" below shows that portmaster does not do what you indicate the build environment should do. The beginning is not essential material.] On 2016-Dec-11, at 4:40 AM, Gerald Pfeifer = wrote: > On Sun, 11 Dec 2016, Mark Millard wrote: >> I reported already that devel/kBuild/Makefile has in its >> Makefile: >>=20 >> USE_GCC=3D any >>=20 >> and devel/kBuild is what causes the lang/gcc* build. (I >> reported more than that but it is the part relevant here.) >=20 > I had read that, and I di investigate. It was just setup material (context) for what followed. I had no doubt that you had looked into what I'd reported. > USE_GCC=3Dany is the equivalent of USE_GCC=3D4.2+, and lang/gcc6 and > lang/gcc6-devel should both meet this requirement. >=20 > (In general, do not use a gcc*-devel port unless you really want=20 > or need to, though; use the corresponding gcc* port instead.) In genreal I have avoided *-devel's but with with -r428312 having updated the likes of devel/powerpc64-gcc and devel/amd64-gcc and such to be 6.2.0 based I was exploring what combinations of 6.2.0 installations were compatible vs. not. Historically on, e.g., powerpc64, devel/powerpc64-gcc and the matching lang/gcc* by version conflicted so I picked an alternate lang/gcc* if a devel/powerpc64-gcc updated to match what I already had from lang/gcc* . >> Additional information (gained later) is that if I "pkg delete=20 >> gcc6-devel" then instead of devel/kBuild trying to install lang/gcc6=20= >> it tries to install lang/gcc (no number). >=20 > That works as designed. USE_GCC=3Dyes defaults to lang/gcc. = USE_GCC=3Dany=20 > tries to use an existing GCC system compiler and lang/gcc by default = if=20 > none is present. Understood. >> If I clean that out and put back lang/gcc6-devel and try again it=20 >> goes back to trying to install lang/gcc6 . >=20 > That is a little odd. It means gcc6 from lang/gcc6-devel is found > and identified as a suitable version of GCC. Yep: odd. > Then Mk/bsd.gcc.mk adds >=20 > BUILD_DEPENDS+=3D gcc6:lang/gcc6 >=20 > when it resolves USE_GCC=3Dany. >=20 > That should not trigger and pull in lang/gcc6, though, as long > as gcc6 is found. You are wrong relative to portmaster: it uses (from "sh -x" output, including for its relevant recursive uses): # pkg query %n-%v lang/gcc6 as its test and ends up with am empty response that it interprets as needs-installation. By contrast: # pkg query %n-%v lang/gcc6-devel gcc6-devel-6.2.1.s20161201 gives a match and would be classified as installed. The sh -x output that is relevant: + pm_cd /usr/ports/lang/gcc6 + builtin cd /usr/ports/lang/gcc6 + grep -ql ^CONFLICTS Makefile + origin=3Dlang/gcc6 + iport_from_origin lang/gcc6 + local sn dir + [ -n yes ] + pkg query %n-%v lang/gcc6 + return 1 + iport=3D'' + check_exclude lang/gcc6 + [ -n '' ] + return 0 + [ -n '' -a -n '' ] + [ -n '' -a -n '' ] + [ -n '' ] + check_interactive lang/gcc6 + [ -n '' ] + return 0 + update_port lang/gcc6 + local deps + [ -n '' ] + [ -z '' ] + echo '=3D=3D=3D>>> Launching child to install lang/gcc6' =3D=3D=3D>>> Launching child to install lang/gcc6 + dep_of_deps=3D2 + [ -n pm_first_pass ] + [ ! '(' -n '' -a -n '' ')' ] + num_of_deps=3D2 + deps=3D'(2/2)' + term_printf ' >> devel/kBuild >> lang/gcc6 (2/2)' + echo -e '\n=3D=3D=3D>>> emulators/virtualbox-ose-additions >> = devel/kBuild >> lang/gcc6 (2/2)' =3D=3D=3D>>> emulators/virtualbox-ose-additions >> devel/kBuild >> = lang/gcc6 (2/2) + [ -n '' ] + printf '\033]0;portmaster: emulators/virtualbox-ose-additions >> = devel/kBuild >> lang/gcc6 (2/2)\007' ESC]0;portmaster: emulators/virtualbox-ose-additions >> devel/kBuild >> = lang/gcc6 (2/2)^G+ [ -n doing_dep_check -o '(' -n '' -a -n pm_first_pass = ')' ] + unset NO_DEP_UPDATES + [ -z '' -o -n pm_first_pass ] + sh -x /usr/local/sbin/portmaster -D -K lang/gcc6 + trap trap_exit INT >> It appears to be picking up that a gcc is installed when >> lang/gcc6-devel and that it is is version 6 based but then >> it looks for lang/gcc6 specifically but does not find it >> and so tries to install lang/gcc6. Its identification of the >> version is not enough to identify what specific gcc port >> to look for but it only looks for the one possible source >> to satisfy the dependency --and not finding that specific >> port it then tries to install that specific port that it >> did not find. >=20 > That's pretty close. It finds the gcc6 binary and hence settles > on GCC 6 as the compiler to use, but when resolving dependencies > then it apparently does not find the gcc6 binary (or does, and > something triggers a full rebuild regardless with lang/gcc6 instead=20 > of the original lang/gcc6-devel). See above for what portmaster really does. > Do you, by any chance, have some non-standard settings that would > trigger such an unconditional rebuild? I try to be as standard as I can given that I experiment with clang targeting powerpc64 and powerpc and other such oddities and that I want rather current C++ language/library standards. > In general, for ports work lang/gcc is the one to use, and lang/gccX=20= > over lang/gccX-devel. Relative to lang/gcc vs. lang/gcc* . . . A) devel/powerpc64-gcc and devel/amd64-gcc and the like updated to 6.2.0 at -r428312 . and: B) I want the more current C++ status. Historically I have avoided lang/gcc*-devel . But when devel/*-gcc's update versions I tend to experiment with what combinations conflict for installation vs. what combinations to not. > Somehow it feels your setup adds layers of shaky, untested and > non-standard elements on top of each other. Nope. As stands across /usr/src/ and /usr/ports/ I have around 19 patched files. I do tend to have KERNCONF files that include the standard ones and then change a few things. For ports I try to get by with /etc/make.file having: WANT_QT_VERBOSE_CONFIGURE=3D1 # DEFAULT_VERSIONS+=3Dperl5=3D5.24 WRKDIRPREFIX=3D/usr/obj/portswork WITH_DEBUG=3D WITH_DEBUG_FILES=3D MALLOC_PRODUCTION=3D But the binutils vintage problems for powerpc64 (system and head ports) and such lead me to do more for the contexts in which I deal with those. I tend to have powerpc64 and powerpc patches because of my experimenting with clang targeting them and that the standard powerpc64 build does not boot PowerMac G5's reliably. Some patches are ones that someone has requested that I try, usually relative to something that I've reported. I also have ones that work around problems so I can see if there is more to report.=20 > As far as lang/gcc* ports are concerned, I believe the best use > of our time will be moving lang/gcc from GCC 4.9 (where it finally > got to) to GCC 5. The only place that I've been using lang/gcc49 was on powerpc64 for my self-hosted libc++ based powerpc64 system builds: For buildworld buildkernel I used: 0) lang/gcc49 analogously to the clang system compiler 1) devel/powerpc64-sxtoolchain-gcc anlogously to a cross compiler toolchain. This was via SRC_CONF_ENV file content to control what was used. > Gerald =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Mon Dec 12 21:08:59 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09AA0C737B1 for ; Mon, 12 Dec 2016 21:08:59 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E92021C04 for ; Mon, 12 Dec 2016 21:08:58 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.88) (envelope-from ) id 1cGXq7-0009RZ-UG; Mon, 12 Dec 2016 14:08:51 -0700 Date: Mon, 12 Dec 2016 14:08:51 -0700 From: The Doctor To: dovecot@dovecot.org, freebsd-ports@freebsd.org Subject: Dovcot issues Message-ID: <20161212210851.GA35681@doctor.nl2k.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.7.1 (2016-10-04) 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, 12 Dec 2016 21:08:59 -0000 I am seeing issues with Thunderbird IMAP and POP3 and Entourage issues of non-deleting / repeating e-mail. Any one else gettting that? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Merry Christmas 2016 and Happy New Year 2017 From owner-freebsd-ports@freebsd.org Mon Dec 12 21:16:40 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08BEAC73B48; Mon, 12 Dec 2016 21:16:40 +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 DCEA2266; Mon, 12 Dec 2016 21:16:39 +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=Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date: Content-Transfer-Encoding:Content-Type:MIME-Version: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=I3C9rIWkmNc8Wp7Gfqw6975THCceLaMDZWOkO/hLmmY=; b=uf5VfcVtLeaZXK0Ljs4ZjSQiO0 vykCqBV5txVbTtUPxABIR3fIaT2uXlZdBYcw1M9A6W+AuI5r5iHb4q4dWlzfZohz1mi4wo3kx5FDJ xuytc0AcMx4T2s2v9E3gF9yd1YO96++020+DdoD5uFSTZ7xA980dclunOkfImtFo6t20=; Received: from thebighonker.lerctr.org ([2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]:41970 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cGXxb-000AOd-Tv; Mon, 12 Dec 2016 15:16:36 -0600 Received: from 2001:470:1f0f:42c:14a4:63d7:321:d9b2 by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Mon, 12 Dec 2016 15:16:35 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 12 Dec 2016 15:16:35 -0600 From: Larry Rosenman To: The Doctor Cc: dovecot@dovecot.org, freebsd-ports@freebsd.org, owner-freebsd-ports@freebsd.org Subject: Re: Dovcot issues In-Reply-To: <20161212210851.GA35681@doctor.nl2k.ab.ca> References: <20161212210851.GA35681@doctor.nl2k.ab.ca> Message-ID: X-Sender: ler@lerctr.org User-Agent: Roundcube Webmail/1.2.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: Mon, 12 Dec 2016 21:16:40 -0000 On 2016-12-12 15:08, The Doctor wrote: > I am seeing issues with > Thunderbird > > IMAP and POP3 > > and > > Entourage issues > > of non-deleting / repeating e-mail. > > Any one else gettting that? Not I. Which Dovecot release? Pigeonhole? Mailbox format? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 From owner-freebsd-ports@freebsd.org Tue Dec 13 00:20:16 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B205C733ED for ; Tue, 13 Dec 2016 00:20:16 +0000 (UTC) (envelope-from kayasaman@gmail.com) Received: from mail-wj0-x233.google.com (mail-wj0-x233.google.com [IPv6:2a00:1450:400c:c01::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D55F91AEA for ; Tue, 13 Dec 2016 00:20:15 +0000 (UTC) (envelope-from kayasaman@gmail.com) Received: by mail-wj0-x233.google.com with SMTP id v7so86895057wjy.2 for ; Mon, 12 Dec 2016 16:20:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=0gXnsodpF1p5fBtuS0+bIDer51B/bZVYCylWN/iS6nM=; b=qTTWh9X4LTyQTsCySCAUoZbzaMtYu2Fv/PFs218az9sY5exx8lvUFNo5BveO8pCqkC 9MRUw0WwkK2NQm+J+FgHOJvLM0I1ufxgRBmImUTJB3XFs/Ar5Y/ADgHNt5/DnP+vXSPv uFXDui+Bz4bUhffzu8+fqmJF869cFS/TONfSDGmU25YmsIUPmqaQ+k5RqmO/PoHWFZY+ IQ91VNrhvEZqpqf4gppV9tGTzP5svRcn5kSXnVuQsuYth0nN033NXSdK4F/pIbVMKl1c fyQ5krTej7TpxmQHYnBzMSAJUOGdihKdkROB8bPhs4h3aGHRbQ01AUyXailuJUFQ4mcw h6sA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=0gXnsodpF1p5fBtuS0+bIDer51B/bZVYCylWN/iS6nM=; b=JYh77DbVhe2fhIsru7C7D44DDLIBvbZPnP9xqrVgmsMthMXmZTut0eiZKH+YUD8zdK MLh37FEF/63KKI+OyJUzvpTnDcqmxCaP6suf6OE+c/G7xd0+NefIMSfLHRHkSbnG5LdG XEYu/meWOHtQiGi+wwllWhVR/6zMCfjRrC+a47j5oUpnhD2o09i9iJd9HHBQWa5LdTmc 70cdjiH2+CBhEKZ7GHn6v3v2Eh7QDRdJHMjyRUgL4cf5aVyFzSxtJ9R6VukLHcjVTLyR ZeYQe1bXdodCNWJe8QNMYogrmMSXdkYJOShKJ9FDOj0Wy47DluR7uIC7o/6X3RvP0yoq b4xg== X-Gm-Message-State: AKaTC00wm2Rvjq93bRFz9L3MVkafAOUGBWA9K0JLb3cLxtCgpszWdIREcz2m+s5s4fKkCQ== X-Received: by 10.194.205.225 with SMTP id lj1mr93605270wjc.122.1481588413501; Mon, 12 Dec 2016 16:20:13 -0800 (PST) Received: from x220.optiplex-networks.com (optiplexnetworks.plus.com. [212.159.80.17]) by smtp.googlemail.com with ESMTPSA id cl6sm59556271wjc.10.2016.12.12.16.20.12 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Dec 2016 16:20:12 -0800 (PST) To: freebsd-ports From: Kaya Saman Subject: Ntopng port segfaulting when using with Mysql Message-ID: <0570f8c8-00fa-2f70-53ce-260796189e88@gmail.com> Date: Tue, 13 Dec 2016 00:20:12 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2016 00:20:16 -0000 Hi, I'm trying to run Ntopng while logging to a Mysql server. I'm using this command to start it: ntopng -r ris-server:6379 -i lagg0 -F "mysql;remote-db-host;ntopng;flows;uname;passwd" -U ntopng -m 192.168.0.0/16,172.16.0.0/12,10.0.0.0/8 -D all -S all What happens is that if I click on a host IP address then the Graph icon I get this: 13/Dec/2016 00:16:12 [NetworkInterface.cpp:1057] WARNING: If you have TSO/GRO enabled, please disable it Segmentation fault I'm wondering if it's something to do with this: https://github.com/ntop/ntopng/issues/778 or something in the actual Port build mechanism causing this like a library or so? The version I have installed should be the latest from @Ports: # ntopng -V v.2.5.161212 [Community Edition] GIT rev: :2.5.161212 Any insight would be highly appreciated. Regards, Kaya From owner-freebsd-ports@freebsd.org Tue Dec 13 00:23:57 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3833AC738ED for ; Tue, 13 Dec 2016 00:23:57 +0000 (UTC) (envelope-from kayasaman@gmail.com) Received: from mail-wj0-x22f.google.com (mail-wj0-x22f.google.com [IPv6:2a00:1450:400c:c01::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 B9E2126D for ; Tue, 13 Dec 2016 00:23:56 +0000 (UTC) (envelope-from kayasaman@gmail.com) Received: by mail-wj0-x22f.google.com with SMTP id tg4so86939460wjb.1 for ; Mon, 12 Dec 2016 16:23:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to; bh=yn4g/hsrfoBTvvcrufNy9sw7EHL1aDanK9L/0EeOBKU=; b=ebn632z11ZM4rRoCBrofuXOkaOzHqf3E6GLitV1z+qqzF34taeqWBsBQyiFBo1LaaS XsBMTpJc4TY6fBAnub7fDKgu2whDF4aqcxes1VTnD4z//dYe/Ipiy9vELpK1amgbBMSQ roL5tZ3WfQLvfR7+R1HE4XUInBcy8+E5MSdAHoDzZBVAjwtgXUkRIrUmhVGsy7JZtkgE 02HSPn1OCRbk6H1NhWFE5fqevcCdz/LO0GV/7z60nuqB0v1hNuC7PqC8EgAO1zpjy8xt gk5SluR3ua9QitIbJZWDt8/KCo84yYXodd7vuVQbNGlx3UM7GfdqOZiN735Pjy1exG+2 x0Mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to; bh=yn4g/hsrfoBTvvcrufNy9sw7EHL1aDanK9L/0EeOBKU=; b=NvgxEMadhoIYkU0x4Hd4MNZ0Y0IfI8H1skALnSZeF76ta3IcEOsUKwDPuQb2rWecyW 31WEb8xjXiETPpN2sXiS6QQcbsHV6bM99jdm9TWdsnt4XG5IBaXycNyQpR/ZfqXlCUFu KaQJ41j0evE9PnnRuiU6Cg3B6Au32RqHpAdA5RTO1m/NGWkVv/50VRvynaXHbSKNYvSF bPpbmeALRoacEtcefmEBXH8LLjXI2eSSX80lhdmv8UMQFTW/LUI2Ph+kR0uTTYgkPH/3 30qYoVwJBehM/sLtgK2Prv+QLhBpl75qBi489Zb2EJCzgDGOhXRCOYDiAhg6OVX+95k8 carQ== X-Gm-Message-State: AKaTC01JTF14kgqrACyT3L/epGpSRh3TYB4H9bpc3Vh99tN7jWTnQhh4PVaIw6tIasTtsg== X-Received: by 10.194.109.42 with SMTP id hp10mr58317104wjb.167.1481588634708; Mon, 12 Dec 2016 16:23:54 -0800 (PST) Received: from x220.optiplex-networks.com (optiplexnetworks.plus.com. [212.159.80.17]) by smtp.googlemail.com with ESMTPSA id kp5sm59620087wjb.8.2016.12.12.16.23.53 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Dec 2016 16:23:54 -0800 (PST) Subject: Fwd: Ntopng port segfaulting when using with Mysql References: <0570f8c8-00fa-2f70-53ce-260796189e88@gmail.com> To: freebsd-ports From: Kaya Saman X-Forwarded-Message-Id: <0570f8c8-00fa-2f70-53ce-260796189e88@gmail.com> Message-ID: <72415579-c88b-3182-05e5-37a9c938a69b@gmail.com> Date: Tue, 13 Dec 2016 00:23:53 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <0570f8c8-00fa-2f70-53ce-260796189e88@gmail.com> 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: Tue, 13 Dec 2016 00:23:57 -0000 If it helps here's the -v "Verbose" output: 13/Dec/2016 00:21:32 [Lua.cpp:218] Found 1 interface views 13/Dec/2016 00:21:32 [Ntop.cpp:759] No allowed interface found for lagg0 13/Dec/2016 00:21:32 [Lua.cpp:222] Returning name lagg0 13/Dec/2016 00:21:32 [Lua.cpp:271] ntop_select_interface() called 13/Dec/2016 00:21:32 [Ntop.cpp:1171] Getting interface view at name lagg0 13/Dec/2016 00:21:32 [Ntop.cpp:759] No allowed interface found for lagg0 13/Dec/2016 00:21:32 [Lua.cpp:250] getCurrentInterface() called 13/Dec/2016 00:21:32 [Lua.cpp:2771] ntop_get_interface_stats() called 13/Dec/2016 00:21:32 [Lua.cpp:271] ntop_select_interface() called 13/Dec/2016 00:21:32 [Ntop.cpp:1171] Getting interface view at name lagg0 13/Dec/2016 00:21:32 [Ntop.cpp:759] No allowed interface found for lagg0 13/Dec/2016 00:21:32 [Lua.cpp:250] getCurrentInterface() called 13/Dec/2016 00:21:32 [Lua.cpp:2771] ntop_get_interface_stats() called 13/Dec/2016 00:21:32 [Lua.cpp:717] ntop_is_windows() called 13/Dec/2016 00:21:32 [Lua.cpp:717] ntop_is_windows() called 13/Dec/2016 00:21:32 [Lua.cpp:607] ntop_is_not_empty_file() called 13/Dec/2016 00:21:32 [Lua.cpp:2229] ntop_rrd_fetch(/var/tmp/ntopng/1/rrd/..../bytes.rrd) 13/Dec/2016 00:21:32 [Lua.cpp:4201] ntop_lua_http_print() called 13/Dec/2016 00:21:32 [Lua.cpp:4201] ntop_lua_http_print() called 13/Dec/2016 00:21:32 [Lua.cpp:4201] ntop_lua_http_print() called 13/Dec/2016 00:21:32 [Lua.cpp:4201] ntop_lua_http_print() called 13/Dec/2016 00:21:32 [Lua.cpp:4201] ntop_lua_http_print() called 13/Dec/2016 00:21:32 [Lua.cpp:4201] ntop_lua_http_print() called 13/Dec/2016 00:21:32 [Lua.cpp:4201] ntop_lua_http_print() called 13/Dec/2016 00:21:32 [Lua.cpp:4201] ntop_lua_http_print() called 13/Dec/2016 00:21:32 [Lua.cpp:4201] ntop_lua_http_print() called 13/Dec/2016 00:21:32 [Lua.cpp:2470] ntop_get_prefs() called 13/Dec/2016 00:21:32 [Lua.cpp:250] getCurrentInterface() called 13/Dec/2016 00:21:32 [Lua.cpp:2834] ntop_interface_exec_sql_query() called 13/Dec/2016 00:21:32 [Lua.cpp:250] getCurrentInterface() called 13/Dec/2016 00:21:32 [Lua.cpp:388] ntop_get_ndpi_protocol_id() called Segmentation fault -------- Forwarded Message -------- Subject: Ntopng port segfaulting when using with Mysql Date: Tue, 13 Dec 2016 00:20:12 +0000 From: Kaya Saman To: freebsd-ports Hi, I'm trying to run Ntopng while logging to a Mysql server. I'm using this command to start it: ntopng -r ris-server:6379 -i lagg0 -F "mysql;remote-db-host;ntopng;flows;uname;passwd" -U ntopng -m 192.168.0.0/16,172.16.0.0/12,10.0.0.0/8 -D all -S all What happens is that if I click on a host IP address then the Graph icon I get this: 13/Dec/2016 00:16:12 [NetworkInterface.cpp:1057] WARNING: If you have TSO/GRO enabled, please disable it Segmentation fault I'm wondering if it's something to do with this: https://github.com/ntop/ntopng/issues/778 or something in the actual Port build mechanism causing this like a library or so? The version I have installed should be the latest from @Ports: # ntopng -V v.2.5.161212 [Community Edition] GIT rev: :2.5.161212 Any insight would be highly appreciated. Regards, Kaya From owner-freebsd-ports@freebsd.org Tue Dec 13 00:57:53 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B112C74090; Tue, 13 Dec 2016 00:57:53 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 040F41270; Tue, 13 Dec 2016 00:57:52 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.88) (envelope-from ) id 1cGbPh-000JLz-Da; Mon, 12 Dec 2016 17:57:49 -0700 Date: Mon, 12 Dec 2016 17:57:49 -0700 From: The Doctor To: Larry Rosenman Cc: owner-freebsd-ports@freebsd.org, freebsd-ports@freebsd.org, dovecot@dovecot.org Subject: Re: Dovcot issues Message-ID: <20161213005749.GB74126@doctor.nl2k.ab.ca> References: <20161212210851.GA35681@doctor.nl2k.ab.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) 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, 13 Dec 2016 00:57:53 -0000 On Mon, Dec 12, 2016 at 03:16:35PM -0600, Larry Rosenman wrote: > On 2016-12-12 15:08, The Doctor wrote: > > I am seeing issues with > > Thunderbird > > > > IMAP and POP3 > > > > and > > > > Entourage issues > > > > of non-deleting / repeating e-mail. > > > > Any one else gettting that? > Not I. Which Dovecot release? Pigeonhole? Mailbox format? Dovcote 2.2.27 using mbox. > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 E-Mail: ler@lerctr.org > US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Merry Christmas 2016 and Happy New Year 2017 From owner-freebsd-ports@freebsd.org Tue Dec 13 01:11:15 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D9A1C7462D; Tue, 13 Dec 2016 01:11:15 +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 E01DB18BD; Tue, 13 Dec 2016 01:11:14 +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=Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date: Content-Transfer-Encoding:Content-Type:MIME-Version: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=y9ktRT9d3oSkX2/6AkDHYfLRV0xugTcfnNZmSxLHwm4=; b=pmBZf4TbbsaQegGGfrObzxHReQ mbI4F40TLosdgXYT1TorHgLI7KwZtPA6UXLc1Wg9xBRFclNXIRj99jhffvZ0+NsCHGje8JWZEuYDK TCLLOgKobw5Xa3YePPQvcT/GJfB4KYeNf5Mn/1UVsZbwpIIyuLZkGpkDIEiXfPDl2AHo=; Received: from thebighonker.lerctr.org ([2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]:46416 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cGbcg-000I0E-15; Mon, 12 Dec 2016 19:11:14 -0600 Received: from 74-196-221-212.pfvlcmta01.res.dyn.suddenlink.net ([74.196.221.212]) by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Mon, 12 Dec 2016 19:11:13 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 12 Dec 2016 19:11:13 -0600 From: Larry Rosenman To: The Doctor Cc: owner-freebsd-ports@freebsd.org, freebsd-ports@freebsd.org, dovecot@dovecot.org Subject: Re: Dovcot issues In-Reply-To: <20161213005749.GB74126@doctor.nl2k.ab.ca> References: <20161212210851.GA35681@doctor.nl2k.ab.ca> <20161213005749.GB74126@doctor.nl2k.ab.ca> Message-ID: <856314736e6025b482f75493ae435fcd@lerctr.org> X-Sender: ler@lerctr.org User-Agent: Roundcube Webmail/1.2.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, 13 Dec 2016 01:11:15 -0000 On 2016-12-12 18:57, The Doctor wrote: > On Mon, Dec 12, 2016 at 03:16:35PM -0600, Larry Rosenman wrote: >> On 2016-12-12 15:08, The Doctor wrote: >> > I am seeing issues with >> > Thunderbird >> > >> > IMAP and POP3 >> > >> > and >> > >> > Entourage issues >> > >> > of non-deleting / repeating e-mail. >> > >> > Any one else gettting that? >> Not I. Which Dovecot release? Pigeonhole? Mailbox format? > > Dovcote 2.2.27 using mbox. > Same Here, FreeBSD with no issues whatsoever. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 From owner-freebsd-ports@freebsd.org Tue Dec 13 01:28:55 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C7E7C74310 for ; Tue, 13 Dec 2016 01:28:55 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [IPv6:2001:418:3fd::f7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1858F89A for ; Tue, 13 Dec 2016 01:28:54 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:418:3fd::1f] (haymarket.m5p.com [IPv6:2001:418:3fd::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id uBD1SlqU005181 for ; Mon, 12 Dec 2016 20:28:53 -0500 (EST) (envelope-from george+freebsd@m5p.com) Subject: Re: Dovcot issues To: freebsd-ports@freebsd.org References: <20161212210851.GA35681@doctor.nl2k.ab.ca> <20161213005749.GB74126@doctor.nl2k.ab.ca> <856314736e6025b482f75493ae435fcd@lerctr.org> From: George Mitchell Message-ID: <5f64fc8a-bd8f-e664-98e1-fb6a8026ea9c@m5p.com> Date: Mon, 12 Dec 2016 20:28:47 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <856314736e6025b482f75493ae435fcd@lerctr.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.8 required=10.0 tests=ALL_TRUSTED, RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.1 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Mon, 12 Dec 2016 20:28:53 -0500 (EST) 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, 13 Dec 2016 01:28:55 -0000 On 12/12/16 20:11, Larry Rosenman wrote: > On 2016-12-12 18:57, The Doctor wrote: >> On Mon, Dec 12, 2016 at 03:16:35PM -0600, Larry Rosenman wrote: >>> On 2016-12-12 15:08, The Doctor wrote: >>> > I am seeing issues with >>> > Thunderbird >>> > >>> > IMAP and POP3 >>> > >>> > and >>> > >>> > Entourage issues >>> > >>> > of non-deleting / repeating e-mail. >>> > >>> > Any one else gettting that? >>> Not I. Which Dovecot release? Pigeonhole? Mailbox format? >> >> Dovcote 2.2.27 using mbox. >> > > Same Here, FreeBSD with no issues whatsoever. > May I suggest "grep dovecot /var/log/maillog" on your server for possibly informative messages? -- George From owner-freebsd-ports@freebsd.org Tue Dec 13 01:55:47 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF04EC743DC; Tue, 13 Dec 2016 01:55:47 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor.nl2k.ab.ca (doctor.nl2k.ab.ca [204.209.81.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B7AB818C9; Tue, 13 Dec 2016 01:55:47 +0000 (UTC) (envelope-from doctor@doctor.nl2k.ab.ca) Received: from doctor by doctor.nl2k.ab.ca with local (Exim 4.88) (envelope-from ) id 1cGcJm-000M1O-GN; Mon, 12 Dec 2016 18:55:46 -0700 Date: Mon, 12 Dec 2016 18:55:46 -0700 From: The Doctor To: Larry Rosenman Cc: freebsd-ports@freebsd.org, owner-freebsd-ports@freebsd.org, dovecot@dovecot.org Subject: Re: Dovcot issues Message-ID: <20161213015546.GA84504@doctor.nl2k.ab.ca> References: <20161212210851.GA35681@doctor.nl2k.ab.ca> <20161213005749.GB74126@doctor.nl2k.ab.ca> <856314736e6025b482f75493ae435fcd@lerctr.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <856314736e6025b482f75493ae435fcd@lerctr.org> User-Agent: Mutt/1.7.1 (2016-10-04) 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, 13 Dec 2016 01:55:47 -0000 On Mon, Dec 12, 2016 at 07:11:13PM -0600, Larry Rosenman wrote: > On 2016-12-12 18:57, The Doctor wrote: > > On Mon, Dec 12, 2016 at 03:16:35PM -0600, Larry Rosenman wrote: > >> On 2016-12-12 15:08, The Doctor wrote: > >> > I am seeing issues with > >> > Thunderbird > >> > > >> > IMAP and POP3 > >> > > >> > and > >> > > >> > Entourage issues > >> > > >> > of non-deleting / repeating e-mail. > >> > > >> > Any one else gettting that? > >> Not I. Which Dovecot release? Pigeonhole? Mailbox format? > > > > Dovcote 2.2.27 using mbox. > > > > Same Here, FreeBSD with no issues whatsoever. > Looks like the problem is that /var/mail was switched back to chmod 0755 when it should be 1775 or 1777. > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 E-Mail: ler@lerctr.org > US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Merry Christmas 2016 and Happy New Year 2017 From owner-freebsd-ports@freebsd.org Tue Dec 13 05:27:16 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E0C1C7540E for ; Tue, 13 Dec 2016 05:27:16 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ua0-x22f.google.com (mail-ua0-x22f.google.com [IPv6:2607:f8b0:400c:c08::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 3AC9310B2 for ; Tue, 13 Dec 2016 05:27:16 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ua0-x22f.google.com with SMTP id 12so102832896uas.2 for ; Mon, 12 Dec 2016 21:27:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=hTGN8HYiAfZzLoz4sLbLQKBS8VZtKX+/nYDDC5ogkOo=; b=uFvmNQPw/zs5HlU0qNMlDYzmm4Mhve4gAIzPjDXDp8LG4O6i2jme4mAQmAKjmoexpu 6NiayFvxw7smaSkLpBEVolAHhJwLJ75wdQsTKD3EqJjy/2kTEMVzMb4PWCYtF1r46KOP GEVBUkm7VrGCvDtxLl7l7zLplRo83gb9+sj7JPXbA2fJ+frrdxGV7JcQiJwB3+smXnEb 3vRUDZ4Akw/WDTYQg6RxAnmV44t4fVaKM4fa1EGkd0QV4K6aVsjQyhK7iSFOoyRV1hyi 5TfwA1L4G+ltJAlJ4erbUSK1MW9jnQsaSN2WGxI0pGHO0fyKwL0xrrUYN1BYFuF5zMWX WF3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=hTGN8HYiAfZzLoz4sLbLQKBS8VZtKX+/nYDDC5ogkOo=; b=RpH4Pv31efnokv2oM1Qa468B90jPkfsbRrv3Si1fUH0rsJ1jyoONf88i2xx2pv3PIL JXpod8FhJCSIlgLLSQ3NruTOu2aUnRXu0BFXnlNir8NmoGHiz1B8f3Wm7zS+b3R1dV1O Z4/Lj8ZifmfKbiDIov8+beohkMcurHNb1tEv5bksKv7csDuM4aNUY+70hpq0mLCCSul2 tA/o8ukOQ8jHbMtyoKT6rmMv3fjhHN63y0X8UfgDRVuPGi+HVtRvAISVB3AzVXEHS11N 3+/2ozM05uBNboR/PP2i0j1gHZOb6GVs0Y64Iv81fJYcR8PhVorqDuWo2Fpk09/pvPrg JWwQ== X-Gm-Message-State: AKaTC01J6+46yvF8b+aYx4daUFNYWcC+qMu6yia5qK0vSrCp6qdZN7obYGp8WASfqfKv79RyMzelJ/kGHHWvig== X-Received: by 10.176.64.234 with SMTP id i97mr65758338uad.7.1481606835268; Mon, 12 Dec 2016 21:27:15 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.122.15 with HTTP; Mon, 12 Dec 2016 21:27:14 -0800 (PST) In-Reply-To: <201612121931.uBCJV0qO022291@fire.js.berklix.net> References: <201612121931.uBCJV0qO022291@fire.js.berklix.net> From: Kevin Oberman Date: Mon, 12 Dec 2016 21:27:14 -0800 X-Google-Sender-Auth: EB2uMOY9_JMfL38tiG6Fuh93BYM Message-ID: Subject: Re: The ports collection has some serious issues To: "Julian H. Stacey" Cc: Shane Ambler , "Janky Jay, III" , 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, 13 Dec 2016 05:27:16 -0000 On Mon, Dec 12, 2016 at 11:31 AM, Julian H. Stacey wrote: > > I would say this rarely happens with the default setup, the more port > > options you change the more likely it is something will break. > > Yes, I now start: cd /var/db/ports; mv * MV/* ; setenv NO_DIALOG=YES > Before: cd /usr/ports; make BERKLIX_CLIENT=YES # Uses > ports/*/Makefile.local > (still innumerable breaks of course on 1200 ports inc deps.) > > I can re-enable options for a 2nd pass rebuild for the very > few ports need it (maybe some better way?). > > poudriere's `-f' is nice to accept a list. > But I havent found a way to build my list yet from my Makefile.local eg > cd /usr/ports; make BERKLIX_CLIENT=YES echo_my_category_and_port > I'll probably hack bsd.port.mk & bsd.port.subdir.mk > > ${CATEGORIES}/${PORTNAME} is not quite usable, as eg mail/exmh2 emits > "mail tk/exmh". Maybe just `pwd` & strip with sed PORTSDIR ? > > Cheers, > Julian > -- > Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich > Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, > quoted-printable. > http://berklix.eu/brexit/#stolen_votes Just to d one more opinion to this thread, I really agree with Julian that there needs to be a saved quarterly and an active quarterly for exactly the reasons he stated. the jump from quarter to quarter obviates many of the advantages of a quarterly branch Second, I am a bit bewildered at the people who have so much trouble with building from ports. I use portmaster and really wish there was an option to try to continue when a port bombs, but it works well for me. Just this weekend I had to re-build about 90 ports and it went of without a hitch. It is to have at least some understanding of how ports work to minimize problems. Thing like MAKE_JOBS_UNSAFE and trying to wait a bit (a few hours) and trying to update the sources when something fails. I do wish all of this was better documented, though. Guess I should try doing something about that. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-ports@freebsd.org Tue Dec 13 07:08:55 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 95E1BC75733 for ; Tue, 13 Dec 2016 07:08:55 +0000 (UTC) (envelope-from christer.solskogen@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 77D0A7C2 for ; Tue, 13 Dec 2016 07:08:55 +0000 (UTC) (envelope-from christer.solskogen@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 77357C75732; Tue, 13 Dec 2016 07:08:55 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 76DCBC75731 for ; Tue, 13 Dec 2016 07:08:55 +0000 (UTC) (envelope-from christer.solskogen@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1074E7C1 for ; Tue, 13 Dec 2016 07:08:55 +0000 (UTC) (envelope-from christer.solskogen@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id t79so104679647wmt.0 for ; Mon, 12 Dec 2016 23:08:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc; bh=m+6QfBHl5uL2cLmxwRRHMv0Ot9lzW4XMOHF37PtMYKE=; b=vejLnIH1y2XrI882tM/L+tT2hIeMrRdiTpvPk/NYZbk/05P5C9YSQgrMsf37KFn3Jq g6QDtuLdkYJwLSxHLOlzl5fz/MVGk6qJ3gJSOJZ/81bhBtLryL3kOe+waRe908sWWNP0 Z9h8aJNGvgFaQNBSvVGfP7G/OUzeVj5ifw0FYyRry5zZqZsa2uQAe4dacqIL68wVmdLI AtMjG5r1mAzwEukVjprVyjRQ7sKeu5d+qlCwgAwTaLtBQ+yIpdZApDgRGXexvEvL7VcH yex22vSK752drMHV4jD1WUxYPwMW0Wo5BtdULDzc/Ey14Q235rT69noEWghyrqCcD4Rg ZGuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=m+6QfBHl5uL2cLmxwRRHMv0Ot9lzW4XMOHF37PtMYKE=; b=Q+oSfTvSMmGpiOZpuez1nrDAthKYKMcEoG4MTEZKctEiMZLfm3VGzj1+9pkM1DUtIT aC0vvaPFt+ZQ/mbq4xMkjvhrzZO0yTh1NnuINieu5Vsh4ExcmpL92PUMN08SMjtogy7W XfLAMoDkgM6+gpm5vDkCRIRutRqBLUJ6pZTlAR7YC/mficCSY9LF8Nvz9KJYAIk6S3Pq IuAcUp/BRmNp/4Uw8b6VjC4nih+R2RHl5kIrIH0fHZPi4QCrXsbsqdIhPyL2kS2k2YaR NfWSLdaQ/5wbyuddIpXYereWf+sCvqDudhzQWYRSFOevFuCXDnhBPcs948r7b7RfCPyU lK8g== X-Gm-Message-State: AKaTC01luGhbapAnL/h/GLqYlBMr/lz2r7Qp1hF+RCtyE5jge+4IcVFOEr30C7cI/gHE+BUnl3q0cJhukYAheA== X-Received: by 10.28.0.210 with SMTP id 201mr1128297wma.49.1481612932740; Mon, 12 Dec 2016 23:08:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.154.100 with HTTP; Mon, 12 Dec 2016 23:08:12 -0800 (PST) From: Christer Solskogen Date: Tue, 13 Dec 2016 08:08:12 +0100 Message-ID: Subject: FS-UAE port out of date To: tomse@oagd.net Cc: FreeBSD Ports Mailing List 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, 13 Dec 2016 07:08:55 -0000 Just a small remider :-) Hopefully you can update it. -- chs From owner-freebsd-ports@freebsd.org Tue Dec 13 07:50:23 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31623C75362 for ; Tue, 13 Dec 2016 07:50:23 +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 EFD3D1A4D for ; Tue, 13 Dec 2016 07:50:22 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3tdBh60SrczZql; Tue, 13 Dec 2016 08:50:14 +0100 (CET) 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 39eH9z3m2hwK; Tue, 13 Dec 2016 08:50:12 +0100 (CET) Received: from marvin.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Tue, 13 Dec 2016 08:50:12 +0100 (CET) Subject: Re: Ntopng port segfaulting when using with Mysql To: Kaya Saman , freebsd-ports References: <0570f8c8-00fa-2f70-53ce-260796189e88@gmail.com> From: Guido Falsi Message-ID: <0f14ee2c-1094-0b30-bf29-ce9ed7f15e68@FreeBSD.org> Date: Tue, 13 Dec 2016 08:50:11 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <0570f8c8-00fa-2f70-53ce-260796189e88@gmail.com> Content-Type: text/plain; charset=windows-1252 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, 13 Dec 2016 07:50:23 -0000 On 12/13/16 01:20, Kaya Saman wrote: > Hi, > > > I'm trying to run Ntopng while logging to a Mysql server. > Hi, I'll send you an update to the port to test. Please give me a little while to prepare it. Upstream is not tagging releases but just grabs periodically the head of the stable branch and packages that, this is in contrast with how ports manage things, so I'll have to think about how to actually update the port. -- Guido Falsi From owner-freebsd-ports@freebsd.org Tue Dec 13 08:03:27 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07397C75981 for ; Tue, 13 Dec 2016 08:03:27 +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 E88E235D for ; Tue, 13 Dec 2016 08:03:26 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id E7E40C7597E; Tue, 13 Dec 2016 08:03:26 +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 E5E32C7597D for ; Tue, 13 Dec 2016 08:03:26 +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 D92A835C for ; Tue, 13 Dec 2016 08:03:26 +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 uBD83QJJ065852 for ; Tue, 13 Dec 2016 08:03:26 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id uBD83QRo065851; Tue, 13 Dec 2016 08:03:26 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201612130803.uBD83QRo065851@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, 13 Dec 2016 08:03:26 +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, 13 Dec 2016 08:03:27 -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 ------------------------------------------------+-----------------+------------ comms/gammu | 1.37.91 | 1.38.0 ------------------------------------------------+-----------------+------------ science/pynn | 0.8.1 | 0.8.2 ------------------------------------------------+-----------------+------------ sysutils/shlock | 2.6.0 | 2.6.1 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Tue Dec 13 09:32:00 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E11FEC6B9D8 for ; Tue, 13 Dec 2016 09:32:00 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-163.reflexion.net [208.70.211.163]) (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 7F30BF98 for ; Tue, 13 Dec 2016 09:31:59 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 32527 invoked from network); 13 Dec 2016 09:31:58 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 13 Dec 2016 09:31:58 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.20.0) with SMTP; Tue, 13 Dec 2016 04:31:58 -0500 (EST) Received: (qmail 16690 invoked from network); 13 Dec 2016 09:31:58 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 13 Dec 2016 09:31:58 -0000 Received: from [192.168.1.118] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id C232DEC8816 for ; Tue, 13 Dec 2016 01:31:57 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: The ports collection has some serious issues Message-Id: <03DF1D77-0F7E-46E0-9151-4F6E33B82C80@dsl-only.net> Date: Tue, 13 Dec 2016 01:31:57 -0800 To: FreeBSD Ports X-Mailer: Apple Mail (2.3251) 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, 13 Dec 2016 09:32:01 -0000 Julian Elischer julian at freebsd.org wrote on Mon Dec 12 16:15:32 UTC 2016: > The problem I get hit by is that the quarterly packages are deleted > immediately on the creation of the next quarterly set. Packages: true --but not true of svn's sources for ports: https://svnweb.freebsd.org/ports/branches/201*Q*/ svn has 2014 's, 2015 's, and 2016 's sources for each of the quarters: Q1 , Q2 , Q3 , Q4 . Things seem to be set up more for source based builds (or local package builds and distribution based on such sources for such builds). (Not that I'm doing anything where I depend on the issues or distinctions. I just noted the quarterly history that is available and where it happens to exist --which may well be obvious to most folks involved.) === Mark Millard markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Tue Dec 13 16:11:14 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4060C75CB9 for ; Tue, 13 Dec 2016 16:11:14 +0000 (UTC) (envelope-from rizzo@i805.com.br) Received: from server.i805.com.br (mailhost.i805.com.br [50.7.9.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fbsd10.amd64", Issuer "fbsd10.amd64" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A4EF1FFD for ; Tue, 13 Dec 2016 16:11:13 +0000 (UTC) (envelope-from rizzo@i805.com.br) Received: from www.i805.com.br (localhost [127.0.0.1]) by server.i805.com.br (8.15.2/8.15.2) with ESMTP id uBDGAVLA072454 for ; Tue, 13 Dec 2016 18:10:51 +0200 (EET) (envelope-from rizzo@i805.com.br) From: "Nilton Jose Rizzo" To: freebsd-ports@freebsd.org Subject: How I do this? Date: Tue, 13 Dec 2016 13:10:31 -0300 Message-Id: <20161213155952.M21328@i805.com.br> X-Mailer: OpenWebMail 3.00_beta4 20140806 79bb7cc X-OriginatingIP: 186.221.219.53 (rizzo) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on server.i805.com.br 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, 13 Dec 2016 16:11:14 -0000 Hi all I need to use a new version of OpenCV 3.1. I removed the OpenCv 2.4 version and I installed the new version, but now I need to install other ports that needs opencv, the ports system tells me to install a opencv2.4. Is there something to ports' system accept a new version of OpenCV? --- /************************************************* **Nilton José Rizzo UFRRJ **http://www.rizzo.eng.br http://www.ufrrj.br **http://lattes.cnpq.br/0079460703536198 **************************************************/ From owner-freebsd-ports@freebsd.org Tue Dec 13 16:24:06 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61A09C763B6 for ; Tue, 13 Dec 2016 16:24:06 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::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 26D12FCD for ; Tue, 13 Dec 2016 16:24:05 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mail-qk0-x230.google.com with SMTP id q130so121335611qke.1 for ; Tue, 13 Dec 2016 08:24:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=7PftQJdpcqMkSipSJTWq1UiNNPnsv5WuzfvADLsTW9w=; b=Sxmjc+h1EyWhlB+BjVfhPNOb9pTUyoWqgvDnCpkRp5Ylm/k5E6uzz+w5EOA6ywBOBa Rvu+Wb64YjZ18myF9Fg4WSmwTDNlkfeQpHxYihxQAMsap9hfNBs23bEJ5ABx0BO0aly1 TAuQtfr2X/ufub8cbzAnLbFcyBgTTLFAq1phI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=7PftQJdpcqMkSipSJTWq1UiNNPnsv5WuzfvADLsTW9w=; b=AsHpjUqQ8lJBid5i7LcrLwRqhrqH2Lm4IsFPPSLAYir7tyQcpYQ9AhYmvhejepP42n Cz8oX/KIkUHBL78zbM580JP+2fPaWSWuIDnQok4vLQG0Q3XLcapzKK3MnnP/63zrc5mR zqfGrRvw4S8XxyHQU8UQwQguf2HGHE6pKRKBKp1GjwAM+39GXvQRGYI1xDS/a9C8JuBe 32qp2jSmp/UYy8xUThgxgGE1fzp/jhgJsZV1n/OB33bzEqGpjfUagmsZ7tLfnl/UXskY G563BHnxS14YZ0IVKrwRiHXG8aRKbot6Wfz9Hztnv9DamtjmLaorjuTokN66UGELy09N 2cGA== X-Gm-Message-State: AKaTC03MqejblOcEuuVHthph4Pwl6J0pfUcOEUK+1dKDq9mOvDb2umJu6OilXdwffvONLg== X-Received: by 10.55.201.8 with SMTP id q8mr83212958qki.42.1481646244860; Tue, 13 Dec 2016 08:24:04 -0800 (PST) Received: from [10.50.213.38] ([177.20.152.129]) by smtp.googlemail.com with ESMTPSA id p19sm29360840qte.23.2016.12.13.08.24.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Dec 2016 08:24:04 -0800 (PST) Subject: Re: How I do this? To: freebsd-ports@freebsd.org References: <20161213155952.M21328@i805.com.br> From: =?UTF-8?B?T3RhY8OtbGlv?= Message-ID: <1dab6694-4c40-456d-1498-5c45b298226a@bsd.com.br> Date: Tue, 13 Dec 2016 13:23:51 -0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161213155952.M21328@i805.com.br> Content-Type: text/plain; charset=utf-8; format=flowed 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: Tue, 13 Dec 2016 16:24:06 -0000 Em 13/12/2016 13:10, Nilton Jose Rizzo escreveu: > Hi all > > I need to use a new version of OpenCV 3.1. I > removed the OpenCv 2.4 version and I installed > the new version, but now I need to install other > ports that needs opencv, the ports system tells me > to install a opencv2.4. Is there something to > ports' system accept a new version of OpenCV? > > --- > /************************************************* > **Nilton José Rizzo UFRRJ > **http://www.rizzo.eng.br http://www.ufrrj.br > **http://lattes.cnpq.br/0079460703536198 > **************************************************/ > How you did to install OpenCV 3.1? I'm using OpenCV 3.1 but I installed using a patch from here https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210505 To use others ports that needs OpenCV I compiled from sources using ports collection. For example, ffmpeg needs OpenCV so, I deinstall ffmpeg and OpenCV 2.4, install OpenCV 3.1 and rebuild/install ffmpeg from ports. []'s -Otacilio From owner-freebsd-ports@freebsd.org Tue Dec 13 18:05:38 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 232C9C76630 for ; Tue, 13 Dec 2016 18:05:38 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0D23810F1 for ; Tue, 13 Dec 2016 18:05:38 +0000 (UTC) (envelope-from julian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0C773C7662F; Tue, 13 Dec 2016 18:05: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 0C114C7662E for ; Tue, 13 Dec 2016 18:05:38 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D9CCE10F0; Tue, 13 Dec 2016 18:05:37 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-230-194.lns20.per1.internode.on.net [121.45.230.194]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id uBDI5WV2032796 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 13 Dec 2016 10:05:35 -0800 (PST) (envelope-from julian@freebsd.org) Subject: Re: what is the purpose of the quarterly ports branches? To: George Mitchell , Jason Unovitch References: <7c73fc75-b4d9-063d-02f9-628e06f8d4bd@freebsd.org> <20161207025955.GA21488@Silverstone> <3a97d014-1b8b-7e34-6704-1ee5fd8b97ca@m5p.com> Cc: "ports@FreeBSD.org" From: Julian Elischer Message-ID: Date: Wed, 14 Dec 2016 02:05:26 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <3a97d014-1b8b-7e34-6704-1ee5fd8b97ca@m5p.com> Content-Type: text/plain; charset=windows-1252; 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, 13 Dec 2016 18:05:38 -0000 On 7/12/2016 10:12 PM, George Mitchell wrote: > On 12/06/16 21:59, Jason Unovitch wrote: >> On Mon, Dec 05, 2016 at 10:48:20PM +0000, Ben Woods wrote: >>> On Tue., 6 Dec. 2016 at 4:44 am, Julian Elischer wrote: >>> >>>> they are effectively useless because the results are not archived, and >>>> the quarterly pkg branch actually changes day by day, so making two >>>> machines from the same quarterly branch can give you different >>>> machines (making it useless for paying work) >>>> >>>> not to mention that if you use the quarterly pkg branch you run he >>>> risk of it completely changing if you happen to be unlucky enough to >>>> be doing it across a quarterly boundary. then you end up with a >>>> completely messed up system. (from experience). >>>> >> If you are handling the burden of support for a customer then perhaps >> Poudriere and building internally is the best option. Then if you want >> to stay on an older quarterly because none of what you deploy to >> customers is impacted by security issues you can roll them at your own >> pace. >> >>>> But the big question still remains.. >>>> >>>> What do you think you are solving and why are they changing? shouldn't >>>> a snapshot be stable? >> >> Think releng compared to stable in the src repo rather than >> release/stable. They change in the same fashion to get SA (in the form >> of VuXML) and errata worthy fixes. >> [...] > If only! At least the current base releng does not arbitrarily > disappear every three months. -- George so I think there is a simple partial fix to stop SOME of the worst problems. Name the package quarterly sets the same as the ports branches, Use a symlink to point to them. and keep them around for 6 months, so there are always 2, one of which has pretty much stopped changing. (and provide an EASY way to snarf the lot. currently it's done via an index.html or something that screws it up. > From owner-freebsd-ports@freebsd.org Tue Dec 13 18:08:42 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12EC6C766E7 for ; Tue, 13 Dec 2016 18:08:42 +0000 (UTC) (envelope-from indexbuild@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 01E101233 for ; Tue, 13 Dec 2016 18:08:42 +0000 (UTC) (envelope-from indexbuild@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 013ACC766E6; Tue, 13 Dec 2016 18:08:42 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00D63C766E4 for ; Tue, 13 Dec 2016 18:08:42 +0000 (UTC) (envelope-from indexbuild@FreeBSD.org) Received: from portsindexbuild.ysv.freebsd.org (portsindexbuild.ysv.freebsd.org [IPv6:2001:1900:2254:206a::16:6601]) (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 E99CA1232 for ; Tue, 13 Dec 2016 18:08:41 +0000 (UTC) (envelope-from indexbuild@FreeBSD.org) Received: from portsindexbuild.ysv.freebsd.org ([127.0.1.2]) by portsindexbuild.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id uBDI8fNQ052025 for ; Tue, 13 Dec 2016 18:08:41 GMT (envelope-from indexbuild@portsindexbuild.ysv.freebsd.org) Received: (from indexbuild@localhost) by portsindexbuild.ysv.freebsd.org (8.15.2/8.15.2/Submit) id uBDI8fuN052024 for ports@FreeBSD.org; Tue, 13 Dec 2016 18:08:41 GMT (envelope-from indexbuild) Date: Tue, 13 Dec 2016 18:08:41 GMT From: Ports Index build Message-Id: <201612131808.uBDI8fuN052024@portsindexbuild.ysv.freebsd.org> To: ports@FreeBSD.org Subject: INDEX build failed for 9.x 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, 13 Dec 2016 18:08:42 -0000 INDEX build failed with errors: Generating INDEX-9 - please wait.."/usr/share/mk/bsd.init.mk", line 12: Unknown directive Unknown modifier 'U' "/usr/share/mk/bsd.compiler.mk", line 38: Malformed conditional (${MK_CCACHE_BUILD:Uno} == "yes" && !make(showconfig) && (${CC:M*ccache/world/*} == "" || ${CXX:M*ccache/world/*} == "")) "/usr/share/mk/bsd.compiler.mk", line 107: missing `in' in for X_ in CC $${_empty_var_} XCC X_ "/usr/share/mk/bsd.compiler.mk", line 108: Malformed conditional (${cc} == "CC" || !empty(XCC)) Unknown modifier 'h' Error expanding embedded variable. "Makefile", line 22: warning: "fmake -f "/home/indexbuild/tindex/ports/www/tclhttpd/files/Makefile.lib" -V SHLIB_NAME" returned non-zero status Done. make_index: /home/indexbuild/tindex/ports/emulators/linux-c6: no entry for /home/indexbuild/tindex/ports/www/linux-c6-flashplugin11 Committers on the hook: amdmi3 ehaupt royger sunpoet tijl Most recent SVN update was: Updating '.': U MOVED D www/linux-c6-flashplugin11 D www/linux-c7-flashplugin11 D www/linux-f10-flashplugin11 U www/Makefile U www/linux-c6-flashplugin24/Makefile U www/linux-c6-flashplugin24/distinfo U www/linux-c6-flashplugin24/pkg-descr U www/wordpress/Makefile U www/wordpress/distinfo U www/kanboard/Makefile U www/kanboard/distinfo U www/kanboard/pkg-plist U www/pear-HTML_AJAX/pkg-descr U www/pear-HTML_TagCloud/pkg-descr U www/pear-HTTP/pkg-descr U www/pear-HTTP_Client/pkg-descr U www/pear-HTTP_Download/pkg-descr U www/pear-HTTP_FloodControl/pkg-descr U www/pear-HTTP_Header/pkg-descr U www/pear-HTTP_Request/pkg-descr U www/pear-HTTP_Request2/pkg-descr U www/pear-HTTP_Server/pkg-descr U www/pear-HTTP_Session2/pkg-descr U www/pear-HTTP_Upload/pkg-descr U www/pear-HTTP_WebDAV_Client/pkg-descr U www/pear-HTTP_WebDAV_Server/pkg-descr U www/pear-Services_Amazon/pkg-descr U www/pear-Services_Amazon_S3/pkg-descr U www/pear-Services_Blogging/pkg-descr U www/pear-Services_Compete/pkg-descr U www/pear-Services_Delicious/pkg-descr U www/pear-Services_Digg/pkg-descr U www/pear-Services_Facebook/pkg-descr U www/pear-Services_GeoNames/pkg-descr U www/pear-Services_Google/pkg-descr U www/pear-Services_OpenSearch/pkg-descr U www/pear-Services_ShortURL/pkg-descr U www/pear-Services_TinyURL/pkg-descr U www/pear-Services_TwitPic/pkg-descr U www/pear-Services_W3C_CSSValidator/pkg-descr U www/pear-Services_W3C_HTMLValidator/pkg-descr U www/pear-Services_Yadis/pkg-descr U www/pear-Services_Yahoo/pkg-descr U www/pear-Services_urlTea/pkg-descr U www/pear-Structures_DataGrid_Renderer_Flexy/pkg-descr U www/pear-Structures_DataGrid_Renderer_Pager/pkg-descr U www/pear-Structures_DataGrid_Renderer_Smarty/pkg-descr U www/pear-Text_Wiki/pkg-descr U www/pear-UDDI/pkg-descr U www/pear-XML_GRDDL/pkg-descr U databases/rocksdb/Makefile U databases/rocksdb/distinfo A databases/rocksdb/files A databases/rocksdb/files/patch-utilities-column_aware_encoding_exp.cc A databases/rocksdb/files/patch-utilities-persistent_cache-hash_table_bench.cc A databases/rocksdb/files/patch-utilities-persistent_cache-persistent_cache_bench.cc U databases/rocksdb/pkg-plist U databases/mysqldumper/Makefile U databases/mydumper/Makefile U databases/mydumper/distinfo U databases/mydumper/pkg-descr U databases/pear-DB/pkg-descr U databases/pear-DBA/pkg-descr U databases/pear-DBA_Relational/pkg-descr U databases/pear-DB_DataObject/pkg-descr U databases/pear-DB_DataObject_FormBuilder/pkg-descr U databases/pear-DB_Pager/pkg-descr U databases/pear-DB_QueryTool/pkg-descr U databases/pear-DB_Sqlite_Tools/pkg-descr U databases/pear-DB_Table/pkg-descr U databases/pear-DB_ldap/pkg-descr U databases/pear-DB_ldap2/pkg-descr U databases/pear-MDB/pkg-descr U databases/pear-MDB2/pkg-descr U databases/pear-MDB2_Driver_mysql/pkg-descr U databases/pear-MDB2_Driver_mysqli/pkg-descr U databases/pear-MDB2_Driver_pgsql/pkg-descr U databases/pear-MDB2_Schema/pkg-descr U databases/pear-MDB_QueryTool/pkg-descr U databases/pear-Structures_DataGrid_DataSource_Array/pkg-descr U databases/pear-Structures_DataGrid_DataSource_CSV/pkg-descr U databases/pear-Structures_DataGrid_DataSource_DB/pkg-descr U databases/pear-Structures_DataGrid_DataSource_DBQuery/pkg-descr U databases/pear-Structures_DataGrid_DataSource_DBTable/pkg-descr U databases/pear-Structures_DataGrid_DataSource_DataObject/pkg-descr U databases/pear-Structures_DataGrid_DataSource_MDB2/pkg-descr U databases/pear-Structures_DataGrid_DataSource_PDO/pkg-descr U databases/pear-XML_Query2XML/pkg-descr U security/p5-Authen-Radius/Makefile U security/p5-Authen-Radius/distinfo U security/p5-Authen-Radius/pkg-plist U security/pear-Auth/pkg-descr U security/pear-Auth_HTTP/pkg-descr U security/pear-Auth_PrefManager/pkg-descr U security/pear-Auth_SASL/pkg-descr U security/pear-Crypt_Blowfish/pkg-descr U security/pear-Crypt_CHAP/pkg-descr U security/pear-Crypt_DiffieHellman/pkg-descr U security/pear-Crypt_GPG/pkg-descr U security/pear-Crypt_HMAC2/pkg-descr U security/pear-Crypt_MicroID/pkg-descr U security/pear-Crypt_RC4/pkg-descr U security/pear-Crypt_RSA/pkg-descr U security/pear-Crypt_XXTEA/pkg-descr U security/pear-File_HtAccess/pkg-descr U security/pear-File_Passwd/pkg-descr U security/pear-File_SMBPasswd/pkg-descr U security/pear-HTML_Crypt/pkg-descr U security/pear-LiveUser/pkg-descr U security/pear-LiveUser_Admin/pkg-descr U security/pear-Net_Portscan/pkg-descr U security/pear-Text_Password/pkg-descr U textproc/rubygem-autoprefixer-rails/Makefile U textproc/rubygem-autoprefixer-rails/distinfo U textproc/sk-mythes/Makefile U textproc/sk-mythes/distinfo U textproc/pear-File_Fortune/pkg-descr U textproc/pear-File_MARC/pkg-descr U textproc/pear-Numbers_Roman/pkg-descr U textproc/pear-Numbers_Words/pkg-descr U textproc/pear-Spreadsheet_Excel_Writer/pkg-descr U textproc/pear-Structures_DataGrid_DataSource_RSS/pkg-descr U textproc/pear-Structures_DataGrid_DataSource_XML/pkg-descr U textproc/pear-Structures_DataGrid_Renderer_CSV/pkg-descr U textproc/pear-Structures_DataGrid_Renderer_XLS/pkg-descr U textproc/pear-Structures_DataGrid_Renderer_XML/pkg-descr U textproc/pear-Text_Highlighter/pkg-descr U textproc/pear-Validate_ISPN/pkg-descr U textproc/pear-XML_Beautifier/pkg-descr U textproc/pear-XML_DTD/pkg-descr U textproc/pear-XML_Feed_Parser/pkg-descr U textproc/pear-XML_HTMLSax/pkg-descr U textproc/pear-XML_Wddx/pkg-descr U misc/p5-Geo-Coder-OpenCage/Makefile U misc/p5-Geo-Coder-OpenCage/distinfo U misc/pear-Services_Weather/pkg-descr U misc/pear-Text_Figlet/pkg-descr U sysutils/p5-Tail-Stat/Makefile U sysutils/p5-Tail-Stat/distinfo U sysutils/s6/Makefile U sysutils/s6/distinfo U sysutils/s6/pkg-plist U sysutils/pear-Cache/pkg-descr U sysutils/pear-Cache_Lite/pkg-descr U sysutils/pear-File/pkg-descr U sysutils/pear-File_Find/pkg-descr U sysutils/pear-File_Fstab/pkg-descr U sysutils/pear-File_Gettext/pkg-descr U sysutils/pear-I18Nv2/pkg-descr U sysutils/pear-Log/pkg-descr U sysutils/pear-Translation2/pkg-descr U devel/p5-SVN-S4/Makefile U devel/p5-SVN-S4/distinfo U devel/p5-SVN-S4/pkg-plist U devel/p5-Connector/Makefile U devel/p5-Connector/distinfo U devel/p5-Connector/pkg-plist U devel/skalibs/Makefile U devel/skalibs/distinfo U devel/skalibs/pkg-plist D devel/tig/files U devel/tig/Makefile U devel/tig/distinfo U devel/tig/pkg-descr U devel/p5-Parse-Yapp/Makefile U devel/pear-Config/pkg-descr U devel/pear-Console_Color/pkg-descr U devel/pear-Console_CommandLine/pkg-descr U devel/pear-Console_Getargs/pkg-descr U devel/pear-Console_Table/pkg-descr U devel/pear-Date/pkg-descr U devel/pear-Date_Holidays/pkg-descr U devel/pear-Date_Holidays_Austria/pkg-descr U devel/pear-Date_Holidays_Brazil/pkg-descr U devel/pear-Date_Holidays_Denmark/pkg-descr U devel/pear-Date_Holidays_Discordian/pkg-descr U devel/pear-Date_Holidays_EnglandWales/pkg-descr U devel/pear-Date_Holidays_Germany/pkg-descr U devel/pear-Date_Holidays_Iceland/pkg-descr U devel/pear-Date_Holidays_Ireland/pkg-descr U devel/pear-Date_Holidays_Italy/pkg-descr U devel/pear-Date_Holidays_Japan/pkg-descr U devel/pear-Date_Holidays_Netherlands/pkg-descr U devel/pear-Date_Holidays_Norway/pkg-descr U devel/pear-Date_Holidays_PHPdotNet/pkg-descr U devel/pear-Date_Holidays_Romania/pkg-descr U devel/pear-Date_Holidays_Slovenia/pkg-descr U devel/pear-Date_Holidays_Sweden/pkg-descr U devel/pear-Date_Holidays_UNO/pkg-descr U devel/pear-Date_Holidays_USA/pkg-descr U devel/pear-Date_Holidays_Ukraine/pkg-descr U devel/pear-Event_Dispatcher/pkg-descr U devel/pear-FSM/pkg-descr U devel/pear-HTML_BBCodeParser/pkg-descr U devel/pear-HTML_CSS/pkg-descr U devel/pear-HTML_Common/pkg-descr U devel/pear-HTML_Common2/pkg-descr U devel/pear-HTML_Form/pkg-descr U devel/pear-HTML_Javascript/pkg-descr U devel/pear-HTML_Page2/pkg-descr U devel/pear-HTML_QuickForm/pkg-descr U devel/pear-HTML_QuickForm2/pkg-descr U devel/pear-HTML_QuickForm_Controller/pkg-descr U devel/pear-HTML_QuickForm_Livesearch/pkg-descr U devel/pear-HTML_QuickForm_Renderer_Tableless/pkg-descr U devel/pear-HTML_QuickForm_SelectFilter/pkg-descr U devel/pear-HTML_QuickForm_advmultiselect/pkg-descr U devel/pear-HTML_Select/pkg-descr U devel/pear-HTML_Table/pkg-descr U devel/pear-HTML_Template_Flexy/pkg-descr U devel/pear-HTML_Template_IT/pkg-descr U devel/pear-HTML_Template_PHPLIB/pkg-descr U devel/pear-HTML_TreeMenu/pkg-descr U devel/pear-I18N/pkg-descr U devel/pear-Math_Fraction/pkg-descr U devel/pear-Net_Gearman/pkg-descr U devel/pear-OLE/pkg-descr U devel/pear-PEAR_Info/pkg-descr U devel/pear-PEAR_PackageFileManager/pkg-descr U devel/pear-PEAR_PackageFileManager2/pkg-descr U devel/pear-PEAR_PackageFileManager_Plugins/pkg-descr U devel/pear-PHPDoc/pkg-descr U devel/pear-PHP_ArrayOf/pkg-descr U devel/pear-PHP_Beautifier/pkg-descr U devel/pear-PHP_CodeSniffer/pkg-descr U devel/pear-PHP_Compat/pkg-descr U devel/pear-PHP_CompatInfo/pkg-descr U devel/pear-PHP_Parser/pkg-descr U devel/pear-PHP_ParserGenerator/pkg-descr U devel/pear-PHP_UML/pkg-descr U devel/pear-Pager/pkg-descr U devel/pear-PhpDocumentor/pkg-descr U devel/pear-Structure_LinkedList/pkg-descr U devel/pear-Structures_DataGrid/pkg-descr U devel/pear-Structures_DataGrid_Renderer_Console/pkg-descr U devel/pear-Structures_DataGrid_Renderer_HTMLSortForm/pkg-descr U devel/pear-Structures_DataGrid_Renderer_HTMLTable/pkg-descr U devel/pear-Structures_DataGrid_Renderer_XUL/pkg-descr U devel/pear-System_Command/pkg-descr U devel/pear-Testing_Selenium/pkg-descr U devel/pear-Text_Diff/pkg-descr U devel/pear-VFS/pkg-descr U devel/pear-Validate/pkg-descr U devel/pear-Validate_AU/pkg-descr U devel/pear-Validate_Finance/pkg-descr U devel/pear-Validate_Finance_CreditCard/pkg-descr U devel/pear-Validate_US/pkg-descr U devel/pear-Var_Dump/pkg-descr U devel/pear-VersionControl_Git/pkg-descr U devel/pear-VersionControl_SVN/pkg-descr U devel/pear-XML_NITF/pkg-descr U devel/pear-XML_Parser/pkg-descr U devel/pear-XML_SVG/pkg-descr U devel/pear-XML_Serializer/pkg-descr U devel/pear-XML_Transformer/pkg-descr U devel/pear-XML_Util/pkg-descr U devel/pear-codegen/pkg-descr U german/mythes/Makefile U german/mythes/distinfo U german/wordpress/Makefile U german/wordpress/distinfo U x11-fonts/Makefile A x11-fonts/emojione-color-font-ttf A x11-fonts/emojione-color-font-ttf/Makefile A x11-fonts/emojione-color-font-ttf/distinfo A x11-fonts/emojione-color-font-ttf/pkg-descr U net/3proxy/Makefile U net/3proxy/distinfo U net/py-netifaces/Makefile U net/py-netifaces/distinfo U net/self-service-password/Makefile U net/self-service-password/distinfo U net/self-service-password/pkg-plist U net/pear-Auth_RADIUS/pkg-descr U net/pear-File_Bittorrent2/pkg-descr U net/pear-Net_CDDB/pkg-descr U net/pear-Net_CheckIP/pkg-descr U net/pear-Net_DIME/pkg-descr U net/pear-Net_DNSBL/pkg-descr U net/pear-Net_Dict/pkg-descr U net/pear-Net_Finger/pkg-descr U net/pear-Net_Geo/pkg-descr U net/pear-Net_GeoIP/pkg-descr U net/pear-Net_IDNA/pkg-descr U net/pear-Net_IPv4/pkg-descr U net/pear-Net_IPv6/pkg-descr U net/pear-Net_Ident/pkg-descr U net/pear-Net_LDAP/pkg-descr U net/pear-Net_LDAP2/pkg-descr U net/pear-Net_MAC/pkg-descr U net/pear-Net_NNTP/pkg-descr U net/pear-Net_Nmap/pkg-descr U net/pear-Net_POP3/pkg-descr U net/pear-Net_Ping/pkg-descr U net/pear-Net_SMS/pkg-descr U net/pear-Net_SMTP/pkg-descr U net/pear-Net_Server/pkg-descr U net/pear-Net_Socket/pkg-descr U net/pear-Net_Traceroute/pkg-descr U net/pear-Net_URL/pkg-descr U net/pear-Net_URL2/pkg-descr U net/pear-Net_URL_Mapper/pkg-descr U net/pear-Net_UserAgent_Detect/pkg-descr U net/pear-Net_UserAgent_Mobile/pkg-descr U net/pear-Net_Vpopmaild/pkg-descr U net/pear-Net_Whois/pkg-descr U net/pear-SOAP/pkg-descr U net/pear-Services_Pingback/pkg-descr U net/pear-Services_Twitter/pkg-descr U net/pear-URI_Template/pkg-descr U net/pear-XML_RPC/pkg-descr U net/pear-XML_RPC2/pkg-descr U chinese/wordpress-zh_TW/Makefile U chinese/wordpress-zh_TW/distinfo U japanese/wordpress/Makefile U japanese/wordpress/distinfo U games/pinball/Makefile A games/pinball/files/patch-base_Config.cpp U games/pear-Games_Chess/pkg-descr D x11/xdotool/pkg-plist U x11/xdotool/Makefile U x11/xdotool/distinfo U UPDATING U lang/execline/Makefile U lang/execline/distinfo U lang/execline/pkg-plist U mail/mutt/Makefile U mail/mutt/distinfo D mail/mutt/files/patch-gpgme180 U mail/pear-Contact_Vcard_Build/pkg-descr U mail/pear-Contact_Vcard_Parse/pkg-descr U mail/pear-MIME_Type/pkg-descr U mail/pear-Mail/pkg-descr U mail/pear-Mail_Mbox/pkg-descr U mail/pear-Mail_Mime/pkg-descr U mail/pear-Mail_Queue/pkg-descr U mail/pear-Mail_mimeDecode/pkg-descr U mail/pear-Net_Cyrus/pkg-descr U mail/pear-Net_IMAP/pkg-descr U mail/pear-Net_LMTP/pkg-descr U emulators/xen-kernel/Makefile A emulators/xen-kernel/files/xsa200-4.7.patch U archivers/pear-File_Archive/pkg-descr U archivers/pear-PHP_Archive/pkg-descr U audio/pear-Text_Spell_Audio/pkg-descr U benchmarks/pear-Benchmark/pkg-descr U converters/pear-Services_JSON/pkg-descr U dns/pear-File_DNS/pkg-descr U dns/pear-Net_DNS/pkg-descr U dns/pear-Net_DNS2/pkg-descr U finance/pear_Payment_DTA/pkg-descr U ftp/pear-Net_FTP/pkg-descr U graphics/pear-Image_3D/pkg-descr U graphics/pear-Image_Barcode/pkg-descr U graphics/pear-Image_Barcode2/pkg-descr U graphics/pear-Image_Canvas/pkg-descr U graphics/pear-Image_Color/pkg-descr U graphics/pear-Image_Graph/pkg-descr U graphics/pear-Image_GraphViz/pkg-descr U graphics/pear-Image_Transform/pkg-descr U irc/pear-Net_SmartIRC/pkg-descr U math/pear-Math_BigInteger/pkg-descr U math/pear-Math_Combinatorics/pkg-descr U print/pear-File_PDF/pkg-descr U shells/pear-PHP_Shell/pkg-descr Updated to revision 428522. From owner-freebsd-ports@freebsd.org Tue Dec 13 18:21:23 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E781BC76C3D for ; Tue, 13 Dec 2016 18:21:23 +0000 (UTC) (envelope-from bounce+389dfa.8c621-ports=freebsd.org@mail.andela.co) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id CCA111CE9 for ; Tue, 13 Dec 2016 18:21:23 +0000 (UTC) (envelope-from bounce+389dfa.8c621-ports=freebsd.org@mail.andela.co) Received: by mailman.ysv.freebsd.org (Postfix) id C8F45C76C3C; Tue, 13 Dec 2016 18:21:23 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8917C76C3B for ; Tue, 13 Dec 2016 18:21:23 +0000 (UTC) (envelope-from bounce+389dfa.8c621-ports=freebsd.org@mail.andela.co) Received: from z6.mailgun.us (z6.mailgun.us [104.130.96.6]) (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 9AE561CE7 for ; Tue, 13 Dec 2016 18:21:23 +0000 (UTC) (envelope-from bounce+389dfa.8c621-ports=freebsd.org@mail.andela.co) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mail.andela.co; q=dns/txt; s=smtp; t=1481653282; h=Content-Transfer-Encoding: Content-Type: Mime-Version: Date: Subject: To: From: Message-Id: List-Unsubscribe: Sender; bh=J0toJcfmXFiXVZ/eSvsp1pyygtUsOWtfUPkEGR03Pto=; b=TCubZMwpp6ZGT8OU1JQsWONbdVAvo5BsaDhWcN798ka0lhnQ+2Uk1ccYkbcS3gR3zaekynbI qEDrgydj4G+dyriDszPYn7sKK53ZuiOi8/mhaQLOMkWnwz46ncKBjpzUUgk0wkIu5tVPkX4m 8WuSVP6qcwVHzQbD0E0zJZdDtRU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=mail.andela.co; s=smtp; q=dns; h=Sender: List-Unsubscribe: Message-Id: From: To: Subject: Date: Mime-Version: Content-Type: Content-Transfer-Encoding; b=ExpmfjcdOMsAbjRDOUtpLtb2lnQiUVrzczrnUGbytGUGTk9HY7qXA9nVKEdLicvu9+pvbI Jgsvgo1Nh0UExkuqRz2M3PfuicrA6AP+yLcU3tESXQwOB5CB+wXXPMMBOIhqm4bWm1NCsqXc yb2oOdgaPChd51obpitx3ZhoC5Q78= Sender: noreplay=mgsecure.com@mail.andela.co X-Mailgun-Sending-Ip: 104.130.96.6 X-Mailgun-Sid: WyJmODkwMCIsICJwb3J0c0BmcmVlYnNkLm9yZyIsICI4YzYyMSJd Received: from WIN-1V1VSSCR1DR (ec2-54-201-127-80.us-west-2.compute.amazonaws.com [54.201.127.80]) by mxa.mailgun.org with ESMTP id 58503a04.7ff02c4f43b0-smtp-out-n03; Tue, 13 Dec 2016 18:12:20 -0000 (UTC) Message-Id: <038c02ae-42717-78ce7585040741@win-1v1vsscr1dr> From: "Important Notice" To: ports@freebsd.org Subject: Update Your Account Date: Tue, 13 Dec 2016 18:11:15 +0000 X-Priority: 3 MIME-Version: 1.0 Content-Type: text/plain; charset="ascii" 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, 13 Dec 2016 18:21:24 -0000 From owner-freebsd-ports@freebsd.org Tue Dec 13 20:33:08 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1218FC756D0 for ; Tue, 13 Dec 2016 20:33:08 +0000 (UTC) (envelope-from jhs@berklix.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 F1B29D3 for ; Tue, 13 Dec 2016 20:33:07 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id F106DC756CF; Tue, 13 Dec 2016 20:33:07 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0AB3C756CE for ; Tue, 13 Dec 2016 20:33:07 +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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 91393D2; Tue, 13 Dec 2016 20:33:06 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p5B226212.dip0.t-ipconnect.de [91.34.98.18]) (authenticated bits=128) by land.berklix.org (8.15.2/8.15.2) with ESMTPA id uBDKWwOG002067; Tue, 13 Dec 2016 20:32:59 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 uBDKWrdB003240; Tue, 13 Dec 2016 21:32:53 +0100 (CET) (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 uBDKWaVK017178; Tue, 13 Dec 2016 21:32:48 +0100 (CET) (envelope-from jhs@berklix.com) Message-Id: <201612132032.uBDKWaVK017178@fire.js.berklix.net> To: ports@FreeBSD.org Subject: No port should need root for make fetch From: "Julian H. Stacey" Organization: http://berklix.eu BSD Linux Unix Consultants, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ Date: Tue, 13 Dec 2016 21:32:36 +0100 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, 13 Dec 2016 20:33:08 -0000 Hi ports@ IMO No port should need root for cd /usr/ports; make -i fetch The first one that broke for me was databases/mysql-q4m (OK might be others before, but I have DUDS = arabic biology chinese hebrew hungarian japanese korean polish portuguese russian ukrainian vietnamese games demime majordomo acroreadwrapper acroread9 chimera dosbox emil firefox freerdp gimp-app gv libcue mp3splt-gtk nut opera ripit vlc xorg xsane ) (MAINTAINER CC'd) but there's more ports beyond, usually because some ports also go berserk & install, or mabe install dependents. Cheers, Julian -- Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable. http://berklix.eu/brexit/#stolen_votes From owner-freebsd-ports@freebsd.org Tue Dec 13 20:45:43 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA80DC75E87 for ; Tue, 13 Dec 2016 20:45:43 +0000 (UTC) (envelope-from ken@f-leads.com) Received: from IND01-BO1-obe.outbound.protection.outlook.com (mail-bo1ind01on0133.outbound.protection.outlook.com [104.47.101.133]) (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 E0BA6C4F for ; Tue, 13 Dec 2016 20:45:42 +0000 (UTC) (envelope-from ken@f-leads.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT2437315.onmicrosoft.com; s=selector1-fleads-com0c; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=crWkoD+9dW347v0ANiRnslKmBYaF0zYwtL9ZTnhwuN4=; b=QaEi8imkUCdVfs1t0loW+BE5NR+yG0COPxjY1Sy2TbYFLrvsb3fpVpdAYJ7SPZxFM0ys3rE/5wa+pTBb7ut1CsICV1sX7tKS6s/pi5+RudA4MhN0pyJ5asjNesm5NaSYaF73Fzu+JcxZvIsoY3FzOjDiMFXvt6isf2uZkq6D5UE= Received: from PN1PR01MB0830.INDPRD01.PROD.OUTLOOK.COM (10.174.146.140) by PN1PR01MB0832.INDPRD01.PROD.OUTLOOK.COM (10.174.146.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.747.13; Tue, 13 Dec 2016 19:11:05 +0000 Received: from PN1PR01MB0830.INDPRD01.PROD.OUTLOOK.COM ([10.174.146.140]) by PN1PR01MB0830.INDPRD01.PROD.OUTLOOK.COM ([10.174.146.140]) with mapi id 15.01.0747.023; Tue, 13 Dec 2016 19:11:06 +0000 From: Ken Harvey To: "freebsd-ports@freebsd.org" Subject: Marketing Automation Thread-Topic: Marketing Automation Thread-Index: AdJVbFxTuvyUmXJ3TlSv+W3bnUWiaQ== Date: Tue, 13 Dec 2016 19:11:06 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=ken@f-leads.com; x-originating-ip: [49.207.54.173] x-ms-office365-filtering-correlation-id: 2fab1764-580f-424a-3242-08d4238bc9e2 x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:PN1PR01MB0832; x-microsoft-exchange-diagnostics: 1; PN1PR01MB0832; 7:93xPTu4QiYT5BnFyKOQjXOb4ylT5pza28c4/fkc6equ+Pm73EHYAzKAMzUPq0EQyochA+fo96Iv6esQMCohk+ry8GDjr0HUxMtvkO/P0tfACaDLH1XD5Y+vC52zrPiA6bgnC94x5f/uceCWUyb/gjteJBvJplNpjLfmSfoDrdiFGCEixsUgPmDuNmqTm1SQNbyGPI4rPnjg7IsPK++3g2dWhL0MLgKTaXdhdEnyutZ9o6UjRiKaKU0kJEC7mUao5mNFc3QAtAxdlBohw7EvksWlgtO6zKQBPWgkVK19t6GWDFCQUAGNhkCbkyq0OBH8WCZPQ7I8h0bKWPdecQLDQFjVJk13ngUeH836UXzSKdFYrJFhBPmNnolGht6h/idFbiVqSiakv9EeeXW7CW9oXxk2gkNIOC4pUgWlGZXjHd8VS5LAb+gEWpa7m8IwxnIwTM6cMiRlaz1+5aZHrHxQ/dw== x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(21748063052155); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123562025)(20161123564025)(20161123560025)(20161123555025)(2016111802025)(6072148)(6043046); SRVR:PN1PR01MB0832; BCL:0; PCL:0; RULEID:; SRVR:PN1PR01MB0832; x-forefront-prvs: 01559F388D x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(39410400002)(39860400002)(39850400002)(39450400003)(39840400002)(152014003)(189002)(199003)(50986999)(54356999)(7736002)(110136003)(7696004)(101416001)(5630700001)(7116003)(5660300001)(74316002)(38730400001)(6916009)(2501003)(189998001)(2351001)(106356001)(105586002)(5640700002)(6436002)(6506006)(6116002)(790700001)(3846002)(102836003)(2900100001)(66066001)(3660700001)(92566002)(33656002)(3280700002)(77096006)(97736004)(107886002)(9326002)(81166006)(122556002)(81156014)(9686002)(3480700004)(8676002)(8936002)(9476002)(2906002)(9406002)(68736007)(450100001)(86362001)(62570200001); DIR:OUT; SFP:1102; SCL:1; SRVR:PN1PR01MB0832; H:PN1PR01MB0830.INDPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: f-leads.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: f-leads.com X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Dec 2016 19:11:06.0082 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 10d42f6f-1cc3-4240-bc4e-ddc259a1e015 X-MS-Exchange-Transport-CrossTenantHeadersStamped: PN1PR01MB0832 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: Tue, 13 Dec 2016 20:45:43 -0000 Hi, Would you be interested in an email lead list of different Sales and Market= ing Automation software users? Would it help to acquire business informatio= n along with contact details of key profiles and decision makers? Users Includes: > Salesforce Users > Marketo Users > ExactTarget Users > Eloqua Users > Silverpop Users Title includes: > CMO > VP/Director Marketing > VP/Director Sales > Marketing Manager The list comes with complete contact information like Contact name, Email a= ddress, Title, Company name, Phone number, Mailing address, etc. I'd be happy to send over few sample records on your request, and set up a = time to discuss in detail. If there is someone else in your organization that I need to speak with, I'= d be grateful if you would forward this email to the appropriate contact an= d help me with the introduction. Have a great day! Regards, ] Ken Harvey / INF Solutions / 302-250-4336 If you don't wish to receive emails from us reply back with "Unsubscribe". From owner-freebsd-ports@freebsd.org Tue Dec 13 21:09:21 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B778AC7672B for ; Tue, 13 Dec 2016 21:09:21 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 17D2ED1 for ; Tue, 13 Dec 2016 21:09:20 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([77.181.21.39]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LjqLx-1csj2q4BEP-00bq3I for ; Tue, 13 Dec 2016 22:09:18 +0100 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 69DB423CF5A for ; Tue, 13 Dec 2016 22:09:15 +0100 (CET) Subject: Re: No port should need root for make fetch To: null References: <201612132032.uBDKWaVK017178@fire.js.berklix.net> From: Matthias Andree Message-ID: Date: Tue, 13 Dec 2016 22:09:14 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <201612132032.uBDKWaVK017178@fire.js.berklix.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:FNzHUplxEfF4vUvuYeU82OsyjNyQPhtVejVTwTJgpCblzOwigBR aby9hkAghMzVtxvkVAoN5lmFN4lavoTmcCvyHgfBYuxuUcppp1c4wvNMNb0AcxLwLQVlECs hJz1hbalvMsxTPCcunP7V5EQ7QvMp2uLP0j/y5JGhosgk4BinZqN6uJcDCxWTXpj9QSWxxP JRLqQZzLXVlPlESzpmepw== X-UI-Out-Filterresults: notjunk:1;V01:K0:ya48GU0x20c=:h1xP+dCyoaJd1UpNIShQ54 DmK6mHd5dirNBXkDeDD/1zAY6UjalHSLqvyc9U6Tvvjbzbg2x27BT8jK99yPKqamUP90oILot BukDNc30LcyBIDY8o1EGJpzKOwd0A3ynWuhORtEuWVisgUJ/kGJO4FP5mpkvTctrBzllsSexo NHQaKvxvwxKvaCokfDkr8BL0+4zJfS4IlyssF8gPigbF5ZBVEtZpvj9dqnbBz6ZvDs2232UEp 243YfTCAkWVkifXrJUuQh0Rgpt4n49qCdly7OJHZ2miZoscTMhToLvizYV/5U9pWXtXBDeaRR fOpuTX+G8RhjHQo1NbWZhLvW7iklSqffIjTGSTacTD29nbxvD96e1F/IwsESJVq+L2l/B0KMH xjvRHevfwunIlS6b9adIi994v2ONUq006AxKRlF7AlOZJKs2MR1SNc+ccg9p4Rw+Th9TQOnv0 jSwEXZvLj2hZLHfO61zShnqYI7MOPRZJ/i5eTzaQaIvBaneyB0GpO+pV0SrcnYXg8EoTzXqns LF527fLZc1Tkz2zI9Hqtie5Awye5JiL6FCW/grt0tuET/WjVcZPIsGaBlkZRelHSHmWccievM 8VxSiHIKCBz9Yr6+t17NO69cnWeUe9oJDy8tSgShIP22MWF6JWubZy4g7X3F36aSbLj561Cwb LgyVYwVWDaYC9c32jIBG7n/iImmgtW0yP3DcwXWzNDb5IVdM8oI5miNDzQ/WEnNlUyeBqvB8j BNQUWE3mRiruZzEbmFBVcoA47vL4J3EtOKEVzlAV/+orEvj1kLBcSuw38qsBb8WxWCcWKt1QX kLil26p 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, 13 Dec 2016 21:09:21 -0000 Am 13.12.2016 um 21:32 schrieb Julian H. Stacey: > Hi ports@ > IMO No port should need root for > cd /usr/ports; make -i fetch > The first one that broke for me was databases/mysql-q4m > (OK might be others before, but I have DUDS = > arabic biology chinese hebrew hungarian japanese korean > polish portuguese russian ukrainian vietnamese games demime > majordomo acroreadwrapper acroread9 chimera dosbox emil > firefox freerdp gimp-app gv libcue mp3splt-gtk nut opera > ripit vlc xorg xsane > ) > (MAINTAINER CC'd) but there's more ports beyond, usually because > some ports also go berserk & install, or mabe install dependents. Julian, How is that a problem of "some" ports? All ports require root for "make fetch" because the normal distfiles/ directory is underneath /usr/ports/ and thus only writable by root. Make the /usr/ports/distfiles/ directory writable to a certain group of users, make the DIRECTORY setgid (chmod g+s ...), add the users to that group, and you're set, alternatively, redirect that storage to a user-writable directory by setting the DISTDIR environment variable (this can happen on the make command-line, too). > # DISTDIR - Where to search for and store copies of original sources > # Default: ${PORTSDIR}/distfiles (source: /usr/ports/Mk/bsd.port.mk) HTH Matthias From owner-freebsd-ports@freebsd.org Tue Dec 13 21:14:15 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B8FCC76969 for ; Tue, 13 Dec 2016 21:14:15 +0000 (UTC) (envelope-from indexbuild@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 29F3C843 for ; Tue, 13 Dec 2016 21:14:15 +0000 (UTC) (envelope-from indexbuild@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 25F4FC76967; Tue, 13 Dec 2016 21:14:15 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25A27C76966 for ; Tue, 13 Dec 2016 21:14:15 +0000 (UTC) (envelope-from indexbuild@FreeBSD.org) Received: from portsindexbuild.ysv.freebsd.org (portsindexbuild.ysv.freebsd.org [IPv6:2001:1900:2254:206a::16:6601]) (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 0244D842 for ; Tue, 13 Dec 2016 21:14:15 +0000 (UTC) (envelope-from indexbuild@FreeBSD.org) Received: from portsindexbuild.ysv.freebsd.org ([127.0.1.2]) by portsindexbuild.ysv.freebsd.org (8.15.2/8.15.2) with ESMTP id uBDLEE0e042850 for ; Tue, 13 Dec 2016 21:14:14 GMT (envelope-from indexbuild@portsindexbuild.ysv.freebsd.org) Received: (from indexbuild@localhost) by portsindexbuild.ysv.freebsd.org (8.15.2/8.15.2/Submit) id uBDLEEux042848 for ports@FreeBSD.org; Tue, 13 Dec 2016 21:14:14 GMT (envelope-from indexbuild) Date: Tue, 13 Dec 2016 21:14:14 GMT From: Ports Index build Message-Id: <201612132114.uBDLEEux042848@portsindexbuild.ysv.freebsd.org> To: ports@FreeBSD.org Subject: INDEX now builds successfully on 9.x 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, 13 Dec 2016 21:14:15 -0000 From owner-freebsd-ports@freebsd.org Tue Dec 13 21:35:52 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13B4AC76068 for ; Tue, 13 Dec 2016 21:35:52 +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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A87D31693 for ; Tue, 13 Dec 2016 21:35:51 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p5B226212.dip0.t-ipconnect.de [91.34.98.18]) (authenticated bits=128) by land.berklix.org (8.15.2/8.15.2) with ESMTPA id uBDLZmmj004227; Tue, 13 Dec 2016 21:35:49 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 uBDLZh6c003500; Tue, 13 Dec 2016 22:35:43 +0100 (CET) (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 uBDLZPVp017655; Tue, 13 Dec 2016 22:35:37 +0100 (CET) (envelope-from jhs@berklix.com) Message-Id: <201612132135.uBDLZPVp017655@fire.js.berklix.net> To: Matthias Andree cc: null Subject: Re: No port should need root for make fetch 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, 13 Dec 2016 22:09:14 +0100." Date: Tue, 13 Dec 2016 22:35:25 +0100 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, 13 Dec 2016 21:35:52 -0000 Hi, Reference: > From: Matthias Andree > Date: Tue, 13 Dec 2016 22:09:14 +0100 Matthias Andree wrote: > Am 13.12.2016 um 21:32 schrieb Julian H. Stacey: > > Hi ports@ > > IMO No port should need root for > > cd /usr/ports; make -i fetch > > The first one that broke for me was databases/mysql-q4m > > (OK might be others before, but I have DUDS = > > arabic biology chinese hebrew hungarian japanese korean > > polish portuguese russian ukrainian vietnamese games demime > > majordomo acroreadwrapper acroread9 chimera dosbox emil > > firefox freerdp gimp-app gv libcue mp3splt-gtk nut opera > > ripit vlc xorg xsane > > ) > > (MAINTAINER CC'd) but there's more ports beyond, usually because > > some ports also go berserk & install, or mabe install dependents. > > Julian, > > How is that a problem of "some" ports? All ports require root for "make > fetch" No they dont. > because the normal distfiles/ directory is underneath /usr/ports/ > and thus only writable by root. No its not cd /usr/ports/distfiles ; ls -la | head total 73937104 drwxr-xr-x 406 jhs staff 893440 Dec 13 22:29 ./ drwxr-xr-x 23 jhs staff 1536 Dec 1 00:22 ../ pwd /.amd_mnt/fire/0s4/ftp/pub/FreeBSD/dists/current > Make the /usr/ports/distfiles/ directory > writable to a certain group of users, make the DIRECTORY setgid (chmod > g+s ...), add the users to that group, and you're set, alternatively, > redirect that storage to a user-writable directory by setting the > DISTDIR environment variable (this can happen on the make command-line, > too). > > > # DISTDIR - Where to search for and store copies of original sources > > # Default: ${PORTSDIR}/distfiles > (source: /usr/ports/Mk/bsd.port.mk) Thanks for the well intentioned & good advice Matthias, But some few ports are truly Badly Behaved with make fetch. Cheers, Julian -- Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable. http://berklix.eu/brexit/#stolen_votes From owner-freebsd-ports@freebsd.org Tue Dec 13 22:01:25 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C342BC764C4 for ; Tue, 13 Dec 2016 22:01:25 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 267341EC for ; Tue, 13 Dec 2016 22:01:24 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([77.181.21.39]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Lcjgd-1d0wBf4331-00k779 for ; Tue, 13 Dec 2016 23:01:17 +0100 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 2357523CF5A for ; Tue, 13 Dec 2016 23:01:14 +0100 (CET) Subject: Re: No port should need root for make fetch To: null References: <201612132135.uBDLZPVp017655@fire.js.berklix.net> From: Matthias Andree Message-ID: <96f44b17-b5a3-d24e-dee4-935d55a70019@gmx.de> Date: Tue, 13 Dec 2016 23:01:13 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <201612132135.uBDLZPVp017655@fire.js.berklix.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K0:u4zBnc5uQQsay8HeggxtGppamurRCnbxR6QxFgBGxJN4zAs71G6 VCHSxhPzUT0XqI8vhub72dt5caS/TlVpQaVWCA1BIXtlc3dfszU2valo6649qtGnzX0qivg rfpZhZzVnJv7nDORy0Wwe/7hASAQZCZCicVAc+TFbawtCGcBnNtUXibevIscJenOrMeB4dm pc+zOwbpqt09+iqIzKu3w== X-UI-Out-Filterresults: notjunk:1;V01:K0:8SjUFf7pfxA=:qrH+SBLFoqmRRL1DdCWjnY aSgJRg7qQBYuQVRT2x+oz2uH5RUaBgWUbAjfuNZ8A51tvf4Sw5iYPusDpyk2wztaTXQImYYLK MevpMt9W0yupyMHRiIDDpiX2Tz1cPQuDQF5UaWFxJa2TUaZK4PNpzfabskoSm6vUHwKhmtK6x TaTIjHuZ/F3qRTIG8AfmgK+HDxIFtB+IAy70JZiCuQoFBR4pxsgXjDH4VLFQBCV0bAaKdxUIa Mc04FP0yVEtK3kDvkGLdOq4H8JQAyhYfvjBNIzxll5P6K+C5B3RP8ED0tJUBJ+ONLagh4u5uh DGhYAtokt0SbWXDk+3zMCCxB55OZnQ3IQRg9lmygukf/TrdChzb8fi5e7Kt4cjAeRkIsU1VSl 6v9Bk5bpUSSg9AlDZ7jtAwDtKJq0IR6g55wIuhxmbFV0mbW9sGQVbSdYrLHFWElXELJbqUeUH 6Qk0rtMBw8wtAvZ8bRTuGFKRKkNYdiAb22Voj9Rq/DNWPBKEjJJXX551C56UeoALdjYfnb+x/ T0lBD/WwBksjInvSBsJyChT/aaxsO41lE6/XcOoQWhxpA+kz14sH/Ufi6kXzhV/Hn3GfEIiiu zRWjnow4JlJEqNw/UT7mI0wevP/MDux8YuDqJixE59fsmQawzfp2cRt797sveSqE0nJ5wRixe vn+8Ca5p07cHbw3n7eN6nY4TetZJTA8bgG4mFHaYZm9aYMs9oNHxXzsS4psobjJVnkhA6cMt1 pw4CSdQuhBCniYcDVcGuq9cm//G7iiN86ReBwy5pp5L3+5yzHGus9klsXlz5YK2dwumwtuLMq mmRqVTt 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, 13 Dec 2016 22:01:25 -0000 Am 13.12.2016 um 22:35 schrieb Julian H. Stacey: > >> How is that a problem of "some" ports? All ports require root for "mak= e >> fetch" > No they dont. Given that, then "none do".=20 I'll do what what you omitted in your blind rage, I've dug the important detail up for you, which was the first guess: $ grep _DEPENDS Makefile /dev/null /usr/ports/databases/mysql-q4m/Makefile:FETCH_DEPENDS+=3D =20 ${NONEXISTENT}:${_MYSQL_SERVER}:build This doesn't say "give me root". It needs to be able to build the requisite port. Obviously the fix is to make sure that if you want to fetch as unprivileged user, that you can also *build*. I assume that if you want *fetch* as unprivileged user, that you also want to *build* as unprivileged user, so I'd take that for granted, but it's not the case on your system. On my system, which has a WRKDIRPREFIX that I am permitted to write to with the unprivileged user account doing the builds, "make fetch" for mysql-q4m passes without a hitch. > Thanks for the well intentioned & good advice Matthias, > But some few ports are truly Badly Behaved with make fetch. Can you cite chapter and verse of the rule that makes such a port "truly Badly Behaved", for reference in this list's archives? From owner-freebsd-ports@freebsd.org Tue Dec 13 22:14:37 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6DDF1C76831 for ; Tue, 13 Dec 2016 22:14:37 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [185.24.122.233]) (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 07CDDA08 for ; Tue, 13 Dec 2016 22:14:35 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (p5DC0EAC5.dip0.t-ipconnect.de [93.192.234.197]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id uBDMER4c008661 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Tue, 13 Dec 2016 22:14:27 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host p5DC0EAC5.dip0.t-ipconnect.de [93.192.234.197] claimed to be ultrabook.yoonka.com Subject: Re: what is the purpose of the quarterly ports branches? To: freebsd-ports@freebsd.org References: <7c73fc75-b4d9-063d-02f9-628e06f8d4bd@freebsd.org> <20161207025955.GA21488@Silverstone> <3a97d014-1b8b-7e34-6704-1ee5fd8b97ca@m5p.com> From: Grzegorz Junka Message-ID: <0b018f88-4b64-67c8-a938-ae45fc19d08f@gjunka.com> Date: Tue, 13 Dec 2016 22:14:22 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; 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, 13 Dec 2016 22:14:37 -0000 On 13/12/2016 18:05, Julian Elischer wrote: > On 7/12/2016 10:12 PM, George Mitchell wrote: >> On 12/06/16 21:59, Jason Unovitch wrote: >>> On Mon, Dec 05, 2016 at 10:48:20PM +0000, Ben Woods wrote: >>>> On Tue., 6 Dec. 2016 at 4:44 am, Julian Elischer >>>> wrote: >>>> >>>>> they are effectively useless because the results are not archived, >>>>> and >>>>> the quarterly pkg branch actually changes day by day, so making two >>>>> machines from the same quarterly branch can give you different >>>>> machines (making it useless for paying work) >>>>> >>>>> not to mention that if you use the quarterly pkg branch you run he >>>>> risk of it completely changing if you happen to be unlucky enough to >>>>> be doing it across a quarterly boundary. then you end up with a >>>>> completely messed up system. (from experience). >>>>> >>> If you are handling the burden of support for a customer then perhaps >>> Poudriere and building internally is the best option. Then if you want >>> to stay on an older quarterly because none of what you deploy to >>> customers is impacted by security issues you can roll them at your own >>> pace. >>> >>>>> But the big question still remains.. >>>>> >>>>> What do you think you are solving and why are they changing? >>>>> shouldn't >>>>> a snapshot be stable? >>> >>> Think releng compared to stable in the src repo rather than >>> release/stable. They change in the same fashion to get SA (in the form >>> of VuXML) and errata worthy fixes. >>> [...] >> If only! At least the current base releng does not arbitrarily >> disappear every three months. -- George > > so I think there is a simple partial fix to stop SOME of the worst > problems. > Name the package quarterly sets the same as the ports branches, Use a > symlink to point to them. > and keep them around for 6 months, so there are always 2, one of which > has pretty much stopped changing. > (and provide an EASY way to snarf the lot. currently it's done via an > index.html or something that screws it up. I heard that ports' SVN is mirrored to Github. Isn't it enough to just create a branch or tag for each quarterly release? Even if quarterly packages are deleted, re-building packages from such branch/tag should allow to recreate those packages as required since the same code would give the same packages? Grzegorz From owner-freebsd-ports@freebsd.org Tue Dec 13 22:28:48 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8850DC76D8D for ; Tue, 13 Dec 2016 22:28:48 +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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 111461248 for ; Tue, 13 Dec 2016 22:28:46 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p5B226212.dip0.t-ipconnect.de [91.34.98.18]) (authenticated bits=128) by land.berklix.org (8.15.2/8.15.2) with ESMTPA id uBDMSho4006024; Tue, 13 Dec 2016 22:28:44 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 uBDMSddC003790; Tue, 13 Dec 2016 23:28:39 +0100 (CET) (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 uBDMSL1r018077; Tue, 13 Dec 2016 23:28:33 +0100 (CET) (envelope-from jhs@berklix.com) Message-Id: <201612132228.uBDMSL1r018077@fire.js.berklix.net> To: Matthias Andree cc: null Subject: Re: No port should need root for make fetch 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, 13 Dec 2016 23:01:13 +0100." <96f44b17-b5a3-d24e-dee4-935d55a70019@gmx.de> Date: Tue, 13 Dec 2016 23:28:21 +0100 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, 13 Dec 2016 22:28:48 -0000 Matthias Andree wrote: > Am 13.12.2016 um 22:35 schrieb Julian H. Stacey: > > > >> How is that a problem of "some" ports? All ports require root for "make > >> fetch" > > No they dont. > > Given that, then "none do". > > I'll do what what you omitted in your blind rage, Huh ? Wrong guess, I'm just tired of broken ports. > I've dug the important > detail up for you, which was the first guess: > > $ grep _DEPENDS Makefile /dev/null > /usr/ports/databases/mysql-q4m/Makefile:FETCH_DEPENDS+= > ${NONEXISTENT}:${_MYSQL_SERVER}:build > > This doesn't say "give me root". It needs to be able to build the > requisite port. > > Obviously the fix is to make sure that if you want to fetch as > unprivileged user, that you can also *build*. > I assume that if you want *fetch* as unprivileged user, that you also > want to *build* as unprivileged user, No, wrong. I'm just building a stockpile of local distfiles for use later on a mass build. I'm quite happy to build as root. > so I'd take that for granted, but > it's not the case on your system. > > On my system, which has a WRKDIRPREFIX that I am permitted to write to > with the unprivileged user account doing the builds, "make fetch" for > mysql-q4m passes without a hitch. Please stop guessing & assuming wrongly, try as normal user what I reported in 3rd line of my first post cd /usr/ports; make -i fetch & you will breaking ports.. > > Thanks for the well intentioned & good advice Matthias, > > But some few ports are truly Badly Behaved with make fetch. > > Can you cite chapter and verse of the rule that makes such a port "truly > Badly Behaved", for reference in this list's archives? You seem to be looking to argue. I'm not going to. Run as normal user cd /usr/ports; make -i fetch Cheers, Julian -- Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable. http://berklix.eu/brexit/#stolen_votes From owner-freebsd-ports@freebsd.org Tue Dec 13 22:34:27 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66F61C76154 for ; Tue, 13 Dec 2016 22:34:27 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE82419EA for ; Tue, 13 Dec 2016 22:34:26 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([77.181.21.39]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MFLhE-1cMNA33cVo-00ELbE for ; Tue, 13 Dec 2016 23:34:24 +0100 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 366A323CF5A for ; Tue, 13 Dec 2016 23:34:21 +0100 (CET) Subject: Re: No port should need root for make fetch To: null References: <201612132228.uBDMSL1r018077@fire.js.berklix.net> From: Matthias Andree Message-ID: <1b62d470-40a3-8cc9-6dd2-bd07ca6753f1@gmx.de> Date: Tue, 13 Dec 2016 23:34:20 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <201612132228.uBDMSL1r018077@fire.js.berklix.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:XfNY6ZSTE0FYOn6ktPlobarhjE7N8OYIAmIItMAxE8Q72o16nGy eSZcrkapCJwUmU/Q6OMEfOzm05F/9F0ox3oahP14fE3uirPmWDqo1D8b6/vZXNexk60Q3fp ijOkVJ4YVOQScsqyMSMhUKTI5MKhiT/Pp9PRk/opOuSdNXsf2cxh/Mwy6phgQx5RsJxdBp+ KTglEDlJ1e/RzE2UQua8g== X-UI-Out-Filterresults: notjunk:1;V01:K0:NjC22vgEq7U=:X1coGUKcKLuPkAwNew3HDX gdVXKXfCgOIaeMVl5v5fpxcOLvC/Mou4PY/xyXYqc9/YVgv4YwA9jPAxMGHuY17AZ8eM8xf2u UvxRl8lBO8aete5rwZwdlnx10VUDNMU/W7MbDQB6fct97hOQwhL/vGHry+1d9hX9d3kXVf/cT TeubWZntvVkEzamg8L8MR2jHcQDtYqHeOYVlKj3aqT53rVq9Nhik8oUThE1wXyNQUrwEcAcCT 0OnInOryAPtl5duqlu/cuJtxFnmrR9PhEUxpDPLd6QofquBHLuznkfbAlzG8r0SY5TZqWLyi9 5OrDouAZIK0VzsueAn8jQxVaHHEcrugWDpv53gdLa/C1GDgRspTBUKksQilnI+exObisi9Rzt HedBkbkZR30QONaooancttG+8L8BfgsJTIsD7xKZQNIbZ2DUcjXq18u8gzmHKRtPB5DJdbZD+ Nr/gVb+/Anfq7oqvCD1el6GWlJCtHE+pBZurYD7KCeBw5NLrSmGjhEM4B+7t6Vn3NHJZW+R/b dNdGdNeHapyyC3/XXscgD6+qM/rW7AZrov5Zu9p6OM2TxKKP3h1xXKIhCQ5qKNpwGp5xz7Jfj F2H0HfALjkulTflbOfTHN5zo+CSoLmrr50O0uxHlOtOae6OxxrzI9b1z7uCvy1Q/e6uq1SGo/ m182Ui+J65qn/EGibhDoq00QnC2T/VhdIb+Y+H27OoWE05eYrdZWRWURkipdRMvLBDozHY3A5 jYh0BzFwuypNbJFodMS3nv12T1/G9kDW8I2ek8NyO/annlg1SIcrmwk8Zqd3GqmiIZB9J3zz5 jpZeWU0 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, 13 Dec 2016 22:34:27 -0000 Am 13.12.2016 um 23:28 schrieb Julian H. Stacey: > I'm just building a stockpile of local distfiles for use later on a mass build. > I'm quite happy to build as root. > > [...] > Please stop guessing & assuming wrongly, > try as normal user what I reported in 3rd line of my first post > cd /usr/ports; make -i fetch > & you will breaking ports.. I'm certainly not going out to download some 30,000 distfiles. I've checked that "make checksum" works for me as unprivileged user on the one port, and I do appreciate that if one port has FETCH_DEPENDS=aaaa:bbbb:build can hurt. So where's the solution for you? Are you proposing a change in that ports should not be permitted to require the "build" stage of another port as requisite, which has been a standard mechanism in *_DEPENDS for years? Cheers, Matthias From owner-freebsd-ports@freebsd.org Wed Dec 14 05:17:49 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60E17C767D9 for ; Wed, 14 Dec 2016 05:17:49 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 47009109F for ; Wed, 14 Dec 2016 05:17:49 +0000 (UTC) (envelope-from peter@rulingia.com) Received: by mailman.ysv.freebsd.org (Postfix) id 43963C767D6; Wed, 14 Dec 2016 05:17:49 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43447C767D5 for ; Wed, 14 Dec 2016 05:17:49 +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 BE658109E for ; Wed, 14 Dec 2016 05:17:47 +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 uBE5HD2Y088390 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 14 Dec 2016 16:17:22 +1100 (AEDT) (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 uBE5H8lm090843 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 14 Dec 2016 16:17:08 +1100 (AEDT) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id uBE5H6Ua090842; Wed, 14 Dec 2016 16:17:06 +1100 (AEDT) (envelope-from peter) Date: Wed, 14 Dec 2016 16:17:06 +1100 From: Peter Jeremy To: "Julian H. Stacey" Cc: ports@FreeBSD.org Subject: Re: No port should need root for make fetch Message-ID: <20161214051706.GS61036@server.rulingia.com> References: <201612132032.uBDKWaVK017178@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="sgneBHv3152wZ8jf" Content-Disposition: inline In-Reply-To: <201612132032.uBDKWaVK017178@fire.js.berklix.net> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.7.1 (2016-10-04) 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, 14 Dec 2016 05:17:49 -0000 --sgneBHv3152wZ8jf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2016-Dec-13 21:32:36 +0100, "Julian H. Stacey" wrote: >IMO No port should need root for=20 > cd /usr/ports; make -i fetch In a stock FreeBSD install, all ports require root to both fetch and build. You have customised your system in a non-standard way so you are getting non-standard behaviour which doesn't match you expectations. IMO (which is equally valid to yours), no-one should need to run "cd /usr/ports; make -i fetch" so there's no problem to solve. --=20 Peter Jeremy --sgneBHv3152wZ8jf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJYUNXSXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs0ZaEQAJ2ThoVILYWYY9+XqhY45KtS mdKvw1k/gr++oTQc8kXldK7P27djmRWv+6vdu7EVkrm5Z2vaN0ZiDfuK/bX7jZpg GWnCILPwlNX0+2RmSaVhXBgyZZHEnTITGWvE34WzL5eU2y8hHLHIAi0zVUc+bdf6 kO3n+FsWni4dUrsMCoVYSX+8UpQhJgy/ixPF8zXnt/o+nCybyn92y8N4og53imd2 KFYheo6mCOm7kAnKvKmLLwYKmR7FCV3BulDomlK97GUH64x5HEvp87kbom0rzvXU z6IjGL4BZYk29WWb3E1C0/BTRixWMUWscLcdhIbhHDBztC2zD4VpLiA52SZi/31F GTVVi6YPXy2yijUqfgM1Qs12vrdw917/s6MMBsH7DvJ2Fk8YnjcJREi7uZDFCJ7t kNJlyqJdL++4XqX4Cb3cfO05o2fj/OBLYzkx2oHDNgF+k4BTBf7dL0LuHpcxTYQ7 ciz0jb6RgNAxHwnyzKQAdxAMix1U7b4ZAGuqQYck74qeaqGoiyKKZZIScWkQ35ql iV3KcSWiofeQujrwIcgIgeiv3IvWJwNXMm2bt+5TH37/1IAocHAIyumzjMbq5ntg PCy2fw2+Xq7h0pEl/A/QDkBadJysyHxCCzlkLu382bli/JLaiWg0HAka3+On6nJC jy99v3O+uj0bPpD4TOnU =LpPj -----END PGP SIGNATURE----- --sgneBHv3152wZ8jf-- From owner-freebsd-ports@freebsd.org Wed Dec 14 08:06:16 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECB5AC772D0 for ; Wed, 14 Dec 2016 08:06:16 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by mx1.freebsd.org (Postfix) with ESMTP id 8A0D9162E for ; Wed, 14 Dec 2016 08:06:15 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ppp118-210-147-181.bras1.adl6.internode.on.net (HELO leader.local) ([118.210.147.181]) by ipmail06.adl6.internode.on.net with ESMTP; 14 Dec 2016 18:35:58 +1030 Subject: Re: The ports collection has some serious issues To: "Julian H. Stacey" References: <201612121931.uBCJV0qO022291@fire.js.berklix.net> Cc: freebsd-ports@freebsd.org From: Shane Ambler Message-ID: Date: Wed, 14 Dec 2016 18:35:55 +1030 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <201612121931.uBCJV0qO022291@fire.js.berklix.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 08:06:17 -0000 On 13/12/2016 06:01, Julian H. Stacey wrote: >> I would say this rarely happens with the default setup, the more port >> options you change the more likely it is something will break. > > Yes, I now start: cd /var/db/ports; mv * MV/* ; setenv NO_DIALOG=YES > Before: cd /usr/ports; make BERKLIX_CLIENT=YES # Uses ports/*/Makefile.local > (still innumerable breaks of course on 1200 ports inc deps.) > > I can re-enable options for a 2nd pass rebuild for the very > few ports need it (maybe some better way?). That's what I like about poudriere, one port can fail and builds still continue until as much is built as possible. I also know that everything is built before changing anything that is installed. > poudriere's `-f' is nice to accept a list. > But I havent found a way to build my list yet from my Makefile.local eg > cd /usr/ports; make BERKLIX_CLIENT=YES echo_my_category_and_port > I'll probably hack bsd.port.mk & bsd.port.subdir.mk make all-depends-list also - make build-depends-list make run-depends-list make package-depends-list make test-depends-list To create a list of ports I have installed I just use pkg info -aqo | sort > myports.list For setting options, I created /usr/local/etc/poudriere.d/mypkg-make.conf and filled it with lines like DEFAULT_VERSIONS= apache=2.4 perl5=5.20 pgsql=9.5 OPTIONS_SET= OPTIMIZED_CFLAGS CPU_OPTS SIMD MMX SSE SSE2 SSSE3 x11-servers_xorg-server_SET= DEVD SUID x11-servers_xorg-server_UNSET= HAL then I use poudriere bulk -j 10stableamd64 -p myports -z mypkg -f myports.list that way these settings are only used when building my pkg repo and not when I test build any ports (use poudriere.d/make.conf for settings to be used in all poudriere builds). My /etc/make.conf only contains - .include "/usr/local/etc/poudriere.d/mypkg-make.conf" so the same setting are used for any manual port builds as well as my poudriere created pkg repo. -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-ports@freebsd.org Wed Dec 14 08:42:02 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB50FC77BC4 for ; Wed, 14 Dec 2016 08:42:02 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by mx1.freebsd.org (Postfix) with ESMTP id 4D0CC1A07 for ; Wed, 14 Dec 2016 08:42:01 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ppp118-210-147-181.bras1.adl6.internode.on.net (HELO leader.local) ([118.210.147.181]) by ipmail06.adl6.internode.on.net with ESMTP; 14 Dec 2016 19:11:58 +1030 Subject: Re: The ports collection has some serious issues To: scratch65535@att.net, freebsd-ports References: <20161208085926.GC2691@gmail.com> <5s3t4c576qeivfr32d2j7u1fm8jkia97jf@4ax.com> From: Shane Ambler Message-ID: Date: Wed, 14 Dec 2016 19:11:57 +1030 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <5s3t4c576qeivfr32d2j7u1fm8jkia97jf@4ax.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 08:42:02 -0000 On 12/12/2016 23:14, scratch65535@att.net wrote: > [Default] On Mon, 12 Dec 2016 17:01:33 +1030, Shane Ambler > wrote: >> The quarterly ports has been setup for a couple of years but doesn't >> seem to be documented well, or it just isn't obvious to find. You can >> use svn to checkout a stable branch by specifying a branch name, such as >> ports/branches/2016Q4 instead of ports/head. You can also adjust pkg to >> use the quarterly ports by changing the pkg repo URL from >> pkg.FreeBSD.org/${ABI}/latest to pkg.FreeBSD.org/${ABI}/quarterly > > That's interesting. The ones that break on me are the ones I get > from portsnap. Does portsnap tap quarterly or something else? Pretty sure portsnap gets snapshots from HEAD. Don't see a way to set quarterly for it, so svn would be needed to get a quarterly ports tree. It would mostly be a matter of timing, a snapshot is made for portsnap and a pkg build is started. By the time the pkg repo is built (a day? two?) a new snapshot would be in use by portsnap so it would never be in sync with the pkg repo. It might be worth changing defaults to use quarterly for both portsnap and pkg. An average user shouldn't have issues to only getting new versions every three months, for those that want to stay on the cutting edge a few settings can be changed to use HEAD and/or latest. -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-ports@freebsd.org Wed Dec 14 08:46:51 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDBEBC77CBF for ; Wed, 14 Dec 2016 08:46:51 +0000 (UTC) (envelope-from knu@iDaemons.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 B61F41C7B for ; Wed, 14 Dec 2016 08:46:51 +0000 (UTC) (envelope-from knu@iDaemons.org) Received: by mailman.ysv.freebsd.org (Postfix) id B275AC77CBE; Wed, 14 Dec 2016 08:46:51 +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 B21CEC77CBD for ; Wed, 14 Dec 2016 08:46:51 +0000 (UTC) (envelope-from knu@iDaemons.org) Received: from mail.musha.org (v055125.ppp.asahi-net.or.jp [124.155.55.125]) by mx1.freebsd.org (Postfix) with ESMTP id 834251C78 for ; Wed, 14 Dec 2016 08:46:50 +0000 (UTC) (envelope-from knu@iDaemons.org) Received: by mail.musha.org (Postfix, from userid 58) id 3tdqh761bVznW6n; Wed, 14 Dec 2016 17:37:27 +0900 (JST) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on daemon.musha.org X-Spam-Level: ** X-Spam-Status: No, score=2.8 required=13.0 tests=BAYES_50, CONTENT_TYPE_PRESENT, FAKEDWORD_ONE,FAKEDWORD_VERTICALLINE,ONLY1HOPDIRECT,RP_MATCHES_RCVD, SPF_HELO_FAIL,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 Received: from daemon.musha.org (daemon.local.idaemons.org [192.168.11.11]) by mail.musha.org (Postfix) with ESMTP id 3tdqh72RgQznW6k; Wed, 14 Dec 2016 17:37:27 +0900 (JST) Date: Wed, 14 Dec 2016 17:37:24 +0900 Message-ID: <86y3zinby3.knu@iDaemons.org> From: "Akinori MUSHA" To: "Julian H. Stacey" Cc: ports@FreeBSD.org Subject: Re: No port should need root for make fetch In-Reply-To: <201612132032.uBDKWaVK017178@fire.js.berklix.net> References: <201612132032.uBDKWaVK017178@fire.js.berklix.net> Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 081D 099C 1705 861D 4B70 B04A 920B EFC7 9FD9 E1EE MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Wed_Dec_14_17:37:21_2016-1"; micalg=pgp-sha1; protocol="application/pgp-signature" 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, 14 Dec 2016 08:46:51 -0000 --pgp-sign-Multipart_Wed_Dec_14_17:37:21_2016-1 Content-Type: text/plain; charset=US-ASCII Hi, Thanks for the info. On Wed, 14 Dec 2016 05:32:36 +0900, Julian H. Stacey wrote: > Hi ports@ > IMO No port should need root for > cd /usr/ports; make -i fetch > The first one that broke for me was databases/mysql-q4m > (OK might be others before, but I have DUDS = > arabic biology chinese hebrew hungarian japanese korean > polish portuguese russian ukrainian vietnamese games demime > majordomo acroreadwrapper acroread9 chimera dosbox emil > firefox freerdp gimp-app gv libcue mp3splt-gtk nut opera > ripit vlc xorg xsane > ) > (MAINTAINER CC'd) but there's more ports beyond, usually because > some ports also go berserk & install, or mabe install dependents. Having the dependency as FETCH_DEPENDS [*] was not my idea, but that was for a reason: you should not fetch a file while building a port. * https://svnweb.freebsd.org/ports/head/databases/mysql-q4m/Makefile#rev297196 And you are making a point here: you should not build a port (which involves installing its build dependencies as root) while fetching a file. These two demands cannot be easily satisfied at the same time, and I believe that in general, the idea of FETCH_DEPENDS implies that fetching may require the root privilege. For example, if the distfile were only available via some weird protocol that any standard tool in the base system cannot speak, then you'd need to install a tool for that from another port as root. I admit that the use of FETCH_DEPENDS in this particular port might be an abuse of the feature, but still, you should note that fetching in general is not always a root-free operation. Perhaps copying mysql-server's build dependencies to mysql-q4m may mitigate the issue here, but that does not seem quite right considering the cost for maintenance. What do you think? -- Akinori MUSHA / https://akinori.org/ --pgp-sign-Multipart_Wed_Dec_14_17:37:21_2016-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit Content-Description: OpenPGP Digital Signature -----BEGIN PGP SIGNATURE----- iEYEABECAAYFAlhRBMIACgkQkgvvx5/Z4e6N4QCdEQKzEA+ZhVYTZJtMmqYyzYQp 3CMAoKLPlIKneXJaW+6oPV2NeKCoRXX3 =tioK -----END PGP SIGNATURE----- --pgp-sign-Multipart_Wed_Dec_14_17:37:21_2016-1-- From owner-freebsd-ports@freebsd.org Wed Dec 14 09:11:43 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E5692C7583F for ; Wed, 14 Dec 2016 09:11: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 D28C51F00 for ; Wed, 14 Dec 2016 09:11:43 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id D1F59C7583E; Wed, 14 Dec 2016 09:11: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 D1A99C7583D for ; Wed, 14 Dec 2016 09:11: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 C50041EFF for ; Wed, 14 Dec 2016 09:11: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 uBE9Bh82018570 for ; Wed, 14 Dec 2016 09:11:43 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id uBE9Bhbg018561; Wed, 14 Dec 2016 09:11:43 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201612140911.uBE9Bhbg018561@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, 14 Dec 2016 09:11: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, 14 Dec 2016 09:11: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 ------------------------------------------------+-----------------+------------ databases/mysql-connector-odbc | 5.3.4 | 5.3.7 ------------------------------------------------+-----------------+------------ devel/pecl-weakref | 0.2.6 | 0.3.3 ------------------------------------------------+-----------------+------------ 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 Dec 14 09:16:30 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DE0B1C75D19 for ; Wed, 14 Dec 2016 09:16:30 +0000 (UTC) (envelope-from luca.pizzamiglio@gmail.com) Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A77DD12E9 for ; Wed, 14 Dec 2016 09:16:30 +0000 (UTC) (envelope-from luca.pizzamiglio@gmail.com) Received: by mail-oi0-x233.google.com with SMTP id w63so14154628oiw.0 for ; Wed, 14 Dec 2016 01:16:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=jcIxiX5cDEJ/YYWVUJAb3/vUGOKUSelgmAlmlF8ovwU=; b=RLPoRW3BMToA346X864zmjEy3BdsVQpyX5zMLp0mx/uDVibwiov8AMp/JQyvU9FZFO Q7gOB1EAyYcKK3z83xSBNMnI7CqdzwZaYiJDdNpeRMCDEfqd9V13g1hbx0RuFOnH7wAC Qw29ls0tdmlVDHtCMsZ690zUB2mowpYvT371QjfacIubiCFG/BiPZHXLGlDsG/of3yXp ZsYEcO+XbHuPUJBghCD2PVnfZd2NMu5Lvu3iVPwL9Q+OJp2bmX9RUwdYgLWUQwb6vvyD fdWeImYOkMtQ+30JTw1SGijxlsm1xEaYp3MBZkiPcbLaQzFLDVfcqRDd2mz14edJH66m BGjA== 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=jcIxiX5cDEJ/YYWVUJAb3/vUGOKUSelgmAlmlF8ovwU=; b=ZLZlZajIBeda1YqAavAODG7TDQZgXSFFPeD9EBw0Ft0bvC/Rfy9OLoUKf9+iVjniIw UlE38e+bgX1SlUTkGTBl5qDv8MdnwSg+nj7C2t1wvu+aq6YP/O3jdmWRIAV9pP3Dy0wn xFYCJxXw/bBV4dKBPovnN5i2rQqqXPDKDRpvBPCODMUA/CFAChthLT1C+vKiTqYo66l+ HnCXAR4OxpCz+imjnJmw0sBUUikXMddfCQ0dt1loHatrNQkAsfZAgF9D4nSk0SIPQIwW fDljuMd5fsmHtHNxxTa4ofMzmnkDij4o0TbkchpDaeTjuu2GU9VDzufSDHd7516SEb+s 3yLg== X-Gm-Message-State: AKaTC00weONT1K0PotkhBTRdsiRlYpVDnH5+BO3oD0SuTXjxnW9QWVbOROODLPexbFKu9jA8OlDYcbkaxgmoZQ== X-Received: by 10.157.46.5 with SMTP id q5mr61460050otb.46.1481706989914; Wed, 14 Dec 2016 01:16:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.183.11.72 with HTTP; Wed, 14 Dec 2016 01:16:09 -0800 (PST) From: Luca Pizzamiglio Date: Wed, 14 Dec 2016 10:16:09 +0100 Message-ID: Subject: Optional circular dependency between multimedia/ffmpeg and audio/chromaprint To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 09:16:31 -0000 Today I discovered a circular dependency: if multimedia/ffmpeg has the chromaprint option enabled, then it needs audio/chromaprint audio/chromaprint always needs multimedia/ffmpeg Using portmaster, I was unable to update both of them. At the moment, I remove the option in multimedia/ffmpeg, but I don't a better solution. Best regards, Luca From owner-freebsd-ports@freebsd.org Wed Dec 14 14:33:05 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E19FDC77918 for ; Wed, 14 Dec 2016 14:33:05 +0000 (UTC) (envelope-from bob@eager.cx) 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 CEAB117FA for ; Wed, 14 Dec 2016 14:33:05 +0000 (UTC) (envelope-from bob@eager.cx) Received: by mailman.ysv.freebsd.org (Postfix) id CE050C77917; Wed, 14 Dec 2016 14:33:05 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDA9FC77915 for ; Wed, 14 Dec 2016 14:33:05 +0000 (UTC) (envelope-from bob@eager.cx) Received: from kipling.tavi.co.uk (kipling.tavi.co.uk [81.187.145.130]) by mx1.freebsd.org (Postfix) with ESMTP id 9863017F8 for ; Wed, 14 Dec 2016 14:33:05 +0000 (UTC) (envelope-from bob@eager.cx) Received: from raksha.tavi.co.uk (raksha.tavi.co.uk [81.187.145.139]) by kipling.tavi.co.uk (Postfix) with ESMTP id 2E37175961 for ; Wed, 14 Dec 2016 14:27:19 +0000 (GMT) Date: Wed, 14 Dec 2016 14:27:19 +0000 From: Bob Eager To: ports@freebsd.org Subject: emulators/simh failing to build; PR waiting Message-ID: <20161214142719.77e70c3c@raksha.tavi.co.uk> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; i386-portbld-freebsd10.3) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAMFBMVEUwXjFLc0vD0cS7y7zw9PDZ4tkWSRaVrZZ+m39qi2tXfVj////7+/utwK4IPggAOAAJUUA7AAABKklEQVQ4jWPYjQMwDFYJp0NKEKCNJmEf9h8CsimXiL2e33s3/e7F7K2Cs3f3dCMkQkMKj4YuCY3K3iR+e7fMaiSjvkX0/5cFGrWpe2uLzOpaExUVqMS/8PX/Re5ey960OLBTZpFA8+IlSBKPQ92zNyUUBsosN58uIY0k8f+/ONCoYytkVuhWzVwNkYiYbqk5M3NmOVBi41YZ8RsGF7shEtFb5KJ3r969CyixM7OTPeFUxG2IxLO8/9/SvqXlc+/x3h295YzLlj2nIRJQj//nRvc5TEIal8RsXBLVuCQwIgoq/u80DomP6HEOk/iOS+IJLonZOCT+ReOQ+Lkbh0QKLonbOCR+7MYhsRqHBJrVcIl/1TgklqKLQyQ+tGKIgyQOqXpjig94diZRAgAXmDX6jyWafAAAAABJRU5ErkJggg====== MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 14:33:06 -0000 I took over maintainership of this port a little while ago. I generated some minor fixes, but it wasn't worth uploading them. About three weeks ago I started getting emails from pkg-fallout about build failures on i386 and amd64. This is only happening on CURRENT so far. I have incorporated the fix for this and submitted the whole lot as a PR; the PR is 214990. The fix has been tested on the CURRENT snapshot for the end of November. The PR hasn't been picked up yet; could someone take a look, please? -- Bob From owner-freebsd-ports@freebsd.org Wed Dec 14 15:20:07 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C61DEC8061C for ; Wed, 14 Dec 2016 15:20:07 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mail.inka.de (quechua.inka.de [IPv6:2a04:c9c7:0:1073:217:a4ff:fe3b:e77c]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9349513A9 for ; Wed, 14 Dec 2016 15:20:07 +0000 (UTC) (envelope-from news@mips.inka.de) Received: from mips.inka.de (news@[127.0.0.1]) by mail.inka.de with uucp (rmailwrap 0.5) id 1cHBLg-0002Ma-CI; Wed, 14 Dec 2016 16:20:04 +0100 Received: from lorvorc.mips.inka.de (localhost [127.0.0.1]) by lorvorc.mips.inka.de (8.15.2/8.15.2) with ESMTP id uBEFGc0N092543 for ; Wed, 14 Dec 2016 16:16:38 +0100 (CET) (envelope-from news@lorvorc.mips.inka.de) Received: (from news@localhost) by lorvorc.mips.inka.de (8.15.2/8.15.2/Submit) id uBEFGcEu092542 for freebsd-ports@freebsd.org; Wed, 14 Dec 2016 16:16:38 +0100 (CET) (envelope-from news) To: freebsd-ports@freebsd.org From: Christian Weisgerber Newsgroups: list.freebsd.ports Subject: COPYTREE_SHARE failure in poudriere Date: Wed, 14 Dec 2016 15:16:38 +0000 (UTC) Message-ID: User-Agent: slrn/1.0.3 (FreeBSD) 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, 14 Dec 2016 15:20:07 -0000 I'm stuck here with this bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215150 It comes down to ${COPYTREE_SHARE} erroring out when performing a chmod. I expect that this isn't a problem with the port (if only because I would be swamped with reports otherwise), but some detail of the submitter's poudriere set-up. I can't dig into poudriere now. Can anybody help Marko figure out what's going on there? -- Christian "naddy" Weisgerber naddy@mips.inka.de From owner-freebsd-ports@freebsd.org Wed Dec 14 16:11:28 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C44CFC66B2C; Wed, 14 Dec 2016 16:11:28 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: from mail.hs.ntnu.edu.tw (mail.hs.ntnu.edu.tw [140.131.149.3]) (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 95B121262; Wed, 14 Dec 2016 16:11:25 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: by mail.hs.ntnu.edu.tw (Postfix, from userid 800) id 8FE881C6457; Thu, 15 Dec 2016 00:03:16 +0800 (CST) Received: from mail.hs.ntnu.edu.tw (localhost [127.0.0.1]) (Authenticated sender: iblis@hs.ntnu.edu.tw) by mail.hs.ntnu.edu.tw (Postfix) with ESMTPA id 591CE1C644A; Thu, 15 Dec 2016 00:03:16 +0800 (CST) Received: from 140-113-138-96.Dorm12.NCTU.edu.tw ([140.113.138.96]) by mail.hs.ntnu.edu.tw with HTTP (HTTP/1.1 POST); Thu, 15 Dec 2016 00:03:16 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Thu, 15 Dec 2016 00:03:16 +0800 From: Iblis Lin To: freebsd-ports@FreeBSD.org Cc: freebsd-numerics@FreeBSD.org Subject: lang/julia call for testing Message-ID: User-Agent: HSNU Mail X-Bogosity: Ham, tests=bogofilter, spamicity=0.498649, version=1.2.4 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, 14 Dec 2016 16:11:28 -0000 Hi, The PR on bugzilla is here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215297 And here is the repo of the port: https://github.com/lwhsu/freebsd-ports-lang-julia (Thanks to patient guidance from lwhsu@ !) Some notes about options: By default, the GPL_LIBS will not be enabled, this cause some fft related function not working. If we enable the GPL_LIBS, the version of math/suitespare in our ports is too old, it will make tons of function reveal warning. Need help for update suitespare. If you are interested in this port, please help on testing. To be honest, I am not a developer of julia and even cannot write any julia code (maybe was able to write few). I started to port it, just because I need to write machine learning homework in my university course. :p There is also lots of math libs julia required, and I still cannot understand the complex relationship of them at all , e.g. tons of Xblas, LAPACK ... etc. If I pin the wrong depends in Makefile, please comment. Or, one can be replaced by another one, please comment, also. I will try to add OPTIONS. About the `make test`, I still got some mmap testing failure on my box. Maybe we can discuss them first. Then, upstream to julia's github issue tracker. -- Iblis Lin 林峻頤 From owner-freebsd-ports@freebsd.org Wed Dec 14 16:53:26 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5491C80FAF for ; Wed, 14 Dec 2016 16:53:26 +0000 (UTC) (envelope-from jankyj@unfs.us) 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 A3FD5154E for ; Wed, 14 Dec 2016 16:53:26 +0000 (UTC) (envelope-from jankyj@unfs.us) Received: by mailman.ysv.freebsd.org (Postfix) id A060CC80FAD; Wed, 14 Dec 2016 16:53:26 +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 A007DC80FAC for ; Wed, 14 Dec 2016 16:53:26 +0000 (UTC) (envelope-from jankyj@unfs.us) Received: from stig.purplehat.org (stig.purplehat.org [50.243.134.106]) (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 794191547 for ; Wed, 14 Dec 2016 16:53:26 +0000 (UTC) (envelope-from jankyj@unfs.us) Received: from localhost (bill.goatse.unfs.us [50.243.134.106]) by stig.purplehat.org (Postfix) with ESMTP id BAA6F5E806 for ; Wed, 14 Dec 2016 09:53:24 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=unfs.us; s=mail; t=1481734404; bh=MyHVxcDIQsRuJStpMu6SdBlt+u7Fkyk0bKXYkxhb2NA=; h=To:From:Subject:Date; b=EwM6rDsdD9MsQa9SC9Pd2zSyzr0IH3mfH3KBOcUZZbvZYq8w30XWykkwPwZl9x+Ea /bD/05O1L8LCRlLIIcDuLTkRLRirsGo2PEfHwkRBwYdAkkEmJy4VYZtFnZyz0lXcHr w331y6iEbIbG6B+7FlGMa0sTsGlgbX6ihTU+B7/Y= Received: from stig.purplehat.org ([50.243.134.106]) by localhost (stig.purplehat.org [50.243.134.106]) (maiad, port 10024) with ESMTP id 42698-10 for ; Wed, 14 Dec 2016 09:53:24 -0700 (MST) Received: from drp01-dev.enwd.co.sc.charterlab.com (71-85-81-72.static.dnvr.co.charter.com [71.85.81.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: jankyj@unfs.us) by stig.purplehat.org (Postfix) with ESMTPSA id C78835E7FC for ; Wed, 14 Dec 2016 09:53:23 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=unfs.us; s=mail; t=1481734403; bh=MyHVxcDIQsRuJStpMu6SdBlt+u7Fkyk0bKXYkxhb2NA=; h=To:From:Subject:Date; b=elRqb3x8yBLygyTMgZlOoYVUylcFikmCv2s9kSTPMo6sYY5SPXvM7IFlxib0jVFFP AZvUxmnn+ilJYUUgK6pWDSja//3v/wQYlKzPA6u2GZtiVzybfGMnWV5GL9jU8YZnlY sWo89o6yYhEAGOBYNb1z+FJDFtk41hm5H6lJ9X5A= To: ports@freebsd.org From: "Janky Jay, III" Subject: mail/p5-Net-SMTP-SSL Deprecated Message. Message-ID: <38d48d9c-08ec-b273-bf0b-d7da0fd03f9b@unfs.us> Date: Wed, 14 Dec 2016 09:53:22 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ghak0lmOOGvd4nGd7Gl9KDwuc0VXMNVEv" X-Virus-Scanned: Maia Mailguard 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, 14 Dec 2016 16:53:26 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ghak0lmOOGvd4nGd7Gl9KDwuc0VXMNVEv Content-Type: multipart/mixed; boundary="eiqRf7ormgVGWM7QUAVvpW5O8AW6Hq2vj"; protected-headers="v1" From: "Janky Jay, III" To: ports@freebsd.org Message-ID: <38d48d9c-08ec-b273-bf0b-d7da0fd03f9b@unfs.us> Subject: mail/p5-Net-SMTP-SSL Deprecated Message. --eiqRf7ormgVGWM7QUAVvpW5O8AW6Hq2vj Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello All, So, mail/p5-Net-SMTP-SSL is a requirement of security/maia (a port I maintain) and it is apparently being deprecated as of March of next year. I see this in my nightly reports: p5-Net-SMTP-SSL-1.04: Tag: expiration_date Value: 2017-03-31 p5-Net-SMTP-SSL-1.04: Tag: deprecated Value: Deprecated by upstream, use Net::SMTP instead I'd like to get this dependency updated in the port but I don't see a "Net::SMTP" available (at least in the ${LOCALBASE}/mail directory. I see others such as p5-Net-SMTP-TLS and p5-Net-SMTPS and p5-Net-SMTP_auth, etc... My question is, what port am I supposed to use instead of p5-Net-SMTP-SSL? I see no configuration options for SSL in the other ports. Just want to make sure I do this correctly. Any information will be greatly appreciated! Kind Regards, Janky Jay, III --eiqRf7ormgVGWM7QUAVvpW5O8AW6Hq2vj-- --ghak0lmOOGvd4nGd7Gl9KDwuc0VXMNVEv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlhReQIACgkQGK3MsUbJZn5m+QCdHZP9Vobr2efOwlWkpYgRfgR9 5QAAniKI9C1lBuUgf3B+lNP9rRmeN14v =Y4FT -----END PGP SIGNATURE----- --ghak0lmOOGvd4nGd7Gl9KDwuc0VXMNVEv-- From owner-freebsd-ports@freebsd.org Wed Dec 14 17:22:20 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B844C77CB5 for ; Wed, 14 Dec 2016 17:22:20 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DF30810AD for ; Wed, 14 Dec 2016 17:22:19 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from host-4-75.office.adestra.com (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 74F0F7BFF for ; Wed, 14 Dec 2016 17:22:15 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/74F0F7BFF; dkim=none; dkim-atps=neutral Subject: Re: mail/p5-Net-SMTP-SSL Deprecated Message. To: freebsd-ports@freebsd.org References: <38d48d9c-08ec-b273-bf0b-d7da0fd03f9b@unfs.us> From: Matthew Seaman Message-ID: <1c38c3ba-c8ce-4e56-9c33-19224a680aac@FreeBSD.org> Date: Wed, 14 Dec 2016 17:22:08 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <38d48d9c-08ec-b273-bf0b-d7da0fd03f9b@unfs.us> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="JnhH3BmcoMLeo3Mbf8Qb9guR9FeeTMpx1" X-Spam-Status: No, score=0.9 required=5.0 tests=BAYES_00,RCVD_IN_RP_RNBL, RDNS_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 17:22:20 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JnhH3BmcoMLeo3Mbf8Qb9guR9FeeTMpx1 Content-Type: multipart/mixed; boundary="lk6iNVbHamFxMBPL5xdwfW1ceA9GlIGdI"; protected-headers="v1" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: <1c38c3ba-c8ce-4e56-9c33-19224a680aac@FreeBSD.org> Subject: Re: mail/p5-Net-SMTP-SSL Deprecated Message. References: <38d48d9c-08ec-b273-bf0b-d7da0fd03f9b@unfs.us> In-Reply-To: <38d48d9c-08ec-b273-bf0b-d7da0fd03f9b@unfs.us> --lk6iNVbHamFxMBPL5xdwfW1ceA9GlIGdI Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2016/12/14 16:53, Janky Jay, III wrote: > Hello All, >=20 > So, mail/p5-Net-SMTP-SSL is a requirement of security/maia (a port I > maintain) and it is apparently being deprecated as of March of next > year. I see this in my nightly reports: >=20 > p5-Net-SMTP-SSL-1.04: Tag: expiration_date Value: 2017-03-31 > p5-Net-SMTP-SSL-1.04: Tag: deprecated Value: Deprecated by upstream, us= e > Net::SMTP instead >=20 > I'd like to get this dependency updated in the port but I don't see a > "Net::SMTP" available (at least in the ${LOCALBASE}/mail directory. I > see others such as p5-Net-SMTP-TLS and p5-Net-SMTPS and > p5-Net-SMTP_auth, etc... >=20 > My question is, what port am I supposed to use instead of > p5-Net-SMTP-SSL? I see no configuration options for SSL in the other > ports. Just want to make sure I do this correctly. Any information will= > be greatly appreciated! Net::SMTP is a core perl module, or you can install the p5-Net-3.10_1,1 package to get a slightly newer version of it. Net::SMTP has had SSL support capability since version 1.28 way back in 2014. You just need to have IO::Socket::SSL installed too. In the intervening 3 or so years, applications are meant to have been re-written to use Net::SMTP rather than Net::SMTP::SSL, but clearly this has not happened universally. Cheers, Matthew --lk6iNVbHamFxMBPL5xdwfW1ceA9GlIGdI-- --JnhH3BmcoMLeo3Mbf8Qb9guR9FeeTMpx1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJYUX/GXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTn5KYP/jn2ofPY3HAebt1BkxgmXatx /31CrgTxMZvUQMogAekBJqYVxXlB9nS2ISM6O2mWCMgYwmtCJfdr631iGXT4ERGn uTJ2UYIVmKIV7/Q5vqANhsunkxacYC31ZYHvqN3noBklsSXju9A0TxuXWu8viyto zWtCS9QWQPLEWuh6HBIgGROYICnJQdUiagYPoVX+lYG7gd8YwEbZxOrthLls0WGE 13S2EAQkkKxLdohtUxF3AquLFlvm4v+5RyjEV+VEizvCVbDkp4+5dabRkMGD+Dev e46iqJtJbQsvqCea37ilI8Sd4490n7l/o9krCdWNewF2m1bqT/xDGM6JyraLF55a 5s9iDVWJ4rW3Qphi0Xxhb919KugJJtHunWHYYLNvzLro+ZyLbsS5cSWHVtoSJhsK DQmx/Ja/GdZUxUD1CDW+GcrqDiXhUbaVQ2c9Vm+hPqd15qNF9ISXR5tPyyKVdKwy M3FMdUAgP0qblais37u7xI2R0J9TIE1GqzfW4f6bRlq+u71hyD0XBS6EyxVVaSat lfY6gmE43wfJQuDW3+BPUv3hMDstGwMq7ZbF9WMnHgJHfzgcJaKIjBYOltm3yoPb e3LLK3Br4wEH23rRx1pk5s69BUbkx0M9XaWiqe73FOzJfw3LTy0NvDaxB46qhPBs 6KxuZzXZ+b+atXbaoeWP =oXhu -----END PGP SIGNATURE----- --JnhH3BmcoMLeo3Mbf8Qb9guR9FeeTMpx1-- From owner-freebsd-ports@freebsd.org Wed Dec 14 19:35:18 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97A01C80272 for ; Wed, 14 Dec 2016 19:35:18 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7FF4B1A99 for ; Wed, 14 Dec 2016 19:35:17 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-230-194.lns20.per1.internode.on.net [121.45.230.194]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id uBEJZAAL046556 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 14 Dec 2016 11:35:13 -0800 (PST) (envelope-from julian@freebsd.org) Subject: Re: (In)Stability of the Quarterly Branch To: "Vlad K." , Freebsd Ports References: <3e7f94efc6428181a289742d7dd627df@acheronmedia.com> From: Julian Elischer Message-ID: <32224185-936b-adfa-9db1-a3c11c5bfc6c@freebsd.org> Date: Thu, 15 Dec 2016 03:35:05 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <3e7f94efc6428181a289742d7dd627df@acheronmedia.com> Content-Type: text/plain; charset=windows-1252; 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, 14 Dec 2016 19:35:18 -0000 Please add my voice to this.. It's not really that much that needs to be done. lets just call it 'learning from experience' Also, the quarterly PACKAGES should be kept around a bit longer too. and the pkg archives need to be in a layout that the system installer can be pointed at them in 4 years time when you want to rebuild a legacy machine. On 16/11/2016 8:17 PM, Vlad K. wrote: > The quarterly branch (Q) is intended to provide a set of "stable" > packages that in the lifetime of such a branch, receive only bug and > security fixes. That is the theory and intent behind the branch. In > practice, however: > > 1. The Q branch is cut off at predetermined dates (ie. not when it's > stable and ready), and it is cut off from HEAD, thus including the > state of ports at that moment. This breaks the promise of stability > and guarantees that every 3 months there will be uncertainty as to > whether the fresh new versions are working or not. There is no such > thing as a "Pre-Quarterly repo" which would receive all updates for > the NEXT Q branch-off, and which would freeze and stabilize for some > time before branch-off. And even if it did, 3 months would be too > short. > > It is effectively not much different from tracking HEAD and doing > updates only every three months, with the added benefit that SOME > security updates will come down sooner. But: > > 2. Unfortunately not all "security or bug-only fixes" are MFH'd, and > as a bugzilla triager I've had the opportunity to observe this in > practice. It can be as simple as accepting a minor upstream version > bump, or as complex as requiring cherry-picking and backporting code > if upstream mixes security, bug fixes with new features. It is > none-the-less a manual work requiring ports-secteam to review and > accept the patches. It is not clear who is supposed to do > cherry-picked backporting if the patches to HEAD cannot be MFH'd as > they are. It is also additional burden to the ports-secTEAM which at > the moment is, effectively, one person. In out current build environment at $JOB we check out every package we need in ports at it's own SVN revision. Usually that is defined to be a default, but sometimes in order to get a fully working set we need to slide a port or two forwards or backwards a bit. (and hope it doesn't hit a ports API change). (this means we really need to stay on head though) > > As it is obvious that the promise of a stable repo in its current > form requires manpower and manual work which we do not have, my > proposal is to abandon the promise of "security/bugfix" only changes > and adopt the approach not unlike Gentoo's, in which a "STABLE" > repository receives ALL the updates from HEAD, but only after > certain criteria has been met, like minimal age of changes, no open > issues, a certain battery of regression/integration/unit tests is > performed, etc... > > The key, I believe, is in automation which we can achieve with this, > and with that offer at least SOME level of stability without broken > promises. The key to this automation is no manual review, which can > only be achieved if we accept ALL changes, but stabilized to certain > degree. > > The idea of a "stable" repository is a valiant one, we definitely > need it if we want to increase the usage of FreeBSD in production as > more than just a base OS that does routing and ZFS storage -- namely > production use of stable ports. And IMHO we only need to balance > between how stable we can provide/guarantee it and what resources > and manpower we have available to do so. > > > What are the community's thoughts on this? > > From owner-freebsd-ports@freebsd.org Wed Dec 14 19:45:52 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 683C9C80722 for ; Wed, 14 Dec 2016 19:45:52 +0000 (UTC) (envelope-from jhs@berklix.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 524171291 for ; Wed, 14 Dec 2016 19:45:52 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 4EAAFC80721; Wed, 14 Dec 2016 19:45: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 4E51DC80720 for ; Wed, 14 Dec 2016 19:45:52 +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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E3BEC1290 for ; Wed, 14 Dec 2016 19:45:50 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (pD9FE9B3A.dip0.t-ipconnect.de [217.254.155.58]) (authenticated bits=128) by land.berklix.org (8.15.2/8.15.2) with ESMTPA id uBEJjkLG049661; Wed, 14 Dec 2016 19:45:47 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 uBEJji6n015688; Wed, 14 Dec 2016 20:45:44 +0100 (CET) (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 uBEJjPv5076115; Wed, 14 Dec 2016 20:45:38 +0100 (CET) (envelope-from jhs@berklix.com) Message-Id: <201612141945.uBEJjPv5076115@fire.js.berklix.net> To: "Akinori MUSHA" cc: ports@freebsd.org, "Julian H. Stacey" Subject: Re: No port should need root for make fetch 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 "Wed, 14 Dec 2016 17:37:24 +0900." <86y3zinby3.knu@iDaemons.org> Date: Wed, 14 Dec 2016 20:45:25 +0100 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, 14 Dec 2016 19:45:52 -0000 Hi Akinori MUSHA, Thanks for the thoughtful reply, I'll get back in a couple of days, I've been diverted. Cheers, Julian -- Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable. http://berklix.eu/brexit/#stolen_votes From owner-freebsd-ports@freebsd.org Wed Dec 14 19:52:20 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8100DC809F2 for ; Wed, 14 Dec 2016 19:52:20 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4838918B7; Wed, 14 Dec 2016 19:52:18 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject; s=201508; t= 1481745130; bh=m+/7JNuO6igcC/6/V1ECIJZDrlNh6uNJ9Wm2FJNtWsE=; b=M 1SJ2AH/2aXvZWswiAC11LcqKMwLxElJZmcRlyH021gSEsTZi7Ez1hYpatglSUfKX ml6QYQV19KMeocNznZXf91U/+QWtHYcLYA0BjXZg83FU/juwCoanzky+Yifq1vRM 9ZJz7M6r3cW4wg2aWLVdGphBh5LhnG5UCPpMpa7qwM= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 360D5111E5; Wed, 14 Dec 2016 14:52:10 -0500 (EST) Subject: Re: qt5-webkit fails to build [solved] To: Raphael Kubo da Costa References: <026c0a40-931b-2cb3-e8c4-f39bb8a34588@protected-networks.net> <86wpfuw7z2.fsf@FreeBSD.org> <86a8cjzrho.fsf@FreeBSD.org> Cc: FreeBSD Ports From: Michael Butler Message-ID: Date: Wed, 14 Dec 2016 14:52:08 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; 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, 14 Dec 2016 19:52:20 -0000 On 11/28/16 17:27, Michael Butler wrote: > Yes - built from -current source, > > Sent from my iPhone > >> On Nov 29, 2016, at 00:03, Raphael Kubo da Costa wrote: >> >> Michael Butler writes: >> >>> /usr/lib/libgcc_s.so: error: undefined reference to 'free' >>> /usr/lib/libgcc_s.so: error: undefined reference to '__assert' >>> /usr/lib/libgcc_s.so: error: undefined reference to 'fwrite' >>> /usr/lib/libgcc_s.so: error: undefined reference to 'fflush' >>> /usr/lib/libgcc_s.so: error: undefined reference to 'malloc' >>> /usr/lib/libgcc_s.so: error: undefined reference to '__stderrp' >>> /usr/lib/libgcc_s.so: error: undefined reference to 'snprintf' >>> /usr/lib/libgcc_s.so: error: undefined reference to 'fprintf' >>> /usr/lib/libgcc_s.so: error: undefined reference to 'memcpy' >>> /usr/lib/libgcc_s.so: error: undefined reference to 'abort' >>> /usr/lib/libgcc_s.so: error: undefined reference to 'memset' >>> /usr/lib/libgcc_s.so: error: undefined reference to 'getenv' >>> /usr/lib/libgcc_s.so: error: undefined reference to 'dladdr' >>> /usr/lib/libgcc_s.so: error: undefined reference to 'mprotect' >> >> This looks unrelated to qt5-webkit; are you building your own world? It seems that more than just the QT5 module with the version bump (or qt5-gui) needs to be recompiled. It appears to be fixed by .. portupgrade -f icu-\*; portupgrade -f qt5-\* Michael From owner-freebsd-ports@freebsd.org Wed Dec 14 21:58:13 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03781C800E8 for ; Wed, 14 Dec 2016 21:58:13 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A99DF75F for ; Wed, 14 Dec 2016 21:58:12 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-qk0-x234.google.com with SMTP id n21so36738601qka.3 for ; Wed, 14 Dec 2016 13:58:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jHty6pRFACTfOrOHZ772hQU8hCpryln99kmumudpulk=; b=BuLUeH9vwPUUHn3Z7Ne8txMSmYmmHoHP3jwwzvRrNSED1MSjsz5RpxajvPHvMta9nD 297cgf5yv3kK0yweTTaJUVfGmpeDNbBBDnAhYccYER3UtFtUrXqsG0xXNDql8fqSRhD5 zMmld1laLpBStTANEhDSRWxKe1sGmvWGFvS+qbidNbqe8jm+wYT0bYHnxqdk/7EkKSvT 6LdzoTtdPjpoYCh+wDmGNgD2MclHmjemrZxM9uVWLepc/4nEKCh+3pgHNuqXSp6fGQje vmQ8fXVj5+3iOCT/mCbqzqOENWT3PJgiOt60bv6avjW99DagOKedKnNYMVpd9v7Bq7Lt fgeA== 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=jHty6pRFACTfOrOHZ772hQU8hCpryln99kmumudpulk=; b=kxccLZgc4+PpLON40euwWnQO7ilwg7rxvgrnATzeB+o5BvVOhxtqhZTgFaO4M0BQoi MqihFvkUkYNymmlDaquo7C2hPlOFk7Z6jclJAIifnRv6xBGzzQrFdTKALgFv4wQ9dwm5 UytUSAayxC6ZZXsMsdm6qWEO4QJPT9VAUe3elZvLxaHEk8B7sdnNGSdkdztzy0SfRJoJ z6KJ0CbVFtLGkiTWCah2knr1b3thGElfqTO0JlUmPM8TLWCSMFSoXx0ePaVEAsehAwfd 49zAqGOs5Tt5yMZ28fvNGiVqVzk+k9LaCuKFZQYaK6nm3Gt3BpaDeDAer3zurB4KazGf MmLg== X-Gm-Message-State: AKaTC01OmvOn4g6A+yjhO1uZA31zFpf5E9q1xlHcynBPSsDSo50QTNZ5dtcrZkx96O5Nkn5ePGlqazD+65N9VA== X-Received: by 10.55.112.65 with SMTP id l62mr42412977qkc.76.1481752691858; Wed, 14 Dec 2016 13:58:11 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.165.161 with HTTP; Wed, 14 Dec 2016 13:58:11 -0800 (PST) In-Reply-To: <96f44b17-b5a3-d24e-dee4-935d55a70019@gmx.de> References: <201612132135.uBDLZPVp017655@fire.js.berklix.net> <96f44b17-b5a3-d24e-dee4-935d55a70019@gmx.de> From: Freddie Cash Date: Wed, 14 Dec 2016 13:58:11 -0800 Message-ID: Subject: Re: No port should need root for make fetch To: Matthias Andree Cc: null 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: Wed, 14 Dec 2016 21:58:13 -0000 On Tue, Dec 13, 2016 at 2:01 PM, Matthias Andree wrote: > Am 13.12.2016 um 22:35 schrieb Julian H. Stacey: > > > >> How is that a problem of "some" ports? All ports require root for "mak= e > >> fetch" > > No they dont. > > Given that, then "none do". > > I'll do what what you omitted in your blind rage, I've dug the important > detail up for you, which was the first guess: > > $ grep _DEPENDS Makefile /dev/null > /usr/ports/databases/mysql-q4m/Makefile:FETCH_DEPENDS+=3D > ${NONEXISTENT}:${_MYSQL_SERVER}:build > > This doesn't say "give me root". It needs to be able to build the > requisite port. > Obviously the fix is to make sure that if you want to fetch as > unprivileged user, that you can also *build*. > I assume that if you want *fetch* as unprivileged user, that you also > want to *build* as unprivileged user, so I'd take that for granted, but > it's not the case on your system. > > On my system, which has a WRKDIRPREFIX that I am permitted to write to > with the unprivileged user account doing the builds, "make fetch" for > mysql-q4m passes without a hitch. > > > Thanks for the well intentioned & good advice Matthias, > > But some few ports are truly Badly Behaved with make fetch. > > Can you cite chapter and verse of the rule that makes such a port "truly > Badly Behaved", for reference in this list's archives? =E2=80=8B =E2=80=8BI guess the =E2=80=8Bbetter question would be, why does one need to BUILD a port when just downloading the sources for another port? Shouldn't the fetch process be just that ... downloading the sources into the DISTDIR?=E2=80=8B =E2=80=8B =E2=80=8BRegardless of which user you do things as, it just seems bizarre t= hat you would need to compile port X in order to fetch the sources for port Y. Not saying there's never a situation where that would be needed, it just seems non-intuitive.=E2=80=8B I can see situations where you'd want to fetch dis= tfiles ahead of time as a different user from the one used to build the ports, where this behaviour could break things (like Julian discovered). What does the a compiled mysql-server port provide that's needed to download the sources for mysql-q4m? That can't be put off until the build phase? --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-ports@freebsd.org Wed Dec 14 22:03:56 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A9E1C803AC for ; Wed, 14 Dec 2016 22:03:56 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id DD8BAC70 for ; Wed, 14 Dec 2016 22:03:55 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id DA184C803AB; Wed, 14 Dec 2016 22:03:55 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D802FC803AA for ; Wed, 14 Dec 2016 22:03:55 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8D88CC6F for ; Wed, 14 Dec 2016 22:03:55 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-qt0-x22d.google.com with SMTP id c47so39130699qtc.2 for ; Wed, 14 Dec 2016 14:03:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gbxefqnG2IAqgBjoGskO7gjhONXC6lmANM8pW4t3D3M=; b=I8wVBHxPXiXKczhc1Ye4JeVcu1Dn/LwGv5+jwLEMwFAfv4ADZjogoQgC9O5eAkwDqA bJL2h87Mv2K9ZaUIDr7Use0gsPtfxp8ayD5CNZKZr+XTodGnCmmwrwt/+XV6e65utDf8 ZPy2GrooarYXQQMACHK/7r2r9V9gmnCF9Ena+nM96MzSBtBBTcEJeLTvvN1Qp5yqURg8 tX0FTQG6q0ZGqHSYvwTldg7fE/zp+8P+a2vkFVRDK9zw31Csg1sjM8ifnCEYoQOureKU ilMwkIHFVpSWb5egZ832CvrXZSzFtuEqJ82ocDOSP2sEgxjaVPB8xOxtXYhv9dPANQ4i uUnQ== 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=gbxefqnG2IAqgBjoGskO7gjhONXC6lmANM8pW4t3D3M=; b=HjocwlKYCVAtOdznNbjuvEl2udoAL+FkxDn6k6FuIpd4osdFnmMMZl7xp8oDcpBjAl pwjKBpMvzlQwLhP0j8XKMmhdSkafQ/tjvKv6u4xt5iKFolmbHiLh5FE6/0NqeWy6CZYV GzqFG5GK5YRfBJJpIK+D4iWjXrKD0jdtWK/EJr+Yhfkz75HHT0VrDsPXmSlNQOj63vkk tF5LZzsKlZ1OTL5jst3EYjF7dRG0QGCQDWbT0K/lnbWrGzpcVkizLhwkirD9EXV3aZqw NrZYPTruuZttgczhd3Cz5TeGQ91me/tM+L3gcKTDOyKv0y3WVle+HF7KQtPUCgoB9Us4 ohSA== X-Gm-Message-State: AKaTC00gLSBsTtVM/d2CHWrktwopNzuCOLiduS6ag3GdG5ttVln7G/K4zIQjLvpl8tVoS+YL4K/5ZAhJQiuqLQ== X-Received: by 10.237.61.202 with SMTP id j10mr100412129qtf.121.1481753034815; Wed, 14 Dec 2016 14:03:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.165.161 with HTTP; Wed, 14 Dec 2016 14:03:52 -0800 (PST) In-Reply-To: <86y3zinby3.knu@iDaemons.org> References: <201612132032.uBDKWaVK017178@fire.js.berklix.net> <86y3zinby3.knu@iDaemons.org> From: Freddie Cash Date: Wed, 14 Dec 2016 14:03:52 -0800 Message-ID: Subject: Re: No port should need root for make fetch To: Akinori MUSHA Cc: "Julian H. Stacey" , FreeBSD Ports Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 22:03:56 -0000 On Wed, Dec 14, 2016 at 12:37 AM, Akinori MUSHA wrote: > Hi, > > Thanks for the info. > > On Wed, 14 Dec 2016 05:32:36 +0900, > Julian H. Stacey wrote: > > Hi ports@ > > IMO No port should need root for > > cd /usr/ports; make -i fetch > > The first one that broke for me was databases/mysql-q4m > > (OK might be others before, but I have DUDS =3D > > arabic biology chinese hebrew hungarian japanese korean > > polish portuguese russian ukrainian vietnamese games demime > > majordomo acroreadwrapper acroread9 chimera dosbox emil > > firefox freerdp gimp-app gv libcue mp3splt-gtk nut opera > > ripit vlc xorg xsane > > ) > > (MAINTAINER CC'd) but there's more ports beyond, usually because > > some ports also go berserk & install, or mabe install dependents. > > Having the dependency as FETCH_DEPENDS [*] was not my idea, but that > was for a reason: you should not fetch a file while building a port. > > * https://svnweb.freebsd.org/ports/head/databases/mysql- > q4m/Makefile#rev297196 =E2=80=8BShouldn't this be split into two, then? =E2=80=8BFETCH_DEPENDS+=3D ${NONEXISTENT}:${PORTSDIR}/databases/mysql${MYSQL_VER}-server:fetch BUILD_DEPENDS+=3D ${NONEXISTENT}:${PORTSDIR}/databases/mysql${MYSQL_VER}-server:build =E2=80=8BThat way, only the fetch target is run on the mysql-server port wh= en running the fetch target on the mysql-q4m port. And the build target is run on the mysql-server port when the build target is run on the mysql-q4m port. Or is there no :fetch support in the _DEPENDS framework?=E2=80=8B --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-ports@freebsd.org Wed Dec 14 22:07:26 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AAAD7C804E8 for ; Wed, 14 Dec 2016 22:07:26 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 754C4EB0 for ; Wed, 14 Dec 2016 22:07:26 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-io0-x22b.google.com with SMTP id h30so52939028iod.2 for ; Wed, 14 Dec 2016 14:07:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=e5c6Ph5XUigYgdTOKhwDpuuzo7u3o8F7nDdJe9KGkE4=; b=BCWlPPwripwtir/wAEQY2BWPXo3WEc+/xzdMhUi6Sfws3AXqsBIf6vWZ7pFLhwDHK6 EwvhEwERxRAO0s1WUQzqtqPwQoeBSBBsQ2i3r+s7SbHt9P4V19S1lI/y0MKlO0b+UEUU 7LzU9/04tZDr+bTRNhszDA7Icd2y/uBALUQE2w0JXy4PHeptgATsBca7NVgi93H2NPTN zL7QwTHOE/FYgm4+pChuuy/OgTM3dRue+ywoxIk0hcaeaYHLzqsehfn2VXlTL8W7Pq0m RuzEDCVES6fgKnkdhpnpHcAbRZLyT4bOCy2b2CymZnfsTxlIFHpepySjOZMa4cH3mX+h iCIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=e5c6Ph5XUigYgdTOKhwDpuuzo7u3o8F7nDdJe9KGkE4=; b=PACl4RyM29iA4G1jiawXsw4vI2jI42ykak/Z8VRP718irA6cd985WUmpwuVqCP1Lri 8BTylcG584SNlO0F3f+2+Tcmd2T1tSl9kexbgBf+K094pKtw4KizTAtgOT9Budypx9ih Sy8BprtanVGxfPRFx9zI4oTUAPH/VFGiOs1h8BGSDidjEOQZPoYwofnMJ7yM354iAVHp SrEOdI7ZC1PPFQGfNKVSQ4LOh3WKZTE9mbvqHVMDolrbYs2FxEY/ZP9fQChzeuPvm0aa TbHh65WVgDKWPQ5BRLDXU5p8M+ursbOuUfE98fJTo6za9JyIaboxtclryL6UH+hVAAaL F7wA== X-Gm-Message-State: AKaTC00FVVoLkMK6lu6T7YANZyGsdX1qwlMIV3EwuEdXXk/rFrahcIQxW8p4LcZ4xPNNsNeMZsbhbFlHDnkQZw== X-Received: by 10.107.57.131 with SMTP id g125mr63049094ioa.108.1481753245899; Wed, 14 Dec 2016 14:07:25 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ben Woods Date: Wed, 14 Dec 2016 22:07:15 +0000 Message-ID: Subject: Re: Optional circular dependency between multimedia/ffmpeg and audio/chromaprint To: Luca Pizzamiglio , freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 22:07:26 -0000 On Wed., 14 Dec. 2016 at 5:16 pm, Luca Pizzamiglio < luca.pizzamiglio@gmail.com> wrote: > Today I discovered a circular dependency: > > > > if multimedia/ffmpeg has the chromaprint option enabled, then it needs > > audio/chromaprint > > audio/chromaprint always needs multimedia/ffmpeg > > > > Using portmaster, I was unable to update both of them. > > At the moment, I remove the option in multimedia/ffmpeg, but I don't a > > better solution. > Hi Luca, It looks like ffmpeg is already marked as broken if the chromaprint option is enabled. This option was only added during the recent update to ffmpeg3 a few days ago, so it has always been marked as broken. It is disabled by default also. Do you need this functionality for something you are doing? I haven't looked into how it could be possible to break the loop to allow it to be enabled sorry. Regards, Ben From owner-freebsd-ports@freebsd.org Thu Dec 15 06:50:13 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5186C8113D; Thu, 15 Dec 2016 06:50:13 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: from mail.hs.ntnu.edu.tw (mail.hs.ntnu.edu.tw [140.131.149.3]) (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 751F61282; Thu, 15 Dec 2016 06:50:12 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: by mail.hs.ntnu.edu.tw (Postfix, from userid 800) id 9D9A81C6473; Thu, 15 Dec 2016 14:50:03 +0800 (CST) Received: from abeing (IP-215-9.cs.nctu.edu.tw [140.113.215.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: iblis@hs.ntnu.edu.tw) by mail.hs.ntnu.edu.tw (Postfix) with ESMTPSA id 0E3371C644F; Thu, 15 Dec 2016 14:49:55 +0800 (CST) Date: Thu, 15 Dec 2016 14:49:49 +0800 From: Iblis Lin To: freebsd-ports@FreeBSD.org Cc: freebsd-numerics@FreeBSD.org Subject: Re: lang/julia call for testing Message-ID: <20161215064948.GA35400@abeing> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) X-Bogosity: Ham, tests=bogofilter, spamicity=0.499888, version=1.2.4 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, 15 Dec 2016 06:50:13 -0000 Hi, I just found the official doc points to gcc6 as one of depends: https://github.com/JuliaLang/julia#freebsd Julia only use the fortran compiler in gcc, do not need the c compiler. But seems the Uses/fortran.mk do not accept any argument to change the gcc version. If I change the gcc version via USE_GCC=6, it changes CC as well. As previous remarks, Julia only need the fortran compiler of gcc. There are some side effects that we do not want from USE_GCC. I think this is a flaw in ports framework. Any idea? -- Iblis Lin 林峻頤 On Thu, Dec 15, 2016 at 12:03:16AM +0800, Iblis Lin wrote: > Hi, > > The PR on bugzilla is here: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215297 > > And here is the repo of the port: > https://github.com/lwhsu/freebsd-ports-lang-julia > > (Thanks to patient guidance from lwhsu@ !) > > Some notes about options: > By default, the GPL_LIBS will not be enabled, this cause some > fft related function not working. > If we enable the GPL_LIBS, the version of math/suitespare in > our ports is too old, it will make tons of function reveal > warning. Need help for update suitespare. > > If you are interested in this port, please help on testing. > To be honest, I am not a developer of julia and even cannot write > any julia code (maybe was able to write few). I started to port it, > just because I need to write machine learning homework in my university > course. :p There is also lots of math libs julia required, and I still > cannot understand the complex relationship of them at all > , e.g. tons of Xblas, LAPACK ... etc. If I pin the wrong depends in > Makefile, please comment. Or, one can be replaced by another one, > please comment, also. I will try to add OPTIONS. > > About the `make test`, I still got some mmap testing failure on my box. > Maybe we can discuss them first. Then, upstream to julia's github > issue tracker. > > -- > Iblis Lin > 林峻頤 > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Thu Dec 15 08:43:57 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6642AC7573C for ; Thu, 15 Dec 2016 08:43:57 +0000 (UTC) (envelope-from mat@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 4902E1BB5 for ; Thu, 15 Dec 2016 08:43:57 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 48547C7573B; Thu, 15 Dec 2016 08:43:57 +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 47F36C75737 for ; Thu, 15 Dec 2016 08:43:57 +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 D22771BB4 for ; Thu, 15 Dec 2016 08:43:56 +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 66E05BDCAC; Thu, 15 Dec 2016 09:43:53 +0100 (CET) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) (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 2EC83BDC77; Thu, 15 Dec 2016 09:43:53 +0100 (CET) Subject: Re: No port should need root for make fetch To: Peter Jeremy , "Julian H. Stacey" References: <201612132032.uBDKWaVK017178@fire.js.berklix.net> <20161214051706.GS61036@server.rulingia.com> Cc: ports@FreeBSD.org From: Mathieu Arnold Organization: Absolight / The FreeBSD Foundation Message-ID: <05247bf0-d31e-6a88-57ab-69687f5f1af1@FreeBSD.org> Date: Thu, 15 Dec 2016 09:43:51 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161214051706.GS61036@server.rulingia.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="DGSU3oBxEObQfJgphgOxw3rKcgIQc3tac" 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, 15 Dec 2016 08:43:57 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --DGSU3oBxEObQfJgphgOxw3rKcgIQc3tac Content-Type: multipart/mixed; boundary="dOnQHIf4atvvsNDlGRoClUg5hVpGItq5f"; protected-headers="v1" From: Mathieu Arnold To: Peter Jeremy , "Julian H. Stacey" Cc: ports@FreeBSD.org Message-ID: <05247bf0-d31e-6a88-57ab-69687f5f1af1@FreeBSD.org> Subject: Re: No port should need root for make fetch References: <201612132032.uBDKWaVK017178@fire.js.berklix.net> <20161214051706.GS61036@server.rulingia.com> In-Reply-To: <20161214051706.GS61036@server.rulingia.com> --dOnQHIf4atvvsNDlGRoClUg5hVpGItq5f Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Le 14/12/2016 =C3=A0 06:17, Peter Jeremy a =C3=A9crit : > On 2016-Dec-13 21:32:36 +0100, "Julian H. Stacey" wro= te: >> IMO No port should need root for=20 >> cd /usr/ports; make -i fetch > In a stock FreeBSD install, all ports require root to both fetch and bu= ild. > You have customised your system in a non-standard way so you are gettin= g > non-standard behaviour which doesn't match you expectations. That is plain not true. The numbers of ports that need root to fetch and build can be counted on one hand, and need to be fixed. We have QAT builds that check it: http://package19.nyi.freebsd.org/build.html?mastername=3D103i386-default-= build-as-user&build=3D428533 poudriere-devel defaults as doing everything as a non root user (default nobody), except executing all the -depends target, as they need to install stuff in LOCALBASE. --=20 Mathieu Arnold --dOnQHIf4atvvsNDlGRoClUg5hVpGItq5f-- --DGSU3oBxEObQfJgphgOxw3rKcgIQc3tac 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 iQJ8BAEBCgBmBQJYUlfIXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IIdcP/1L23tsQb8pPWitEvoXEFsxi O/FWuo01fUfSnB3XiuVL4VadE1OnBxblLeWXxrZ7acdRkS0XpYWeX5qB3WUyLzOf EBPEt2SxnK5xM3YjzY76U1BBfJWhnqQ59IVRyYYn0D7ynKm/Mgo74vYrMzdWd5Qv 2h79eA/fPzwRkNdCzuo/iF3qmsLG0GQc5/zoZMQttvvH9osj+fmqKImi5ZFAmmWz SWC8hTIjXa0PnkcE4kCfMmWLcLHg0c6AzqQLTKVCa7vVDgAO1usi6zuEw5ZWSVje aKgwFfIrWM80r+/MxfwOks+r3Ufxr03QpIzbBdLqfYQSYE+kY8bAVPG+rjuU8aGK ooRrhaMVuYmWlDr/9Kh/JAy08JJYGddHmUZwY2Nt3s2ugWt3v91l4SysTI06od+i O9LT+3HYrQOTEDDjtVDFE2aBJhInt2dlkj0db1CdPJR7jRUrLffk4E0ErQhPGb/M fMI0zT4RWmfQI2LSbt+ymc0gP7zRrWFP4RhcOyJoGSc7HoD/ezMKrD05POhJQJDX CuEmDH0CbK4AidMRc6dT7TlQiEUo54vc8HXYfmurW57Oj0KEt68z29+GA119/IF1 VbWWjFJvOTHNgAevx5aX1w7LAqcK5lfkz5o7YD8GbdL4YaxK865/7VI9YkC5bGwn QJ1tS+1EnrCVmhiaIA7+ =vf6T -----END PGP SIGNATURE----- --DGSU3oBxEObQfJgphgOxw3rKcgIQc3tac-- From owner-freebsd-ports@freebsd.org Thu Dec 15 09:05:14 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0044C802D2 for ; Thu, 15 Dec 2016 09:05:14 +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 BD932C6C for ; Thu, 15 Dec 2016 09:05:14 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id BD07EC802CF; Thu, 15 Dec 2016 09:05:14 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCB85C802CE for ; Thu, 15 Dec 2016 09:05:14 +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 AFFE8C6B for ; Thu, 15 Dec 2016 09:05:14 +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 uBF95EpR010066 for ; Thu, 15 Dec 2016 09:05:14 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id uBF95E3l010065; Thu, 15 Dec 2016 09:05:14 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201612150905.uBF95E3l010065@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, 15 Dec 2016 09:05:14 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2016 09:05:14 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/libthai | 0.1.25 | 0.1.26 ------------------------------------------------+-----------------+------------ math/giacxcas | 1.2.2-57 | 1.2.2-105 ------------------------------------------------+-----------------+------------ net/ipsumdump | 1.85 | 1.86 ------------------------------------------------+-----------------+------------ 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 Dec 15 11:24:15 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 200D4C8120B for ; Thu, 15 Dec 2016 11:24:15 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from avasout08.plus.net (avasout08.plus.net [212.159.14.20]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 85AC81EE9 for ; Thu, 15 Dec 2016 11:24:13 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from curlew.milibyte.co.uk ([80.229.31.82]) by avasout08 with smtp id LBM01u0091mJoLY01BM1FU; Thu, 15 Dec 2016 11:21:02 +0000 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.2 cv=CYdK3/jl c=1 sm=1 tr=0 a=cd0K7rcWwnZFf6xQxRobyA==:117 a=cd0K7rcWwnZFf6xQxRobyA==:17 a=KsS_0DhyHCIA:10 a=kj9zAlcOel0A:10 a=MKtGQD3n3ToA:10 a=n5n_aSjo0skA:10 a=dik7HMQjudEA:10 a=ZZnuYtJkoWoA:10 a=6I5d2MoRAAAA:8 a=mv93vHV62QyxF2n6gRgA:9 a=CjuIK1q_8ugA:10 a=82-kyh_VXv8A:10 a=IjZwj45LgO3ly-622nXo:22 Received: from curlew.lan ([192.168.1.13]) by curlew.milibyte.co.uk with esmtp (Exim 4.87) (envelope-from ) id 1cHU5s-0008wv-0w for freebsd-ports@freebsd.org; Thu, 15 Dec 2016 11:21:00 +0000 Date: Thu, 15 Dec 2016 11:20:59 +0000 From: Mike Clarke To: freebsd-ports@freebsd.org Message-ID: <20161215112059.25e72af9@curlew.lan> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 Subject: Make index fails with no entry for /usr/ports/audio/linux-c7-mikmod Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) 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, 15 Dec 2016 11:24:15 -0000 curlew:/root# freebsd-version -ku 11.0-RELEASE-p2 11.0-RELEASE-p5 curlew:/root# make -C /usr/ports index Generating INDEX-11 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- [snip] --- describe.x11-toolkits --- --- describe.x11-wm --- make_index: /usr/ports/games/linux-uplink-demo: no entry for /usr/ports/audio/linux-c7-mikmod curlew:/root# ls -l /usr/ports/audio/linux-c7-mikmod ls: /usr/ports/audio/linux-c7-mikmod: No such file or directory https://www.freebsd.org/cgi/ports.cgi?query=linux-c7-mikmod&stype=all reports nothing found so what's causing make index to try to index it? -- Mike Clarke From owner-freebsd-ports@freebsd.org Thu Dec 15 13:16:20 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 060B0C81B65 for ; Thu, 15 Dec 2016 13:16:20 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-ua0-x234.google.com (mail-ua0-x234.google.com [IPv6:2607:f8b0:400c:c08::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 B415E893 for ; Thu, 15 Dec 2016 13:16:19 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: by mail-ua0-x234.google.com with SMTP id 12so6683770uas.2 for ; Thu, 15 Dec 2016 05:16:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gBWZbVUf25oEdR/Bjxjd6Ps13zv1IiPs4MmjdDPA6yc=; b=iQdkXsQVzAcaa7cxz/IbpiGdtavBoCP/OHF/n9SaVMS+A9dxsB4V6ywJ2Bghwh+SNR bLTVybD8Dn4nKwgTflGbepeC2RTszf3mBiC3WzS2L10S0yEg6S5QuNwHSez2XmyONT3Y CjSB5c5YfMfEk+92SlUpTyfB0HDj4g8dPKGUZUOAfvf167db9ef9I8UyT7FnEfN7bFHw epJNIi4fXVWWd6KpmqvH3KUL9asd3f9bQg/qkQ1ivMlQrQKqyvcGiPvpz0QkmgO6wQkF VwApXHNBtrdZL2IPTrNPzDBHJxEBmAZ4L/qGEOtRSbF+7VpuSCDcJ/JRn44PWkdiRdgW SwgA== 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=gBWZbVUf25oEdR/Bjxjd6Ps13zv1IiPs4MmjdDPA6yc=; b=oBlk/fahO0S79Z8nNRRLio3Vl5SNQAH6wB/7x90JMym5U1xIwbWtw2r0xviK51YMqW dv6Aj3c8dqIG6B80vu1B8nvbLOKbkcS7Au9juX8INTxKMCPV4krq49ffLFCgCmL5vByl Yqk7I39GW8s1KPSjphzBNzo/gZ6x6GXhxVQcJRHigm5EjpaX1s1WFwaAhvoc4baG46Cn t0jAKTsDk4NPqATukMqWwShfDCae9UJOvlahxO2d0n+bIUhsrObq7npmx+U5+6ui6k1T TsjdUHp2sISXgAIXh4bORVssbxJXqBC/Mn13famNqaGBc71LekZn4yoOjwFp+s1Vxz2s whKA== X-Gm-Message-State: AKaTC007OHJ/MKt1Dv48AkAUv/QiPzkSVy9Rsw71rzAVBnjhNk2q2GiPP0Q6gnYtK2pDY5n0Gzf2t8dG6AuYdA== X-Received: by 10.176.2.247 with SMTP id 110mr976514uah.162.1481807778676; Thu, 15 Dec 2016 05:16:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.103.47.83 with HTTP; Thu, 15 Dec 2016 05:16:18 -0800 (PST) In-Reply-To: <3e7f94efc6428181a289742d7dd627df@acheronmedia.com> References: <3e7f94efc6428181a289742d7dd627df@acheronmedia.com> From: David Demelier Date: Thu, 15 Dec 2016 14:16:18 +0100 Message-ID: Subject: Re: (In)Stability of the Quarterly Branch To: "Vlad K." Cc: Freebsd Ports Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2016 13:16:20 -0000 2016-11-16 13:17 GMT+01:00 Vlad K. : > The quarterly branch (Q) is intended to provide a set of "stable" packages > that in the lifetime of such a branch, receive only bug and security fixes. > That is the theory and intent behind the branch. In practice, however: > > 1. The Q branch is cut off at predetermined dates (ie. not when it's stable > and ready), and it is cut off from HEAD, thus including the state of ports > at that moment. This breaks the promise of stability and guarantees that > every 3 months there will be uncertainty as to whether the fresh new > versions are working or not. There is no such thing as a "Pre-Quarterly > repo" which would receive all updates for the NEXT Q branch-off, and which > would freeze and stabilize for some time before branch-off. And even if it > did, 3 months would be too short. > > It is effectively not much different from tracking HEAD and doing updates > only every three months, with the added benefit that SOME security updates > will come down sooner. But: > > 2. Unfortunately not all "security or bug-only fixes" are MFH'd, and as a > bugzilla triager I've had the opportunity to observe this in practice. It > can be as simple as accepting a minor upstream version bump, or as complex > as requiring cherry-picking and backporting code if upstream mixes security, > bug fixes with new features. It is none-the-less a manual work requiring > ports-secteam to review and accept the patches. It is not clear who is > supposed to do cherry-picked backporting if the patches to HEAD cannot be > MFH'd as they are. It is also additional burden to the ports-secTEAM which > at the moment is, effectively, one person. > > As it is obvious that the promise of a stable repo in its current form > requires manpower and manual work which we do not have, my proposal is to > abandon the promise of "security/bugfix" only changes and adopt the approach > not unlike Gentoo's, in which a "STABLE" repository receives ALL the updates > from HEAD, but only after certain criteria has been met, like minimal age of > changes, no open issues, a certain battery of regression/integration/unit > tests is performed, etc... > The problem is that there are no tests in FreeBSD ports. All source based systems I've tested: pkgsrc, FreeBSD ports, OpenBSD, Gentoo; FreeBSD is the one that have the most instability. Not to mention committers that commit without testing the port, just look at www/redmine to get your point of view on that issue. On the other hand, your idea is indeed good and could be a good start. Quaterly branches change too quickly. That's simple: each time I install a new port, I'm behind 2 or 3 quarters the last one. So I usually update all before installing the new one. What I want: a ports tree that matches the FreeBSD version like OpenBSD. You have FreeBSD 11.0? You get a ports tree for that version specifically. No major update, no breaking changes. Just bug fixes. That will also simplify a lot FreeBSD ports by not having thousands of conditional checking the FreeBSD version. Waiting for more stability, I really encourage people to use poudriere to build packages to avoid breaking a system at each upgrade. Regards, -- Demelier David From owner-freebsd-ports@freebsd.org Thu Dec 15 13:43:39 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E77C6C8190C for ; Thu, 15 Dec 2016 13:43: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 912F51B66 for ; Thu, 15 Dec 2016 13:43:39 +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 D8E5A1AAF011; Thu, 15 Dec 2016 14:43:30 +0100 (CET) Subject: Re: (In)Stability of the Quarterly Branch To: David Demelier , "Vlad K." References: <3e7f94efc6428181a289742d7dd627df@acheronmedia.com> Cc: Freebsd Ports From: Torsten Zuehlsdorff Message-ID: <2bd42508-a1f9-b0f2-e329-51af36604a45@toco-domains.de> Date: Thu, 15 Dec 2016 14:43:30 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; 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, 15 Dec 2016 13:43:40 -0000 On 15.12.2016 14:16, David Demelier wrote: > 2016-11-16 13:17 GMT+01:00 Vlad K. : >> The quarterly branch (Q) is intended to provide a set of "stable" packages >> that in the lifetime of such a branch, receive only bug and security fixes. >> That is the theory and intent behind the branch. In practice, however: >> >> 1. The Q branch is cut off at predetermined dates (ie. not when it's stable >> and ready), and it is cut off from HEAD, thus including the state of ports >> at that moment. This breaks the promise of stability and guarantees that >> every 3 months there will be uncertainty as to whether the fresh new >> versions are working or not. There is no such thing as a "Pre-Quarterly >> repo" which would receive all updates for the NEXT Q branch-off, and which >> would freeze and stabilize for some time before branch-off. And even if it >> did, 3 months would be too short. >> >> It is effectively not much different from tracking HEAD and doing updates >> only every three months, with the added benefit that SOME security updates >> will come down sooner. But: >> >> 2. Unfortunately not all "security or bug-only fixes" are MFH'd, and as a >> bugzilla triager I've had the opportunity to observe this in practice. It >> can be as simple as accepting a minor upstream version bump, or as complex >> as requiring cherry-picking and backporting code if upstream mixes security, >> bug fixes with new features. It is none-the-less a manual work requiring >> ports-secteam to review and accept the patches. It is not clear who is >> supposed to do cherry-picked backporting if the patches to HEAD cannot be >> MFH'd as they are. It is also additional burden to the ports-secTEAM which >> at the moment is, effectively, one person. >> >> As it is obvious that the promise of a stable repo in its current form >> requires manpower and manual work which we do not have, my proposal is to >> abandon the promise of "security/bugfix" only changes and adopt the approach >> not unlike Gentoo's, in which a "STABLE" repository receives ALL the updates >> from HEAD, but only after certain criteria has been met, like minimal age of >> changes, no open issues, a certain battery of regression/integration/unit >> tests is performed, etc... > > The problem is that there are no tests in FreeBSD ports. All source > based systems I've tested: pkgsrc, FreeBSD ports, OpenBSD, Gentoo; > FreeBSD is the one that have the most instability. Not to mention > committers that commit without testing the port, just look at > www/redmine to get your point of view on that issue. www/redmine is a special case like for example GitLab. This are ports based on rubygems and the ports-tree has a hard time to replicate the gems. When one port need an update for a specific gem another can break. Other systems avoid the problem by ignoring it. You need to install and maintain all gems by yourself. This includes updates, security checks and of course installation of dependencies. > On the other hand, your idea is indeed good and could be a good start. > Quaterly branches change too quickly. That's simple: each time I > install a new port, I'm behind 2 or 3 quarters the last one. So I > usually update all before installing the new one. > > What I want: a ports tree that matches the FreeBSD version like > OpenBSD. You have FreeBSD 11.0? You get a ports tree for that version > specifically. No major update, no breaking changes. Just bug fixes. > That will also simplify a lot FreeBSD ports by not having thousands of > conditional checking the FreeBSD version. That what i really, really, really NOT want. I have regular problems with our admins because of that. You want a specific version of an software? No problem: just install a specific version of your operation system. Need two of them, but they are not in this bundle? To bad, than you need a new server. This is an daily-base scenario i really don't want to port to FreeBSD. Yes, there are problems and tests are very helpful. But you need to check why something is broken. Often the upstream is broken, not the port. In the case of redmine the ports-tree lacks the pessimistic operator which can catch many of the breaks in the last. It is one idea to teach the ports-tree how this work. Also there is an ongoing effort in increasing the tests. Every help is appreciated! > Waiting for more stability, I really encourage people to use poudriere > to build packages to avoid breaking a system at each upgrade. This is a good idea. But does not help everytime. Many rubygem based ports build just fine, but fail afterwards. Greetings, Torsten From owner-freebsd-ports@freebsd.org Thu Dec 15 14:16:15 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28822C810AB for ; Thu, 15 Dec 2016 14:16:15 +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 E05B4CA6 for ; Thu, 15 Dec 2016 14:16:14 +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 1380228470; Thu, 15 Dec 2016 15:16:06 +0100 (CET) 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 14ADA28429; Thu, 15 Dec 2016 15:16:05 +0100 (CET) Subject: Re: (In)Stability of the Quarterly Branch To: Torsten Zuehlsdorff , David Demelier , "Vlad K." Cc: Freebsd Ports References: <3e7f94efc6428181a289742d7dd627df@acheronmedia.com> <2bd42508-a1f9-b0f2-e329-51af36604a45@toco-domains.de> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <5852A5A4.6070309@quip.cz> Date: Thu, 15 Dec 2016 15:16:04 +0100 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: <2bd42508-a1f9-b0f2-e329-51af36604a45@toco-domains.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2016 14:16:15 -0000 Torsten Zuehlsdorff wrote on 2016/12/15 14:43: >> The problem is that there are no tests in FreeBSD ports. All source >> based systems I've tested: pkgsrc, FreeBSD ports, OpenBSD, Gentoo; >> FreeBSD is the one that have the most instability. Not to mention >> committers that commit without testing the port, just look at >> www/redmine to get your point of view on that issue. > > www/redmine is a special case like for example GitLab. This are ports > based on rubygems and the ports-tree has a hard time to replicate the > gems. When one port need an update for a specific gem another can break. > > Other systems avoid the problem by ignoring it. You need to install and > maintain all gems by yourself. This includes updates, security checks > and of course installation of dependencies. First - I really appreciate your work on ports! And now Redmine - I think I was bitten by every Redmine failure after upgrade :) I wonder if the solution for ports like Redmine can be some kind of isolation. Python have virtualenv, AFAIK Ruby has something like this too. Will it be possible to connect ports (packages) with some type of "environment" defined just for "this package"? Miroslav Lachmanh From owner-freebsd-ports@freebsd.org Thu Dec 15 14:22:30 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 740EBC813E7 for ; Thu, 15 Dec 2016 14:22:30 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 26F241271 for ; Thu, 15 Dec 2016 14:22:29 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id uBFEMLBw066200 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 15 Dec 2016 07:22:21 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id uBFEMLfL066197; Thu, 15 Dec 2016 07:22:21 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Thu, 15 Dec 2016 07:22:21 -0700 (MST) From: Warren Block To: Daniil Berendeev cc: freebsd-ports@FreeBSD.org Subject: Re: The ports collection has some serious issues In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.1 (wonkity.com [127.0.0.1]); Thu, 15 Dec 2016 07:22:21 -0700 (MST) 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, 15 Dec 2016 14:22:30 -0000 On Thu, 8 Dec 2016, Daniil Berendeev wrote: > 5) svn repository. > I don't want to spark a holy war and I don't belong to those type of > people who are always obsessed that something isn't done in their way. > But guys, svn is not a good tool for ports. Just for one reason, > actually (as for me, I could tolerate anything else, but not this one) > -- size. The size of repository is 20G+ and growing. I don't want to > pull 20G+ in /usr/ports just because I need to use ports. It's just > sick. The repository is so big because, as all ya know, svn is expensive > in branch operations. Since you've began to do those 2xxxQx branches the > size of the repository began to grow rapidly. It's inefficient and > uncomfortable. For such a work something like git or mercurial should be > used, they'd fit in 3-4G. Here, it doesn't look like that. Don't forget that /usr/ports/distfiles accumulates old versions and must be manually cleaned out from time to time. portmaster has a couple of options to remove distfiles that are not needed. % du -hd0 /usr/ports 8.1G /usr/ports % du -hd0 /usr/ports/distfiles 6.5G /usr/ports/distfiles After copying that to /tmp and deleting distfiles entirely: % du -hd0 /tmp/usr/ports 1.4G /tmp/usr/ports Deleting /usr/ports/distfiles entirely is something I avoid because it seems that just when an urgent rebuild is needed, a distfile will be unfetchable. The portmaster options can keep distfiles only for currently installed ports, or current distfiles for any port, whether installed or not. From owner-freebsd-ports@freebsd.org Thu Dec 15 14:40:47 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D32FFC819C4 for ; Thu, 15 Dec 2016 14:40:47 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A39541A33 for ; Thu, 15 Dec 2016 14:40:47 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id uBFEekF8071040 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 15 Dec 2016 07:40:46 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id uBFEekJf071037; Thu, 15 Dec 2016 07:40:46 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Thu, 15 Dec 2016 07:40:46 -0700 (MST) From: Warren Block To: Matt Smith cc: Daniil Berendeev , freebsd-ports@FreeBSD.org Subject: Re: The ports collection has some serious issues In-Reply-To: <20161208085926.GC2691@gmail.com> Message-ID: References: <20161208085926.GC2691@gmail.com> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.1 (wonkity.com [127.0.0.1]); Thu, 15 Dec 2016 07:40:46 -0700 (MST) 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, 15 Dec 2016 14:40:47 -0000 On Thu, 8 Dec 2016, Matt Smith wrote: > On Dec 08 05:16, Daniil Berendeev wrote: >> >> Although portmaster is not releated to the FreeBSD project and is an >> outside tool, there aren't any alternatives from the project itself. So >> use it or die. Not a nice situation. > > People have been trying to get portmaster deprecated and removed from the > handbook but have met with resistance. Well, yes. Because it works, has no dependencies, and there is no equivalent replacement. Except maybe portupgrade, which has legacy problems like poor default options. > The recommended replacements are ports-mgmt/synth and ports-mgmt/poudriere. > These build an entire package repository that the pkg tool can use but they > do so in clean chrooted environments, and rebuild everything that's required > to keep a consistent ABI. Synth is more designed for a single live system > like a desktop or a single server, whereas poudriere is what the freebsd > package build clusters use and is more designed for that type of usage. Worth > taking a look. These are package builders. Technically preferable, given adequate disk space and memory, but not equivalent to portmaster. > It's a shame the handbook hasn't been updated to give this information. Which information, in particular? A section on Poudriere was submitted, and I spent a fair amount of time editing it and getting it in there. As far as Synth or other information, I'm not aware of any pending Handbook or other documentation submissions. From owner-freebsd-ports@freebsd.org Thu Dec 15 15:30:08 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F3FDC77883 for ; Thu, 15 Dec 2016 15:30:08 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (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 F27A0192C for ; Thu, 15 Dec 2016 15:30:07 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id 5E34D43BDE; Thu, 15 Dec 2016 09:28:51 -0600 (CST) Reply-To: marino@freebsd.org To: FreeBSD Mailing List , wblock@wonkity.com From: John Marino Subject: The ports collection has some serious issues Message-ID: <3959e18e-5819-b2c5-69a9-c71ce1282383@marino.st> Date: Thu, 15 Dec 2016 09:29:59 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161215-0, 12/15/2016), Outbound message X-Antivirus-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: Thu, 15 Dec 2016 15:30:08 -0000 > On Thu, 8 Dec 2016, Matt Smith wrote: > >> On Dec 08 05:16, Daniil Berendeev wrote: >>> >>> Although portmaster is not releated to the FreeBSD project and is an >>> outside tool, there aren't any alternatives from the project itself. So >>> use it or die. Not a nice situation. >> >> People have been trying to get portmaster deprecated and removed from the >> handbook but have met with resistance. > > Well, yes. Because it works, has no dependencies, and there is no > equivalent replacement. Except maybe portupgrade, which has legacy > problems like poor default options. Every single week, somebody falsely accuses the ports tree of being broken but the accuser is the only one with the problem. What do they all have in common? They are portmaster users. I'll iterate, saying "portmaster works" means applying a very generous definition of "works". >> The recommended replacements are ports-mgmt/synth and ports-mgmt/poudriere. >> These build an entire package repository that the pkg tool can use but they >> do so in clean chrooted environments, and rebuild everything that's required >> to keep a consistent ABI. Synth is more designed for a single live system >> like a desktop or a single server, whereas poudriere is what the freebsd >> package build clusters use and is more designed for that type of usage. Worth >> taking a look. > > These are package builders. Technically preferable, given adequate disk > space and memory, but not equivalent to portmaster. It's like saying git and svn are not equivalent to cvs. > >> It's a shame the handbook hasn't been updated to give this information. > > Which information, in particular? A section on Poudriere was submitted, > and I spent a fair amount of time editing it and getting it in there. > As far as Synth or other information, I'm not aware of any pending > Handbook or other documentation submissions. for starters: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214679 Previous PRs indicated that recommendations for portmaster and portupgrade were to be removed, but so far this PR has stalled. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-ports@freebsd.org Thu Dec 15 15:41:55 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE347C77CEF for ; Thu, 15 Dec 2016 15:41:55 +0000 (UTC) (envelope-from kayasaman@gmail.com) Received: from mail-wj0-x231.google.com (mail-wj0-x231.google.com [IPv6:2a00:1450:400c:c01::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 639C016A for ; Thu, 15 Dec 2016 15:41:55 +0000 (UTC) (envelope-from kayasaman@gmail.com) Received: by mail-wj0-x231.google.com with SMTP id tg4so69893556wjb.1 for ; Thu, 15 Dec 2016 07:41:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=1+wsZLcUtqP3LAteej8TPyA5kINuW8USnn+ulGMJ1RU=; b=bxhOAXxJ57J33syG9+LRD4SOmJq5dB1kajn15LMqcI2rmYG895VrrqETMgnlEbYtWC 9j0wievOsxX2ulMnQM1kbueHEIUwdjLZRzfbY47kLY/i+bp8FqQcBqli9zw4jAKdA+/X w7QNgfB1lJXCtGV3mmG/wUt1qHZ+8Da7skYBVLSU3MKTlXk9RcJJ3FchtljBV21pmQEy bvkY39fDiY4G+LqsR2PvuZNO4PF8n2he0Q8BddGWTMxJDbzTjKCQ4JyD8RBTUWvF+nFl jNGRdi8kdZsDSguHyq2GsOIgyaO2d9ZUm/ZruylBaqiWBAPEcozHgeLHBAjXOE7TKJWD kJEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=1+wsZLcUtqP3LAteej8TPyA5kINuW8USnn+ulGMJ1RU=; b=HZVA3UIYUH5gzZxmbcDS+Xr5UfgkE7bJwbMkOnCc5jgAp++LiSWh7QZoWxLXXf8E+C 9s8ltiZwFfpbKnFk0TVg0+3Wwpl/gsDgCSHzC2dv/j8KSSwBBvDxOhAfza68pdNcRM4K /+vsZ5MFdrIsy2RJ+y3UOBP76GjxXKkSO4tv/XRnkcu8jnMQYNcnZHfP9Cy2KkSDp1k2 MDVSBH1Kgz50AIx9pNpQS3rioVbBwt3okb5mQrNC04/2Ztfvcf6YUMdm+1HbJCC4F0Xv wqtNTWp8zqUs2PvXjfO81UpLQWJUo67tQYqx9fqNTAdeYXrZuopYIK0QW/Z+9a5q0BFw fQdw== X-Gm-Message-State: AKaTC033uvrEUbChHgPKNBjB3/YPRNaJg3QfoapLekIojzDbLutV7OVcebOqABILP+JtZQ== X-Received: by 10.194.141.141 with SMTP id ro13mr2080645wjb.76.1481816513598; Thu, 15 Dec 2016 07:41:53 -0800 (PST) Received: from x220.optiplex-networks.com (optiplexnetworks.plus.com. [212.159.80.17]) by smtp.googlemail.com with ESMTPSA id gj6sm2561777wjb.29.2016.12.15.07.41.52 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Dec 2016 07:41:52 -0800 (PST) To: freebsd-ports From: Kaya Saman Subject: munin-master won't build: no 'module_name' or MANIFEST file Message-ID: <880c9551-c45e-e0f3-40c8-5ac3851be39b@gmail.com> Date: Thu, 15 Dec 2016 15:41:52 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2016 15:41:55 -0000 Hi, I'm trying to rebuild munin-master but keep running into this: cd master && /usr/local/bin/perl Build.PL No 'module_name' was provided and it could not be inferred from other properties. This will prevent a packlist from being written for this file. Please set either 'module_name' or 'dist_version_from' in Build.PL. Can't find dist packages without a MANIFEST file Run 'Build manifest' to generate one WARNING: Possible missing or corrupt 'MANIFEST' file. Nothing to enter for 'provides' field in metafile. JSON::PP 2.27300 is not available at /usr/local/lib/perl5/site_perl/CPAN/Meta.pm line 616. gmake[1]: *** [Makefile:435: master/Build] Error 255 gmake[1]: Leaving directory '/usr/ports/sysutils/munin-master/work/munin-2.0.27' *** Error code 1 Stop. make: stopped in /usr/ports/sysutils/munin-master What can I do to fix it? It asks to run: Build manifest - but where do I run this? Many thanks. Kaya From owner-freebsd-ports@freebsd.org Thu Dec 15 15:49:58 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AEAB6C81047 for ; Thu, 15 Dec 2016 15:49:58 +0000 (UTC) (envelope-from tz@FreeBSD.org) Received: from toco-domains.de (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7C94C96F; Thu, 15 Dec 2016 15:49:58 +0000 (UTC) (envelope-from tz@FreeBSD.org) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id 812EA1AAF011; Thu, 15 Dec 2016 16:49:56 +0100 (CET) Subject: Re: The ports collection has some serious issues To: marino@freebsd.org, FreeBSD Mailing List , wblock@wonkity.com References: <3959e18e-5819-b2c5-69a9-c71ce1282383@marino.st> From: Torsten Zuehlsdorff Message-ID: Date: Thu, 15 Dec 2016 16:49:56 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <3959e18e-5819-b2c5-69a9-c71ce1282383@marino.st> Content-Type: text/plain; charset=windows-1252; 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, 15 Dec 2016 15:49:58 -0000 On 15.12.2016 16:29, John Marino wrote: >>>> Although portmaster is not releated to the FreeBSD project and is an >>>> outside tool, there aren't any alternatives from the project itself. So >>>> use it or die. Not a nice situation. >>> >>> People have been trying to get portmaster deprecated and removed from >>> the >>> handbook but have met with resistance. >> >> Well, yes. Because it works, has no dependencies, and there is no >> equivalent replacement. Except maybe portupgrade, which has legacy >> problems like poor default options. > > Every single week, somebody falsely accuses the ports tree of being > broken but the accuser is the only one with the problem. What do they > all have in common? They are portmaster users. I'll iterate, saying > "portmaster works" means applying a very generous definition of "works". Not really, no. Its not every week and often there is a misuse or miss-understanding of portmaster. With an argument like this you can also state there is every week a falsely accuse, because of poudriere. This would also be true (and is). >>> The recommended replacements are ports-mgmt/synth and >>> ports-mgmt/poudriere. >>> These build an entire package repository that the pkg tool can use >>> but they >>> do so in clean chrooted environments, and rebuild everything that's >>> required >>> to keep a consistent ABI. Synth is more designed for a single live >>> system >>> like a desktop or a single server, whereas poudriere is what the freebsd >>> package build clusters use and is more designed for that type of >>> usage. Worth >>> taking a look. >> >> These are package builders. Technically preferable, given adequate disk >> space and memory, but not equivalent to portmaster. > > It's like saying git and svn are not equivalent to cvs. I have a hard time to see git in this line. Its the way you use it. Yes, of course all three are code repositories. But one of them is a distributed repository and the other two are not. The differences are huge. Of course it also depends on your usage. I personally (means "heavily subjective) find git more than annoying. It lacks very important features (user management), is hard to use in automatic environments and make easy things (rename/delete branches) very hard. Other people really like all of this. It depends. So maybe the accusers just use the wrong tool? Greetings, Torsten From owner-freebsd-ports@freebsd.org Thu Dec 15 15:51:44 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D32ABC81276 for ; Thu, 15 Dec 2016 15:51:44 +0000 (UTC) (envelope-from rwmaillists@googlemail.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 B09FBB14 for ; Thu, 15 Dec 2016 15:51:44 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mailman.ysv.freebsd.org (Postfix) id AFEDDC81275; Thu, 15 Dec 2016 15:51:44 +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 AF8C6C81274 for ; Thu, 15 Dec 2016 15:51:44 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (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 44A39B11 for ; Thu, 15 Dec 2016 15:51:44 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wm0-x243.google.com with SMTP id u144so7295738wmu.0 for ; Thu, 15 Dec 2016 07:51:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=JiwCq6ab8Uy1wPX8iF6/gOK5uAfxyc0d6/iIMf4ZUNM=; b=YNqjqCtBRf80XF/bs5biM8wsoQttyOVF9iPd1WL2+2GKmapGim8ltLlKo9zdH1hZ/j ++Y4xIfUpwHTpJnbbjz8kaZ6BkZifqpKupIHAj27sGyPDwNt07/N7hQTI8s9WAAXybBY UFqllXSfyEoEGIEZ9SxVzCVhgxEsgiZ7DMjdcRwA8S9SCGB1Cr7u7+8Lnxay2fgfHfia B8ygEZ/S8sJ59bBfkHcjiebNcKtnc/xneJKzJz/yGKI6sluameVVa0xyNXcOXnmptYjC 9GSRU5RvU+YGOUCr0NfG8g/+id9tGK0TWuaTnLvPzL8387nnLOTr6nWSUiRig7Rgdl3O 4sCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=JiwCq6ab8Uy1wPX8iF6/gOK5uAfxyc0d6/iIMf4ZUNM=; b=KhO6ZRatV4TiO50hpC2vGw6Y0fQKb6yfbOp1QRbcLqgn0m5IlyhVIFw+d1kaN9a+4A 87pSNYHlc50pjJLidGRDienO3kPQVF1MlkJTH4Om4USuczHFbWcqLrVa8pQ7PiNcBzVq qvsUQ2uU7bUtOZbPobOFuU0D4guzYgj7Ypw26+DPoLLDtc+3ohSE8atVZjDHfxyECl7i xeiB5qa/j9ajJ846euR58wN4MFoXw9QMs0uIM9uOsB7+h1LUUCqRBvRIQOaIyFhHR+K0 2r27NZxUweJVBltjH/68e/p1jB+hPJPYs3evQbu2R7Dr2LiO9DjvsxH8ERKf1OgmGfSC 8Wgw== X-Gm-Message-State: AIkVDXIxlwk5tzT5vhqsJ+nOmmMCiZSGTKwecfbMW3la0DukP5dxcoNPFIHt+lNQCT8Oaw== X-Received: by 10.28.95.85 with SMTP id t82mr2029135wmb.56.1481817102114; Thu, 15 Dec 2016 07:51:42 -0800 (PST) Received: from gumby.homeunix.com ([81.17.24.158]) by smtp.gmail.com with ESMTPSA id cl6sm2612147wjc.10.2016.12.15.07.51.40 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 15 Dec 2016 07:51:41 -0800 (PST) Date: Thu, 15 Dec 2016 15:51:39 +0000 From: RW To: ports@freebsd.org Subject: Re: The ports collection has some serious issues Message-ID: <20161215155139.4a3d6033@gumby.homeunix.com> In-Reply-To: References: <20161208085926.GC2691@gmail.com> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2016 15:51:44 -0000 On Thu, 15 Dec 2016 07:40:46 -0700 (MST) Warren Block wrote: > On Thu, 8 Dec 2016, Matt Smith wrote: > > > On Dec 08 05:16, Daniil Berendeev wrote: > >> > >> Although portmaster is not releated to the FreeBSD project and is > >> an outside tool, there aren't any alternatives from the project > >> itself. So use it or die. Not a nice situation. > > > > People have been trying to get portmaster deprecated and removed > > from the handbook but have met with resistance. > > Well, yes. Because it works, has no dependencies, and there is no > equivalent replacement. Except maybe portupgrade, which has legacy > problems like poor default options. That's a very minor issue, and an absurd excuse to rule-out portupgrade. From owner-freebsd-ports@freebsd.org Thu Dec 15 16:00:47 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22530C8160A for ; Thu, 15 Dec 2016 16:00:47 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (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 D44D914FD; Thu, 15 Dec 2016 16:00:46 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id 2039243C1F; Thu, 15 Dec 2016 09:59:36 -0600 (CST) Subject: Re: The ports collection has some serious issues To: Torsten Zuehlsdorff , FreeBSD Mailing List , wblock@wonkity.com References: <3959e18e-5819-b2c5-69a9-c71ce1282383@marino.st> From: John Marino Reply-To: marino@freebsd.org Message-ID: <3cf805df-eb25-187c-8bf9-b6c2be5e977d@marino.st> Date: Thu, 15 Dec 2016 10:00:44 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161215-0, 12/15/2016), Outbound message X-Antivirus-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: Thu, 15 Dec 2016 16:00:47 -0000 On 12/15/2016 09:49, Torsten Zuehlsdorff wrote: > On 15.12.2016 16:29, John Marino wrote: >>>>> Although portmaster is not releated to the FreeBSD project and is an >>>>> outside tool, there aren't any alternatives from the project >>>>> itself. So >>>>> use it or die. Not a nice situation. >>>> >>>> People have been trying to get portmaster deprecated and removed from >>>> the >>>> handbook but have met with resistance. >>> >>> Well, yes. Because it works, has no dependencies, and there is no >>> equivalent replacement. Except maybe portupgrade, which has legacy >>> problems like poor default options. >> >> Every single week, somebody falsely accuses the ports tree of being >> broken but the accuser is the only one with the problem. What do they >> all have in common? They are portmaster users. I'll iterate, saying >> "portmaster works" means applying a very generous definition of "works". > > Not really, no. Its not every week and often there is a misuse or > miss-understanding of portmaster. It is every week. Consider the FreeBSD forums as well. "misuse" and "misunderstanding" failures are attributed to the tool. Let's stop making excuses for portmaster. It is what it is and we've had years to evaluate it. > With an argument like this you can also state there is every week a > falsely accuse, because of poudriere. This would also be true (and is). I couldn't state that accurately. I can't recall any misuse reports (and I can't come up with a feasible case in my head right now) > >>>> The recommended replacements are ports-mgmt/synth and >>>> ports-mgmt/poudriere. >>>> These build an entire package repository that the pkg tool can use >>>> but they >>>> do so in clean chrooted environments, and rebuild everything that's >>>> required >>>> to keep a consistent ABI. Synth is more designed for a single live >>>> system >>>> like a desktop or a single server, whereas poudriere is what the >>>> freebsd >>>> package build clusters use and is more designed for that type of >>>> usage. Worth >>>> taking a look. >>> >>> These are package builders. Technically preferable, given adequate disk >>> space and memory, but not equivalent to portmaster. >> >> It's like saying git and svn are not equivalent to cvs. > > I have a hard time to see git in this line. Its the way you use it. Yes, > of course all three are code repositories. But one of them is a > distributed repository and the other two are not. The differences are huge. > Of course it also depends on your usage. I personally (means "heavily > subjective) find git more than annoying. It lacks very important > features (user management), is hard to use in automatic environments and > make easy things (rename/delete branches) very hard. Other people really > like all of this. It depends. > > So maybe the accusers just use the wrong tool? The point is that you wouldn't start a new project with cvs. You may or may not transfer an existing project from cvs, but you're letting cvs die by attribution. The same should be for portmaster. Some users will never see the light. Let them suffer by their own hand. But for Pete's sake, don't recommend it to new users. That's not doing them any kind of service. Portmaster is not maintained. Since you put your name on it, you've made not a single commit to the repository, much less a new release. Yet there are PRs on it. Please, can we somehow discourage new people from starting on it? Anybody with a machine that doesn't have a resources to run poudriere or synth should not be building packages on that machine. Veterans have the option to use portmaster in a case like that, but it's not something that should be suggested to newbies. Now the discussion is sidetracked, but really nothing has improved since I tried to get a warning added to portmaster months ago. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-ports@freebsd.org Thu Dec 15 16:01:32 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFFEFC817C8 for ; Thu, 15 Dec 2016 16:01:32 +0000 (UTC) (envelope-from duchateau.olivier@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 633B41660 for ; Thu, 15 Dec 2016 16:01:32 +0000 (UTC) (envelope-from duchateau.olivier@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id g23so7382503wme.1 for ; Thu, 15 Dec 2016 08:01:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=rAfnUon5UhNlfI56JNJPrMm/Rk8gqELBaABf9jFqDQA=; b=OJP5zAyDu8KHAa5PHpNFU993SR64ja/gUV732zLgTHkn5F/BwGUNvK6ZRwt+PbOfbg i3bHLTTmWdrrATsC7r8GzHs0QKFPpNvb2C5k0s42pMy5DjNHR7OHM1UcJ4FM2UYtIjU9 fH4PNDIZtfh/6FaFLXKg+FfmxNWvFQIuD192PbmfcTi6ZpgXpOlyr8ZYxtAZcO8wqoxB QMWREVc/NQ246sCLQfJ7jkhfFfQjed0AHU7tUq0r17yGbSXKIspHL9q1MfzhdjwfUOEP M2/CWDeQoZP5Ctk8cw4eyLg+XfT77HMyqA7KZBopdEAsSTYE+asUWX75T0y6FoLFTgTn C5BA== 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:in-reply-to :references:mime-version:content-transfer-encoding; bh=rAfnUon5UhNlfI56JNJPrMm/Rk8gqELBaABf9jFqDQA=; b=phjnjni4Q/ll65J9eA2t+Zg2NN0pHuykMTGqg48EbGkANrMBECK1auIvK8silgWENO uEUX3JWKysudShdLzjTIGxIZ/DFw3PinYgSiJqwmlWn7FhqyXSKWluuGOegh/7koXrta jrwNK5gOMxExPbQ6gPrVH9nKhkrjop3+quaMwvRj+bLR803tjnSaiMq7p3UkOEBzPqIn QeDh/J4EYUOYH0Af0+OG32WaGfM9TwRQDCu0NZwhVtm2DTaijZwf6L81EHQao+E4rrzl mu138tld/dMqqV1DMC6dPfxEkXfvByJTjceCdOdRm7yxew+RHNR5jXKwK0OmTHqZRPai nU8w== X-Gm-Message-State: AIkVDXKnAVqzKbepkVWNSiDeoTK8slEDGKPUVfhDvhRPWUah0taN3jCfaZ03N3MGTEXEGA== X-Received: by 10.28.194.135 with SMTP id s129mr2231939wmf.55.1481817690821; Thu, 15 Dec 2016 08:01:30 -0800 (PST) Received: from localhost (AMarseille-655-1-785-203.w92-158.abo.wanadoo.fr. [92.158.146.203]) by smtp.gmail.com with ESMTPSA id pd2sm2621078wjb.31.2016.12.15.08.01.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Dec 2016 08:01:30 -0800 (PST) Date: Thu, 15 Dec 2016 17:01:54 +0100 From: Olivier Duchateau To: David Demelier Cc: "Vlad K." , Freebsd Ports Subject: Re: (In)Stability of the Quarterly Branch Message-Id: <20161215170154.0ca2017914c0bb032516b413@gmail.com> In-Reply-To: References: <3e7f94efc6428181a289742d7dd627df@acheronmedia.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2016 16:01:32 -0000 On Thu, 15 Dec 2016 14:16:18 +0100 David Demelier wrote: > 2016-11-16 13:17 GMT+01:00 Vlad K. : > > The quarterly branch (Q) is intended to provide a set of "stable" packages > > that in the lifetime of such a branch, receive only bug and security fixes. > > That is the theory and intent behind the branch. In practice, however: > > > > 1. The Q branch is cut off at predetermined dates (ie. not when it's stable > > and ready), and it is cut off from HEAD, thus including the state of ports > > at that moment. This breaks the promise of stability and guarantees that > > every 3 months there will be uncertainty as to whether the fresh new > > versions are working or not. There is no such thing as a "Pre-Quarterly > > repo" which would receive all updates for the NEXT Q branch-off, and which > > would freeze and stabilize for some time before branch-off. And even if it > > did, 3 months would be too short. > > > > It is effectively not much different from tracking HEAD and doing updates > > only every three months, with the added benefit that SOME security updates > > will come down sooner. But: > > > > 2. Unfortunately not all "security or bug-only fixes" are MFH'd, and as a > > bugzilla triager I've had the opportunity to observe this in practice. It > > can be as simple as accepting a minor upstream version bump, or as complex > > as requiring cherry-picking and backporting code if upstream mixes security, > > bug fixes with new features. It is none-the-less a manual work requiring > > ports-secteam to review and accept the patches. It is not clear who is > > supposed to do cherry-picked backporting if the patches to HEAD cannot be > > MFH'd as they are. It is also additional burden to the ports-secTEAM which > > at the moment is, effectively, one person. > > > > As it is obvious that the promise of a stable repo in its current form > > requires manpower and manual work which we do not have, my proposal is to > > abandon the promise of "security/bugfix" only changes and adopt the approach > > not unlike Gentoo's, in which a "STABLE" repository receives ALL the updates > > from HEAD, but only after certain criteria has been met, like minimal age of > > changes, no open issues, a certain battery of regression/integration/unit > > tests is performed, etc... > > > > The problem is that there are no tests in FreeBSD ports. All source > based systems I've tested: pkgsrc, FreeBSD ports, OpenBSD, Gentoo; > FreeBSD is the one that have the most instability. Not to mention > committers that commit without testing the port, just look at > www/redmine to get your point of view on that issue. Are your serious when you said, there're no tests on FreeBSD ports. I can tell you Xfce ports are tested with FreeBSD i386 9.3 and amd64 11.0 machines (on real hardware, no virtualization), and on poudriere with Gtk+ 3.20 (port version is not not in ports tree, it's defaut toolkits for the next stable release 4.14). For the LXQt desktop is the same thing (tested with official ports tree Qt5 and which one in plasma5 branch (on KDE repository). I'm also working on the Pantheon desktop (desktop environment of Elementary OS, I use Vala 0.30.2 and Vala 0.34.4, in order to test stability of applications. I use also OpenBSD macppc, it's piece of shit. WebKit browers are broken, Xfce components crash often, stable branch is outdated, fix are not propagated in stable branch. Personally I prefer the FreeBSD scheme, because I'm sure it's quite stable. > > On the other hand, your idea is indeed good and could be a good start. > Quaterly branches change too quickly. That's simple: each time I > install a new port, I'm behind 2 or 3 quarters the last one. So I > usually update all before installing the new one. > > What I want: a ports tree that matches the FreeBSD version like > OpenBSD. You have FreeBSD 11.0? You get a ports tree for that version > specifically. No major update, no breaking changes. Just bug fixes. > That will also simplify a lot FreeBSD ports by not having thousands of > conditional checking the FreeBSD version. > > Waiting for more stability, I really encourage people to use poudriere > to build packages to avoid breaking a system at each upgrade. > > Regards, > > -- > Demelier David > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" -- olivier From owner-freebsd-ports@freebsd.org Thu Dec 15 16:25:14 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54E12C81057 for ; Thu, 15 Dec 2016 16:25:14 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EC2C09A3 for ; Thu, 15 Dec 2016 16:25:13 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from host-4-75.office.adestra.com (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 3EED779D6 for ; Thu, 15 Dec 2016 16:25:09 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/3EED779D6; dkim=none; dkim-atps=neutral Subject: Re: (In)Stability of the Quarterly Branch To: freebsd-ports@freebsd.org References: <3e7f94efc6428181a289742d7dd627df@acheronmedia.com> <20161215170154.0ca2017914c0bb032516b413@gmail.com> From: Matthew Seaman Message-ID: Date: Thu, 15 Dec 2016 16:25:01 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161215170154.0ca2017914c0bb032516b413@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="tsE7TwppDsFN8JDVQsA84BdlnDwuG0ri2" X-Spam-Status: No, score=0.9 required=5.0 tests=BAYES_00,RCVD_IN_RP_RNBL, RDNS_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2016 16:25:14 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --tsE7TwppDsFN8JDVQsA84BdlnDwuG0ri2 Content-Type: multipart/mixed; boundary="a7XLXsctw67nvt4vibkcdqIl844nMd5RR"; protected-headers="v1" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: Subject: Re: (In)Stability of the Quarterly Branch References: <3e7f94efc6428181a289742d7dd627df@acheronmedia.com> <20161215170154.0ca2017914c0bb032516b413@gmail.com> In-Reply-To: <20161215170154.0ca2017914c0bb032516b413@gmail.com> --a7XLXsctw67nvt4vibkcdqIl844nMd5RR Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2016/12/15 16:01, Olivier Duchateau wrote: >> The problem is that there are no tests in FreeBSD ports. All source >> based systems I've tested: pkgsrc, FreeBSD ports, OpenBSD, Gentoo; >> FreeBSD is the one that have the most instability. Not to mention >> committers that commit without testing the port, just look at >> www/redmine to get your point of view on that issue. > Are your serious when you said, there're no tests on FreeBSD ports. I > can tell you Xfce ports are tested with FreeBSD i386 9.3 and amd64 > 11.0 machines (on real hardware, no virtualization), and on poudriere > with Gtk+ 3.20 (port version is not not in ports tree, it's defaut > toolkits for the next stable release 4.14). >=20 > For the LXQt desktop is the same thing (tested with official ports > tree Qt5 and which one in plasma5 branch (on KDE repository). >=20 > I'm also working on the Pantheon desktop (desktop environment of > Elementary OS, I use Vala 0.30.2 and Vala 0.34.4, in order to test > stability of applications. >=20 > I use also OpenBSD macppc, it's piece of shit. WebKit browers are > broken, Xfce components crash often, stable branch is outdated, fix > are not propagated in stable branch. Personally I prefer the FreeBSD > scheme, because I'm sure it's quite stable. Most port committers will run compile tests any time they update a port: the better ones will test compilation on all supported FreeBSD versions and all hardware architectures they have access to (ie. generally i386 and amd64). Additionally the package build cluster will rebuild any modified ports within a few days for all of the OS versions and architectures the project tries to provide ports for: that's yet another level of validating the coding of the port itself. However, I believe the OP's point is that *we do not routinely run the software's own built-in regression tests for the packages we succeed in building*. This is something that is slowly coming. For instance, you can run 'make test' for many python, ruby or perl packages and see those tests being run. TEST_DEPENDS is pretty much standardized as the way to install dependencies required for testing nowadays. Yet another layer of package validation would be very good to have, but it isn't routine yet. Cheers, Matthew --a7XLXsctw67nvt4vibkcdqIl844nMd5RR-- --tsE7TwppDsFN8JDVQsA84BdlnDwuG0ri2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJYUsPkXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnQx4QAIHcIZZxd/hQgMxKcgAwzgRn j2/UNYb1VU0eaEkLwFB+d5Qt354bLzydAjxJaUfLuqw4zvobNSj0GGjNStris5F1 ibqoNKHUpq0iFZdcs20niMNzENFE56T9TSMc4iOapLM67VXA48MhB5NUB9jp2sNE aPvirgXXrQ3I7Tfm6ZVrL+F8HtjeKjzomdjQbcvUVCf3gXxd47qa7+gW6Ug5pUWt /zzATHq+HosEblczj9dfdPpwaxjlAUhGy1VvAVfueCb6bxpx0tEN8li3i0kkbFYx aqB9Depk+Qr8Gm1pZvO2OYIRuoXIWDamD1a7XikYGXvIsEJru+zLzrxPe1D/0y+z 89verHRCtfp7F3a7DHuG4k5iav/lEtbQxa6BAJhBOonPdHfdM5LCdZue+j3hIZa5 9nhpsTCJGnnKDBiCFh1Gn68A01hHcmzy5/ze42NMonMwtgOhWg5C4Kfldghp6pay AHNWd2Wncga8E1mBARVui4tCbTzpUpeZsiPj4sZBBHBL9suWEed/8Q4HbMCOtDhs 4vPzipeEC8lcj7Wwa2lu5pKlwHfkZmodZ9vhG+o9KAIBytP9AasPpqOj9GuU5GT7 DOINThVOYAlN1x0PkPFr8POVBljNabPKqjxSipRE4hxbTZuQuZV5xBkRNIzjHWyP Fa5ivBo6CTi6KdmttmE7 =IXYu -----END PGP SIGNATURE----- --tsE7TwppDsFN8JDVQsA84BdlnDwuG0ri2-- From owner-freebsd-ports@freebsd.org Thu Dec 15 16:29:29 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9BDDC811B8 for ; Thu, 15 Dec 2016 16:29:29 +0000 (UTC) (envelope-from wblock@wonkity.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 9390CD03 for ; Thu, 15 Dec 2016 16:29:29 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: by mailman.ysv.freebsd.org (Postfix) id 92E9CC811B7; Thu, 15 Dec 2016 16:29: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 92978C811B6 for ; Thu, 15 Dec 2016 16:29:29 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6587ED02 for ; Thu, 15 Dec 2016 16:29:28 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id uBFGTQHf098352 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 15 Dec 2016 09:29:26 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id uBFGTQrg098349; Thu, 15 Dec 2016 09:29:26 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Thu, 15 Dec 2016 09:29:26 -0700 (MST) From: Warren Block To: RW cc: ports@freebsd.org Subject: Re: The ports collection has some serious issues In-Reply-To: <20161215155139.4a3d6033@gumby.homeunix.com> Message-ID: References: <20161208085926.GC2691@gmail.com> <20161215155139.4a3d6033@gumby.homeunix.com> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.1 (wonkity.com [127.0.0.1]); Thu, 15 Dec 2016 09:29:27 -0700 (MST) 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, 15 Dec 2016 16:29:29 -0000 On Thu, 15 Dec 2016, RW via freebsd-ports wrote: > On Thu, 15 Dec 2016 07:40:46 -0700 (MST) > Warren Block wrote: > >> On Thu, 8 Dec 2016, Matt Smith wrote: >> >>> On Dec 08 05:16, Daniil Berendeev wrote: >>>> >>>> Although portmaster is not releated to the FreeBSD project and is >>>> an outside tool, there aren't any alternatives from the project >>>> itself. So use it or die. Not a nice situation. >>> >>> People have been trying to get portmaster deprecated and removed >>> from the handbook but have met with resistance. >> >> Well, yes. Because it works, has no dependencies, and there is no >> equivalent replacement. Except maybe portupgrade, which has legacy >> problems like poor default options. > > That's a very minor issue, and an absurd excuse to rule-out portupgrade. I didn't rule it out. Portupgrade gets some of the defaults wrong, like not running all the 'make config' steps first. That's a legacy issue because if the default changes, it could conceivably cause problems for existing users. Beyond that, other than a dependency on Ruby, portupgrade at least exists in the same space as portmaster. From owner-freebsd-ports@freebsd.org Thu Dec 15 16:32:01 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3E13C81367 for ; Thu, 15 Dec 2016 16:32:01 +0000 (UTC) (envelope-from tz@FreeBSD.org) Received: from toco-domains.de (mail.toco-domains.de [176.9.39.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5C132FF2; Thu, 15 Dec 2016 16:32:01 +0000 (UTC) (envelope-from tz@FreeBSD.org) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id 6C20C1AAF011; Thu, 15 Dec 2016 17:31:58 +0100 (CET) Subject: Re: The ports collection has some serious issues To: marino@freebsd.org, FreeBSD Mailing List , wblock@wonkity.com References: <3959e18e-5819-b2c5-69a9-c71ce1282383@marino.st> <3cf805df-eb25-187c-8bf9-b6c2be5e977d@marino.st> From: Torsten Zuehlsdorff Message-ID: Date: Thu, 15 Dec 2016 17:31:58 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <3cf805df-eb25-187c-8bf9-b6c2be5e977d@marino.st> Content-Type: text/plain; charset=windows-1252; 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, 15 Dec 2016 16:32:01 -0000 On 15.12.2016 17:00, John Marino wrote: > On 12/15/2016 09:49, Torsten Zuehlsdorff wrote: >> On 15.12.2016 16:29, John Marino wrote: >>>>>> Although portmaster is not releated to the FreeBSD project and is an >>>>>> outside tool, there aren't any alternatives from the project >>>>>> itself. So >>>>>> use it or die. Not a nice situation. >>>>> >>>>> People have been trying to get portmaster deprecated and removed from >>>>> the >>>>> handbook but have met with resistance. >>>> >>>> Well, yes. Because it works, has no dependencies, and there is no >>>> equivalent replacement. Except maybe portupgrade, which has legacy >>>> problems like poor default options. >>> >>> Every single week, somebody falsely accuses the ports tree of being >>> broken but the accuser is the only one with the problem. What do they >>> all have in common? They are portmaster users. I'll iterate, saying >>> "portmaster works" means applying a very generous definition of "works". >> >> Not really, no. Its not every week and often there is a misuse or >> miss-understanding of portmaster. > > It is every week. Consider the FreeBSD forums as well. No, it isn't. Lets check the history. This is just a general statement. portmaster was added 2006 and the portstree startet in 1994. Yes, there are emotions in discussions and they are really needed to drive things, but we need to ensure to drive in the right direction. > "misuse" and "misunderstanding" failures are attributed to the tool. > Let's stop making excuses for portmaster. It is what it is and we've > had years to evaluate it. I'm with you at this point. portmaster is incredible complex and hard to understand. Therefore it is easy to misue or to misunderstand. >> With an argument like this you can also state there is every week a >> falsely accuse, because of poudriere. This would also be true (and is). > > I couldn't state that accurately. I can't recall any misuse reports > (and I can't come up with a feasible case in my head right now) I could. My colleague did some of them. :D Even i generate some of them. >>>>> The recommended replacements are ports-mgmt/synth and >>>>> ports-mgmt/poudriere. >>>>> These build an entire package repository that the pkg tool can use >>>>> but they >>>>> do so in clean chrooted environments, and rebuild everything that's >>>>> required >>>>> to keep a consistent ABI. Synth is more designed for a single live >>>>> system >>>>> like a desktop or a single server, whereas poudriere is what the >>>>> freebsd >>>>> package build clusters use and is more designed for that type of >>>>> usage. Worth >>>>> taking a look. >>>> >>>> These are package builders. Technically preferable, given adequate >>>> disk >>>> space and memory, but not equivalent to portmaster. >>> >>> It's like saying git and svn are not equivalent to cvs. >> >> I have a hard time to see git in this line. Its the way you use it. Yes, >> of course all three are code repositories. But one of them is a >> distributed repository and the other two are not. The differences are >> huge. >> Of course it also depends on your usage. I personally (means "heavily >> subjective) find git more than annoying. It lacks very important >> features (user management), is hard to use in automatic environments and >> make easy things (rename/delete branches) very hard. Other people really >> like all of this. It depends. >> >> So maybe the accusers just use the wrong tool? > > The point is that you wouldn't start a new project with cvs. You may or > may not transfer an existing project from cvs, but you're letting cvs > die by attribution. > > The same should be for portmaster. Some users will never see the light. > Let them suffer by their own hand. But for Pete's sake, don't > recommend it to new users. That's not doing them any kind of service. I see recommendations for poudriere or synth, but not for portmaster. And i give them too. But both are tools which are not feasible for every situation. I often have a hard time to get them their space they need to make things better. So it would be a good idea under which circumstances portmaster is a good choice and whenever it is not. > Portmaster is not maintained. Since you put your name on it, you've > made not a single commit to the repository, much less a new release. Yet > there are PRs on it. No excuses here. You are right, but its another store. I approved a commit which than breaks portmaster even after very good testing. And that make me even more cautious. But also i'm not allowed to change the code or do changes by myself, so its no surprise its very hard and i considered to drop my maintainer line multiple times. Thats just beside that the code is not written in a way which supports testing. So there is a very big risk in every change. I started to rewrite it in an private repo, but since it works (i could close many PRs) it really is at the bottom of my list. > Please, can we somehow discourage new people from starting on it? > Anybody with a machine that doesn't have a resources to run poudriere or > synth should not be building packages on that machine. I provide a poudriere server for my customers. Its not to nice to use, but they can configure it like the need and without the pressure on their own server. Maybe we need something like this to make it easier to abandon portmaster. Greetings, Torsten From owner-freebsd-ports@freebsd.org Thu Dec 15 16:35:57 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E98DBC813F8 for ; Thu, 15 Dec 2016 16:35:57 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (mail.sorbs.net [67.231.146.200]) by mx1.freebsd.org (Postfix) with ESMTP id D70861158 for ; Thu, 15 Dec 2016 16:35:57 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from C02LJ0HMFFT4.corp.proofpoint.com (static-58-108-170-168.optusnet.com.au [58.108.170.168]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0OI800K44JT96M20@hades.sorbs.net> for freebsd-ports@freebsd.org; Thu, 15 Dec 2016 08:43:58 -0800 (PST) Subject: Re: (In)Stability of the Quarterly Branch To: "Vlad K." , Freebsd Ports References: <3e7f94efc6428181a289742d7dd627df@acheronmedia.com> From: Michelle Sullivan Message-id: <5852C669.4040409@sorbs.net> Date: Fri, 16 Dec 2016 02:35:53 +1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 In-reply-to: <3e7f94efc6428181a289742d7dd627df@acheronmedia.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: Thu, 15 Dec 2016 16:35:58 -0000 Vlad K. wrote: > The quarterly branch (Q) is intended to provide a set of "stable" > packages that in the lifetime of such a branch, receive only bug and > security fixes. That is the theory and intent behind the branch. In > practice, however: > > 1. The Q branch is cut off at predetermined dates (ie. not when it's > stable and ready), and it is cut off from HEAD, thus including the > state of ports at that moment. This breaks the promise of stability > and guarantees that every 3 months there will be uncertainty as to > whether the fresh new versions are working or not. There is no such > thing as a "Pre-Quarterly repo" which would receive all updates for > the NEXT Q branch-off, and which would freeze and stabilize for some > time before branch-off. And even if it did, 3 months would be too short. > > It is effectively not much different from tracking HEAD and doing > updates only every three months, with the added benefit that SOME > security updates will come down sooner. But: > > 2. Unfortunately not all "security or bug-only fixes" are MFH'd, and > as a bugzilla triager I've had the opportunity to observe this in > practice. It can be as simple as accepting a minor upstream version > bump, or as complex as requiring cherry-picking and backporting code > if upstream mixes security, bug fixes with new features. It is > none-the-less a manual work requiring ports-secteam to review and > accept the patches. It is not clear who is supposed to do > cherry-picked backporting if the patches to HEAD cannot be MFH'd as > they are. It is also additional burden to the ports-secTEAM which at > the moment is, effectively, one person. > > As it is obvious that the promise of a stable repo in its current form > requires manpower and manual work which we do not have, my proposal is > to abandon the promise of "security/bugfix" only changes and adopt the > approach not unlike Gentoo's, in which a "STABLE" repository receives > ALL the updates from HEAD, but only after certain criteria has been > met, like minimal age of changes, no open issues, a certain battery of > regression/integration/unit tests is performed, etc... > > The key, I believe, is in automation which we can achieve with this, > and with that offer at least SOME level of stability without broken > promises. The key to this automation is no manual review, which can > only be achieved if we accept ALL changes, but stabilized to certain > degree. > > The idea of a "stable" repository is a valiant one, we definitely need > it if we want to increase the usage of FreeBSD in production as more > than just a base OS that does routing and ZFS storage -- namely > production use of stable ports. And IMHO we only need to balance > between how stable we can provide/guarantee it and what resources and > manpower we have available to do so. > > > What are the community's thoughts on this? > > That's what it needed but people charging through new versions and linuxifying FreeBSD screwed the pooch... This conversation/thread should have happened 2 years back. Michelle From owner-freebsd-ports@freebsd.org Thu Dec 15 16:46:54 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93AEFC81801 for ; Thu, 15 Dec 2016 16:46:54 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (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 4F5A61875; Thu, 15 Dec 2016 16:46:53 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id 51E3D43BAC; Thu, 15 Dec 2016 10:45:43 -0600 (CST) Subject: Re: The ports collection has some serious issues To: Torsten Zuehlsdorff , FreeBSD Mailing List , wblock@wonkity.com References: <3959e18e-5819-b2c5-69a9-c71ce1282383@marino.st> <3cf805df-eb25-187c-8bf9-b6c2be5e977d@marino.st> From: John Marino Reply-To: marino@freebsd.org Message-ID: <3daf4aea-82ea-de8f-86d8-5c3b19a1f8a3@marino.st> Date: Thu, 15 Dec 2016 10:46:51 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161215-0, 12/15/2016), Outbound message X-Antivirus-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: Thu, 15 Dec 2016 16:46:54 -0000 On 12/15/2016 10:31, Torsten Zuehlsdorff wrote: > On 15.12.2016 17:00, John Marino wrote: >> It is every week. Consider the FreeBSD forums as well. > > No, it isn't. Lets check the history. This is just a general statement. > portmaster was added 2006 and the portstree startet in 1994. Can you agree that if you combine both this list and issues that arise on the FreeBSD forums that portmaster users talk about problems frequently? Does it matter if it's weekly or biweekly? It seems to happen all the time on the forums, but I'm not going scan them to prove an exact frequency. > > I could. My colleague did some of them. :D Even i generate some of them. > As a side discussion I would like to know what they are and if they are valid for Synth as well. > I see recommendations for poudriere or synth, but not for portmaster. > And i give them too. Unfortunately portmaster get a lot of positive press on the forums. > >> Portmaster is not maintained. Since you put your name on it, you've >> made not a single commit to the repository, much less a new release. Yet >> there are PRs on it. > > No excuses here. You are right, but its another store. I approved a > commit which than breaks portmaster even after very good testing. And > that make me even more cautious. But also i'm not allowed to change the > code or do changes by myself, so its no surprise its very hard and i > considered to drop my maintainer line multiple times. Thats just beside > that the code is not written in a way which supports testing. So there > is a very big risk in every change. I started to rewrite it in an > private repo, but since it works (i could close many PRs) it really is > at the bottom of my list. Interesting, but not surprising. I know it was claimed to negate my good point that such a piece of software needs a maintainer, but it had to be somebody with deep level knowledge with both the capability and *authority* to make the changes. So now users think it's maintained and have a false confidence in it. But with your name on it, I can't push for it to be marked "deprecated" (with no expiration, that's important) anymore. It's a loophole. >> Please, can we somehow discourage new people from starting on it? >> Anybody with a machine that doesn't have a resources to run poudriere or >> synth should not be building packages on that machine. > > I provide a poudriere server for my customers. Its not to nice to use, > but they can configure it like the need and without the pressure on > their own server. Maybe we need something like this to make it easier to > abandon portmaster. For i386 and amd64 users, synth does not require more resources than portmaster. People on those platforms can't use "resources" as a reason not to use Synth. From what I can tell, portmaster people hate what they consider unnecessary rebuilds which both poudriere and synth (currently [1]) do, but it's this avoidance of rebuilds that cause all their problems. So providing them a poudriere service wouldn't solve that "problem" for them. John [1] I've got it on my todo list to provide a new method that would eliminate the "my builder just rebuilt 150 packages, but pkg(8) only upgraded 2 packages" issue that some users don't want to see. It's a lot more complicated than the conservative yet bulletproof approach currently used by poudriere and synth. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-ports@freebsd.org Thu Dec 15 17:01:09 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2B6E5C81EA9 for ; Thu, 15 Dec 2016 17:01:09 +0000 (UTC) (envelope-from tz@FreeBSD.org) Received: from toco-domains.de (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B81D669C; Thu, 15 Dec 2016 17:01:08 +0000 (UTC) (envelope-from tz@FreeBSD.org) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id 503841AAF011; Thu, 15 Dec 2016 18:01:07 +0100 (CET) Subject: Re: The ports collection has some serious issues To: marino@freebsd.org, FreeBSD Mailing List , wblock@wonkity.com References: <3959e18e-5819-b2c5-69a9-c71ce1282383@marino.st> <3cf805df-eb25-187c-8bf9-b6c2be5e977d@marino.st> <3daf4aea-82ea-de8f-86d8-5c3b19a1f8a3@marino.st> From: Torsten Zuehlsdorff Message-ID: Date: Thu, 15 Dec 2016 18:01:07 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <3daf4aea-82ea-de8f-86d8-5c3b19a1f8a3@marino.st> Content-Type: text/plain; charset=windows-1252; 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, 15 Dec 2016 17:01:09 -0000 On 15.12.2016 17:46, John Marino wrote: > On 12/15/2016 10:31, Torsten Zuehlsdorff wrote: >> On 15.12.2016 17:00, John Marino wrote: >>> It is every week. Consider the FreeBSD forums as well. >> >> No, it isn't. Lets check the history. This is just a general statement. >> portmaster was added 2006 and the portstree startet in 1994. > > Can you agree that if you combine both this list and issues that arise > on the FreeBSD forums that portmaster users talk about problems > frequently? Yes, of course. I wasn't serious with this point and just want to degrade a little of the emotion to get back to a more technical and solvable level. >> I could. My colleague did some of them. :D Even i generate some of them. > > As a side discussion I would like to know what they are and if they are > valid for Synth as well. Good question. I will ask my colleague to check; hopefully he does it also. >> I see recommendations for poudriere or synth, but not for portmaster. >> And i give them too. > > Unfortunately portmaster get a lot of positive press on the forums. Okay, that is just the opposite of the mailinglist. For bugzilla we have the helpful team around koops, which adjust the PRs. Maybe we should install something like that for the forum? Or just print a warning whenever portmaster is used (which would be much easier). We even can automatically link the word portmaster to an website, which gives more information and some warning. >>> Portmaster is not maintained. Since you put your name on it, you've >>> made not a single commit to the repository, much less a new release. Yet >>> there are PRs on it. >> >> No excuses here. You are right, but its another store. I approved a >> commit which than breaks portmaster even after very good testing. And >> that make me even more cautious. But also i'm not allowed to change the >> code or do changes by myself, so its no surprise its very hard and i >> considered to drop my maintainer line multiple times. Thats just beside >> that the code is not written in a way which supports testing. So there >> is a very big risk in every change. I started to rewrite it in an >> private repo, but since it works (i could close many PRs) it really is >> at the bottom of my list. > > Interesting, but not surprising. I know it was claimed to negate my > good point that such a piece of software needs a maintainer, but it had > to be somebody with deep level knowledge with both the capability and > *authority* to make the changes. > > So now users think it's maintained and have a false confidence in it. > But with your name on it, I can't push for it to be marked "deprecated" > (with no expiration, that's important) anymore. It's a loophole. A breakable loophole. Since i figured out, that a complete rewrite would be a better solution, than the permanent danger of an very hard to test software, we can drop my name from it. >>> Please, can we somehow discourage new people from starting on it? >>> Anybody with a machine that doesn't have a resources to run poudriere or >>> synth should not be building packages on that machine. >> >> I provide a poudriere server for my customers. Its not to nice to use, >> but they can configure it like the need and without the pressure on >> their own server. Maybe we need something like this to make it easier to >> abandon portmaster. > > For i386 and amd64 users, synth does not require more resources than > portmaster. People on those platforms can't use "resources" as a reason > not to use Synth. From what I can tell, portmaster people hate what > they consider unnecessary rebuilds which both poudriere and synth > (currently [1]) do, but it's this avoidance of rebuilds that cause all > their problems. > > So providing them a poudriere service wouldn't solve that "problem" for > them. It does. Since they are not aware of the "unnecessary" rebuilds, its no "problem" anymore. If you have to watch rebuilding 150 ports just for an update of 2 ports, its a complete different story. If pkg only update 2 ports and you can't see the work behind them, everything is fine. Its a little bit psychological. Greetings, Torsten From owner-freebsd-ports@freebsd.org Thu Dec 15 17:17:55 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 890B2C8162F; Thu, 15 Dec 2016 17:17:55 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: from mail.hs.ntnu.edu.tw (mail.hs.ntnu.edu.tw [140.131.149.3]) (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 59B4D1295; Thu, 15 Dec 2016 17:17:54 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: by mail.hs.ntnu.edu.tw (Postfix, from userid 800) id 78DB01C6457; Fri, 16 Dec 2016 01:17:45 +0800 (CST) Received: from abeing (IP-215-9.cs.nctu.edu.tw [140.113.215.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: iblis@hs.ntnu.edu.tw) by mail.hs.ntnu.edu.tw (Postfix) with ESMTPSA id 3BE6D1C644A; Fri, 16 Dec 2016 01:17:45 +0800 (CST) Date: Fri, 16 Dec 2016 01:17:44 +0800 From: Iblis Lin To: ports@FreeBSD.org Cc: freebsd-ports@FreeBSD.org Subject: Re: The ports collection has some serious issues Message-ID: <20161215171743.GA20206@abeing> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) X-Bogosity: Ham, tests=bogofilter, spamicity=0.506773, version=1.2.4 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, 15 Dec 2016 17:17:55 -0000 I want to talk about another issue: the testing of ports framework We usually test our ports via poudriere or synth. We have a greate ports framework to help us build software, and we only need to write a few lines of code to leveage it. But ... where is the testing of the framework ? Those code under Mk/* is quite complex nowaday, and the requirement is keeping changing (for example, more and more new languages appear, helpers need to be added into ports framework). This will be a big barrier for maintenance. Is time to build a next generation framework? I think about this issue for a few weeks already, but still not get a good answer. I only sorted out some principles and want to hear more feedback: 1) Select a modern scripting language Lots of testing methodology implemented in those languages. Most of them are high-level. The cost of maintenance (hopefully) reduce. So, I think this is a good starting point. 2) Not to abandon tons of Makfile 3) Not to introduce any new dependency for a end user Just my imagination: In order to keep (2) and (3), I will use Python to build a system doing Makfile code generation. The ports framework managers and porters just write some Python function and testing code, then generate a proper tested and stable Makefiles for users. -- Iblis Lin 林峻頤 From owner-freebsd-ports@freebsd.org Thu Dec 15 17:43:19 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0C1BEC813F1 for ; Thu, 15 Dec 2016 17:43:19 +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 C3862D84; Thu, 15 Dec 2016 17:43:18 +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 7BE8928429; Thu, 15 Dec 2016 18:43:14 +0100 (CET) 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 BBC9D28417; Thu, 15 Dec 2016 18:43:13 +0100 (CET) Subject: Re: The ports collection has some serious issues To: marino@freebsd.org, Torsten Zuehlsdorff , FreeBSD Mailing List , wblock@wonkity.com References: <3959e18e-5819-b2c5-69a9-c71ce1282383@marino.st> <3cf805df-eb25-187c-8bf9-b6c2be5e977d@marino.st> <3daf4aea-82ea-de8f-86d8-5c3b19a1f8a3@marino.st> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <5852D631.4090208@quip.cz> Date: Thu, 15 Dec 2016 18:43:13 +0100 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: <3daf4aea-82ea-de8f-86d8-5c3b19a1f8a3@marino.st> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2016 17:43:19 -0000 John Marino wrote on 2016/12/15 17:46: > [1] I've got it on my todo list to provide a new method that would > eliminate the "my builder just rebuilt 150 packages, but pkg(8) only > upgraded 2 packages" issue that some users don't want to see. It's a > lot more complicated than the conservative yet bulletproof approach > currently used by poudriere and synth. This is interesting case - we are running own Poudriere repo and I am fine with it. But I am a bit nervous when I know 150 packages was rebuilt and just 2 upgraded by pkg. In this case I want pkg to update (reinstall) all of them. If something changed so that 150 packages must be rebuilt why pkg doesn't reinstall them? Isn't it the possible place for problems after upgrade? Mirek From owner-freebsd-ports@freebsd.org Thu Dec 15 17:59:39 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD045C81BFA for ; Thu, 15 Dec 2016 17:59:39 +0000 (UTC) (envelope-from buzon15@tuempresaactualizada.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id ABDB4188F for ; Thu, 15 Dec 2016 17:59:39 +0000 (UTC) (envelope-from buzon15@tuempresaactualizada.com) Received: by mailman.ysv.freebsd.org (Postfix) id A84AFC81BF9; Thu, 15 Dec 2016 17:59:39 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7EF6C81BF8 for ; Thu, 15 Dec 2016 17:59:39 +0000 (UTC) (envelope-from buzon15@tuempresaactualizada.com) Received: from mail2.tuempresaactualizada.com (mail2.tuempresaactualizada.com [107.150.32.196]) by mx1.freebsd.org (Postfix) with ESMTP id 8889C188E for ; Thu, 15 Dec 2016 17:59:39 +0000 (UTC) (envelope-from buzon15@tuempresaactualizada.com) Received: from WIN-JL967LLBK95 (107.150.32.196) by mail2.tuempresaactualizada.com id habcvs0our02 for ; Thu, 15 Dec 2016 11:59:18 -0600 (envelope-from ) X-client: DFINE08132 Message-ID: From: "=?utf-8?Q?cu=C3=A1ndo_es_obligatoria_la_contabilidad_electr=C3=B3nica?=" To: Subject: =?utf-8?Q?Auditor=C3=ADas_a_trav=C3=A9s_del_Buz=C3=B3n_Tributario?= Date: Thu, 15 Dec 2016 11:59:18 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 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, 15 Dec 2016 17:59:39 -0000 IA0KDQpFbiBsw61uZWEgeSBlbiBWaXZvIC8gUGFyYSB0b2RvIHN1IEVxdWlwbyBjb24gdW5hIHNv bGEgQ29uZXhpw7NuIA0KDQpBdWRpdG9yw61hcyBhIHRyYXbDqXMgZGVsIEJ1esOzbiBUcmlidXRh cmlvDQoyOSBkZSBkaWNpZW1icmUgLSBPbmxpbmUgZW4gVml2byAtIDEwOjAwIGEgMTM6MDAgSHJz ICAgICAgIA0KIA0KQSB0cmF2w6lzIGRlIGVzdGEgQ2FwYWNpdGFjacOzbiBPbmxpbmUgZW4gVml2 byBlbnTDqXJlc2UgY3XDoWxlcyBzb24gbG9zIHNlY3RvcmVzIGludm9sdWNyYWRvcywgZW4gcXXD qSBjb25zaXN0ZW4gZGljaGFzIGF1ZGl0b3LDrWFzLCBhIHF1w6kgc2VnbWVudG9zIHZhbiBkaXJp Z2lkYXMgeSBjw7NtbyBzZSB0ZW5kcsOhbiBxdWUgcmVzb2x2ZXIgbGFzIGluY29uZm9ybWlkYWRl cyBlbiB0w6lybWlub3MgZGVsIEJ1esOzbiBUcmlidXRhcmlvLiBEZXNjdWJyYSBjw7NtbyBsYXMg cGVyc29uYXMgZsOtc2ljYXMgeSBsb3MgcGVxdWXDsW9zIG5lZ29jaW9zIGluc2NyaXRvcyBlbiBl bCBSw6lnaW1lbiBkZSBJbmNvcnBvcmFjacOzbiBGaXNjYWwgKFJJRikgc29uIGxvcyBzZWN0b3Jl cyBxdWUgbcOhcyBoYW4gcmVzZW50aWRvIGxvcyBjYW1iaW9zIGVudHJhZG9zIGVuIHZpZ29yIGVu IDIwMTQsIHlhIHF1ZSB0b2RhdsOtYSBoYXkgY2FyZW5jaWFzIHTDqWNuaWNhcyB5IHRlY25vbMOz Z2ljYXMuIA0KIlByZWd1bnRlIHBvciBudWVzdHJhIFByb21vY2nDs24gTmF2aWRlw7FhIiANCg0K DQpURU1BUklPOiANCg0KMS4gUXXDqSBzb24gbG9zIHRyw6FtaXRlcyBwb3IgQnV6w7NuIFRyaWJ1 dGFyaW8geSBBdWRpdG9yw61hcyBFbGVjdHLDs25pY2FzIGRlbCBTQVQuDQoNCjIuIE1hcmNvIGxl Z2FsIGRlbCBCdXrDs24gVHJpYnV0YXJpbyB5IGxhcyBBdWRpdG9yw61hcy4NCg0KMy4gQSBwYXJ0 aXIgZGUgY3XDoW5kbyBlcyBvYmxpZ2F0b3JpYSBsYSBjb250YWJpbGlkYWQgZWxlY3Ryw7NuaWNh Lg0KDQo0LiBWaWdlbmNpYSBkZSBsYSBub3RpZmljYWNpw7NuIHbDrWEgZS1tYWlsOiBTZSBpbmN1 bXBsZSBjb24gZWwgcGFnbyBkZSBpbXB1ZXN0b3MgcG9yIG5vIHRlbmVyIGFjY2VzbyBhIGludGVy bmV0Lg0KDQoNCg0KDQouLi7CoVkgbXVjaG8gbcOhcyENCg0KDQogDQrCv1JlcXVpZXJlIGxhIGlu Zm9ybWFjacOzbiBhIGxhIEJyZXZlZGFkPw0KcmVzcG9uZGEgZXN0ZSBlbWFpbCBjb24gbGEgcGFs YWJyYTogDQpJbmZvIC0gQnV6w7NuLg0KY2VudHJvIHRlbGVmw7NuaWNvOiAwMTgwMDIxMjkzOTMN CiANCg0KTGljLiBBcnR1cm8gTMOzcGV6DQpDb29yZGluYWRvciBkZSBFdmVudG8NCg0KDQogDQrC v0RlbWFzaWFkb3MgbWVuc2FqZXMgZW4gc3UgY3VlbnRhPyBSZXNwb25kYSBlc3RlIG1lbnNhamUg aW5kaWNhbmRvIHF1ZSBzb2xvIGRlc2VhIHJlY2liaXIgQ0FMRU5EQVJJTyB5IHPDs2xvIHJlY2li aXLDoSB1biBjb3JyZW8gYWwgbWVzLiBTaSBkZXNlYSBjYW5jZWxhciBsYSBzdXNjcmlwY2nDs24s IHNvbGljaXRlIHN1IEJBSkEuIA0KIA0KDQogDQoNCiANCg0K From owner-freebsd-ports@freebsd.org Thu Dec 15 18:18:14 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1442EC812C3 for ; Thu, 15 Dec 2016 18:18:14 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [IPv6:2001:418:3fd::f7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BAE731F2 for ; Thu, 15 Dec 2016 18:18:13 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:418:3fd::1f] (haymarket.m5p.com [IPv6:2001:418:3fd::1f]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTP id uBFII5QA033804; Thu, 15 Dec 2016 13:18:10 -0500 (EST) (envelope-from george+freebsd@m5p.com) Subject: Re: The ports collection has some serious issues To: Warren Block , Matt Smith References: <20161208085926.GC2691@gmail.com> Cc: freebsd-ports@FreeBSD.org, Daniil Berendeev From: George Mitchell Message-ID: <3b00e76a-7a97-aa1b-72e9-236161044c3b@m5p.com> Date: Thu, 15 Dec 2016 13:18:05 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.8 required=10.0 tests=ALL_TRUSTED, RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mattapan.m5p.com X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.1 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Thu, 15 Dec 2016 13:18:11 -0500 (EST) 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, 15 Dec 2016 18:18:14 -0000 On 12/15/16 09:40, Warren Block wrote: > On Thu, 8 Dec 2016, Matt Smith wrote: > >> On Dec 08 05:16, Daniil Berendeev wrote: >>> >>> Although portmaster is not releated to the FreeBSD project and is an >>> outside tool, there aren't any alternatives from the project itself. So >>> use it or die. Not a nice situation. >> >> People have been trying to get portmaster deprecated and removed from >> the handbook but have met with resistance. > > Well, yes. Because it works, has no dependencies, and there is no > equivalent replacement. [...] Warren, you have hit the nail on the head. -- George From owner-freebsd-ports@freebsd.org Thu Dec 15 18:41:13 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EB04C81BF9 for ; Thu, 15 Dec 2016 18:41:13 +0000 (UTC) (envelope-from list-freebsd-ports@jyborn.se) Received: from mailgate.leissner.se (mailgate.leissner.se [212.3.1.210]) by mx1.freebsd.org (Postfix) with ESMTP id 056E21149 for ; Thu, 15 Dec 2016 18:41:12 +0000 (UTC) (envelope-from list-freebsd-ports@jyborn.se) Received: from mailgate.leissner.se (localhost [127.0.0.1]) by mailgate.leissner.se (8.15.2/8.15.2) with ESMTP id uBFIVhO9056721 for ; Thu, 15 Dec 2016 19:31:43 +0100 (CET) (envelope-from list-freebsd-ports@jyborn.se) Received: (from uucp@localhost) by mailgate.leissner.se (8.15.2/8.15.2/Submit) id uBFIVhDP056717 for ; Thu, 15 Dec 2016 19:31:43 +0100 (CET) (envelope-from list-freebsd-ports@jyborn.se) Received: from pol.leissner.se(192.71.29.17), claiming to be "pol-server.leissner.se" via SMTP by mailgate.leissner.se, id smtpdc8Zzsj; Thu Dec 15 19:31:37 2016 Received: from localhost (pol-server.leissner.se [local]); by pol-server.leissner.se (OpenSMTPD) with ESMTPA id 60361e49; Thu, 15 Dec 2016 19:31:22 +0100 (CET) Date: Thu, 15 Dec 2016 19:31:22 +0100 From: list-freebsd-ports@jyborn.se To: George Mitchell , Warren Block Cc: Matt Smith , freebsd-ports@FreeBSD.org, Daniil Berendeev Subject: Re: The ports collection has some serious issues Message-ID: <20161215183122.GG5268@pol-server.leissner.se> References: <20161208085926.GC2691@gmail.com> <3b00e76a-7a97-aa1b-72e9-236161044c3b@m5p.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3b00e76a-7a97-aa1b-72e9-236161044c3b@m5p.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2016 18:41:13 -0000 On Thu, Dec 15, 2016 at 01:18:05PM -0500, George Mitchell wrote: > On 12/15/16 09:40, Warren Block wrote: > > On Thu, 8 Dec 2016, Matt Smith wrote: > > > >> On Dec 08 05:16, Daniil Berendeev wrote: > >>> > >>> Although portmaster is not releated to the FreeBSD project and is an > >>> outside tool, there aren't any alternatives from the project itself. So > >>> use it or die. Not a nice situation. > >> > >> People have been trying to get portmaster deprecated and removed from > >> the handbook but have met with resistance. > > > > Well, yes. Because it works, has no dependencies, and there is no > > equivalent replacement. [...] > > Warren, you have hit the nail on the head. -- George +1 I never have problems with portmaster. (But portupgrade could at times be an utter mess, I never looked back after switching to portmaster many years ago.) And I'm not at all interested in running poudriere or synth, thank you. Peter From owner-freebsd-ports@freebsd.org Thu Dec 15 19:15:29 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5B8CC82701 for ; Thu, 15 Dec 2016 19:15:29 +0000 (UTC) (envelope-from mazhe@alkumuna.eu) Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [212.27.42.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 7F111991 for ; Thu, 15 Dec 2016 19:15:28 +0000 (UTC) (envelope-from mazhe@alkumuna.eu) Received: from yggdrasil.alkumuna.eu (unknown [IPv6:2a01:e35:8a74:6e70:232:36ff:fe5c:3a87]) by smtp1-g21.free.fr (Postfix) with ESMTPS id 82B8AB0054E; Thu, 15 Dec 2016 20:15:22 +0100 (CET) Received: from freedom.alkumuna.eu ([IPv6:2a01:e35:8a74:6e70:62a4:4cff:fe54:b212]) (authenticated bits=0) by yggdrasil.alkumuna.eu (8.15.2/8.15.2) with ESMTPSA id uBFJFIjK021082 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 15 Dec 2016 20:15:21 +0100 (CET) (envelope-from mazhe@alkumuna.eu) Date: Thu, 15 Dec 2016 20:15:17 +0100 From: Matthieu Volat To: list-freebsd-ports@jyborn.se Cc: freebsd-ports@FreeBSD.org Subject: Re: The ports collection has some serious issues Message-ID: <20161215201517.2e6bcd39@freedom.alkumuna.eu> In-Reply-To: <20161215183122.GG5268@pol-server.leissner.se> References: <20161208085926.GC2691@gmail.com> <3b00e76a-7a97-aa1b-72e9-236161044c3b@m5p.com> <20161215183122.GG5268@pol-server.leissner.se> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/jU6g+MDKYSul.WTvqM+pBEO"; protocol="application/pgp-signature" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alkumuna.eu; s=default; t=1481829321; bh=2RPSxEx/73Yxh3uT7/uHFnOkd6uZL1uNgrE7K93uC3I=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References:MIME-Version:Content-Type; b=qrxez07BYDDuAb9YzcYwLoK60ONT6kfMnc7p2lMab5c881Hwh8tgmWKKPNh40U2QU2Q/w4tMKjQAfIS5rMhHkV+00ggHpvqpt9T0JxIJjdPp50MulLe8I/ZQmO2rE0SJBuTpSC24XxtfbGb7Wl3EenAN/tCT/OS1paG5xzq3iiQ= 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, 15 Dec 2016 19:15:29 -0000 --Sig_/jU6g+MDKYSul.WTvqM+pBEO Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Thu, 15 Dec 2016 19:31:22 +0100 list-freebsd-ports@jyborn.se wrote: > On Thu, Dec 15, 2016 at 01:18:05PM -0500, George Mitchell wrote: > > On 12/15/16 09:40, Warren Block wrote: > > > On Thu, 8 Dec 2016, Matt Smith wrote: > > >=20 > > >> On Dec 08 05:16, Daniil Berendeev wrote: > > >>> > > >>> Although portmaster is not releated to the FreeBSD project and is an > > >>> outside tool, there aren't any alternatives from the project itself= . So > > >>> use it or die. Not a nice situation. > > >> > > >> People have been trying to get portmaster deprecated and removed from > > >> the handbook but have met with resistance. > > >=20 > > > Well, yes. Because it works, has no dependencies, and there is no > > > equivalent replacement. [...] > >=20 > > Warren, you have hit the nail on the head. -- George >=20 > +1 >=20 > I never have problems with portmaster. > (But portupgrade could at times be an utter mess, > I never looked back after switching to portmaster > many years ago.) >=20 > And I'm not at all interested in running poudriere > or synth, thank you. >=20 It seems that if people happy with portmaster keep silent, others will assu= me it's okay to try to dismiss it; so here am I, happy with portmaster. I could switch to something else that is feature wise similar; but if it wo= uld not written in some quasi-obselete/niche/hipster programing language or= involve admin/config tasks like creating repos. Until a challenger appears, I'm just going to use and recommend portmaster. Happy bsding everybody -- Matthieu --Sig_/jU6g+MDKYSul.WTvqM+pBEO Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTxuiqPSkQnzRDOjsP4Q0N5gpmLfgUCWFLrxQAKCRD4Q0N5gpmL fgl4AJ0f07zAhazYqmjezPxgBGPXMSA+kQCfXCRElGCekkJDNDx3aTgGCtTPtrU= =Nxn7 -----END PGP SIGNATURE----- --Sig_/jU6g+MDKYSul.WTvqM+pBEO-- From owner-freebsd-ports@freebsd.org Thu Dec 15 19:44:37 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C3A4C82DC7 for ; Thu, 15 Dec 2016 19:44:37 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 817C41721 for ; Thu, 15 Dec 2016 19:44:37 +0000 (UTC) (envelope-from peter@rulingia.com) Received: by mailman.ysv.freebsd.org (Postfix) id 80D79C82DC6; Thu, 15 Dec 2016 19:44:37 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80789C82DC5 for ; Thu, 15 Dec 2016 19:44:37 +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 14FC41720; Thu, 15 Dec 2016 19:44:36 +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 uBFJi7bc097713 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 16 Dec 2016 06:44:13 +1100 (AEDT) (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 uBFJi0en076099 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 16 Dec 2016 06:44:01 +1100 (AEDT) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id uBFJhxEe076086; Fri, 16 Dec 2016 06:43:59 +1100 (AEDT) (envelope-from peter) Date: Fri, 16 Dec 2016 06:43:59 +1100 From: Peter Jeremy To: Mathieu Arnold Cc: "Julian H. Stacey" , ports@FreeBSD.org Subject: Re: No port should need root for make fetch Message-ID: <20161215194358.GA75755@server.rulingia.com> References: <201612132032.uBDKWaVK017178@fire.js.berklix.net> <20161214051706.GS61036@server.rulingia.com> <05247bf0-d31e-6a88-57ab-69687f5f1af1@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="tKW2IUtsqtDRztdT" Content-Disposition: inline In-Reply-To: <05247bf0-d31e-6a88-57ab-69687f5f1af1@FreeBSD.org> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.7.1 (2016-10-04) 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, 15 Dec 2016 19:44:37 -0000 --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2016-Dec-15 09:43:51 +0100, Mathieu Arnold wrote: >Le 14/12/2016 =E0 06:17, Peter Jeremy a =E9crit : >> On 2016-Dec-13 21:32:36 +0100, "Julian H. Stacey" wrot= e: >>> IMO No port should need root for=20 >>> cd /usr/ports; make -i fetch >> In a stock FreeBSD install, all ports require root to both fetch and bui= ld. >> You have customised your system in a non-standard way so you are getting >> non-standard behaviour which doesn't match you expectations. > >That is plain not true. By default, /usr/ports/distfiles is mode 0775 root:wheel and the only member of wheel is root. Fetching a port requires writing to /usr/ports/distfiles, hence root is the only user that can fetch distfiles. Likewise, by default, ports are built it /usr/ports/CATEGORY/NAME/work. /usr/ports/CATEGORY/NAME is only writable by root so only root can create the work directory in which to build ports. If you change the above defaults (which I suspect most people do) then you are correct that only a handful of ports need root to fetch or build (and I think that is still too many) - but I explicitly specified "stock install= ". --=20 Peter Jeremy --tKW2IUtsqtDRztdT Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJYUvJ+XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs0KX0P/2ui0WAvri6x3aQ1ZORIj2OX uWieuUCstmTWKOy7N2gAGlRiTQkazdd9eOcWhFxG+P+dmstUa+vqOPucbIxUnFZf 3Aw6ee91yWCHSJjMss/dTlB5tcbedPnNbROxBKreKxgu5Kb8gggllyRiDX0g4/i8 +vVfzTFO4P/Iu6CQ5DySvc/KZul67Cy+xuiVtCfsplMRWjCaClNY0NjNNhqKodm3 qlHNSljMowXqxhRzJ2KmobStFFh/kA65FZAkJWw8UKZDHLy1dZVk+AbMtu8B2COU UcvyyJbZrO5UvSrb+fQCXljvD9z9SPFpviU9HrzB6vvQtlyQFVxJJF1dlrt895LV FGDtS1Khb5FFVDX3NsGOTIhA6IwO0SAjJQVPHzeJIcidXb4gux/a7DC686KuU0ck NL54BG18FfvSQUxlnfBvUCiveM7M2DHVfUIFT+s67YPQoG+uxgC1GFGO81NuQvuH xqiFgXMjrWOvTSS8oHMKJ4Elj5J8Jvebxp8+0E6rof3k/PRXppqvwJ+t3KQpGBEx dl9L9v/oQW9oYxs20uXvLPpmwpyN73UWLPloSjr7VFm+sFA5Dud0+PfPD8aw8Siy VSephVIKJQuhzJWtNgdjvk1jN0tY2v2cgy/IV8M6wG+EH3eQPXYXd0hNMknOgLL6 mLdplygAjGdd5qD4t6Ga =WtNp -----END PGP SIGNATURE----- --tKW2IUtsqtDRztdT-- From owner-freebsd-ports@freebsd.org Thu Dec 15 23:23:07 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1C5EC82891 for ; Thu, 15 Dec 2016 23:23:07 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1EF311232 for ; Thu, 15 Dec 2016 23:23:06 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([77.181.91.205]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LdYSM-1czDan2v3K-00ik98 for ; Fri, 16 Dec 2016 00:23:04 +0100 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id A86B423CF5A for ; Fri, 16 Dec 2016 00:23:02 +0100 (CET) From: Matthias Andree Subject: CFT: OpenVPN 2.4 port update for FreeBSD To: freebsd-ports Message-ID: Date: Fri, 16 Dec 2016 00:23:02 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="c77oI4uD9m9FVcktvuBBkkD2SK1lkFbFj" X-Provags-ID: V03:K0:kGifLXuik2JG2VrFy/WDPmIQYooQLJ7n03IUHVY4vVKGVwc36+e 4E1K7j7yuPDAQllbP3vWLbs3cg/e9guw2cKBihcfet2t/QN4Qpr/3sirQPtl7aOE3+0QifY LkkBPJ637vER0SFjzfdBmlp5kg62w6zah+R4yAIpzS4/0k4KJE93CUhjgjMCeCHoOTBqLNV ERJrbtbBrJjs1k98KyZQQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:0lLKPEF1+LQ=:HoFce4lxjL13DInDhYSkqR Ye64dZIf9bQ+taIT/0HET6mKVnuof69wK54rIAD8WIXB2wZMR9HEOS45J2+JKVUfjBSiOfbm9 hrTOrjarx4jgmqY+AkrgwSmnlKkXDUEDucFhpbdDzRDegD/q7jpogAGj2v/ozp4cj/O/U/BIK HEKHJnc9gdcRnGwuOCBiikl1UZ7VxAe3rgIeQ6nICeEx16u0C/2W+YveSbml6ktuXCzEDEvsY HE4NJ1wi7IAHrrxfPsHFJrc361NZGu9bep64KziHr5tPGtIxB1wChKL6DJkxmhHr/SXxHlKuy nHkp792flfEP6DYeEH/gdv1GwLYSpP1CBICPauqodYeeSXbJCKDK6TYKz6VMewRRF/nIBsNAl Kq0Kai8Ev4RwW2kjhwQgGxSk2GlwupdLGCltUii92jThgHSEJReeGszVEr/IiW00hpqxe+5he q0zpBlQ/KueAS0nmBdEBeT6/czgenABRTFFaKvR/nWZ2onzEfC+ye13jEs9x53yeHN2lEwP1u csnM6t9BFirVtKPTOOK6xNvadr/AxJVihzeqchnh57SWLwrJwOUFyqgrG+l74PoPdvOr0/SBv tC3Yet2pM4fh13CrsTxrwpPD/5WzvBzncJ8wlA7ScGDMLgRGc1pti6JG+D61JcaOwTlYrZWgB 8G6Zv9kQE9CvLiU4ydU6HdeXosmfBBWesGjJSobRYEAzgX6hnVc4wT+3TAH0hwba1ln10rqW2 CiRXMAms6KWNMuiSaZUlh1Ls8Zeps0wHjZWyS7uV6oN0L4+su5GYfhiGAv8= 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, 15 Dec 2016 23:23:07 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --c77oI4uD9m9FVcktvuBBkkD2SK1lkFbFj Content-Type: multipart/mixed; boundary="twJg6GlU8WcnIpmEi2DRWTNHxQ72uxKp5"; protected-headers="v1" From: Matthias Andree To: freebsd-ports Message-ID: Subject: CFT: OpenVPN 2.4 port update for FreeBSD --twJg6GlU8WcnIpmEi2DRWTNHxQ72uxKp5 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Greetings, I've put up an OpenVPN 2.4-rc1 port for FreeBSD up for testing. Get it from https://people.freebsd.org/~mandree/openvpn-2.4.r1-v1.tar.xz Or review the diff at https://reviews.freebsd.org/D8813 Cheers, Matthias --twJg6GlU8WcnIpmEi2DRWTNHxQ72uxKp5-- --c77oI4uD9m9FVcktvuBBkkD2SK1lkFbFj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJYUyXWAAoJEOQSsVbv84Vah/IQAM1GqMLl94E9wPIrAkW6vLHM Camnw3GVG99rsUn6N9/VAu0XYF/9ULqXfr7uYlVGLTgHzTkQPSc0M13N5vF1Mg5C JJjVu3aiJoOEfSzei+0bq2J8d8Fnqw8+DZWCxu1TbD3aqSrYPk2zF/TQvNYZKdhS T4fxFdCCqp7lv/RgR/wBH1YM56hNxNCxzq+vpm6dDObmAs/W1j2i4WXk1YoM3qDU HQrlfutkBLkMiJtkohPrkKMwwycWn+I71nuK8sOMXc5RjvtAkXDL2NACpwew9TPm zdE1pvZvA6ppJ0c/PZ3k7idkTd+jbUCEvslgxe1ESWqOuLFwpMWJOcf5RMgHs3rb cW9hYOM22wz8PR/B/xy2uz3LTm8L1AWxnRi4YtDyYUd1uLSSJb+p2h22XYFyZieQ jaEaUBML2DvH4F5jWjJeIdzU7Sz8snPi8r68H4Q0K3yQ34FGFCYEfJGsvVsWGvlo 7pxzypJoeexqFOqBd3VhRhl5JANNzV9CvZxTexrzKtNnXxzr5q3fNHe+iPpdnoXD woyW9Eo5KsRKuSanh4KEgKeJzKUx7k1bF3VU9AGcoZEwS7SQ+laGCAHhOy/wr6FG u1seuchsUvOsWRMGUochSRuiAVQYzyBdLl85+PHu/mkjRvpwvy8N9dn6JOWDHwIa qO0PJeykJagYeg8LIQ+Y =Zawc -----END PGP SIGNATURE----- --c77oI4uD9m9FVcktvuBBkkD2SK1lkFbFj-- From owner-freebsd-ports@freebsd.org Fri Dec 16 00:45:53 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A792EC76417 for ; Fri, 16 Dec 2016 00:45:53 +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 70DF31CBD for ; Fri, 16 Dec 2016 00:45:51 +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 85DCE284A0 for ; Fri, 16 Dec 2016 01:45:48 +0100 (CET) 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 A69E82849F for ; Fri, 16 Dec 2016 01:45:47 +0100 (CET) To: freebsd-ports From: Miroslav Lachman <000.fbsd@quip.cz> Subject: can somebody commit this fix for isc-dhcp43 port? Message-ID: <5853393B.2060609@quip.cz> Date: Fri, 16 Dec 2016 01:45:47 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 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: Fri, 16 Dec 2016 00:45:53 -0000 net/isc-dhcp43-server: rc script does not play nice with service -e https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213463 Reported at October, added patch and poudriere log but still uncommitted. Reminded at November and? Still not committed. Miroslav Lachman From owner-freebsd-ports@freebsd.org Fri Dec 16 01:10:50 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFBF1C76DC4 for ; Fri, 16 Dec 2016 01:10:50 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-167.reflexion.net [208.70.211.167]) (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 74B351947 for ; Fri, 16 Dec 2016 01:10:49 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 13787 invoked from network); 16 Dec 2016 01:10:42 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 16 Dec 2016 01:10:42 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.20.0) with SMTP; Thu, 15 Dec 2016 20:10:51 -0500 (EST) Received: (qmail 28590 invoked from network); 16 Dec 2016 01:10:51 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 16 Dec 2016 01:10:51 -0000 Received: from [192.168.1.103] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id E8A74EC8FB9 for ; Thu, 15 Dec 2016 17:10:41 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: The ports collection has some serious issues Message-Id: Date: Thu, 15 Dec 2016 17:10:40 -0800 To: FreeBSD Ports X-Mailer: Apple Mail (2.3251) 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, 16 Dec 2016 01:10:50 -0000 John Marino freebsd.contact at marino.st on Thu Dec 15 16:46:54 UTC 2016 wrote: > For i386 and amd64 users, synth does not require more resources than > portmaster. People on those platforms can't use "resources" as a reason > not to use Synth. From what I can tell, portmaster people hate what > they consider unnecessary rebuilds which both poudriere and synth > (currently [1]) do, but it's this avoidance of rebuilds that cause all > their problems. Also on Thu Dec 15 16:00:47 UTC 2016: > Anybody with a machine that doesn't have a resources to run poudriere or > synth should not be building packages on that machine. Veterans have > the option to use portmaster in a case like that, but it's not something > that should be suggested to newbies. Note: My FreeBSD usage is not from any of the main families of usage. Do not think that I expect things to be biased for my use. My kind of context may well be implicitly not intended to be covered by the above. I wonder if build tool recommendations need some breakout by user categories rather than one grand overall recommendation. This might be just a note of "no specific recommendation" for some category(s). I use my context below as a potential example. I primarily experiment with self hosting FreeBSD activities on powerpc64, powerpc, armv6/armv7, and aarch64, reporting issues that I find. For the powerpc family this has focused on fairly modern clang usage for buildworld and buildkernel -- as well as building ports. This tends to fit me with "developer" and less with "user" in some respects. If synth was buildable and usable on powerpc64, powerpc, armv6/armv7, and aarch64 I likely would have tried it. (I do not want to be using different self-hosting techniques per TARGET_ARCH but instead use one set of techniques on all.) Building synth would take up more time and space than portmaster but I could have tolerated such. For the SD card contexts I tend to have an SSD for the root file system. This likely is uncommon. Only the old powerpc's have fewer than 4 cores/processors supported by FreeBSD: one armv7 has 8 but FreeBSD supports only 4. buildworld with -j 4 or so does take a long time on the armv7 machines (for example). Of course there are large differences in performance compared to modern amd64's. When I tried portupgrade over a time I had problems with ruby in these environments. (amd64 went okay.) I eventually backed off, figuring I'd retry after some significant time in case they were temporary issues. Other than backups/recovery media I have one powerpc64 SSD for experiments, one powerpc SSD, one armv7 SSD (and an SD card) per single board computer type, and the same for the one aarch64 single board computer. Definitely not build-once/distribute-many generally. (But the armv7 context could do a little of that as I'm currently structuring things.) After "pkg autoremove" "portmaster --list-origins" lists 20-30 or so ports in each case. Before the autoremove "pkg info | wc" is under 100 as I remember. I sometimes have patches to ports involved when someone asks me to test such for something that I've reported. And because of binutils problems for powerpc64 I use older versions from svn in the contexts that I deal with targeting powerpc64's (that includes the devel/powerpc64-binutils slave port). For a time devel/powerpc64-gcc could not finish buildworld unless I used an older vintage from svn. I really do use devel/powerpc64-gcc and devel/powerpc64-binutils and devel/powerpc64-xtoolchain-gcc on a powerpc64: a "self hosted cross build" of sorts. Getting devel/powerpc64-gcc installed on a powerpc64 requires a work-around because it is not a true cross-build and some things are not the same if the target architecture is not distinct: I'm operating outside the intended usage model. The work around involves copying/moving some files to the right place/name in the staging area so that installation can find them and complete. [I also use amd64 FreeBSD under virtualbox in another operating system. This context has more to it but is still likely less than is typical.] [Ignoring amd64:] If I had been able to use synth on the variety of machines it would appear that the contribution of my time preferences might have eventually stopped my use. (Not the number of ports rebuilt as such but the systematic time spent.) "Might" because for my context it is not obvious up front what my judgement might be after a trail period. I'm not sure what I would have done about issues like devel/powerpc64-gcc being built and installed on a powerpc64 machine and needing a work around. Or testing patches for ports. I did not try to figure it out since I since I discovered synth was not an option first. I configure to avoid "disk" space issues generally (SSD root filesystems normally, with plenty of space). RAM varies from 1G to 2G Bytes over the armv7's, aarch64, and some powerpc's, but for powerpc64 there is more RAM: 8G, 12G, or 16G Bytes. So if I had the option for these machines only the time "resource" would be likely to have contributed to switching away from synth after experimenting. (Presuming the patches and workarounds were handled.) This may be unusual for armv7 single board computers and the like. Next most likely for resource limitations might be those with less 2G Byte of RAM. So far I've been able to handle what portmaster has done and have mostly used it. I've had fewer problems than I had with portupgrade. But I have had some issues on occasion. [I even used a mix: portmaster to go through the configure prompts up front and then answer "n" then use portupgrade for the actual build based on those configurations.] It would appear to me that some folks avoiding synth and the like are managing tradeoffs. Others are just blocked relative to synth itself or have run into (temporary?) problems with the infrastructure behind some of the alternatives. The result for me was portmaster vs. the most general/powerful infrastructure (poudriere). At least for a time after the other experiments I'm using portmaster for now and dealing with whatever issues are involved. At some point I may try poudriere in each of these environments. But I may find that my context may just not be a good fit to the main powerful tool, time preferences possibly being part of the judgment: occasional extra work possibly preferred to systematic time-taken. === Mark Millard markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Fri Dec 16 01:29:34 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08E2AC8239C for ; Fri, 16 Dec 2016 01:29:34 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (mail.sorbs.net [67.231.146.200]) by mx1.freebsd.org (Postfix) with ESMTP id EDEE11617 for ; Fri, 16 Dec 2016 01:29:33 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from C02LJ0HMFFT4.corp.proofpoint.com (static-58-108-170-168.optusnet.com.au [58.108.170.168]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0OI900K6D8IJ6M60@hades.sorbs.net> for freebsd-ports@FreeBSD.org; Thu, 15 Dec 2016 17:37:34 -0800 (PST) Subject: Re: The ports collection has some serious issues To: Matthieu Volat , list-freebsd-ports@jyborn.se Cc: freebsd-ports@FreeBSD.org References: <20161208085926.GC2691@gmail.com> <3b00e76a-7a97-aa1b-72e9-236161044c3b@m5p.com> <20161215183122.GG5268@pol-server.leissner.se> <20161215201517.2e6bcd39@freedom.alkumuna.eu> From: Michelle Sullivan Message-id: <58534376.9040502@sorbs.net> Date: Fri, 16 Dec 2016 11:29:26 +1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 In-reply-to: <20161215201517.2e6bcd39@freedom.alkumuna.eu> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 01:29:34 -0000 Matthieu Volat wrote: > On Thu, 15 Dec 2016 19:31:22 +0100 > list-freebsd-ports@jyborn.se wrote: > >> On Thu, Dec 15, 2016 at 01:18:05PM -0500, George Mitchell wrote: >>> On 12/15/16 09:40, Warren Block wrote: >>>> On Thu, 8 Dec 2016, Matt Smith wrote: >>>> >>>>> On Dec 08 05:16, Daniil Berendeev wrote: >>>>>> Although portmaster is not releated to the FreeBSD project and is an >>>>>> outside tool, there aren't any alternatives from the project itself. So >>>>>> use it or die. Not a nice situation. >>>>> People have been trying to get portmaster deprecated and removed from >>>>> the handbook but have met with resistance. >>>> Well, yes. Because it works, has no dependencies, and there is no >>>> equivalent replacement. [...] >>> Warren, you have hit the nail on the head. -- George >> +1 >> >> I never have problems with portmaster. >> (But portupgrade could at times be an utter mess, >> I never looked back after switching to portmaster >> many years ago.) >> >> And I'm not at all interested in running poudriere >> or synth, thank you. >> > It seems that if people happy with portmaster keep silent, others will assume it's okay to try to dismiss it; Yup > so here am I, happy with portmaster. Don't worry, the people that have the power will dismiss it when they deem you need to "upgrade" to using synth or poudreire... oh and don't worry they'll remove distfiles and the previous 4 versions of the distfiles so that you can't keep your own local copy running, especially if you publish how to use it yourself. > > I could switch to something else that is feature wise similar; but if it would not written in some quasi-obselete/niche/hipster programing language or involve admin/config tasks like creating repos. > > Until a challenger appears, I'm just going to use and recommend portmaster. > Same. Regards, Michelle From owner-freebsd-ports@freebsd.org Fri Dec 16 01:43:15 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E74CFC828BA for ; Fri, 16 Dec 2016 01:43:15 +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 A43C31234; Fri, 16 Dec 2016 01:43:15 +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 E9E4A2847E; Fri, 16 Dec 2016 02:43:12 +0100 (CET) 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 43A3428417; Fri, 16 Dec 2016 02:43:12 +0100 (CET) To: FreeBSD Ports From: Miroslav Lachman <000.fbsd@quip.cz> Subject: sysutils/php56-fileinfo exit signal Segmentation fault Cc: Alex Dupre Message-ID: <585346AF.3080400@quip.cz> Date: Fri, 16 Dec 2016 02:43:11 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 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: Fri, 16 Dec 2016 01:43:16 -0000 I am running webmail Roundcube on many machines but on one machine file upload (attachment) doesn't work. I tracked it down to PHP extension fileinfo. Everytime I tried to upload a file I got this error in Apache error log: [Fri Dec 16 02:35:27.775113 2016] [core:notice] [pid 6883] AH00052: child pid 6890 exit signal Segmentation fault (11) Sometimes [Fri Dec 16 02:36:02.110390 2016] [core:notice] [pid 6883] AH00052: child pid 6998 exit signal Bus error (10) If fileinfo extension is disabled (removed ext-20-fileinfo.ini from /usr/local/etc/php/) upload works fine. I tried to change the order of extension but it doesn't change anything if it is last or second or anywhere in the middle of the list. I don't know what can be wrong on this machine because all machines have pkgs from the same poudriere repo. All are running Apache 2.4 and PHP 5.6. Does anybody have some idea how to solve this? (I cannot disable fileinfo because it is needed by other websites on this machine) Miroslav Lachman From owner-freebsd-ports@freebsd.org Fri Dec 16 03:03:58 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA8F5C8205B for ; Fri, 16 Dec 2016 03:03:58 +0000 (UTC) (envelope-from pipfstarrd@openmailbox.org) Received: from mail2.openmailbox.org (mail2.openmailbox.org [62.4.1.33]) (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 AE525791 for ; Fri, 16 Dec 2016 03:03:58 +0000 (UTC) (envelope-from pipfstarrd@openmailbox.org) Received: by mail2.openmailbox.org (Postfix, from userid 1001) id 89C15108565; Fri, 16 Dec 2016 03:57:09 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org; s=openmailbox; t=1481857029; bh=68V1zhJQu65MSyoPX+DtcIG6Ucc46mamnvngQxQ+GLM=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=DVyzORqDnQLBBYEAbar7B2g9BvFvQGChOOmZuOlPYevZwExcufv27jkui5DLoYS4M J6a14YxXfIXFL9b8bc2TdYq2QPB/1ye61W/lKeu0/C6EQdyn9UTGR7ytfzJ20f+vWT iMOlEORr3bEJJ6mAGZta30mY3hsnsHbw4St9m+U8= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on h3 X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=NO_RECEIVED,NO_RELAYS, T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Subject: Re: The ports collection has some serious issues DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org; s=openmailbox; t=1481857025; bh=68V1zhJQu65MSyoPX+DtcIG6Ucc46mamnvngQxQ+GLM=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=EowhuLxFK30IvZRWOpNApa3IyaKeIcz3dA06qNOddaNapea8AlgXuhzNW6MJzIwtN TcfzW125vSv6v38+is2aMlb76ZYh5dQwoW5WLGXni/nQJDkZQj7qKaLmIxFQOSsTha oBybwXGBCR/PrdKDzX8u9Bsn6Fzvmxfr7nFCy6Us= To: Warren Block References: Cc: freebsd-ports@FreeBSD.org From: Daniil Berendeev Message-ID: Date: Fri, 16 Dec 2016 02:59:30 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 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, 16 Dec 2016 03:03:59 -0000 > Here, it doesn't look like that. Don't forget that /usr/ports/distfiles > accumulates old versions and must be manually cleaned out from time to > time. portmaster has a couple of options to remove distfiles that are > not needed. > > % du -hd0 /usr/ports > 8.1G /usr/ports > % du -hd0 /usr/ports/distfiles > 6.5G /usr/ports/distfiles > > After copying that to /tmp and deleting distfiles entirely: > > % du -hd0 /tmp/usr/ports > 1.4G /tmp/usr/ports Well, I know that, I were trying to tell that portsnap(8) is fetching HEAD by default and I didn't find any way to change that behavior. So the only way to pick another branch would be fetching the entire svn repository. I need it for development purposes also, so anyway I'd have to do that. But the size of the svn repository causes pure pain. Subversion is not intended for development style that requires keeping lots of branches and tags. Everyone knows that. At the moment, the repository takes ~/> du -h ports-fbsdsvn/ 42G ports-fbsdsvn/ In git, Mercurial, bazaar, well, any modern version control system you can create tons of branches, tags without wasting space or time. -- Cheers~ PGP key fingerprint: 07B3 2177 3E27 BF41 DC65 CC95 BDA8 88F1 E9F9 CEEF You can retrieve my public key at pgp.mit.edu. From owner-freebsd-ports@freebsd.org Fri Dec 16 05:42:20 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF928C80D6F for ; Fri, 16 Dec 2016 05:42:20 +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 799B81685 for ; Fri, 16 Dec 2016 05:42:19 +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 uBG5g9da099725 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 16 Dec 2016 16:42:14 +1100 (AEDT) (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 uBG5g21q079103 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 16 Dec 2016 16:42:02 +1100 (AEDT) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id uBG5g2fX079102 for freebsd-ports@FreeBSD.org; Fri, 16 Dec 2016 16:42:02 +1100 (AEDT) (envelope-from peter) Date: Fri, 16 Dec 2016 16:42:02 +1100 From: Peter Jeremy To: freebsd-ports@FreeBSD.org Subject: Re: The ports collection has some serious issues Message-ID: <20161216054202.GC75755@server.rulingia.com> References: <20161208085926.GC2691@gmail.com> <3b00e76a-7a97-aa1b-72e9-236161044c3b@m5p.com> <20161215183122.GG5268@pol-server.leissner.se> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="jq0ap7NbKX2Kqbes" Content-Disposition: inline In-Reply-To: <20161215183122.GG5268@pol-server.leissner.se> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.7.1 (2016-10-04) 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, 16 Dec 2016 05:42:20 -0000 --jq0ap7NbKX2Kqbes Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2016-Dec-15 19:31:22 +0100, list-freebsd-ports@jyborn.se wrote: >On Thu, Dec 15, 2016 at 01:18:05PM -0500, George Mitchell wrote: >> On 12/15/16 09:40, Warren Block wrote: >> > On Thu, 8 Dec 2016, Matt Smith wrote: >> >=20 >> >> On Dec 08 05:16, Daniil Berendeev wrote: >> >>> >> >>> Although portmaster is not releated to the FreeBSD project and is an >> >>> outside tool, there aren't any alternatives from the project itself.= So >> >>> use it or die. Not a nice situation. >> >> >> >> People have been trying to get portmaster deprecated and removed from >> >> the handbook but have met with resistance. >> >=20 >> > Well, yes. Because it works, has no dependencies, and there is no >> > equivalent replacement. [...] >>=20 >> Warren, you have hit the nail on the head. -- George > >+1 > >I never have problems with portmaster. I don't know about never - I think I managed to get it into a dependency loop once - but I've never had any issues that I could not resolve or that would entice me to look at an alternative. >(But portupgrade could at times be an utter mess, >I never looked back after switching to portmaster >many years ago.) Likewise, portupgrade would explode and shower my system with bits of corrupt database to often for comfort. At least part of that was caused by portupgrade depending on quite a few other ports and getting confused when it updated things whilst it was using them. >And I'm not at all interested in running poudriere >or synth, thank you. Interestingly, the most vocal proponent of deleting portmaster and portupgrade is the author/maintainer of synch. --=20 Peter Jeremy --jq0ap7NbKX2Kqbes Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJYU36qXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs056IQAI9MiJCegijnPGlx2FWiuj6g htRhXeqKp7K6440Te7ExtdSh4q6q2AbNpFRR4aoPEcnTS6nINaWr5A1nm9g8cCbr 0QJLSgQGMsjoPbFjsVeMQktK9w24u7AAcxKoX4A5P8Ab/UoNqy6p1O/WKhpO8vnT T9FeriefxgrMrkFhca3ltyqYf2s85443aiNj5wJv5NJ70ur3cB8zjoTI7xM9Ekvi 8MZZxrLy+zYD/E+J/tQXpl0COzJewuNFOUGzb4PX1GX6uTEsaz/J/CkOxjbVleN2 d/ofLjZqrDqARdQmzWp9Ac6BiSUpoP3GSsFebNTYOGRtEZuocLVhmnyPlI0rpt1h efMufaPSBt3L5Ap8Z8Q3+UgSaVKCaMSd6Qlk/Cd/v9rvBYkCwoIPEgxhnVOnD/kP kmxOWEi+BodeLx/pueG/s93p82Oy0h+EB8/lDueQw2ylyEk6StHz0kl4+vWtc6zk +KiLLMKwNJYImWB6xyhEc/doPKaNpFI6yY88NHdKuCRVEDeyT1E6j8x3Uaa7cNf7 LxspLllm/TfomGRQeWVLXQGMkEvgoFFv3qg0wOIquaxy+wL7uVbDyJddZ7G2yx+v Et80ogfRf5vaMXXH0Jq7FVhzDydAbGEEur80dpHbysNJlarNNI3t5r4LsdJgPg/o hPIBOAw2XjpwiXbC4M20 =uqfb -----END PGP SIGNATURE----- --jq0ap7NbKX2Kqbes-- From owner-freebsd-ports@freebsd.org Fri Dec 16 06:42:26 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3F1EC82BA7 for ; Fri, 16 Dec 2016 06:42:26 +0000 (UTC) (envelope-from tingox@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3AF9E145E for ; Fri, 16 Dec 2016 06:42:26 +0000 (UTC) (envelope-from tingox@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id f82so19597536wmf.1 for ; Thu, 15 Dec 2016 22:42:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=++A3fEaSAX5gfTogi7LQhfOHRWdUS3rJ+xvfUP0E44w=; b=NonpsS3V/5Q0No1A8kU0zxUTvliH794LBnpoDsz01VmaHqC33VhI/o/Qr1ScuA3Osr XYKs1rzWl8OLiE/Bn5W5+jv+7pjX8l98n4h8bTSRowAZoWEF66cra45IL9/aK2WbqeUS dn0aBU+FoHKOoKYG98WgbfN/izpb0Am4eog6eC4Ea/JUliNdO68z4QVNX+0gl2LGkPYp MWX5gD254T/PA80pB65fJs5tz6cN2knrEYemghClQTlV0Tcy9SVMbTy3nu8OBPaXgxc8 G6CdJICMHZ+fbRUyOzsSyraQl5xPtv29jc8En9EZrUpnV9Mk4itlA//twgcscDCtUmBs sZ3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=++A3fEaSAX5gfTogi7LQhfOHRWdUS3rJ+xvfUP0E44w=; b=Mklt4Vnrs8677kYqiDMkc9N1GJaehcL1UAyqLNzjGzbuD1jTa+UU5cnUaRdZik5XKC tc4rrO+kjkn3iOQtKE4Dq4tX2decQ0OpBkydHElE8O13lPRcwEZbtMLbTI5elSkg3yhf ajoH71iw/sUrimjViVg2DyzwGgwwVPNtV9V9os4bmtVxKmgl+XDfbvuRSyKikq72EM7q 9/QucwKnNwRbPgogngOA0Gvqe5qbt82U0o18E2WffGy2EDX0uO42L9dwmBwaRHPEWGrc PG3yVHWWFiazMV1HSgdvN1qX0q95efQfwPmVhbw57mDSZ3yATiZ4NFtFVprIaQcDnAiX Hjnw== X-Gm-Message-State: AKaTC00PxqSCzVgJya1NNLDgGbKmwsEw6leIAKXF+C8N4saG6wAgLvPT5L7DjyehC7HRXyq2pR3DjI0lznuvvw== X-Received: by 10.25.196.72 with SMTP id u69mr386113lff.32.1481870543908; Thu, 15 Dec 2016 22:42:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.190.77 with HTTP; Thu, 15 Dec 2016 22:42:22 -0800 (PST) In-Reply-To: <20161216054202.GC75755@server.rulingia.com> References: <20161208085926.GC2691@gmail.com> <3b00e76a-7a97-aa1b-72e9-236161044c3b@m5p.com> <20161215183122.GG5268@pol-server.leissner.se> <20161216054202.GC75755@server.rulingia.com> From: Torfinn Ingolfsen Date: Fri, 16 Dec 2016 07:42:22 +0100 Message-ID: Subject: Re: The ports collection has some serious issues To: FreeBSD Ports ML Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 06:42:26 -0000 On Fri, Dec 16, 2016 at 6:42 AM, Peter Jeremy wrote: > On 2016-Dec-15 19:31:22 +0100, list-freebsd-ports@jyborn.se wrote: >>On Thu, Dec 15, 2016 at 01:18:05PM -0500, George Mitchell wrote: > >>(But portupgrade could at times be an utter mess, >>I never looked back after switching to portmaster >>many years ago.) > > Likewise, portupgrade would explode and shower my system with bits of > corrupt database to often for comfort. At least part of that was caused > by portupgrade depending on quite a few other ports and getting confused > when it updated things whilst it was using them. > FWIW, I'm a happy portupgrade user. Yes - sometimes it breaks, but it is quite rare, and I am able to fix the breakage when it happens. So for me it is "good enough". >>And I'm not at all interested in running poudriere >>or synth, thank you. > > Interestingly, the most vocal proponent of deleting portmaster and > portupgrade is the author/maintainer of synch. I won't say "never". But I feel that both package builders (poudriere, synth) need some more time to shake out more issues / bugs and get into a better shape first. This isn't based on any specific problems or bugs, more a "felleing2 based on people's feedback in the forums and on mailing lists. If I was interested in package builders, I would spend some time helping to test them. Since my interests related to FreeBSD is on other things / tools / whatever, I spend my "FreeBSD time" on those other things instead. HTH -- Regards, Torfinn Ingolfsen From owner-freebsd-ports@freebsd.org Fri Dec 16 06:45:26 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D5288C82C6D for ; Fri, 16 Dec 2016 06:45:26 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-wj0-x22f.google.com (mail-wj0-x22f.google.com [IPv6:2a00:1450:400c:c01::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 7B3F71654 for ; Fri, 16 Dec 2016 06:45:26 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-wj0-x22f.google.com with SMTP id tk12so85686962wjb.3 for ; Thu, 15 Dec 2016 22:45:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=6FZMcrxN5Y+9yKMpCmz15Pgpb16njbHFvpwT+euLJFU=; b=MAOnPocRsnR7fYQXB+HbbkT0IIGgyh1Yiv53o1J3AA8K4mC3ebohxKuzMO8VUD0A6G FYzwGUaPJwVwf+fMhlgFr5lzUz6jlt8OuX8ZggKa/CsB360vgoeKZYG+rtdXO7i9QLkX tGDE0KlHVDM5r/sGrMGWH1TUeiOO7eUg0QzaXy3DFLIVaI4bxYju97MZGB8fnDs/XyMG ULffASk9d49QcZq7C7C0HeM+Td+O5siI0OthU4YKlC1Y0Piyg3yFv2bEkLIpNaxt35IU 6epPV5EHHLzcCBzj4sb4X6gmzFLpqIgrc7TQ7LJm3tgixNfO0zMyJaSMmdv5tmRprWK/ EVaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=6FZMcrxN5Y+9yKMpCmz15Pgpb16njbHFvpwT+euLJFU=; b=tb5iAZDOlryc5vujFI2gia4q1fh2XzN11/PGuQZqKNapYzF+LwjHupctNLNpvNsWuK TMN6RB949dT3XY1mGegGSMaFUh6AgM97qo9Tq4Hz7WsJqqSbaHhXjqb3yJ2efbOkjIZz KYIz9hzH+mImetE2PQbFPIs9iPWqKOPtJGg3hMH0OxZfngZ8cMR3iuKDhbCJuh+ZDiBT 00MBNr6KzjCSj4d9Yp9NPTnU6rKxdt7JaYy2LhsK+mC4+QkhlBmOiYLNAfHeivQtrKv2 kR69SW3cmwhGk2lPGtraFatO4f0BVaRTCcsqg+ucnFj6CBeCRNK9a8HTjt/ppr+Tpodc sz7w== X-Gm-Message-State: AIkVDXKwGW6VyiCYelP/+sLgjtrFKOfvAIHRo+EDGRCqfzpfb3VrD0mPayBNoUCQ5lHWQ6hXXHwg9P1EHc4/5Q== X-Received: by 10.194.69.230 with SMTP id h6mr1349704wju.63.1481870724808; Thu, 15 Dec 2016 22:45:24 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.28.51.78 with HTTP; Thu, 15 Dec 2016 22:45:24 -0800 (PST) In-Reply-To: <20161216054202.GC75755@server.rulingia.com> References: <20161208085926.GC2691@gmail.com> <3b00e76a-7a97-aa1b-72e9-236161044c3b@m5p.com> <20161215183122.GG5268@pol-server.leissner.se> <20161216054202.GC75755@server.rulingia.com> From: Kevin Oberman Date: Thu, 15 Dec 2016 22:45:24 -0800 X-Google-Sender-Auth: Qy8B3X4HUnM53KBX8Zg_c0m5dNE Message-ID: Subject: Re: The ports collection has some serious issues To: Peter Jeremy Cc: 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: Fri, 16 Dec 2016 06:45:26 -0000 On Thu, Dec 15, 2016 at 9:42 PM, Peter Jeremy wrote: > On 2016-Dec-15 19:31:22 +0100, list-freebsd-ports@jyborn.se wrote: > >On Thu, Dec 15, 2016 at 01:18:05PM -0500, George Mitchell wrote: > >> On 12/15/16 09:40, Warren Block wrote: > >> > On Thu, 8 Dec 2016, Matt Smith wrote: > >> > > >> >> On Dec 08 05:16, Daniil Berendeev wrote: > >> >>> > >> >>> Although portmaster is not releated to the FreeBSD project and is an > >> >>> outside tool, there aren't any alternatives from the project > itself. So > >> >>> use it or die. Not a nice situation. > >> >> > >> >> People have been trying to get portmaster deprecated and removed from > >> >> the handbook but have met with resistance. > >> > > >> > Well, yes. Because it works, has no dependencies, and there is no > >> > equivalent replacement. [...] > >> > >> Warren, you have hit the nail on the head. -- George > > > >+1 > > > >I never have problems with portmaster. > > I don't know about never - I think I managed to get it into a dependency > loop once - but I've never had any issues that I could not resolve or > that would entice me to look at an alternative. > > >(But portupgrade could at times be an utter mess, > >I never looked back after switching to portmaster > >many years ago.) > > Likewise, portupgrade would explode and shower my system with bits of > corrupt database to often for comfort. At least part of that was caused > by portupgrade depending on quite a few other ports and getting confused > when it updated things whilst it was using them. > > >And I'm not at all interested in running poudriere > >or synth, thank you. > > Interestingly, the most vocal proponent of deleting portmaster and > portupgrade is the author/maintainer of synch. > > -- > Peter Jeremy > Just to add another voice of those who use portmaster on a regular basis. I moved to portmaster about seven years ago and have has very few issues with it. I have had issues building ports from time to time, but it's been a long time since i hit one that was not a problem with the port... often related to the options I use. I like that it has no dependencies. I like that it is very stable. There are things I would like to see changed, but I would be very upset to lose it. Since it is stable, the only way I would lose it is if the underlying port structure changed in a way that required work on it. Saying that synth and poudriere are replacements for portmaster/portupgrade simply indicate lack of familiarity with my (and others) use cases. I have used synth and it is excellent, but not on my development system where everything is built from source and I hope always will be. I have found portupgrade too fragile for the reasons mentioned. I had to clean up a mangled database once too often. (Yes, it is a flat text db, so it can be fixed manually, but it is NOT fun!) -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-ports@freebsd.org Fri Dec 16 07:24:23 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B974BC8250B for ; Fri, 16 Dec 2016 07:24:23 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-ua0-x236.google.com (mail-ua0-x236.google.com [IPv6:2607:f8b0:400c:c08::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7407C7A3; Fri, 16 Dec 2016 07:24:23 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: by mail-ua0-x236.google.com with SMTP id 51so30493135uai.1; Thu, 15 Dec 2016 23:24:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fzCv1Mtx9hg4g2GHMwRYpEFNtDZ/94SrjV9vj9et2NI=; b=OFsBlcrj6l8aro5fzUmBwKpQdSGf1+HMUPbfKe1xZxy+aKVDxRNVHnu8Q1Uf/Qg3Z1 eVmN47sndjaINVpdHQZA1FSXaHj+HDRUPzyZJ+pwuBMXb1xYHe6vCgGZt/MhVKM1YDR6 sEfjsAqLZR5ZmpVyHeK2fgr0PTEHNXmKcM4MSQAZTZBkY3iaLH/CAmWnL4fBcz3XlCMv P6Ud9fD/ZitAS5/tIvEjiryf+aie1TGoNNSqCiqNXPzWI7oyrmgUwz3nqZypHeWXwsSb 9IkKAH4heuhC0AtcJr77BzzhaeURFHoKqXxsy0YNQYdnXTch/rgTrlZpcHaLLADreLBO 2J6w== 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=fzCv1Mtx9hg4g2GHMwRYpEFNtDZ/94SrjV9vj9et2NI=; b=QxZF+4nuh0KcRjXcYEuv1A1OBSR0iV2IjVrDNG5bv+ckXIKdRNbe+ebJv7Lpji/5Jj drNgog3TC3wtbmI0287iPIlQOtwLNhQqEEgprPG9M3c4OPmW67SnGuXM/T1TK8Rjm5Pn is2kE+BmI17SYIWd51AgnE9+KTCgmbA09KDmdmXaTNfLNJR6X/Wu+qQfD0TnkCWE6bEt voHMr0vlrH8w8gUBsrly/7DNoEsJSMM066dMEgaU/AUrQRMIKnmXf/kbqVdYv/lzozg6 WrvwCc4A6XG5AbBam/jB2dEYCzl4UB126hiQSNs/0pha7EOj+I6Dj6dpBYyZ6Tv2PznQ opLA== X-Gm-Message-State: AKaTC02Zdw4iHKo+fApa0G0GUyEVKinC1SEPf6mojdLiGXa0m+OVFgt/16z4DvDnHgBROymHor195WJtpgwkdw== X-Received: by 10.176.82.48 with SMTP id i45mr1145424uaa.126.1481873062340; Thu, 15 Dec 2016 23:24:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.103.47.83 with HTTP; Thu, 15 Dec 2016 23:24:21 -0800 (PST) In-Reply-To: References: <3e7f94efc6428181a289742d7dd627df@acheronmedia.com> <20161215170154.0ca2017914c0bb032516b413@gmail.com> From: David Demelier Date: Fri, 16 Dec 2016 08:24:21 +0100 Message-ID: Subject: Re: (In)Stability of the Quarterly Branch To: Matthew Seaman Cc: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 07:24:23 -0000 2016-12-15 17:25 GMT+01:00 Matthew Seaman : > On 2016/12/15 16:01, Olivier Duchateau wrote: >>> The problem is that there are no tests in FreeBSD ports. All source >>> based systems I've tested: pkgsrc, FreeBSD ports, OpenBSD, Gentoo; >>> FreeBSD is the one that have the most instability. Not to mention >>> committers that commit without testing the port, just look at >>> www/redmine to get your point of view on that issue. > >> Are your serious when you said, there're no tests on FreeBSD ports. I >> can tell you Xfce ports are tested with FreeBSD i386 9.3 and amd64 >> 11.0 machines (on real hardware, no virtualization), and on poudriere >> with Gtk+ 3.20 (port version is not not in ports tree, it's defaut >> toolkits for the next stable release 4.14). >> >> For the LXQt desktop is the same thing (tested with official ports >> tree Qt5 and which one in plasma5 branch (on KDE repository). >> >> I'm also working on the Pantheon desktop (desktop environment of >> Elementary OS, I use Vala 0.30.2 and Vala 0.34.4, in order to test >> stability of applications. >> >> I use also OpenBSD macppc, it's piece of shit. WebKit browers are >> broken, Xfce components crash often, stable branch is outdated, fix >> are not propagated in stable branch. Personally I prefer the FreeBSD >> scheme, because I'm sure it's quite stable. > > Most port committers will run compile tests any time they update a port: > the better ones will test compilation on all supported FreeBSD versions > and all hardware architectures they have access to (ie. generally i386 > and amd64). > I'm not talking about being sure that the port builds, but that the software works. This is a next step that is too often forgotten. For example I remember several years ago having a problem with audio/mumble. The port was building fine, the window opened fine but it was impossible to speak because there was a problem regarding the CELT libraries IIRC. That a port build is nice, that it works is better. And it's the same thing for www/redmine, each time I install it on a fresh machine, `service redmine start` won't start (after configuring of course) because the Gemfile is broken again. These are not the only ones. Glade also suffers a bug that makes it almost unusable. > Additionally the package build cluster will rebuild any modified ports > within a few days for all of the OS versions and architectures the > project tries to provide ports for: that's yet another level of > validating the coding of the port itself. > > However, I believe the OP's point is that *we do not routinely run the > software's own built-in regression tests for the packages we succeed in > building*. This is something that is slowly coming. For instance, you > can run 'make test' for many python, ruby or perl packages and see those > tests being run. TEST_DEPENDS is pretty much standardized as the way to > install dependencies required for testing nowadays. > Yes, I fully understand the requirements of such tests. I just would like that maintainers test the port by building it and *by running* them. This is time consuming for sure, but if the maintainers have no time, then just keep an old but fully working version :-) Regards, -- Demelier David From owner-freebsd-ports@freebsd.org Fri Dec 16 07:54:25 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E967C82B8C for ; Fri, 16 Dec 2016 07:54:25 +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 D50D1144E for ; Fri, 16 Dec 2016 07:54:24 +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 D7EB620990 for ; Fri, 16 Dec 2016 02:54:22 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute7.internal (MEProxy); Fri, 16 Dec 2016 02:54:22 -0500 DKIM-Signature: v=1; a=rsa-sha1; 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=xKjPGBJrbGEnGfVXd35yADvirr E=; b=nP6852vvdJJBM15c2PxgCqgzpBtf6o9IaP00fXDvzVoep1SyqVr4bJ42GO lpK+XofyunN6SB61Bus8eUHPi+1YAHvcVPUblMh/yqlfq1BAqqH3NUWQLd9hhfq9 II/mtPXfnWmcg9RAkWEhDmY+FadyBIXUUR0UvsPk0yse9Rf0M= DKIM-Signature: v=1; a=rsa-sha1; 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=smtpout; bh=xK jPGBJrbGEnGfVXd35yADvirrE=; b=trlijXTQQ4OAKLS6vhIDqDSCbtfYfNpiY8 Mvm5isXg1ZGB6bxUS8QmT00CLo4Aj2TCbi/SKpBcUPHV6phjm8JFpSFmfBHSLAMa uYjGbt/zygqz/htu/Db3xf5FPtTyU7LVE8UQBkCUFhdhaeVBd4JVUtRUwY+NJZoW 2TSNCUzK8= X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id B96B748001; Fri, 16 Dec 2016 02:54:22 -0500 (EST) Message-Id: <1481874862.2026028.820904953.14AFC6AA@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-bb5bdba7 References: <20161208122802.5d6dy7hjkkusms7h@ivaldir.etoilebsd.net> Subject: Re: The ports collection has some serious issues In-Reply-To: Date: Fri, 16 Dec 2016 08:54:22 +0100 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, 16 Dec 2016 07:54:25 -0000 On Mon, 12 Dec 2016, at 17:20, Julian Elischer wrote: > > Have you considered using things like poudriere that would allow you to build > > your own repository with your own set of packages and options. > > > > You will benefit: > > - ability to use pkg for your upgrades > > - ability to use customize your packages > > - safe rebuild process (in case of broken ABI) > > > > Best regards, > > Bapt > I'm actually slowly moving to this if I can work out how to specify my > own chroot image, and a few other things I need to tweak. (my own sets > of patches to add). Hi Julian, I've been doing this with poudriere + pkg + git for a couple of years now very happily, using a lagging ports checkout (similar to the quarterly branch but taken at our convenience), and git rebasing our custom patches so they "float" up to the top. We're using it at iwantmyname.com now as well. The guts of it is: - use poudriere as usual but with a git-backed /usr/ports - store custom patches in /usr/ports and push to https://github.com/ideegeo/ports/ until they get committed in FreeBSD ports tree - git rebase periodically to pull in shiny bits from git://github.com/freebsd/freebsd-ports master branch - ansible pkg triggers a poudriere run whenever we add a new package to the list - these are made available via our pkg repo to our servers - in practice, ansible is used to set up the whole stuff from scratch including letsencrypt certs for the https://pkg.example.org/ but these are the pre-automation steps I started with. Here are the raw notes from our wiki and that should be sufficient for you to try this out on a test VM somewhere. I assume I've forgotten stuff or made errors but promise to blog it over Christmas with a longer explanation. https://gist.github.com/dch/ec2693c051c66dcd2f17b30fc575a910 BTW I'm not exactly sure what you mean about a custom chroot image, but I imagine you can fiddle with the poudriere base in zroot/poudriere/jails/11_amd64 to your heart's content and it will be used during the build. A+ Dave From owner-freebsd-ports@freebsd.org Fri Dec 16 08:01:20 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CC5DC82FA7 for ; Fri, 16 Dec 2016 08:01:20 +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 32C1A181D for ; Fri, 16 Dec 2016 08:01:20 +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 BA5A8209E9 for ; Fri, 16 Dec 2016 03:01:18 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute7.internal (MEProxy); Fri, 16 Dec 2016 03:01:18 -0500 DKIM-Signature: v=1; a=rsa-sha1; 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=7nlMsvNNc0oEiYiabEqwUorofz 8=; b=qAgmPloOgVsRHlAjHy9DbBs2Qb8F4+PQlsAfK9EYnNbX26pBBBTWcF6/or OlqEPtCf7bcRnkfcL85f5+81Wvr5U8NQQkeIolCjowC35RQAr2GFqMKO4l7IXIxf 4TeXo1g9/tc18zvGgRjrUCNp3l6pZe0Hly3q/NJ5z+iut4Gto= DKIM-Signature: v=1; a=rsa-sha1; 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=smtpout; bh=7n lMsvNNc0oEiYiabEqwUorofz8=; b=NBa18Xa0VSgLfPhQFZxGFDpWA74ssBHAuq gHGrrcHfybWQQYe7wGrbKCdgq09R5Yf2FfomkH3QBcyuogUef6h1NtYjVqhCY46m EuB9DkOVRJssM+ZJCaMiWF99rz0rTbGdbizE6E0AucWHWziboN53pFOO41T36aVs x1FS2+RsY= X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 9DCCE48001; Fri, 16 Dec 2016 03:01:18 -0500 (EST) Message-Id: <1481875278.2027307.820920449.18442D1C@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-bb5bdba7 In-Reply-To: <0b018f88-4b64-67c8-a938-ae45fc19d08f@gjunka.com> Date: Fri, 16 Dec 2016 09:01:18 +0100 References: <7c73fc75-b4d9-063d-02f9-628e06f8d4bd@freebsd.org> <20161207025955.GA21488@Silverstone> <3a97d014-1b8b-7e34-6704-1ee5fd8b97ca@m5p.com> <0b018f88-4b64-67c8-a938-ae45fc19d08f@gjunka.com> Subject: Re: what is the purpose of the quarterly ports branches? 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, 16 Dec 2016 08:01:20 -0000 On Tue, 13 Dec 2016, at 23:14, Grzegorz Junka wrote: > I heard that ports' SVN is mirrored to Github. Isn't it enough to just > create a branch or tag for each quarterly release? Even if quarterly > packages are deleted, re-building packages from such branch/tag should > allow to recreate those packages as required since the same code would > give the same packages? These branches already exist BTW: https://github.com/freebsd/freebsd-ports/tree/branches/2016Q3 A+ Dave From owner-freebsd-ports@freebsd.org Fri Dec 16 08:05:38 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3166C82284 for ; Fri, 16 Dec 2016 08:05:38 +0000 (UTC) (envelope-from tz@FreeBSD.org) Received: from toco-domains.de (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 704791BD9; Fri, 16 Dec 2016 08:05:38 +0000 (UTC) (envelope-from tz@FreeBSD.org) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id D6C021AAF07A; Fri, 16 Dec 2016 09:05:34 +0100 (CET) Subject: Re: The ports collection has some serious issues To: Miroslav Lachman <000.fbsd@quip.cz>, marino@freebsd.org, FreeBSD Mailing List , wblock@wonkity.com References: <3959e18e-5819-b2c5-69a9-c71ce1282383@marino.st> <3cf805df-eb25-187c-8bf9-b6c2be5e977d@marino.st> <3daf4aea-82ea-de8f-86d8-5c3b19a1f8a3@marino.st> <5852D631.4090208@quip.cz> From: Torsten Zuehlsdorff Message-ID: <3ff99214-41f0-b34b-a343-63e1671d4b16@FreeBSD.org> Date: Fri, 16 Dec 2016 09:05:33 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <5852D631.4090208@quip.cz> Content-Type: text/plain; charset=windows-1252; 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: Fri, 16 Dec 2016 08:05:38 -0000 On 15.12.2016 18:43, Miroslav Lachman wrote: > John Marino wrote on 2016/12/15 17:46: > >> [1] I've got it on my todo list to provide a new method that would >> eliminate the "my builder just rebuilt 150 packages, but pkg(8) only >> upgraded 2 packages" issue that some users don't want to see. It's a >> lot more complicated than the conservative yet bulletproof approach >> currently used by poudriere and synth. > > This is interesting case - we are running own Poudriere repo and I am > fine with it. But I am a bit nervous when I know 150 packages was > rebuilt and just 2 upgraded by pkg. In this case I want pkg to update > (reinstall) all of them. > If something changed so that 150 packages must be rebuilt why pkg > doesn't reinstall them? Isn't it the possible place for problems after > upgrade? Not really. I found the following explanation from babt about this behavior: https://lists.freebsd.org/pipermail/freebsd-ports/2015-January/097569.html Since its from last year, it is maybe outdated. But if this issue still stands, its worth addressing it. Greetings, Torsten From owner-freebsd-ports@freebsd.org Fri Dec 16 08:56:26 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B993BC8244C for ; Fri, 16 Dec 2016 08:56:26 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp205.alice.it (smtp205.alice.it [82.57.200.101]) by mx1.freebsd.org (Postfix) with ESMTP id 51A1E1C96 for ; Fri, 16 Dec 2016 08:56:25 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (79.18.61.100) by smtp205.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 585272E30046D6AD for freebsd-ports@freebsd.org; Fri, 16 Dec 2016 09:56:23 +0100 Received: from guardian.ventu (bane.local.netfence.it [10.1.2.15]) (authenticated bits=0) by soth.ventu (8.15.2/8.15.2) with ESMTPSA id uBG8tvFM004430 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 16 Dec 2016 09:56:00 +0100 (CET) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host bane.local.netfence.it [10.1.2.15] claimed to be guardian.ventu Subject: Re: The ports collection has some serious issues To: freebsd-ports@freebsd.org References: <20161208085926.GC2691@gmail.com> <3b00e76a-7a97-aa1b-72e9-236161044c3b@m5p.com> <20161215183122.GG5268@pol-server.leissner.se> <20161216054202.GC75755@server.rulingia.com> From: Andrea Venturoli Message-ID: <569b4856-41f2-fbde-dc2c-0fa01efab84b@netfence.it> Date: Fri, 16 Dec 2016 09:55:56 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 10.1.2.13 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, 16 Dec 2016 08:56:26 -0000 On 12/16/16 07:42, Torfinn Ingolfsen wrote: > FWIW, I'm a happy portupgrade user. Me too. I just frequently run into a bug: when icu is updated, somehow the old libraries are not saved and all ports depending on icu break. Now I know that I should take care with that single port. Also, I wish I would be to be able to "portupgrade" a jail, i.e. running portupgrade in base and update the ports inside jails, without the need to install portupgrade (and ruby and every other dependency) in the jail. That said, I've been considering the move to poudriere, but that's a low priority task. bye av. From owner-freebsd-ports@freebsd.org Fri Dec 16 10:08:57 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 187DCC77B04 for ; Fri, 16 Dec 2016 10:08:57 +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 980F7163A; Fri, 16 Dec 2016 10:08:56 +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 E8A0B1AAF07A; Fri, 16 Dec 2016 11:08:53 +0100 (CET) Subject: Re: (In)Stability of the Quarterly Branch To: David Demelier , Matthew Seaman References: <3e7f94efc6428181a289742d7dd627df@acheronmedia.com> <20161215170154.0ca2017914c0bb032516b413@gmail.com> Cc: freebsd-ports@freebsd.org From: Torsten Zuehlsdorff Message-ID: <7e071aa9-4fd8-9e6e-07f1-d0fa6632087a@toco-domains.de> Date: Fri, 16 Dec 2016 11:08:53 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; 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: Fri, 16 Dec 2016 10:08:57 -0000 On 16.12.2016 08:24, David Demelier wrote: > 2016-12-15 17:25 GMT+01:00 Matthew Seaman : >> On 2016/12/15 16:01, Olivier Duchateau wrote: >>>> The problem is that there are no tests in FreeBSD ports. All source >>>> based systems I've tested: pkgsrc, FreeBSD ports, OpenBSD, Gentoo; >>>> FreeBSD is the one that have the most instability. Not to mention >>>> committers that commit without testing the port, just look at >>>> www/redmine to get your point of view on that issue. >> >>> Are your serious when you said, there're no tests on FreeBSD ports. I >>> can tell you Xfce ports are tested with FreeBSD i386 9.3 and amd64 >>> 11.0 machines (on real hardware, no virtualization), and on poudriere >>> with Gtk+ 3.20 (port version is not not in ports tree, it's defaut >>> toolkits for the next stable release 4.14). >>> >>> For the LXQt desktop is the same thing (tested with official ports >>> tree Qt5 and which one in plasma5 branch (on KDE repository). >>> >>> I'm also working on the Pantheon desktop (desktop environment of >>> Elementary OS, I use Vala 0.30.2 and Vala 0.34.4, in order to test >>> stability of applications. >>> >>> I use also OpenBSD macppc, it's piece of shit. WebKit browers are >>> broken, Xfce components crash often, stable branch is outdated, fix >>> are not propagated in stable branch. Personally I prefer the FreeBSD >>> scheme, because I'm sure it's quite stable. >> >> Most port committers will run compile tests any time they update a port: >> the better ones will test compilation on all supported FreeBSD versions >> and all hardware architectures they have access to (ie. generally i386 >> and amd64). > > I'm not talking about being sure that the port builds, but that the > software works. This is a next step that is too often forgotten. For > example I remember several years ago having a problem with > audio/mumble. The port was building fine, the window opened fine but > it was impossible to speak because there was a problem regarding the > CELT libraries IIRC. I really support this, but from a committer perspective its quite impossible. Often enough we just have no idea how the port needs to work - so we must trust the maintainer. But too often there is none. >> Additionally the package build cluster will rebuild any modified ports >> within a few days for all of the OS versions and architectures the >> project tries to provide ports for: that's yet another level of >> validating the coding of the port itself. >> >> However, I believe the OP's point is that *we do not routinely run the >> software's own built-in regression tests for the packages we succeed in >> building*. This is something that is slowly coming. For instance, you >> can run 'make test' for many python, ruby or perl packages and see those >> tests being run. TEST_DEPENDS is pretty much standardized as the way to >> install dependencies required for testing nowadays. >> > > Yes, I fully understand the requirements of such tests. I just would > like that maintainers test the port by building it and *by running* > them. This is time consuming for sure, but if the maintainers have no > time, then just keep an old but fully working version :-) There are two problems with this: 1) Many ports have no maintainer 2) Even more ports have no tests at all I'm a big fan for testing. I test every software i wrote and in every firm i worked i had the lowest bug count. But if you try to teach other people to write tests too you hit a hard wall... So we need to address multiple problems. I'm currently working on an project to improve the management of the ports-tree. Hopefully i can free some time for all so we can test the runtime much better. Greetings, Torsten From owner-freebsd-ports@freebsd.org Fri Dec 16 10:08:59 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3ADDDC77B0B for ; Fri, 16 Dec 2016 10:08:59 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0CD781645 for ; Fri, 16 Dec 2016 10:08:58 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-230-194.lns20.per1.internode.on.net [121.45.230.194]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id uBGA8mVH055183 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Fri, 16 Dec 2016 02:08:51 -0800 (PST) (envelope-from julian@freebsd.org) Subject: Re: (In)Stability of the Quarterly Branch To: freebsd-ports@freebsd.org References: <3e7f94efc6428181a289742d7dd627df@acheronmedia.com> <2bd42508-a1f9-b0f2-e329-51af36604a45@toco-domains.de> From: Julian Elischer Message-ID: Date: Fri, 16 Dec 2016 18:08:43 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <2bd42508-a1f9-b0f2-e329-51af36604a45@toco-domains.de> Content-Type: text/plain; charset=windows-1252; 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: Fri, 16 Dec 2016 10:08:59 -0000 On 15/12/2016 9:43 PM, Torsten Zuehlsdorff wrote: > On 15.12.2016 14:16, David Demelier wrote: [...] >> >> What I want: a ports tree that matches the FreeBSD version like >> OpenBSD. You have FreeBSD 11.0? You get a ports tree for that version >> specifically. No major update, no breaking changes. Just bug fixes. >> That will also simplify a lot FreeBSD ports by not having thousands of >> conditional checking the FreeBSD version. > > That what i really, really, really NOT want. I have regular problems > with our admins because of that. You want a specific version of an > software? No problem: just install a specific version of your > operation system. Need two of them, but they are not in this bundle? > To bad, than you need a new server. This is an daily-base scenario i > really don't want to port to FreeBSD. the problem I have is that on the one machine the UI people want node-x.y and the VM configuration people need boto-a.b, but boto-a.b and node-x.y don't exist at the same time in the ports tree and there is no snapshot of packages when they exist.. it's like saying "that dinosaur and this dinosaur never met because one was Jurassic and the other was Triassic. To make it worse the packages taken from different times insist on installing different versions of some other package, so I can't just take packages from different times (because they OVERSPECIFY their dependencies,, it may work but I don't get the chance because the install balks). So I'm left with compiling.. If I use poudriere I need otmake a synthetic tree with different revisions, bus the API for the ports tree moves so fast that often you cant; even do that because one requires mk/uses/python.mumble and theother wants some incompatible other change. So the problems I see are 1/ over specification of dependencies, leading to artificial requirements to upgrade things. 2/ leaf dependencies having too many options, leading to exponential fan-out of dependencies. 3/ API changes too frequent, and not enough care taken thinking about what happens if one needs to get a back-rev version of something. 4/ ports not always noticing when a dependency package is installed and compiling the dependency anyhow. here's an example; 'tracker' is a simple package. but requires the following makefiles to be in sync API wise. # Build dependencies TRACKER_DEP_PORTS:= devel/desktop-file-utils devel/gettext-tools devel/gmake graphics/gtk-update-icon-cache TRACKER_DEP_PORTS+= print/indexinfo textproc/intltool devel/gettext lang/perl5.20 lang/python27 graphics/poppler TRACKER_DEP_PORTS+= devel/gobject-introspection textproc/libxslt devel/pkgconf multimedia/gstreamer1-plugins TRACKER_DEP_PORTS+= devel/xdg-utils converters/o3read graphics/poppler-utils www/w3m TRACKER_DEP_PORTS+= devel/desktop-file-utils graphics/gtk-update-icon-cache multimedia/gstreamer1-plugin TRACKER_DEP_PORTS+= devel/dbus-glib mail/gmime26 sysutils/hal textproc/raptor sysutils/e2fsprogs TRACKER_DEP_PORTS+= misc/e2fsprogs-libuuid devel/icu multimedia/libmediaart devel/librest TRACKER_DEP_PORTS+= multimedia/totem-pl-parser audio/flac audio/libvorbis textproc/libcue TRACKER_DEP_PORTS+= audio/libogg audio/taglib graphics/poppler-glib graphics/libgxps TRACKER_DEP_PORTS+= devel/libgsf textproc/exempi textproc/wv graphics/libexif TRACKER_DEP_PORTS+= graphics/giflib graphics/png graphics/tiff devel/gettext-runtime TRACKER_DEP_PORTS+= accessibility/atk graphics/gdk-pixbuf2 devel/glib20 x11-toolkits/gtk30 TRACKER_DEP_PORTS+= textproc/libxml2 x11-toolkits/pango archivers/libarchive databases/sqlite3 TRACKER_DEP_PORTS+= devel/libffi devel/pcre converters/libiconv graphics/cairo devel/bison TRACKER_DEP_PORTS+= lang/python2 x11/libXext x11/libXrender x11/libX11 x11/libXinerama TRACKER_DEP_PORTS+= x11/libXi x11/libXrandr x11/libXcursor x11/libXfixes x11/libXdamage TRACKER_DEP_PORTS+= x11/libXcomposite x11-toolkits/libXt graphics/jasper graphics/jbigkit graphics/jpeg-turbo TRACKER_DEP_PORTS+= x11-fonts/fontconfig x11-fonts/libXft print/freetype2 print/harfbuzz x11-fonts/xorg-fonts-truetype TRACKER_DEP_PORTS+= x11-fonts/encodings misc/shared-mime-info misc/hicolor-icon-theme textproc/p5-XML-Parser security/libgcrypt TRACKER_DEP_PORTS+= multimedia/gstreamer1 misc/iso-codes devel/orc devel/dbus multimedia/v4l_compat TRACKER_DEP_PORTS+= sysutils/policykit devel/libvolume_id sysutils/consolekit misc/pciids sysutils/gnome_subr TRACKER_DEP_PORTS+= sysutils/dmidecode ftp/curl textproc/gtk-doc lang/vala security/ca_root_nss TRACKER_DEP_PORTS+= devel/libsoup-gnome multimedia/libquvi09 textproc/expat2 devel/cmake graphics/lcms2 TRACKER_DEP_PORTS+= graphics/openjpeg15 graphics/poppler-data graphics/libwmf accessibility/at-spi2-atk graphics/libepoxy TRACKER_DEP_PORTS+= graphics/colord print/cups x11-themes/adwaita-icon-theme textproc/xmlto x11/xprop TRACKER_DEP_PORTS+= x11/xset devel/boehm-gc TRACKER_DEP_PORTS+= misc/dejagnu x11/xcb-util-renderutil graphics/libGL graphics/libEGL x11/glproto TRACKER_DEP_PORTS+= x11/dri2proto x11/pixman x11/renderproto devel/xorg-macros x11/bigreqsproto TRACKER_DEP_PORTS+= x11/xcmiscproto x11/xextproto x11/xtrans x11/kbproto x11/inputproto TRACKER_DEP_PORTS+= x11-fonts/xf86bigfontproto x11/libXau x11/libXdmcp x11/xproto x11/libxcb TRACKER_DEP_PORTS+= devel/m4 x11/xineramaproto x11/fixesproto x11/randrproto x11/damageproto TRACKER_DEP_PORTS+= x11/compositeproto x11/libSM devel/nasm graphics/graphite2 x11-fonts/font-bh-ttf TRACKER_DEP_PORTS+= x11-fonts/font-misc-meltho x11-fonts/font-misc-ethiopic x11-fonts/mkfontscale x11-fonts/font-util x11-fonts/dejavu TRACKER_DEP_PORTS+= security/libgpg-error shells/bash misc/getopt textproc/docbook-xsl print/libpaper TRACKER_DEP_PORTS+= devel/libatomic_ops textproc/docbook-xml x11/libICE multimedia/libv4l TRACKER_DEP_PORTS+= lang/expect lang/tcl86 devel/libcheck x11/xcb-proto devel/libpthread-stubs TRACKER_DEP_PORTS+= x11/xcb-util devel/makedepend devel/libclc devel/llvm36 lang/gcc TRACKER_DEP_PORTS+= devel/binutils x11/presentproto x11/libXxf86vm x11/libxshmfence graphics/libdrm TRACKER_DEP_PORTS+= graphics/libglapi devel/libdevq graphics/gbm textproc/py-sphinx devel/jsoncpp TRACKER_DEP_PORTS+= devel/cmake-modules x11-fonts/mkfontdir x11-fonts/bdftopcf x11-fonts/libfontenc textproc/xmlcatmgr TRACKER_DEP_PORTS+= textproc/docbook textproc/xmlcharent textproc/docbook-sgml sysutils/polkit textproc/jade TRACKER_DEP_PORTS+= textproc/itstool textproc/rarian devel/libsoup TRACKER_DEP_PORTS+= devel/autoconf devel/automake lang/clang36 devel/libedit devel/ninja TRACKER_DEP_PORTS+= devel/py-Jinja2 textproc/py-docutils devel/py-six devel/py-setuptools27 devel/py-babel TRACKER_DEP_PORTS+= textproc/py-pygments textproc/py-sphinx_rtd_theme textproc/py-alabaster textproc/py-snowballstemmer math/gmp TRACKER_DEP_PORTS+= math/mpfr lang/gcc-ecj45 archivers/zip math/mpc x11/xf86vidmodeproto TRACKER_DEP_PORTS+= devel/libpciaccess x11/libXvMC devel/scons x11-fonts/libXfont textproc/iso8879 TRACKER_DEP_PORTS+= textproc/sdocbook-xml lang/spidermonkey170 textproc/py-libxml2 net/glib-networking multimedia/libquvi-scripts09 TRACKER_DEP_PORTS+= net/libproxy lang/lua52 accessibility/at-spi2-core devel/libtool graphics/libglesv2 TRACKER_DEP_PORTS+= graphics/argyllcms textproc/docbook-utils net/avahi-app security/gnutls x11-toolkits/libXmu TRACKER_DEP_PORTS+= x11-fonts/libXfontcache misc/help2man devel/autoconf-wrapper devel/automake-wrapper devel/py-setuptools TRACKER_DEP_PORTS+= devel/gmake-lite textproc/py-MarkupSafe devel/py-pytest devel/py-pytz textproc/py-pystemmer TRACKER_DEP_PORTS+= x11/videoproto x11/libXv x11-fonts/fontsproto devel/nspr devel/gsettings-desktop-schemas that's the fanout of makefiles that making 'tracker ' hits. and if anything goes wrong in any of that.. it stops.. so making a 'blended' system is really hard. yeah yeah "don't do that"... but it's not that simple in the real world. > > This is a good idea. But does not help everytime. Many rubygem based > ports build just fine, but fail afterwards. yeah > > Greetings, > Torsten > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to > "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@freebsd.org Fri Dec 16 10:11:06 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4115C77C3B for ; Fri, 16 Dec 2016 10:11:06 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8FEEA1931 for ; Fri, 16 Dec 2016 10:11:06 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-230-194.lns20.per1.internode.on.net [121.45.230.194]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id uBGAB1OV055196 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Fri, 16 Dec 2016 02:11:04 -0800 (PST) (envelope-from julian@freebsd.org) Subject: Re: what is the purpose of the quarterly ports branches? To: freebsd-ports@freebsd.org References: <7c73fc75-b4d9-063d-02f9-628e06f8d4bd@freebsd.org> <20161207025955.GA21488@Silverstone> <3a97d014-1b8b-7e34-6704-1ee5fd8b97ca@m5p.com> <0b018f88-4b64-67c8-a938-ae45fc19d08f@gjunka.com> <1481875278.2027307.820920449.18442D1C@webmail.messagingengine.com> From: Julian Elischer Message-ID: <19940dc8-40de-81f8-7d79-73e6bfe2dc5a@freebsd.org> Date: Fri, 16 Dec 2016 18:10:56 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <1481875278.2027307.820920449.18442D1C@webmail.messagingengine.com> Content-Type: text/plain; charset=windows-1252; 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: Fri, 16 Dec 2016 10:11:06 -0000 On 16/12/2016 4:01 PM, Dave Cottlehuber wrote: > > On Tue, 13 Dec 2016, at 23:14, Grzegorz Junka wrote: >> I heard that ports' SVN is mirrored to Github. Isn't it enough to just >> create a branch or tag for each quarterly release? Even if quarterly >> packages are deleted, re-building packages from such branch/tag should >> allow to recreate those packages as required since the same code would >> give the same packages? > These branches already exist BTW: > > https://github.com/freebsd/freebsd-ports/tree/branches/2016Q3 the trouble is that the packages are deleted as soon as they are stable. > > A+ > Dave > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@freebsd.org Fri Dec 16 10:30:30 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE617C80219 for ; Fri, 16 Dec 2016 10:30:30 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: from mail.irealone.com (fawn.irealone.com [IPv6:2001:1af8:4010:a07b:10::2]) (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 B74CA15F for ; Fri, 16 Dec 2016 10:30:30 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mail.irealone.com (Postfix, from userid 1002) id 591FB60DCB; Fri, 16 Dec 2016 11:30:28 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=acheronmedia.com; s=mail; t=1481884228; bh=pMc8zfkbfbHOv5Xw/48qONPqOLHlDGCrZCSkEcJ3Cjc=; h=To:Subject:Date:From:In-Reply-To:References:From; b=sKuZapfQUTxnG4cY6uiR33B4dqilM/+G4Wgd9YxQwnRa5vpp2tt31D7M7rXEJa7Dt jxLatjeUz2IUN/aYG90n0/1v0V6BTDUbRMeDwZO2glLjWIObath4qiDKBuymc/8rBT w8whW/caGErcagwbisvA6eTIHFPltrRV8REhZ/i8= To: freebsd-ports@freebsd.org Subject: Re: (In)Stability of the Quarterly Branch X-PHP-Originating-Script: 0:rcube.php MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 16 Dec 2016 11:30:28 +0100 From: "Vlad K." Organization: Acheron Media In-Reply-To: <7e071aa9-4fd8-9e6e-07f1-d0fa6632087a@toco-domains.de> References: <3e7f94efc6428181a289742d7dd627df@acheronmedia.com> <20161215170154.0ca2017914c0bb032516b413@gmail.com> <7e071aa9-4fd8-9e6e-07f1-d0fa6632087a@toco-domains.de> Message-ID: <06804aa11a2fb6aae231d50fd5656389@acheronmedia.com> X-Sender: vlad-fbsd@acheronmedia.com User-Agent: Roundcube Webmail/1.1.7 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, 16 Dec 2016 10:30:31 -0000 On 2016-12-16 11:08, Torsten Zuehlsdorff wrote: > > There are two problems with this: > 1) Many ports have no maintainer > 2) Even more ports have no tests at all We can't have our cake and eat it :) Obviously, a STABLE repo would have to be a subset of ports, not all 26k of them. The criteria I spoke of in the original post would include that each port has a valid maintainer. Maintainer TIMEOUTS would be monitored and port kicked out if the maintainer is gone. For starters, we'd have to enumerate all the ports that have stable upstreams. For example, RoundCube supports both the new 1.2.x repo and the old, legacy 1.1.x. That means 1.1.x could've been added to the STABLE repo and maintained until it EOLs. Second, ports that do not obey some reasonable versioning scheme, eg. major version changes MAY break backwards compatibility, minor MUST not, and major.minor.point MUST be only bugfixes and security. can be added ONLY and ONLY if the MAINTAINER commits to manually checking every change and making sure only security and bugfixes are backported. Third, ports with no unit tests... well.. I don't know how many are there, but perhaps we can make a list of "strategically important" ports for servers and maybe desktops, and those that are strategically important but have no unit tests, would go in, but would require an active maintainer committed to do run tests. I'm sure such a list would be bikeshed into oblivion, but we could at least try... Fourth. It'd be ideal if Poudriere could grow a function that: a) runs port's unit tests b) permutates OPTIONS and for each re-runs the build + unit test. Broken combinations can be automatically marked as BROKEN. Now... automatically: b.1) a patch is automatically generated but a human has to review and commit b.2) the testing infrastructure autocommits (I'm sure portmgr would object to this) b.3) we create a new "stability" database like vuxml which these automated tests can automatically populate Brainstorming here, critique welcome! -- Vlad K. From owner-freebsd-ports@freebsd.org Fri Dec 16 10:38:51 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62916C80598 for ; Fri, 16 Dec 2016 10:38:51 +0000 (UTC) (envelope-from wjw@withagen.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (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 2581EA32; Fri, 16 Dec 2016 10:38:51 +0000 (UTC) (envelope-from wjw@withagen.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id AB25633CD1; Fri, 16 Dec 2016 11:38:39 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y5TShC1l8ScZ; Fri, 16 Dec 2016 11:38:37 +0100 (CET) Received: from [192.168.101.51] (vpn.ecoracks.nl [176.74.240.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id D416533CD0; Fri, 16 Dec 2016 11:38:37 +0100 (CET) Subject: Re: what is the purpose of the quarterly ports branches? To: Julian Elischer , freebsd-ports@freebsd.org References: <7c73fc75-b4d9-063d-02f9-628e06f8d4bd@freebsd.org> <20161207025955.GA21488@Silverstone> <3a97d014-1b8b-7e34-6704-1ee5fd8b97ca@m5p.com> <0b018f88-4b64-67c8-a938-ae45fc19d08f@gjunka.com> <1481875278.2027307.820920449.18442D1C@webmail.messagingengine.com> <19940dc8-40de-81f8-7d79-73e6bfe2dc5a@freebsd.org> From: Willem Jan Withagen Message-ID: Date: Fri, 16 Dec 2016 11:38:35 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <19940dc8-40de-81f8-7d79-73e6bfe2dc5a@freebsd.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 10:38:51 -0000 On 16-12-2016 11:10, Julian Elischer wrote: > On 16/12/2016 4:01 PM, Dave Cottlehuber wrote: >> >> On Tue, 13 Dec 2016, at 23:14, Grzegorz Junka wrote: >>> I heard that ports' SVN is mirrored to Github. Isn't it enough to just >>> create a branch or tag for each quarterly release? Even if quarterly >>> packages are deleted, re-building packages from such branch/tag should >>> allow to recreate those packages as required since the same code would >>> give the same packages? >> These branches already exist BTW: >> >> https://github.com/freebsd/freebsd-ports/tree/branches/2016Q3 > > the trouble is that the packages are deleted as soon as they are stable. It is sort of amusing/depressing/hilarious of all the flavours and ways everybody works with ports. And I've used them all, just hard core building, postmaster, portsnap, pouderiere... Each has its merit, but IMHO everything is not as bad as frozen in stone CentOS packages. Where I have the feeling that I'm years behind on some of the stuff, and the only way out is to start gathering and build manually. Ports is way more comfortable. For the Q-branches: Storage could be an issue, but isn't this why we have ZFS with snapshot/clones.... Just at the end of a Q freeze both ports and distfiles in a snapshot. --WjW From owner-freebsd-ports@freebsd.org Fri Dec 16 12:51:46 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2206C82537 for ; Fri, 16 Dec 2016 12:51:46 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) Received: from taro.utanet.at (taro.utanet.at [IPv6:2001:938:1337:25::25:45]) (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 6545B1B08 for ; Fri, 16 Dec 2016 12:51:46 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=utanet.at; s=rev1; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date:Message-ID:Subject:From:To; bh=LDOGV2+7lX2hK5y3Ctq1ux14ejWBn7h9gjHoHai8OQ0=; b=cttcfTmelqdNvaXq6IIT4axENoW15Sih+yrWVJRYZ/vVO+C5ywALyhAFxXOlb4zK4ZjO45PpV8GQxIkWgZDZw7jKqhlU9Kq/Oa8KK1fOGD8XWEo9TbSpWaDcqXjjrkv1P1111pCXdUqUBIFLDzGcZdtf96uA1Qz96vfgGVZ8MbM=; Received: from plenty.xoc.tele2net.at ([213.90.36.8]) by taro.utanet.at with esmtp (Exim 4.80) (envelope-from ) id 1cHrzE-0000QA-Fo for freebsd-ports@freebsd.org; Fri, 16 Dec 2016 13:51:44 +0100 Received: from 193-83-12-236.adsl.highway.telekom.at ([193.83.12.236] helo=[10.0.0.93]) by plenty.xoc.tele2net.at with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1cHrzE-0005H5-E1 for freebsd-ports@freebsd.org; Fri, 16 Dec 2016 13:51:44 +0100 To: freebsd-ports@freebsd.org From: Walter Schwarzenfeld Subject: Annoying problem lzma - lzmalib Message-ID: <245fde33-3c94-55f0-c675-0cf54aaf9af4@utanet.at> Date: Fri, 16 Dec 2016 13:51:41 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-TELE2-Authenticated-As: cf62768e218b4d81d95cc5390f1bd9dfc8b05683 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 12:51:46 -0000 Hallo ! Some ports fails with "undefined reference....." different statement but points to lzma. Mostly I can solve it with adding LDFLAGS+= -L/usr/lib -llzma to the Makefile. Today it was an update of rpm4. I had to delete lzmali, update rmp4 and reinstall rpm4. In summary I have10 ports with the lzma problem. One of the two solution helps, but it is annoying. Could someone solve the pathproblem with lzma and lzmalib. From owner-freebsd-ports@freebsd.org Fri Dec 16 12:55:33 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71509C827BF for ; Fri, 16 Dec 2016 12:55:33 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) Received: from tatiana.utanet.at (tatiana.utanet.at [IPv6:2001:938:1337:25::25:46]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 333BD1CFD for ; Fri, 16 Dec 2016 12:55:33 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=utanet.at; s=rev1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Subject:References:To; bh=awlldkPtlLc2iJL+kAMyyvD6hK/RTbMyzo8nF6L0uI4=; b=no9Ebx4dlt/3C8nADEbsmplrHK0Q8ePiAIywIQP8yiPb5JaDcpMChyz2qTAiiGp9h6IWv8lpLs69lduuxYA+W2lrgQoU1fFYd82soCA6nhHFVIhXUlBlgltqrUH7ptkpmAR8de/jJ3JU1GpI5SZTV+IJ0I+lLl1Y2nszntcYods=; Received: from paris.xoc.tele2net.at ([213.90.36.7]) by tatiana.utanet.at with esmtp (Exim 4.80) (envelope-from ) id 1cHs2t-0000N8-Eg for freebsd-ports@freebsd.org; Fri, 16 Dec 2016 13:55:31 +0100 Received: from 193-83-12-236.adsl.highway.telekom.at ([193.83.12.236] helo=[10.0.0.93]) by paris.xoc.tele2net.at with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1cHs2t-000199-Cw for freebsd-ports@freebsd.org; Fri, 16 Dec 2016 13:55:31 +0100 To: freebsd-ports@freebsd.org References: <245fde33-3c94-55f0-c675-0cf54aaf9af4@utanet.at> Subject: Re: Annoying problem lzma - lzmalib From: Walter Schwarzenfeld Message-ID: <8ca57c66-a042-fc45-7366-1d37059db652@utanet.at> Date: Fri, 16 Dec 2016 13:55:29 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <245fde33-3c94-55f0-c675-0cf54aaf9af4@utanet.at> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-TELE2-Authenticated-As: cf62768e218b4d81d95cc5390f1bd9dfc8b05683 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 12:55:33 -0000 some typos I had to delete lzmalib, update rmp4 and reinstall lzmalib. From owner-freebsd-ports@freebsd.org Fri Dec 16 13:12:22 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4058CC82CB8 for ; Fri, 16 Dec 2016 13:12:22 +0000 (UTC) (envelope-from tomas@ciernik.sk) Received: from anastasia.ciernik.sk (anastasia.ciernik.sk [IPv6:2a01:390:dc4:0:225:90ff:fed0:7249]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "anastasia.ciernik.sk", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C8C6E793 for ; Fri, 16 Dec 2016 13:12:21 +0000 (UTC) (envelope-from tomas@ciernik.sk) Received: from anastasia.ciernik.sk (localhost [127.0.0.1]) by anastasia.ciernik.sk (Postfix) with ESMTP id D1A6314930A8 for ; Fri, 16 Dec 2016 14:12:08 +0100 (CET) X-Virus-Scanned: amavisd-new at ciernik.sk X-Spam-Flag: NO X-Spam-Score: -5.999 X-Spam-Level: X-Spam-Status: No, score=-5.999 required=6.2 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-2.999] autolearn=ham autolearn_force=no Authentication-Results: anastasia.ciernik.sk (amavisd-new); dkim=pass (2048-bit key) header.d=ciernik.sk Received: from anastasia.ciernik.sk ([127.0.0.1]) by anastasia.ciernik.sk (anastasia.ciernik.sk [127.0.0.1]) (amavisd-new, port 10026) with LMTP id eTtyFrpU1vf8 for ; Fri, 16 Dec 2016 14:12:06 +0100 (CET) Received: from bonaventura.ciernik.local (sona.ciernik.sk [213.160.163.159]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by anastasia.ciernik.sk (Postfix) with ESMTPSA id 26843149301B for ; Fri, 16 Dec 2016 14:12:06 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ciernik.sk; s=2016080510; t=1481893926; bh=yYzQvrQmZvStTT8c6FEAGaHbWqBEvoA8B4HaYiOkGeU=; h=Subject:To:References:From:Date:In-Reply-To; b=LVEIJK+HbgpwsMGHDaxj+3G/Tk/R7APlBRpoFbG22pd9M6/nfDBOQ/yPhECebO7ty RcLOxgPBadcmPIjhtWwj0GysAzool58NUGB15YZk2WkNoIEbS8c1Dfd+UXWaVPPnuM D9KNtPofxC0N1rDsSo5e7IZnCY16RG3kmVfKKSEJyh1NE0mBSoDssAw84tRgFbZyyW JcPT6VEp2asS2QO3AUpEGPZMPTkq3JIyX/G8T2MODw8IRqUYygf2fd6n6bLtTwrTag 0syUpvJadn8PsYs8PluiTX60bwbATJ/qZfzB5jHinQdhcn8qgG56MKVslYTkGl32Or G9o/AnwuGcopw== Subject: Re: sysutils/php56-fileinfo exit signal Segmentation fault To: freebsd-ports@freebsd.org References: <585346AF.3080400@quip.cz> From: tomas@ciernik.sk Message-ID: Date: Fri, 16 Dec 2016 14:12:05 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <585346AF.3080400@quip.cz> Content-Type: text/plain; charset=UTF-8 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, 16 Dec 2016 13:12:22 -0000 Hello, this was also issue for me. I think it is conflict with svn module - after disabling dav_svn_module problem disappeared. Best regards, Tomas Ciernik. Dňa 12/16/2016 o 02:43 Miroslav Lachman napísal(a): > I am running webmail Roundcube on many machines but on one machine file > upload (attachment) doesn't work. I tracked it down to PHP extension > fileinfo. Everytime I tried to upload a file I got this error in Apache > error log: > > [Fri Dec 16 02:35:27.775113 2016] [core:notice] [pid 6883] AH00052: > child pid 6890 exit signal Segmentation fault (11) > > Sometimes > > [Fri Dec 16 02:36:02.110390 2016] [core:notice] [pid 6883] AH00052: > child pid 6998 exit signal Bus error (10) > > If fileinfo extension is disabled (removed ext-20-fileinfo.ini from > /usr/local/etc/php/) upload works fine. > I tried to change the order of extension but it doesn't change anything > if it is last or second or anywhere in the middle of the list. > > I don't know what can be wrong on this machine because all machines have > pkgs from the same poudriere repo. All are running Apache 2.4 and PHP 5.6. > > Does anybody have some idea how to solve this? > > (I cannot disable fileinfo because it is needed by other websites on > this machine) > > Miroslav Lachman > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Fri Dec 16 14:12:54 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69460C83F8B for ; Fri, 16 Dec 2016 14:12:54 +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 2E53DCED for ; Fri, 16 Dec 2016 14:12:53 +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 9DE502849B; Fri, 16 Dec 2016 15:12:49 +0100 (CET) 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 D77C728490; Fri, 16 Dec 2016 15:12:48 +0100 (CET) Subject: Re: sysutils/php56-fileinfo exit signal Segmentation fault To: tomas@ciernik.sk, freebsd-ports@freebsd.org References: <585346AF.3080400@quip.cz> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <5853F660.60402@quip.cz> Date: Fri, 16 Dec 2016 15:12:48 +0100 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: Fri, 16 Dec 2016 14:12:54 -0000 tomas@ciernik.sk wrote on 2016/12/16 14:12: > Hello, > > this was also issue for me. I think it is conflict with svn module - > after disabling dav_svn_module problem disappeared. Thank you for this information. It is true that machine in question have dav_svn_module and other machines doesn't. I am wondering how PHP extensions can conflict with Apache module and how can I solve it. I cannot disable fileinfo nor svn module. And it worked few month ago with PHP 5.5. Miroslav Lachman From owner-freebsd-ports@freebsd.org Fri Dec 16 14:17:06 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9C4CC821F3 for ; Fri, 16 Dec 2016 14:17:06 +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 94EF8EFC; Fri, 16 Dec 2016 14:17:06 +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 7103C1AAF014; Fri, 16 Dec 2016 15:17:04 +0100 (CET) Subject: Re: what is the purpose of the quarterly ports branches? To: Willem Jan Withagen , Julian Elischer , freebsd-ports@freebsd.org References: <7c73fc75-b4d9-063d-02f9-628e06f8d4bd@freebsd.org> <20161207025955.GA21488@Silverstone> <3a97d014-1b8b-7e34-6704-1ee5fd8b97ca@m5p.com> <0b018f88-4b64-67c8-a938-ae45fc19d08f@gjunka.com> <1481875278.2027307.820920449.18442D1C@webmail.messagingengine.com> <19940dc8-40de-81f8-7d79-73e6bfe2dc5a@freebsd.org> From: Torsten Zuehlsdorff Message-ID: Date: Fri, 16 Dec 2016 15:17:03 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; 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: Fri, 16 Dec 2016 14:17:06 -0000 On 16.12.2016 11:38, Willem Jan Withagen wrote: > On 16-12-2016 11:10, Julian Elischer wrote: >> On 16/12/2016 4:01 PM, Dave Cottlehuber wrote: >>> >>> On Tue, 13 Dec 2016, at 23:14, Grzegorz Junka wrote: >>>> I heard that ports' SVN is mirrored to Github. Isn't it enough to just >>>> create a branch or tag for each quarterly release? Even if quarterly >>>> packages are deleted, re-building packages from such branch/tag should >>>> allow to recreate those packages as required since the same code would >>>> give the same packages? >>> These branches already exist BTW: >>> >>> https://github.com/freebsd/freebsd-ports/tree/branches/2016Q3 >> >> the trouble is that the packages are deleted as soon as they are stable. > > It is sort of amusing/depressing/hilarious of all the flavours and ways > everybody works with ports. And I've used them all, just hard core > building, postmaster, portsnap, pouderiere... > Each has its merit, but IMHO everything is not as bad as frozen in stone > CentOS packages. Or Ubunut or or or... One of the big advantages of the portstree is, that you actually get new versions of the software and not just security-fixes. I regularly stumble across actual bugs, which are there for years, just because the are not fixed by purpose. This is really really frustrating. Bringing new versions is a big plus for the ports-tree. And if you don't need them you are free to stay with the old ones. And its easy enough to build and change everything like you want. Ever really tried this for various linux-distros? Its very painful. Greetings, Torsten From owner-freebsd-ports@freebsd.org Fri Dec 16 14:45:13 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5ACC4C82AFD for ; Fri, 16 Dec 2016 14:45:13 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (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 39A5A1D8D for ; Fri, 16 Dec 2016 14:45:12 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id 9F81A43C42; Fri, 16 Dec 2016 08:44:02 -0600 (CST) From: John Marino Reply-To: John Marino To: FreeBSD Mailing List , tingox@gmail.com Subject: The ports collection has some serious issues Message-ID: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> Date: Fri, 16 Dec 2016 08:45:09 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161216-0, 12/16/2016), Outbound message X-Antivirus-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: Fri, 16 Dec 2016 14:45:13 -0000 > > On Fri, Dec 16, 2016 at 6:42 AM, Peter Jeremy wrote: >> On 2016-Dec-15 19:31:22 +0100, list-freebsd-ports at jyborn.se wrote: >> Interestingly, the most vocal proponent of deleting portmaster and >> portupgrade is the author/maintainer of synch. It's not interesting at all. Synth was in a large part created because people were irrationally sticking with portmaster and more frighteningly gaining new users. > I won't say "never". But I feel that both package builders (poudriere, > synth) need some more time to shake out more issues / bugs and get > into a better shape first. This isn't based on any specific problems > or bugs, more a "felleing2 based on people's feedback in the forums > and on mailing lists. I insist that you base this on "specific problems". Speaking for Synth, there are no known bugs in it. There are no pending issues with existing features. It is updated frequently. AFAIK poudriere is updated regularly as well. The above is an accusation that you absolutely must back up with fact because it's basically defamation. > If I was interested in package builders, I would spend some time > helping to test them. Since my interests related to FreeBSD is on > other things / tools / whatever, I spend my "FreeBSD time" on those > other things instead. DragonFly has switched to Synth from poudriere as it's primary package builder. That means it builds entire repositories (25,000 packages) biweekly on multiple servers. It's highly used which serves as continuous testing. I also use it on FreeBSD to test updates to ports. In fact, anyone that updates ports should use either poudriere testport or synth test. (Based on evidence, it's clear that some people whom I won't name publicly never use the QA checks before committing significant changes but that's getting sidetracked). The point is that these tools are in great shape and to imply otherwise needs proof. It's portmaster that's not receiving updates. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-ports@freebsd.org Fri Dec 16 15:06:32 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0FACC830D0 for ; Fri, 16 Dec 2016 15:06:32 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9E22192C for ; Fri, 16 Dec 2016 15:06:32 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: by mailman.ysv.freebsd.org (Postfix) id 9D833C830CF; Fri, 16 Dec 2016 15:06:32 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D290C830CD for ; Fri, 16 Dec 2016 15:06:32 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (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 7B93E92B for ; Fri, 16 Dec 2016 15:06:32 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id 1946543C43; Fri, 16 Dec 2016 09:05:23 -0600 (CST) From: John Marino Reply-To: marino@freebsd.org To: "ports@FreeBSD.org Ports" , Kevin Oberman Subject: The ports collection has some serious issues Message-ID: Date: Fri, 16 Dec 2016 09:06:30 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161216-0, 12/16/2016), Outbound message X-Antivirus-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: Fri, 16 Dec 2016 15:06:32 -0000 From Kevin Oberman: > Just to add another voice of those who use portmaster on a regular basis. I > moved to portmaster about seven years ago and have has very few issues with > it. I have had issues building ports from time to time, but it's been a > long time since i hit one that was not a problem with the port... often > related to the options I use. I like that it has no dependencies. I like > that it is very stable. There are things I would like to see changed, but I > would be very upset to lose it. Since it is stable, the only way I would > lose it is if the underlying port structure changed in a way that required > work on it. > > Saying that synth and poudriere are replacements for portmaster/portupgrade > simply indicate lack of familiarity with my (and others) use cases. I have > used synth and it is excellent, but not on my development system where > everything is built from source and I hope always will be. I have found > portupgrade too fragile for the reasons mentioned. I had to clean up a > mangled database once too often. (Yes, it is a flat text db, so it can be > fixed manually, but it is NOT fun!) "but not on my development system where everything is built from source and I hope always will be" At face value, this doesn't make sense because synth is a tool for building everything from source, so your development system is exactly where it should be installed. So you must be talking about build dependencies of synth (there are no run dependencies). While I think the requirement of rebuilding synth from source is artificial, I've provided a very reasonable approach to solving this which I feel compelled to repeat for the readers of Kevin's post. The solution: Starting with a clean system: 1) install synth from binary package from official freebsd builder (a single package) 2) Configure synth if necessary 3) command synth to build itself 4) pkg delete synth (system is once again clean) 5) pkg add -F /path/to/synth/packages/synth-* Now you have a system containing s/w built by itself. On an modest system less than 4 years old, it might take 30 minutes at most. So the "synth has dependencies" detraction is extremely weak. For people that trust FreeBSD to provide untainted binaries, it's not an issue at all and for the paranoid, it's easily worked around. Saying that the use of Ada limits it to the platforms it can run on natively is a valid detraction, but it's BUILD dependencies really aren't due to the availability of binary packages, the PRIMARY product of the ports tree. RE: poudriere, it has no dependencies. It's just as appropriate on the dev system and adding a jail and configuring it also takes less than 30 minutes. Either is very appropriate for a system that must build everything that is run on it. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-ports@freebsd.org Fri Dec 16 15:40:02 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F913C83B6F for ; Fri, 16 Dec 2016 15:40:02 +0000 (UTC) (envelope-from marquis@roble.com) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 24E7D1B61 for ; Fri, 16 Dec 2016 15:40:01 +0000 (UTC) (envelope-from marquis@roble.com) Date: Fri, 16 Dec 2016 07:34:19 -0800 (PST) From: Roger Marquis To: FreeBSD Mailing List Subject: Re: The ports collection has some serious issues In-Reply-To: <3cf805df-eb25-187c-8bf9-b6c2be5e977d@marino.st> Message-ID: <1612160725340.3123@mx5.roble.com> References: <3959e18e-5819-b2c5-69a9-c71ce1282383@marino.st> <3cf805df-eb25-187c-8bf9-b6c2be5e977d@marino.st> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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, 16 Dec 2016 15:40:02 -0000 > It is every week. Consider the FreeBSD forums as well. > "misuse" and "misunderstanding" failures are attributed to the tool. Let's > stop making excuses for portmaster. It is what it is and we've had years to > evaluate it. If portmaster was part of base I'd agree that it should be deprecated, however, being a port it can be afforded more leeway. All portmaster needs IMO is a strong WARNING message to be displayed on installation A) enumerating some of the potential bugs and B) clarifying that portmaster is third party software that is neither actively maintained nor supported (or recommended?) by FreeBSD. Roger From owner-freebsd-ports@freebsd.org Fri Dec 16 15:54:05 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 29935C80038 for ; Fri, 16 Dec 2016 15:54:05 +0000 (UTC) (envelope-from freebsd.contact@marino.st) 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 1681687A for ; Fri, 16 Dec 2016 15:54:05 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: by mailman.ysv.freebsd.org (Postfix) id 15D69C80034; Fri, 16 Dec 2016 15:54:05 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 157E1C80033 for ; Fri, 16 Dec 2016 15:54:05 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (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 E892E879 for ; Fri, 16 Dec 2016 15:54:04 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id 14D6543C3B; Fri, 16 Dec 2016 09:52:49 -0600 (CST) From: John Marino Reply-To: marino@freebsd.org To: "ports@FreeBSD.org Ports" , Roger Marquis Subject: The ports collection has some serious issues Message-ID: <5c6df0ce-a473-d125-10a0-71b95a83512b@marino.st> Date: Fri, 16 Dec 2016 09:53:56 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161216-0, 12/16/2016), Outbound message X-Antivirus-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: Fri, 16 Dec 2016 15:54:05 -0000 Roger Marquis wrote >> It is every week. Consider the FreeBSD forums as well. >> "misuse" and "misunderstanding" failures are attributed to the tool. Let's >> stop making excuses for portmaster. It is what it is and we've had years to >> evaluate it. > > If portmaster was part of base I'd agree that it should be deprecated, > however, being a port it can be afforded more leeway. All portmaster > needs IMO is a strong WARNING message to be displayed on installation A) > enumerating some of the potential bugs and B) clarifying that portmaster > is third party software that is neither actively maintained nor > supported (or recommended?) by FreeBSD. It is just semantics. A "deprecated" message is just a warning. Maybe even a "strong" warning. By itself, it means nothing more than that. Since the beginning, portmaster was not going to be removed, it was just going to carry this warning to alert users. What you propose is what has always been proposed. I never understood why people went ape-**** over it, unless they don't understand what "deprecated without expiration" actually means. I just assumed that having such a warning was a scarlet letter and fans of portmaster didn't want the reputation defamed. If Torsten drops maintainership then some sort of "strong" warning should come with that drop. I would be satisfied with adding a descriptive DEPRECATED message myself. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-ports@freebsd.org Fri Dec 16 16:09:02 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E4BBC804AD for ; Fri, 16 Dec 2016 16:09:02 +0000 (UTC) (envelope-from marquis@roble.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 0F78DE6B for ; Fri, 16 Dec 2016 16:09:02 +0000 (UTC) (envelope-from marquis@roble.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0BF90C804AC; Fri, 16 Dec 2016 16:09: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 0BA09C804AB for ; Fri, 16 Dec 2016 16:09:02 +0000 (UTC) (envelope-from marquis@roble.com) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 01D07E6A; Fri, 16 Dec 2016 16:09:01 +0000 (UTC) (envelope-from marquis@roble.com) Date: Fri, 16 Dec 2016 08:09:01 -0800 (PST) From: Roger Marquis To: marino@freebsd.org cc: "ports@FreeBSD.org Ports" Subject: Re: The ports collection has some serious issues In-Reply-To: <5c6df0ce-a473-d125-10a0-71b95a83512b@marino.st> Message-ID: <1612160801490.3123@mx5.roble.com> References: <5c6df0ce-a473-d125-10a0-71b95a83512b@marino.st> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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, 16 Dec 2016 16:09:02 -0000 > It is just semantics. That may be but as illustrated in this thread people maintain unreasonable expectations of portmaster which they often blame on the ports subsystem. > I never understood why people went ape-**** over it, unless they don't > understand what "deprecated without expiration" actually means. Perhaps then this is the crux of the issue. From my experience "deprecated" means only that something will not appear in a future version of the OS. It implies nothing about the suitability of the software itself. "deprecated without expiration" is a contradiction. > If Torsten drops maintainership then some sort of "strong" warning should > come with that drop. I would be satisfied with adding a descriptive > DEPRECATED message myself. TZ or no TZ we should drop the deprecation notice until it has an expiration date and clarify the warning terms (ASAP). At least that way, when a thread like this comes up in the future, the only response needed would be a pointer to the install message. Roger From owner-freebsd-ports@freebsd.org Fri Dec 16 16:16:33 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 766C2C8076C for ; Fri, 16 Dec 2016 16:16:33 +0000 (UTC) (envelope-from freebsd.contact@marino.st) 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 61EF3136C for ; Fri, 16 Dec 2016 16:16:33 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: by mailman.ysv.freebsd.org (Postfix) id 614A4C8076B; Fri, 16 Dec 2016 16:16:33 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60F05C8076A for ; Fri, 16 Dec 2016 16:16:33 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (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 3E90A136B for ; Fri, 16 Dec 2016 16:16:32 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id EFE9243C38; Fri, 16 Dec 2016 10:15:23 -0600 (CST) Subject: Re: The ports collection has some serious issues To: Roger Marquis References: <5c6df0ce-a473-d125-10a0-71b95a83512b@marino.st> <1612160801490.3123@mx5.roble.com> Cc: "ports@FreeBSD.org Ports" From: John Marino Reply-To: marino@freebsd.org Message-ID: Date: Fri, 16 Dec 2016 10:16:31 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <1612160801490.3123@mx5.roble.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161216-0, 12/16/2016), Outbound message X-Antivirus-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: Fri, 16 Dec 2016 16:16:33 -0000 On 12/16/2016 10:09, Roger Marquis wrote: >> I never understood why people went ape-**** over it, unless they don't >> understand what "deprecated without expiration" actually means. > > Perhaps then this is the crux of the issue. From my experience > "deprecated" means only that something will not appear in a future > version of the OS. It implies nothing about the suitability of the > software itself. "deprecated without expiration" is a contradiction. From porters handbook, section 12.15: "It is possible to set DEPRECATED without an EXPIRATION_DATE (for instance, recommending a newer version of the port), but the converse does not make any sense." So it's not a contradiction. Ports that have a specific removal date must have EXPIRATION_DATE set. If you say, well DEPRECATION implies removal, I'd agree, but it's at an indefinite time and I'd say that time would come when portmaster no longer works on the current ports tree. When that happens (and it probably will happen) then EXPIRATION can be set. > >> If Torsten drops maintainership then some sort of "strong" warning >> should come with that drop. I would be satisfied with adding a >> descriptive DEPRECATED message myself. > > TZ or no TZ we should drop the deprecation notice until it has an > expiration date and clarify the warning terms (ASAP). At least that > way, when a thread like this comes up in the future, the only response > needed would be a pointer to the install message. Which notice should we drop? There's no DEPRECATION set now. There's no warning set. portmaster is not marked as "deprecated". And as the handbook points out: You can't have EXPIRATION without DEPRECATED, but it's perfectly legal to have the reverse. It's documented clearly. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-ports@freebsd.org Fri Dec 16 16:39:32 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1790C80B7A for ; Fri, 16 Dec 2016 16:39:32 +0000 (UTC) (envelope-from marquis@roble.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 A18C81D8E for ; Fri, 16 Dec 2016 16:39:32 +0000 (UTC) (envelope-from marquis@roble.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9E254C80B79; Fri, 16 Dec 2016 16:39:32 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C241C80B77 for ; Fri, 16 Dec 2016 16:39:32 +0000 (UTC) (envelope-from marquis@roble.com) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 865141D8D; Fri, 16 Dec 2016 16:39:32 +0000 (UTC) (envelope-from marquis@roble.com) Date: Fri, 16 Dec 2016 08:39:31 -0800 (PST) From: Roger Marquis To: marino@freebsd.org cc: "ports@FreeBSD.org Ports" Subject: Re: The ports collection has some serious issues In-Reply-To: Message-ID: <1612160831390.3123@mx5.roble.com> References: <5c6df0ce-a473-d125-10a0-71b95a83512b@marino.st> <1612160801490.3123@mx5.roble.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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, 16 Dec 2016 16:39:32 -0000 John Marino wrote: > From porters handbook, section 12.15: > "It is possible to set DEPRECATED without an EXPIRATION_DATE (for instance, > recommending a newer version of the port) I'd consider that to be a bug. > So it's not a contradiction. Ports that have a specific removal date must > have EXPIRATION_DATE set. If you say, well DEPRECATION implies removal, I'd > agree, but it's at an indefinite time and I'd say that time would come when > portmaster no longer works on the current ports tree. When that happens (and > it probably will happen) then EXPIRATION can be set. Non-standard uses of the term "deprecated" are problematic from a usability perspective. Since there is currently no deprecation messages (apologies for the misunderstanding, I haven't used portmaster) at least (TZ) add an install-time WARNING so we can avoid misleading potential portmaster users (and related mailing lists threads/topics). IMO, Roger From owner-freebsd-ports@freebsd.org Fri Dec 16 17:16:32 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E0C0C81874 for ; Fri, 16 Dec 2016 17:16:32 +0000 (UTC) (envelope-from fiscal16@tuempresaactualizada.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 4D89C1320 for ; Fri, 16 Dec 2016 17:16:32 +0000 (UTC) (envelope-from fiscal16@tuempresaactualizada.com) Received: by mailman.ysv.freebsd.org (Postfix) id 4A0B7C81873; Fri, 16 Dec 2016 17:16:32 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47E7BC81872 for ; Fri, 16 Dec 2016 17:16:32 +0000 (UTC) (envelope-from fiscal16@tuempresaactualizada.com) Received: from mail2.tuempresaactualizada.com (mail2.tuempresaactualizada.com [107.150.32.196]) by mx1.freebsd.org (Postfix) with ESMTP id 22F7C131F for ; Fri, 16 Dec 2016 17:16:31 +0000 (UTC) (envelope-from fiscal16@tuempresaactualizada.com) Received: from WIN-JL967LLBK95 (107.150.32.196) by mail2.tuempresaactualizada.com id hagglu0our0d for ; Fri, 16 Dec 2016 11:16:13 -0600 (envelope-from ) X-client: DFINE08132 Message-ID: From: "PERSONAS MORALES" To: Subject: CIERRE FISCAL 2016 Date: Fri, 16 Dec 2016 11:16:13 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 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, 16 Dec 2016 17:16:32 -0000 IA0KDQpFbiBsw61uZWEgeSBlbiBWaXZvIC8gUGFyYSB0b2RvIHN1IEVxdWlwbyBjb24gdW5hIHNv bGEgQ29uZXhpw7NuIA0KDQpDSUVSUkUgRklTQ0FMIDIwMTYgUEFSQSBQRVJTT05BUyBNT1JBTEVT DQoyMiBkZSBkaWNpZW1icmUgLSBPbmxpbmUgZW4gVml2byAtIDEwOjAwIGEgMTM6MDAgeSBkZSAx NTowMCBhIDE4OjAwIEhycyAgICAgICANCiANCk9iamV0aXZvOiBJZGVudGlmaWNhciBsYXMgcHJp bmNpcGFsZXMgZGlzcG9zaWNpb25lcyBkZSBsYSBMZXkgZGVsIElTUiwgcmVsYWNpb25hZGFzIGNv biBlbCBjaWVycmUgZmlzY2FsIGRlbCAyMDE2LCBwYXJhIGVsYWJvcmFyIGxhIGRlY2xhcmFjacOz biBhbnVhbCBkZWwgSVNSIGRlIHBlcnNvbmFzIG1vcmFsZXMgZGVsIFTDrXR1bG8gSUkgZGUgbGEg TElTUi4gDQrCv1BvciBxdcOpIGFzaXN0aXI/IENvbm9jZXLDoSBsYSBkZXRlcm1pbmFjacOzbiBk ZWwgYWp1c3RlIGFudWFsIHBvciBpbmZsYWNpw7NuLiAtIExhIHJlbnRhIGdyYXZhYmxlIHBhcmEg UFRVIHkgc3VzIGRpZmVyZW5jaWFzIGNvbiBsYSB1dGlsaWRhZCBmaXNjYWwgeSBjb24gZWwgcmVz dWx0YWRvIGZpc2NhbCBwYXJhIGVsIElTUi4gTG9zIGluZ3Jlc29zIGFjdW11bGFibGVzIHBhcmEg SVNSLiAtIExhcyBwcmluY2lwYWxlcyBkZWR1Y2Npb25lcyBlbiBJU1IsIHN1cyByZXF1aXNpdG9z LCBsYXMgbGltaXRhZGFzIHkgbGFzIHByb2hpYmlkYXMuICANCiJQcmVndW50ZSBwb3IgbnVlc3Ry YSBQcm9tb2Npw7NuIE5hdmlkZcOxYSIgDQoNCg0KVEVNQVJJTzoNCg0KMS4gSW5ncmVzb3MgYWN1 bXVsYWJsZXMgcGFyYSBJU1IuDQoNCjIuIFBhcGVsIGRlIHRyYWJham8gcGFyYSBkZXRlcm1pbmFy IGxvcyBpbmdyZXNvcyBjb250YWJsZXMsIGxvcyBkZWwgSVNSIHkgbG9zIGRlIGxhIFBUVS4gDQoN CjMuIFByaW5jaXBhbGVzIGRlZHVjY2lvbmVzIHkgc3VzIHJlcXVpc2l0b3MgcGFyYSBJU1IgeSBs YSBQVFUuIA0KDQo0LiBSZXZpc2nDs24gZGUgc3UgY29udGFiaWxpZGFkIGVsZWN0csOzbmljYSAo Y2lmcmFzIGRlIGNvbnRyb2wpLiANCg0KNS4gUmV2aXNpw7NuIGRlIHN1cyBubyBkZWR1Y2libGVz IGRlIGFjdWVyZG8gYWwgYXJ0IDI4IGZyYWNjacOzbiBYWFggZGUgbGEgTElTUi4NCg0KDQoNCi4u LsKhWSBtdWNobyBtw6FzIQ0KDQoNCiANCsK/UmVxdWllcmUgbGEgaW5mb3JtYWNpw7NuIGEgbGEg QnJldmVkYWQ/DQpyZXNwb25kYSBlc3RlIGVtYWlsIGNvbiBsYSBwYWxhYnJhOiANCkluZm8gLSBD aWVycmUuDQpjZW50cm8gdGVsZWbDs25pY286IDAxODAwMjEyOTM5Mw0KIA0KDQpMaWMuIEFydHVy byBMw7NwZXoNCkNvb3JkaW5hZG9yIGRlIEV2ZW50bw0KDQoNCiANCsK/RGVtYXNpYWRvcyBtZW5z YWplcyBlbiBzdSBjdWVudGE/IFJlc3BvbmRhIGVzdGUgbWVuc2FqZSBpbmRpY2FuZG8gcXVlIHNv bG8gZGVzZWEgcmVjaWJpciBDQUxFTkRBUklPIHkgc8OzbG8gcmVjaWJpcsOhIHVuIGNvcnJlbyBh bCBtZXMuIFNpIGRlc2VhIGNhbmNlbGFyIGxhIHN1c2NyaXBjacOzbiwgc29saWNpdGUgc3UgQkFK QS4uDQogDQoNCiANCg0KIA0KDQo= From owner-freebsd-ports@freebsd.org Fri Dec 16 18:16:28 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF7E6C8379E for ; Fri, 16 Dec 2016 18:16:28 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [185.24.122.233]) (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 88D50111B for ; Fri, 16 Dec 2016 18:16:27 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (ip-109-84-0-162.web.vodafone.de [109.84.0.162]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id uBGIGJUP098076 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 16 Dec 2016 18:16:20 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host ip-109-84-0-162.web.vodafone.de [109.84.0.162] claimed to be ultrabook.yoonka.com Subject: Re: what is the purpose of the quarterly ports branches? To: freebsd-ports@freebsd.org References: <7c73fc75-b4d9-063d-02f9-628e06f8d4bd@freebsd.org> <20161207025955.GA21488@Silverstone> <3a97d014-1b8b-7e34-6704-1ee5fd8b97ca@m5p.com> <0b018f88-4b64-67c8-a938-ae45fc19d08f@gjunka.com> <1481875278.2027307.820920449.18442D1C@webmail.messagingengine.com> <19940dc8-40de-81f8-7d79-73e6bfe2dc5a@freebsd.org> From: Grzegorz Junka Message-ID: <8b5a1d94-ab9d-7ffb-7ddb-e20fe92903ac@gjunka.com> Date: Fri, 16 Dec 2016 18:16:13 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <19940dc8-40de-81f8-7d79-73e6bfe2dc5a@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 18:16:29 -0000 On 16/12/2016 10:10, Julian Elischer wrote: > On 16/12/2016 4:01 PM, Dave Cottlehuber wrote: >> >> On Tue, 13 Dec 2016, at 23:14, Grzegorz Junka wrote: >>> I heard that ports' SVN is mirrored to Github. Isn't it enough to just >>> create a branch or tag for each quarterly release? Even if quarterly >>> packages are deleted, re-building packages from such branch/tag should >>> allow to recreate those packages as required since the same code would >>> give the same packages? >> These branches already exist BTW: >> >> https://github.com/freebsd/freebsd-ports/tree/branches/2016Q3 > > the trouble is that the packages are deleted as soon as they are stable. But it shouldn't be that much work to rebuild them? Setting up poudriere took one afternoon. Greg From owner-freebsd-ports@freebsd.org Fri Dec 16 18:23:36 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 475FEC8395C for ; Fri, 16 Dec 2016 18:23:36 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) 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 314BD159A for ; Fri, 16 Dec 2016 18:23:36 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: by mailman.ysv.freebsd.org (Postfix) id 309D7C8395B; Fri, 16 Dec 2016 18:23:36 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2EA2CC8395A for ; Fri, 16 Dec 2016 18:23:36 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from mail.mimar.rs (mail1.mimar.rs [193.53.106.128]) (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 DF1A31599 for ; Fri, 16 Dec 2016 18:23:34 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from mail1.mimar.rs (localhost [127.0.1.128]) by mail.mimar.rs (Postfix) with ESMTP id 143BF9FA8967 for ; Fri, 16 Dec 2016 19:23:26 +0100 (CET) X-Virus-Scanned: amavisd-new at mimar.rs Received: from mail.mimar.rs ([127.0.1.128]) by mail1.mimar.rs (amavis.mimar.rs [127.0.1.128]) (amavisd-new, port 10026) with LMTP id RHH76YoS73bE for ; Fri, 16 Dec 2016 19:23:20 +0100 (CET) Received: from efreet.kappastar.com (178-221-61-94.dynamic.isp.telekom.rs [178.221.61.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: marko.cupac@mimar.rs) by mail.mimar.rs (Postfix) with ESMTPSA id 363149FA891B for ; Fri, 16 Dec 2016 19:23:20 +0100 (CET) Date: Fri, 16 Dec 2016 19:23:24 +0100 From: Marko =?UTF-8?B?Q3VwYcSH?= To: Subject: thanx for thunar crash on rename bug fix! Message-ID: <20161216192324.42fc43cc@efreet.kappastar.com> Organization: Mimar X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 18:23:36 -0000 Hi, I just wanted do say thank you to whoever fixed Thunar, or something lower below, so that Thunar does not crash anymore when renaming files. --=20 Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupa=C4=87 https://www.mimar.rs/ From owner-freebsd-ports@freebsd.org Fri Dec 16 18:24:18 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67C25C8399C for ; Fri, 16 Dec 2016 18:24:18 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [185.24.122.233]) (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 149F31649 for ; Fri, 16 Dec 2016 18:24:17 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from ultrabook.yoonka.com (ip-109-84-0-162.web.vodafone.de [109.84.0.162]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id uBGIOFE1098220 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 16 Dec 2016 18:24:16 GMT (envelope-from list1@gjunka.com) X-Authentication-Warning: msa1.earth.yoonka.com: Host ip-109-84-0-162.web.vodafone.de [109.84.0.162] claimed to be ultrabook.yoonka.com Subject: Re: The ports collection has some serious issues To: freebsd-ports@freebsd.org References: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> From: Grzegorz Junka Message-ID: <1d6472b9-f3d1-57c1-31b8-0066a8f967d0@gjunka.com> Date: Fri, 16 Dec 2016 18:24:09 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> Content-Type: text/plain; charset=windows-1252; 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: Fri, 16 Dec 2016 18:24:18 -0000 On 16/12/2016 14:45, John Marino wrote: >> > DragonFly has switched to Synth from poudriere as it's primary package > builder. That means it builds entire repositories (25,000 packages) > biweekly on multiple servers. It's highly used which serves as > continuous testing. I also use it on FreeBSD to test updates to > ports. In fact, anyone that updates ports should use either poudriere > testport or synth test. (Based on evidence, it's clear that some > people whom I won't name publicly never use the QA checks before > committing significant changes but that's getting sidetracked). > > The point is that these tools are in great shape and to imply > otherwise needs proof. It's portmaster that's not receiving updates. I think adding synth as the default builder in the FreeBSD Handbook and deprecating portmaster and portupgrade in the documentation would go a long way towards letting newcomers use the ports in the proper way (since they are not maintained anyway). They wouldn't need to be removed from ports for those hardcore users who are already used to using them. The current presence of those tools in the official Handbook makes them somehow the official way of upgrading ports in FreeBSD, even if it's the worst way of upgrading ports possible. Grzegorz From owner-freebsd-ports@freebsd.org Fri Dec 16 18:46:23 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC5DDC83EF2 for ; Fri, 16 Dec 2016 18:46:23 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) Received: from taro.utanet.at (taro.utanet.at [IPv6:2001:938:1337:25::25:45]) (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 6DDB832D for ; Fri, 16 Dec 2016 18:46:23 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=utanet.at; s=rev1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Subject:References:To; bh=xMb9EoEDawH412WXIjRzPdcH9dxiKynr1AJTax8y0jo=; b=BH4CZ8Nxt/7FqktpoFimY87VEJd0izNnxiQbYU4/bR8cPpYrEEby/iwWbeDcHW0cXoANS/tObZ2LsjA4q5eiYVwdZz39cWUZ+vVGE643QZmLzrLKLnMFtEwvqwZH48r7m3OfihAfjXfo4h2A2uZZqNiJbGsuYiA8ns6+TimeZzk=; Received: from pam.xoc.tele2net.at ([213.90.36.6]) by taro.utanet.at with esmtp (Exim 4.80) (envelope-from ) id 1cHxWP-0000CP-Fd for freebsd-ports@freebsd.org; Fri, 16 Dec 2016 19:46:21 +0100 Received: from 193-83-12-236.adsl.highway.telekom.at ([193.83.12.236] helo=[10.0.0.93]) by pam.xoc.tele2net.at with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1cHxWP-0003Be-Dd for freebsd-ports@freebsd.org; Fri, 16 Dec 2016 19:46:21 +0100 To: freebsd-ports@freebsd.org References: <8ca57c66-a042-fc45-7366-1d37059db652@utanet.at> Subject: Re: Annoying problem lzma - lzmalib From: Walter Schwarzenfeld Message-ID: Date: Fri, 16 Dec 2016 19:46:18 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <8ca57c66-a042-fc45-7366-1d37059db652@utanet.at> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-TELE2-Authenticated-As: cf62768e218b4d81d95cc5390f1bd9dfc8b05683 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 18:46:23 -0000 Bext oribken with liblzma: math/R checking for lzma_version_number in -llzma... no configure: error: "liblzma library and headers are required" ===> Script "configure" failed unexpectedly. Please report the problem to jrm@FreeBSD.org [maintainer] and attach the "/ram/usr/ports/math/R/work/R-3.3.2/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 From owner-freebsd-ports@freebsd.org Fri Dec 16 18:48:59 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3ED6AC83FE4 for ; Fri, 16 Dec 2016 18:48:59 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) Received: from taro.utanet.at (taro.utanet.at [IPv6:2001:938:1337:25::25:45]) (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 00DD16A1 for ; Fri, 16 Dec 2016 18:48:58 +0000 (UTC) (envelope-from w.schwarzenfeld@utanet.at) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=utanet.at; s=rev1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Subject:References:To; bh=ewivrJHBtKUPM3S/R5DJrRuBTXbHmSz9KwQG5rS8L90=; b=Lq4T3bHLMvDpmlJnv3Xc2agSQGZcjJIIvSOBej5BQnDdqgyU4LHeOWN7z52+hafxBH76FHQbIa2Rhq2Wa7UaN9voGz2WkyceIR81UalwnNA5Nn00jpS0/OhgzYoheAMapIvD6/w0iN0h3f0QZ+BTjrLIVLRiWh3xxHk1HqLYA2g=; Received: from paris.xoc.tele2net.at ([213.90.36.7]) by taro.utanet.at with esmtp (Exim 4.80) (envelope-from ) id 1cHxYv-0000Wk-1o for freebsd-ports@freebsd.org; Fri, 16 Dec 2016 19:48:57 +0100 Received: from 193-83-12-236.adsl.highway.telekom.at ([193.83.12.236] helo=[10.0.0.93]) by paris.xoc.tele2net.at with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1cHxYu-0004UX-WE for freebsd-ports@freebsd.org; Fri, 16 Dec 2016 19:48:57 +0100 To: freebsd-ports@freebsd.org References: Subject: Re: Annoying problem lzma - lzmalib From: Walter Schwarzenfeld Message-ID: Date: Fri, 16 Dec 2016 19:48:56 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-TELE2-Authenticated-As: cf62768e218b4d81d95cc5390f1bd9dfc8b05683 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 18:48:59 -0000 correct Next problem with liblzma. (Sorry). From owner-freebsd-ports@freebsd.org Fri Dec 16 19:49:53 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0813C83339 for ; Fri, 16 Dec 2016 19:49:53 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (mail.covisp.net [65.121.55.42]) (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 C0B1A10F8 for ; Fri, 16 Dec 2016 19:49:53 +0000 (UTC) (envelope-from kremels@kreme.com) Received: by mail.covisp.net (Postfix, from userid 125) id 3tgLVy60vszvBCS; Fri, 16 Dec 2016 13:36:50 -0700 (MST) From: "@lbutlr" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Gettext Issues Message-Id: <5E460EDF-E9BA-4076-821D-52225EB28224@kreme.com> Date: Fri, 16 Dec 2016 00:22:02 -0700 To: freebsd-ports@freebsd.org X-Mailer: Apple Mail (2.3259) 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, 16 Dec 2016 19:49:53 -0000 > 2014-11-30 > Affects: users of devel/gettext (close to everyone) > Author: tijl@FreeBSD.org > Reason:=20 > The devel/gettext port has been split up in devel/gettext-runtime, a > lightweight package containing runtime libraries, and = devel/gettext-tools, > a package containing developer tools. The devel/gettext port still = exists > as a metaport. >=20 > You must first delete the existing installation of gettext and then > reinstall it. This will break sudo, so you *must* do this in a root > shell (sudo -i) if you use sudo. I cannot imagine that gettext hasn't been updated on my system in over 2 = years, but I seem to be having an issue that appears to be related to = this based on the errors. Shared object "libintl.so.8" not found, required by "bash" For example. I have logged into the console directly as the root user and tried to = build gettext via portmaster of via make clean && make install but I get = errors about missing files. pkg-static: Unable to access file = /usr/ports/devel/gettext-runtime/work/stage/usr/local/include/autosprintf.= h: No such file or directory I've tried to build gettext-runtime first, but to no avail. From owner-freebsd-ports@freebsd.org Fri Dec 16 20:19:27 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13DD1C83D17 for ; Fri, 16 Dec 2016 20:19:27 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 67D58B5E for ; Fri, 16 Dec 2016 20:19:25 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mandree.no-ip.org ([78.49.44.178]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MUYiV-1c9ycA3Ax9-00RLdU for ; Fri, 16 Dec 2016 21:19:18 +0100 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 621C523CF5A for ; Fri, 16 Dec 2016 21:19:16 +0100 (CET) From: Matthias Andree Subject: CFT: OpenVPN 2.4 port update (upstream rc2) for FreeBSD To: freebsd-ports Message-ID: Date: Fri, 16 Dec 2016 21:19:06 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="bJUwUSSw7a2fOhH1J2j0vdeUFbU0hBdHl" X-Provags-ID: V03:K0:+u+ArxCiFPcwuy86Ycj6L20Wcv1x+sWksFNSPQ2B/cwljUbyg6T VIu0LNkB7AJ/i1o9BCJbUXp05gq8udiGsk566wA7mULzNbQxh4a+8hEmZEwyfF3k+Ta6Yon R+2IcQlIYtYRPncSDeTUvVkqSRD92XHQXnyJbfJtWO9byh7/mS6rYs3zL58ykqL2bvS2b73 FB7pvvbK0ewMPZ7di8//w== X-UI-Out-Filterresults: notjunk:1;V01:K0:twKA4j+ZHJs=:hw628eyy64GPNs8CfNWPRh qtPJDZEbVtkscvCawiehPEOpvbT7/4DTqXI3lhKI+BgffjJzLnRU2wU5nLAB4neE+x6hyKQhI XYKRLFRz5Zg9E2PngKO0/osSmp0KxqRfVdouW/F2HyYK8uNNqoUas985P7EiBhDyUiBkzRv3X CFHcNqqhHN8076f2TQp+GoOyPTU8NowSFNTHS2/BEDbZWzgubWXnBdEbHdVNUkj8F36qThNwM DgIk5tC+dVGjj0NXaZmceN2lMr/lDAKV6YqUzJZNBqL5sTLni919hJelq/MDjvWXej7AfsxHl 5D39DriLjw8pUDn1ERI8hqYbP9uBSJpQJRfYh9qQLu8GKOTgRW2aM7tZzdfg889lHE3lZipri CUoKPd2H6XCIJwvp4oo04j/6m5vvGxKuZFN+vECK6dTKFipdXMi43ONX2J/EYupcNgi1pcLGX jxUOiPncs7CsVNXUE8Ffg8n7oCCPRbuHHvogr0j5Glxv7aHxLCCX4lG1ODk7++uW+4TF6Kkx6 u3Lq6mE3WVLggQQ0RGtMTFlEE4Fr/z2MO02kgIBP5wS51guW4fwTx515myORknGbolSSPSvLe ufGelBBCLYXdSRCozINUaSxJCYhtKfm2Ny9OP2J2Fb6qH2STNBNfcWW0un70nzQ/8Xd4daLgz 6XHSymIRRfCatW67E4vxhZeM9hdjxRTN8PHuDFm+vkKyVBFvfj42+6GfQ6OO2Zt3Nl7E3bf8O 7P39QcCaQmVd+k3rWzLh1OUNfZsd90TxSbzaQedcMiFFp849Tg3XZlIT/h0= 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, 16 Dec 2016 20:19:27 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --bJUwUSSw7a2fOhH1J2j0vdeUFbU0hBdHl Content-Type: multipart/mixed; boundary="J50SGQ4RwceMcB6p9mGfC5gNJkIKUiIrf"; protected-headers="v1" From: Matthias Andree To: freebsd-ports Message-ID: Subject: CFT: OpenVPN 2.4 port update (upstream rc2) for FreeBSD --J50SGQ4RwceMcB6p9mGfC5gNJkIKUiIrf Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Greetings, I've put up a new OpenVPN 2.4-rc2 port for FreeBSD for testing. Get it from . This time, it also contains the openvpn23 and openvpn23-polarssl ports (as modified copies of what we have now) that I plan to keep for the first quarter of 2017 and then retire, just in case. The diff at https://reviews.freebsd.org/D8813 has been updated, too. Cheers, Matthias --J50SGQ4RwceMcB6p9mGfC5gNJkIKUiIrf-- --bJUwUSSw7a2fOhH1J2j0vdeUFbU0hBdHl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJYVEw6AAoJEOQSsVbv84VaNfEP/3Z2YwxumGjRGN4Zp/AP8Pnu LbJhZaRH8LHHS96yU2UUKO5mQpb2LDBlmrcNPaTu0kpNpW4sBxFv5KvfnCCtGPwM UnxoD3rGjuoe/9Ibbgjg5lM8UTeohiHwXpG8ViZBDcuXhxPDe/l6agKWzhOU0anV PnSVujsq9myj84hguPeSj2vhfLoSJmlq5sPAnn/FHMI/kF/k7pEOFXp9DzOTCPU5 FpQFxWdMRmILGykSj8afTwakPIOSsMEv7AQ6VNPP6N37djkst352IBQ6LKyTpAkY YtGZE/ipOkxQSSq659YR3zFGzVfAfjU9KxvCrGEZK9LwjrhSN2Mc27d2rpAcPJsy UubL/aMmQ5LBSSDthTA1mSaPyBt+teTmn2Bl/FvgOoPgCn4S0ZEtgCIVPmZ+xlty SagwI8KYDAM/8AqxPV7DpdxosX3XGdcgwbpDWXTFxZdza621t0SZ16OxnJ8X7Ozz /yQUZEZXbXjxBE/A32aWkOBcZv5P5HlmQADg+DYj8L0Ta82EoXkWVn3q0gHHdvjO YuYyXzRL0BzppNtulivf6OpLLFpVgK1dDQ/n5bPhMs0bOcoeagfCxU0UD3tJeqoY 4V5L+dC7+Bu8dXGm1XQjAbeT9BjMVTSD7khhVb3ebDllSqXJbaP2DLM5/HBo7U/a CvxAGOgHt1Ya1L8obKGT =PFcy -----END PGP SIGNATURE----- --bJUwUSSw7a2fOhH1J2j0vdeUFbU0hBdHl-- From owner-freebsd-ports@freebsd.org Fri Dec 16 22:55:04 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EB23C838AD for ; Fri, 16 Dec 2016 22:55:04 +0000 (UTC) (envelope-from michael.brodeur@unseen.is) 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 4E189955 for ; Fri, 16 Dec 2016 22:55:04 +0000 (UTC) (envelope-from michael.brodeur@unseen.is) Received: by mailman.ysv.freebsd.org (Postfix) id 46E5FC838AC; Fri, 16 Dec 2016 22:55:04 +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 46802C838AB for ; Fri, 16 Dec 2016 22:55:04 +0000 (UTC) (envelope-from michael.brodeur@unseen.is) Received: from mt02.unseen.is (mt02.unseen.is [82.221.109.2]) (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 ED725954 for ; Fri, 16 Dec 2016 22:55:03 +0000 (UTC) (envelope-from michael.brodeur@unseen.is) Received: from localhost (localhost.localdomain [127.0.0.1]) by mt02.unseen.is (Postfix) with ESMTP id 5C31F5229D7 for ; Fri, 16 Dec 2016 22:45:44 +0000 (GMT) X-Spam-Flag: NO X-Spam-Score: -2.01 X-Spam-Level: X-Spam-Status: No, score=-2.01 tagged_above=-10 required=6.6 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: mt02.unseen.is (amavisd-new); dkim=pass (1024-bit key) header.d=unseen.is Received: from mt02.unseen.is ([127.0.0.1]) by localhost (mt02.unseen.is [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id DwWvMiJHVusm for ; Fri, 16 Dec 2016 22:45:43 +0000 (GMT) Received: from localhost (localhost.localdomain [127.0.0.1]) by mt02.unseen.is (Postfix) with ESMTP id 660785229D8 for ; Fri, 16 Dec 2016 22:45:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.9.2 mt02.unseen.is 660785229D8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unseen.is; s=45C3F388-BD2F-11E6-A1E8-E0951B849DDC; t=1481928343; bh=BZkiAgTVkkUVGMXINKn5ngTgf2EZGYSHx8x1xPoCmnQ=; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type: Content-Transfer-Encoding; b=ArceultQ8OHmk1yNZdXT5iIDCeGjGem1HwxQNSnd4EZjvV0vxOQBbJvgsKlnUiAg1 ZxIQmC3bCy2jIlNx+tPraCOd6oyap1P9cXWljxaQtwOF1rzhyEGkoFRBXAxJ8qAGY8 7OAVvT69olS1DFsT7n0sCR9RyNOGPIkuCtX+APaw= X-Virus-Scanned: amavisd-new at Received: from mt02.unseen.is ([127.0.0.1]) by localhost (mt02.unseen.is [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Ww3n_7-Q3HlW for ; Fri, 16 Dec 2016 22:45:43 +0000 (GMT) Received: from mb02.unseen.is (mb02.unseen.is [82.221.109.20]) by mt02.unseen.is (Postfix) with ESMTP id 445D85229D7 for ; Fri, 16 Dec 2016 22:45:43 +0000 (GMT) Date: Fri, 16 Dec 2016 22:45:43 +0000 (GMT) From: michael.brodeur@unseen.is To: ports@freebsd.org Message-ID: <665434249.1209117.1481928343106.JavaMail.zimbra@unseen.is> Subject: Irrlicht-1.8.4 sparc64 compatability? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [82.221.107.114] X-Mailer: Zimbra 8.6.0_GA_1153 (zclient/8.6.0_GA_1153) Thread-Topic: Irrlicht-1.8.4 sparc64 compatability? Thread-Index: DYxdvDWLpnohyWGwWo2kZPrXgalPfg== 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, 16 Dec 2016 22:55:04 -0000 I was browsing through the commit history of this package and noticed that it has problems compiling for sparc64? I wanted to find out if there was a particular reason for that? Please let me know! Best, Michael Brodeur From owner-freebsd-ports@freebsd.org Sat Dec 17 00:17:55 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9BBF9C8368D for ; Sat, 17 Dec 2016 00:17:55 +0000 (UTC) (envelope-from kremels@kreme.com) Received: from mail.covisp.net (mail.covisp.net [65.121.55.42]) (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 8BC9A1D9F for ; Sat, 17 Dec 2016 00:17:55 +0000 (UTC) (envelope-from kremels@kreme.com) From: "@lbutlr" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Re: Gettext Issues Date: Fri, 16 Dec 2016 17:17:52 -0700 References: <5E460EDF-E9BA-4076-821D-52225EB28224@kreme.com> To: freebsd-ports@freebsd.org In-Reply-To: <5E460EDF-E9BA-4076-821D-52225EB28224@kreme.com> Message-Id: X-Mailer: Apple Mail (2.3259) 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, 17 Dec 2016 00:17:55 -0000 > On 16 Dec 2016, at 00:22, @lbutlr wrote: >=20 >=20 >> 2014-11-30 >> Affects: users of devel/gettext (close to everyone) >> Author: tijl@FreeBSD.org >> Reason:=20 >> The devel/gettext port has been split up in devel/gettext-runtime, a >> lightweight package containing runtime libraries, and = devel/gettext-tools, >> a package containing developer tools. The devel/gettext port still = exists >> as a metaport. >>=20 >> You must first delete the existing installation of gettext and then >> reinstall it. This will break sudo, so you *must* do this in a root >> shell (sudo -i) if you use sudo. >=20 > I cannot imagine that gettext hasn't been updated on my system in over = 2 years, but I seem to be having an issue that appears to be related to = this based on the errors. >=20 > Shared object "libintl.so.8" not found, required by "bash" >=20 > For example. >=20 > I have logged into the console directly as the root user and tried to = build gettext via portmaster of via make clean && make install but I get = errors about missing files. >=20 > pkg-static: Unable to access file = /usr/ports/devel/gettext-runtime/work/stage/usr/local/include/autosprintf.= h: No such file or directory >=20 >=20 > I've tried to build gettext-runtime first, but to no avail. To clarify, if I try to make gettext-runtime it ends with: install -m 0644 ABOUT-NLS = '/usr/ports/devel/gettext-runtime/work/stage/usr/local/share/gettext' =3D=3D=3D=3D> Compressing man pages (compress-man) ls: = /usr/ports/devel/gettext-runtime/work/stage/usr/local/info/autosprintf.inf= o*: No such file or directory And the error is correct, the file does not exist. From owner-freebsd-ports@freebsd.org Sat Dec 17 07:49:57 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 98471C84960 for ; Sat, 17 Dec 2016 07:49:57 +0000 (UTC) (envelope-from hrant@dadivanyan.net) Received: from pandora.amnic.net (pandora.amnic.net [IPv6:2001:67c:21c:a610::11]) (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 516AF672; Sat, 17 Dec 2016 07:49:57 +0000 (UTC) (envelope-from hrant@dadivanyan.net) Received: from ran by pandora.amnic.net with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cI9ke-000ANC-DY; Sat, 17 Dec 2016 11:49:52 +0400 Subject: Re: The ports collection has some serious issues In-Reply-To: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> To: John Marino Date: Sat, 17 Dec 2016 11:49:52 +0400 (AMT) From: Hrant Dadivanyan CC: FreeBSD Mailing List , tingox@gmail.com X-PGP: https://amnic.net/pgpkeys/hrant.asc X-NCC-RegID: am.isoc X-Mailer: ELM [version 2.4ME+ PL127 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="UTF-8" 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: Sat, 17 Dec 2016 07:49:57 -0000 > > > > On Fri, Dec 16, 2016 at 6:42 AM, Peter Jeremy wrote: > >> On 2016-Dec-15 19:31:22 +0100, list-freebsd-ports at jyborn.se wrote: > >> Interestingly, the most vocal proponent of deleting portmaster and > >> portupgrade is the author/maintainer of synch. > > It's not interesting at all. Synth was in a large part created because > people were irrationally sticking with portmaster and more frighteningly > gaining new users. > Please don't judge what's rational and what's not, because it's community and when many people, even irrationally from your POV, sticking with portmaster, then it's worth to consider and look for a way to keep it up. > The point is that these tools are in great shape and to imply otherwise > needs proof. It's portmaster that's not receiving updates. > In current shape it works well for many people (and demanded by) in community, so why should it be removed ? You can warn as much as you want against, but you can't decide to remove. Hrant > John > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > _______________________________________________ > 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" -- Hrant Dadivanyan (aka Ran d'Adi) hrant(at)dadivanyan.net /* "Feci quod potui, faciant meliora potentes." */ ran(at)psg.com From owner-freebsd-ports@freebsd.org Sat Dec 17 08:51:48 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF270C824BF for ; Sat, 17 Dec 2016 08:51:48 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.232]) (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 BDEE11F2 for ; Sat, 17 Dec 2016 08:51:48 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [74.134.208.22] ([74.134.208.22:48488] helo=localhost) by dnvrco-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id EA/CB-31287-C9CF4585; Sat, 17 Dec 2016 08:51:41 +0000 Date: Sat, 17 Dec 2016 08:51:36 +0000 Message-ID: From: "Thomas Mueller" To: freebsd-ports@freebsd.org Subject: Re: The ports collection has some serious issues References: X-RR-Connecting-IP: 107.14.64.6:25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2016 08:51:49 -0000 >From John Marino: > At face value, this doesn't make sense because synth is a tool for building > everything from source, so your development system is exactly where it should > be installed. > So you must be talking about build dependencies of synth (there are no run > dependencies). While I think the requirement of rebuilding synth from source > is artificial, I've provided a very reasonable approach to solving this which > I feel compelled to repeat for the readers of Kevin's post. The solution: > Starting with a clean system: > 1) install synth from binary package from official freebsd builder (a single > package) > 2) Configure synth if necessary > 3) command synth to build itself > 4) pkg delete synth (system is once again clean) > 5) pkg add -F /path/to/synth/packages/synth-* > Now you have a system containing s/w built by itself. On an modest system > less than 4 years old, it might take 30 minutes at most. > So the "synth has dependencies" detraction is extremely weak. For people that > trust FreeBSD to provide untainted binaries, it's not an issue at all and for > the paranoid, it's easily worked around. Saying that the use of Ada limits it > to the platforms it can run on natively is a valid detraction, but it's BUILD > dependencies really aren't due to the availability of binary packages, the > PRIMARY product of the ports tree. > RE: poudriere, it has no dependencies. It's just as appropriate on the dev > system and adding a jail and configuring it also takes less than 30 minutes. > Either is very appropriate for a system that must build everything that is run > on it. I believe you could cd $PORTSDIR/ports-mgmt/synth and make package-recursive |& tee build-12amd64.log (or whatever you want to name the log file; this example if for shell tcsh)? For a system with pkgng, is there any difference in package format between "make install", portmaster and portupgrade? If your system already has portmaster, you could portmaster ports-mgmt/synth |& tee synth-12amd64.log? And then switch from portmaster to synth for all further ports builds/updates? It would not be necessary to start with a clean system for FreeBSD, as opposed to NetBSD, or am I mistaken here? First port-upgrading tool I used in FreeBSD was portupgrade. Subsequently I switched to portmaster. Tom From owner-freebsd-ports@freebsd.org Sat Dec 17 09:49:25 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49FE9C81A69 for ; Sat, 17 Dec 2016 09:49:25 +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 372071D0 for ; Sat, 17 Dec 2016 09:49:25 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 368FDC81A68; Sat, 17 Dec 2016 09:49:25 +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 363E1C81A67 for ; Sat, 17 Dec 2016 09:49:25 +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 298AF1CE for ; Sat, 17 Dec 2016 09:49:25 +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 uBH9nKSG025887 for ; Sat, 17 Dec 2016 09:49:24 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.ysv.freebsd.org (8.15.2/8.15.2/Submit) id uBH9HwAD032925; Sat, 17 Dec 2016 09:17:58 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201612170917.uBH9HwAD032925@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, 17 Dec 2016 09:17:58 +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, 17 Dec 2016 09:49:25 -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 ------------------------------------------------+-----------------+------------ net-mgmt/mk-livestatus | 1.2.8p13 | 1.2.8p15 ------------------------------------------------+-----------------+------------ 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 Dec 17 10:25:23 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0027FC8387C for ; Sat, 17 Dec 2016 10:25:22 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CA63B17CE for ; Sat, 17 Dec 2016 10:25:22 +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 1F0242057A for ; Sat, 17 Dec 2016 05:25:21 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute7.internal (MEProxy); Sat, 17 Dec 2016 05:25:21 -0500 DKIM-Signature: v=1; a=rsa-sha1; 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=ZZdOTRH7QTZBiqLialaLKss1Kw Q=; b=nGT5wh2EtgRhvh5UVRdJ1fcA+Q9WWYEaIqGMaJaDHWnew5zZzkt55SLc2/ /0GrqxGPakI0St8yiUJXcFxy8ZOL4pYMKm1pauvCgYsNFmRz/8X+JC+8T8L1TVqj aNX0C+CE0qGRC9oIrXRrYauyWOOgurm7ams0xbWuXoAZiJzCg= DKIM-Signature: v=1; a=rsa-sha1; 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=smtpout; bh=ZZ dOTRH7QTZBiqLialaLKss1KwQ=; b=WHa+WNsMWh2BHjU+QfINkijlv76HjV3cDE KSl7IkGRvpXr9me3GEr9vcmiZvRNZChTOXorK2NDeJnKlvwdChi9s9OcJWxmcatQ W1EVoQQmWlUXDTsdzMDcFnRSoBaLULZp9a+Amk7f6tIgWE27qU17zwXMiDCogDCn LTRW7SCqc= X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id EA55848001; Sat, 17 Dec 2016 05:25:20 -0500 (EST) Message-Id: <1481970320.3226425.821927745.488CB138@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-bb5bdba7 Subject: Re: The ports collection has some serious issues In-Reply-To: <1612160725340.3123@mx5.roble.com> Date: Sat, 17 Dec 2016 11:25:20 +0100 References: <3959e18e-5819-b2c5-69a9-c71ce1282383@marino.st> <3cf805df-eb25-187c-8bf9-b6c2be5e977d@marino.st> <1612160725340.3123@mx5.roble.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: Sat, 17 Dec 2016 10:25:23 -0000 On Fri, 16 Dec 2016, at 16:34, Roger Marquis wrote: > If portmaster was part of base I'd agree that it should be deprecated, > however, being a port it can be afforded more leeway. All portmaster > needs IMO is a strong WARNING message to be displayed on installation A) > enumerating some of the potential bugs and B) clarifying that portmaster > is third party software that is neither actively maintained nor > supported (or recommended?) by FreeBSD. > > Roger ^ this ^ The key thing that needs to change for newcomers (as a recent one myself) is to give a clear & simple recommendation in the Handbook.. not in ports or whatever after you've sifted the internet looking for more information - the implications of choosing pkg quarterly vs pkg latest, vs poudriere, portmaster etc is not at all clear - it's hard to know what is project supported vs community supported - knowing that e.g. DFLY uses synth exclusively now, and the the FreeBSD build cluster uses poudriere, gives a warm fuzzy feeling Some illustrative use cases are: - sysadmin for servers - personal user who needs custom options I was lucky to run into the first poudriere episode from bsdnow.tv and went with that from the get-go. synth's documentation is superb and keeps getting better. Both are excellent tools. A+ Dave From owner-freebsd-ports@freebsd.org Sat Dec 17 11:36:49 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 034F9C84A82 for ; Sat, 17 Dec 2016 11:36:49 +0000 (UTC) (envelope-from tijl@coosemans.org) Received: from mailrelay119.isp.belgacom.be (mailrelay119.isp.belgacom.be [195.238.20.146]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "relay.skynet.be", Issuer "GlobalSign Organization Validation CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 741A51C6A for ; Sat, 17 Dec 2016 11:36:48 +0000 (UTC) (envelope-from tijl@coosemans.org) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2CuAgBOIlVY//s+sVtcHQEFAQsBgzcBA?= =?us-ascii?q?QEBAR+BYI1Pc5VlJgGCcJF3ggqGIgKCF0AUAQIBAQEBAQEBYiiEaQEFOhweBRA?= =?us-ascii?q?LGAklDyoeBhOIb6xcixkBAQEBAQEEAQEBASSLD4QSEQGFfQWacJEndI9mjhmED?= =?us-ascii?q?x83Y0KGAj00hkmCLgEBAQ?= X-IPAS-Result: =?us-ascii?q?A2CuAgBOIlVY//s+sVtcHQEFAQsBgzcBAQEBAR+BYI1Pc5V?= =?us-ascii?q?lJgGCcJF3ggqGIgKCF0AUAQIBAQEBAQEBYiiEaQEFOhweBRALGAklDyoeBhOIb?= =?us-ascii?q?6xcixkBAQEBAQEEAQEBASSLD4QSEQGFfQWacJEndI9mjhmEDx83Y0KGAj00hkm?= =?us-ascii?q?CLgEBAQ?= Received: from 251.62-177-91.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([91.177.62.251]) by relay.skynet.be with ESMTP; 17 Dec 2016 12:36:39 +0100 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.15.2/8.15.2) with ESMTP id uBHBaboo034738; Sat, 17 Dec 2016 12:36:38 +0100 (CET) (envelope-from tijl@coosemans.org) Date: Sat, 17 Dec 2016 12:36:36 +0100 From: Tijl Coosemans To: "@lbutlr" Cc: freebsd-ports@freebsd.org Subject: Re: Gettext Issues Message-ID: <20161217123636.7c15d081@kalimero.tijl.coosemans.org> In-Reply-To: References: <5E460EDF-E9BA-4076-821D-52225EB28224@kreme.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2016 11:36:49 -0000 On Fri, 16 Dec 2016 17:17:52 -0700 "@lbutlr" wrote: >> On 16 Dec 2016, at 00:22, @lbutlr wrote: >>> 2014-11-30 >>> Affects: users of devel/gettext (close to everyone) >>> Author: tijl@FreeBSD.org >>> Reason: >>> The devel/gettext port has been split up in devel/gettext-runtime, a >>> lightweight package containing runtime libraries, and devel/gettext-tools, >>> a package containing developer tools. The devel/gettext port still exists >>> as a metaport. >>> >>> You must first delete the existing installation of gettext and then >>> reinstall it. This will break sudo, so you *must* do this in a root >>> shell (sudo -i) if you use sudo. >> >> I cannot imagine that gettext hasn't been updated on my system in over >> 2 years, but I seem to be having an issue that appears to be related >> to this based on the errors. >> >> Shared object "libintl.so.8" not found, required by "bash" >> >> For example. >> >> I have logged into the console directly as the root user and tried to >> build gettext via portmaster of via make clean && make install but I >> get errors about missing files. >> >> pkg-static: Unable to access file >> /usr/ports/devel/gettext-runtime/work/stage/usr/local/include/autosprintf.h: >> No such file or directory >> >> >> I've tried to build gettext-runtime first, but to no avail. > > To clarify, if I try to make gettext-runtime it ends with: > > install -m 0644 ABOUT-NLS '/usr/ports/devel/gettext-runtime/work/stage/usr/local/share/gettext' > ====> Compressing man pages (compress-man) > ls: /usr/ports/devel/gettext-runtime/work/stage/usr/local/info/autosprintf.info*: No such file or directory > > And the error is correct, the file does not exist. Can you email me /usr/ports/devel/gettext-runtime/work/gettext-0.19.8.1/gettext-runtime/config.log From owner-freebsd-ports@freebsd.org Sat Dec 17 12:17:43 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97071C84661 for ; Sat, 17 Dec 2016 12:17:43 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from mail.abinet.ru (mail.abinet.ru [136.243.72.227]) by mx1.freebsd.org (Postfix) with ESMTP id 616C81DE8 for ; Sat, 17 Dec 2016 12:17:43 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from [10.0.0.1] (unknown [10.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.abinet.ru (Postfix) with ESMTPSA id 9FDBF1D85C for ; Sat, 17 Dec 2016 12:10:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=abinet.ru; s=dkim; t=1481976640; bh=2bgkEupJu6nBBY0uGBPU7K+MmYs9wFS/KKjPUyUksus=; h=Date:From:To:Subject:References:In-Reply-To; b=jMME/0oOxXSseU2O9sYQkQWIXirb/H5idedGU5yQQyuVQkMP34aqLfc4VWkid4TlB oiC0LDAYmoZHIRx7BVojX5QCTdcA7XsgvcybWsmKzESJkCL630QoHr0/nq6uuKw7SF AIwUCo188x/ENWi7jk9CL/Z5LzBu1CAeuaRGk0mg= Message-ID: <58552B3F.3050603@abinet.ru> Date: Sat, 17 Dec 2016 15:10:39 +0300 From: abi User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.9) Gecko/20161026 FossaMail/25.2.4 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: The ports collection has some serious issues References: 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: Sat, 17 Dec 2016 12:17:43 -0000 I tried to switch from portmaster to synth yesterday. Tests was sponsored by zfs snapshots. I still have strong opinion that synth IS NOT replacement for portmaster and not usable at all. Yes, synth build ports, however it's just builds them. I don't receive information: 1. Why it builds exactly this list of ports, what has changed when I upgraded my ports. 2. It doesn't provide dialog for port options, so 2.1 I don't receive information if port options have changed. I don't know what else will be pulled to my system after port tree update. 2.2 If I make option files for all ports, synth fails to rebuild repository if port and it's options are out of sync. 2.3 When port infrastructure switch to newer default version I must be aware that this change occur and set damn options for new default port. So, synth is just a dumb port building tool. If you need your own port options you are in risk. Developer of synth said that the problem is in my 'portmaster thinking' I should change. And now I see that he tried to deprecate portmaster! Fuck it. Until synth gets interactive mode. Probably I will switch to Linux (yes, I know nobody cares) if the ability to keep custom port options will be lost. The only tool for this now is portmaster. Maybe it's my 'portmaster thinking' but I don't understand how one can use synth if he or she want at least be slightly aware what's going on in his/her system. On 17.12.2016 10:49, Hrant Dadivanyan wrote: >>> >>> On Fri, Dec 16, 2016 at 6:42 AM, Peter Jeremy wrote: >>>> On 2016-Dec-15 19:31:22 +0100, list-freebsd-ports at jyborn.se wrote: >>>> Interestingly, the most vocal proponent of deleting portmaster and >>>> portupgrade is the author/maintainer of synch. >> >> It's not interesting at all. Synth was in a large part created because >> people were irrationally sticking with portmaster and more frighteningly >> gaining new users. >> > > Please don't judge what's rational and what's not, because it's community > and when many people, even irrationally from your POV, sticking with > portmaster, then it's worth to consider and look for a way to keep it up. > >> The point is that these tools are in great shape and to imply otherwise >> needs proof. It's portmaster that's not receiving updates. >> > > In current shape it works well for many people (and demanded by) in > community, so why should it be removed ? You can warn as much as you want > against, but you can't decide to remove. > From owner-freebsd-ports@freebsd.org Sat Dec 17 12:42:03 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E376CC84FEA for ; Sat, 17 Dec 2016 12:42:03 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from nm13-vm3.bullet.mail.ne1.yahoo.com (nm13-vm3.bullet.mail.ne1.yahoo.com [98.138.91.143]) (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 B296EE15 for ; Sat, 17 Dec 2016 12:42:03 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1481978358; bh=dx5pnN0qgNji2Ni/XyrSVIoq25njG7wvYAlBzkb97og=; h=Subject:To:References:From:Date:In-Reply-To:From:Subject; b=KQijPoidj8cb6sI+AK/7VGepJqAauA3efAbBB3BbZ2Kb/Gp6hGq+W4m05zFaRUi2lSUIQBYQS2g+Qcf4jIa1rNWjgXo5WqEhhm01nXbQ2s8Z3v3ZRQQqp2qyRgBFhw2pweO2m6v0ZIjYawH5bZcNckM6SsDP1a7C9hfV/4oXMJUoLeqnbE53gun/G4C/47cyoadwkPw2Oh8Qr6oAmrIuBWR7GfqkKbo/bdgspL3cn2h9I+ClBfBNvR48DZ7RJhkoVBuM04qFU9rtJFxfd7wYbx2Q+kI9EkuTxPLvTbk5/T9eooudsY7WIWz+ZWe1KYwlP0iRGXD5uRrrnRyJhctgGA== Received: from [98.138.226.177] by nm13.bullet.mail.ne1.yahoo.com with NNFMP; 17 Dec 2016 12:39:18 -0000 Received: from [98.138.89.253] by tm12.bullet.mail.ne1.yahoo.com with NNFMP; 17 Dec 2016 12:39:18 -0000 Received: from [127.0.0.1] by omp1045.mail.ne1.yahoo.com with NNFMP; 17 Dec 2016 12:39:18 -0000 X-Yahoo-Newman-Id: 88919.50937.bm@omp1045.mail.ne1.yahoo.com Received: (qmail 42551 invoked from network); 17 Dec 2016 12:39:18 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1481978358; bh=dx5pnN0qgNji2Ni/XyrSVIoq25njG7wvYAlBzkb97og=; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=TLfPg0MR33/9aBGPTzE5kdFcW82wgGJz+xMCwHz3l8oglZhapDTZ7JoDqpeuXNLcF4i0T6AVWDoV0YZqXYqwyRu/MjvyRg3H4+UGQ6yShF98v/b9XR0xdQzBMuRy7WA2ESlrSa8eqIH3YzxraHPzgrdiCeJQ40A/wy9vC+eh318= X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: kmyLeMUVM1mpTSrtN18toO.Wd0wqZSy9tVxf0dpcyvoJHlQ sfnDOkMELNLkQ71kWk.Ml5FCBIESYgzRquHqFBHcvSrH4tnlatzwM1VJJdA3 nM6wE3EEW7TwQzRO.8wqeFTqv.nGAWNaMcxBbMwT6qVY1JASsx0OJAbIbBFp uXO8AdEUXLxq9Aesf38R_eexBcahTBPfzhXz3YdX76848lmsICe43qABZgPm ElBq9p5De6CfFtj8PpLVnC4F_BEL_keK4jBnpZX1r7NvlElj4zpcI7qcepIg jqvhorrzKxrB2rHULBS_rdd2M_vKWXTHbTAFuG.O.0UU5CT9Pks_etd53Wk8 oGENqLj7n_LFu9hjeYKmhMj0WX_8_Gvlrfyv2eyhcnufkNV1_pVN1EvKACvZ U5KYhT0uMOPEfZOWEtj3k1w7HzJZ1YxJ3i0efuk8gkh5FLlZJjlf6.2Av4BN pICyTIVWooSjNCna3ssQWhvFRWMNnIHEzhqz0rWBmrUqJnk77LZcapu66tz4 pBHUfTBGYTSaM5KZhZKgRA5CKkMqFjqY.tAe4H.zdLPZTfcWfcCm9xQRRefu nQFkPv.quhY0lzRJA5vA- X-Yahoo-SMTP: 6IZaPQyswBAeyzp3urHRlQfBxGxx4Js3YAIn Subject: Re: The ports collection has some serious issues To: freebsd-ports@freebsd.org References: <20161208085926.GC2691@gmail.com> <3b00e76a-7a97-aa1b-72e9-236161044c3b@m5p.com> <20161215183122.GG5268@pol-server.leissner.se> From: Jeffrey Bouquet Message-ID: Date: Sat, 17 Dec 2016 04:39:15 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161215183122.GG5268@pol-server.leissner.se> Content-Type: text/plain; charset=windows-1252; 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: Sat, 17 Dec 2016 12:42:04 -0000 tacking a slightly off-topic topic onto this one On 12/15/16 10:31 AM, list-freebsd-ports@jyborn.se wrote: > On Thu, Dec 15, 2016 at 01:18:05PM -0500, George Mitchell wrote: >> On 12/15/16 09:40, Warren Block wrote: >>> On Thu, 8 Dec 2016, Matt Smith wrote: >>> >>>> On Dec 08 05:16, Daniil Berendeev wrote: >>>>> Although portmaster is not releated to the FreeBSD project and is an >>>>> outside tool, there aren't any alternatives from the project itself. So >>>>> use it or die. Not a nice situation. >>>> People have been trying to get portmaster deprecated and removed from >>>> the handbook but have met with resistance. >>> Well, yes. Because it works, has no dependencies, and there is no >>> equivalent replacement. [...] >> Warren, you have hit the nail on the head. -- George > +1 > > I never have problems with portmaster. > (But portupgrade could at times be an utter mess, > I never looked back after switching to portmaster > many years ago.) > > And I'm not at all interested in running poudriere > or synth, thank you. > > Peter > _______________________________________________ > 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" synth here: silently fails, year in year out synth on a new install equal to this one: good to go poudriere: inexpert, hundreds of .htm saved for howto portmanager: MOVED, saved hours debugging portupgrade/portmaster until it started not working so well. custom .sh : did most of what portmaster did, sometimes very rarely in use edited locally portmaster: fail at coding on my part portmaster: has worked mostly, gave up recently though. Really would like it fully pkg compliant portupgrade: features since /var/db/pkg/DIRECTORIES not front-ended by sqlite3 expertise required have not worked, pkgdb -F for example IIRC All of those restored to 2006 goodness and working together seamlessly? I cannot wait. Possible with enough systemd-too-complex systems migrated to FreeBSD someday may happen... But the reason for this add-on to that topic: due to gcc gcc49 conflicts I was forced to desinstall math/ised. Now: if one will pardon xclip pasted in formatting: pkg-static install ised Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. pkg-static: hugin has a missing dependency: autopano-sift-C pkg-static: truecrypt has a missing dependency: fusefs-kmod Checking integrity... done (2 conflicting) - gcc-4.9.4 conflicts with gcc49-4.9.4_1 on /usr/local/bin/i386-portbld-freebsd11.0-c++49 - gcc-4.9.4 conflicts with gcc49-4.9.4_1 on /usr/local/bin/i386-portbld-freebsd11.0-c++49 Checking integrity... done (0 conflicting) The following 33 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: truecrypt-7.1a_3 gcc49-4.9.4_1 ircii-20151120 py34-setuptools_scm-1.10.1 py34-msgpack-python-0.4.7 3dm-2.11.00.021_1,1 py34-llfuse-1.0 xalarm-3.06_3 p5-PDF-Template-0.22_1 pdflib-perl-7.0.5_2 xpi-web_developer-1.2.2 pathneck-1.3 mpack-1.6_3 webcopy-0.98b7 lha-ac-1.14i_10 lv-4.51_3 window-1.0 solarized-1.0.0 freefonts-0.10_7 weedit-2.0.3 ncp-1.2.4 shorten-3.6.1 jail-primer-0.2 lynis-2.4.0 win32-codecs-20110131,1 areca-cli-i386-1.14.7.150519,1 pkg_cleanup-2.1 sscalc-1.0 New packages to be INSTALLED: ised: 2.7.1_1 gcc: 4.9.4 dejavu: 2.37 Installed packages to be REINSTALLED: pkg-1.9.4 opera-12.16_6 (options changed) Number of packages to be removed: 28 Number of packages to be installed: 3 Number of packages to be reinstalled: 2 The operation will free 103 MiB. 13 MiB to be downloaded. Proceed with this action? [y/N]: n Additionally, it does not build. Maybe on the other machine that synth runs on, I could put it on a thumbdrive and install just the ised binary... Also had to deinstall scilab, PDL, py27-game, solarwolf, etc etc. IIRC Nothing urgent at all but my thoughts on this gcc conflict issue as well as maybe chiming into the topic of this thread Sorry to waste anyone's time, may be a local issue to this particular ports tree, some errant file. From owner-freebsd-ports@freebsd.org Sat Dec 17 13:22:48 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD499C85204 for ; Sat, 17 Dec 2016 13:22:48 +0000 (UTC) (envelope-from tingox@gmail.com) Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 53777128 for ; Sat, 17 Dec 2016 13:22:48 +0000 (UTC) (envelope-from tingox@gmail.com) Received: by mail-lf0-x236.google.com with SMTP id t196so25920134lff.3 for ; Sat, 17 Dec 2016 05:22:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=7OeAV/HE2QS/V+bFvSPDp0AO6V97A+zi1r+M8R3gkjc=; b=C3hRwYPNVEH270ZsGnpILHiXkgZtBv9BsUN1+/WCI8A12W67piLKDZ99/vfeOhSFM2 WIjYLhP9REV1AdC8vYidsfPlMI2V4Edl6E8XK6ItC9F4KtCmXJPd+rHPzcE+KrG8/dTN 7ht18gc7EtOee9fXfO4ZVDI+H/9sp+XyM8cmBonjxeRX3YSKAdA8hbc0jrkgmZssynTF za1KA649Rs/+ziYE1o8OEfjteK197arBG/dC8nnPbv6yyM8gWYHqzk98wYLktkkZ+EQM cOtCgKrRvDou1vk7qw4V+KVdl3lQtC8M02Q5PGtwLhTd89FfaWgrWPGksoUyS7SyFK5d S92Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=7OeAV/HE2QS/V+bFvSPDp0AO6V97A+zi1r+M8R3gkjc=; b=tP77D7rKRHUa+Foy1L39b0jrQEUfAymcOzn/IctNJ8Wal/rVVaWF/9OwOeSOkwKlVJ GuW6Iiusq0HzWSMzIpdrNHk9cZwTyTFdaSg2T5LS5kxYTKbG1ZaVATBGm3moTUhoU4pA ED566V1Y8OHAyN5GMGNJdQ5QjFuuTIl+7FQ3fqIvkc716PnsnqAbtDxwLslkk0Xseq7f /b8smerqZ7GC5jn9L4hUbDZ4AHee3ie7NbPgwSKIOskEskL08NmOZseLoETBVJPVx0w5 gVFbn0UENxAI9Czx7dKgZBs0udILXdWYkb2DCsLhFyMsOSDxjyFJpfxv5VTdvFxiQhPy iWEQ== X-Gm-Message-State: AIkVDXLQIPYv+IczUCkvDHqvHqVaZgWx89qTrrwbv+doWt/2BBibME19kISHMvmzFK0tsuQebuaxheoEbasd0Q== X-Received: by 10.46.21.2 with SMTP id s2mr3304672ljd.19.1481980965264; Sat, 17 Dec 2016 05:22:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.190.77 with HTTP; Sat, 17 Dec 2016 05:22:44 -0800 (PST) In-Reply-To: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> References: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> From: Torfinn Ingolfsen Date: Sat, 17 Dec 2016 14:22:44 +0100 Message-ID: Subject: Re: The ports collection has some serious issues To: FreeBSD Ports ML Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2016 13:22:48 -0000 On Fri, Dec 16, 2016 at 3:45 PM, John Marino wrote: >> > >> I won't say "never". But I feel that both package builders (poudriere, >> synth) need some more time to shake out more issues / bugs and get >> into a better shape first. This isn't based on any specific problems >> or bugs, more a "felleing2 based on people's feedback in the forums >> and on mailing lists. FWIW, the above was written by me, not by Peter Jeremy - the quoting got a bit messed up here. > I insist that you base this on "specific problems". Speaking for Synth, > there are no known bugs in it. There are no pending issues with existing > features. It is updated frequently. AFAIK poudriere is updated regularly > as well. The above is an accusation that you absolutely must back up with > fact because it's basically defamation. Defamation? Accusation? Strong words, and not my intention at all. First of all - anyone can create what he or she wants. And he or she can use whatever logic, reasoning or other means (marketing for example) to get people to use that creation. If people like the creation they will use it, based on their own criteria for using it - not necessarily based on *anything* the creator of said creation has presented at all. Unless the creator is a controlling authority (a government creating new laws that require that everybody drive on the right side of the road for example) he or she can't force anyone to use that creation. And no, it doesn't matter if the creation is the best such creation in the world and it has benchmarks to back it up. Now, regarding synth: as I have already said, I have no special interest in package builders. I do need a tool to build and install the ports I use, and my current tool (portupgrade or manual building) still works for that. I might try synth in the future sometime, but for tools that I have no special interest in, I prefer that they are a bit more mature. I use my own "metric" to measure maturity of a tool - I read users's feedback in forums and mailinglists, and filter out PEBCACs and other "new user - new tool" issues. Based on that, I will consider using a tool when the discussions around it has quieted down to a reasonable level. All subjective, all by my own standards. If you still find this though to handle and an accusation, my suggestion would be for you to take a long holiday break from computers and spend time with friends and family. Best wishes for the holidays for everyone! -- Regards, Torfinn Ingolfsen From owner-freebsd-ports@freebsd.org Sat Dec 17 13:32:07 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB778C85496 for ; Sat, 17 Dec 2016 13:32:07 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from mail.skysmurf.nl (spectrum.skysmurf.nl [83.162.175.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.skysmurf.nl", Issuer "mail.skysmurf.nl" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 692F892D; Sat, 17 Dec 2016 13:32:06 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from spectrum.skysmurf.nl (mail.skysmurf.nl [192.168.42.4]) by mail.skysmurf.nl (8.15.2/8.15.2) with SMTP id uBHDQ9fK001443; Sat, 17 Dec 2016 14:26:09 +0100 (CET) (envelope-from freebsd@skysmurf.nl) Received: by spectrum.skysmurf.nl (sSMTP sendmail emulation); Sat, 17 Dec 2016 14:26:09 +0100 Date: Sat, 17 Dec 2016 14:26:09 +0100 From: Alphons van Werven To: John Marino Cc: FreeBSD Mailing List , tingox@gmail.com Subject: Re: The ports collection has some serious issues Message-ID: <20161217132608.GA1352@spectrum.skysmurf.nl> References: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline In-Reply-To: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> X-PGP-Key: http://www.skysmurf.nl/~fonz/fonz_pubkey.asc User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2016 13:32:08 -0000 --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable John Marino wrote: > In fact, anyone that updates ports should use either poudriere testport > or synth test. Then consider these relinquished: /usr/ports/archivers/zip /usr/ports/astro/wmmoonclock /usr/ports/astro/xearth /usr/ports/devel/byaccj /usr/ports/devel/csmith /usr/ports/devel/gzstream /usr/ports/devel/t1lib /usr/ports/games/xroach /usr/ports/games/xteddy /usr/ports/graphics/hsetroot /usr/ports/mail/xmailbox /usr/ports/misc/fortune-mod-futurama /usr/ports/science/gromacs /usr/ports/security/chaosreader /usr/ports/www/fcgi /usr/ports/www/fcgiwrap /usr/ports/x11/grabc /usr/ports/x11/xdialog /usr/ports/x11/xtrlock /usr/ports/x11-fm/catseye-fm /usr/ports/x11-fonts/cyberbit-ttfonts /usr/ports/x11-servers/Xfstt Please remove my e-mail address and mirror URL from the relevant Makefiles. --=20 A.J. "Fonz" van Werven mailsig: Help! I'm a prisoner in a Chinese fortune cookie factory. --zhXaljGHf11kAtnf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJYVTzwAAoJEAfP7gJTaCe8Cs4QAJLBdj0fUBaRE35N8snQcjHn 8deLeNX/OW7RIu9nqSuO5m9N+Dm9szQrasVvXsWsCoigLcTnpwI+jtz/gsxLR0m3 llsN/dQ67C8RzjW/Alju4Dqrbo90RiEUegVVvVQoZTtLMSBow+GtrntJmXB80hvj yVDVVUQRjBzJjlsd7zOTIKlFYKfMVFJcEIBk0PycAh3qNKiP//hg5BmOaGVF9Nf6 Wg54TQMilEIzOxLuoBnf/LuUUyzQ4vSNteDQHvuJzpUBlXKgfbne10uN1RpQ9F9f qEpA6yxhOj6SCUbRfeSIxvEx6/tsx8w0jTqcfHS+mEIkVSWOKMB4nu7Iqb8bQ8WH ADpMEyiuvtUY3dUw4hb0/H1my4UVUUpxTAQWj1C37yg4HbZAIU7wpRsNQ08rdCR9 eHQql186arkKR9LEIuPYmg1yC2i2CCNWKGxcF0QeBSKY9O+/8YaTQrS7nNDHWwsB iYWpLXoB/xMov+EZLRh4nQLRTOBZYPIgLGabJNOlB1J9UwQXN08wVAlYaZC5OwCR M8F8/BtPleNlSjcduOmJGopG9SZJI35cn1iWm5SWaLYVpMzwsjlLjkJn61jcZcp9 eBLdmYS0ZoKDsR23BLgyWyohODDfH2KnHHnOmwP7V/XCdDKRlWV4zRmv8d842gBq extk2YfC6X34Gjl9ZpqE =5pvm -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf-- From owner-freebsd-ports@freebsd.org Sat Dec 17 13:55:20 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9F7BC85A00 for ; Sat, 17 Dec 2016 13:55:20 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 519631498 for ; Sat, 17 Dec 2016 13:55:19 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 36581 invoked by uid 89); 17 Dec 2016 13:55:11 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@185.17.206.127) by mail.grem.de with ESMTPA; 17 Dec 2016 13:55:11 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: The ports collection has some serious issues From: Michael Gmelin X-Mailer: iPhone Mail (14C92) In-Reply-To: <20161217132608.GA1352@spectrum.skysmurf.nl> Date: Sat, 17 Dec 2016 14:55:11 +0100 Cc: John Marino , tingox@gmail.com, FreeBSD Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: <54CEEF4F-3E62-45D1-902A-DA4372E9F060@freebsd.org> References: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> <20161217132608.GA1352@spectrum.skysmurf.nl> To: Alphons van Werven 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, 17 Dec 2016 13:55:21 -0000 > On 17 Dec 2016, at 14:26, Alphons van Werven wrote: >=20 > John Marino wrote: >=20 >> In fact, anyone that updates ports should use either poudriere testport >> or synth test. >=20 > Then consider these relinquished: >=20 > /usr/ports/archivers/zip > /usr/ports/astro/wmmoonclock > /usr/ports/astro/xearth > /usr/ports/devel/byaccj > /usr/ports/devel/csmith > /usr/ports/devel/gzstream > /usr/ports/devel/t1lib > /usr/ports/games/xroach > /usr/ports/games/xteddy > /usr/ports/graphics/hsetroot > /usr/ports/mail/xmailbox > /usr/ports/misc/fortune-mod-futurama > /usr/ports/science/gromacs > /usr/ports/security/chaosreader > /usr/ports/www/fcgi > /usr/ports/www/fcgiwrap > /usr/ports/x11/grabc > /usr/ports/x11/xdialog > /usr/ports/x11/xtrlock > /usr/ports/x11-fm/catseye-fm > /usr/ports/x11-fonts/cyberbit-ttfonts > /usr/ports/x11-servers/Xfstt >=20 > Please remove my e-mail address and mirror URL from the relevant > Makefiles. >=20 Maybe you could elaborate a bit more what you find so annoying about running= "poudriere testport origin" before doing "svn commit" that you are willing t= o drop port maintainership over it? -m= From owner-freebsd-ports@freebsd.org Sat Dec 17 14:38:12 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB796C841D3 for ; Sat, 17 Dec 2016 14:38:12 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C51A0A14 for ; Sat, 17 Dec 2016 14:38:12 +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 50E242070E for ; Sat, 17 Dec 2016 09:38:11 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute7.internal (MEProxy); Sat, 17 Dec 2016 09:38:11 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=skunkwerks.at; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= mesmtp; bh=A7jyRx7bCSvojsXaYS8EtnQhHqw=; b=Ijjq4CnbubTAEu6Tq5zzr EzptAW1+tL5lO3uuu2f4SIxIWjiyL5NvfiraoCdDnFoxxk1zGTSWr/akjO6vYGC/ lZG7VA6BMRIXs0bOq7IO2Au0L0NVjfb/xD7BUY3G7iiPYTNPzuWhah6SRa2y+IMF ZpIWHqsE6lkFVmQL+/So78= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=smtpout; bh=A7jyRx7bCSvojsXaYS8EtnQhH qw=; b=lNRlPaesnUv4AwKYvYR0MKps7/fBQclHxMgoA9FgLa0E4ybj5ZzahAKf1 rPhDIUGdfFzILNDROreyKfxv6lQPcQLHZ9mmnDjpJLMyrIZoJcyp/uoPd+Ut/FJV m4QzAWlVMz7Bos9hwgL3n+ksKg/l4GD48f6h0xriHLAgaokEZ8= X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 1E5F448001; Sat, 17 Dec 2016 09:38:11 -0500 (EST) Message-Id: <1481985491.3272909.822072409.1CF4492A@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-07a65709 Subject: Re: www/h2o needs a committer [BZ#213733] Date: Sat, 17 Dec 2016 15:38:11 +0100 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, 17 Dec 2016 14:38:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213733 www/h2o update this still needs a committer - I am getting bugged by users waiting for this to land. thanks! A+ Dave From owner-freebsd-ports@freebsd.org Sat Dec 17 14:52:19 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA1EEC84B83 for ; Sat, 17 Dec 2016 14:52:19 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [185.24.122.233]) (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 97C3D16B6 for ; Sat, 17 Dec 2016 14:52:18 +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 uBHEqGSM027277 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sat, 17 Dec 2016 14:52:17 GMT (envelope-from list1@gjunka.com) Subject: Re: The ports collection has some serious issues To: freebsd-ports@freebsd.org References: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> From: Grzegorz Junka Message-ID: <77f78075-6724-bd4f-7822-638e7d6575db@gjunka.com> Date: Sat, 17 Dec 2016 14:52:16 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; 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: Sat, 17 Dec 2016 14:52:20 -0000 On 17/12/2016 13:22, Torfinn Ingolfsen wrote: > On Fri, Dec 16, 2016 at 3:45 PM, John Marino wrote: > > Now, regarding synth: as I have already said, I have no special > interest in package builders. I do need a tool to build and install > the ports I use, and my current tool (portupgrade or manual building) > still works for that. > I might try synth in the future sometime, but for tools that I have no > special interest in, I prefer that they are a bit more mature. I use > my own "metric" to measure maturity of a tool - I read users's > feedback in forums and mailinglists, and filter out PEBCACs and other > "new user - new tool" issues. Based on that, I will consider using a > tool when the discussions around it has quieted down to a reasonable > level. All subjective, all by my own standards. > > If you still find this though to handle and an accusation, my > suggestion would be for you to take a long holiday break from > computers and spend time with friends and family. > Best wishes for the holidays for everyone! I believe the main point is that portupgrade/portmaster shouldn't be used by default by newcomers to FreeBSD. It easily breaks and if you have no knowledge about the system, you will post questions to this list, which seems to be annoying people. I tried to used portupgrade/portmaster in the past and whereas it's fine with small amount of packages, is unusable when there is a few hundred or thousand of them installed. Very often the build was leaving my system messed up because some port only partially build and half of the dependencies were reinstalled and the other half were not. There is no undo in those tools. It's essentially press enter and pray. Grzegorz From owner-freebsd-ports@freebsd.org Sat Dec 17 14:55:31 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3DF2C84C88 for ; Sat, 17 Dec 2016 14:55:31 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (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 B013E17C5; Sat, 17 Dec 2016 14:55:30 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id 62D7343C0B; Sat, 17 Dec 2016 08:54:19 -0600 (CST) Subject: Re: The ports collection has some serious issues To: Michael Gmelin , Alphons van Werven References: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> <20161217132608.GA1352@spectrum.skysmurf.nl> <54CEEF4F-3E62-45D1-902A-DA4372E9F060@freebsd.org> Cc: tingox@gmail.com, FreeBSD Mailing List Reply-To: marino@freebsd.org From: John Marino Message-ID: <0f993f23-0029-6c21-d42b-7109141f98b6@marino.st> Date: Sat, 17 Dec 2016 08:55:28 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <54CEEF4F-3E62-45D1-902A-DA4372E9F060@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161217-0, 12/17/2016), Outbound message X-Antivirus-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: Sat, 17 Dec 2016 14:55:31 -0000 On 12/17/2016 07:55, Michael Gmelin wrote: > > >> On 17 Dec 2016, at 14:26, Alphons van Werven wrote: >> >> John Marino wrote: >> >>> In fact, anyone that updates ports should use either poudriere testport >>> or synth test. >> >> Then consider these relinquished: >> >> /usr/ports/archivers/zip >> /usr/ports/astro/wmmoonclock >> /usr/ports/astro/xearth >> /usr/ports/devel/byaccj >> /usr/ports/devel/csmith >> /usr/ports/devel/gzstream >> /usr/ports/devel/t1lib >> /usr/ports/games/xroach >> /usr/ports/games/xteddy >> /usr/ports/graphics/hsetroot >> /usr/ports/mail/xmailbox >> /usr/ports/misc/fortune-mod-futurama >> /usr/ports/science/gromacs >> /usr/ports/security/chaosreader >> /usr/ports/www/fcgi >> /usr/ports/www/fcgiwrap >> /usr/ports/x11/grabc >> /usr/ports/x11/xdialog >> /usr/ports/x11/xtrlock >> /usr/ports/x11-fm/catseye-fm >> /usr/ports/x11-fonts/cyberbit-ttfonts >> /usr/ports/x11-servers/Xfstt >> >> Please remove my e-mail address and mirror URL from the relevant >> Makefiles. >> > > Maybe you could elaborate a bit more what you find so annoying about running "poudriere testport origin" before doing "svn commit" that you are willing to drop port maintainership over it? > > -m > Especially since "update ports" means "commit to ports" and Fonz doesn't have commit privileges. It wasn't even directed at maintainers (although I would say that maintainers that don't test their updates aren't doing good work and relying on a committer to catch obvious mistakes). I like Fonz a lot but that is pure drama queen stuff right there. "Check your work, please". "I quit". Ok. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-ports@freebsd.org Sat Dec 17 15:06:30 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF1DFC84F68 for ; Sat, 17 Dec 2016 15:06:30 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (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 CB5871BDC for ; Sat, 17 Dec 2016 15:06:30 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id 03E9D43C0B; Sat, 17 Dec 2016 09:05:19 -0600 (CST) Subject: Re: The ports collection has some serious issues To: Hrant Dadivanyan References: Cc: FreeBSD Mailing List , tingox@gmail.com Reply-To: marino@freebsd.org From: John Marino Message-ID: <99aa1f8b-066a-088b-e4ce-63bb2d291236@marino.st> Date: Sat, 17 Dec 2016 09:06:29 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161217-0, 12/17/2016), Outbound message X-Antivirus-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: Sat, 17 Dec 2016 15:06:31 -0000 On 12/17/2016 01:49, Hrant Dadivanyan wrote: >>> >>> On Fri, Dec 16, 2016 at 6:42 AM, Peter Jeremy wrote: >>>> On 2016-Dec-15 19:31:22 +0100, list-freebsd-ports at jyborn.se wrote: >>>> Interestingly, the most vocal proponent of deleting portmaster and >>>> portupgrade is the author/maintainer of synch. >> >> It's not interesting at all. Synth was in a large part created because >> people were irrationally sticking with portmaster and more frighteningly >> gaining new users. >> > > Please don't judge what's rational and what's not, because it's community > and when many people, even irrationally from your POV, sticking with > portmaster, then it's worth to consider and look for a way to keep it up. Why don't *you* look for a way to keep it up? TZ already said he is looking to drop maintainership. Now *YOU* have the chance to do more than order volunteers around. > >> The point is that these tools are in great shape and to imply otherwise >> needs proof. It's portmaster that's not receiving updates. >> > > In current shape it works well for many people (and demanded by) in > community, so why should it be removed ? You can warn as much as you want > against, but you can't decide to remove. > > Hrant Hrant, you must work on your reading comprehension. Nobody has talked about removing portmaster, at all. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-ports@freebsd.org Sat Dec 17 15:24:16 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1AD9C852F5 for ; Sat, 17 Dec 2016 15:24:16 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9F1542F2 for ; Sat, 17 Dec 2016 15:24:16 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: by mailman.ysv.freebsd.org (Postfix) id 9B964C852F4; Sat, 17 Dec 2016 15:24:16 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99634C852F3 for ; Sat, 17 Dec 2016 15:24:16 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (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 6D2212F1 for ; Sat, 17 Dec 2016 15:24:16 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id D2B4D43C0B; Sat, 17 Dec 2016 09:23:05 -0600 (CST) From: John Marino Reply-To: marino@freebsd.org To: "ports@FreeBSD.org Ports" , mueller6722@twc.com Subject: The ports collection has some serious issues Message-ID: Date: Sat, 17 Dec 2016 09:24:14 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161217-0, 12/17/2016), Outbound message X-Antivirus-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: Sat, 17 Dec 2016 15:24:16 -0000 From Thomas Mueller: >> From John Marino: >> Starting with a clean system: 1) install synth from binary package >> from official freebsd builder (a single >> package) 2) Configure synth if necessary 3) command synth to build >> itself 4) pkg delete synth (system is once again clean) 5) pkg add -F >> /path/to/synth/packages/synth-* > >> Now you have a system containing s/w built by itself. On an modest >> system less than 4 years old, it might take 30 minutes at most. > > I believe you could cd $PORTSDIR/ports-mgmt/synth and > make package-recursive |& tee build-12amd64.log (or whatever you want to > name the log file; this example if for shell tcsh)? That installs build dependencies on the system. That would be no better than running portmaster the first time. If you run the process I suggested, you'll end up with a self-hosted machine with no extra stuff installed. > For a system with pkgng, is there any difference in package format > between "make install", portmaster and portupgrade? There shouldn't be, the ports framework is responsible for creating the package. > If your system already has portmaster, you could portmaster > ports-mgmt/synth |& tee synth-12amd64.log? > > And then switch from portmaster to synth for all further ports > builds/updates? sure. Although it will still be dirty from portmaster so at that point you would gather a "prime list" of packages, feed thoughs into synth to create a local repository, remove all packages from the system and re-install them with the "prime list" and the new local repository. > It would not be necessary to start with a clean system for FreeBSD, as > opposed to NetBSD, or am I mistaken here? No, you can start anytime but I do recommend the procedure above to ensure the system is in good shape and doesn't contain unnecessary package installations. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-ports@freebsd.org Sat Dec 17 16:45:09 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1DF03C84F30 for ; Sat, 17 Dec 2016 16:45:09 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0B249191C for ; Sat, 17 Dec 2016 16:45:09 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: by mailman.ysv.freebsd.org (Postfix) id 07B42C84F2F; Sat, 17 Dec 2016 16:45:09 +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 05A12C84F2E for ; Sat, 17 Dec 2016 16:45:09 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (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 C70AB191B for ; Sat, 17 Dec 2016 16:45:08 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id EB70043BDE; Sat, 17 Dec 2016 10:43:51 -0600 (CST) From: John Marino Reply-To: marino@freebsd.org To: "ports@FreeBSD.org Ports" , abi@abinet.ru Subject: The ports collection has some serious issues Message-ID: Date: Sat, 17 Dec 2016 10:45:00 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161217-0, 12/17/2016), Outbound message X-Antivirus-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: Sat, 17 Dec 2016 16:45:09 -0000 abi wrote: > I tried to switch from portmaster to synth yesterday. Tests was > sponsored by zfs snapshots. > > I still have strong opinion that synth IS NOT replacement for portmaster > and not usable at all. > > Yes, synth build ports, however it's just builds them. I don't receive > information: > > 1. Why it builds exactly this list of ports, what has changed when I > upgraded my ports. What you are apparently saying is that Synth wants to rebuild certain ports after you update your ports tree and you want the exact reaason why. That reasoning is available via the WHYFAIL environment variable and the new 06_obsolete_packages.log file. Unless you're hunting for bugs in synth, this information is "just for fun". If your goal is to not rebuild packages when synth (and poudriere) say they must be rebuilt, then yes, portmaster is for you along with the consequences. > 2. It doesn't provide dialog for port options, so > 2.1 I don't receive information if port options have changed. I don't > know what else will be pulled to my system after port tree update. which of course is a false statement. If you set port options which then change, Synth will stop and tell you to reconfigure or remove the saved port options. > 2.2 If I make option files for all ports, synth fails to rebuild > repository if port and it's options are out of sync. yes, of course. If you give it impossible instructions, it will stop and ask you to fix them. Any reasonable person would want to be informed when the options are incorrect. Did you also notice that extended use of portmaster resulted in dozens of obsolete options files that you weren't aware of? So your criticism here is that you think Synth should just ignore these bad configurations? > 2.3 When port infrastructure switch to newer default version I must be > aware that this change occur and set damn options for new default port. Another false statement. The ports framework has a DEFAULT_VERSIONS support which you can override via a profile mk.conf, just as poudriere does. Doing so avoid surprises. There is also an UPDATING file in the ports tree but that's more for portmaster and portupgrade users. > So, synth is just a dumb port building tool. If you need your own port > options you are in risk. Developer of synth said that the problem is in > my 'portmaster thinking' I should change. An absurd assertion spoken loudly by someone that is ill-informed on the topic. > Fuck it. Until synth gets interactive mode. Probably I will switch to > Linux (yes, I know nobody cares) if the ability to keep custom port > options will be lost. The only tool for this now is portmaster. Regardless of how factually incorrect your evaluation of the other tools are, you have the freedom to make this choice. > Maybe it's my 'portmaster thinking' but I don't understand how one can > use synth if he or she want at least be slightly aware what's going on > in his/her system. Because everyone else used synth (or poudriere) long enough to understand how those tools actually work. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-ports@freebsd.org Sat Dec 17 18:33:03 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62DA6C85139 for ; Sat, 17 Dec 2016 18:33:03 +0000 (UTC) (envelope-from abi@abinet.ru) 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 4EC2F78C for ; Sat, 17 Dec 2016 18:33:03 +0000 (UTC) (envelope-from abi@abinet.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 4B5A8C85138; Sat, 17 Dec 2016 18:33:03 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 493FAC85137 for ; Sat, 17 Dec 2016 18:33:03 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from mail.abinet.ru (mail.abinet.ru [136.243.72.227]) by mx1.freebsd.org (Postfix) with ESMTP id C73E178B; Sat, 17 Dec 2016 18:33:01 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from [10.0.1.1] (unknown [10.0.1.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.abinet.ru (Postfix) with ESMTPSA id F1F4A1D99E; Sat, 17 Dec 2016 18:32:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=abinet.ru; s=dkim; t=1481999579; bh=rNYcVbhKCRBkXuB+AIwsb2EGTcvbakrrNf9gljjSIm8=; h=Date:From:To:Subject:References:In-Reply-To; b=FConpytL/tGAjKtKHWY6g41cA3QXTFaJK6xy0Dd2jRcO43sKUlhxEEpPnguHHpatM rKqd3h4xxAYRaK0BCDydYqQFQZUu9kZLeZ4oNtOZoko8qq1KPufzqm0JXvgcIA6hjf FGoa6G9FFGDx73xZ0qovfVPSLyyJK/qVvGNphH3M= Message-ID: <58558519.3080509@abinet.ru> Date: Sat, 17 Dec 2016 21:34:01 +0300 From: abi User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.8) Gecko/20151117 FossaMail/25.1.9 MIME-Version: 1.0 To: marino@freebsd.org, "ports@FreeBSD.org Ports" Subject: Re: The ports collection has some serious issues References: 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: Sat, 17 Dec 2016 18:33:03 -0000 >> 2. It doesn't provide dialog for port options, so >> 2.1 I don't receive information if port options have changed. I don't >> know what else will be pulled to my system after port tree update. > > which of course is a false statement. > If you set port options which then change, Synth will stop and tell > you to reconfigure or remove the saved port options. Not at all. For example, let's assume I go recommended way and have options for ports with not default settings. Let's say, I have perl with default options (no OPTIONS file). Let's say port maintainer adds new option, [NSA Backdoor] Perl will be silently compiled with that option, right? This is not paranoia, here is example from real world - I rebuilded one port and noticed new option - [USE GCC] with default On. I really don't want that gnu beast in my system, so I investigated the problem and suggested patch to compile port under clang. Everyone happy. We can search PR database if you don't believe me. If I was synth user, I've ended with gcc pulled. > >> 2.2 If I make option files for all ports, synth fails to rebuild >> repository if port and it's options are out of sync. > > yes, of course. If you give it impossible instructions, it will stop > and ask you to fix them. Any reasonable person would want to be > informed when the options are incorrect. Did you also notice that > extended use of portmaster resulted in dozens of obsolete options > files that you weren't aware of? So your criticism here is that you > think Synth should just ignore these bad configurations? No, I didn't notece obsolete options. Maybe my /var/db/ports is a complete mess and I should cry in tears. but when portmaster encounters new options it invokes dialog4ports and let me fix the problem. If this leaves some staled OPTIONS file, I'd say it's portmaster bug, not design feature. We all know that portmaster is in rather poor shape. > >> 2.3 When port infrastructure switch to newer default version I must be >> aware that this change occur and set damn options for new default port. > > Another false statement. > The ports framework has a DEFAULT_VERSIONS support which you can > override via a profile mk.conf, just as poudriere does. Doing so > avoid surprises. There is also an UPDATING file in the ports tree but > that's more for portmaster and portupgrade users. First of all, synth ignores /etc/make.conf completely. Yes, we definitely need another place to keep global make options, however DEFAULT_VERSIONS suggestion is a bad advice here. Here is example: recently ports framework deprecated perl 5.20 and switched to 5.24 portmaster users should recompile all ports depended on perl (from my point of view this is done not very reliable), but when it comes to new perl, portmaster will invoke dialog4ports. synth user with non-default perl options will receive new perl with default one. I hit this very problem during my synth test when I noticed pgadmin3 liked to postgresql93-client and added DEFAULT_VERSIONS to 96. > >> So, synth is just a dumb port building tool. If you need your own port >> options you are in risk. Developer of synth said that the problem is in >> my 'portmaster thinking' I should change. > > An absurd assertion spoken loudly by someone that is ill-informed on > the topic. I see how synth can be used in pkg framework, I even agree that synth is poudriere done right and I feel I will use synth test feature for ports I maintain, what I fail to see, how I can use it to keep my laptop updated. I'm not asking for pony here, the examples I provided (if true) lead to overcomplexity maintaining packages up to date. From owner-freebsd-ports@freebsd.org Sat Dec 17 18:45:33 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D01CC853CD for ; Sat, 17 Dec 2016 18:45:33 +0000 (UTC) (envelope-from tingox@gmail.com) Received: from mail-lf0-x241.google.com (mail-lf0-x241.google.com [IPv6:2a00:1450:4010:c07::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 ABD60E3A for ; Sat, 17 Dec 2016 18:45:32 +0000 (UTC) (envelope-from tingox@gmail.com) Received: by mail-lf0-x241.google.com with SMTP id 30so2565487lfy.1 for ; Sat, 17 Dec 2016 10:45:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=Un4AcG/RJtCufcMRL3H28Zvcu7nGQJfxTlAmE0ZbVFE=; b=IBU+jURFwQkhGdTuwmKfVnDW2XIIRLFd2CW69GEIlaqry4M2f+RWBo6RCH6Tw5LEj+ NNWMO8g/bY/ThektSY+w8nVx/HxRUWOJioZTsD6ahwpH6b08SoMIEorep7e9UM6e1I4S 7mJG6yGjM2LYGWU34NN+SsuawWF87+ka/EQJ9AT6AROWZOzSKgi4y8F6lCqltsBNwflA DSHWbwLh7S1C4T9pv6HUs+qsBuUbogOH8Nj+cONxRiGf4Ybws7Y9MhGR6Bth6WMtMH8t 6/ydKMJK0/hG0zdcnCXQUl3vQFx/Ifxn1Ww9Wq+GIWJeAaG9k1dN+jYZpw37RCBkFbHu 5mKA== 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:cc; bh=Un4AcG/RJtCufcMRL3H28Zvcu7nGQJfxTlAmE0ZbVFE=; b=UjuqaZd8TCBdx0pKqKXS7X79JvSX+UWmktjD6RWdaDZFPddteWbTgtadRiIIbDTjVZ V49h2gu+sSKv6L88mrM2fZuxCqkfq/43ML0ZJ0d3VddBdscDIv4b9EAmXhcegUaCa1J7 FT+ajeG38uPIGP1GAgKEkDaa4JHhTy1T8+DqW6JrCOrxj1qDrk9luqOOmHc2qLIUYwBx OtMunEYGsFxCcd/VkRKt36fvNScPYzRdpP5kyI1UV9dlONcG8Hhau8WFLDWdYqTKrvb+ 9mHl0ISn5BtbZwxa2iSttc27Y67N94VFOfmab0MbqYjgS2R59TLzn5M7SQGN6UNKZ8Rv TuCQ== X-Gm-Message-State: AIkVDXLa/wk20jcd4bt8nhAlfyUpO1nU1dIz09J1jhFqjC8SVd1gUIp8ex1z5S3jzRzy0Lh36TyHssHRCEVSQg== X-Received: by 10.46.21.2 with SMTP id s2mr3753886ljd.19.1482000330909; Sat, 17 Dec 2016 10:45:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.190.77 with HTTP; Sat, 17 Dec 2016 10:45:30 -0800 (PST) From: Torfinn Ingolfsen Date: Sat, 17 Dec 2016 19:45:30 +0100 Message-ID: Subject: graphics/ocropus - new repository? To: FreeBSD Ports ML Cc: hiroto.kagotani@gmail.com Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2016 18:45:33 -0000 FWIW, it looks like https://github.com/tmbdev/ocropy is a (new) repository for ocropus source code. HTH -- Regards, Torfinn Ingolfsen From owner-freebsd-ports@freebsd.org Sat Dec 17 18:51:48 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B0DEC8548A for ; Sat, 17 Dec 2016 18:51:48 +0000 (UTC) (envelope-from freebsd.contact@marino.st) 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 467791131 for ; Sat, 17 Dec 2016 18:51:48 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: by mailman.ysv.freebsd.org (Postfix) id 42DEFC85489; Sat, 17 Dec 2016 18:51:48 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4288FC85488 for ; Sat, 17 Dec 2016 18:51:48 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (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 1FACD1130 for ; Sat, 17 Dec 2016 18:51:47 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id 31C10438BD; Sat, 17 Dec 2016 12:50:37 -0600 (CST) Subject: Re: The ports collection has some serious issues To: abi , "ports@FreeBSD.org Ports" References: <58558519.3080509@abinet.ru> From: John Marino Reply-To: marino@freebsd.org Message-ID: Date: Sat, 17 Dec 2016 12:51:42 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <58558519.3080509@abinet.ru> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161217-0, 12/17/2016), Outbound message X-Antivirus-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: Sat, 17 Dec 2016 18:51:48 -0000 On 12/17/2016 12:34, abi wrote: > >>> 2. It doesn't provide dialog for port options, so >>> 2.1 I don't receive information if port options have changed. I don't >>> know what else will be pulled to my system after port tree update. >> >> which of course is a false statement. >> If you set port options which then change, Synth will stop and tell >> you to reconfigure or remove the saved port options. > > Not at all. For example, let's assume I go recommended way and have > options for ports with not default settings. Let's say, I have perl with > default options (no OPTIONS file). Let's say port maintainer adds new > option, [NSA Backdoor] > Perl will be silently compiled with that option, right? Yes. If you don't explicitly save the options then Synth has no way to detect a change in options. > This is not paranoia, here is example from real world - I rebuilded one port and > noticed new option - [USE GCC] with default On. I really don't want that > gnu beast in my system, so I investigated the problem and suggested > patch to compile port under clang. Everyone happy. We can search PR > database if you don't believe me. > If I was synth user, I've ended with gcc pulled. If your view of the world means that any or all ports maintainers are out to get you, then yes, I see your problem. There are ways to recursively set every possible option though. You can easily write a script to iterate your build list and recursively check every option using the standard ports framework. If you did that, then synth would detect every option change and stop. > >> >>> 2.2 If I make option files for all ports, synth fails to rebuild >>> repository if port and it's options are out of sync. >> >> yes, of course. If you give it impossible instructions, it will stop >> and ask you to fix them. Any reasonable person would want to be >> informed when the options are incorrect. Did you also notice that >> extended use of portmaster resulted in dozens of obsolete options >> files that you weren't aware of? So your criticism here is that you >> think Synth should just ignore these bad configurations? > No, I didn't notece obsolete options. Maybe my /var/db/ports is a > complete mess and I should cry in tears. but when portmaster encounters > new options it invokes dialog4ports and let me fix the problem. If this > leaves some staled OPTIONS file, I'd say it's portmaster bug, not design > feature. We all know that portmaster is in rather poor shape. The detection of changed options by ports framework doesn't always work. It definitely doesn't work if portmaster is controlling it. You shouldn't rely on this. > First of all, synth ignores /etc/make.conf completely. Yes, we As does poudriere, as it was designed to do. As it should do. > definitely need another place to keep global make options, however > DEFAULT_VERSIONS suggestion is a bad advice here. > Here is example: recently ports framework deprecated perl 5.20 and > switched to 5.24 > portmaster users should recompile all ports depended on perl (from my > point of view this is done not very reliable), but when it comes to new > perl, portmaster will invoke dialog4ports. > synth user with non-default perl options will receive new perl with > default one. I hit this very problem during my synth test when I noticed > pgadmin3 liked to postgresql93-client and added DEFAULT_VERSIONS to 96. synth will rebuild everything that changes as a result of change to [profile]-make.conf as does poudriere. It deletes the obsoleted packages first then rebuilds everything that's missing. It works. If you use "synth status" to give it a build list, of course it's also going to keep building the old perl because you told it to. That's just a convenience command. If you want to be exact, you maintain a discrete build list of the prime ports. When in doubt, you can always remove all and reinstall the prime list after the repository is brought up to speed. That's not necessarily done often, but it is guaranteed to always work. > I see how synth can be used in pkg framework, I even agree that synth is > poudriere done right and I feel I will use synth test feature for ports > I maintain, what I fail to see, how I can use it to keep my laptop > updated. I'm not asking for pony here, the examples I provided (if true) > lead to overcomplexity maintaining packages up to date. I guess it just takes more experience. It's definitely not more complex than portmaster. I would say it's simpler. Plus the fact that portmaster can only build serially while both synth and poudriere build in parallel is a huge advantage to any single system user. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-ports@freebsd.org Sat Dec 17 19:35:22 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34077C850C5 for ; Sat, 17 Dec 2016 19:35:22 +0000 (UTC) (envelope-from linimon@lonesome.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 22C9132D for ; Sat, 17 Dec 2016 19:35:22 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mailman.ysv.freebsd.org (Postfix) id 1F391C850C4; Sat, 17 Dec 2016 19:35:22 +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 1ED51C850C2 for ; Sat, 17 Dec 2016 19:35:22 +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 EE65032C; Sat, 17 Dec 2016 19:35:21 +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 C75F5263; Sat, 17 Dec 2016 13:35:15 -0600 (CST) Date: Sat, 17 Dec 2016 13:35:14 -0600 From: Mark Linimon To: marino@freebsd.org Cc: "ports@FreeBSD.org Ports" , abi@abinet.ru Subject: Re: The ports collection has some serious issues Message-ID: <20161217193514.GA22107@lonesome.com> References: 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: Sat, 17 Dec 2016 19:35:22 -0000 This is the sixth "top of thread" post. Could you please arrange to stop breaking email threading? Thanks. mcl From owner-freebsd-ports@freebsd.org Sat Dec 17 19:40:13 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DBA4BC85231 for ; Sat, 17 Dec 2016 19:40:13 +0000 (UTC) (envelope-from freebsd.contact@marino.st) 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 C6EB07A2 for ; Sat, 17 Dec 2016 19:40:13 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: by mailman.ysv.freebsd.org (Postfix) id C641FC85230; Sat, 17 Dec 2016 19:40:13 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5EDDC8522F for ; Sat, 17 Dec 2016 19:40:13 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (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 A36CF7A1 for ; Sat, 17 Dec 2016 19:40:12 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id DDB0143BA1; Sat, 17 Dec 2016 13:39:01 -0600 (CST) Subject: Re: The ports collection has some serious issues To: Mark Linimon References: <20161217193514.GA22107@lonesome.com> Cc: "ports@FreeBSD.org Ports" , abi@abinet.ru Reply-To: marino@freebsd.org From: John Marino Message-ID: Date: Sat, 17 Dec 2016 13:40:10 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <20161217193514.GA22107@lonesome.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161217-0, 12/17/2016), Outbound message X-Antivirus-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: Sat, 17 Dec 2016 19:40:14 -0000 On 12/17/2016 13:35, Mark Linimon wrote: > This is the sixth "top of thread" post. Could you please arrange to stop > breaking email threading? Thanks. > > mcl > I have to assume you're talking to me. Mark: 1) I am not subscribed to the mail list 2) FreeBSD chooses not to store the raw email content like it does for svn commits. Thus I have no way to "continue" a thread that didn't CC me. Now, given those two facts, what *EXACTLY* do you suggest I do differently? Right now you are attacking me for something that's not my fault. It's FreeBSD's fault if anything. I don't care if the consequence is a broken thread since FreeBSD has the ability to make it better. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-ports@freebsd.org Sat Dec 17 19:48:03 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFA62C85487 for ; Sat, 17 Dec 2016 19:48:03 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from mail.skysmurf.nl (spectrum.skysmurf.nl [83.162.175.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.skysmurf.nl", Issuer "mail.skysmurf.nl" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5DA56B73; Sat, 17 Dec 2016 19:48:02 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from spectrum.skysmurf.nl (mail.skysmurf.nl [192.168.42.4]) by mail.skysmurf.nl (8.15.2/8.15.2) with SMTP id uBHJlwIe008353; Sat, 17 Dec 2016 20:47:58 +0100 (CET) (envelope-from freebsd@skysmurf.nl) Received: by spectrum.skysmurf.nl (sSMTP sendmail emulation); Sat, 17 Dec 2016 20:47:58 +0100 Date: Sat, 17 Dec 2016 20:47:58 +0100 From: Alphons van Werven To: Michael Gmelin Cc: John Marino , tingox@gmail.com, FreeBSD Mailing List Subject: Re: The ports collection has some serious issues Message-ID: <20161217194758.GB7888@spectrum.skysmurf.nl> References: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> <20161217132608.GA1352@spectrum.skysmurf.nl> <54CEEF4F-3E62-45D1-902A-DA4372E9F060@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wzJLGUyc3ArbnUjN" Content-Disposition: inline In-Reply-To: <54CEEF4F-3E62-45D1-902A-DA4372E9F060@freebsd.org> X-PGP-Key: http://www.skysmurf.nl/~fonz/fonz_pubkey.asc User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2016 19:48:03 -0000 --wzJLGUyc3ArbnUjN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Michael Gmelin wrote: > Maybe you could elaborate a bit more what you find so annoying about > running "poudriere testport origin" before doing "svn commit" that you > are willing to drop port maintainership over it? Sure. In this case it's the precedent that bugs me. Needless to say, not being a committer myself, whether/that said folks are required to use Poudriere and/or Synth for their QA checking is ipso facto none of my concern. However, I'm pretty sure I know what comes next. When maintainers need to provide build/QA logs with their PRs (which I think in many cases makes perfect sense to request, BTW) soon enough Portupgrade or Portmaster logs, Portlint output, output of explicit # make check-foo && make bar-qa && make love && make install and such will cease to suffice and those logs will be going to have to be Poudriere and/or Synth logs specifically. In other words: I suspect it won't be long before port maintainership will de facto force maintainers to install, learn and use Poudriere and/or Synth. And it just so happens that for me the former in particular is a definite no go for flight. To put things into perspective, I do feel compelled to point out that this is merely the straw that broke the proverbial camel's back. Or the spark that ignited the gunpowder, if one happens to know what poudriere actually means. I've been a FreeBSD stalwart since the turn of the century (if not slightly earlier) and for the most part it has been wonderful. But ever since some time during the 9.X era I started to pick up signs that the FreeBSD project as a whole is moving into a direction that troubles me--in some cases deeply indeed. Particularly during the last few months I found myself increasingly strongly contemplating moving away from FreeBSD altogether. And that is exactly what I've now decided to do. There's nothing overly dramatic about that; it's a simple observation that too many things involving the FreeBSD project in general are going in what I consider undesirable directions, leading to the pragmatic conclusion that, the past notwithstanding, FreeBSD is unfortunately no longer the right operating system for me, neither personally nor professionally. I'll assume the above was sufficiently elaborate. Regards, Fonz --=20 A.J. "Fonz" van Werven Notice: this e-mail address wil expire on Sat 24 Dec 2016. --wzJLGUyc3ArbnUjN Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJYVZZuAAoJEAfP7gJTaCe842EP/1HwBtCrtMIr8KfQ8xXfAl/Q ljbkfgaRosH1rmADDbxY2PBk/dt30eCHev1gU/OO53PTdtjyJkjVmC8UbOqX35In o9oEc/R63QuivPfEAynhAmyY06WvLc7GcoJlNOx5BdNityRGMX1soET8a8STnmZt uDjYOotOx+JvLjsVrRVJENopl84LONpdsKTXc4HifYEL8t4UxNqghHLzVVW8Gtv6 4YPIXpgRoJn+d+GCSQUFMCM2kL1TDnm09PYKASQPMYLkeQLyNzm9qlgLVFSVr3eP kWSTA9dMUGo4KDktTr/5yXtf6+37c+9gCdGh9+r5aUnKV0K08PgNegzSoY+1poNQ RNQuxFiEK1ZdN4CYSwqATVawgP0Z5VD8i792goO3TsLKe6U25Tmuv1srP4fNypnt k+jdeZUKVv/L4iv94+ZgDpPAVjpghMOK6wVD7m7b5RXjfUxMUXrnsJ9wD+OXAz2s XIxDrjWxreI10Nz6hZP3vxFoBBAFWFXk40YwbRhWezuSQVBBKhevRmh2IPtro7ly FoSa3ndPxyrbEOiQ91tbnmj8UjG3bd+AqQlSOnirM1Hi27nOGgTihl9aztfAHykr BjQBlH1ADqmnkbl9aoaW/TWe7LJtdk1qT/H1+p46Sv2u5n4iH93KCL7E3KM/4pkb 1ykpffuoXfpNQD7fjnop =2ptc -----END PGP SIGNATURE----- --wzJLGUyc3ArbnUjN-- From owner-freebsd-ports@freebsd.org Sat Dec 17 19:54:59 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41AE3C856C8 for ; Sat, 17 Dec 2016 19:54:59 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (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 1D1051118; Sat, 17 Dec 2016 19:54:58 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id C98FB43BA1; Sat, 17 Dec 2016 13:53:47 -0600 (CST) Subject: Re: The ports collection has some serious issues To: Alphons van Werven , Michael Gmelin References: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> <20161217132608.GA1352@spectrum.skysmurf.nl> <54CEEF4F-3E62-45D1-902A-DA4372E9F060@freebsd.org> <20161217194758.GB7888@spectrum.skysmurf.nl> Cc: tingox@gmail.com, FreeBSD Mailing List Reply-To: marino@freebsd.org From: John Marino Message-ID: Date: Sat, 17 Dec 2016 13:54:56 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <20161217194758.GB7888@spectrum.skysmurf.nl> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161217-0, 12/17/2016), Outbound message X-Antivirus-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: Sat, 17 Dec 2016 19:54:59 -0000 On 12/17/2016 13:47, Alphons van Werven wrote: > Needless to say, not being a committer myself, whether/that said folks are > required to use Poudriere and/or Synth for their QA checking is ipso facto > none of my concern. However, I'm pretty sure I know what comes next. When > maintainers need to provide build/QA logs with their PRs (which I think in > many cases makes perfect sense to request, BTW) soon enough Portupgrade or > Portmaster logs, Portlint output, output of explicit > # make check-foo && make bar-qa && make love && make install > and such will cease to suffice and those logs will be going to have to be > Poudriere and/or Synth logs specifically. In other words: I suspect it > won't be long before port maintainership will de facto force maintainers > to install, learn and use Poudriere and/or Synth. And it just so happens > that for me the former in particular is a definite no go for flight. portmaster and portupgrade logs have not been sufficient in years. It is quite possible to pass building in those and fail miserably in reliable environments such as poudriere. Since they are 100% untrustworthy, no, they aren't acceptable. I mean, they are better than zero testing effort at all, but barely. > > To put things into perspective, I do feel compelled to point out that this > is merely the straw that broke the proverbial camel's back. Or the spark > that ignited the gunpowder, if one happens to know what poudriere actually > means. I've been a FreeBSD stalwart since the turn of the century (if not > slightly earlier) and for the most part it has been wonderful. But ever > since some time during the 9.X era I started to pick up signs that the > FreeBSD project as a whole is moving into a direction that troubles me--in > some cases deeply indeed. Particularly during the last few months I found > myself increasingly strongly contemplating moving away from FreeBSD > altogether. And that is exactly what I've now decided to do. > > There's nothing overly dramatic about that; it's a simple observation that > too many things involving the FreeBSD project in general are going in what > I consider undesirable directions, leading to the pragmatic conclusion > that, the past notwithstanding, FreeBSD is unfortunately no longer the > right operating system for me, neither personally nor professionally. > > I'll assume the above was sufficiently elaborate. well, sorry to see you go. Since reverting your name on that many ports is quite a bit of work, maybe you could open one final PR and provide a patch that does this? John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus From owner-freebsd-ports@freebsd.org Sat Dec 17 20:38:40 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69AF6C854B2 for ; Sat, 17 Dec 2016 20:38:40 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id CF961A35 for ; Sat, 17 Dec 2016 20:38:39 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 41351 invoked by uid 89); 17 Dec 2016 20:38:37 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@185.17.206.127) by mail.grem.de with ESMTPA; 17 Dec 2016 20:38:37 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: The ports collection has some serious issues From: Michael Gmelin X-Mailer: iPhone Mail (14C92) In-Reply-To: <20161217194758.GB7888@spectrum.skysmurf.nl> Date: Sat, 17 Dec 2016 21:38:36 +0100 Cc: tingox@gmail.com, John Marino , FreeBSD Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: <2E32E0E1-C44F-497B-9852-6E2A6E331FD8@freebsd.org> References: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> <20161217132608.GA1352@spectrum.skysmurf.nl> <54CEEF4F-3E62-45D1-902A-DA4372E9F060@freebsd.org> <20161217194758.GB7888@spectrum.skysmurf.nl> To: Alphons van Werven 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, 17 Dec 2016 20:38:40 -0000 > On 17 Dec 2016, at 20:47, Alphons van Werven wrote: >=20 > Michael Gmelin wrote: >=20 >> Maybe you could elaborate a bit more what you find so annoying about >> running "poudriere testport origin" before doing "svn commit" that you >> are willing to drop port maintainership over it? >=20 > Sure. In this case it's the precedent that bugs me. >=20 > Needless to say, not being a committer myself, whether/that said folks are= > required to use Poudriere and/or Synth for their QA checking is ipso facto= > none of my concern. However, I'm pretty sure I know what comes next. When > maintainers need to provide build/QA logs with their PRs (which I think in= > many cases makes perfect sense to request, BTW) soon enough Portupgrade or= > Portmaster logs, Portlint output, output of explicit > # make check-foo && make bar-qa && make love && make install > and such will cease to suffice and those logs will be going to have to be > Poudriere and/or Synth logs specifically. In other words: I suspect it > won't be long before port maintainership will de facto force maintainers > to install, learn and use Poudriere and/or Synth. And it just so happens > that for me the former in particular is a definite no go for flight. >=20 > To put things into perspective, I do feel compelled to point out that this= > is merely the straw that broke the proverbial camel's back. Or the spark > that ignited the gunpowder, if one happens to know what poudriere actually= > means. I've been a FreeBSD stalwart since the turn of the century (if not > slightly earlier) and for the most part it has been wonderful. But ever > since some time during the 9.X era I started to pick up signs that the > FreeBSD project as a whole is moving into a direction that troubles me--in= > some cases deeply indeed. Particularly during the last few months I found > myself increasingly strongly contemplating moving away from FreeBSD > altogether. And that is exactly what I've now decided to do. >=20 > There's nothing overly dramatic about that; it's a simple observation that= > too many things involving the FreeBSD project in general are going in what= > I consider undesirable directions, leading to the pragmatic conclusion > that, the past notwithstanding, FreeBSD is unfortunately no longer the > right operating system for me, neither personally nor professionally. >=20 > I'll assume the above was sufficiently elaborate. >=20 It was quite elaborate, but didn't really answer the question - it managed t= o explain your emotions though, maybe that was more important anyway. Attaching poudriere logs has been best practice for years now and I (using Fre= eBSD since the mid-90s) adapted quickly, as it made perfect sense to me and g= etting started with poudriere just took a couple of minutes. If anything, th= e situation got better this year, as we have a second option (synth) availab= le now. Anyway, it's sad to see you leave, thanks for all your contributions, I've b= een using some of your ports for years. -m= From owner-freebsd-ports@freebsd.org Sat Dec 17 21:08:43 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C93DCC85B4D for ; Sat, 17 Dec 2016 21:08:43 +0000 (UTC) (envelope-from la5lbtyi@aon.at) Received: from smtpout-fallback.aon.at (smtpout-fallback.aon.at [195.3.96.120]) (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 2468A17CC for ; Sat, 17 Dec 2016 21:08:42 +0000 (UTC) (envelope-from la5lbtyi@aon.at) Received: (qmail 15517 invoked from network); 17 Dec 2016 21:08:32 -0000 Received: from unknown (HELO smtpout.aon.at) ([172.18.1.199]) (envelope-sender ) by fallback44.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 17 Dec 2016 21:08:32 -0000 X-A1Mail-Track-Id: 1482008912:15516:fallback44:172.18.1.199:1 Received: (qmail 27744 invoked from network); 17 Dec 2016 21:08:25 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on WARSBL605.highway.telekom.at X-Spam-Level: Received: from 88-117-79-64.adsl.highway.telekom.at (HELO gandalf.xyzzy) ([88.117.79.64]) (envelope-sender ) by smarthub79.res.a1.net (qmail-ldap-1.03) with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP for ; 17 Dec 2016 21:08:25 -0000 X-A1Mail-Track-Id: 1482008905:27736:smarthub79:88.117.79.64:1 Received: from mizar.xyzzy (mizar.xyzzy [192.168.1.19]) by gandalf.xyzzy (8.15.2/8.15.2) with ESMTP id uBHL8PBT058221 for ; Sat, 17 Dec 2016 22:08:25 +0100 (CET) (envelope-from la5lbtyi@aon.at) To: freebsd-ports@freebsd.org From: Martin Birgmeier Subject: Dropping enigmail support from enigmail Organization: MBi at home Message-ID: <7b88cb8b-953a-a53e-b552-cb6bf6ffe27f@aon.at> Date: Sat, 17 Dec 2016 22:08:25 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2016 21:08:43 -0000 After upgrading to thunderbird-45.5.1_6 I noticed that enigmail (and lightning) support were gone from thunderbird. I tried to find a replacement package until I read the svn log message: gecko: drop ENIGMAIL, LIGHTNING to simplify updates ENIGMAIL can still return as www/xpi-enigmail but, alas, xpi-* ports and their framework are mostly unmaintained. So this means that after a simple PORTREVISION change I cannot send, receive, or reread encrypted mails any more. I think a decision to remove such an essential component should not be taken so lightly, especially when the actual port version (45.5.1) has not even changed. What is being planned to remedy this unfortunate situation? -- Martin From owner-freebsd-ports@freebsd.org Sat Dec 17 22:09:15 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5F36C85C5C for ; Sat, 17 Dec 2016 22:09:15 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (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 AB2A4180F; Sat, 17 Dec 2016 22:09:15 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 084BC66E8; Sat, 17 Dec 2016 22:09:15 +0000 (UTC) To: freebsd-ports@freebsd.org, la5lbtyi@aon.at Subject: Re: Dropping enigmail support from enigmail In-Reply-To: <7b88cb8b-953a-a53e-b552-cb6bf6ffe27f@aon.at> Message-Id: <20161217220915.084BC66E8@freefall.freebsd.org> Date: Sat, 17 Dec 2016 22:09:15 +0000 (UTC) From: jbeich@freebsd.org (Jan Beich) 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, 17 Dec 2016 22:09:15 -0000 Martin Birgmeier writes: > After upgrading to thunderbird-45.5.1_6 I noticed that enigmail (and > lightning) support were gone from thunderbird. I tried to find a > replacement package until I read the svn log message: Lightning had 2 copies, only one of those was removed. For Enigmail see /usr/ports/UPDATING from 20161216. > I think a decision to remove such an essential component should not be > taken so lightly, especially when the actual port version (45.5.1) has > not even changed. Why the version should change? Enigmail isn't part of Thunderbird distribution but just one of third-party extensions you can find on addons.mozilla.org. For historic reasons it was bundled with the port but the requirment is gone. ENIGMAIL option was unmaintained beyond updates which were irregular. And it was bound to get in the way if anyone attempted to refactor the current maintenance nightmare gecko@ is in. From owner-freebsd-ports@freebsd.org Sat Dec 17 23:16:11 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8FD3BC85F9D for ; Sat, 17 Dec 2016 23:16:11 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from mail.skysmurf.nl (spectrum.skysmurf.nl [83.162.175.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.skysmurf.nl", Issuer "mail.skysmurf.nl" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 25DA81B07; Sat, 17 Dec 2016 23:16:10 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from spectrum.skysmurf.nl (mail.skysmurf.nl [192.168.42.4]) by mail.skysmurf.nl (8.15.2/8.15.2) with SMTP id uBHNG7YM074375; Sun, 18 Dec 2016 00:16:07 +0100 (CET) (envelope-from freebsd@skysmurf.nl) Received: by spectrum.skysmurf.nl (sSMTP sendmail emulation); Sun, 18 Dec 2016 00:16:07 +0100 Date: Sun, 18 Dec 2016 00:16:07 +0100 From: Alphons van Werven To: marino@freebsd.org Cc: Michael Gmelin , tingox@gmail.com, FreeBSD Mailing List Subject: Re: The ports collection has some serious issues Message-ID: <20161217231607.GA74355@spectrum.skysmurf.nl> References: <192c99ca-ed3b-44da-633a-99629fdcea70@marino.st> <20161217132608.GA1352@spectrum.skysmurf.nl> <54CEEF4F-3E62-45D1-902A-DA4372E9F060@freebsd.org> <20161217194758.GB7888@spectrum.skysmurf.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.skysmurf.nl/~fonz/fonz_pubkey.asc User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2016 23:16:11 -0000 --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable John Marino wrote: > maybe you could open one final PR and provide a patch that does this? Fair enough, will do. Fonz --=20 A.J. "Fonz" van Werven Notice: this e-mail address wil expire on Sat 24 Dec 2016. --n8g4imXOkfNTN/H1 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJYVcc3AAoJEAfP7gJTaCe8XUIP/jy2MQ6odfaxyqwku957nwon BichATw0BfjwNvA9IEIxNcEyoiQPhjD9bMi9G08vjL9Ng5Ooc8I/nqPFYAza8EJc GSQiemNMmseWI/GSoWOiPXmpDvY+dZjnP0o2DPNw1gCyAPsMWZejs6infZ49T0T8 uEekzzq7JyA1Wpl27ygE5fEJB7A5cAw4MKwVyElkW1X9Kr/iDQFOXQlO0wqOFxLI yPam90OxhXw87vK474eHn6dX29U3cvoWbss80DbB9C/H4XkaeN/TOZ/U1TM5haxs 0EwB9c8g2Bb41Np+T+tgJhiAxDU0u6U0BCmDGVeu35/8ecF4JOc6qgIv+9T29xe+ fQZszwM+WJ4D0Z7nq+IJJT7BXUEy4RgdyCapHYaiabHIJe7BsES5kNwrHD7s3ta+ 2iMIk6BoHSkyYNfsIfzrMGx6uTfmaBoZNnsKLMx7hrkCmt2bnvOTGqLDmt+QgMmX Btd5X65k3Z5bE1wajuy8dw8cKhQMR7+4GyC4/6Zl8kNuybu0m24tU4Q+e6Xd72pO NqeXqohgz1XRGctwqup0KLjBhlkvQI25L0ousMNxWMMm8VOogi4lR0Zo3atI6OXl utcqGPLTNTxzenNxw5qEWluqk2Je1mrWIZ/GW6dDSQEB5LthRe6DNMvc0i2RPfqR oC9KtYB4GvFbHM4yOFIp =cedY -----END PGP SIGNATURE----- --n8g4imXOkfNTN/H1--