From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 00:01:12 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 347251065697; Sun, 28 Aug 2011 00:01:12 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 61FC11501D6; Sun, 28 Aug 2011 00:00:07 +0000 (UTC) Message-ID: <4E598506.2030507@FreeBSD.org> Date: Sat, 27 Aug 2011 17:00:06 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0 MIME-Version: 1.0 To: urb@twe.net References: <4E57FBC1.1020009@FreeBSD.org> <4E580082.1030202@FreeBSD.org> <4E59324E.5070602@twe.net> <4E595C14.9030503@FreeBSD.org> <4E597167.8030403@twe.net> In-Reply-To: <4E597167.8030403@twe.net> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: mnag@FreeBSD.org, freebsd-ports@freebsd.org Subject: Re: mail/postfix-policyd-spf relies on vulnerable mail/libspf2-10 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 00:01:12 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 08/27/2011 15:36, Uffe R. B. Andersen wrote: > Den 27-08-2011 23:05, Doug Barton skrev: >>> libspf2 port is currently libspf2-1.2.9_1 and according to the >>> page you refer to, the vulnerability affects libspf2 <1.2.8. > >> Yes, that was my point. :) mail/libspf2-10 and mail/libspf2 are >> different ports. mail/postfix-policyd-spf currently relies on the >> former, it needs to be fixed to work with the latter instead. > > Sorry for missing that point, but as mail/libspf2-10 and mail/libspf2 > are different ports, why should vulnerabilities listed for only one of > them apply for both? I appreciate your responses, but I think you're missing one or more large'ish pieces of the puzzle. Here is what I'm seeing with an up to date portaudit db: portaudit -a Affected package: libspf2-1.0.4_1 Type of problem: libspf2 -- Buffer overflow. Reference: http://portaudit.FreeBSD.org/2ddbfd29-a455-11dd-a55e-00163e000016.html pkg_info -qo libspf2-1.0.4_1 mail/libspf2-10 pkg_info -R libspf2-1.0.4_1 Information for libspf2-1.0.4_1: Required by: postfix-policyd-spf-1.0.1_3 cd /usr/ports/mail/libspf2-10/ make -V PKGNAME libspf2-1.0.4_1 The solution here is that postfix-policyd-spf needs to be updated to not rely on a vulnerable version of libspf2. Doug - -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAEBCAAGBQJOWYUGAAoJEFzGhvEaGryEnUAIAKf/lui9bgcm8tW/uFFoJcJm 3zjIRL5rdlCOX3T6pRurGMHI49sQRFEKPc/npEPq2UYTmnt9wYYB2Yv4l/OVz/WA N5qjldk4ciT9oFdYRFC6zEQzPjnDh0C4zmiJs6jrNxo9PZt+2ghuDIB0vpkmHbAv zvLfn8Gqy/LZY+mae/5xTfnUxPWHE87TmoajPjIwNMn2qWD8lA0RhxjjHeTBH9al lBM350BsOFhAo+SLeQ20+tycngi0PjF9SbrsTCTdMvNocB5PvisGadE4eGcJ46PT lu4Tnxh5U3dbC/qNfsug02v6pofKiiwtIJjcok40pKrVJNR79+VxjjoitzODlsY= =8sLS -----END PGP SIGNATURE----- From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 02:08:45 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B85B106566C; Sun, 28 Aug 2011 02:08:45 +0000 (UTC) (envelope-from kubito@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id ABE988FC15; Sun, 28 Aug 2011 02:08:44 +0000 (UTC) Received: by gxk28 with SMTP id 28so4722460gxk.13 for ; Sat, 27 Aug 2011 19:08:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=9+m+Gt63O1rE00ISI1h8OjuJPA2QxfaKNMq6yXb3DaM=; b=qe0/lF5fF1+QQyKmonyczhntp4G+Ua0kLp1RBYngdoCqtiF0R+AcYwr/zaCNhQdrPP soGql7nVpsFD0nsirq15547NXPWiw474+Xv28KeFxskSk2e3pxTGRlVqbbOfsGceu9l/ M2SFuJqzpXPKpMjbMPR9j4ab6eIZNHrBJXSIY= Received: by 10.236.116.33 with SMTP id f21mr16012470yhh.45.1314495959097; Sat, 27 Aug 2011 18:45:59 -0700 (PDT) Received: from gibbon.gmail.com ([189.61.193.250]) by mx.google.com with ESMTPS id q25sm3691589yhm.6.2011.08.27.18.45.56 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 27 Aug 2011 18:45:57 -0700 (PDT) Sender: Raphael Kubo da Costa From: Raphael Kubo da Costa To: Rene Ladan References: <4C040F4F.1010709@freebsd.org> Date: Sat, 27 Aug 2011 22:45:49 -0300 In-Reply-To: <4C040F4F.1010709@freebsd.org> (Rene Ladan's message of "Mon, 31 May 2010 21:34:39 +0200") Message-ID: <87y5yeb96a.fsf@FreeBSD.org> User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: kde-freebsd@kde.org, freebsd ports Subject: Re: [kde-freebsd] devel/cmake bug: "-pthread; -D_THREAD_SAFE" emitted instead of "-pthread -D_THREAD_SAFE" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 02:08:45 -0000 Rene Ladan writes: > somehow devel/cmake outputs "-pthread;-D_THREAD_SAFE" instead of > "-pthread -D_THREAD_SAFE" to the generated Makefiles (note the semicolon). > > This means some list is passed verbatim to the compiler, causing the > shell to execute the wrong commands. I have looked into the source code > but there seems to be no relevant mention of "-D_THREAD_SAFE", nor in > /usr/include or /usr/local/include. > > A workaround of course is to patch the generated Makefiles, but it would > be nicer to fix the real problem (which does not seem to exist on most > Linux distributions). > > I'm using cmake 2.8.1, but it also happens with earlier versions. > > I don't have a testcase yet, sorry. Hey there, Do you still experience this one? From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 02:28:10 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 509F8106566C for ; Sun, 28 Aug 2011 02:28:10 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id DE0078FC12 for ; Sun, 28 Aug 2011 02:28:09 +0000 (UTC) Received: by wyh15 with SMTP id 15so4066046wyh.13 for ; Sat, 27 Aug 2011 19:28:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tP/i0SfAu5u/jJdul3mcU2UivpuBGFjEQSGvpjiN3ZI=; b=lWf+o3aNQlNDCSCA9YBmFLG1Nkvf67PhSk8ZRzuRzMftngOvTdciKPSwiIClnjZUCh zbbmbdqCrkETysLlS+Mm3Z0eY+PRJ/LYUYfaHTfN2v4S4EtMRxYzscV7qF7CMjudWGYm eMDKhXH1qS4SRQA1lxIBMzfR5jkEwOs5d3mHQ= MIME-Version: 1.0 Received: by 10.216.88.212 with SMTP id a62mr2407321wef.43.1314498488738; Sat, 27 Aug 2011 19:28:08 -0700 (PDT) Received: by 10.216.208.158 with HTTP; Sat, 27 Aug 2011 19:28:08 -0700 (PDT) In-Reply-To: <20110807211700.20043883@fabiankeil.de> References: <4E3EE2CB.6050704@protected-networks.net> <20110807211700.20043883@fabiankeil.de> Date: Sat, 27 Aug 2011 21:28:08 -0500 Message-ID: From: Brandon Gooch To: Fabian Keil Content-Type: text/plain; charset=ISO-8859-1 Cc: ports@freebsd.org, Michael Butler , amistry@am-productions.biz Subject: Re: fusefs-kmod on recent -current X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 02:28:10 -0000 On Sun, Aug 7, 2011 at 2:17 PM, Fabian Keil wrote: > Michael Butler wrote: > >> Seems that the change to the mount flags in recent -current has broken >> the compilation of sysutils/fusefs-kmod :-( >> >> It now needs something like the attached to compile, > > The attachment didn't make it. Anyway, there's already a PR about it: > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/159322 > > Fabian > There are several patches actually: http://www.freebsd.org/cgi/query-pr-summary.cgi?category=&severity=&priority=&class=&state=&sort=none&text=fusefs-kmod&responsible=&multitext=&originator=&release= An appropriate one should be chosen that contains a check for the FreeBSD version. Getting the appropriate one committed seems to be the issue. Has anyone heard from this amistry@am-productions.biz? Can we get a manual override here? Main point of this simple-to-fix issue is that as 9.0-RELEASE approaches, having a broken fusefs-kmod is just bad news for a lot of users -- and it looks bad for FreeBSD too. -Brandon From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 04:06:17 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0EB9106564A for ; Sun, 28 Aug 2011 04:06:17 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id B6AA98FC08 for ; Sun, 28 Aug 2011 04:06:17 +0000 (UTC) Received: by gxk28 with SMTP id 28so4763905gxk.13 for ; Sat, 27 Aug 2011 21:06:16 -0700 (PDT) Received: by 10.142.139.19 with SMTP id m19mr1628235wfd.108.1314504347090; Sat, 27 Aug 2011 21:05:47 -0700 (PDT) Received: from osiris.chen.org.nz (118-93-186-168.dsl.dyn.ihug.co.nz. [118.93.186.168]) by mx.google.com with ESMTPS id y5sm10696160pbq.12.2011.08.27.21.05.44 (version=SSLv3 cipher=OTHER); Sat, 27 Aug 2011 21:05:45 -0700 (PDT) Message-ID: <4E59BE96.7050204@chen.org.nz> Date: Sun, 28 Aug 2011 16:05:42 +1200 From: Jonathan Chen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4E59BC38.9060809@chen.org.nz> In-Reply-To: <4E59BC38.9060809@chen.org.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Missing libproxy.la? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 04:06:18 -0000 Hi, On 28/08/2011 15:55, Jonathan Chen wrote: > Hi all, > > I read UPDATING and did a: > # portupgrade -rf libnotify-0.\* libproxy-0.\* > > and this mostly succeeded except where it failed. In particular > x11/gnome-panel complains: > CCLD clock-applet > gnome-libtool: link: cannot find the library > `/usr/local/lib/libproxy.la' or unhandled argument > `/usr/local/lib/libproxy.la' > > This leaves me with a slightly unusable system. Reinstalling libproxy > still does not resolve the problem. How can I make this work again? So, after reading the problems that other people had been having, I took a punt and resintalled libgweather, and this corrected my build. This one's for the archives. Cheers. -- Jonathan Chen ---------------------------------------------------------------------- "A little learning is a dangerous thing but a lot of ignorance is just as bad." - Bob Edwards From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 04:26:49 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0361D106564A for ; Sun, 28 Aug 2011 04:26:49 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by mx1.freebsd.org (Postfix) with ESMTP id D85588FC12 for ; Sun, 28 Aug 2011 04:26:48 +0000 (UTC) Received: by pzk33 with SMTP id 33so15315882pzk.18 for ; Sat, 27 Aug 2011 21:26:48 -0700 (PDT) Received: by 10.142.234.11 with SMTP id g11mr1621953wfh.304.1314503740825; Sat, 27 Aug 2011 20:55:40 -0700 (PDT) Received: from osiris.chen.org.nz (118-93-186-168.dsl.dyn.ihug.co.nz. [118.93.186.168]) by mx.google.com with ESMTPS id x6sm10682677pba.5.2011.08.27.20.55.38 (version=SSLv3 cipher=OTHER); Sat, 27 Aug 2011 20:55:39 -0700 (PDT) Message-ID: <4E59BC38.9060809@chen.org.nz> Date: Sun, 28 Aug 2011 15:55:36 +1200 From: Jonathan Chen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Missing libproxy.la? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 04:26:49 -0000 Hi all, I read UPDATING and did a: # portupgrade -rf libnotify-0.\* libproxy-0.\* and this mostly succeeded except where it failed. In particular x11/gnome-panel complains: CCLD clock-applet gnome-libtool: link: cannot find the library `/usr/local/lib/libproxy.la' or unhandled argument `/usr/local/lib/libproxy.la' This leaves me with a slightly unusable system. Reinstalling libproxy still does not resolve the problem. How can I make this work again? Cheers. -- Jonathan Chen ---------------------------------------------------------------------- char *p="char *p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);} From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 06:11:22 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D1B1106564A for ; Sun, 28 Aug 2011 06:11:22 +0000 (UTC) (envelope-from 2igosha@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0C2658FC16 for ; Sun, 28 Aug 2011 06:11:21 +0000 (UTC) Received: by bkat8 with SMTP id t8so4649977bka.13 for ; Sat, 27 Aug 2011 23:11:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=AZV2xvBCNnE8B+WG1nfWDg+r00N4uZJr6dX9ZPm1/Ds=; b=OMedgTOMY8XSlCfitMlBVzxkAcdiGvM/w7YyREjdYMyW1k6N+gErmkfoISgGNqxq68 McfKrXA/fVEZD6ILp/sHDt8uFvNzczF+kVbtT/MUCNEF6IsmF5RqJkRsLAmeULdHQy9n HEPyqPBnKYTBw6CSkVJjXGKh10axVMxeAiuOk= Received: by 10.204.132.212 with SMTP id c20mr1400236bkt.352.1314511880990; Sat, 27 Aug 2011 23:11:20 -0700 (PDT) Received: from [192.168.1.3] ([91.79.151.133]) by mx.google.com with ESMTPS id j17sm867700bks.46.2011.08.27.23.11.19 (version=SSLv3 cipher=OTHER); Sat, 27 Aug 2011 23:11:20 -0700 (PDT) Message-ID: <4E59DC06.3000405@soumenkov.com> Date: Sun, 28 Aug 2011 10:11:18 +0400 From: Igor Soumenkov <2igosha@gmail.com> User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110416 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4E58A6AA.4060805@soumenkov.com> <4E58F04F.7030008@cassiba.com> <4E58F3B4.8060706@soumenkov.com> <4E592A74.8020605@soumenkov.com> <4E593F71.1000401@soumenkov.com> <878vqecwnz.fsf@FreeBSD.org> In-Reply-To: <878vqecwnz.fsf@FreeBSD.org> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Subject: Re: How to escalate? ports/159276 - cmake X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 06:11:22 -0000 On 28.08.2011 02:33, Raphael Kubo da Costa wrote: > Igor Soumenkov <2igosha@gmail.com> writes: > >> The same effect can be achieved by specifying >> CMAKE_C(XX)_FLAGS_{RELEASE,DEBUG} in command line. >> So, I suggest removing the patch from >> ports/devel/cmake/files/patch-Modules_Compiler_GNU.cmake and patching >> ports/Mk/bsd.cmake.mk instead (attached). After applying this patch >> system C(XX)FLAGS will be propagated for Release and Debug build >> configurations. >> >> [...] >> >> --- ports/Mk/bsd.cmake.mk.original 2011-08-27 21:47:00.000000000 +0400 >> +++ ports/Mk/bsd.cmake.mk 2011-08-27 22:43:46.000000000 +0400 >> @@ -53,7 +53,11 @@ >> CMAKE_ARGS+= -DCMAKE_C_COMPILER:STRING="${CC}" \ >> -DCMAKE_CXX_COMPILER:STRING="${CXX}" \ >> -DCMAKE_C_FLAGS:STRING="${CFLAGS}" \ >> + -DCMAKE_C_FLAGS_DEBUG:STRING="${CFLAGS}" \ >> + -DCMAKE_C_FLAGS_RELEASE:STRING="${CFLAGS}" \ >> -DCMAKE_CXX_FLAGS:STRING="${CXXFLAGS}" \ >> + -DCMAKE_CXX_FLAGS_DEBUG:STRING="${CXXFLAGS}" \ >> + -DCMAKE_CXX_FLAGS_RELEASE:STRING="${CXXFLAGS}" \ >> -DCMAKE_INSTALL_PREFIX:PATH="${CMAKE_INSTALL_PREFIX}" \ >> -DCMAKE_BUILD_TYPE:STRING="${CMAKE_BUILD_TYPE}" \ >> -DTHREADS_HAVE_PTHREAD_ARG:BOOL=YES > At first sight, the patch looks OK to me and solves the problem in a > cleaner way. > > You could try submitting this patch to ports/159276. It might require an > exp-run, but I think it could get in. Submitted the patch. From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 08:54:13 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1EF371065670 for ; Sun, 28 Aug 2011 08:54:13 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id D597E8FC08 for ; Sun, 28 Aug 2011 08:54:12 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1Qxb87-000NKp-Tm for freebsd-ports@freebsd.org; Sun, 28 Aug 2011 10:54:11 +0200 Date: Sun, 28 Aug 2011 10:54:11 +0200 From: Kurt Jaeger To: freebsd-ports@freebsd.org Message-ID: <20110828085411.GC28186@home.opsec.eu> References: <4E59BC38.9060809@chen.org.nz> <4E59BE96.7050204@chen.org.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E59BE96.7050204@chen.org.nz> Subject: evolution problem even after libgweather (was Re: Missing libproxy.la?) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 08:54:13 -0000 On 28/08/2011 Jonathan Chen wrote: > > and this mostly succeeded except where it failed. In particular > > x11/gnome-panel complains: > > CCLD clock-applet > > gnome-libtool: link: cannot find the library > > `/usr/local/lib/libproxy.la' or unhandled argument > > `/usr/local/lib/libproxy.la' > > > > This leaves me with a slightly unusable system. Reinstalling libproxy > > still does not resolve the problem. How can I make this work again? > > So, after reading the problems that other people had been having, I took > a punt and resintalled libgweather, and this corrected my build. This > one's for the archives. I still have a similar problem, but with evolution, even after I reinstalled libgweather. Any ideas ? -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 09:06:17 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 228E01065673 for ; Sun, 28 Aug 2011 09:06:17 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by mx1.freebsd.org (Postfix) with ESMTP id D713B8FC14 for ; Sun, 28 Aug 2011 09:06:16 +0000 (UTC) Received: from p57918f02.dip.t-dialin.net ([87.145.143.2] helo=krabat.raven.hur) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1QxbJf-00058R-Sd; Sun, 28 Aug 2011 11:06:08 +0200 Message-ID: <4E5A04FC.1070503@gwdg.de> Date: Sun, 28 Aug 2011 11:06:04 +0200 From: Rainer Hurling User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110825 Thunderbird/6.0 MIME-Version: 1.0 To: Kurt Jaeger References: <4E59BC38.9060809@chen.org.nz> <4E59BE96.7050204@chen.org.nz> <20110828085411.GC28186@home.opsec.eu> In-Reply-To: <20110828085411.GC28186@home.opsec.eu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: freebsd-ports@freebsd.org Subject: Re: evolution problem even after libgweather (was Re: Missing libproxy.la?) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 09:06:17 -0000 On 28.08.2011 10:54 (UTC+1), Kurt Jaeger wrote: > On 28/08/2011 Jonathan Chen wrote: > >>> and this mostly succeeded except where it failed. In particular >>> x11/gnome-panel complains: >>> CCLD clock-applet >>> gnome-libtool: link: cannot find the library >>> `/usr/local/lib/libproxy.la' or unhandled argument >>> `/usr/local/lib/libproxy.la' >>> >>> This leaves me with a slightly unusable system. Reinstalling libproxy >>> still does not resolve the problem. How can I make this work again? >> >> So, after reading the problems that other people had been having, I took >> a punt and resintalled libgweather, and this corrected my build. This >> one's for the archives. > > I still have a similar problem, but with evolution, even > after I reinstalled libgweather. > > Any ideas ? I had to reinstall libgweather, libgdata and evolution-data-server before I was able to continue. Hope this helps, Rainer From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 09:25:21 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0ECB9106566B for ; Sun, 28 Aug 2011 09:25:21 +0000 (UTC) (envelope-from freebsd-ports@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id BC0A18FC15 for ; Sun, 28 Aug 2011 09:25:20 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QxbcF-0007T8-5U for freebsd-ports@freebsd.org; Sun, 28 Aug 2011 11:25:19 +0200 Received: from g231134222.adsl.alicedsl.de ([92.231.134.222]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 28 Aug 2011 11:25:19 +0200 Received: from rotkap by g231134222.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 28 Aug 2011 11:25:19 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-ports@freebsd.org From: Heino Tiedemann Date: Sun, 28 Aug 2011 11:16:10 +0200 Organization: yes Lines: 25 Message-ID: References: <4E560ACC.4080407@FreeBSD.org> <4E560D94.90902@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: g231134222.adsl.alicedsl.de User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (berkeley-unix) X-Face: v6Lci{Mw=kwHf$`7C?L-U#BHn7O\wqF-1qg#Vk%}nUQv\i^mM/.p=wU+cr)yXf#Ob+foOOxW; ir"QI!|25wG3`ywF)yh~@V.kKtr.qp+v.R; w?c@ZzM#!'/7r_+)$NjMN:]qo-]`&z~KlP}|cERO'%s9":6\ZnN/O List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 09:25:21 -0000 Matthias Andree wrote: > Oh I see Dirk has just fixed this at 08:51 UTC. Thanks, that was quick! Fixed? I cannot update my cups ports: cups-base-1.4.6_5 < needs updating (port has 1.4.8) cups-client-1.4.6 < needs updating (port has 1.4.8) cups-image-1.4.6 < needs updating (port has 1.4.8) ** Listing the failed packages (-:ignored / *:skipped / !:failed) - print/cups-base (marked as IGNORE) - print/cups-client (marked as IGNORE) - print/cups-image (marked as IGNORE) Do I have do to something that these problem diasapear? Heino From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 10:30:30 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 507F2106566B for ; Sun, 28 Aug 2011 10:30:30 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by mx1.freebsd.org (Postfix) with ESMTP id 12B568FC0A for ; Sun, 28 Aug 2011 10:30:29 +0000 (UTC) Received: from p57918f02.dip.t-dialin.net ([87.145.143.2] helo=krabat.raven.hur) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1QxcdH-000839-M4; Sun, 28 Aug 2011 12:30:27 +0200 Message-ID: <4E5A18C3.9090105@gwdg.de> Date: Sun, 28 Aug 2011 12:30:27 +0200 From: Rainer Hurling User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110825 Thunderbird/6.0 MIME-Version: 1.0 To: rotkap@gmx.de References: <4E560ACC.4080407@FreeBSD.org> <4E560D94.90902@gmx.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: Heino Tiedemann , freebsd-ports@freebsd.org Subject: Re: print/cups-* ports vs. GNUTLS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 10:30:30 -0000 On 28.08.2011 11:16 (UTC+1), Heino Tiedemann wrote: > Matthias Andree wrote: > >> Oh I see Dirk has just fixed this at 08:51 UTC. Thanks, that was quick! > > Fixed? > > I cannot update my cups ports: > > cups-base-1.4.6_5< needs updating (port has 1.4.8) > cups-client-1.4.6< needs updating (port has 1.4.8) > cups-image-1.4.6< needs updating (port has 1.4.8) > > > > ** Listing the failed packages (-:ignored / *:skipped / !:failed) > - print/cups-base (marked as IGNORE) > - print/cups-client (marked as IGNORE) > - print/cups-image (marked as IGNORE) > > > > Do I have do to something that these problem diasapear? This was discussed before on this list and on the forum. It should be sufficient to remove the GNUTLS option for the three mentioned ports. You can use 'make rmconfig' or 'make config' for this. > Heino Hope this helps, Rainer From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 10:36:06 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A4D0106564A for ; Sun, 28 Aug 2011 10:36:06 +0000 (UTC) (envelope-from urb@twe.net) Received: from xerox.twe.net (0107ds2-ba.0.fullrate.dk [90.184.98.110]) by mx1.freebsd.org (Postfix) with ESMTP id A2C4E8FC12 for ; Sun, 28 Aug 2011 10:36:05 +0000 (UTC) Received: from xerox.twe.net (localhost [127.0.0.1]) by xerox.twe.net (Postfix) with ESMTP id 97A1B6D431 for ; Sun, 28 Aug 2011 12:36:02 +0200 (CEST) X-Virus-Scanned: amavisd-new at twe.net Received: from xerox.twe.net ([127.0.0.1]) by xerox.twe.net (xerox.twe.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id agrQ_AiURzNh for ; Sun, 28 Aug 2011 12:35:45 +0200 (CEST) Received: from [192.168.21.3] (eddie.internt.twe.net [192.168.21.3]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by xerox.twe.net (Postfix) with ESMTPSA id E09336D429 for ; Sun, 28 Aug 2011 12:35:44 +0200 (CEST) Message-ID: <4E5A19F4.1050406@twe.net> Date: Sun, 28 Aug 2011 12:35:32 +0200 From: "Uffe R. B. Andersen" Organization: Andersen|nu User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4E57FBC1.1020009@FreeBSD.org> <4E580082.1030202@FreeBSD.org> <4E59324E.5070602@twe.net> <4E595C14.9030503@FreeBSD.org> <4E597167.8030403@twe.net> <4E598506.2030507@FreeBSD.org> In-Reply-To: <4E598506.2030507@FreeBSD.org> X-Enigmail-Version: 1.3.1 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: mail/postfix-policyd-spf relies on vulnerable mail/libspf2-10 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: urb@twe.net List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 10:36:06 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Den 28-08-2011 02:00, Doug Barton skrev: > I appreciate your responses, but I think you're missing one or > more large'ish pieces of the puzzle. Here is what I'm seeing with > an up to date portaudit db: > > portaudit -a Affected package: libspf2-1.0.4_1 Type of problem: > libspf2 -- Buffer overflow. Reference: > http://portaudit.FreeBSD.org/2ddbfd29-a455-11dd-a55e-00163e000016.html > > pkg_info -qo libspf2-1.0.4_1 mail/libspf2-10 > > pkg_info -R libspf2-1.0.4_1 Information for libspf2-1.0.4_1: > > Required by: postfix-policyd-spf-1.0.1_3 > > cd /usr/ports/mail/libspf2-10/ make -V PKGNAME libspf2-1.0.4_1 > > > The solution here is that postfix-policyd-spf needs to be updated > to not rely on a vulnerable version of libspf2. Indeed you're right. Googling the issue reveal that postfix-policyd-spf apparently is rather unmaintained and people suggest using the perl or python versions instead. I do remember having this issue myself, some 2 years ago and nothing seems to have happened since then. The Google result also show, that postfix-policyd-spf doesn't compile with newer versions of libspf2. Perhaps we should ask to have postfix-policyd-spf removed from the ports tree altogether? - -- Med venlig hilsen - Sincerely Uffe R. B. Andersen - mailto:urb@twe.net http://blog.andersen.nu/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (MingW32) iEYEARECAAYFAk5aGfQACgkQxC95nUQcrpibUwCfUT5KUxfE/0Q+5AC5WKSDD4xY IbIAoOPIJhDRXtr7OdQR008uUWVObd74 =6qj0 -----END PGP SIGNATURE----- From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 10:44:50 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D6BE1065672; Sun, 28 Aug 2011 10:44:50 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id B19508FC08; Sun, 28 Aug 2011 10:44:49 +0000 (UTC) Received: by gxk28 with SMTP id 28so4900616gxk.13 for ; Sun, 28 Aug 2011 03:44:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=QJGwQBePW6CSK8FAbgPYm5yr1kH2wV1jIjfqXArQTrk=; b=eLs0FHxMPV8aaulk01AWIv9Gp3DFY6o4Irxp/kYefnjvtrWnozRl6jiUHdGcbX5wmh a5ms2X7I+m/5bb2o6ndn0fLpJZp1inYuDZ8wJxIwDu0vE85bYHA3SYr+dVhtXn9IbE7s cQNovF0NBucKA5IOo2YIkZSPXwCcJcXxJmScY= Received: by 10.231.56.75 with SMTP id x11mr7373541ibg.98.1314528288043; Sun, 28 Aug 2011 03:44:48 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.42.4 with HTTP; Sun, 28 Aug 2011 03:44:18 -0700 (PDT) In-Reply-To: <4E5A19F4.1050406@twe.net> References: <4E57FBC1.1020009@FreeBSD.org> <4E580082.1030202@FreeBSD.org> <4E59324E.5070602@twe.net> <4E595C14.9030503@FreeBSD.org> <4E597167.8030403@twe.net> <4E598506.2030507@FreeBSD.org> <4E5A19F4.1050406@twe.net> From: Chris Rees Date: Sun, 28 Aug 2011 11:44:18 +0100 X-Google-Sender-Auth: 2Y_urw7oLHsWctd8-5sYsqxyv5A Message-ID: To: urb@twe.net, mnag@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ports@freebsd.org Subject: Re: mail/postfix-policyd-spf relies on vulnerable mail/libspf2-10 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 10:44:50 -0000 On 28 August 2011 11:35, Uffe R. B. Andersen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Den 28-08-2011 02:00, Doug Barton skrev: >> I appreciate your responses, but I think you're missing one or >> more large'ish pieces of the puzzle. Here is what I'm seeing with >> an up to date portaudit db: >> >> portaudit -a Affected package: libspf2-1.0.4_1 Type of problem: >> libspf2 -- Buffer overflow. Reference: >> http://portaudit.FreeBSD.org/2ddbfd29-a455-11dd-a55e-00163e000016.html >> >> =A0pkg_info -qo libspf2-1.0.4_1 mail/libspf2-10 >> >> pkg_info -R libspf2-1.0.4_1 Information for libspf2-1.0.4_1: >> >> Required by: postfix-policyd-spf-1.0.1_3 >> >> cd /usr/ports/mail/libspf2-10/ make -V PKGNAME libspf2-1.0.4_1 >> >> >> The solution here is that postfix-policyd-spf needs to be updated >> to not rely on a vulnerable version of libspf2. > > Indeed you're right. Googling the issue reveal that > postfix-policyd-spf apparently is rather unmaintained and people > suggest using the perl or python versions instead. I do remember > having this issue myself, some 2 years ago and nothing seems to have > happened since then. The Google result also show, that > postfix-policyd-spf doesn't compile with newer versions of libspf2. > > Perhaps we should ask to have postfix-policyd-spf removed from the > ports tree altogether? Hm, perhaps: FORBIDDEN=3D depends on forbidden software (libspf2) DEPRECATED=3D dead upstream, depends on forbidden software (libspf2) EXPIRATION_DATE=3D 2011-10-28 Maintainer added back to the CC list. Chris From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 10:49:04 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97D12106566C; Sun, 28 Aug 2011 10:49:04 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by mx1.freebsd.org (Postfix) with ESMTP id 379748FC08; Sun, 28 Aug 2011 10:49:04 +0000 (UTC) Received: by pzk33 with SMTP id 33so15985349pzk.18 for ; Sun, 28 Aug 2011 03:49:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=go/ppjGSu0Pldr5wpvxFdqI4uDuYVdl7IjE2WHY8tRo=; b=g0DY3J7CBat8MbhxyHfY/VjGnmLqhM1sFVASLibm4OG7QSR+QIf4fkuD2/5gyBYVVu e4q2PwSu4rLTtcmtuxuH4XdPGTwE1Us2kZLvmBzoyYylqGrGD2EPyFJxymEp+vkk7MKG CO4xZng5iu0pmCzaFuYf+5dyRgcDOkpsXhNdc= MIME-Version: 1.0 Received: by 10.142.209.1 with SMTP id h1mr1732676wfg.300.1314528543987; Sun, 28 Aug 2011 03:49:03 -0700 (PDT) Sender: r.c.ladan@gmail.com Received: by 10.142.48.9 with HTTP; Sun, 28 Aug 2011 03:49:03 -0700 (PDT) In-Reply-To: <87y5yeb96a.fsf@FreeBSD.org> References: <4C040F4F.1010709@freebsd.org> <87y5yeb96a.fsf@FreeBSD.org> Date: Sun, 28 Aug 2011 12:49:03 +0200 X-Google-Sender-Auth: h-Jf1Jz-bTUpvNW10_UEW99-pZ0 Message-ID: From: =?ISO-8859-1?Q?Ren=E9_Ladan?= To: Raphael Kubo da Costa Content-Type: text/plain; charset=ISO-8859-1 Cc: kde-freebsd@kde.org, freebsd ports Subject: Re: [kde-freebsd] devel/cmake bug: "-pthread; -D_THREAD_SAFE" emitted instead of "-pthread -D_THREAD_SAFE" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 10:49:04 -0000 2011/8/28 Raphael Kubo da Costa : > Rene Ladan writes: > >> somehow devel/cmake outputs "-pthread;-D_THREAD_SAFE" instead of >> "-pthread -D_THREAD_SAFE" to the generated Makefiles (note the semicolon). >> >> This means some list is passed verbatim to the compiler, causing the >> shell to execute the wrong commands. I have looked into the source code >> but there seems to be no relevant mention of "-D_THREAD_SAFE", nor in >> /usr/include or /usr/local/include. >> >> A workaround of course is to patch the generated Makefiles, but it would >> be nicer to fix the real problem (which does not seem to exist on most >> Linux distributions). >> >> I'm using cmake 2.8.1, but it also happens with earlier versions. >> >> I don't have a testcase yet, sorry. > > Hey there, > > Do you still experience this one? > No, this has been fixed in cmake (2.8.2 if I remember correctly). Rene From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 10:49:17 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1BEA1065673 for ; Sun, 28 Aug 2011 10:49:17 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 863408FC17 for ; Sun, 28 Aug 2011 10:49:17 +0000 (UTC) Received: by qyk4 with SMTP id 4so1309174qyk.13 for ; Sun, 28 Aug 2011 03:49:16 -0700 (PDT) Received: by 10.229.39.210 with SMTP id h18mr4260443qce.120.1314528556695; Sun, 28 Aug 2011 03:49:16 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id o4sm2753860qct.25.2011.08.28.03.49.15 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Aug 2011 03:49:15 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jerry@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3RmtCG0TmPz2CG4t for ; Sun, 28 Aug 2011 06:49:14 -0400 (EDT) Date: Sun, 28 Aug 2011 06:49:13 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110828064913.7bbab2c2@seibercom.net> In-Reply-To: References: <4E560ACC.4080407@FreeBSD.org> <4E560D94.90902@gmx.de> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: print/cups-* ports vs. GNUTLS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 10:49:18 -0000 On Sun, 28 Aug 2011 11:16:10 +0200 Heino Tiedemann articulated: > Matthias Andree wrote: > > > Oh I see Dirk has just fixed this at 08:51 UTC. Thanks, that was > > quick! > > Fixed? > > I cannot update my cups ports: > > cups-base-1.4.6_5 < needs updating (port has > 1.4.8) cups-client-1.4.6 < needs updating (port > has 1.4.8) cups-image-1.4.6 < needs updating > (port has 1.4.8) > > > > ** Listing the failed packages (-:ignored / *:skipped / !:failed) > - print/cups-base (marked as IGNORE) > - print/cups-client (marked as IGNORE) > - print/cups-image (marked as IGNORE) > > Do I have do to something that these problem diasapear? Well, at lest I am not the only one who ran got bite in the ass by this. Do you have this activated for print/cups-base: [ ] GNUTLS Build with GNUTLS instead of OpenSSL checked? I was receiving an error message that this version of GNUTLS does not support threads. I had to manually go through every cups' configuration and remove any reference to GNUTLS in order to get it to build. What is so strange is that it build just fine before with GNUTLS. You might want to list what versions of the involved programs you have installed. You might want to contact the maintainer AND file a PR. I don't waste my time anymore. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 10:57:39 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 697D7106566B for ; Sun, 28 Aug 2011 10:57:39 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 2C26B8FC0C for ; Sun, 28 Aug 2011 10:57:39 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1Qxd3b-000PD7-OM for freebsd-ports@freebsd.org; Sun, 28 Aug 2011 12:57:39 +0200 Date: Sun, 28 Aug 2011 12:57:39 +0200 From: Kurt Jaeger To: freebsd-ports@freebsd.org Message-ID: <20110828105739.GD28186@home.opsec.eu> References: <4E59BC38.9060809@chen.org.nz> <4E59BE96.7050204@chen.org.nz> <20110828085411.GC28186@home.opsec.eu> <4E5A04FC.1070503@gwdg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E5A04FC.1070503@gwdg.de> Subject: Re: evolution problem even after libgweather (was Re: Missing libproxy.la?) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 10:57:39 -0000 Hi! > > I still have a similar problem, but with evolution, even > > after I reinstalled libgweather. > > > > Any ideas ? > > I had to reinstall libgweather, libgdata and evolution-data-server > before I was able to continue. Thanks, that did help. -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 11:46:04 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47CDA106564A for ; Sun, 28 Aug 2011 11:46:04 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward14.mail.yandex.net (forward14.mail.yandex.net [IPv6:2a02:6b8:0:801::4]) by mx1.freebsd.org (Postfix) with ESMTP id BF5108FC1E for ; Sun, 28 Aug 2011 11:46:03 +0000 (UTC) Received: from smtp13.mail.yandex.net (smtp13.mail.yandex.net [95.108.130.68]) by forward14.mail.yandex.net (Yandex) with ESMTP id 3745419819C0; Sun, 28 Aug 2011 15:46:02 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314531962; bh=caExxyJPtf6QxJyeoz6tN7I3fvkEeOfhNGpTt7th8hs=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=g4BL0tXOWcoyMM6zf+cFXEZPa6YEeQUb/rszwIeqaKa+YMMVnhSZ1QfxTc7SY6ps5 DLXrfD9akLXGYOuNvL0Pr7pStJvNrdXX/4hPjR0Gs/EIVdLxBjmtcivhWTum5FQbr9 tFP8LTzbDdNQG+zuaCmiz/DKPCM3cvOli2GKoCE8= Received: from smtp13.mail.yandex.net (localhost [127.0.0.1]) by smtp13.mail.yandex.net (Yandex) with ESMTP id 22E10E4021E; Sun, 28 Aug 2011 15:46:02 +0400 (MSD) Received: from unknown (unknown [178.76.212.172]) by smtp13.mail.yandex.net (nwsmtp/Yandex) with ESMTP id k1mSBj25; Sun, 28 Aug 2011 15:46:01 +0400 X-Yandex-Spam: 1 Message-ID: <4E59F224.30104@yandex.ru> Date: Sun, 28 Aug 2011 11:45:40 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: Torfinn Ingolfsen References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports ML Subject: Re: Annoying portupgrade behavior X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 11:46:04 -0000 Torfinn Ingolfsen wrote on 27.08.2011 18:43: > Annoying. > root@kg-v2# portupgrade --version > portupgrade 2.4.9.3 > root@kg-v2# uname -a > FreeBSD kg-v2.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Jul 16 > 02:07:14 CEST 2011 root@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC > amd64 > > Is therer a way around this? I also have alexandria installed (i keep the deleted port in deskutils) and have no problem with updating another ports with portmaster. Looks like some complicated logic in new portupgrade, so i'd tryed portmaster instead. -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 11:58:37 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71034106566C for ; Sun, 28 Aug 2011 11:58:37 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2E06C8FC12 for ; Sun, 28 Aug 2011 11:58:37 +0000 (UTC) Received: by ywo32 with SMTP id 32so4878707ywo.13 for ; Sun, 28 Aug 2011 04:58:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=cy1oKBAf4C+LTUCuBYABdynqjPOulvNc4vy/CJLFdAo=; b=o542Bsx5MIbVMTuFbMLoYLYXYvwYPH/sqGnRNMmNgQZu0NnaU5qw0IjiJ3V9KanhmB L1OhlKg9cnJnk9kD5gBdN7slGQQcp44UXArcl1bpKZcCAEyQPIyx41DpkUL/PcbBY0I8 917dFeNWiszF6jf0KMo+4RU4B5QdKdY6RIEAQ= Received: by 10.42.39.18 with SMTP id f18mr2325939ice.281.1314532716102; Sun, 28 Aug 2011 04:58:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.42.4 with HTTP; Sun, 28 Aug 2011 04:58:05 -0700 (PDT) In-Reply-To: References: <20110826172328.67f707d7@cox.net> <1314402348.13483.6.camel@xenon> <867h5zt6gd.fsf@gmail.com> <867h5zm278.fsf@gmail.com> From: Chris Rees Date: Sun, 28 Aug 2011 12:58:05 +0100 Message-ID: To: Test Rat Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ports@freebsd.org Subject: Re: Problem with nvidia-driver and "X" after upgrade X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 11:58:37 -0000 On 27 August 2011 14:36, Chris Rees wrote: > Hah, you're quite right, I misread. Please accept my apologies for thinki= ng > someone as smart as you could suggest such a bad idea ;) To clarify this statement, I would like to point out that I was not saying that Test Rat's idea was a bad idea. I misread his original patch, and disagreed, but once pointed back to the patch, I realised that it was not the idea I had originally thought of. Sorry for the noise, and I'm sorry if you misread it Test Rat ;) Please get in touch if you want to talk further about it. Chris --=20 Chris Rees =A0 =A0 =A0 =A0 =A0| FreeBSD Developer crees@FreeBSD.org =A0 | http://people.freebsd.org/~crees From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 13:08:09 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F44C1065689 for ; Sun, 28 Aug 2011 13:08:09 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id A7B838FC19 for ; Sun, 28 Aug 2011 13:08:08 +0000 (UTC) Received: by vws18 with SMTP id 18so5209187vws.13 for ; Sun, 28 Aug 2011 06:08:08 -0700 (PDT) Received: by 10.220.150.132 with SMTP id y4mr417711vcv.276.1314536887972; Sun, 28 Aug 2011 06:08:07 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id df8sm2345484vdc.13.2011.08.28.06.08.06 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Aug 2011 06:08:07 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jerry@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3RmxHT3hjmz2CG4t for ; Sun, 28 Aug 2011 09:08:05 -0400 (EDT) Date: Sun, 28 Aug 2011 09:08:05 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110828090805.5cf66137@seibercom.net> In-Reply-To: References: <20110826172328.67f707d7@cox.net> <1314402348.13483.6.camel@xenon> <867h5zt6gd.fsf@gmail.com> <867h5zm278.fsf@gmail.com> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: Problem with nvidia-driver and "X" after upgrade X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 13:08:09 -0000 On Sun, 28 Aug 2011 12:58:05 +0100 Chris Rees articulated: > On 27 August 2011 14:36, Chris Rees wrote: > > Hah, you're quite right, I misread. Please accept my apologies for > > thinking someone as smart as you could suggest such a bad idea ;) > > To clarify this statement, I would like to point out that I was not > saying that Test Rat's idea was a bad idea. > > I misread his original patch, and disagreed, but once pointed back to > the patch, I realised that it was not the idea I had originally > thought of. > > Sorry for the noise, and I'm sorry if you misread it Test Rat ;) > Please get in touch if you want to talk further about it. In other words, you formerly believed you understood what you thought he said, but have now realized that what he said was not what you thought? -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ You cannot kill time without injuring eternity. From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 13:57:36 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C96E106566C for ; Sun, 28 Aug 2011 13:57:36 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 170F38FC16 for ; Sun, 28 Aug 2011 13:57:35 +0000 (UTC) Received: by ywo32 with SMTP id 32so4928427ywo.13 for ; Sun, 28 Aug 2011 06:57:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=bVP1TYk44kHFn2840Ln/Dge33EqpYsCRTgtDJlZtht0=; b=OEOvRYIzB7TEZGDnWc7T4S7fK5tZsDora5+/NdZVo36bvssc6z3bORQP/Tha2JszBZ eg8bTRaqlhazYvHwH5KL6S9GKfxv+XVqECLEJAqFv8l2gLHePJo9brdtgYfcKc/t2B+I zmkrwVQITFScdZmMDsppTVcXYpklXrWjhXyOY= MIME-Version: 1.0 Received: by 10.231.4.3 with SMTP id 3mr7909094ibp.72.1314539855230; Sun, 28 Aug 2011 06:57:35 -0700 (PDT) Received: by 10.231.42.4 with HTTP; Sun, 28 Aug 2011 06:57:34 -0700 (PDT) Received: by 10.231.42.4 with HTTP; Sun, 28 Aug 2011 06:57:34 -0700 (PDT) In-Reply-To: <20110828090805.5cf66137@seibercom.net> References: <20110826172328.67f707d7@cox.net> <1314402348.13483.6.camel@xenon> <867h5zt6gd.fsf@gmail.com> <867h5zm278.fsf@gmail.com> <20110828090805.5cf66137@seibercom.net> Date: Sun, 28 Aug 2011 14:57:34 +0100 Message-ID: From: Chris Rees To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Problem with nvidia-driver and "X" after upgrade X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 13:57:36 -0000 On 28 Aug 2011 14:08, "Jerry" wrote: > > On Sun, 28 Aug 2011 12:58:05 +0100 > Chris Rees articulated: > > > On 27 August 2011 14:36, Chris Rees wrote: > > > Hah, you're quite right, I misread. Please accept my apologies for > > > thinking someone as smart as you could suggest such a bad idea ;) > > > > To clarify this statement, I would like to point out that I was not > > saying that Test Rat's idea was a bad idea. > > > > I misread his original patch, and disagreed, but once pointed back to > > the patch, I realised that it was not the idea I had originally > > thought of. > > > > Sorry for the noise, and I'm sorry if you misread it Test Rat ;) > > Please get in touch if you want to talk further about it. > > In other words, you formerly believed you understood what you thought he > said, but have now realized that what he said was not what you thought? That's correct. Now I know people can understand what I meant :) Chris From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 14:14:47 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E70D2106566C for ; Sun, 28 Aug 2011 14:14:47 +0000 (UTC) (envelope-from leslie@eskk.nu) Received: from mx1.bjare.net (mx1.bjare.net [212.31.160.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9CD678FC08 for ; Sun, 28 Aug 2011 14:14:47 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mx1.bjare.net (Postfix) with ESMTP id 792965E169 for ; Sun, 28 Aug 2011 15:55:20 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mx1.bjare.net X-Spam-Flag: NO X-Spam-Score: -2.456 X-Spam-Level: X-Spam-Status: No, score=-2.456 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, SPF_PASS=-0.001] Received: from mx1.bjare.net ([127.0.0.1]) by localhost (mx1.bjare.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id vBDNggTo+Gct for ; Sun, 28 Aug 2011 15:55:07 +0200 (CEST) X-BN-MX1: ja X-BN-MailInfo: BjareNet Received: from bljbsd01.no-ip.org (c-195-216-040-164.static.bjare.net [195.216.40.164]) by mx1.bjare.net (Postfix) with ESMTP id 3C0AC5E163 for ; Sun, 28 Aug 2011 15:55:07 +0200 (CEST) Message-ID: <4E5A48AC.6050201@eskk.nu> Date: Sun, 28 Aug 2011 15:54:52 +0200 From: Leslie Jensen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110817 Thunderbird/6.0 MIME-Version: 1.0 To: ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 14:14:48 -0000 Following the instructions in /usr/ports/UPDATING I issued the command portmaster -r libnotify-0 And after a while I get this error Dependency check complete for print/cups-client libnotify-0.5.2 >> swt-devel-3.6.m5_2,1 >> apache-ant-1.8.2 >> jdk-1.6.0.3p4_25 >> cups-client-1.4.6 ===> Cleaning for cups-client-1.4.8 ===> cups-client-1.4.8 is marked as broken: gnutls does not support threads yet. *** Error code 1 Stop in /usr/ports/print/cups-client Thanks Leslie From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 14:33:48 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B476C1065678 for ; Sun, 28 Aug 2011 14:33:48 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 73DDC8FC0A for ; Sun, 28 Aug 2011 14:33:48 +0000 (UTC) Received: by gxk28 with SMTP id 28so4997997gxk.13 for ; Sun, 28 Aug 2011 07:33:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ih/SSySv5ZBXpOKQV41K6r5QlO9+KCI0Hgtp1PqgaJc=; b=HjQ/c+pkiT/oAsPn2MwadVGejl7wvFOcSjxfTZ3q7QK5w+C+p/xsEeR+DBFxD9HVOi vccTPo0tt+x7IPCdf+j4P1weakZbjG9qAM6E0nvvnjdsi1RbQDLjXQLleLGvO7MRyvoS K3pUU2SpKm9VGN2hlPEh2HcWWNg+YWles7pKI= MIME-Version: 1.0 Received: by 10.231.4.99 with SMTP id 35mr7886936ibq.85.1314542027354; Sun, 28 Aug 2011 07:33:47 -0700 (PDT) Received: by 10.231.42.4 with HTTP; Sun, 28 Aug 2011 07:33:47 -0700 (PDT) Received: by 10.231.42.4 with HTTP; Sun, 28 Aug 2011 07:33:47 -0700 (PDT) In-Reply-To: <4E5A48AC.6050201@eskk.nu> References: <4E5A48AC.6050201@eskk.nu> Date: Sun, 28 Aug 2011 15:33:47 +0100 Message-ID: From: Chris Rees To: Leslie Jensen Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: ports@freebsd.org Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 14:33:48 -0000 make -C /usr/ports/print/cups-client config, disable TLS. Chris On 28 Aug 2011 15:15, "Leslie Jensen" wrote: > > Following the instructions in /usr/ports/UPDATING I issued the command > > > portmaster -r libnotify-0 > > And after a while I get this error > > Dependency check complete for print/cups-client > libnotify-0.5.2 >> swt-devel-3.6.m5_2,1 >> apache-ant-1.8.2 >> > jdk-1.6.0.3p4_25 >> cups-client-1.4.6 > ===> Cleaning for cups-client-1.4.8 > > ===> cups-client-1.4.8 is marked as broken: gnutls does not support > threads yet. > *** Error code 1 > > Stop in /usr/ports/print/cups-client > > Thanks > > Leslie > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 14:59:53 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09317106566C for ; Sun, 28 Aug 2011 14:59:53 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id BA65D8FC14 for ; Sun, 28 Aug 2011 14:59:52 +0000 (UTC) Received: from mr16.lnh.mail.rcn.net ([207.172.157.36]) by smtp02.lnh.mail.rcn.net with ESMTP; 28 Aug 2011 10:30:31 -0400 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr16.lnh.mail.rcn.net (MOS 4.2.3-GA) with ESMTP id BGO89960; Sun, 28 Aug 2011 10:30:32 -0400 Received-SPF: None identity=pra; client-ip=209.6.41.114; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="roberthuff@rcn.com"; x-conformance=sidf_compatible Received-SPF: None identity=mailfrom; client-ip=209.6.41.114; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="roberthuff@rcn.com"; x-conformance=sidf_compatible Received-SPF: None identity=helo; client-ip=209.6.41.114; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="postmaster@jerusalem.litteratus.org.litteratus.org"; x-conformance=sidf_compatible Received: from 209-6-41-114.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.41.114]) by smtp01.lnh.mail.rcn.net with ESMTP; 28 Aug 2011 10:30:32 -0400 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20058.20743.791783.342355@jerusalem.litteratus.org> Date: Sun, 28 Aug 2011 10:30:31 -0400 To: Leslie Jensen In-Reply-To: <4E5A48AC.6050201@eskk.nu> References: <4E5A48AC.6050201@eskk.nu> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr16.lnh.mail.rcn.net) Cc: ports@freebsd.org Subject: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 14:59:53 -0000 Leslie Jensen writes: > > Following the instructions in /usr/ports/UPDATING I issued the command > > > portmaster -r libnotify-0 > > And after a while I get this error > > Dependency check complete for print/cups-client > libnotify-0.5.2 >> swt-devel-3.6.m5_2,1 >> apache-ant-1.8.2 >> > jdk-1.6.0.3p4_25 >> cups-client-1.4.6 > ===> Cleaning for cups-client-1.4.8 > > ===> cups-client-1.4.8 is marked as broken: gnutls does not support > threads yet. > *** Error code 1 > > Stop in /usr/ports/print/cups-client Unless you have a specific reason to use GNUTLS: go to ports/print, run "make config", uncheck the "Use GNUTLS instead of OpenSSL" setting. (If you do have a specific reason, you probably know enough to have handled this already.) Then rebuild. Worked for me. Robert Huff From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 15:30:31 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63DAC1065670 for ; Sun, 28 Aug 2011 15:30:31 +0000 (UTC) (envelope-from carmel_ny@hotmail.com) Received: from blu0-omc3-s38.blu0.hotmail.com (blu0-omc3-s38.blu0.hotmail.com [65.55.116.113]) by mx1.freebsd.org (Postfix) with ESMTP id 126BE8FC20 for ; Sun, 28 Aug 2011 15:30:30 +0000 (UTC) Received: from BLU0-SMTP182 ([65.55.116.74]) by blu0-omc3-s38.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 28 Aug 2011 08:30:31 -0700 X-Originating-IP: [174.109.142.1] X-Originating-Email: [carmel_ny@hotmail.com] Message-ID: Received: from scorpio.seibercom.net ([174.109.142.1]) by BLU0-SMTP182.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Sun, 28 Aug 2011 08:30:29 -0700 Received: from scorpio (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: carmel_ny@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3Rn0Rm29HJz2CG4t for ; Sun, 28 Aug 2011 11:30:28 -0400 (EDT) Date: Sun, 28 Aug 2011 11:30:27 -0400 From: Carmel To: freebsd-ports@freebsd.org In-Reply-To: <20058.20743.791783.342355@jerusalem.litteratus.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 28 Aug 2011 15:30:30.0145 (UTC) FILETIME=[6B4B0F10:01CC6597] Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 15:30:31 -0000 On Sun, 28 Aug 2011 10:30:31 -0400 Robert Huff articulated: > Leslie Jensen writes: > > > > Following the instructions in /usr/ports/UPDATING I issued the > > command > > > > portmaster -r libnotify-0 > > > > And after a while I get this error > > > > Dependency check complete for print/cups-client > > libnotify-0.5.2 >> swt-devel-3.6.m5_2,1 >> > > apache-ant-1.8.2 >> jdk-1.6.0.3p4_25 >> cups-client-1.4.6 > > ===> Cleaning for cups-client-1.4.8 > > > > ===> cups-client-1.4.8 is marked as broken: gnutls does not > > support threads yet. > > *** Error code 1 > > > > Stop in /usr/ports/print/cups-client > > Unless you have a specific reason to use GNUTLS: go to > ports/print, run "make config", uncheck the "Use GNUTLS instead of > OpenSSL" setting. (If you do have a specific reason, you probably > know enough to have handled this already.) > Then rebuild. > Worked for me. My question is what changed? It worked before updating "libnotify". Is "libnotify" the culprit or "GNUTLS" or something else and why didn't anyone catch this problem sooner? It is not like we are talking about some niche application(s). There appears to be a lot of material released lately that is either broken or requiring a considerable amount of manual intervention. Perhaps a moratorium (port freeze) should be considered until all of the outstanding problems have been corrected. -- Carmel ✌ carmel_ny@hotmail.com Never listen to anyone who talks to you for over five minutes about all that things that have happened to them that have left them speechless! From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 17:26:58 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE2A3106566B for ; Sun, 28 Aug 2011 17:26:58 +0000 (UTC) (envelope-from sahil@tandon.net) Received: from spartan.hamla.org (spartan.hamla.org [206.251.255.30]) by mx1.freebsd.org (Postfix) with ESMTP id BD9148FC0C for ; Sun, 28 Aug 2011 17:26:58 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spartan.hamla.org (Postfix) with ESMTP id 83BD4170FE for ; Sun, 28 Aug 2011 13:27:27 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tandon.net; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:reply-to:message-id :subject:subject:from:from:date:date:received; s=aegis; t= 1314552447; bh=Ucsrz/e2ZMGdt2+QADv5yBLk0DinhAZUniWT3/KmtDc=; b=j vkTMNg4Gk/EzCSkXn22R/L/F+omVzzxoCOR59+BofS8va9ZrTxurRyYrAxs6WLpx YEHkqqMBsN7lxJPGo6rkMhzRzzjy78DIwVVPGOjsuyK5MuTgLHQeZUEECvLmcnbS m1vDhKqWXLrsy6uHAl9bVNrGAcJP/z8uW2ux3Yj6aI= X-Virus-Scanned: by ClamAV at spartan.hamla.org Received: from spartan.hamla.org ([127.0.0.1]) by localhost (spartan.hamla.org [127.0.0.1]) (amavisd-new, port 10027) with LMTP id AAfHZeol8A9N for ; Sun, 28 Aug 2011 13:27:27 -0400 (EDT) Date: Sun, 28 Aug 2011 13:26:51 -0400 From: Sahil Tandon To: freebsd-ports@freebsd.org Message-ID: <20110828172651.GB277@magic.hamla.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 17:26:58 -0000 On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote: > My question is what changed? It worked before updating "libnotify". Is > "libnotify" the culprit or "GNUTLS" or something else and why didn't > anyone catch this problem sooner? The chain of dependencies during the libnotify update prompted the upgrade of cups. The latter's OpenSSL interfaces are explicitly thread-safe, which GNU TLS is not. > There appears to be a lot of material released lately that is either > broken or requiring a considerable amount of manual intervention. > Perhaps a moratorium (port freeze) should be considered until all of > the outstanding problems have been corrected. We are sorry for the inconvenience which is surely frustrating, but freezing the tree because of this does not seem appropriate. -- Sahil Tandon From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 17:41:04 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 38507106566C for ; Sun, 28 Aug 2011 17:41:04 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 3476423CF4F for ; Sun, 28 Aug 2011 19:41:03 +0200 (CEST) Message-ID: <4E5A7DAE.8090904@FreeBSD.org> Date: Sun, 28 Aug 2011 19:41:02 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4E5A48AC.6050201@eskk.nu> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: OPTIONS framework bug vs. SSL issues (was: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 17:41:04 -0000 Am 28.08.2011 16:33, schrieb Chris Rees: > make -C /usr/ports/print/cups-client config, disable TLS. > > Chris > On 28 Aug 2011 15:15, "Leslie Jensen" wrote: >> >> Following the instructions in /usr/ports/UPDATING I issued the command >> >> >> portmaster -r libnotify-0 >> >> And after a while I get this error >> >> Dependency check complete for print/cups-client >> libnotify-0.5.2 >> swt-devel-3.6.m5_2,1 >> apache-ant-1.8.2 >> >> jdk-1.6.0.3p4_25 >> cups-client-1.4.6 >> ===> Cleaning for cups-client-1.4.8 >> >> ===> cups-client-1.4.8 is marked as broken: gnutls does not support >> threads yet. >> *** Error code 1 >> >> Stop in /usr/ports/print/cups-client Greetings, just a brain flash: bsd.port.mk currently re-prompts OPTIONS if they've changed, for instance, through addition. Should we change this feature in b.p.mk so that it also re-prompt the user when the defaults have changed? Or should the CUPS port remove the GNUTLS offering altogether until either GNUTLS is multithreaded, CUPS single-threaded, or CUPS offers another library? Would it help the licensing mess to use NSS instead? I recall Fedora working on API-compatible layers so they could unify OpenSSL/GNUTLS/NSS APIs and rebase everything onto NSS. I haven't checked lately though what the status is. Best, Matthias From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 17:46:55 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C447106566B for ; Sun, 28 Aug 2011 17:46:55 +0000 (UTC) (envelope-from sahil@tandon.net) Received: from spartan.hamla.org (spartan.hamla.org [206.251.255.30]) by mx1.freebsd.org (Postfix) with ESMTP id 0BCD88FC0A for ; Sun, 28 Aug 2011 17:46:54 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spartan.hamla.org (Postfix) with ESMTP id CD295170FE for ; Sun, 28 Aug 2011 13:47:23 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tandon.net; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:reply-to:message-id :subject:subject:from:from:date:date:received; s=aegis; t= 1314553643; bh=QPX49hYVzz04x8xLapRaQ+OIRtBJ2idaSrdlfWjJ3VA=; b=Y SC6qKDoppC6SqcQ8VCeMqw/HUYDkfHgYCDSvdYxTbHNXsaxOIqT00fTC6ISvH0oT 0413NyutHiMx1Ony+Lmiue8Y0ARuCvIWIcqch33cvOyMwVG3E80QMzN8nxMLNfwd l8Vpyfn7Q8cIYOim7g05fny+qquSEWJg35VzFFqcMA= X-Virus-Scanned: by ClamAV at spartan.hamla.org Received: from spartan.hamla.org ([127.0.0.1]) by localhost (spartan.hamla.org [127.0.0.1]) (amavisd-new, port 10027) with LMTP id iV6u66oV2LGb for ; Sun, 28 Aug 2011 13:47:23 -0400 (EDT) Date: Sun, 28 Aug 2011 13:46:42 -0400 From: Sahil Tandon To: freebsd-ports@freebsd.org Message-ID: <20110828174640.GC277@magic.hamla.org> References: <4E5A48AC.6050201@eskk.nu> <4E5A7DAE.8090904@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E5A7DAE.8090904@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: OPTIONS framework bug vs. SSL issues (was: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 17:46:55 -0000 On Sun, 2011-08-28 at 19:41:02 +0200, Matthias Andree wrote: > just a brain flash: bsd.port.mk currently re-prompts OPTIONS if > they've changed, for instance, through addition. > > Should we change this feature in b.p.mk so that it also re-prompt the > user when the defaults have changed? Sounds like a good idea. -- Sahil Tandon From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 17:48:45 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EEEFE1065673 for ; Sun, 28 Aug 2011 17:48:45 +0000 (UTC) (envelope-from leslie@eskk.nu) Received: from mx1.bjare.net (mx1.bjare.net [212.31.160.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9FF9C8FC29 for ; Sun, 28 Aug 2011 17:48:45 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mx1.bjare.net (Postfix) with ESMTP id EF7555E137; Sun, 28 Aug 2011 19:48:58 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mx1.bjare.net X-Spam-Flag: NO X-Spam-Score: -2.456 X-Spam-Level: X-Spam-Status: No, score=-2.456 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, SPF_PASS=-0.001] Received: from mx1.bjare.net ([127.0.0.1]) by localhost (mx1.bjare.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id MZVQUo7p6eVl; Sun, 28 Aug 2011 19:48:56 +0200 (CEST) X-BN-MX1: ja X-BN-MailInfo: BjareNet Received: from bljbsd01.no-ip.org (c-195-216-040-164.static.bjare.net [195.216.40.164]) by mx1.bjare.net (Postfix) with ESMTP id 111C85E024; Sun, 28 Aug 2011 19:48:55 +0200 (CEST) Message-ID: <4E5A7F79.1090100@eskk.nu> Date: Sun, 28 Aug 2011 19:48:41 +0200 From: Leslie Jensen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: Chris Rees References: <4E5A48AC.6050201@eskk.nu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 17:48:46 -0000 2011-08-28 16:33, Chris Rees skrev: > make -C /usr/ports/print/cups-client config, disable TLS. > > Chris > On 28 Aug 2011 15:15, "Leslie Jensen" wrote: >> >> Following the instructions in /usr/ports/UPDATING I issued the command >> >> >> portmaster -r libnotify-0 >> >> And after a while I get this error >> >> Dependency check complete for print/cups-client >> libnotify-0.5.2>> swt-devel-3.6.m5_2,1>> apache-ant-1.8.2>> >> jdk-1.6.0.3p4_25>> cups-client-1.4.6 >> ===> Cleaning for cups-client-1.4.8 >> >> ===> cups-client-1.4.8 is marked as broken: gnutls does not support >> threads yet. >> *** Error code 1 >> >> Stop in /usr/ports/print/cups-client >> >> Thanks >> >> Leslie >> _______________________________________________ Thank you all :-) I'm up and running again. /Leslie From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 17:57:30 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0EFE106566B for ; Sun, 28 Aug 2011 17:57:30 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 418B98FC0C for ; Sun, 28 Aug 2011 17:57:29 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p7SHUxWP021313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 28 Aug 2011 20:30:59 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p7SHUxSa053960 for ; Sun, 28 Aug 2011 20:30:59 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p7SHUxlJ053959 for freebsd-ports@freebsd.org; Sun, 28 Aug 2011 20:30:59 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 28 Aug 2011 20:30:59 +0300 From: Kostik Belousov To: freebsd-ports@freebsd.org Message-ID: <20110828173059.GT17489@deviant.kiev.zoral.com.ua> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eXO0gIpoqofqJkSt" Content-Disposition: inline In-Reply-To: <20110828172651.GB277@magic.hamla.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 17:57:31 -0000 --eXO0gIpoqofqJkSt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 28, 2011 at 01:26:51PM -0400, Sahil Tandon wrote: > On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote: >=20 > > My question is what changed? It worked before updating "libnotify". Is > > "libnotify" the culprit or "GNUTLS" or something else and why didn't > > anyone catch this problem sooner? >=20 > The chain of dependencies during the libnotify update prompted the > upgrade of cups. The latter's OpenSSL interfaces are explicitly > thread-safe, which GNU TLS is not. >=20 > > There appears to be a lot of material released lately that is either > > broken or requiring a considerable amount of manual intervention. > > Perhaps a moratorium (port freeze) should be considered until all of > > the outstanding problems have been corrected. >=20 > We are sorry for the inconvenience which is surely frustrating, but > freezing the tree because of this does not seem appropriate. Might be, completely ignoring the option 'use gnutls' in cups ports, until it can be made working, will change everybody life to be easier. --eXO0gIpoqofqJkSt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk5ae1MACgkQC3+MBN1Mb4hJLQCgssu8Fp96SQ0O/rHsCTcQKL+N kSIAn3lcXKMsJVbauxo3qOF+CyNOaRfi =ppRd -----END PGP SIGNATURE----- --eXO0gIpoqofqJkSt-- From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 18:04:45 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5EAEC1065672 for ; Sun, 28 Aug 2011 18:04:45 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0E8428FC0C for ; Sun, 28 Aug 2011 18:04:44 +0000 (UTC) Received: by vxh11 with SMTP id 11so4887933vxh.13 for ; Sun, 28 Aug 2011 11:04:44 -0700 (PDT) Received: by 10.220.116.13 with SMTP id k13mr557582vcq.245.1314554684368; Sun, 28 Aug 2011 11:04:44 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id b20sm1766957vcw.37.2011.08.28.11.04.43 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Aug 2011 11:04:43 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jerry@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3Rn3sk0QRsz2CG4t for ; Sun, 28 Aug 2011 14:04:42 -0400 (EDT) Date: Sun, 28 Aug 2011 14:04:41 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110828140441.0b64c14c@seibercom.net> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Time to remove the GNUTLS option in the print/cups-client port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 18:04:45 -0000 It has become apparent that the: [ ] GNUTLS Build with GNUTLS instead of OpenSSL option in the print/cups-client port is not working. Activating it causes the port build to fail. Perhaps it is time to remove this option from the port. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ Good health is simply the slowest possible way to die. From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 18:06:55 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE0C7106566C for ; Sun, 28 Aug 2011 18:06:55 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 97F768FC15 for ; Sun, 28 Aug 2011 18:06:55 +0000 (UTC) Received: by iadx2 with SMTP id x2so314573iad.13 for ; Sun, 28 Aug 2011 11:06:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=VCbpB9zYVShXPPN2jBzXBF8e1/PhL8Scqbur95ejttE=; b=FaPR5QDmACQgAPs9o99f+Zsw+amntUsRNed/xzZyEaSHFmCjriVYvO3Zk2QpO8x07i E1DdwrX6XQzxDqAYajhQ2bNWjMPVGvsa/YXT1tbZoem+dI63eIF3FS9pM3FO1AMTY9dI SnZmIzLrI0Er7t4aqcIwCmB6dghRYLGEvTvKQ= Received: by 10.231.4.99 with SMTP id 35mr8317045ibq.85.1314554815048; Sun, 28 Aug 2011 11:06:55 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.42.4 with HTTP; Sun, 28 Aug 2011 11:06:25 -0700 (PDT) In-Reply-To: <20110828173059.GT17489@deviant.kiev.zoral.com.ua> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> From: Chris Rees Date: Sun, 28 Aug 2011 19:06:25 +0100 X-Google-Sender-Auth: Ds-Tcn_sKMPC03-GZfsy-bBbRSU Message-ID: To: Kostik Belousov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ports@freebsd.org Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 18:06:55 -0000 On 28 August 2011 18:30, Kostik Belousov wrote: > On Sun, Aug 28, 2011 at 01:26:51PM -0400, Sahil Tandon wrote: >> On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote: >> >> > My question is what changed? It worked before updating "libnotify". Is >> > "libnotify" the culprit or "GNUTLS" or something else and why didn't >> > anyone catch this problem sooner? >> >> The chain of dependencies during the libnotify update prompted the >> upgrade of cups. =A0The latter's OpenSSL interfaces are explicitly >> thread-safe, which GNU TLS is not. >> >> > There appears to be a lot of material released lately that is either >> > broken or requiring a considerable amount of manual intervention. >> > Perhaps a moratorium (port freeze) should be considered until all of >> > the outstanding problems have been corrected. >> >> We are sorry for the inconvenience which is surely frustrating, but >> freezing the tree because of this does not seem appropriate. > > Might be, completely ignoring the option 'use gnutls' in cups ports, > until it can be made working, will change everybody life to be easier. I can see why that might be appealing, but I'd be less than impressed if I'd selected WITH_TLS and found the option silently ignored. Perhaps the IGNORE message could be clarified... Chris From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 18:08:59 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1542B106566B for ; Sun, 28 Aug 2011 18:08:59 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id C9FC48FC15 for ; Sun, 28 Aug 2011 18:08:58 +0000 (UTC) Received: by gyd10 with SMTP id 10so5091568gyd.13 for ; Sun, 28 Aug 2011 11:08:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; bh=FvESqx3aTbzpg7/LVcLd42mc6gFoaArs79SXZd/zUDo=; b=g/5p0y34I84N3YEE+FMks2TSG7Uz+eZyS3urv/GtaITf82L9UQCqhydMTMf5D/XV6Q 6ogK+ve+7uZ/5jJtzSz2FoHkIR85EaqeATepH5CeR4bwYh5nlsjWT3L0+T5MD55X9/JZ 6A9xxwxyQmbytRnY5hdByvlDJITvGBj2+wPjg= Received: by 10.231.4.3 with SMTP id 3mr8425981ibp.72.1314554938079; Sun, 28 Aug 2011 11:08:58 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.42.4 with HTTP; Sun, 28 Aug 2011 11:08:28 -0700 (PDT) In-Reply-To: <20110828140441.0b64c14c@seibercom.net> References: <20110828140441.0b64c14c@seibercom.net> From: Chris Rees Date: Sun, 28 Aug 2011 19:08:28 +0100 X-Google-Sender-Auth: dt0E8iS1xDX5qjJSvWGriR6LC7g Message-ID: To: freebsd-ports@freebsd.org, jerry@seibercom.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: Time to remove the GNUTLS option in the print/cups-client port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 18:08:59 -0000 On 28 August 2011 19:04, Jerry wrote: > It has become apparent that the: > > =A0[ ] GNUTLS =A0 =A0 =A0 Build with GNUTLS instead of OpenSSL > > option in the print/cups-client port is not working. Activating it > causes the port build to fail. Perhaps it is time to remove this option > from the port. > Hopefully it will only be a temporary problem. Chris From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 18:14:14 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDB2A106564A for ; Sun, 28 Aug 2011 18:14:14 +0000 (UTC) (envelope-from sahil@tandon.net) Received: from spartan.hamla.org (spartan.hamla.org [206.251.255.30]) by mx1.freebsd.org (Postfix) with ESMTP id AC4318FC1B for ; Sun, 28 Aug 2011 18:14:14 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spartan.hamla.org (Postfix) with ESMTP id A91CC170FE for ; Sun, 28 Aug 2011 14:14:43 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tandon.net; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:reply-to:message-id :subject:subject:from:from:date:date:received; s=aegis; t= 1314555283; bh=HmHBqcLzS7i2mQHVBgOCME59HXj8n3TBTb4fEGUSKbo=; b=I 1RJHx/Zwn4hvqZLE/QM36SUoY35rUaAuAvNv2MLmxb9KWeOXZ/P6Ds/PtyIcM6Th OGo9+6fU/c3W51E03w7+6jDGYT+ff6bChpmh21myxMTGDMiCW70kZ2MRvifZCuze hu4zG9eLnHec80SbAA0Avgtb4xidGQfu9l/nKwX3Ks= X-Virus-Scanned: by ClamAV at spartan.hamla.org Received: from spartan.hamla.org ([127.0.0.1]) by localhost (spartan.hamla.org [127.0.0.1]) (amavisd-new, port 10027) with LMTP id aab-34bF4EnY for ; Sun, 28 Aug 2011 14:14:43 -0400 (EDT) Date: Sun, 28 Aug 2011 14:13:59 -0400 From: Sahil Tandon To: freebsd-ports@freebsd.org Message-ID: <20110828181356.GD277@magic.hamla.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110828173059.GT17489@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 18:14:14 -0000 On Sun, 2011-08-28 at 20:30:59 +0300, Kostik Belousov wrote: > On Sun, Aug 28, 2011 at 01:26:51PM -0400, Sahil Tandon wrote: > > On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote: > > > > > My question is what changed? It worked before updating "libnotify". Is > > > "libnotify" the culprit or "GNUTLS" or something else and why didn't > > > anyone catch this problem sooner? > > > > The chain of dependencies during the libnotify update prompted the > > upgrade of cups. The latter's OpenSSL interfaces are explicitly > > thread-safe, which GNU TLS is not. > > > > > There appears to be a lot of material released lately that is either > > > broken or requiring a considerable amount of manual intervention. > > > Perhaps a moratorium (port freeze) should be considered until all of > > > the outstanding problems have been corrected. > > > > We are sorry for the inconvenience which is surely frustrating, but > > freezing the tree because of this does not seem appropriate. > > Might be, completely ignoring the option 'use gnutls' in cups ports, > until it can be made working, will change everybody life to be easier. What "might be"? As already noted, the GNUTLS option now defaults to OFF and users are warned (via the BROKEN construct) if it is selected. -- Sahil Tandon From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 18:36:51 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DBC9106564A for ; Sun, 28 Aug 2011 18:36:51 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 2A0558FC1E for ; Sun, 28 Aug 2011 18:36:50 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p7SIX0cW047476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 28 Aug 2011 21:33:00 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p7SIX04K056285 for ; Sun, 28 Aug 2011 21:33:00 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p7SIX0Hl056284 for freebsd-ports@freebsd.org; Sun, 28 Aug 2011 21:33:00 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 28 Aug 2011 21:33:00 +0300 From: Kostik Belousov To: freebsd-ports@freebsd.org Message-ID: <20110828183300.GX17489@deviant.kiev.zoral.com.ua> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yP6PQUgJdmhVCFKJ" Content-Disposition: inline In-Reply-To: <20110828181356.GD277@magic.hamla.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 18:36:51 -0000 --yP6PQUgJdmhVCFKJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 28, 2011 at 02:13:59PM -0400, Sahil Tandon wrote: > On Sun, 2011-08-28 at 20:30:59 +0300, Kostik Belousov wrote: >=20 > > On Sun, Aug 28, 2011 at 01:26:51PM -0400, Sahil Tandon wrote: > > > On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote: > > >=20 > > > > My question is what changed? It worked before updating "libnotify".= Is > > > > "libnotify" the culprit or "GNUTLS" or something else and why didn't > > > > anyone catch this problem sooner? > > >=20 > > > The chain of dependencies during the libnotify update prompted the > > > upgrade of cups. The latter's OpenSSL interfaces are explicitly > > > thread-safe, which GNU TLS is not. > > >=20 > > > > There appears to be a lot of material released lately that is either > > > > broken or requiring a considerable amount of manual intervention. > > > > Perhaps a moratorium (port freeze) should be considered until all of > > > > the outstanding problems have been corrected. > > >=20 > > > We are sorry for the inconvenience which is surely frustrating, but > > > freezing the tree because of this does not seem appropriate. > >=20 > > Might be, completely ignoring the option 'use gnutls' in cups ports, > > until it can be made working, will change everybody life to be easier. >=20 > What "might be"? >=20 > As already noted, the GNUTLS option now defaults to OFF and users are > warned (via the BROKEN construct) if it is selected.=20 Apparently, this have to be written explicitely. Users, who upgrade their ports, are not presented with the configuration dialog. Using automated tool like portupgrade, all you get is a list of the failed ports. After that, user needs to start investigation, spending his own time and possibly time of the people on list. Ignoring or removing the option makes the ports upgrade without user intervention. I am willing to spend some more time describing unobvious points of this consideration. --yP6PQUgJdmhVCFKJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk5aidsACgkQC3+MBN1Mb4gM+QCaA8vDEtVBOT3XunXuuGElJ7Gw g90AoICy1aMgIrNk6cBQs5ZLtJfD/ozO =YsJl -----END PGP SIGNATURE----- --yP6PQUgJdmhVCFKJ-- From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 18:41:52 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 464AD106564A for ; Sun, 28 Aug 2011 18:41:52 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 01C9B8FC0C for ; Sun, 28 Aug 2011 18:41:51 +0000 (UTC) Received: by gyd10 with SMTP id 10so5106372gyd.13 for ; Sun, 28 Aug 2011 11:41:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=lHfZ+wdMx+f+iMEPWbh8G+QpwjUGNQniGkcwop1ZlOw=; b=aAACbgcOB7B9cmFgfP5pKiSFxZJWQxeVTfsPu+VQVoVqOWjKz97FTmZeJ0uUiFShg/ Yq/boGW/b1FFBIVaY6/2jHFr2Lq004WCT7QUDSvXHyFjNLGc9kDcozO6W2AtVBwV7ii0 1jTujDSAXHN8IYTxVOIQtdJ/gvbfFtM/dTqJQ= Received: by 10.42.144.1 with SMTP id z1mr3817689icu.306.1314556911110; Sun, 28 Aug 2011 11:41:51 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.61.148 with HTTP; Sun, 28 Aug 2011 11:41:20 -0700 (PDT) In-Reply-To: <20110828183300.GX17489@deviant.kiev.zoral.com.ua> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> From: Chris Rees Date: Sun, 28 Aug 2011 19:41:20 +0100 X-Google-Sender-Auth: PuAbYcGRumsldUNNwSPOV_qQj_0 Message-ID: To: Kostik Belousov , dinoex@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ports@freebsd.org Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 18:41:52 -0000 On 28 August 2011 19:33, Kostik Belousov wrote: > On Sun, Aug 28, 2011 at 02:13:59PM -0400, Sahil Tandon wrote: >> On Sun, 2011-08-28 at 20:30:59 +0300, Kostik Belousov wrote: >> >> > On Sun, Aug 28, 2011 at 01:26:51PM -0400, Sahil Tandon wrote: >> > > On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote: >> > > >> > > > My question is what changed? It worked before updating "libnotify"= . Is >> > > > "libnotify" the culprit or "GNUTLS" or something else and why didn= 't >> > > > anyone catch this problem sooner? >> > > >> > > The chain of dependencies during the libnotify update prompted the >> > > upgrade of cups. =A0The latter's OpenSSL interfaces are explicitly >> > > thread-safe, which GNU TLS is not. >> > > >> > > > There appears to be a lot of material released lately that is eith= er >> > > > broken or requiring a considerable amount of manual intervention. >> > > > Perhaps a moratorium (port freeze) should be considered until all = of >> > > > the outstanding problems have been corrected. >> > > >> > > We are sorry for the inconvenience which is surely frustrating, but >> > > freezing the tree because of this does not seem appropriate. >> > >> > Might be, completely ignoring the option 'use gnutls' in cups ports, >> > until it can be made working, will change everybody life to be easier. >> >> What "might be"? >> >> As already noted, the GNUTLS option now defaults to OFF and users are >> warned (via the BROKEN construct) if it is selected. > > Apparently, this have to be written explicitely. Users, who upgrade > their ports, are not presented with the configuration dialog. Using > automated tool like portupgrade, all you get is a list of the failed > ports. After that, user needs to start investigation, spending his > own time and possibly time of the people on list. > > Ignoring or removing the option makes the ports upgrade without user > intervention. > > I am willing to spend some more time describing unobvious points of > this consideration. Alright, how about this? RCS file: /home/pcvs/ports/print/cups-base/Makefile,v retrieving revision 1.162 diff -u -r1.162 Makefile --- Makefile 25 Aug 2011 14:54:39 -0000 1.162 +++ Makefile 28 Aug 2011 18:40:24 -0000 @@ -124,7 +124,7 @@ .endif .if defined(WITH_GNUTLS) -BROKEN=3D gnutls does not support threads yet +BROKEN=3D gnutls does not support threads yet; disable the GNUTLS option to build CONFIGURE_ARGS+=3D --disable-openssl --enable-gnutls CONFIGURE_ENV+=3D PKGCONFIG=3D"${LOCALBASE}/bin/pkg-config" LIB_DEPENDS+=3D gnutls-openssl.27:${PORTSDIR}/security/gnutls Dirk, do you have any objections if I were to commit that? Chris From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 18:45:46 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC894106566B for ; Sun, 28 Aug 2011 18:45:45 +0000 (UTC) (envelope-from sahil@tandon.net) Received: from spartan.hamla.org (spartan.hamla.org [206.251.255.30]) by mx1.freebsd.org (Postfix) with ESMTP id B05368FC12 for ; Sun, 28 Aug 2011 18:45:45 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spartan.hamla.org (Postfix) with ESMTP id A22C4170FE; Sun, 28 Aug 2011 14:46:14 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tandon.net; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:reply-to:message-id :subject:subject:from:from:date:date:received; s=aegis; t= 1314557174; bh=U0GZWPJzrnUUyVQv7EmaVQ9NYbqQ2LBl6Kq9JYhgsH8=; b=V +EIcU1AzhN25xQKqhsa/Lpvi2Xt9Ew3hOSlleBrzrDcNVPN/HPOTrytonrT20a8c 06E7difTMsUUCodawv69VPWbv1OLgIbvXuFc+g8wefZY8MyHXCSuvsSPPd3qTL+I rRjk3RBHgrHyWtxV2WnN3kfqUww8jJt4lSRfPZXKTs= X-Virus-Scanned: by ClamAV at spartan.hamla.org Received: from spartan.hamla.org ([127.0.0.1]) by localhost (spartan.hamla.org [127.0.0.1]) (amavisd-new, port 10027) with LMTP id vdFdJWPi1rtS; Sun, 28 Aug 2011 14:46:14 -0400 (EDT) Date: Sun, 28 Aug 2011 14:45:42 -0400 From: Sahil Tandon To: freebsd-ports@freebsd.org Message-ID: <20110828184542.GE277@magic.hamla.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110828183300.GX17489@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: dinoex@FreeBSD.org Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 18:45:46 -0000 On Sun, 2011-08-28 at 21:33:00 +0300, Kostik Belousov wrote: > On Sun, Aug 28, 2011 at 02:13:59PM -0400, Sahil Tandon wrote: > > On Sun, 2011-08-28 at 20:30:59 +0300, Kostik Belousov wrote: > > > > > On Sun, Aug 28, 2011 at 01:26:51PM -0400, Sahil Tandon wrote: > > > > On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote: > > > > > > > > > My question is what changed? It worked before updating "libnotify". Is > > > > > "libnotify" the culprit or "GNUTLS" or something else and why didn't > > > > > anyone catch this problem sooner? > > > > > > > > The chain of dependencies during the libnotify update prompted the > > > > upgrade of cups. The latter's OpenSSL interfaces are explicitly > > > > thread-safe, which GNU TLS is not. > > > > > > > > > There appears to be a lot of material released lately that is either > > > > > broken or requiring a considerable amount of manual intervention. > > > > > Perhaps a moratorium (port freeze) should be considered until all of > > > > > the outstanding problems have been corrected. > > > > > > > > We are sorry for the inconvenience which is surely frustrating, but > > > > freezing the tree because of this does not seem appropriate. > > > > > > Might be, completely ignoring the option 'use gnutls' in cups ports, > > > until it can be made working, will change everybody life to be easier. > > > > What "might be"? > > > > As already noted, the GNUTLS option now defaults to OFF and users are > > warned (via the BROKEN construct) if it is selected. > > Apparently, this have to be written explicitely. Users, who upgrade > their ports, are not presented with the configuration dialog. Using > automated tool like portupgrade, all you get is a list of the failed > ports. After that, user needs to start investigation, spending his > own time and possibly time of the people on list. > > Ignoring or removing the option makes the ports upgrade without user > intervention. I am sorry users have had to "intervene" in managing their systems, but rather than removing the option entirely, I prefer mandree@'s more structural suggestion of re-prompting the user when defaults change. In the meantime, a note in UPDATING about explicitly disabling the GNUTLS option for cups ports is probably appropriate. I have copied the maintainer in hopes that he will consider it. > I am willing to spend some more time describing unobvious points of > this consideration. No, the consideration is trivial and does not need explaining; I just had trouble parsing your English. -- Sahil Tandon From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 18:53:23 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFA38106564A; Sun, 28 Aug 2011 18:53:23 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 5DFF18FC08; Sun, 28 Aug 2011 18:53:23 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p7SInXVc055822 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 28 Aug 2011 21:49:33 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p7SInXRi056912; Sun, 28 Aug 2011 21:49:33 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p7SInXx3056911; Sun, 28 Aug 2011 21:49:33 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 28 Aug 2011 21:49:33 +0300 From: Kostik Belousov To: Chris Rees Message-ID: <20110828184933.GY17489@deviant.kiev.zoral.com.ua> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Hwc0ilm0gE8kvSWy" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean Cc: dinoex@freebsd.org, freebsd-ports@freebsd.org Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 18:53:23 -0000 --Hwc0ilm0gE8kvSWy Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 28, 2011 at 07:41:20PM +0100, Chris Rees wrote: > On 28 August 2011 19:33, Kostik Belousov wrote: > > On Sun, Aug 28, 2011 at 02:13:59PM -0400, Sahil Tandon wrote: > >> On Sun, 2011-08-28 at 20:30:59 +0300, Kostik Belousov wrote: > >> > >> > On Sun, Aug 28, 2011 at 01:26:51PM -0400, Sahil Tandon wrote: > >> > > On Sun, 2011-08-28 at 11:30:27 -0400, Carmel wrote: > >> > > > >> > > > My question is what changed? It worked before updating "libnotif= y". Is > >> > > > "libnotify" the culprit or "GNUTLS" or something else and why di= dn't > >> > > > anyone catch this problem sooner? > >> > > > >> > > The chain of dependencies during the libnotify update prompted the > >> > > upgrade of cups. =9AThe latter's OpenSSL interfaces are explicitly > >> > > thread-safe, which GNU TLS is not. > >> > > > >> > > > There appears to be a lot of material released lately that is ei= ther > >> > > > broken or requiring a considerable amount of manual intervention. > >> > > > Perhaps a moratorium (port freeze) should be considered until al= l of > >> > > > the outstanding problems have been corrected. > >> > > > >> > > We are sorry for the inconvenience which is surely frustrating, but > >> > > freezing the tree because of this does not seem appropriate. > >> > > >> > Might be, completely ignoring the option 'use gnutls' in cups ports, > >> > until it can be made working, will change everybody life to be easie= r. > >> > >> What "might be"? > >> > >> As already noted, the GNUTLS option now defaults to OFF and users are > >> warned (via the BROKEN construct) if it is selected. > > > > Apparently, this have to be written explicitely. Users, who upgrade > > their ports, are not presented with the configuration dialog. Using > > automated tool like portupgrade, all you get is a list of the failed > > ports. After that, user needs to start investigation, spending his > > own time and possibly time of the people on list. > > > > Ignoring or removing the option makes the ports upgrade without user > > intervention. > > > > I am willing to spend some more time describing unobvious points of > > this consideration. >=20 > Alright, how about this? >=20 > RCS file: /home/pcvs/ports/print/cups-base/Makefile,v > retrieving revision 1.162 > diff -u -r1.162 Makefile > --- Makefile 25 Aug 2011 14:54:39 -0000 1.162 > +++ Makefile 28 Aug 2011 18:40:24 -0000 > @@ -124,7 +124,7 @@ > .endif >=20 > .if defined(WITH_GNUTLS) > -BROKEN=3D gnutls does not support threads yet > +BROKEN=3D gnutls does not support threads yet; disable the GNUTLS > option to build > CONFIGURE_ARGS+=3D --disable-openssl --enable-gnutls > CONFIGURE_ENV+=3D PKGCONFIG=3D"${LOCALBASE}/bin/pkg-config" > LIB_DEPENDS+=3D gnutls-openssl.27:${PORTSDIR}/security/gnutls >=20 > Dirk, do you have any objections if I were to commit that? It still requires manual intervention into the process which can be automat= ed. --Hwc0ilm0gE8kvSWy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk5ajb0ACgkQC3+MBN1Mb4hfCwCg0rlis1wktFbBOChcr+Iwy5/U qusAmweBxxai/LPllx0nIGhRQNk29JBv =MK2z -----END PGP SIGNATURE----- --Hwc0ilm0gE8kvSWy-- From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 19:22:38 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2D56106564A for ; Sun, 28 Aug 2011 19:22:38 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6CF858FC13 for ; Sun, 28 Aug 2011 19:22:38 +0000 (UTC) Received: by vxh11 with SMTP id 11so4918993vxh.13 for ; Sun, 28 Aug 2011 12:22:37 -0700 (PDT) Received: by 10.220.9.131 with SMTP id l3mr1194638vcl.148.1314559357826; Sun, 28 Aug 2011 12:22:37 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id fc7sm1356123vdc.0.2011.08.28.12.22.36 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Aug 2011 12:22:36 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jerry@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3Rn5bb0lrwz2CG4t for ; Sun, 28 Aug 2011 15:22:35 -0400 (EDT) Date: Sun, 28 Aug 2011 15:22:34 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110828152234.54cc9fac@seibercom.net> In-Reply-To: <20110828184542.GE277@magic.hamla.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 19:22:38 -0000 On Sun, 28 Aug 2011 14:45:42 -0400 Sahil Tandon articulated: > I am sorry users have had to "intervene" in managing their systems, > but rather than removing the option entirely, I prefer mandree@'s more > structural suggestion of re-prompting the user when defaults change. > In the meantime, a note in UPDATING about explicitly disabling the > GNUTLS option for cups ports is probably appropriate. I have copied > the maintainer in hopes that he will consider it. Sahil, I think you are being a little to flippant regrading this problem. Obviously any end user is responsible for maintaining his/her system. It is apparently that FreeBSD does not test updates as rigorously as other OSs might. Therefore, when the problem was first discovered in regards to "cups" and "GNUTLS" it is obviously that the end user would have to manually correct the problem. However, this is no longer day 0. The particulars of this case are well know. IMHO, a notice should have been inserted into the UPDATING file immediately -- in other words as soon as the phenomena was confirmed. To allow the port to be shipped with a known problem borders on criminal. At the very lest, it displays gross indifference to the users of FreeBSD. Nothing here is specifically blaming your for this problem. It takes more than one individual to screw things up this thoroughly. However, it takes only one person with a set of balls to get a solution implemented. The fact that you are actually going to wait for the maintainer the port in question to give his permission for you to issue a warning and hopefully a fix for this problem is pathetic. Seriously, and I don't mean any disrespect, but what government agency do you work for? :) -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ The climate of Bombay is such that its inhabitants have to live elsewhere. From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 19:30:51 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30632106564A for ; Sun, 28 Aug 2011 19:30:51 +0000 (UTC) (envelope-from sahil@tandon.net) Received: from spartan.hamla.org (spartan.hamla.org [206.251.255.30]) by mx1.freebsd.org (Postfix) with ESMTP id 0C1468FC15 for ; Sun, 28 Aug 2011 19:30:50 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spartan.hamla.org (Postfix) with ESMTP id C9055170FE for ; Sun, 28 Aug 2011 15:31:19 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tandon.net; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:reply-to:message-id :subject:subject:from:from:date:date:received; s=aegis; t= 1314559879; bh=l74ve4lbQpU/Zt8/+rY/wN7iFLxmtrXPtXAJJHKs0Nw=; b=E Yec0xC8NPMR/zGtK0JRlzTiJyCzB4ZyEvDrpt1sZTM+tuGWLelVweEX2V7WCq4gc PJ0EOAHHH4dxfbQfN4oCdw6GM9n9rRzcq+Sijix/l2zeLxwda9w6w2Jl7jmRRxGT RNl0d2Lxj4EeplatGCqEace/ls1Y5A4pMRUdXHBhUQ= X-Virus-Scanned: by ClamAV at spartan.hamla.org Received: from spartan.hamla.org ([127.0.0.1]) by localhost (spartan.hamla.org [127.0.0.1]) (amavisd-new, port 10027) with LMTP id QNDoBSWGiL7O for ; Sun, 28 Aug 2011 15:31:19 -0400 (EDT) Date: Sun, 28 Aug 2011 15:30:47 -0400 From: Sahil Tandon To: freebsd-ports@freebsd.org Message-ID: <20110828193046.GA668@magic.hamla.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110828152234.54cc9fac@seibercom.net> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 19:30:51 -0000 On Sun, 2011-08-28 at 15:22:34 -0400, Jerry wrote: > On Sun, 28 Aug 2011 14:45:42 -0400 > Sahil Tandon articulated: > > > I am sorry users have had to "intervene" in managing their systems, > > but rather than removing the option entirely, I prefer mandree@'s more > > structural suggestion of re-prompting the user when defaults change. > > In the meantime, a note in UPDATING about explicitly disabling the > > GNUTLS option for cups ports is probably appropriate. I have copied > > the maintainer in hopes that he will consider it. > > Sahil, I think you are being a little to flippant regrading this > problem. I do not mean to be flippant, so if that is how my message came across, I am sorry. > Obviously any end user is responsible for maintaining his/her system. > It is apparently that FreeBSD does not test updates as rigorously as > other OSs might. Therefore, when the problem was first discovered in > regards to "cups" and "GNUTLS" it is obviously that the end user would > have to manually correct the problem. Yes, a bit of manual intervention may be required, and for this inconvenience there should have been something in UPDATING. > However, this is no longer day 0. The particulars of this case are > well know. IMHO, a notice should have been inserted into the UPDATING > file immediately -- in other words as soon as the phenomena was > confirmed. To allow the port to be shipped with a known problem > borders on criminal. At the very lest, it displays gross indifference > to the users of FreeBSD. Criminal? Indifference? This sort of troll-ish hyperbole is decidedly unhelpful. I do agree that a note in UPDATING is appropriate. > Nothing here is specifically blaming your for this problem. It takes > more than one individual to screw things up this thoroughly. However, > it takes only one person with a set of balls to get a solution > implemented. The fact that you are actually going to wait for the > maintainer the port in question to give his permission for you to > issue a warning and hopefully a fix for this problem is pathetic. Ah, more trolling. > Seriously, and I don't mean any disrespect, but what government agency > do you work for? :) I don't work for a government agency, but cute attempt. -- Sahil Tandon From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 20:30:00 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1C33106566B for ; Sun, 28 Aug 2011 20:30:00 +0000 (UTC) (envelope-from code@apotheon.net) Received: from oproxy9.bluehost.com (oproxy9.bluehost.com [IPv6:2605:dc00:100:2::a2]) by mx1.freebsd.org (Postfix) with SMTP id 8EFEB8FC19 for ; Sun, 28 Aug 2011 20:30:00 +0000 (UTC) Received: (qmail 20632 invoked by uid 0); 28 Aug 2011 20:29:59 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by oproxy9.bluehost.com with SMTP; 28 Aug 2011 20:29:59 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.net; s=default; h=In-Reply-To:Content-Type:Mime-Version:References:Message-ID:Subject:To:From:Date; bh=77whX7t8Apn3gNcOwlCuhzui8PTEwYrj89KWXs9vwiQ=; b=G+uM89vIHIvA+jzQsTwBB1nDKQPmEiEhU8AQowgS+YNvgVe2QZnrw5rybLnYSNslN/aM/oJb9pTLPQKaOe3QdP7O56OEpEUgHHmeGBW3hXnJeDoMYutjrxga8D6LTssC; Received: from c-24-8-180-234.hsd1.co.comcast.net ([24.8.180.234] helo=kukaburra.hydra) by box543.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1QxlzS-0006er-9g for freebsd-ports@freebsd.org; Sun, 28 Aug 2011 14:29:59 -0600 Received: by kukaburra.hydra (sSMTP sendmail emulation); Sun, 28 Aug 2011 14:11:37 -0600 Date: Sun, 28 Aug 2011 14:11:37 -0600 From: Chad Perrin To: freebsd-ports@freebsd.org Message-ID: <20110828201137.GA61262@guilt.hydra> Mail-Followup-To: freebsd-ports@freebsd.org References: <20110828140441.0b64c14c@seibercom.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.org} {sentby:smtp auth 24.8.180.234 authed with ren@apotheon.org} Subject: Re: Time to remove the GNUTLS option in the print/cups-client port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 20:30:00 -0000 --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 28, 2011 at 07:08:28PM +0100, Chris Rees wrote: > On 28 August 2011 19:04, Jerry wrote: > > It has become apparent that the: > > > > =A0[ ] GNUTLS =A0 =A0 =A0 Build with GNUTLS instead of OpenSSL > > > > option in the print/cups-client port is not working. Activating it > > causes the port build to fail. Perhaps it is time to remove this option > > from the port. >=20 > Hopefully it will only be a temporary problem. What exactly is the benefit of using GnuTLS instead of OpenSSL anyway? --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --sdtB3X0nJg68CQEu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk5aoPkACgkQ9mn/Pj01uKXW5ACg47gptH83aj7YCo9N2WggW9wG Z0gAnjH7RReJ6hA+PcPg74/k8IImWJFa =rqnZ -----END PGP SIGNATURE----- --sdtB3X0nJg68CQEu-- From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 20:42:44 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id C9BEA106566C; Sun, 28 Aug 2011 20:42:44 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 8392F14F22B; Sun, 28 Aug 2011 20:42:44 +0000 (UTC) Message-ID: <4E5AA844.5030501@FreeBSD.org> Date: Sun, 28 Aug 2011 13:42:44 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: freebsd-ports@FreeBSD.org References: <4E5A48AC.6050201@eskk.nu> <4E5A7DAE.8090904@FreeBSD.org> <20110828174640.GC277@magic.hamla.org> In-Reply-To: <20110828174640.GC277@magic.hamla.org> X-Enigmail-Version: 1.3.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Sahil Tandon Subject: Re: OPTIONS framework bug vs. SSL issues X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 20:42:44 -0000 On 8/28/2011 10:46 AM, Sahil Tandon wrote: > On Sun, 2011-08-28 at 19:41:02 +0200, Matthias Andree wrote: > >> just a brain flash: bsd.port.mk currently re-prompts OPTIONS if >> they've changed, for instance, through addition. >> >> Should we change this feature in b.p.mk so that it also re-prompt the >> user when the defaults have changed? The way that (for example) portmaster works now is that if the user has already answered the questions for that port they don't get the dialog again unless a knob has been added or deleted. Personally I would find it surprising to be presented with the dialog again if there were no changes to the set of options. I wouldn't see a change in defaults in this case since my answers are already going to be filled in. For this specific case I probably would have changed the language of the gnutls option to make it clear that it needs to be un-selected, and added a no-op OPTION to make sure that users saw the dialog. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 20:54:54 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10F9E1065670 for ; Sun, 28 Aug 2011 20:54:54 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 906B98FC16 for ; Sun, 28 Aug 2011 20:54:53 +0000 (UTC) Received: by fxe4 with SMTP id 4so5043837fxe.13 for ; Sun, 28 Aug 2011 13:54:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=EHf2W41HK9bLjqgqrDQlnRVsiEMDlTgVueVx/S4255Y=; b=n5U6HdR+qAtYE+v/7p2ZyPIxH0n8ylT+Q8GaMNhcvmk7/tzgoAiV83/fYoCrvkniF7 9P7DaY7F6n4t5JV05NFZ/5U7Gmqmu0GjEyrcsUx2j2wN33urccWSKDWK3wOGDveEskxi dhKs0ulbE91BMk12CL5SaZodfHEfA4S3ftpoM= Received: by 10.223.21.141 with SMTP id j13mr5741962fab.79.1314564892358; Sun, 28 Aug 2011 13:54:52 -0700 (PDT) Received: from [10.0.101.2] (hotel.grandberoun.cz [90.182.105.26]) by mx.google.com with ESMTPS id c18sm3220281fah.15.2011.08.28.13.54.50 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Aug 2011 13:54:51 -0700 (PDT) From: Michal Varga To: freebsd-ports@FreeBSD.org In-Reply-To: <20110828193046.GA668@magic.hamla.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> Content-Type: text/plain; charset="UTF-8" Organization: Stonehenge Date: Sun, 28 Aug 2011 22:54:49 +0200 Message-ID: <1314564889.82067.89.camel@xenon> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 20:54:54 -0000 On Sun, 2011-08-28 at 15:30 -0400, Sahil Tandon wrote: [...] > Criminal? Indifference? This sort of troll-ish hyperbole is decidedly > unhelpful. I do agree that a note in UPDATING is appropriate. [...] > Ah, more trolling. To contribute my random few cents to the debate (without actually contributing anything of worth, so you don't really have to read it): Replies like these already made me discard like 20 of my own emails in the past, mid-write, exactly because of this expected outcome - accusations of trolling, because, why not, that's really what it's all about, right. So to say for myself - I do not know Jerry, but I definitely share his sentiments and even find his tone quite funnily (is that a word?) appropriate, as the ports quality, over the last year, went totally, horribly, down the drain. On some of my desktop setups, I keep about 900-1000 installed ports (and there are some ~200-300 for servers in general). There already seems not to be a single week, even once, without some MAJOR breakage that always takes hours (sometimes days) to track down and fix by my own (yes, even stuff as simple as "hey, you should have known that you only need to disable TLS and everything is fine again, duh" might take hours when walking through 100s of steps upgrade process and ESPECIALLY when that one particular breakage is combined with another, unrelated one. How much I love those days). And I know that every time I'd start writing a mail about it, my tone would be exactly the same as Jerry chose. With the expected result of "Zomg stop trolling", or for a change, the ever popular megahit "Patches welcome" (yes, like that will help anyone now), without even bothering to read what I'm really trying to complain about. The fact is, that port breakages are already so LOVING common these days that some people (like me) now take them as a regular daily routine. And sooner or later, more of them will start cracking and going for the same tone as Jerry did. On a weekly basis, again and again, there are port updates being introduced with what seems to be absolutely no testing whatsoever, some breakages take multiple takes on fixing by their respective port maintainers, new versions of major dependencies get introduced only to be rolled back few days later; using ports especially for this last year feels like a rollercoaster ride without a seatbelt, upside down, inside a volcano, wearing a parachute. And none of this is PORTS issue itself. It's a quality control issue, or more like - the horrible lack of it. So, was really Jerry's tone so trollish? I don't really think so. I'd simply consider him angry, as for myself, I know how many such emails I personally didn't have nerves to send, and would really, really love to. But somehow I feel, Jerry's is simply a start and there is much more of this to see in the coming future... m. -- Michal Varga, Stonehenge (Gmail account) From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 20:57:18 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 84D151065675 for ; Sun, 28 Aug 2011 20:57:18 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id A6961150E96 for ; Sun, 28 Aug 2011 20:57:17 +0000 (UTC) Message-ID: <4E5AABAE.6030200@FreeBSD.org> Date: Sun, 28 Aug 2011 13:57:18 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> In-Reply-To: <20110828183300.GX17489@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 1.3.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 20:57:18 -0000 On 8/28/2011 11:33 AM, Kostik Belousov wrote: > Apparently, this have to be written explicitely. Users, who upgrade > their ports, are not presented with the configuration dialog. The dialog is re-presented to the user if the quantity of options has changed. That's a feature. See my previous message on a way to make this feature work for us in this situation. > Using > automated tool like portupgrade, all you get is a list of the failed > ports. After that, user needs to start investigation, spending his > own time and possibly time of the people on list. > > Ignoring or removing the option makes the ports upgrade without user > intervention. Neither of those is a valid option (pardon the pun). The primary goal is to avoid breaking the user's system, not to make the upgrade process go through without human intervention. Imagine a scenario where the user has a critical dependency on cups being compiled with gnutls. Not upgrading the currently installed (and working) version is a totally valid outcome. Silently upgrading cups to a version without gnutls makes the upgrade process "successful," but with a very poor outcome for the user. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 21:14:27 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 086C01065670 for ; Sun, 28 Aug 2011 21:14:27 +0000 (UTC) (envelope-from sahil@tandon.net) Received: from spartan.hamla.org (spartan.hamla.org [206.251.255.30]) by mx1.freebsd.org (Postfix) with ESMTP id D7E588FC15 for ; Sun, 28 Aug 2011 21:14:26 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spartan.hamla.org (Postfix) with ESMTP id A1CF0170E3; Sun, 28 Aug 2011 17:14:55 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tandon.net; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:reply-to:message-id :subject:subject:from:from:date:date:received; s=aegis; t= 1314566095; bh=X6jBrXYcfEqvt5pVUWAxY2KQ6JPizNXmbMwAb2Z6SiA=; b=r XeOSu3x1D72ysdMASb2xSdnWu+tIXLrRB7iLtfqqq/5+SSFuNCCTiZPLemErHqzT KXe6ouWJl1MuVyBD1z5kQ2KqD4XI7NYYtwIkLbXA6tYid4wWhloD7ywdSIOGX7R2 Avd11bTDJavfhvOabKPz2PRcOn9FKMRb+/5xT/6Aow= X-Virus-Scanned: by ClamAV at spartan.hamla.org Received: from spartan.hamla.org ([127.0.0.1]) by localhost (spartan.hamla.org [127.0.0.1]) (amavisd-new, port 10027) with LMTP id GjHEslSULGOM; Sun, 28 Aug 2011 17:14:55 -0400 (EDT) Date: Sun, 28 Aug 2011 17:14:22 -0400 From: Sahil Tandon To: Michal Varga Message-ID: <20110828211422.GB668@magic.hamla.org> References: <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1314564889.82067.89.camel@xenon> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-ports@FreeBSD.org Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 21:14:27 -0000 On Sun, 2011-08-28 at 22:54:49 +0200, Michal Varga wrote: > On Sun, 2011-08-28 at 15:30 -0400, Sahil Tandon wrote: > > [...] > > Criminal? Indifference? This sort of troll-ish hyperbole is decidedly > > unhelpful. I do agree that a note in UPDATING is appropriate. > > [...] > > Ah, more trolling. > > To contribute my random few cents to the debate (without actually > contributing anything of worth, so you don't really have to read it): That is to say, chiming in from the cheap seats? :) > Replies like these already made me discard like 20 of my own emails in > the past, mid-write, exactly because of this expected outcome - > accusations of trolling, because, why not, that's really what it's all > about, right. Have you followed the rest of the thread, where I (and others) have debated the actual _issue_, rather than engaging in ad hominem attacks towards the parties involved? Disappointment with the ports tree is completely understandable and frustration in this case is warranted, but using inflammatory hyperbole and attacking volunteers is silly. So please, do not conflate being called a troll (when you're actually being one) vs. being labelled one for highlighting a problem. > So to say for myself - I do not know Jerry, but I definitely share his > sentiments and even find his tone quite funnily (is that a word?) > appropriate, as the ports quality, over the last year, went totally, > horribly, down the drain. I'm sorry you feel that way, I hope the quality can improve from what you find to be an unacceptably low level. > On some of my desktop setups, I keep about 900-1000 installed ports (and > there are some ~200-300 for servers in general). There already seems not > to be a single week, even once, without some MAJOR breakage that always > takes hours (sometimes days) to track down and fix by my own (yes, even > stuff as simple as "hey, you should have known that you only need to > disable TLS and everything is fine again, duh" might take hours when > walking through 100s of steps upgrade process and ESPECIALLY when that > one particular breakage is combined with another, unrelated one. How > much I love those days). I understand and appreciate your frustration, I have had similar experiences. > And I know that every time I'd start writing a mail about it, my tone > would be exactly the same as Jerry chose. With the expected result of > "Zomg stop trolling", or for a change, the ever popular megahit "Patches > welcome" (yes, like that will help anyone now), without even bothering > to read what I'm really trying to complain about. That is unfortunate; can you please share an example of this happening to you in the past on this list? Just so we can put it in context. > The fact is, that port breakages are already so LOVING common these > days that some people (like me) now take them as a regular daily > routine. And sooner or later, more of them will start cracking and > going for the same tone as Jerry did. On a weekly basis, again and > again, there are port updates being introduced with what seems to be > absolutely no testing whatsoever, some breakages take multiple takes > on fixing by their respective port maintainers, new versions of major > dependencies get introduced only to be rolled back few days later; > using ports especially for this last year feels like a rollercoaster > ride without a seatbelt, upside down, inside a volcano, wearing a > parachute. And none of this is PORTS issue itself. It's a quality > control issue, or more like - the horrible lack of it. I am sorry your experience has been so horrible. > So, was really Jerry's tone so trollish? Yes. Re-read the thread, from the beginning. > I don't really think so. I'd simply consider him angry, as for myself, > I know how many such emails I personally didn't have nerves to send, > and would really, really love to. But somehow I feel, Jerry's is > simply a start and there is much more of this to see in the coming > future... Your anger is understandable, but attacking people on this list is not. -- Sahil Tandon From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 21:15:11 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1EBC1065670 for ; Sun, 28 Aug 2011 21:15:11 +0000 (UTC) (envelope-from sahil@tandon.net) Received: from spartan.hamla.org (spartan.hamla.org [206.251.255.30]) by mx1.freebsd.org (Postfix) with ESMTP id 8F77C8FC15 for ; Sun, 28 Aug 2011 21:15:11 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spartan.hamla.org (Postfix) with ESMTP id 9B815170E3 for ; Sun, 28 Aug 2011 17:15:40 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tandon.net; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:reply-to:message-id :subject:subject:from:from:date:date:received; s=aegis; t= 1314566140; bh=4f5XJVrC8BP+ZLmhKdKfCkHKfS/FgUjPHdOGkcz3hsU=; b=r ixPaLsImFsObxPGHwUMC3H9+Iphw4I9SBkVqpEfAOPzExR5e7a8ap1J6h2QPAiGS L/R4FwsJhbCv2YBdS4RP+/PXqlCQmG/LEFcjR1Yi83epqS2jc7GVRxkkdCwA9GiC Xoa36T9Zz+9LmIpPi7I1rb2vBYO+9lcBhGP5BTvUdo= X-Virus-Scanned: by ClamAV at spartan.hamla.org Received: from spartan.hamla.org ([127.0.0.1]) by localhost (spartan.hamla.org [127.0.0.1]) (amavisd-new, port 10027) with LMTP id 6FtKsQvLpLQ9 for ; Sun, 28 Aug 2011 17:15:40 -0400 (EDT) Date: Sun, 28 Aug 2011 17:15:08 -0400 From: Sahil Tandon To: freebsd-ports@freebsd.org Message-ID: <20110828211508.GC668@magic.hamla.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <4E5AABAE.6030200@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E5AABAE.6030200@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 21:15:11 -0000 On Sun, 2011-08-28 at 13:57:18 -0700, Doug Barton wrote: > On 8/28/2011 11:33 AM, Kostik Belousov wrote: > > Ignoring or removing the option makes the ports upgrade without user > > intervention. > > Neither of those is a valid option (pardon the pun). The primary goal > is to avoid breaking the user's system, not to make the upgrade > process go through without human intervention. Imagine a scenario > where the user has a critical dependency on cups being compiled with > gnutls. Not upgrading the currently installed (and working) version is > a totally valid outcome. Silently upgrading cups to a version without > gnutls makes the upgrade process "successful," but with a very poor > outcome for the user. Bingo. -- Sahil Tandon From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 21:29:28 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08C4E106564A for ; Sun, 28 Aug 2011 21:29:28 +0000 (UTC) (envelope-from m@micheas.net) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 9E81C8FC0A for ; Sun, 28 Aug 2011 21:29:27 +0000 (UTC) Received: by wwi36 with SMTP id 36so5124562wwi.31 for ; Sun, 28 Aug 2011 14:29:26 -0700 (PDT) Received: by 10.216.134.155 with SMTP id s27mr1026815wei.53.1314565502073; Sun, 28 Aug 2011 14:05:02 -0700 (PDT) MIME-Version: 1.0 Sender: m@micheas.net Received: by 10.216.168.68 with HTTP; Sun, 28 Aug 2011 14:04:42 -0700 (PDT) In-Reply-To: <20110828201137.GA61262@guilt.hydra> References: <20110828140441.0b64c14c@seibercom.net> <20110828201137.GA61262@guilt.hydra> From: Micheas Herman Date: Sun, 28 Aug 2011 14:04:42 -0700 X-Google-Sender-Auth: 1I8iYepj4gitD46rXEUKLb9Nebo Message-ID: To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: Time to remove the GNUTLS option in the print/cups-client port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 21:29:28 -0000 On Sun, Aug 28, 2011 at 1:11 PM, Chad Perrin wrote: > > What exactly is the benefit of using GnuTLS instead of OpenSSL anyway? The only benefit that I have heard of is that gnutls works around at least one of the patent issues that openssl has. (the probably both infringe on dozens, if not hundreds, of erroneously issued American patents) -- Micheas From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 21:43:15 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 7229C106564A for ; Sun, 28 Aug 2011 21:43:15 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 78DC514FF72; Sun, 28 Aug 2011 21:43:14 +0000 (UTC) Message-ID: <4E5AB672.4020607@FreeBSD.org> Date: Sun, 28 Aug 2011 14:43:14 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: Michal Varga References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> In-Reply-To: <1314564889.82067.89.camel@xenon> X-Enigmail-Version: 1.3.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Ports system quality and trolling X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 21:43:15 -0000 On 8/28/2011 1:54 PM, Michal Varga wrote: > On Sun, 2011-08-28 at 15:30 -0400, Sahil Tandon wrote: > > [...] >> Criminal? Indifference? This sort of troll-ish hyperbole is decidedly >> unhelpful. FWIW, I agree with Sahil that this post of Jerry's was over the top, as several of his have been of late. To use the word "criminal" in this context is sufficient all on its own. To accuse people who spend an enormous amount of their own free time trying to make this thing work of being indifferent is just plain rude. > To contribute my random few cents to the debate (without actually > contributing anything of worth, so you don't really have to read it): > > Replies like these already made me discard like 20 of my own emails in > the past, mid-write, exactly because of this expected outcome - > accusations of trolling, because, why not, that's really what it's all > about, right. Well, no. :) Personally I find this message of yours to be well thought out and well stated. You raise some valid concerns without making personal attacks. That kind of feedback is always welcome. > So to say for myself - I do not know Jerry, but I definitely share his > sentiments and even find his tone quite funnily (is that a word?) > appropriate, as the ports quality, over the last year, went totally, > horribly, down the drain. > > On some of my desktop setups, I keep about 900-1000 installed ports (and > there are some ~200-300 for servers in general). There already seems not > to be a single week, even once, without some MAJOR breakage that always > takes hours (sometimes days) to track down and fix by my own ... FWIW, my experience has not been even close to yours, although I do find broken things occasionally. > And I know that every time I'd start writing a mail about it, my tone > would be exactly the same as Jerry chose. With the expected result of > "Zomg stop trolling", First, if you find something broken, please report it; in a calm, factual manner; ASAP. That will help us fix it ASAP and help avoid other users having to share the same frustration. Second, if you have concerns about the direction that things are heading in a more general way, feel free to express them as you have here. You may find that people agree with you. :) > or for a change, the ever popular megahit "Patches welcome" Sometimes that *is* the correct answer though. There is only so much that the existing pool of volunteers can do. If we don't get new people who are willing to get their hands dirty, the project dies. > On a weekly basis, again and again, there are port > updates being introduced with what seems to be absolutely no testing > whatsoever, some breakages take multiple takes on fixing by their > respective port maintainers, While I'm certainly not going to say that mistakes never get made, with very nearly 23,000 ports, and a nearly infinite number of possible OPTIONS combinations, shaking out all of the corner cases can be very difficult for even the most dedicated of maintainers. But, see below. > new versions of major dependencies get introduced only to be rolled back few days later; If you're talking about the recent ruby update, an enormous amount of work went into that prior to the trigger being pulled in an effort to make it as smooth as possible. It's unfortunate that in spite of that effort there were still some "issues" that were only discovered after users rushed to perform the upgrade. In this case backing out the change was the responsible course of action. > So, was really Jerry's tone so trollish? Yes. There is a world of difference between expressing concern about the issue (as you have done) and attacking people on a personal level. Now, how do we fix this? It has been suggested numerous times that one solution to this problem would be a "stable" ports tree. The idea being that after changes have had a chance to shake out for a while in the head of the ports tree they get merged back to a stable branch. This needs to happen, yesterday. The other thing that will help between now and then is to manage your change windows a little more conservatively. Except for security-related updates there is almost always zero reason to upgrade to new versions of things immediately after they hit the ports tree. With all due respect to those involved, one of the reasons the ruby thing was such a mess was that users jumped in and started upgrading stuff without knowing what they were doing, or why. Personally as soon as the notice about the upcoming change went out I put the knob in make.conf to keep my systems at 1.8 to make sure I wasn't affected. So all this is not to say, "You're wrong!" but instead to try and constructively address the concerns you've raised, and hopefully provide some suggestions on how to address them. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 22:05:31 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5511106566C for ; Sun, 28 Aug 2011 22:05:31 +0000 (UTC) (envelope-from jeroen@virtualhost.nl) Received: from mail.virtualhost.nl (mail.virtualhost.nl [89.200.201.133]) by mx1.freebsd.org (Postfix) with ESMTP id 5895F8FC1F for ; Sun, 28 Aug 2011 22:05:30 +0000 (UTC) Received: (qmail 15215 invoked by uid 1141); 28 Aug 2011 23:38:49 +0200 Received: from ip120-12-208-87.adsl2.static.versatel.nl (HELO blue.myspectrum.nl) (87.208.12.120) (smtp-auth username jeroen@virtualhost.nl, mechanism plain) by mail.virtualhost.nl (qpsmtpd/0.84) with (CAMELLIA256-SHA encrypted) ESMTPSA; Sun, 28 Aug 2011 23:38:49 +0200 Message-ID: <4E5AB569.4060703@virtualhost.nl> Date: Sun, 28 Aug 2011 23:38:49 +0200 From: Jeroen User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.18) Gecko/20110625 Thunderbird/3.1.11 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: firefox 6: mercurial seems to be missing as depency X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 22:05:31 -0000 Hi all, When updating firefox to the latest version (from ports) it complained about hg not being found. Apparently a dependency to mercurial is missing. I haven't checked why, installing it resolved it. Regards, Jeroen From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 22:28:47 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFB80106566B for ; Sun, 28 Aug 2011 22:28:47 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6DE438FC0C for ; Sun, 28 Aug 2011 22:28:47 +0000 (UTC) Received: by fxe4 with SMTP id 4so5087010fxe.13 for ; Sun, 28 Aug 2011 15:28:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=wEWlt/TLHmRx35mpXH9Qj1PGIOmBTG0WEnTWDeaj1Hc=; b=nS87SCFEPFG/SX16CgSwbp1voQF11tr9k+22JhXjm3rOD38oOF7ozt8zT/62tdq6HG qk019lRA0sZFSdDQXAL6vqbXDlkdOHAb+ZZheKFVUi000LbrC7xhRP/hJw4wArksqyvy 4zbyhTMTSE/y7l1viHCaShSmkBbPI724vArpA= Received: by 10.223.46.90 with SMTP id i26mr3804027faf.83.1314570526295; Sun, 28 Aug 2011 15:28:46 -0700 (PDT) Received: from [10.0.101.2] (hotel.grandberoun.cz [90.182.105.26]) by mx.google.com with ESMTPS id c4sm3088334fac.11.2011.08.28.15.28.44 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Aug 2011 15:28:45 -0700 (PDT) From: Michal Varga To: freebsd-ports@FreeBSD.org In-Reply-To: <20110828211422.GB668@magic.hamla.org> References: <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <20110828211422.GB668@magic.hamla.org> Content-Type: text/plain; charset="UTF-8" Organization: Stonehenge Date: Mon, 29 Aug 2011 00:28:42 +0200 Message-ID: <1314570522.82067.142.camel@xenon> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 22:28:48 -0000 On Sun, 2011-08-28 at 17:14 -0400, Sahil Tandon wrote: > > Replies like these already made me discard like 20 of my own emails in > > the past, mid-write, exactly because of this expected outcome - > > accusations of trolling, because, why not, that's really what it's all > > about, right. > > Have you followed the rest of the thread, where I (and others) have > debated the actual _issue_, rather than engaging in ad hominem attacks > towards the parties involved? Disappointment with the ports tree is > completely understandable and frustration in this case is warranted, but > using inflammatory hyperbole and attacking volunteers is silly. So > please, do not conflate being called a troll (when you're actually being > one) vs. being labelled one for highlighting a problem. Yes, I have read the thread and that's why I didn't feel need to add anything directly related to _the issue_ - as everything needed was already said, and solved, by that time. I'm not sure why exactly are you accusing me of ad hominem or any other attacks, as I don't remember making any of those. Pointing out that I can easily see why Jerry chose that specific tone of his emails doesn't really make an attack in my book, sorry. Then, I don't think he was really attacking you too, but I'm accustomed to the style of sarcasm he opted for, which might possibly be some cultural thing. It sometimes happens. > > So to say for myself - I do not know Jerry, but I definitely share his > > sentiments and even find his tone quite funnily (is that a word?) > > appropriate, as the ports quality, over the last year, went totally, > > horribly, down the drain. > > I'm sorry you feel that way, I hope the quality can improve from what > you find to be an unacceptably low level. Now I just hope you're being sarcastic too. > > And I know that every time I'd start writing a mail about it, my tone > > would be exactly the same as Jerry chose. With the expected result of > > "Zomg stop trolling", or for a change, the ever popular megahit "Patches > > welcome" (yes, like that will help anyone now), without even bothering > > to read what I'm really trying to complain about. > > That is unfortunate; can you please share an example of this happening > to you in the past on this list? Just so we can put it in context. I don't feel like pointing fingers and that was not my intention in the first place. Also, I've been here for way too long for that. What I was trying to point out that every time someone accuses someone else of trolling just because the guy was genuinely frustrated or angry (and actually, quite right to be), god has to kill a bag of kittens somewhere. Not every person that doesn't write in pink letters is necessarilly a troll, and not every person making a sarcastic comment about a pretty frustrating situation is there to make a personal attack (on you, or anyone else). Did you ever experience the situation down over the supermarket, when someone just takes one's parking spot, on which he exclaims "Damn, have you seen that? I'd kill that guy!" I hope you understand that he really isn't making any life threats (heck, even if he was, like that means anything). I'd suggest, if I may, rereading Jerry's messages with a glass of wine some time, and when you get to those very offending words, like, "criminal", thinking of them more in the context they were written in, instead of just the words alone. It definitely seems to help me, as for some reason I don't find them offending, while on the other hand, being bitten by the same situation, I can appreciate the sarcasm. > > I don't really think so. I'd simply consider him angry, as for myself, > > I know how many such emails I personally didn't have nerves to send, > > and would really, really love to. But somehow I feel, Jerry's is > > simply a start and there is much more of this to see in the coming > > future... > > Your anger is understandable, but attacking people on this list is not. For me, the GNUTLS situation was already more like "oh for christ, not again". It would hardly make me genuinely angry these days, with all the breakage happening in ports every other moment. And just being discontent doesn't yet an attack make, no matter how much you see it there. Jerry, while obviously sarcastic, wasn't any vulgar as far as I noticed, and even specifically pointed out in few places that he is not blaming (if I was you, I'd read that as "attacking", but that might be just me again) you, specifically. And if you think that now even some random me is just again *attacking* you, because I somehow sympathize with Jerry's position.. Well, I don't know then, but maybe just - harden the LOVE up? (A little bit, maybe.) m. -- Michal Varga, Stonehenge (Gmail account) From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 22:37:39 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 57DC7106564A for ; Sun, 28 Aug 2011 22:37:39 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 1F5E214E266; Sun, 28 Aug 2011 22:37:38 +0000 (UTC) Message-ID: <4E5AC332.3070009@FreeBSD.org> Date: Sun, 28 Aug 2011 15:37:38 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: Michal Varga References: <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <20110828211422.GB668@magic.hamla.org> <1314570522.82067.142.camel@xenon> In-Reply-To: <1314570522.82067.142.camel@xenon> X-Enigmail-Version: 1.3.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 22:37:39 -0000 On 8/28/2011 3:28 PM, Michal Varga wrote: > Not every person that doesn't write in pink letters is > necessarilly a troll, and not every person making a sarcastic comment > about a pretty frustrating situation is there to make a personal attack > (on you, or anyone else). Being frustrated and/or angry about a frustrating situation is perfectly normal. Taking that frustration out on people on the mailing list is not acceptable however. The lists don't exist for people to vent their frustration, they exist to help move the project forward. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 22:41:02 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD9EC106566B for ; Sun, 28 Aug 2011 22:41:02 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7BD6F8FC0A for ; Sun, 28 Aug 2011 22:41:02 +0000 (UTC) Received: by qwc9 with SMTP id 9so3715056qwc.13 for ; Sun, 28 Aug 2011 15:41:01 -0700 (PDT) Received: by 10.229.65.84 with SMTP id h20mr4855588qci.52.1314571261737; Sun, 28 Aug 2011 15:41:01 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id s9sm3030118qcx.38.2011.08.28.15.41.00 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Aug 2011 15:41:00 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jerry@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3RnB0W2m7Bz2CG4t for ; Sun, 28 Aug 2011 18:40:59 -0400 (EDT) Date: Sun, 28 Aug 2011 18:40:58 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110828184058.37812e34@seibercom.net> In-Reply-To: <4E5AB672.4020607@FreeBSD.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: Ports system quality and trolling X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 22:41:02 -0000 On Sun, 28 Aug 2011 14:43:14 -0700 Doug Barton articulated: > On 8/28/2011 1:54 PM, Michal Varga wrote: > > On Sun, 2011-08-28 at 15:30 -0400, Sahil Tandon wrote: > > > > [...] > >> Criminal? Indifference? This sort of troll-ish hyperbole is > >> decidedly unhelpful. > > FWIW, I agree with Sahil that this post of Jerry's was over the top, > as several of his have been of late. To use the word "criminal" in > this context is sufficient all on its own. To accuse people who spend > an enormous amount of their own free time trying to make this thing > work of being indifferent is just plain rude. Specifically, I said "borders on criminal". Get your facts straight. Second, I was specifically referring to the act, not the individual. In addition, "Spending enormous amounts of time" != "valid excuse". A mass murderer can spend enormous amounts of time planning his crime. Does that absolve him from the actual crime? > > To contribute my random few cents to the debate (without actually > > contributing anything of worth, so you don't really have to read > > it): > > > > Replies like these already made me discard like 20 of my own emails > > in the past, mid-write, exactly because of this expected outcome - > > accusations of trolling, because, why not, that's really what it's > > all about, right. > > Well, no. :) Personally I find this message of yours to be well > thought out and well stated. You raise some valid concerns without > making personal attacks. That kind of feedback is always welcome. > > > So to say for myself - I do not know Jerry, but I definitely share > > his sentiments and even find his tone quite funnily (is that a > > word?) appropriate, as the ports quality, over the last year, went > > totally, horribly, down the drain. > > > > On some of my desktop setups, I keep about 900-1000 installed ports > > (and there are some ~200-300 for servers in general). There already > > seems not to be a single week, even once, without some MAJOR > > breakage that always takes hours (sometimes days) to track down and > > fix by my own ... > > FWIW, my experience has not been even close to yours, although I do > find broken things occasionally. I have 1,112+/- ports installed on any given day on one of my machines. Your statement, without knowing your exact configuration, applications, etcetera is not a valid counter statement. It stands to reason that an increase in the number of ports used would show a corresponding increase in the number of port failures. > > And I know that every time I'd start writing a mail about it, my > > tone would be exactly the same as Jerry chose. With the expected > > result of "Zomg stop trolling", > > First, if you find something broken, please report it; in a calm, > factual manner; ASAP. That will help us fix it ASAP and help avoid > other users having to share the same frustration. Second, if you have > concerns about the direction that things are heading in a more > general way, feel free to express them as you have here. You may find > that people agree with you. :) And then again, you may not. > > or for a change, the ever popular megahit "Patches welcome" > > Sometimes that *is* the correct answer though. There is only so much > that the existing pool of volunteers can do. If we don't get new > people who are willing to get their hands dirty, the project dies. A quick death is often the best course of action. > > On a weekly basis, again and again, there are port > > updates being introduced with what seems to be absolutely no testing > > whatsoever, some breakages take multiple takes on fixing by their > > respective port maintainers, > > While I'm certainly not going to say that mistakes never get made, > with very nearly 23,000 ports, and a nearly infinite number of > possible OPTIONS combinations, shaking out all of the corner cases > can be very difficult for even the most dedicated of maintainers. > But, see below. > > > new versions of major dependencies get introduced only to be rolled > > back few days later; > > If you're talking about the recent ruby update, an enormous amount of > work went into that prior to the trigger being pulled in an effort to > make it as smooth as possible. It's unfortunate that in spite of that > effort there were still some "issues" that were only discovered after > users rushed to perform the upgrade. In this case backing out the > change was the responsible course of action. If this was an isolated issue, I would certainly agree with you. However, it has become the norm and not the exception for this sort of behavior. > > So, was really Jerry's tone so trollish? > > Yes. There is a world of difference between expressing concern about > the issue (as you have done) and attacking people on a personal level. The root problem is group mentality. Attempting to convey a message that runs counter to the "group" is like making a statement against the Pope, or the towel head god, or what ever. People immediately become paranoid and defensive. They act like a group of school girls who have to have their egos messaged on a daily basis. > Now, how do we fix this? It has been suggested numerous times that one > solution to this problem would be a "stable" ports tree. The idea > being that after changes have had a chance to shake out for a while > in the head of the ports tree they get merged back to a stable > branch. This needs to happen, yesterday. What really needs to happen, besides that, is that FreeBSD realize that there are wireless-N devices in existence, have been for over 5 years, and actually develop real, fully functional drivers for them. Opps, sorry, I forgot to blame the manufacturers and, or Microsoft for that failure. I'll skip the part about getting the device to operate without having to waste time attempting to get it manually configure just to make a simple network connect. That would be assuming that there was a driver available for the device to begin with. > The other thing that will help between now and then is to manage your > change windows a little more conservatively. Except for > security-related updates there is almost always zero reason to > upgrade to new versions of things immediately after they hit the > ports tree. With all due respect to those involved, one of the > reasons the ruby thing was such a mess was that users jumped in and > started upgrading stuff without knowing what they were doing, or why. > Personally as soon as the notice about the upcoming change went out I > put the knob in make.conf to keep my systems at 1.8 to make sure I > wasn't affected. I have no problem with that. No one should be forced to update their system if they choose not to. However, to carry your statement to its logical conclusion, you should issue a warning that attempting to update your system carries dire risks since the updates have not been properly tested. For the record, users knew exactly why the were updating "ruby", they wanted to. If it was not to be used, then why release it? What they did not know was that it was going to bite them in the ass, like so many other updates (cups+gnutls) have lately. If it had been failing on a few obscure programs, then I could probably say it was an unfortunate oversight. When it starts failing on major applications used by a large number of FreeBSD users, then it should be labels what it is, incompetency. Opps, did I hurt someone's feeling? Well, you screwed up my system and wasted hours of my valuable time, so now we are even. > So all this is not to say, "You're wrong!" but instead to try and > constructively address the concerns you've raised, and hopefully > provide some suggestions on how to address them. That and $1.50 (give or take) will get you a cup of coffee. From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 22:50:11 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDA1D1065673 for ; Sun, 28 Aug 2011 22:50:11 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6C5098FC08 for ; Sun, 28 Aug 2011 22:50:11 +0000 (UTC) Received: by vxh11 with SMTP id 11so4998977vxh.13 for ; Sun, 28 Aug 2011 15:50:10 -0700 (PDT) Received: by 10.220.106.212 with SMTP id y20mr1373699vco.91.1314571810633; Sun, 28 Aug 2011 15:50:10 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id gd12sm1857802vcb.11.2011.08.28.15.50.09 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Aug 2011 15:50:09 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jerry@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3RnBC41Jzqz2CG4t for ; Sun, 28 Aug 2011 18:50:08 -0400 (EDT) Date: Sun, 28 Aug 2011 18:50:07 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110828185007.1a6542a4@seibercom.net> In-Reply-To: References: <20110828140441.0b64c14c@seibercom.net> <20110828201137.GA61262@guilt.hydra> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: Time to remove the GNUTLS option in the print/cups-client port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 22:50:11 -0000 On Sun, 28 Aug 2011 14:04:42 -0700 Micheas Herman articulated: > On Sun, Aug 28, 2011 at 1:11 PM, Chad Perrin > wrote: > > > > What exactly is the benefit of using GnuTLS instead of OpenSSL > > anyway? > > The only benefit that I have heard of is that gnutls works around at > least one of the patent issues that openssl has. > > (the probably both infringe on dozens, if not hundreds, of erroneously > issued American patents) Erroneously issued in the sense that you are suppose to be paying for the right to use it and are attempting to circumvent the law or issued in the sense that someone else had all ready been issued a valid patent? Or, could it be that you feel someone should work for an indeterminate amount of time, invest his/her monies and take the risks of developing a new product and then be deprived of the right to make a return on their investment just so you can use the article for free? I think I know the answer to that one. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 22:57:49 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB33710656A8 for ; Sun, 28 Aug 2011 22:57:49 +0000 (UTC) (envelope-from sahil@tandon.net) Received: from spartan.hamla.org (spartan.hamla.org [206.251.255.30]) by mx1.freebsd.org (Postfix) with ESMTP id 96E0B8FC15 for ; Sun, 28 Aug 2011 22:57:49 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spartan.hamla.org (Postfix) with ESMTP id 6B87E17131 for ; Sun, 28 Aug 2011 18:58:18 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tandon.net; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:reply-to:message-id :subject:subject:from:from:date:date:received; s=aegis; t= 1314572298; bh=XD24LD5FARKuoDkl1kOv4+JCQL1lE6WmqAbummhQK/g=; b=P nFYeLLXCSs5TNOB4TWDgm+YR2C8vfelLB/cVG9PHpRZOzujSv9L6pVkxIvGC9oDH CwL0qF3BZ5Hyu+PdV0CGTJzn0ZXmO8ZXU9P2HtqJIL/xAYeVPPUssj6xD4I9n5S8 L/5sRJMObd/6ZYRVguOYseZf4gmbbXdEmt2XwDDWgE= X-Virus-Scanned: by ClamAV at spartan.hamla.org Received: from spartan.hamla.org ([127.0.0.1]) by localhost (spartan.hamla.org [127.0.0.1]) (amavisd-new, port 10027) with LMTP id HRHJzEsNmcj9 for ; Sun, 28 Aug 2011 18:58:18 -0400 (EDT) Date: Sun, 28 Aug 2011 18:57:46 -0400 From: Sahil Tandon To: freebsd-ports@freebsd.org Message-ID: <20110828225745.GE668@magic.hamla.org> References: <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <20110828211422.GB668@magic.hamla.org> <1314570522.82067.142.camel@xenon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1314570522.82067.142.camel@xenon> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 22:57:49 -0000 On Mon, 2011-08-29 at 00:28:42 +0200, Michal Varga wrote: > Yes, I have read the thread and that's why I didn't feel need to add > anything directly related to _the issue_ - as everything needed was > already said, and solved, by that time. > > I'm not sure why exactly are you accusing me of ad hominem or any > other attacks, as I don't remember making any of those. Pointing out > that I can easily see why Jerry chose that specific tone of his emails > doesn't really make an attack in my book, sorry. Then, I don't think > he was really attacking you too, but I'm accustomed to the style of > sarcasm he opted for, which might possibly be some cultural thing. It > sometimes happens. I was not accusing you. Sarcasm is not useful on a technical mailing list, no matter how accustomed you are to it. > > I'm sorry you feel that way, I hope the quality can improve from > > what you find to be an unacceptably low level. > > Now I just hope you're being sarcastic too. I am not being sarcastic. I sincerely hope that the ports experience can improve for you and other users (myself included). > What I was trying to point out that every time someone accuses someone > else of trolling just because the guy was genuinely frustrated or > angry (and actually, quite right to be), god has to kill a bag of > kittens somewhere. Not every person that doesn't write in pink letters > is necessarilly a troll, and not every person making a sarcastic > comment about a pretty frustrating situation is there to make a > personal attack (on you, or anyone else). You are arguing with straw men; no one said anything about pink letters or preventing the expression of anger or frustration. If you review this thread, you will notice others suffered the same problem, were frustration, but participated in the conversation with decency. > Did you ever experience the situation down over the supermarket, when > someone just takes one's parking spot, on which he exclaims "Damn, > have you seen that? I'd kill that guy!" I hope you understand that he > really isn't making any life threats (heck, even if he was, like that > means anything). I think you're trying to make an analogy, but it's not working. > And if you think that now even some random me is just again > *attacking* you, because I somehow sympathize with Jerry's position.. > Well, I don't know then, but maybe just - harden the LOVE up? (A > little bit, maybe.) I do not construe your comments as an attack, but I just don't agree with much of what you're saying. :) -- Sahil Tandon From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 23:22:56 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC2D8106564A for ; Sun, 28 Aug 2011 23:22:56 +0000 (UTC) (envelope-from m@micheas.net) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 5A13E8FC08 for ; Sun, 28 Aug 2011 23:22:55 +0000 (UTC) Received: by wwi36 with SMTP id 36so5166242wwi.31 for ; Sun, 28 Aug 2011 16:22:55 -0700 (PDT) Received: by 10.216.18.146 with SMTP id l18mr4058531wel.38.1314573775156; Sun, 28 Aug 2011 16:22:55 -0700 (PDT) MIME-Version: 1.0 Sender: m@micheas.net Received: by 10.216.168.68 with HTTP; Sun, 28 Aug 2011 16:22:35 -0700 (PDT) In-Reply-To: <20110828185007.1a6542a4@seibercom.net> References: <20110828140441.0b64c14c@seibercom.net> <20110828201137.GA61262@guilt.hydra> <20110828185007.1a6542a4@seibercom.net> From: Micheas Herman Date: Sun, 28 Aug 2011 16:22:35 -0700 X-Google-Sender-Auth: uxSd0urleqt0f-sVG6LFOhQLWfo Message-ID: To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: Time to remove the GNUTLS option in the print/cups-client port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 23:22:56 -0000 On Sun, Aug 28, 2011 at 3:50 PM, Jerry wrote: > On Sun, 28 Aug 2011 14:04:42 -0700 > Micheas Herman articulated: > >> On Sun, Aug 28, 2011 at 1:11 PM, Chad Perrin >> wrote: >> > >> > What exactly is the benefit of using GnuTLS instead of OpenSSL >> > anyway? >> >> The only benefit that I have heard of is that gnutls works around at >> least one of the patent issues that openssl has. >> >> (the probably both infringe on dozens, if not hundreds, of erroneously >> issued American patents) > > Erroneously issued in the sense that you are suppose to be paying for > the right to use it and are attempting to circumvent the law or issued > in the sense that someone else had all ready been issued a valid patent? Erroneously issued in that they were patenting already existing and in use technology. I have feelings about the usefulness of software patents but that has nothing to do with the fact that the majority of software patents that are subjected to aggres= sive reexamination fail to be upheld. The debate about software patents would probably be a lot different if this was not the case. In google vs oracle's java fight it looks like about 75% of oracles patents are going to get invalidated. (and those patents were picked for their strength.) >From my inexpert eyes it looks like google vs oracle is going to turn on CEO statements and actions more than the validity of the patents. > > Or, could it be that you feel someone should work for an indeterminate > amount of time, invest his/her monies and take the risks of developing a > new product and then be deprived of the right to make a return on their > investment just so you can use the article for free? I think I know the > answer to that one. This is a total non-sequitur. Most people being harmed by the insane patent mess are people that have invested his/her monies into products and become minimally successful. Any patents on openssl that have been granted in the last few years are obviously bogus. Whether RSA should have been granted patent status is something that reasonable people can disagree on. Patents on bubble sorts have clearly been issued in error. OpenSSL and GnuTLS both infringe on dozens of the later type of patents. > > -- > Jerry =E2=9C=8C > jerry+ports@seibercom.net > > Disclaimer: off-list followups get on-list replies or get ignored. > Please do not ignore the Reply-To header. > __________________________________________________________________ > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 23:26:30 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 81FCF106566C; Sun, 28 Aug 2011 23:26:30 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 04179156F23; Sun, 28 Aug 2011 23:26:28 +0000 (UTC) Message-ID: <4E5ACEA5.3040908@FreeBSD.org> Date: Sun, 28 Aug 2011 16:26:29 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <20110828184058.37812e34@seibercom.net> In-Reply-To: <20110828184058.37812e34@seibercom.net> X-Enigmail-Version: 1.3.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jerry , postmaster@FreeBSD.org Subject: Re: Ports system quality and trolling X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 23:26:30 -0000 Including postmaster@ on this since IMO Jerry has earned himself a short vacation from posting privileges. On 8/28/2011 3:40 PM, Jerry wrote: > On Sun, 28 Aug 2011 14:43:14 -0700 > Doug Barton articulated: > >> On 8/28/2011 1:54 PM, Michal Varga wrote: >>> On Sun, 2011-08-28 at 15:30 -0400, Sahil Tandon wrote: >>> >>> [...] >>>> Criminal? Indifference? This sort of troll-ish hyperbole is >>>> decidedly unhelpful. >> >> FWIW, I agree with Sahil that this post of Jerry's was over the top, >> as several of his have been of late. To use the word "criminal" in >> this context is sufficient all on its own. To accuse people who spend >> an enormous amount of their own free time trying to make this thing >> work of being indifferent is just plain rude. > > Specifically, I said "borders on criminal". Get your facts straight. I'm not sure why you think that makes a difference. The point that Sahil and I are trying to make is that both your words and your tone are, at best, unhelpful. No one who is involved with actually making things work around here believes that the system has no flaws. Quite the contrary, we know the flaws better than most users. But a constant stream of angry messages doesn't do anything to improve the situation. > Second, I was specifically referring to the act, not the individual. In > addition, "Spending enormous amounts of time" != "valid excuse". A mass > murderer can spend enormous amounts of time planning his crime. Does > that absolve him from the actual crime? You seem to be operating under the assumption that we owe you something, and that by failing to provide that thing we owe you we have wronged you somehow. You may wish to take a step back and consider that premise in light of what you're paying for this stuff. :) >> FWIW, my experience has not been even close to yours, although I do >> find broken things occasionally. > > I have 1,112+/- ports installed on any given day on one of my machines. > Your statement, without knowing your exact configuration, applications, > etcetera is not a valid counter statement. And yet, you felt totally comfortable in criticizing it anyway. Without trying to toot my own horn (since this was a minor part of my overall point) I have a non-trivial number of ports installed on my personal systems, support hundreds more on (at least) 4 different combinations of FreeBSD versions and architectures on a regular basis, develop portmaster for people who are using it for massive package building clusters (as well as personal use of course), and receive portmaster-related bug reports from users of an even wider variety of ports. As a result I have a fairly good window into the state of the ports tree at any given time. But all that said, we have almost 23,000 ports. Intimate familiarity with 2,300 ports (a number much larger than I think is reasonably possible for any one person) would still only be 10% of the tree. > It stands to reason that an > increase in the number of ports used would show a corresponding > increase in the number of port failures. Yes, I think you're right about that. >>> And I know that every time I'd start writing a mail about it, my >>> tone would be exactly the same as Jerry chose. With the expected >>> result of "Zomg stop trolling", >> >> First, if you find something broken, please report it; in a calm, >> factual manner; ASAP. That will help us fix it ASAP and help avoid >> other users having to share the same frustration. Second, if you have >> concerns about the direction that things are heading in a more >> general way, feel free to express them as you have here. You may find >> that people agree with you. :) > > And then again, you may not. > >>> or for a change, the ever popular megahit "Patches welcome" >> >> Sometimes that *is* the correct answer though. There is only so much >> that the existing pool of volunteers can do. If we don't get new >> people who are willing to get their hands dirty, the project dies. > > A quick death is often the best course of action. I'm sorry, why is it that you're using FreeBSD at all if you're so overwhelmingly dissatisfied with it? >>> On a weekly basis, again and again, there are port >>> updates being introduced with what seems to be absolutely no testing >>> whatsoever, some breakages take multiple takes on fixing by their >>> respective port maintainers, >> >> While I'm certainly not going to say that mistakes never get made, >> with very nearly 23,000 ports, and a nearly infinite number of >> possible OPTIONS combinations, shaking out all of the corner cases >> can be very difficult for even the most dedicated of maintainers. >> But, see below. >> >>> new versions of major dependencies get introduced only to be rolled >>> back few days later; >> >> If you're talking about the recent ruby update, an enormous amount of >> work went into that prior to the trigger being pulled in an effort to >> make it as smooth as possible. It's unfortunate that in spite of that >> effort there were still some "issues" that were only discovered after >> users rushed to perform the upgrade. In this case backing out the >> change was the responsible course of action. > > If this was an isolated issue, I would certainly agree with you. > However, it has become the norm and not the exception for this sort of > behavior. > >>> So, was really Jerry's tone so trollish? >> >> Yes. There is a world of difference between expressing concern about >> the issue (as you have done) and attacking people on a personal level. > > The root problem is group mentality. Attempting to convey a message > that runs counter to the "group" is like making a statement against the > Pope, or the towel head god, ... and here is where you go completely over the top. This kind of statement does absolutely nothing to add to the substance of your argument, and in fact detracts from whatever valid points you may be making. > or what ever. People immediately become > paranoid and defensive. They act like a group of school girls who have > to have their egos messaged on a daily basis. .... and once again your tone detracts from the valid point you're making. (I.e., that sometimes this reaction does occur, unfortunately.) However, IME what's more common is that the response of "the group" is factually accurate, however much it may be frustrating. >> Now, how do we fix this? It has been suggested numerous times that one >> solution to this problem would be a "stable" ports tree. The idea >> being that after changes have had a chance to shake out for a while >> in the head of the ports tree they get merged back to a stable >> branch. This needs to happen, yesterday. > > What really needs to happen, besides that, is that FreeBSD realize that > there are wireless-N devices in existence, have been for over 5 years, > and actually develop real, fully functional drivers for them. Opps, > sorry, I forgot to blame the manufacturers and, or Microsoft for that > failure. I'll skip the part about getting the device to operate without > having to waste time attempting to get it manually configure just to > make a simple network connect. That would be assuming that there was a > driver available for the device to begin with. Um, yeah, once again, totally unhelpful. First, you're (gratuitously) carping about something completely unrelated to the topic of this thread. Second, you're ignoring some important realities: 1. Of course we're aware 2. Work actually is in progress 3. Drivers don't write themselves If you don't like the pace of the progress you can help, either with contributing code of your own, or contributing financially to the people doing the work. I realize that you're not likely to appreciate either of those answers, but those are the only ones available to you. >> The other thing that will help between now and then is to manage your >> change windows a little more conservatively. Except for >> security-related updates there is almost always zero reason to >> upgrade to new versions of things immediately after they hit the >> ports tree. With all due respect to those involved, one of the >> reasons the ruby thing was such a mess was that users jumped in and >> started upgrading stuff without knowing what they were doing, or why. >> Personally as soon as the notice about the upcoming change went out I >> put the knob in make.conf to keep my systems at 1.8 to make sure I >> wasn't affected. > > I have no problem with that. No one should be forced to update their > system if they choose not to. However, to carry your statement to its > logical conclusion, you should issue a warning that attempting to > update your system carries dire risks ... that's always true ... > since the updates have not been properly tested. ... and this is, once again, unhelpful. > For the record, users knew exactly why the were > updating "ruby", they wanted to. If it was not to be used, then why > release it? What they did not know was that it was going to bite them > in the ass, like so many other updates (cups+gnutls) have lately. If it > had been failing on a few obscure programs, then I could probably say it > was an unfortunate oversight. When it starts failing on major > applications used by a large number of FreeBSD users, then it should be > labels what it is, incompetency. Opps, did I hurt someone's feeling? > Well, you screwed up my system and wasted hours of my valuable time, so > now we are even. And the fact that you think you have the right to lash out like a petulant child is exactly why I'm suggesting that you take a break from posting for a while. Whether postmaster@ attempts to enforce that or not, you might find that getting away from the keyboard is good for you. >> So all this is not to say, "You're wrong!" but instead to try and >> constructively address the concerns you've raised, and hopefully >> provide some suggestions on how to address them. > > That and $1.50 (give or take) will get you a cup of coffee. I don't drink coffee. :) -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Sun Aug 28 23:27:37 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 06FCB1065670 for ; Sun, 28 Aug 2011 23:27:37 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id C1FAB157BBC; Sun, 28 Aug 2011 23:27:35 +0000 (UTC) Message-ID: <4E5ACEE8.1020803@FreeBSD.org> Date: Sun, 28 Aug 2011 16:27:36 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: Micheas Herman References: <20110828140441.0b64c14c@seibercom.net> <20110828201137.GA61262@guilt.hydra> <20110828185007.1a6542a4@seibercom.net> In-Reply-To: X-Enigmail-Version: 1.3.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: Time to remove the GNUTLS option in the print/cups-client port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2011 23:27:37 -0000 On 8/28/2011 4:22 PM, Micheas Herman wrote: > The debate about software patents ... is pretty seriously off-topic. :) -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 00:20:36 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 621B41065670 for ; Mon, 29 Aug 2011 00:20:36 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from cdptpa-omtalb.mail.rr.com (cdptpa-omtalb.mail.rr.com [75.180.132.122]) by mx1.freebsd.org (Postfix) with ESMTP id C51388FC13 for ; Mon, 29 Aug 2011 00:20:35 +0000 (UTC) Received: from cdptpa-omtalb.mail.rr.com ([10.127.143.54]) by cdptpa-qmta02.mail.rr.com with ESMTP id <20110828231817966.WDF3672@cdptpa-qmta02.mail.rr.com> for ; Sun, 28 Aug 2011 23:18:17 +0000 X-Authority-Analysis: v=1.1 cv=UwuCiQyt7jHkjdoYW2VQEWtfJyhst2+aqhtsuVXDAZo= c=1 sm=0 a=1AnfbAj4ZfgA:10 a=kj9zAlcOel0A:10 a=+L5dYfeubEW4PLvjDgtIXQ==:17 a=AfEfcmvjAAAA:8 a=itVrKB2XG0UfzXXN2_oA:9 a=wqz05YJYi0kxpZWGZ2IA:7 a=CjuIK1q_8ugA:10 a=2A2gPVWjU-cA:10 a=+L5dYfeubEW4PLvjDgtIXQ==:117 X-Cloudmark-Score: 0 X-Originating-IP: 76.184.157.127 Received: from [76.184.157.127] ([76.184.157.127:51217] helo=[10.0.0.2]) by cdptpa-oedge04.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id 2E/B1-15749-A7CCA5E4; Sun, 28 Aug 2011 23:17:14 +0000 Date: Sun, 28 Aug 2011 18:17:13 -0500 From: Paul Schmehl To: freebsd-ports@freebsd.org Message-ID: <15B05FD01AE006F6ED5185B4@UTD69340.local> In-Reply-To: <20110828184058.37812e34@seibercom.net> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <20110828184058.37812e34@seibercom.net> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: Ports system quality and trolling X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 00:20:36 -0000 --On August 28, 2011 6:40:58 PM -0400 Jerry wrote: > > I have no problem with that. No one should be forced to update their > system if they choose not to. However, to carry your statement to its > logical conclusion, you should issue a warning that attempting to > update your system carries dire risks since the updates have not been > properly tested. For the record, users knew exactly why the were > updating "ruby", they wanted to. If it was not to be used, then why > release it? What they did not know was that it was going to bite them > in the ass, like so many other updates (cups+gnutls) have lately. If it > had been failing on a few obscure programs, then I could probably say it > was an unfortunate oversight. When it starts failing on major > applications used by a large number of FreeBSD users, then it should be > labels what it is, incompetency. Opps, did I hurt someone's feeling? > Well, you screwed up my system and wasted hours of my valuable time, so > now we are even. > My advice? Go find yourself a better OS and quit bitching about the one you obviously no longer like. Your complaints might be legitimate, but your tone, words and attitude stink. Ooops, did I hurt your feelings? Paul Schmehl, If it isn't already obvious, my opinions are my own and not those of my employer. ****************************************** "When intelligence argues with stupidity and bias, intelligence is bound to lose; intelligence has limits, but stupidity and bias have none." From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 00:24:56 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECD61106564A for ; Mon, 29 Aug 2011 00:24:56 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 90ADB8FC0A for ; Mon, 29 Aug 2011 00:24:56 +0000 (UTC) Received: by qwc9 with SMTP id 9so3738767qwc.13 for ; Sun, 28 Aug 2011 17:24:55 -0700 (PDT) Received: by 10.229.67.105 with SMTP id q41mr5074010qci.7.1314577495667; Sun, 28 Aug 2011 17:24:55 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id r2sm3070195qcv.34.2011.08.28.17.24.53 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Aug 2011 17:24:54 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jerry@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3RnDJP0nBjz2CG4t for ; Sun, 28 Aug 2011 20:24:53 -0400 (EDT) Date: Sun, 28 Aug 2011 20:24:52 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110828202452.6b6b3133@seibercom.net> In-Reply-To: <4E5ACEA5.3040908@FreeBSD.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <20110828184058.37812e34@seibercom.net> <4E5ACEA5.3040908@FreeBSD.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: Ports system quality and trolling X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 00:24:57 -0000 On Sun, 28 Aug 2011 16:26:29 -0700 Doug Barton articulated: > Including postmaster@ on this since IMO Jerry has earned himself a > short vacation from posting privileges. Perhaps you would care to tell me yourself. It could be arranged. > On 8/28/2011 3:40 PM, Jerry wrote: > > On Sun, 28 Aug 2011 14:43:14 -0700 > > Doug Barton articulated: > > > >> On 8/28/2011 1:54 PM, Michal Varga wrote: > >>> On Sun, 2011-08-28 at 15:30 -0400, Sahil Tandon wrote: > >>> > >>> [...] > >>>> Criminal? Indifference? This sort of troll-ish hyperbole is > >>>> decidedly unhelpful. > >> > >> FWIW, I agree with Sahil that this post of Jerry's was over the > >> top, as several of his have been of late. To use the word > >> "criminal" in this context is sufficient all on its own. To accuse > >> people who spend an enormous amount of their own free time trying > >> to make this thing work of being indifferent is just plain rude. > > > > Specifically, I said "borders on criminal". Get your facts straight. > > I'm not sure why you think that makes a difference. The point that > Sahil and I are trying to make is that both your words and your tone > are, at best, unhelpful. > > No one who is involved with actually making things work around here > believes that the system has no flaws. Quite the contrary, we know the > flaws better than most users. But a constant stream of angry messages > doesn't do anything to improve the situation. > > > Second, I was specifically referring to the act, not the > > individual. In addition, "Spending enormous amounts of time" != > > "valid excuse". A mass murderer can spend enormous amounts of time > > planning his crime. Does that absolve him from the actual crime? > > You seem to be operating under the assumption that we owe you > something, and that by failing to provide that thing we owe you we > have wronged you somehow. You may wish to take a step back and > consider that premise in light of what you're paying for this > stuff. :) So, to follow that statement to its logical conclusion, you are inferring that if user is not paying for a product they have no right to expect quality. OK, now I can better understand where you are coming from. > >> FWIW, my experience has not been even close to yours, although I do > >> find broken things occasionally. > > > > I have 1,112+/- ports installed on any given day on one of my > > machines. Your statement, without knowing your exact configuration, > > applications, etcetera is not a valid counter statement. > > And yet, you felt totally comfortable in criticizing it anyway. > Without trying to toot my own horn (since this was a minor part of my > overall point) I have a non-trivial number of ports installed on my > personal systems, support hundreds more on (at least) 4 different > combinations of FreeBSD versions and architectures on a regular > basis, develop portmaster for people who are using it for massive > package building clusters (as well as personal use of course), and > receive portmaster-related bug reports from users of an even wider > variety of ports. As a result I have a fairly good window into the > state of the ports tree at any given time. You have also asked for and I assume received monetary compensation for your services. In other words, get off your high horse. You are not some type of saint. > But all that said, we have almost 23,000 ports. Intimate familiarity > with 2,300 ports (a number much larger than I think is reasonably > possible for any one person) would still only be 10% of the tree. > > > It stands to reason that an > > increase in the number of ports used would show a corresponding > > increase in the number of port failures. > > Yes, I think you're right about that. > > >>> And I know that every time I'd start writing a mail about it, my > >>> tone would be exactly the same as Jerry chose. With the expected > >>> result of "Zomg stop trolling", > >> > >> First, if you find something broken, please report it; in a calm, > >> factual manner; ASAP. That will help us fix it ASAP and help avoid > >> other users having to share the same frustration. Second, if you > >> have concerns about the direction that things are heading in a more > >> general way, feel free to express them as you have here. You may > >> find that people agree with you. :) > > > > And then again, you may not. > > > >>> or for a change, the ever popular megahit "Patches welcome" > >> > >> Sometimes that *is* the correct answer though. There is only so > >> much that the existing pool of volunteers can do. If we don't get > >> new people who are willing to get their hands dirty, the project > >> dies. > > > > A quick death is often the best course of action. > > I'm sorry, why is it that you're using FreeBSD at all if you're so > overwhelmingly dissatisfied with it? Perhaps I did not indite that simply enough for you. I was referring to the port or application that was broken; not the entire OS in its entirety. > >>> On a weekly basis, again and again, there are port > >>> updates being introduced with what seems to be absolutely no > >>> testing whatsoever, some breakages take multiple takes on fixing > >>> by their respective port maintainers, > >> > >> While I'm certainly not going to say that mistakes never get made, > >> with very nearly 23,000 ports, and a nearly infinite number of > >> possible OPTIONS combinations, shaking out all of the corner cases > >> can be very difficult for even the most dedicated of maintainers. > >> But, see below. > >> > >>> new versions of major dependencies get introduced only to be > >>> rolled back few days later; > >> > >> If you're talking about the recent ruby update, an enormous amount > >> of work went into that prior to the trigger being pulled in an > >> effort to make it as smooth as possible. It's unfortunate that in > >> spite of that effort there were still some "issues" that were only > >> discovered after users rushed to perform the upgrade. In this case > >> backing out the change was the responsible course of action. > > > > If this was an isolated issue, I would certainly agree with you. > > However, it has become the norm and not the exception for this sort > > of behavior. > > > >>> So, was really Jerry's tone so trollish? > >> > >> Yes. There is a world of difference between expressing concern > >> about the issue (as you have done) and attacking people on a > >> personal level. > > > > The root problem is group mentality. Attempting to convey a message > > that runs counter to the "group" is like making a statement against > > the Pope, or the towel head god, > > ... and here is where you go completely over the top. This kind of > statement does absolutely nothing to add to the substance of your > argument, and in fact detracts from whatever valid points you may be > making. I can switch from formal academic language to a charmingly colloquial style depending on the audience. It got your attention so it obviously worked. > > or what ever. People immediately become > > paranoid and defensive. They act like a group of school girls who > > have to have their egos messaged on a daily basis. > > .... and once again your tone detracts from the valid point you're > making. (I.e., that sometimes this reaction does occur, > unfortunately.) However, IME what's more common is that the response > of "the group" is factually accurate, however much it may be > frustrating. {see my previous rebuttal} > >> Now, how do we fix this? It has been suggested numerous times that > >> one solution to this problem would be a "stable" ports tree. The > >> idea being that after changes have had a chance to shake out for a > >> while in the head of the ports tree they get merged back to a > >> stable branch. This needs to happen, yesterday. > > > > What really needs to happen, besides that, is that FreeBSD realize > > that there are wireless-N devices in existence, have been for over > > 5 years, and actually develop real, fully functional drivers for > > them. Opps, sorry, I forgot to blame the manufacturers and, or > > Microsoft for that failure. I'll skip the part about getting the > > device to operate without having to waste time attempting to get it > > manually configure just to make a simple network connect. That > > would be assuming that there was a driver available for the device > > to begin with. > > Um, yeah, once again, totally unhelpful. First, you're (gratuitously) > carping about something completely unrelated to the topic of this > thread. Second, you're ignoring some important realities: > > 1. Of course we're aware > 2. Work actually is in progress > 3. Drivers don't write themselves > > If you don't like the pace of the progress you can help, either with > contributing code of your own, or contributing financially to the > people doing the work. I realize that you're not likely to appreciate > either of those answers, but those are the only ones available to you. > > >> The other thing that will help between now and then is to manage > >> your change windows a little more conservatively. Except for > >> security-related updates there is almost always zero reason to > >> upgrade to new versions of things immediately after they hit the > >> ports tree. With all due respect to those involved, one of the > >> reasons the ruby thing was such a mess was that users jumped in and > >> started upgrading stuff without knowing what they were doing, or > >> why. Personally as soon as the notice about the upcoming change > >> went out I put the knob in make.conf to keep my systems at 1.8 to > >> make sure I wasn't affected. > > > > I have no problem with that. No one should be forced to update their > > system if they choose not to. However, to carry your statement to > > its logical conclusion, you should issue a warning that attempting > > to update your system carries dire risks > > ... that's always true ... > > > since the updates have not been properly tested. > > ... and this is, once again, unhelpful. Helpful or not, it is never-the-less factually correct. > > For the record, users knew exactly why the were > > updating "ruby", they wanted to. If it was not to be used, then why > > release it? What they did not know was that it was going to bite > > them in the ass, like so many other updates (cups+gnutls) have > > lately. If it had been failing on a few obscure programs, then I > > could probably say it was an unfortunate oversight. When it starts > > failing on major applications used by a large number of FreeBSD > > users, then it should be labels what it is, incompetency. Opps, did > > I hurt someone's feeling? Well, you screwed up my system and wasted > > hours of my valuable time, so now we are even. > > And the fact that you think you have the right to lash out like a > petulant child is exactly why I'm suggesting that you take a break > from posting for a while. Whether postmaster@ attempts to enforce > that or not, you might find that getting away from the keyboard is > good for you. Darn, did I upset you? The FreeBSD community in general has a wide and variegated opinion as to what is wrong with the OS in general. Attempting to stifle that is about as useless as an ostrich sticking their head in the sand. The difference here is in the basic concept of how you perceive FreeBSD in general. You see what it is and consider it good enough. I see what it could potentially be and want more. If anyone dares to challenge your concepts you crawl into your shell, display paranoid behavior and cry for help. Your refusal to accept the irrefragable proof that there are serious problems with the OS in general contributing to the basic decay in the system as a whole. Now, if FreeBSD wants to put on their web page a prominent disclaimer warning potential users that it doesn't test the applications it disseminates to its user base, has no intention of doing so, and could not care less if it causes the end user a loss of time and or money, then I promise I will never again bring up this subject again. Oh, by the way, YES, I do have the right to lash out. I am not your slave you moron. I fought for the right to speak and be free and I will not let an asshole like you tell me who I can speak to or what I can say. Get use to it. And if I hurt your feeling, good! > >> So all this is not to say, "You're wrong!" but instead to try and > >> constructively address the concerns you've raised, and hopefully > >> provide some suggestions on how to address them. > > > > That and $1.50 (give or take) will get you a cup of coffee. > > I don't drink coffee. :) I kind of sensed that. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 00:40:00 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31C58106566C for ; Mon, 29 Aug 2011 00:40:00 +0000 (UTC) (envelope-from code@apotheon.net) Received: from oproxy9.bluehost.com (oproxy9.bluehost.com [IPv6:2605:dc00:100:2::a2]) by mx1.freebsd.org (Postfix) with SMTP id E499E8FC1A for ; Mon, 29 Aug 2011 00:39:59 +0000 (UTC) Received: (qmail 26760 invoked by uid 0); 29 Aug 2011 00:39:59 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by oproxy9.bluehost.com with SMTP; 29 Aug 2011 00:39:59 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.net; s=default; h=In-Reply-To:Content-Type:Mime-Version:References:Message-ID:Subject:To:From:Date; bh=wX4D8GrWIo9X0FWOc5QDAbWGqrTAO+vtx+vQmD8nZa4=; b=X05kSpF62i6W6/YSBNP3A46AxRxvJuLoiZyfRO+jGdlxPTphLxIjsd7DpNEKfIIiuLaes6iZ0fXXz90GgyWM2UYxZ93kgBNmGj+9NCHQseJrjyvjUvz+nKE5U+577mVj; Received: from c-24-8-180-234.hsd1.co.comcast.net ([24.8.180.234] helo=kukaburra.hydra) by box543.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1QxptO-0003aU-Gv for freebsd-ports@freebsd.org; Sun, 28 Aug 2011 18:39:59 -0600 Received: by kukaburra.hydra (sSMTP sendmail emulation); Sun, 28 Aug 2011 18:21:37 -0600 Date: Sun, 28 Aug 2011 18:21:37 -0600 From: Chad Perrin To: freebsd-ports@freebsd.org Message-ID: <20110829002137.GA61876@guilt.hydra> Mail-Followup-To: freebsd-ports@freebsd.org References: <20110828140441.0b64c14c@seibercom.net> <20110828201137.GA61262@guilt.hydra> <20110828185007.1a6542a4@seibercom.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline In-Reply-To: <20110828185007.1a6542a4@seibercom.net> User-Agent: Mutt/1.4.2.3i X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.org} {sentby:smtp auth 24.8.180.234 authed with ren@apotheon.org} Subject: Re: Time to remove the GNUTLS option in the print/cups-client port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 00:40:00 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 28, 2011 at 06:50:07PM -0400, Jerry wrote: > On Sun, 28 Aug 2011 14:04:42 -0700 > >=20 > > The only benefit that I have heard of is that gnutls works around at > > least one of the patent issues that openssl has. > >=20 > > (the probably both infringe on dozens, if not hundreds, of erroneously > > issued American patents) >=20 > Erroneously issued in the sense that you are suppose to be paying for > the right to use it and are attempting to circumvent the law or issued > in the sense that someone else had all ready been issued a valid patent? >=20 > Or, could it be that you feel someone should work for an indeterminate > amount of time, invest his/her monies and take the risks of developing a > new product and then be deprived of the right to make a return on their > investment just so you can use the article for free? I think I know the > answer to that one. Probably "erroneously issued" in that you should stop trolling, because no matter how much someone likes the patent system in principle, the US patent system has become horribly broken in practice. The world's biggest patent-holders that actually produce anything pretty much all agree that the system is horribly broken, and mostly collect patents for defensive use. --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk5a25EACgkQ9mn/Pj01uKXPmwCfZrllCTUHddT5uNLgFkDFri5v LGIAoOFilxKlUx07ys46Y6lRDcGXr65D =BJVy -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 01:03:15 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60D8F1065670 for ; Mon, 29 Aug 2011 01:03:15 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo201.cox.net (eastrmfepo201.cox.net [68.230.241.216]) by mx1.freebsd.org (Postfix) with ESMTP id F1B718FC13 for ; Mon, 29 Aug 2011 01:03:14 +0000 (UTC) Received: from eastrmimpo02.cox.net ([68.1.16.120]) by eastrmfepo201.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20110829010314.BPHX32549.eastrmfepo201.cox.net@eastrmimpo02.cox.net> for ; Sun, 28 Aug 2011 21:03:14 -0400 Received: from serene.no-ip.org ([98.164.83.25]) by eastrmimpo02.cox.net with bizsmtp id S13D1h00L0YnB6A0213DQG; Sun, 28 Aug 2011 21:03:14 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020205.4E5AE552.000F,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=ax4i8a8snyEA9uWfgWYmXW+3D+RWNhitQWxcW0Jxd9c= c=1 sm=1 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=2vO5UZG1h46htWAnE/rx2g==:17 a=R8vwMfuDAAAA:8 a=6I5d2MoRAAAA:8 a=kviXuzpPAAAA:8 a=IA5yr9RiMo5oKg-261gA:9 a=-vjw7ZNr-txsIkhWUeQA:7 a=CjuIK1q_8ugA:10 a=SV7veod9ZcQA:10 a=4vB-4DCPJfMA:10 a=2vO5UZG1h46htWAnE/rx2g==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from cox.net (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id p7T13DFg090551 for ; Sun, 28 Aug 2011 20:03:13 -0500 (CDT) (envelope-from conrads@cox.net) Date: Sun, 28 Aug 2011 20:03:08 -0500 From: "Conrad J. Sabatier" To: freebsd-ports@freebsd.org Message-ID: <20110828200308.04d60912@cox.net> In-Reply-To: <4E59BC38.9060809@chen.org.nz> References: <4E59BC38.9060809@chen.org.nz> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Missing libproxy.la? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 01:03:15 -0000 On Sun, 28 Aug 2011 15:55:36 +1200 Jonathan Chen wrote: > Hi all, > > I read UPDATING and did a: > # portupgrade -rf libnotify-0.\* libproxy-0.\* > > and this mostly succeeded except where it failed. In particular > x11/gnome-panel complains: > CCLD clock-applet > gnome-libtool: link: cannot find the library > `/usr/local/lib/libproxy.la' or unhandled argument > `/usr/local/lib/libproxy.la' > > This leaves me with a slightly unusable system. Reinstalling libproxy > still does not resolve the problem. How can I make this work again? > > Cheers. FWIW, there was a very similar thread in the FreeBSD-gnome list recently, in which Jung-uk Kim posted a solution using a short shell recipe. Worth checking out. See the thread: missing libproxy.la: brasero builds, gnome-applets doesn't HTH -- Conrad J. Sabatier conrads@cox.net From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 02:05:18 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD6ED106566B for ; Mon, 29 Aug 2011 02:05:18 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo203.cox.net (eastrmfepo203.cox.net [68.230.241.218]) by mx1.freebsd.org (Postfix) with ESMTP id 744438FC13 for ; Mon, 29 Aug 2011 02:05:18 +0000 (UTC) Received: from eastrmimpo02.cox.net ([68.1.16.120]) by eastrmfepo203.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20110829020517.PFSP32702.eastrmfepo203.cox.net@eastrmimpo02.cox.net> for ; Sun, 28 Aug 2011 22:05:17 -0400 Received: from serene.no-ip.org ([98.164.83.25]) by eastrmimpo02.cox.net with bizsmtp id S25H1h0080YnB6A0225H7q; Sun, 28 Aug 2011 22:05:17 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020205.4E5AF3DD.00D6,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=ax4i8a8snyEA9uWfgWYmXW+3D+RWNhitQWxcW0Jxd9c= c=1 sm=1 a=MkVqW7lO938A:10 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=2vO5UZG1h46htWAnE/rx2g==:17 a=FP58Ms26AAAA:8 a=kviXuzpPAAAA:8 a=Mlg-9IgK4rXLx0hf9IEA:9 a=CjuIK1q_8ugA:10 a=4vB-4DCPJfMA:10 a=KB3AhU7pfj782sz8:21 a=_11XZt6j8LsaSP-F:21 a=2vO5UZG1h46htWAnE/rx2g==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from cox.net (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id p7T25GHX090787 for ; Sun, 28 Aug 2011 21:05:16 -0500 (CDT) (envelope-from conrads@cox.net) Date: Sun, 28 Aug 2011 21:05:11 -0500 From: "Conrad J. Sabatier" To: freebsd-ports@FreeBSD.org Message-ID: <20110828210511.3d2e0604@cox.net> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: MASTER_SITE_SOURCEFORGE: how do *you* handle it? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 02:05:18 -0000 I'm wondering how other ports maintainers are dealing with their definitions of MASTER_SITES=, DISTFILES=, DISTNAME=, etc. with regards to Sourceforge. In browsing a number of projects recently on Sourceforge, I've noticed that the paths to project distfiles are now using the element "projects" rather than "project". What I'm looking for is how to declare things in a clean and elegant fashion in a port's Makefile to handle these cases, one that will hopefully not require any revisions for later upgrades. Is it necessary to just scrap the "SF" definition entirely and hardcode the URL? In addition, I've run across a few projects that use slightly differing versions of the project name, either somewhere in the path or for the distfile name itself. For example, looking at the "scidvspc" project earlier today, I noticed this: The link for the distfile is defined as: http://sourceforge.net/projects/scidvspc/files/source/scid_vs_pc-4.5.tgz/download Clicking the download link, one is presented with alternatives in case the download doesn't start automatically. The "mirror" link: https://sourceforge.net/settings/mirror_choices?projectname=scidvspc&filename=source/scid_vs_pc-4.5.tgz The "direct link": https://downloads.sourceforge.net/project/scidvspc/source/scid_vs_pc-4.5.tgz?r=&ts=1314582468&use_mirror=superb-sea2 Frankly, I'm baffled as to how our current definition of "MASTER_SITES=SF/" is supposed to handle all of this. Can anyone point me towards a source of enlightenment? :-) Thanks! -- Conrad J. Sabatier conrads@cox.net From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 02:19:49 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CEF31065672; Mon, 29 Aug 2011 02:19:49 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id B83348FC18; Mon, 29 Aug 2011 02:19:48 +0000 (UTC) Received: by fxe4 with SMTP id 4so5205751fxe.13 for ; Sun, 28 Aug 2011 19:19:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=lvvlhnxxZfDRh/12iOJVTrOeajcUwjcfonfO5T0gVhc=; b=FBouVjqt4qEkfnhnatpWTtonNc1eh0rjyoOucqnEbOyXu4b8Q7P8uyTVXySiaqNMnk mF0DQI6MEUSSLBlejOGNTmkGU8+7FXygnpJ6o47MsVHQIp0j8OnltjgrwVUhVJOGPjaJ aOCmQQOh4GcFWV1Qa2r2gMLBIizmmlP2Y4Dqk= Received: by 10.223.102.11 with SMTP id e11mr6248975fao.8.1314584387489; Sun, 28 Aug 2011 19:19:47 -0700 (PDT) Received: from [10.0.101.2] (hotel.grandberoun.cz [90.182.105.26]) by mx.google.com with ESMTPS id z12sm484900fah.6.2011.08.28.19.19.45 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Aug 2011 19:19:46 -0700 (PDT) From: Michal Varga To: Doug Barton In-Reply-To: <4E5AB672.4020607@FreeBSD.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> Content-Type: text/plain; charset="UTF-8" Organization: Stonehenge Date: Mon, 29 Aug 2011 04:19:44 +0200 Message-ID: <1314584384.82067.323.camel@xenon> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Re: Ports system trolling X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 02:19:49 -0000 On Sun, 2011-08-28 at 14:43 -0700, Doug Barton wrote: > On 8/28/2011 1:54 PM, Michal Varga wrote: > > On Sun, 2011-08-28 at 15:30 -0400, Sahil Tandon wrote: > > > > [...] > >> Criminal? Indifference? This sort of troll-ish hyperbole is decidedly > >> unhelpful. > > FWIW, I agree with Sahil that this post of Jerry's was over the top, as > several of his have been of late. To use the word "criminal" in this > context is sufficient all on its own. To accuse people who spend an > enormous amount of their own free time trying to make this thing work of > being indifferent is just plain rude. While I'm the last one to be trying to belittle the effort put by some people into ports (or FreeBSD in general), lately, this particular mantra is starting to get a little overused. I know that it almost borders with criminal (I see what I did there) even trying to suggest that, but seriously - just because someone "did a lot" this or other day (week, month, or year) for FreeBSD, doesn't make them *untouchable* to critique for the rest of their lives. This is very wrong approach and such way of thinking only leads to a pretty rotten (and pretty elitist) community. Note that I mean it generally, without pointing to any current case at all. It's just... Recently it's being invoked so much that it's on the verge of losing any meaning. Jerry (ok, I'm probably starting to sound like his mother, writing third email about him and all that, but it'd be hard to get to some point without pointing to him directly) clearly stated what was his concern - that there should have been a note put in UPDATING the moment the issue was discovered (I would personally mention *testing* somewhere in there, but that's me), and that the chosen approach - "waiting for a maintainer approval to give his permission for a fix" when you already have there a situation with mailing list filling up with more and more reports about breaks (meaning, people out there actually get bitten by it right at this very moment, losing them time, losing them money, losing them hair, choose what applies) - is pathetic. Now. Would I personally chose the same words? Definitely not, it's far from being polite and I could easily imagine the shitstorm following it (now just see the shitstorm following me using the word shitstorm). But it's not about the one single word from the whole thread, we are not elementary school children. It's about the situation behind it, and that's the one that really needs addressing, not a bunch of heated words. In such situation, I (personally, again) wouldn't consider this even warranting a quiet off-list warning, it's not like this guy is cross spamming threads and randomly attacking people out there just for fun. Late edit: I was only speaking about the situation happening up until starting this particular reply, now I see things got a little bit more heated in meantime (most of which I didn't read, yet), but that's already out of scope of this. Just to make things clear. > > On some of my desktop setups, I keep about 900-1000 installed ports (and > > there are some ~200-300 for servers in general). There already seems not > > to be a single week, even once, without some MAJOR breakage that always > > takes hours (sometimes days) to track down and fix by my own ... > > FWIW, my experience has not been even close to yours, although I do find > broken things occasionally. Well, as far as I remember, you weren't using FreeBSD as a desktop OS (or at least weren't much), so this probably contributes to your (better) experience with recent ports. Of course it's just something out of the back of my head, I may be mistaken, but I think I remember you stating it some time, someplace. Anyway - with some 1000 ports on a full feature desktop system (that's like 1/20th of all we have in total, right), be it Gnome or KDE (god help with both), the breakages are massive, and almost constant. On the other hand, this practically doesn't happen on any major Linux distribution (and no, I'm not that guy arguing we should move ports to debian binary packages, there's no need to worry); this wasn't happening in 4.x days too, this wasn't happening in 5.x days and everyone knows what a.... loving miracle.... FreeBSD 5 was, this wasn't happening in (early) 6.x days (much), but especially from 7 onwards, and the last year, having a 1000-ports desktop system is just a plain nightmare. There is constantly *something* broken. And not like it's just one thing at a time. Do I have stats for it? No, obviously. If I was making paper notes of that, I'd have eradicated few rainforests by now (errr, so no, I don't have stats for it, but I have my daily experiences maintaining both server and desktop BSDs without a break since 2000, so that leaves some memory here and there). [Rest moved to a standalone email, as it's somewhat long and stuff.] m. -- Michal Varga, Stonehenge (Gmail account) From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 02:35:03 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 5D2C8106564A for ; Mon, 29 Aug 2011 02:35:03 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id C63FA1510C6; Mon, 29 Aug 2011 02:35:01 +0000 (UTC) Message-ID: <4E5AFAD4.4040609@FreeBSD.org> Date: Sun, 28 Aug 2011 19:35:00 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <20110828184058.37812e34@seibercom.net> <4E5ACEA5.3040908@FreeBSD.org> <20110828202452.6b6b3133@seibercom.net> In-Reply-To: <20110828202452.6b6b3133@seibercom.net> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jerry Subject: Re: Ports system quality and trolling X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 02:35:03 -0000 On 08/28/2011 17:24, Jerry wrote: > On Sun, 28 Aug 2011 16:26:29 -0700 > Doug Barton articulated: > >> Including postmaster@ on this since IMO Jerry has earned himself a >> short vacation from posting privileges. > > Perhaps you would care to tell me yourself. It could be arranged. Errrr ... huh? I really hope that's not supposed to be an implied threat of physical violence. Otherwise I completely fail to understand what you're getting at. >> On 8/28/2011 3:40 PM, Jerry wrote: >>> On Sun, 28 Aug 2011 14:43:14 -0700 >>> Doug Barton articulated: >>> >>>> On 8/28/2011 1:54 PM, Michal Varga wrote: >>>>> On Sun, 2011-08-28 at 15:30 -0400, Sahil Tandon wrote: >>>>> >>>>> [...] >>>>>> Criminal? Indifference? This sort of troll-ish hyperbole is >>>>>> decidedly unhelpful. >>>> >>>> FWIW, I agree with Sahil that this post of Jerry's was over the >>>> top, as several of his have been of late. To use the word >>>> "criminal" in this context is sufficient all on its own. To accuse >>>> people who spend an enormous amount of their own free time trying >>>> to make this thing work of being indifferent is just plain rude. >>> >>> Specifically, I said "borders on criminal". Get your facts straight. >> >> I'm not sure why you think that makes a difference. The point that >> Sahil and I are trying to make is that both your words and your tone >> are, at best, unhelpful. >> >> No one who is involved with actually making things work around here >> believes that the system has no flaws. Quite the contrary, we know the >> flaws better than most users. But a constant stream of angry messages >> doesn't do anything to improve the situation. >> >>> Second, I was specifically referring to the act, not the >>> individual. In addition, "Spending enormous amounts of time" != >>> "valid excuse". A mass murderer can spend enormous amounts of time >>> planning his crime. Does that absolve him from the actual crime? >> >> You seem to be operating under the assumption that we owe you >> something, and that by failing to provide that thing we owe you we >> have wronged you somehow. You may wish to take a step back and >> consider that premise in light of what you're paying for this >> stuff. :) > > So, to follow that statement to its logical ... I don't think that word means what you think it means ... > conclusion, you are > inferring that if user is not paying for a product they have no right > to expect quality. OK, now I can better understand where you are coming > from. I would never tell someone what they can, or cannot expect, that would be absurd. What I can say is, given the circumstances an expectation that all things FreeBSD will be perfect is not reasonable, and likely to lead to disappointment. >>>> FWIW, my experience has not been even close to yours, although I do >>>> find broken things occasionally. >>> >>> I have 1,112+/- ports installed on any given day on one of my >>> machines. Your statement, without knowing your exact configuration, >>> applications, etcetera is not a valid counter statement. >> >> And yet, you felt totally comfortable in criticizing it anyway. >> Without trying to toot my own horn (since this was a minor part of my >> overall point) I have a non-trivial number of ports installed on my >> personal systems, support hundreds more on (at least) 4 different >> combinations of FreeBSD versions and architectures on a regular >> basis, develop portmaster for people who are using it for massive >> package building clusters (as well as personal use of course), and >> receive portmaster-related bug reports from users of an even wider >> variety of ports. As a result I have a fairly good window into the >> state of the ports tree at any given time. > > You have also asked for and I assume received monetary compensation > for your services. In other words, get off your high horse. You are not > some type of saint. I never said I was. I'm simply pointing out that I actually do have a fairly good grasp of the situation. I'm also very lucky in terms of having been given financial support for some of my FreeBSD work, which is extremely unusual amongst our developer community. >>> The root problem is group mentality. Attempting to convey a message >>> that runs counter to the "group" is like making a statement against >>> the Pope, or the towel head god, >> >> ... and here is where you go completely over the top. This kind of >> statement does absolutely nothing to add to the substance of your >> argument, and in fact detracts from whatever valid points you may be >> making. > > I can switch from formal academic language to a charmingly > colloquial style depending on the audience. It got your attention so it > obviously worked. I don't think that word means what you think it means. :) More to the point, I chose to make a last-ditch effort to try and communicate with you in a civil manner even though a lot of other people have written you off already (meaning, they are simply deleting your posts unread). I see now that I've wasted my time. > Darn, did I upset you? The FreeBSD community in general has a > wide and variegated opinion as to what is wrong with the OS in general. > Attempting to stifle that is about as useless as an ostrich sticking > their head in the sand. Who said anything about stifling opinion, or developers not understanding that there are problems? Did you read my post? Particularly this bit: No one who is involved with actually making things work around here believes that the system has no flaws. Quite the contrary, we know the flaws better than most users. But a constant stream of angry messages doesn't do anything to improve the situation. What some of us are trying to get you to see is that: a) Your expectations are probably not realistic, and b) Your tone is both offensive, and unacceptable. > The difference here is in the basic concept of > how you perceive FreeBSD in general. You see what it is and consider it > good enough. LOL .... I've been working on improving it for 15 years, and advocating for a variety of major changes and improvements both publicly and privately. I'm one of the *last* people who would ever say that FreeBSD is "good enough." > Oh, by the way, YES, I do have the right to lash out. I am not your > slave you moron. I fought for the right to speak and be free and I will > not let an asshole like you tell me who I can speak to or what I can > say. Get use to it. And if I hurt your feeling, good! So, (last time), I don't think "free speech" means what you think it means. You have the right to say anything you want, but you don't have the right to use someone else's resources to do it. Doug (or put another way, you have the right to speak, you don't have the "right" to be heard) -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 02:43:23 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82C07106564A; Mon, 29 Aug 2011 02:43:23 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id D008B8FC12; Mon, 29 Aug 2011 02:43:22 +0000 (UTC) Received: by fxe4 with SMTP id 4so5219003fxe.13 for ; Sun, 28 Aug 2011 19:43:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=3fu7MaIfR67btZEOGbDl6q9J+4F2NjQGgBgNvg80g10=; b=W4z37S4BC2d+bIRHHYG4UXZz3vmuKCGmKz8Av2UFB8wCc61CTRPxUBVu8R+x/QNcMB 0spAv3vwO449jKxfH5Sxudvr40Lzieue7v5lm3TxqHl3IXK+s5BQnmrODViutnXdgxM9 GLph3FZ1kySofj8/iqe+HPclAODOGs0Z2hwmY= Received: by 10.223.31.77 with SMTP id x13mr3091831fac.124.1314585801629; Sun, 28 Aug 2011 19:43:21 -0700 (PDT) Received: from [10.0.101.2] (hotel.grandberoun.cz [90.182.105.26]) by mx.google.com with ESMTPS id e2sm3354634fah.25.2011.08.28.19.43.19 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Aug 2011 19:43:20 -0700 (PDT) From: Michal Varga To: Doug Barton In-Reply-To: <4E5AB672.4020607@FreeBSD.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> Content-Type: text/plain; charset="UTF-8" Organization: Stonehenge Date: Mon, 29 Aug 2011 04:43:18 +0200 Message-ID: <1314585798.82067.338.camel@xenon> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 02:43:23 -0000 On Sun, 2011-08-28 at 14:43 -0700, Doug Barton wrote: > If you're talking about the recent ruby update, an enormous amount of > work went into that prior to the trigger being pulled in an effort to > make it as smooth as possible. It's unfortunate that in spite of that > effort there were still some "issues" that were only discovered after > users rushed to perform the upgrade. In this case backing out the change > was the responsible course of action. I didn't want to mention the Ruby update specifically, because then the debate would turn into this or that specific issue, and honestly, maybe a year ago, I'd still think that it's really just about a specific issue in every single case. But over a course of time, I'm now inclined to see it more as a full picture, and that picture is, sadly, "something just constantly being broken" (yes, in the big picture). No matter how much some individuals invest into FreeBSD ports, the overall loss of quality control is pretty visible, and again - no single individual will fix that all. No two of them, no dozen of them. This is something that has to be fixed on a higher level, and a nice step in that direction would be a complete revamp of (currently like, close to none?) quality control procedures, and then require port maintainers (and commiters) to actually follow them, every time. Even if they are volunteers, and everyone contributes on their own time and resources, sure, but I would, personally, rather have 10000 (or 1000, if there's no other choice) fully working ports again, instead of those 22000 there all the time untested, broken, or missing features or introducing regressions every minor update. > Now, how do we fix this? It has been suggested numerous times that one > solution to this problem would be a "stable" ports tree. The idea being > that after changes have had a chance to shake out for a while in the > head of the ports tree they get merged back to a stable branch. This > needs to happen, yesterday. Stable ports tree *alone* as a solution is a waste of time (yes, I know how ridiculous that statement sounds in this thread, but-). There are only two possible outcomes of this, one worse than another: 1. Nobody will be using the "testing" tree, because it will be constantly superbroken (like, much more than ports are now). In theory, at least for some people, such tree would sound like a great idea to "get your latest Firefox / Xorg / Gimp / whatever you like", but the dependency tree you will need to pull will basically overwrite half of your stable ports tree anyway, so you can as well keep using "testing" on full time. Which in turn means having everything broken all the time. Which in turn means, rarely anybody will be using it outside of port maintainer/commiter circles, which means you won't get any additional testing anyway. And / Or: 2. Stable tree will become terribly outdated, as every just a little bit complicated app comes with 300 dependencies (think of GTK/QT and all the way down from there). This means - do I want, as a maintainer, promote this new (and properly tested) Firefox to the stable tree? Well, but I will need you guys to promote me that latest GTK and right, recent gstreamer, and, uhmmm, some recent smb stuff and just a few more, and oh, they won't work without their latest dependencies too so in turn, we either end up with a ~100 port promote to the stable tree, or we will wait a few months until all the needed components get there on their own. So -stable tree will rot and nobody will want to use it because "man, it has like already three releases old Pidgin, what good is that for?" (which in fact is a security threat by itself, so probably not the very best example, but you get the basic idea). What is needed much more than two different port trees, is a cooldown period combined with *required* testing by port maintainers (and by port commiters), with some actual consequences if they fail to do so. Now this again sounds ridiculous (to some), shooting volunteers against the wall for breaking rules, so that alone is why this will never happen. But the fact is, that in the current state of ports, we advertise something that doesn't really work as a whole. As the current rules go now, port gets a go as long as it compiles, and that's why we have now those beautiful 22000 ports to advertise. Except that there is nothing that requires a port maintainer to know how their port is being used: Again, I'm not going to point fingers, but there was this little dependency port once that after one upgrade totally broke about every single GTK application. How so? Did the maintainer even briefly test it before submitting the new version? As it eventually turned out in a private conversation, he actually tested it pretty thoroughly, with one exception... Port maintainer was a server user and never even ran FreeBSD as a desktop system. And there is this minor issue, that his port is also one of the dependencies that gets pulled into every single GTK application, right? So during his testing, nothing wrong showed up with the new version, as with the limited (non-GTK) scope that he was ever using (and testing) his port for, everything was fine. On the other hand, for desktop users, the new port broke practically everything. Yay. So how would one prevent situations like these without *forcing* volunteers to do job out of the scope they volunteered for? What is the solution for that? Requiring them to test for something they don't even use, or even know? What's the better option then? Having the guy drop maintainership if he is not interested in fully maintaining it as a dependency? Or advertising a working Gnome (KDE, XFCE, whatever) Desktop on FreeBSD, and having down there someone maintaining a low level dependency that can completely break the *desktop OS* every single update, while obviously he is not even testing for it? This is just one of those situations that won't get magically solved by just another ports tree. Obviously, one additional "testing" tree will catch some of the breakages (depending on number of people willing to deal with unstable ports, and in my humble expectations, that would be like: - almost nobody for server configurations (because why) - almost nobody for desktop configurations, because that would mean desktop that's not even starting 90% of the time, so why even bother ), but being the visionary I am, I think it won't change as much as it now shows on a paper. There already are testing repos for various ports (Gnome, Xorg, VirtualBox, etc.), and barely anyone uses them. What is needed more are new, much stricter maintainership and committing policies than there are in effect now, and seriously - who would dare to even suggest such thing and still live through the mass burning and exodus following it? > The other thing that will help between now and then is to manage your > change windows a little more conservatively. Except for security-related > updates there is almost always zero reason to upgrade to new versions of > things immediately after they hit the ports tree. With all due respect > to those involved, one of the reasons the ruby thing was such a mess was > that users jumped in and started upgrading stuff without knowing what > they were doing, or why. Personally as soon as the notice about the > upcoming change went out I put the knob in make.conf to keep my systems > at 1.8 to make sure I wasn't affected. I'd have to strongly disagree with this point of view. Thing to keep in mind is, that at any point in time, there is always *something* that had just hit the tree only moments ago. What if I had those 30 ports to upgrade (or make it 300 if one upgrades once over a month), all of them being cross/dependencies along the path requiring some of each other, and now I have to cherry pick them and blacklist/exclude some based on their arrival time... That's crazy. Many people haven't even heard about half of those dependencies down the tree (and why should they), and how many of them even don't know that Ruby is a programming language (why should they, it's crap anyway) and that 1.9 is a major upgrade. Why would someone upgrading a web browser, music player (or more specifically, *bringing all his applications up to date*) know about some Ruby and what it is and that 1.8 vs 1.9 can also be a major deal-breaker, when for him, it's just some random dependency 30 levels below? Thinking about upgrading ports in this way would require every single port user to become a maintainer of... everything. What you propose is the opposite of cooldown period - you'd require every ports user keeping track on every single port installed and know 'how important' in the overall scheme it is and when it's safe to update it and when you have to schedule a week-long alarm to let it cool down a bit until it's (probably) safe to use it (as some other people got probably burned and hopefully reported it). This is really a bad idea. When ports hit the tree, they should either be stable and ready to use, or not be there at all. m. -- Michal Varga, Stonehenge (Gmail account) From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 02:43:51 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F504106566B; Mon, 29 Aug 2011 02:43:51 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id F22F58FC0C; Mon, 29 Aug 2011 02:43:50 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 57E225619E; Sun, 28 Aug 2011 21:43:50 -0500 (CDT) Date: Sun, 28 Aug 2011 21:43:50 -0500 From: Mark Linimon To: freebsd-ports@freebsd.org Message-ID: <20110829024350.GB2964@lonesome.com> References: <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <20110828184058.37812e34@seibercom.net> <4E5ACEA5.3040908@FreeBSD.org> <20110828202452.6b6b3133@seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110828202452.6b6b3133@seibercom.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: linimon@FreeBSD.org Subject: Re: Ports system quality and trolling X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 02:43:51 -0000 On Sun, Aug 28, 2011 at 08:24:52PM -0400, Jerry wrote: > You have also asked for and I assume received monetary compensation > for your services. In Doug's case: a small percentage of his contributions over the years (e.g. for improvements to portmaster, which he had already written). I'm sure he'll correct me, but IIRC he has not received any pay for the great deal of work he has done over many years on the rc subsystem, bind, and the many other things he has worked on. I doubt even 1% of the time he's spent on the project has been compensated. > The difference here is in the basic concept of how you perceive > FreeBSD in general. You see what it is and consider it good enough. Well, now I've lived to see everything: someone imputing that Doug Barton thinks that FreeBSD is exactly OK as it is :-) Since you probably don't know me, let me be obvious. I'm on portmgr. And anyone on portmgr can tell you with an absolute knowable certainty that Doug Barton does not think FreeBSD is exactly OK as it is. I mean, if you really think that, you haven't been paying attention. Now, any casual reading of the mailing list archives will ably demonstrate that Doug and I have different styles and don't exactly get along. But if you think he's happy with the way things are, or doesn't care about the quality of the system ... I'm sorry, that's just farcical. You're living inside a reality-distortion field. > Oh, by the way, YES, I do have the right to lash out. I am not your > slave you moron. Nor is he yours. Or anyone else working on this project (including myself). But what he, and I, and a lot of other people who work on this project, deserve is to be treated in a civil fashion. In your postings that I've seen this week (no, I haven't read them all), you've made it quite clear that you have no interest in doing so. So: you have exercised your right to speak. And now, for myself, I'm going to exercise my right to not listen, and get on with useful work [*] rather than any more mailing list blather. In case that was tl;dr: plonk. mcl [*] so far since your first posting in this thread, that's consisted of resetting all the i386 package build nodes, cleaning up and restarting the i386-9 package build, writing a document for an upcoming infrastructure change, and the usual PR triage and maintenance work. From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 03:25:18 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 541C5106566B for ; Mon, 29 Aug 2011 03:25:18 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 9B50614FED4; Mon, 29 Aug 2011 03:25:07 +0000 (UTC) Message-ID: <4E5B0692.6020605@FreeBSD.org> Date: Sun, 28 Aug 2011 20:25:06 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0 MIME-Version: 1.0 To: Michal Varga References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314584384.82067.323.camel@xenon> In-Reply-To: <1314584384.82067.323.camel@xenon> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Re: Ports system trolling X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 03:25:18 -0000 On 08/28/2011 19:19, Michal Varga wrote: > On Sun, 2011-08-28 at 14:43 -0700, Doug Barton wrote: >> On 8/28/2011 1:54 PM, Michal Varga wrote: >>> On Sun, 2011-08-28 at 15:30 -0400, Sahil Tandon wrote: >>> >>> [...] >>>> Criminal? Indifference? This sort of troll-ish hyperbole is decidedly >>>> unhelpful. >> >> FWIW, I agree with Sahil that this post of Jerry's was over the top, as >> several of his have been of late. To use the word "criminal" in this >> context is sufficient all on its own. To accuse people who spend an >> enormous amount of their own free time trying to make this thing work of >> being indifferent is just plain rude. > > While I'm the last one to be trying to belittle the effort put by some > people into ports (or FreeBSD in general), lately, this particular > mantra is starting to get a little overused. I can't speak for what others have said, but read what I said carefully. I have never said that people who make mistakes shouldn't be held accountable for them. What I *am* saying is that calling people names is rude. > (meaning, people out there actually get bitten by it right at > this very moment, losing them time, losing them money, losing them hair, > choose what applies) - is pathetic. People who are at risk of losing money if upgrades don't go well should not be doing updates the moment they hit the tree. Sorry to be so blunt, but that's experience talking. :) > Now. Would I personally chose the same words? Definitely not, it's far > from being polite and I could easily imagine the shitstorm following it > (now just see the shitstorm following me using the word shitstorm). But > it's not about the one single word from the whole thread, we are not > elementary school children. It's about the situation behind it, and > that's the one that really needs addressing, not a bunch of heated > words. I agree that the facts need to be discussed, and have both said so and attempted to do just that. But, allowing inappropriate conduct to go uncommented on will simply lead to more of the same. I've been on lists like that, it's not pretty. > Well, as far as I remember, you weren't using FreeBSD as a desktop OS > (or at least weren't much), This is really my day for lolz. :) I have been using FreeBSD as my primary desktop OS for about 13 or 14 years, and have been using -current for most of that time. I also advocate strongly for people to do that, especially developers (and especially especially committers). I'll reply to your other points in your other thread. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 03:29:10 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D7AA106566C for ; Mon, 29 Aug 2011 03:29:10 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail27.syd.optusnet.com.au (mail27.syd.optusnet.com.au [211.29.133.168]) by mx1.freebsd.org (Postfix) with ESMTP id 8B5E78FC14 for ; Mon, 29 Aug 2011 03:29:09 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail27.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p7T3T6he022979 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 29 Aug 2011 13:29:07 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id p7T3T5P9085087 for ; Mon, 29 Aug 2011 13:29:05 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id p7T3T5Uc085086 for freebsd-ports@freebsd.org; Mon, 29 Aug 2011 13:29:05 +1000 (EST) (envelope-from peter) Date: Mon, 29 Aug 2011 13:29:05 +1000 From: Peter Jeremy To: freebsd-ports@freebsd.org Message-ID: <20110829032905.GA84993@server.vk2pj.dyndns.org> References: <20110826050535.GB64576@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline In-Reply-To: <20110826050535.GB64576@server.vk2pj.dyndns.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: Problems building devel/gobject-introspection X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 03:29:10 -0000 --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2011-Aug-26 15:05:35 +1000, Peter Jeremy = wrote: >I am having problems building devel/gobject-introspection on one >9.0-BETA1 host. I can build it without problems on 8.2 and another >9.0-BETA1 box. In all cases, I'm using gcc and amd64. The failure >is: =2E.. >Since this only happens on one box, it's presumably something I've done >but I'm not sure what. Google hasn't helped. Does anyone have any >ideas on where to start looking? Turns out that my python was dodgy. Deleting /var/db/ports/python27/options and rebuilding with default options fixed it. I thought I was using the defaults before but forgot to check the contents before deleting it. Thanks to Ruslan Mahmatkhanov for his suggestions. --=20 Peter Jeremy --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk5bB4EACgkQ/opHv/APuIfG0wCcDHFWBFb2tjTKYj/OETAcsnWe Nw4AoKLD0Mz75tGX6eSZE2S9PXVLuVFP =YXj2 -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3-- From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 03:48:22 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94352106566B; Mon, 29 Aug 2011 03:48:22 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id E879B8FC15; Mon, 29 Aug 2011 03:48:21 +0000 (UTC) Received: by fxe4 with SMTP id 4so5254171fxe.13 for ; Sun, 28 Aug 2011 20:48:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=VpWzMSK5vPmuxLOEVQXs2uBwEX62riBvLmv8SYldwoc=; b=vzCqbIZy4mFcYbqUgupPhlqPSL0r5KF0gelUd8gCw8keKnK0ZYqyhU9nn/+p+HsmAI CBf2Z+fif2/j4iXQK6ia6Y4MT2REPy6a9L+azEBpxn+1/h2Wuj8Esjk5FbebLyyyR8kc 9mRdEIOjVLRjcjF8aeHP8stQQRxhzbUQQmqO8= Received: by 10.223.54.17 with SMTP id o17mr6429203fag.61.1314589700768; Sun, 28 Aug 2011 20:48:20 -0700 (PDT) Received: from [10.0.101.2] (hotel.grandberoun.cz [90.182.105.26]) by mx.google.com with ESMTPS id r12sm3421617fam.14.2011.08.28.20.48.18 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Aug 2011 20:48:19 -0700 (PDT) From: Michal Varga To: Doug Barton In-Reply-To: <4E5B0692.6020605@FreeBSD.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314584384.82067.323.camel@xenon> <4E5B0692.6020605@FreeBSD.org> Content-Type: text/plain; charset="UTF-8" Organization: Stonehenge Date: Mon, 29 Aug 2011 05:48:17 +0200 Message-ID: <1314589697.82067.348.camel@xenon> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Re: Ports system trolling X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 03:48:22 -0000 On Sun, 2011-08-28 at 20:25 -0700, Doug Barton wrote: > > > Well, as far as I remember, you weren't using FreeBSD as a desktop OS > > (or at least weren't much), > > This is really my day for lolz. :) I have been using FreeBSD as my > primary desktop OS for about 13 or 14 years, and have been using > -current for most of that time. I also advocate strongly for people to > do that, especially developers (and especially especially committers). I see, my bad then. Might be that you were just stating that you're not using Gnome, or KDE, or something along the line and it left a wrong fingerprint in my memory. That's why I said that I'm not really sure. Still, if that's the case, I wonder how your ports experience in that regard could be so good. And substituting a full desktop environment for like xorg+twm+vi doesn't count as a desktop in my book :) (Ok, just trolling. But who knows...) m. -- Michal Varga, Stonehenge (Gmail account) From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 04:01:01 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id DA41C106566C for ; Mon, 29 Aug 2011 04:01:01 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 9FEDC14DBF4; Mon, 29 Aug 2011 04:01:00 +0000 (UTC) Message-ID: <4E5B0EFB.6000900@FreeBSD.org> Date: Sun, 28 Aug 2011 21:00:59 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0 MIME-Version: 1.0 To: Michal Varga References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314585798.82067.338.camel@xenon> In-Reply-To: <1314585798.82067.338.camel@xenon> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 04:01:02 -0000 On 08/28/2011 19:43, Michal Varga wrote: > On Sun, 2011-08-28 at 14:43 -0700, Doug Barton wrote: > >> If you're talking about the recent ruby update, an enormous amount of >> work went into that prior to the trigger being pulled in an effort to >> make it as smooth as possible. It's unfortunate that in spite of that >> effort there were still some "issues" that were only discovered after >> users rushed to perform the upgrade. In this case backing out the change >> was the responsible course of action. > > I didn't want to mention the Ruby update specifically, because then the > debate would turn into this or that specific issue, and honestly, maybe > a year ago, I'd still think that it's really just about a specific issue > in every single case. > > But over a course of time, I'm now inclined to see it more as a full > picture, and that picture is, sadly, "something just constantly being > broken" (yes, in the big picture). I can certainly understand how you could come to that conclusion, but like I said, that hasn't been even close to my experience, nor do I think it's representative of even a significant percentage of our users. > No matter how much some individuals > invest into FreeBSD ports, the overall loss of quality control is pretty > visible, and again - no single individual will fix that all. No two of > them, no dozen of them. This is something that has to be fixed on a > higher level, and a nice step in that direction would be a complete > revamp of (currently like, close to none?) quality control procedures, > and then require port maintainers (and commiters) to actually follow > them, every time. I think it would be a mistake to believe that we don't have any quality control at all. I do think it's reasonable to ask whether what we have is adequate, and if not, how can it be improved. That's why I'm suggesting the stable ports tree idea as a step in that direction. > Even if they are volunteers, and everyone contributes on their own time > and resources, sure, but I would, personally, rather have 10000 (or > 1000, if there's no other choice) fully working ports again, instead of > those 22000 there all the time untested, broken, or missing features or > introducing regressions every minor update. Now you're talking! :) This is one of the reasons I have been so supportive of (and made some minor contributions to) the effort to deprecate stale ports. There is also a lot more work to be done in this area. That said, it's you and me against all of the (very!) vocal people who believe that we shouldn't ever deprecate anything. Go figure. :) >> Now, how do we fix this? It has been suggested numerous times that one >> solution to this problem would be a "stable" ports tree. The idea being >> that after changes have had a chance to shake out for a while in the >> head of the ports tree they get merged back to a stable branch. This >> needs to happen, yesterday. > > Stable ports tree *alone* as a solution is a waste of time (yes, I know > how ridiculous that statement sounds in this thread, but-). There are > only two possible outcomes of this, one worse than another: > > 1. Nobody will be using the "testing" tree, because it will be > constantly superbroken (like, much more than ports are now). I'd like to think that we can do a little better than that. :) I also think that a non-trivial number of users will want to use the "latest and greatest" so I'm not quite as pessimistic about this as you are. > And / Or: > > 2. Stable tree will become terribly outdated, as every just a little bit > complicated app comes with 300 dependencies (think of GTK/QT and all the > way down from there). This means - do I want, as a maintainer, promote > this new (and properly tested) Firefox to the stable tree? Well, but I > will need you guys to promote me that latest GTK and right, recent > gstreamer, and, uhmmm, some recent smb stuff and just a few more, and > oh, they won't work without their latest dependencies too so in turn, we > either end up with a ~100 port promote to the stable tree, or we will > wait a few months until all the needed components get there on their > own. So -stable tree will rot and nobody will want to use it because > "man, it has like already three releases old Pidgin, what good is that > for?" (which in fact is a security threat by itself, so probably not the > very best example, but you get the basic idea). This I think is a very valid concern, and one that will have to be addressed with vigor. That said, I think that there are a lot of users who would find value in a ports tree that is overwhelmingly stable, as opposed to always being the latest and greatest. Also, see below. > Again, I'm not going to point fingers, but there was this little > dependency port once that after one upgrade totally broke about every > single GTK application. How so? Did the maintainer even briefly test it > before submitting the new version? As it eventually turned out in a > private conversation, he actually tested it pretty thoroughly, with one > exception... Port maintainer was a server user and never even ran > FreeBSD as a desktop system. And there is this minor issue, that his > port is also one of the dependencies that gets pulled into every single > GTK application, right? So during his testing, nothing wrong showed up > with the new version, as with the limited (non-GTK) scope that he was > ever using (and testing) his port for, everything was fine. On the other > hand, for desktop users, the new port broke practically everything. Yay. > > So how would one prevent situations like these without *forcing* > volunteers to do job out of the scope they volunteered for? What is the > solution for that? Requiring them to test for something they don't even > use, or even know? What's the better option then? Having the guy drop > maintainership if he is not interested in fully maintaining it as a > dependency? Or advertising a working Gnome (KDE, XFCE, whatever) Desktop > on FreeBSD, and having down there someone maintaining a low level > dependency that can completely break the *desktop OS* every single > update, while obviously he is not even testing for it? > > This is just one of those situations that won't get magically solved by > just another ports tree. On the contrary, this is *exactly* the kind of thing that my idea would catch. More completely, my idea is something along the lines of: 1. Establish a baseline of what works with the existing ports tree via -exp run(s). 2. Branch the tree 3. New commits go to the head of the tree 4. "Periodically," we do an -exp run with the stable tree plus selected updates from head. If the tree is no worse off than the baseline promote the tested updates, update the baseline, lather, rinse, repeat. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 04:27:33 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2DA31065672 for ; Mon, 29 Aug 2011 04:27:33 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (m209-73.dsl.rawbw.com [198.144.209.73]) by mx1.freebsd.org (Postfix) with ESMTP id CFFAF8FC19 for ; Mon, 29 Aug 2011 04:27:33 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.5/8.14.5) with ESMTP id p7T4RXVS002628; Sun, 28 Aug 2011 21:27:33 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.5/8.14.5/Submit) id p7T4RWQM002627; Sun, 28 Aug 2011 21:27:32 -0700 (PDT) (envelope-from david) Date: Sun, 28 Aug 2011 21:27:32 -0700 From: David Wolfskill To: Jeroen Message-ID: <20110829042732.GB1915@albert.catwhisker.org> References: <4E5AB569.4060703@virtualhost.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8GpibOaaTibBMecb" Content-Disposition: inline In-Reply-To: <4E5AB569.4060703@virtualhost.nl> User-Agent: Mutt/1.4.2.3i Cc: freebsd-ports@freebsd.org Subject: Re: firefox 6: mercurial seems to be missing as depency X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 04:27:34 -0000 --8GpibOaaTibBMecb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 28, 2011 at 11:38:49PM +0200, Jeroen wrote: > Hi all, >=20 > When updating firefox to the latest version (from ports) it complained=20 > about hg not being found. Apparently a dependency to mercurial is=20 > missing. I haven't checked why, installing it resolved it. I find the above perplexing, as I have firefox-6.0_1,1 installed on a few machines, and none has ever had anything involving mercurial installed or running on it: I see no such dependency in my environment(s). Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --8GpibOaaTibBMecb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk5bFTQACgkQmprOCmdXAD3AsgCfett3rFxr4tSgV82GS3qcoBSn XkYAnA8aoPO9KZtMH27XYLuhnni5Z1bT =EImh -----END PGP SIGNATURE----- --8GpibOaaTibBMecb-- From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 05:35:01 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CBBB1065670; Mon, 29 Aug 2011 05:35:01 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6212D8FC16; Mon, 29 Aug 2011 05:35:00 +0000 (UTC) Received: by fxe4 with SMTP id 4so5311583fxe.13 for ; Sun, 28 Aug 2011 22:34:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=64E0SMf3HHDPa/4R4BCquMAB3mjti7intmMY+25duXg=; b=bk1UsSNg+eL2XYZoIm1lUTDPmbEEWw2aYzP+IVVWQt99rbqAtDoP+log7rVN0MuRks 7mKI3wOvPDj3slDHjSWjm1H+pYlRaxEaDPRKTBBeRmLWhcjZJST6IIchDlSisb6F5IYZ Utm3jNZvaVHA1iW1bONFIIw4kQ6Aq+GyxL6A8= Received: by 10.223.7.7 with SMTP id b7mr6456601fab.9.1314596099209; Sun, 28 Aug 2011 22:34:59 -0700 (PDT) Received: from [10.0.101.2] (hotel.grandberoun.cz [90.182.105.26]) by mx.google.com with ESMTPS id 22sm3472395fay.28.2011.08.28.22.34.57 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Aug 2011 22:34:58 -0700 (PDT) From: Michal Varga To: Doug Barton In-Reply-To: <4E5B0EFB.6000900@FreeBSD.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314585798.82067.338.camel@xenon> <4E5B0EFB.6000900@FreeBSD.org> Content-Type: text/plain; charset="UTF-8" Organization: Stonehenge Date: Mon, 29 Aug 2011 07:34:56 +0200 Message-ID: <1314596096.82067.419.camel@xenon> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 05:35:01 -0000 On Sun, 2011-08-28 at 21:00 -0700, Doug Barton wrote: > I think it would be a mistake to believe that we don't have any quality > control at all. I do think it's reasonable to ask whether what we have > is adequate, and if not, how can it be improved. That's why I'm > suggesting the stable ports tree idea as a step in that direction. Now to be a bit more clearer, I didn't mean it in the sense that anyone can (or will) happily commit random crap to ports just to be done with it and go to movies, that wasn't my intention to suggest. By quality control, I meant first *ensuring* that the new port version will actually do something meaningful, other than, say, segfault everything depending on it. And not introducing it to the general population before that is ensured. See below. > > This is just one of those situations that won't get magically solved by > > just another ports tree. > > On the contrary, this is *exactly* the kind of thing that my idea would > catch. More completely, my idea is something along the lines of: > > 1. Establish a baseline of what works with the existing ports tree via > -exp run(s). > 2. Branch the tree > 3. New commits go to the head of the tree > 4. "Periodically," we do an -exp run with the stable tree plus selected > updates from head. If the tree is no worse off than the baseline promote > the tested updates, update the baseline, lather, rinse, repeat. And there comes the definition of a *working* port. It was pretty easy back when most ports consisted of five dependencies and like three of them were Perl. If it compiled, in 99% cases, it also ran. This no longer works in the scope of huge desktop environments like Gnome/KDE (or XFCE and other lesser players). Obviously, some server configurations suffer from this too - think of Java deploys and similar monstrosities with hundreds of dependencies. Testing only for "Does it still build?" won't help much anymore if the new version silently broke one of the APIs and while Apache still runs with it fine, no desktop user won't be able to boot his OS anymore (that is, boot into the desktop, which for number of people *is* the OS). Or let's just create a hypothetical situation: - We have this popular graphics library called Foo, which is a dependency of basically everything - web browsers, image viewers, editors (GIMP, Inkscape, whatever)... - Port maintainer decides to introduce a new version, but doesn't actually use or care for all the features Foo provides, so he tests it with his favorite image viewer, which he maintains too. So all looks good, port compiles flawlessly, even his vacation photos show ok, so all is done, right? (Raise hand everyone who just recognized at least 100 of the last commits where something instantly broke.) - Except that slowly over days and weeks after introduction, people now start asking on the list (or even worse, FreeBSD forums that nobody reads), why is their web browser missing images since the last week, or why his GIMP crashes every time he tries to edit his work-related 32-bit per channel designs (there's an internal joke in that). - While nobody probably cares much about that guy and his missing browser images, what would you tell to the GIMP guy? That he should have waited longer before upgrading the (for him, 30 levels deep) "Foo" dependency? With furious client breathing down his neck and everything? Yes, he will be eventually able to track the issue down and downgrade Foo to some working version, only after losing a full work day. I know, it's all his fault for not getting a Mac, but I'm still being in the hypothetical land so this still counts. Now where I'm trying to get by this: Either we want to have ports as a "big repository of colorful stuff that even builds", or we want to have some actual products that people can use after they build them. And that needs an additional level of quality control that FreeBSD currently, and horribly, lacks (patches welcome, I know). I'm not saying that this can be solved overnight and definitely not by me, but there's at least one thing that can make the world better in that regard, if some enterprising soul introduced it, I don't know, maybe over a coming decade: That is, forcing maintainers to work together to maintain a whole product, not everyone randomly updating crucial components just because they feel like it's a nice day to do it. - That particular maintainer of Foo graphics library should be forced, by threats of violence, to consult his upgrade with all consumers of his port (that is, other maintainers of ports that use it as a dependency). - Maintainers of those ports should be forced, dunno, possibly by threats of violence, to actually test that proposed library upgrade with their ports and approve or block the upgrade (or somehow work together on a solution, stuff like that). - AND there should be an enforced infrastructure to make all that somewhat easy for them, with -exp runs being a part of that process (and a non-optional part to that). - And only after all involved parties finish all testing and approve the dependency upgrade, commit the port for Joe Public to finally start using it. Without at least this as a corner stone of quality control, ports will only keep rotting further, the more the applications will keep getting complex and entangled in hundreds and hundreds of dependencies. The simple fact that port builds isn't, and wasn't for a long time now, an indicator that the port really works. Or that the *ports* really work as a whole. m. -- Michal Varga, Stonehenge (Gmail account) From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 06:01:31 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82CBC106564A for ; Mon, 29 Aug 2011 06:01:31 +0000 (UTC) (envelope-from m@micheas.net) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 1BA9D8FC0A for ; Mon, 29 Aug 2011 06:01:30 +0000 (UTC) Received: by wwi36 with SMTP id 36so5341253wwi.31 for ; Sun, 28 Aug 2011 23:01:30 -0700 (PDT) Received: by 10.216.39.133 with SMTP id d5mr2581550web.23.1314597690101; Sun, 28 Aug 2011 23:01:30 -0700 (PDT) MIME-Version: 1.0 Sender: m@micheas.net Received: by 10.216.168.68 with HTTP; Sun, 28 Aug 2011 23:01:10 -0700 (PDT) In-Reply-To: <1314596096.82067.419.camel@xenon> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314585798.82067.338.camel@xenon> <4E5B0EFB.6000900@FreeBSD.org> <1314596096.82067.419.camel@xenon> From: Micheas Herman Date: Sun, 28 Aug 2011 23:01:10 -0700 X-Google-Sender-Auth: Mx6ovA1MOpi8jjcDkbHC0hKhj9Q Message-ID: To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 06:01:31 -0000 On Sun, Aug 28, 2011 at 10:34 PM, Michal Varga wrote: > On Sun, 2011-08-28 at 21:00 -0700, Doug Barton wrote: >> I think it would be a mistake to believe that we don't have any quality >> control at all. I do think it's reasonable to ask whether what we have >> is adequate, and if not, how can it be improved. That's why I'm >> suggesting the stable ports tree idea as a step in that direction. I don't know that a stable ports tree is mathematically possible. I would suspect that if one was to consider all of the build options for some of the larger items, (even semi small ones like php) Most possible binaries have never been built much less tested. php as mod_php and fast-cgi and cli and cgi with and without su exec with support for imagemagick and gd and all the possible version of those and which of them have conflicts with the yaz extension (that only brick and mortar libraries use)? And this is very frequently used port. Might a more bazar type approach where the ports tree gave an option to report the build environment and a fail/success that is keyed to the cvs version of the ports? This is just a brainstorm, but considering the pain that debian QA causes debian developers, and the orders of magnitude larger task that QAing the FreeBSD ports tree would be makes me wonder if self reporting wouldn't be a direction to go in. Further down this path, a website could display for any given time the status of the ports tree: failed to build with defaults. -- red built with defaults and crashed upon loading -- yellow built and passed a simple did it run with out crashing test -- light green built and > (arbitrarily chosen number by the ports team) people reported that it works. There seems to be a lot of emotion around this so maybe there is some extra energy that could make something like this happen? Also, anecdotal the ports tree is always/rarely broken, doesn't really help figure out how to make the ports tree better, and know if the change made things better or worse. Just my to pennies american.. Micheas From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 06:18:41 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 862EC106564A for ; Mon, 29 Aug 2011 06:18:41 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 132CB8FC08 for ; Mon, 29 Aug 2011 06:18:40 +0000 (UTC) Received: by fxe4 with SMTP id 4so5340566fxe.13 for ; Sun, 28 Aug 2011 23:18:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FA6ftHllfXpKksh2ZpE7e/P/ZjoUFVilGoEGhXItUNA=; b=iVLdZYRVAY4+pl3M6AYCmXbab9NRv7+wx0/Gzd6JXd+ugIhgQj/wKhym7bbZWa5wnK tahpVA1LOUgxZ1t11sTTr9IxBn32C/3W1KRQrcLt+25XPq3RjE2RnfbiXkT+lxDfNnQR WQ3Jy3qkq06VmuJGk0e+BUfoAQ5DwFc4YXoLg= MIME-Version: 1.0 Received: by 10.223.16.205 with SMTP id p13mr2341361faa.69.1314598719563; Sun, 28 Aug 2011 23:18:39 -0700 (PDT) Received: by 10.223.120.72 with HTTP; Sun, 28 Aug 2011 23:18:39 -0700 (PDT) In-Reply-To: References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314585798.82067.338.camel@xenon> <4E5B0EFB.6000900@FreeBSD.org> <1314596096.82067.419.camel@xenon> Date: Mon, 29 Aug 2011 01:18:39 -0500 Message-ID: From: Adam Vande More To: Micheas Herman Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-ports@freebsd.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 06:18:41 -0000 On Mon, Aug 29, 2011 at 1:01 AM, Micheas Herman wrote: > This is just a brainstorm, but considering the pain that debian QA causes > debian developers, and the orders of magnitude larger task that QAing > the FreeBSD ports tree would be makes me wonder if self reporting wouldn't > be a direction to go in. > What about a utility to list all installed packages built with non-default options? This might be helpful in identifying edge cases. -- Adam Vande More From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 06:30:43 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 68837106566C for ; Mon, 29 Aug 2011 06:30:43 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id A9C021527D9; Mon, 29 Aug 2011 06:30:39 +0000 (UTC) Message-ID: <4E5B320E.8010503@FreeBSD.org> Date: Sun, 28 Aug 2011 23:30:38 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0 MIME-Version: 1.0 To: Michal Varga References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314585798.82067.338.camel@xenon> <4E5B0EFB.6000900@FreeBSD.org> <1314596096.82067.419.camel@xenon> In-Reply-To: <1314596096.82067.419.camel@xenon> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 06:30:43 -0000 On 08/28/2011 22:34, Michal Varga wrote: > On Sun, 2011-08-28 at 21:00 -0700, Doug Barton wrote: >> I think it would be a mistake to believe that we don't have any quality >> control at all. I do think it's reasonable to ask whether what we have >> is adequate, and if not, how can it be improved. That's why I'm >> suggesting the stable ports tree idea as a step in that direction. > > Now to be a bit more clearer, I didn't mean it in the sense that anyone > can (or will) happily commit random crap to ports just to be done with > it and go to movies, that wasn't my intention to suggest. > > By quality control, I meant first *ensuring* that the new port version > will actually do something meaningful, other than, say, segfault > everything depending on it. And not introducing it to the general > population before that is ensured. The point that I'm trying to get across is that by and large maintainers already do that. The fact that in spite of those efforts problems still happen is part and parcel of the vast complexity of the number of ports that we have multiplied by the number of options. That's not to say we can't (and shouldn't) do better. > Testing only for "Does it still build?" won't help much anymore if the > new version silently broke one of the APIs and while Apache still runs > with it fine Believe it or not, I understand that. :) The problem is that extensive run-time testing is not within the realm of possibility without an army of volunteers. Do you want to organize that effort? > Now where I'm trying to get by this: > > Either we want to have ports as a "big repository of colorful stuff that > even builds", or we want to have some actual products that people can > use after they build them. And that needs an additional level of quality > control that FreeBSD currently, and horribly, lacks (patches welcome, I > know). That sounds like PC-BSD to me. (Seriously, give it a try) Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 07:07:09 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF1C210656E7; Mon, 29 Aug 2011 07:07:08 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 40B638FC14; Mon, 29 Aug 2011 07:07:07 +0000 (UTC) Received: by bkat8 with SMTP id t8so5280929bka.13 for ; Mon, 29 Aug 2011 00:07:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=N3ro6nWr6lZV1G1V7q6Em1LORM7xiQcFiCaOOxbGy5Y=; b=GWX5S9ItmW6PabPKSEIM5DkodLmMlfTJibkuSJ9OjKet3UC3o4AqcMT09qztqLxLZZ EfEF+VYxUDmtYIptQnFPMWTbeg/5uRMdULZwnDinVeWi2fCcq7up68vrWRVwN+l5Zksp uL7armm/HrbziP52DpPQY8wGYPH1EBWSGPIz4= Received: by 10.204.132.212 with SMTP id c20mr1873100bkt.352.1314601626923; Mon, 29 Aug 2011 00:07:06 -0700 (PDT) Received: from [10.0.101.2] (hotel.grandberoun.cz [90.182.105.26]) by mx.google.com with ESMTPS id f6sm1101108bkw.63.2011.08.29.00.07.04 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 29 Aug 2011 00:07:05 -0700 (PDT) From: Michal Varga To: Doug Barton In-Reply-To: <4E5B320E.8010503@FreeBSD.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314585798.82067.338.camel@xenon> <4E5B0EFB.6000900@FreeBSD.org> <1314596096.82067.419.camel@xenon> <4E5B320E.8010503@FreeBSD.org> Content-Type: text/plain; charset="UTF-8" Organization: Stonehenge Date: Mon, 29 Aug 2011 09:07:02 +0200 Message-ID: <1314601622.82067.441.camel@xenon> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 07:07:09 -0000 On Sun, 2011-08-28 at 23:30 -0700, Doug Barton wrote: > > Testing only for "Does it still build?" won't help much anymore if the > > new version silently broke one of the APIs and while Apache still runs > > with it fine > > Believe it or not, I understand that. :) The problem is that extensive > run-time testing is not within the realm of possibility without an army > of volunteers. Do you want to organize that effort? That would be the very opposite of the concept I just described. While extensive volunteer testing, if considered standalone, is surely not a bad idea (just that for some reason it never happens anywhere), it lies in a completely different scope than port maintainers *not* randomly upgrading dependencies just on their own without regard to other ports they will affect (and in many cases break, be it on build level, or run-time level). I just double checked if I possibly forgot to send the other half of my email, but nope, it's all right there. > > Now where I'm trying to get by this: > > > > Either we want to have ports as a "big repository of colorful stuff that > > even builds", or we want to have some actual products that people can > > use after they build them. And that needs an additional level of quality > > control that FreeBSD currently, and horribly, lacks (patches welcome, I > > know). > > That sounds like PC-BSD to me. (Seriously, give it a try) Now that's like saying I might want to try *Linux and OS X too (I occasionally use both, just not as my primary desktop, which is FreeBSD). Speaking about PC-BSD, I'm not exactly fan of KDE and also, I find the concept of PBI packages highly offending. Then again, I can't see how would PC-BSD help in this case as it's the exact opposite of what I described. The fact that PC-BSD just tracks ports and builds self-contained packages from them doesn't automagically make them better product, it's still the same ports, but now just horribly packaged too. m. -- Michal Varga, Stonehenge (Gmail account) From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 07:17:15 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 375E3106566B for ; Mon, 29 Aug 2011 07:17:15 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 268B3178EFB; Mon, 29 Aug 2011 07:17:13 +0000 (UTC) Message-ID: <4E5B3CF8.4020805@FreeBSD.org> Date: Mon, 29 Aug 2011 00:17:12 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0 MIME-Version: 1.0 To: Michal Varga References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314585798.82067.338.camel@xenon> <4E5B0EFB.6000900@FreeBSD.org> <1314596096.82067.419.camel@xenon> <4E5B320E.8010503@FreeBSD.org> <1314601622.82067.441.camel@xenon> In-Reply-To: <1314601622.82067.441.camel@xenon> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 07:17:15 -0000 On 08/29/2011 00:07, Michal Varga wrote: > On Sun, 2011-08-28 at 23:30 -0700, Doug Barton wrote: >>> Testing only for "Does it still build?" won't help much anymore if the >>> new version silently broke one of the APIs and while Apache still runs >>> with it fine >> >> Believe it or not, I understand that. :) The problem is that extensive >> run-time testing is not within the realm of possibility without an army >> of volunteers. Do you want to organize that effort? > > That would be the very opposite of the concept I just described. While > extensive volunteer testing, if considered standalone, is surely not a > bad idea (just that for some reason it never happens anywhere), it lies > in a completely different scope than port maintainers *not* randomly > upgrading dependencies just on their own without regard to other ports > they will affect (and in many cases break, be it on build level, or > run-time level). Ok, I'll be more blunt. We don't do that on purpose, obviously. But expecting maintainers to do what you're describing is unrealistic. The only thing it would accomplish is a "stable" ports tree because nothing would ever get updated. :) Seriously ... I get what you're saying, I'm not even saying it's a bad idea, I'm just saying that we lack the person-power to do it now, and are unlikely to ever get to that point. I would also point out that from a project management standpoint developers rarely make good QA people. To do this right you really would want separate teams. >>> Now where I'm trying to get by this: >>> >>> Either we want to have ports as a "big repository of colorful stuff that >>> even builds", or we want to have some actual products that people can >>> use after they build them. And that needs an additional level of quality >>> control that FreeBSD currently, and horribly, lacks (patches welcome, I >>> know). >> >> That sounds like PC-BSD to me. (Seriously, give it a try) > > Now that's like saying I might want to try *Linux and OS X too (I > occasionally use both, just not as my primary desktop, which is > FreeBSD). Those are good alternatives as well. I use FreeBSD as my desktop, but it's painful, and I wouldn't do it at all if I didn't need to. FreeBSD needs to get better in this area, but I seriously doubt it will ever be as easy and painless as something like ubuntu. > Speaking about PC-BSD, I'm not exactly fan of KDE They have other alternatives now. > and also, I find the concept of PBI packages highly offending. Well that's just silly, but I'm not going to argue this point, I've spent enough time on this thread already. > Then again, I can't see how > would PC-BSD help in this case as it's the exact opposite of what I > described. The fact that PC-BSD just tracks ports and builds > self-contained packages from them And you're sure that's all they do? Seriously, I think you should give it another look. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 07:55:26 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DF5E106566C; Mon, 29 Aug 2011 07:55:26 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id BC0718FC16; Mon, 29 Aug 2011 07:55:25 +0000 (UTC) Received: by bkat8 with SMTP id t8so5316204bka.13 for ; Mon, 29 Aug 2011 00:55:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=c4kX9U+iEvkKZHOP28MujUf5I+AtcmSYlPZsWoojv9Y=; b=R+zVGo+T6eiZ/2Zk5E7eOsrEJKm+2KubNCsgFpck0gQnSryAsgkP+t6SPKu2IJ/llu F/gEDzAGaDmbwyrpC1FBsbVxWTR8RxwICasqq47lfvX+O0G2BZQIsOO+AMET3PB3a2In A0MS0AjduqJRLKjy4ALlByMbcz4sfifH6po4c= Received: by 10.204.128.67 with SMTP id j3mr594190bks.71.1314604524759; Mon, 29 Aug 2011 00:55:24 -0700 (PDT) Received: from [10.0.101.2] (hotel.grandberoun.cz [90.182.105.26]) by mx.google.com with ESMTPS id a3sm1127442bkd.2.2011.08.29.00.55.22 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 29 Aug 2011 00:55:23 -0700 (PDT) From: Michal Varga To: Doug Barton In-Reply-To: <4E5B3CF8.4020805@FreeBSD.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314585798.82067.338.camel@xenon> <4E5B0EFB.6000900@FreeBSD.org> <1314596096.82067.419.camel@xenon> <4E5B320E.8010503@FreeBSD.org> <1314601622.82067.441.camel@xenon> <4E5B3CF8.4020805@FreeBSD.org> Content-Type: text/plain; charset="UTF-8" Organization: Stonehenge Date: Mon, 29 Aug 2011 09:55:21 +0200 Message-ID: <1314604521.82067.461.camel@xenon> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 07:55:26 -0000 On Mon, 2011-08-29 at 00:17 -0700, Doug Barton wrote: > are unlikely to ever get to that point. I would also point out that from > a project management standpoint developers rarely make good QA people. > To do this right you really would want separate teams. As I said, that's not something that's in my power to change. In any case, it just leads (and always will lead) only to this outcome: > Those are good alternatives as well. I use FreeBSD as my desktop, but > it's painful, and I wouldn't do it at all if I didn't need to. Other OSes/projects, for some reason, are able to manage their maintainer base to much better results, and it shows. It can either be done here too, or the situation can be ignored for another five, ten years, until FreeBSD fades into obscurity, eventually getting known only as 'that OS where nothing works'. It's an issue that won't go away on its own. m. -- Michal Varga, Stonehenge (Gmail account) From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 09:14:39 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 032B8106566C for ; Mon, 29 Aug 2011 09:14:39 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by mx1.freebsd.org (Postfix) with SMTP id 616868FC08 for ; Mon, 29 Aug 2011 09:14:37 +0000 (UTC) Received: (qmail invoked by alias); 29 Aug 2011 09:14:36 -0000 Received: from g227158159.adsl.alicedsl.de (EHLO apollo.emma.line.org) [92.227.158.159] by mail.gmx.net (mp025) with SMTP; 29 Aug 2011 11:14:36 +0200 X-Authenticated: #428038 X-Provags-ID: V01U2FsdGVkX18gFyRci8cgV8IIIxlJkSGMhUthUFl6FoboJo5spJ GTcObMRmCSyWTZ Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id C0AF523CF4F for ; Mon, 29 Aug 2011 11:14:34 +0200 (CEST) Message-ID: <4E5B587A.7090508@gmx.de> Date: Mon, 29 Aug 2011 11:14:34 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <20110828184058.37812e34@seibercom.net> <4E5ACEA5.3040908@FreeBSD.org> <20110828202452.6b6b3133@seibercom.net> In-Reply-To: <20110828202452.6b6b3133@seibercom.net> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: Ports system quality and trolling X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 09:14:39 -0000 Am 29.08.2011 02:24, schrieb Jerry: > On Sun, 28 Aug 2011 16:26:29 -0700 > Doug Barton articulated: >> You seem to be operating under the assumption that we owe you >> something, and that by failing to provide that thing we owe you we >> have wronged you somehow. You may wish to take a step back and >> consider that premise in light of what you're paying for this >> stuff. :) > > So, to follow that statement to its logical conclusion, you are > inferring that if user is not paying for a product they have no right > to expect quality. OK, now I can better understand where you are coming > from. Jerry, What I believe Doug is trying to say is that there is no formal agreement that would give you personally an enforcable right to a particular quality level of the ports@ tree at all times. Whether that agreement is incentivized by money or whatever else you may think of. I've spend one hour reading and figuring if there are constructive options raised in this thread and I'm sorry to say that those parts were mentioned days ago and nothing new was added in the past day or so. Can we put anything that doesn't specifically deal with how to actually fix the problem, or avoid it for the future, to rest in as far as this thread is concerned? I believe all that bears any relevance to this thread has been said in this thread. Thank you. Best, Matthias From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 09:45:40 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C647106564A for ; Mon, 29 Aug 2011 09:45:40 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward12.mail.yandex.net (forward12.mail.yandex.net [IPv6:2a02:6b8:0:801::2]) by mx1.freebsd.org (Postfix) with ESMTP id 551848FC16 for ; Mon, 29 Aug 2011 09:45:39 +0000 (UTC) Received: from smtp12.mail.yandex.net (smtp12.mail.yandex.net [95.108.131.191]) by forward12.mail.yandex.net (Yandex) with ESMTP id DE8EAC2199C; Mon, 29 Aug 2011 13:45:36 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314611136; bh=87Nc7Nr8sbOBb/axJV48Dr5wSSNMOWxyU2mJRQubzek=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=m2AMHAqEjo7Qsp10QFMndjDTNbnzmmpAJHYlEqXeiLqdCfk18viZNimpos8nVTBl/ MNNfta/RxUIzVN8Dz+Liu8MGXp4WUkotPCMxTq3lkVEf6NC5pOn98vWhCDpbfhqQ+d aWPOcz8YSR3DTVRXj2+7pmBCxArAOEUpw8eaTlbo= Received: from smtp12.mail.yandex.net (localhost [127.0.0.1]) by smtp12.mail.yandex.net (Yandex) with ESMTP id C57D416A02A4; Mon, 29 Aug 2011 13:45:36 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp12.mail.yandex.net (nwsmtp/Yandex) with ESMTP id jakiiw0f; Mon, 29 Aug 2011 13:45:36 +0400 X-Yandex-Spam: 1 Message-ID: <4E5B5FBE.8040905@yandex.ru> Date: Mon, 29 Aug 2011 13:45:34 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: Peter Jeremy References: <20110826050535.GB64576@server.vk2pj.dyndns.org> <20110829032905.GA84993@server.vk2pj.dyndns.org> In-Reply-To: <20110829032905.GA84993@server.vk2pj.dyndns.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: Problems building devel/gobject-introspection X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 09:45:40 -0000 Peter Jeremy wrote on 29.08.2011 07:29: > On 2011-Aug-26 15:05:35 +1000, Peter Jeremy wrote: >> I am having problems building devel/gobject-introspection on one >> 9.0-BETA1 host. I can build it without problems on 8.2 and another >> 9.0-BETA1 box. In all cases, I'm using gcc and amd64. The failure >> is: > ... >> Since this only happens on one box, it's presumably something I've done >> but I'm not sure what. Google hasn't helped. Does anyone have any >> ideas on where to start looking? > > Turns out that my python was dodgy. Deleting > /var/db/ports/python27/options and rebuilding with default options > fixed it. I thought I was using the defaults before but forgot to > check the contents before deleting it. And did you realize what python option had triggered that? I'm curious since i'm wasn't able to reproduce it here. For me it looks like upstream bug dealing with unicode() vs str() output, since errors like that you provide in original message may be fixed by `setenv LANG C` in most of cases. -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 09:47:59 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 475131065675 for ; Mon, 29 Aug 2011 09:47:59 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward12.mail.yandex.net (forward12.mail.yandex.net [IPv6:2a02:6b8:0:801::2]) by mx1.freebsd.org (Postfix) with ESMTP id E916C8FC1C for ; Mon, 29 Aug 2011 09:47:58 +0000 (UTC) Received: from smtp13.mail.yandex.net (smtp13.mail.yandex.net [95.108.130.68]) by forward12.mail.yandex.net (Yandex) with ESMTP id 11E3CC219EC; Mon, 29 Aug 2011 13:47:58 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314611278; bh=/FG3xyC6/00AUAvpTGMMyPgOwKFmPhfuiM3DAQECQWU=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=LXcmdI+YCX79FYLYcF5ZbOSKaJFmqiB5OYKCkLoGBbobLZSP/V4bcpBm4/u/31Tiw GX2VQjZf2rhNxegFneHwKQlRgiaG9wSs+CTmX7lwWC7vnmi3Oh0h15YbfKpoClHJIx vgyhByX2kkUMxOISsYo8xRsmlqcUX0Lmo3d+50VA= Received: from smtp13.mail.yandex.net (localhost [127.0.0.1]) by smtp13.mail.yandex.net (Yandex) with ESMTP id EF552E403D7; Mon, 29 Aug 2011 13:47:57 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp13.mail.yandex.net (nwsmtp/Yandex) with ESMTP id lvmqCM2J; Mon, 29 Aug 2011 13:47:57 +0400 X-Yandex-Spam: 1 Message-ID: <4E5B604B.1090902@yandex.ru> Date: Mon, 29 Aug 2011 13:47:55 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: Jeroen References: <4E5AB569.4060703@virtualhost.nl> In-Reply-To: <4E5AB569.4060703@virtualhost.nl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: firefox 6: mercurial seems to be missing as depency X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 09:47:59 -0000 Jeroen wrote on 29.08.2011 01:38: > Hi all, > > When updating firefox to the latest version (from ports) it complained > about hg not being found. Apparently a dependency to mercurial is > missing. I haven't checked why, installing it resolved it. > > Regards, > Jeroen Can you please show us exact error message for further investigation? -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 10:08:40 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 34AAE1065670; Mon, 29 Aug 2011 10:08:40 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 1547A150EDA; Mon, 29 Aug 2011 10:08:38 +0000 (UTC) Message-ID: <4E5B6525.2020604@FreeBSD.org> Date: Mon, 29 Aug 2011 03:08:37 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0 MIME-Version: 1.0 To: Sunpoet Po-Chuan Hsieh References: <4E385E09.20208@FreeBSD.org> <20110812110703.GA52137@bonjour.sunpoet.net> In-Reply-To: <20110812110703.GA52137@bonjour.sunpoet.net> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: churanov.port.maintainer@gmail.com, "freebsd-ports@FreeBSD.org" Subject: Re: Any progress on updating boost? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 10:08:40 -0000 On 08/12/2011 04:07, Sunpoet Po-Chuan Hsieh wrote: > On Tue, Aug 02, 2011 at 01:28:57PM -0700, Doug Barton wrote: >> I notice that http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/156253 >> exists for the 1.46.1 update, however 1.47 is out since July 11. I'm >> curious about whatever plans may exist to do the update ... > > Hello Doug, > > FYI, I have a patch for boost 1.47 at http://people.FreeBSD.org/~sunpoet/boost.patch > Please try it. Thanks. :) Ok, finally got to try this a bit. Minor bad news, your patch to devel/boost-pyste no longer applies. More bad news, the new boost libs have "issues." I maintain 2 ports that use them, libtorrent-rasterbar and qbittorrent. So I first tried building your new versions of boost-jam and boost-libs ... no problems there. Then I ran my existing qbittorrent binary which was compiled against 1.45, so far so good. The problems came when I rebuilt those 2 against the new boost libs. qbittorrrent starts up Ok, but then it ends up freezing solid, needing to be killed. On the console I get a whole bunch of these: WARNING pid 86327 (qbittorrent): ioctl sign-extension ioctl ffffffff8004667e This is on recent 9-current amd64. The only boost OPTION I have enabled is the one for optimized cflags. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 11:06:08 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 339BD106564A for ; Mon, 29 Aug 2011 11:06:08 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 214E18FC16 for ; Mon, 29 Aug 2011 11:06:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p7TB68lK088466 for ; Mon, 29 Aug 2011 11:06:08 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p7TB66b1088464 for freebsd-ports@FreeBSD.org; Mon, 29 Aug 2011 11:06:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 29 Aug 2011 11:06:06 GMT Message-Id: <201108291106.p7TB66b1088464@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: FreeBSD ports list Cc: Subject: Current unassigned ports problem reports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 11:06:08 -0000 (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/160278 [MAINTAINER] japanese/ibus-skk: update to 1.3.8 o ports/160274 [patch] sysutils/hfsexplorer updated url discripton o ports/160273 [patch] Fix distfile sources for port net/AquaGatekeep f ports/160272 [patch] unbreak port net/AquaGatekeeper o ports/160265 [NEW PORT] lang/pypy 1.6 o ports/160262 New port: net-mgmt/better-cacti-templates - better Cac f ports/160257 [patch] mail/ssmtp: pkg-message needs further descript o ports/160254 [MAINTAINER-UPDATE] from net-mgmt/vidalia 0.2.12 to 0. f ports/160243 emulators/wine-gecko: update to last version f ports/160242 audio/murmur installs directories with incorrect owner o ports/160236 [patch] Upgrade lang/jruby to 1.6.4 o ports/160234 [maintainer-update] comms/grig to 0.8.0 f ports/160233 [patch][update] devel/pinba_engine Update to new revis f ports/160232 Update: x11/xlockmore to 5.34 f ports/160226 Unbreak lang/nawk by updating it to 20110810 o ports/160217 [Maintainer Update] emulators/doscmd update o ports/160213 [NEW PORT] security/py-htpasswd - htpasswd replacement o ports/160212 [maintainer update] textproc/pear-Numbers_Words o ports/160211 [NEW PORT] math/pear-Math_BigInteger : Pure-PHP arbit f ports/160210 [update] devel/php5-pinba o ports/160208 [NEW PORT} print/py27-pdfcolorsplit - script to split o ports/160207 [NEW PORT] devel/php5-dav: The PHP WebDAV extension o ports/160194 [PATCH] sysutils/jdiskreport: update to 1.3.2 o ports/160190 New port: net/samba36-devel Test version of Samba 3.6 f ports/160184 graphics/jpeg2pdf is broken with ruby 1.9, but does no o ports/160182 [maintainer patch] graphics/zbar. Fix pkg-plist, restr o ports/160178 [NEW PORT] www/vimprobable1 - webkit browser inspired o ports/160177 [NEW PORT] www/vimprobable2 - webkit browser inspired o ports/160174 [PATCH] japanese/jcode.pl Fix defined(%hash) is deprec o ports/160172 [NEW PORTS] japanese/wordpress: add ja-wordpress 3.2.1 o ports/160161 [PATCH] deskutils/griffith: eliminate py-pysqlite2x de o ports/160142 Update port: security/fakebo to 0.4.2.1 o ports/160133 Update port: net-im/py-pyxmpp to 1.1.2 o ports/160132 Update port: net-im/cjc to 1.2.1 o ports/160126 Update port: math/parmetis to 4.0 o ports/160122 Update port: lang/libjit to 0.1.2 o ports/160120 Update port: graphics/raster3d to 3.0.2 o ports/160117 Update port: graphics/icoutils to 0.29.1 o ports/160116 Update port: graphics/glfw to 2.7.2 o ports/160115 Update port: graphics/epix to 1.2.9 o ports/160114 Update port: graphics/boxer to 0.3.1 o ports/160113 Update port: graphics/box to 0.2.3 o ports/160112 Update port: games/xspringies to 1.12 o ports/160110 Update port: games/xfrisk to 1.3.r1 o ports/160104 Update port: games/lgeneral to 1.2.2 o ports/160097 Update port: devel/z80-asm to 2.4.p3 o ports/160095 Update port: devel/rlog to 1.4 o ports/160094 Update port: devel/piklab to 0.15.10 o ports/160092 Update port: deskutils/rubrica to 2.0.10 o ports/160091 Update port: deskutils/cdcat to 1.5 o ports/160090 Update port: databases/lsdb to 0.11 o ports/160086 Update port: cad/magic to 7.5.213 o ports/160085 Update port: cad/feappv to 2.2 o ports/160084 Update port: cad/atlc to 4.6.1 o ports/160082 Update port: benchmarks/mdtest to 1.8.3 o ports/160081 Update port: audio/slv2 to 0.6.6 o ports/160080 Update port: audio/liteamp to 0.2.4.2 o ports/160073 Update port: audio/HVSC-Update to 2.8.5 f ports/160072 [UPDATE] security/umit: update to 1.0 o ports/160071 [PATCH] security/zenmap: eliminate py-pysqlite2x depen o ports/160070 [PATCH] multimedia/miro: eliminate py-pysqlite2x depen o ports/160066 [PATCH] security/hottsh: eliminate py-pysqlite2x depen o ports/160065 [PATCH] multimedia/pyjama: eliminate py-pysqlite2x dep o ports/160062 math/pari: fix fetch and undeprecate f ports/160060 collision: sysutils/coreutils Collision between system f ports/160058 [patch] games/instead: update to 1.5.0 o ports/160055 [PATCH] games/anki: eliminate py-pysqlite2x dependency f ports/160052 [patch] sysutils/fusefs-kmod: fix build after vfs_flag o ports/160049 [PATCH] emulators/wahcade: eliminate py-elementtree de f ports/160045 [PATCH] emulators/visualboyadvance-m: fix SFML depend o ports/160039 request to maintain x11/stalonetray o ports/160033 [maintainer] update port devel/libffi o ports/160031 [PATCH] devel/yajl add yajl.pc f ports/160027 net/rabbitmq daemon fails to restart half of the time o ports/160025 update the /databases/py-firebirdsql o ports/160020 [MAINTAINER] japanese/ddskk: update to 14.3 o ports/160012 [maintainer-update] [patch] net-p2p/lopster portlint c o ports/160007 [NEW PORT] ports-mgmt/porttree: Show dependences of Fr o ports/160006 [new port] devel/premake4: cross-platform build script f ports/159996 multimedia/ffmpegthumbnailer doesn't link with libjpeg o ports/159991 [PATCH] devel/py-mercurialserver mark IGNORE o ports/159978 devel/bazaar-ng 2.4.0: Viewing help for subcommands re o ports/159976 new port: games/blackjack o ports/159961 [Patch] Update x11-wm/echinus to version 0.4.7 f ports/159959 [UPDATE] x11-wm/matwm2 to 0.1.2pre3 f ports/159958 [UPDATE] x11/deskpaint to 3.1 f ports/159951 [patch] www/woof to support Python 2.7 o ports/159935 ports-bug [PATCH] devel/libparserutils: update dependencies and f ports/159926 [PATCH] lang/py-prolog: some cleanup o ports/159920 [MAINTAINER] dns/zonecheck: update to 3.0.5 o ports/159915 [MAINTAINER] net-mgmt/ndpmon: [SUMMARIZE CHANGES] o ports/159914 [MAINTAINER] net-mgmt/ramond: [SUMMARIZE CHANGES] o ports/159909 [maintainer] lang/ikarus: add more MASTER_SITES o ports/159908 [new] devel/php5-blitz-devel Templating engin o ports/159903 japanese/a2ps: a2ps-j generates warning errors for obs o ports/159894 [new port] databases/php52-rrdtool f ports/159874 [patch] sysutils/zfs-snapshot-mgmt: respect local time o ports/159873 net/libgcrypt needs libgpg error > 1.8 f ports/159872 [UPDATE] www/xpi-firebug: update to 1.8.1 o ports/159863 [patch] chinese/tin with tin 1.9.6 o ports/159843 [PATCH] databases/postgresql-plpython: unbreak f ports/159821 [patch] www/squid31: dnsserver does not build o ports/159803 update security/monkeysphere to 0.35 f ports/159791 x11-fonts/terminus-font patch apply fails f ports/159790 sysutils/freesbie cannot build iso f ports/159786 [patch] upgrade of security/ossec-hids-server and secu o ports/159766 cannnot execute sysutil/ezjail on 9.0 BETA1 o ports/159760 New port: devel/libparserutils A library useful when w o ports/159748 comms/rxtx installs improperly with openjdk7 o ports/159747 New port: sysutlis/wiimms : Wii and GameCube ISO Tools o ports/159735 [patch] adopt and update comms/rxtx o ports/159728 sysutils/htop-0.9.0_1 is broken (does not show process o ports/159644 Math/asir2000 BROKENed, so update. o ports/159636 [patch] net/freevrrpd: RC script for freevrrpd that co o ports/159631 New port: sysutils/amount FreeBSD specific auto mount o ports/159626 New port: dns/radns IPv6 DNS server address autoconfig f ports/159619 net-mgmt/netams install cgi scripts without exec permi f ports/159607 Update port: graphic/mahotas Efficient Image Processin o ports/159575 [new port] games/stockfish: open source chess engine f ports/159560 [PATCH] devel/php-xdebug: update to 2.1.2 o ports/159550 audo/freeswitch-sounds: update to latest version, othe o ports/159549 [New Port] graphics/ocrfeeder o ports/159544 [New Port] graphics/py-imaging-sane f ports/159516 [patch] Port comms/mlan3 update to 310r2 version o ports/159515 [MAINTAINER] net-mgmt/zabbix-server: update to 1.8.6 f ports/159409 [PATCH] devel/py-boto: update to 2.0 o ports/159393 [New port] x11/gnome-color-chooser: customize appearan o ports/159378 [NEW PORT] lang/php-plua: PLua is a PHP extension whic o ports/159361 sysutils/fusefs-kmod doesn't compile o ports/159325 new port: emulators/joytran f ports/159322 [PATCH] sysutils/fusefs-kmod doesn't build due to rece o ports/159319 databases/postgresql-plpython doesn't build with postg f ports/159313 sysutils/uhidd: uhidd-devd.conf.sample doesn't work o ports/159302 New port:math/geogebra - software for math and geometr f ports/159245 sysutils/duplicity updated to 0.6.14 f ports/159230 [PATCH] fix sysutils/fusefs-kmod for the 64bit mount f o ports/159221 sysutils/ezjail: ezjail-admin command, console option f ports/159218 [patch] update multimedia/ffmpegthumbnailer to 2.0.7, o ports/159217 New port: devel/goprotobuf - Protocol buffers for Go f ports/159205 net-mgmt/zabbix-agent: No active checks on server: hos o ports/159204 net-mgmt/zabbix-server - graphs drawn with no data o ports/159187 [patch] sysutils/am-utils patch to add nolockd to nfs f ports/159177 sysutils/muse on 8.2-STABLE o ports/159168 Update port german/tipp10 to current program version o ports/159152 New port: sysutils/battray o ports/159121 net/freevrrpd: Make adv_int a runtime configurable opt f ports/159108 sysutils/fusefs-smbnetfs update to 0.5.3 o ports/159102 sysutils/fusefs-kmod: fusefs daemonizes before mount i o ports/159083 [NEW PORT] www/py27-django_compressor: Compresses link f ports/159050 PORT graphics/fotoxx Makefile update o ports/159025 New port: www/py-tornado2 - An open source scalable, n o ports/159007 New ports: print/linux-f10-cups-libs, security/linux-f s ports/158983 [NEW PORT] devel/pecl-dtrace: PHP DTrace provider f ports/158968 Update port: lang/mosh version 0.2.7 f ports/158935 [PATCH] print/lpr-wrapper: update to 0.7 o ports/158931 print/perlftlib is not built with perl5.14 o ports/158925 New Port: audio/pithos GNOME Pandora player f ports/158916 [PATCH] textproc/ctpp2: update to 2.7.1 a ports/158910 [PATCH] sysutils/battmond: update to 0.3 f ports/158907 [PATCH] www/interchange: update to 5.6.3 f ports/158898 [PATCH] www/libecap: update to 0.2.0 f ports/158897 [PATCH] net/phamm: update to 0.5.18 f ports/158889 [PATCH] sysutils/ucspi-proxy: update to 0.98 o ports/158878 [patch] textproc/dadadodo assumes long is 32 bits f ports/158824 devel/flyspray: share/flyspray/flyspray.conf.php remai o ports/158791 Update security/openvas-* o ports/158781 New port: games/drcreep Platform Puzzle Game f ports/158731 sysutils/byobu wants module "snack" o ports/158704 New port: mail/mailfromd f ports/158533 [NEW PORT] devel/tiled: 2D game map editor f ports/158403 New port: mail/dovecot2-deleted-to-trash-plugin: dovec o ports/158204 [PATCH] java/jde: update to 2.4.0.1 o ports/158179 some packages do not fully honor -P dir option in pkg_ o ports/158167 [NEW PORT] databases/percona-server: Multithreaded SQL o ports/158044 Multiple net/iaxmodem instances started o ports/157791 audo/midimountain fails to copy all xpm files and fail o ports/157738 New port: net/py-ldaptor o ports/157719 [new port] net-mgmt/zenpack-CheckPing: Provides nagios o ports/157715 [new port] net-mgmt/zenpack-libvirt: Provides monitori f ports/157494 lang/ezm3 fails to compile o ports/157320 [NEW PORT] databases/pecl-pdo_user: PECL classes provi o ports/157301 [New port] net-mgmt/zbxlog: Syslog server receives mes o ports/157282 [MAINTAINER PATCH] net/xrdp: effective login name is n o ports/157191 [new port] net-mgmt/zenpack-MACReport: Lists MAC addre o ports/157190 [new port] net-mgmt/zenpack-GraphPortlet: Enables user o ports/157176 [patch] sysutils/heartbeat crashes when clock_t (signe o ports/157136 [new port] net-mgmt/zenpack-Domain: Provides expiratio o ports/157135 [new port] net-mgmt/zenpack-DellMonitor: Provides Zeno o ports/157133 [new port] net-mgmt/zenpack-ApacheMonitor: Provides pe f ports/157109 conflict between net/netpipes and sysutils/timelimit f ports/157107 conflict between mail/p5-Mail-SPF and mail/libspf2 f ports/157044 x11-toolkits/slgtk: fails to start f ports/157021 multimedia/mplayer: does not build with multimedia/lib o ports/157014 devel/jam: does not compile on FreeBSD 9.0 CURRENT/amd o ports/156834 New port: games/fairymax-devel latest version of games o ports/156791 New port: security/py-kerberos Python bindings for ker f ports/156747 multimedia/mplayer: fix 24-bits OSS + some improvement o ports/156737 [patch] www/squid31: squid.in startup script fixes to o ports/156693 [PATCH] security/hmap: refine this port a bit o ports/156629 [patch] sysutils/puppet patch to use PACKAGEROOT inste o ports/156539 [NEW PORT] print/frescobaldi: A music score editor for o ports/156472 [new port] devel/ocaml-react - OCaml library for react f ports/156376 [PATCH] graphics/optipng: update to 0.6.5 o ports/156362 New port: games/rftg Race for the Galaxy AI o ports/156343 multimedia/xbmc 10.1_1 mp3 playback problem - CALSADir o ports/156313 [patch][new port] astro/gkrellsun2 (Gkrellm2 Plugin) f ports/156252 New port: devel/radar Opensource tools to disasm, debu f ports/156171 port multimedia/mplayer patch-libao2-ao_oss.c is incor f ports/156143 New port: devel/arduino-mk: Build Arduino sketches fro o ports/156119 x11-fonts/font-manager: ignore a problem caused by the f ports/156075 [new port] graphics/openfst: library for constructing, f ports/156034 print/lyx-devel spell checking with enchant does not w f ports/155941 mwserv library support is not included in nepenthes.co f ports/155898 Update port devel/libthai o ports/155788 ports security/cfsd startup -- multiple problems f ports/155697 ports-mgmt/pkg_replace doesn't want to replace java/op o ports/155593 lang/mpd .16.1 ignores embedded cue sheets in FLAC fil f ports/155592 polish/ekg, after polish/libgadu update, contacts are o ports/155570 [patch] devel/py-twistedCore: update to 10.2.0 and oth f ports/155547 java/jboss5 port build failure o ports/155538 new port devel/radlib radlib developer library. Event- o ports/155447 Update ports: net-p2p/eiskaltdcpp-* to 2.2.1, New port f ports/155404 [PATCH] mail/mutt-devel: doesn't build in presence of f ports/155306 multimedia/openshot doesn't work o ports/155225 plz split antlr2 and antlr3 ports. not update antlr2 - o ports/155166 update deskutils/org-mode.el to 7.4 o ports/155120 Update of port devel/php-libawl f ports/155115 devel/doxygen: dependancy loop o ports/155070 NEW PORT: games/CastleVox - new fast strategy board ga f ports/154973 [PATCH] security/ike: fix plist when QTGUI=off, respec o ports/154711 security/heimdal: kadmin: hdb_open: hdb_open failed in o ports/154682 net/iaxmodem: add rc script for running more than 1 ia f ports/154546 update port: games/gemrb to version 0.6.3 o ports/154401 New port: www/jetty7 - newer fork by Eclipse/Codehaus o ports/154285 [NEW PORT] java/netty: Java NIO client server framewor o ports/154217 New port: ports-mgmt/portsreinstall o ports/154202 New port: security/scannedonly - A Samba VFS virus sca o ports/154031 New port: audio/shoutcast2: SHOUTcast Distributed Netw o ports/153926 New port net/freeswitch-snapshot o ports/153810 [PATCH] Fix usb_interrupt_read() in devel/libusb for f o ports/153607 Update devel/djgpp-binutils to version 2.17 o ports/153429 [patch] Fix explicite uses of unzip in ports o ports/153425 [PATCH] www/limesurvey: Added a switch to use PostgreS f ports/153130 sysutils/k3b: problem with k3b and mounting ntfs with o ports/152982 [patch] net/nss_ldap, ignore option nss_initgroups_ign f ports/152915 russian/xmms v. 1.2.11_12 don't see cdinfo and tag's i o ports/152376 New port: audio/lastfmsubmitd o ports/152236 [patch] x11/slim: Enable pam support, add hald and dbu s ports/152195 [PATCH] deskutils/pinot update to xapian-core 1.2.3 f ports/152192 [PATCH] databases/xapian-bindings update to 1.2.3 o ports/152191 [PATCH] databases/xapian-core update to 1.2.3 o ports/152118 New port: deskutils/linux-tahometer A worktime trackin o ports/151930 [PATCH] net-mgmt/netams links to libmysqlclient/libpq o ports/151747 new port: emulators/wine-fbsd64: request for (a variat o ports/151318 [repocopy][new port] x11-wm/stumpwm: rename to x11-wm/ o ports/151296 [patch] ports/sysutils/fusefs-kmod build fails: MNT_NF f ports/150783 mail/qpopper: fails to configure ocasionally o ports/150425 www/squid31: rc.d/squid's squid_fib setting ineffectiv f ports/150235 sysutils/smartmontools build system bug o ports/150194 There is no startup script for databases/cassandra o ports/150086 [NEW PORT] net-im/tkabber-plugins-devel: External Plug o ports/149564 patch for various games/ adding appropriate LICENSEs t f ports/148871 bad packages: p5-XML-Parser-2.36_1 p5-XML-SAX-Expat-0. o ports/147943 New port: net/radsecproxy Radsecproxy is a generic RAD s ports/147829 Improved net/ucarp startup script: multiple VHID and F s ports/147169 bsd.ruby.mk: Adding GEM_ARGS a ports/139203 sysutils/freebsd-snapshot more careful patch not depen o ports/137378 Advisory locks fail with ports/security/cfs on FreeBSD f ports/122333 net/arping - patch to lookup for interface and src ip, o ports/57498 HEIMDAL_HOME should be defined in src or ports Makefil 270 problems total. From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 11:08:38 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09C89106566B for ; Mon, 29 Aug 2011 11:08:38 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D43AD8FC14 for ; Mon, 29 Aug 2011 11:08:37 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p7TB8bAP090525 for ; Mon, 29 Aug 2011 11:08:37 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p7TB8bws090523 for ports@FreeBSD.org; Mon, 29 Aug 2011 11:08:37 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 29 Aug 2011 11:08:37 GMT Message-Id: <201108291108.p7TB8bws090523@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: ports@FreeBSD.org Cc: Subject: Current problem reports assigned to ports@FreeBSD.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 11:08:38 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. No matches to your query From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 12:20:09 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7404C106566B for ; Mon, 29 Aug 2011 12:20:09 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B493C8FC12 for ; Mon, 29 Aug 2011 12:20:08 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA05495; Mon, 29 Aug 2011 15:20:03 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E5B83F3.3050506@FreeBSD.org> Date: Mon, 29 Aug 2011 15:20:03 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110705 Thunderbird/5.0 MIME-Version: 1.0 To: Michal Varga References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314585798.82067.338.camel@xenon> <4E5B0EFB.6000900@FreeBSD.org> <1314596096.82067.419.camel@xenon> <4E5B320E.8010503@FreeBSD.org> <1314601622.82067.441.camel@xenon> <4E5B3CF8.4020805@FreeBSD.org> <1314604521.82067.461.camel@xenon> In-Reply-To: <1314604521.82067.461.camel@xenon> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 12:20:09 -0000 on 29/08/2011 10:55 Michal Varga said the following: > On Mon, 2011-08-29 at 00:17 -0700, Doug Barton wrote: >> are unlikely to ever get to that point. I would also point out that from >> a project management standpoint developers rarely make good QA people. >> To do this right you really would want separate teams. > > As I said, that's not something that's in my power to change. > > In any case, it just leads (and always will lead) only to this outcome: > >> Those are good alternatives as well. I use FreeBSD as my desktop, but >> it's painful, and I wouldn't do it at all if I didn't need to. > > Other OSes/projects, for some reason, are able to manage their > maintainer base to much better results, and it shows. It can either be > done here too, or the situation can be ignored for another five, ten > years, until FreeBSD fades into obscurity, eventually getting known only > as 'that OS where nothing works'. It's an issue that won't go away on > its own. Correct. So what's your personal contribution towards fixing that issue? E.g. finding out how "other OSes/projects, for some reason, are able to manage their maintainer base to much better results" and teaching that to us would be a great contribution. There are many other ways to contribute as well. -- Andriy Gapon From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 14:47:45 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B326410656B0 for ; Mon, 29 Aug 2011 14:47:45 +0000 (UTC) (envelope-from code@apotheon.net) Received: from oproxy3-pub.bluehost.com (oproxy3.bluehost.com [IPv6:2605:dc00:100:2::a3]) by mx1.freebsd.org (Postfix) with SMTP id 7067B8FC25 for ; Mon, 29 Aug 2011 14:47:45 +0000 (UTC) Received: (qmail 25361 invoked by uid 0); 29 Aug 2011 14:47:44 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by oproxy3.bluehost.com with SMTP; 29 Aug 2011 14:47:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.net; s=default; h=In-Reply-To:Content-Type:Mime-Version:References:Message-ID:Subject:To:From:Date; bh=VF+oGdZhAW7mXroZmvqurohDyh15Ao9yZoyPToJylgg=; b=s+NOm5qYtsFuAVHmBJbWOWpHeGXquLWpODfQ9zekTC/xU+XLfIpE56VaUICF5sFPWhYyAqXdFIvzkqmApjMg9uuaQJI+WOtJajmWTyFGVt0SEdz4lb7TuXbAPcNNzlA/; Received: from c-24-8-180-234.hsd1.co.comcast.net ([24.8.180.234] helo=kukaburra.hydra) by box543.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1Qy37n-0006pj-N9 for freebsd-ports@FreeBSD.org; Mon, 29 Aug 2011 08:47:44 -0600 Received: by kukaburra.hydra (sSMTP sendmail emulation); Mon, 29 Aug 2011 08:29:20 -0600 Date: Mon, 29 Aug 2011 08:29:20 -0600 From: Chad Perrin To: freebsd-ports@FreeBSD.org Message-ID: <20110829142920.GA65053@guilt.hydra> Mail-Followup-To: freebsd-ports@FreeBSD.org References: <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314585798.82067.338.camel@xenon> <4E5B0EFB.6000900@FreeBSD.org> <1314596096.82067.419.camel@xenon> <4E5B320E.8010503@FreeBSD.org> <1314601622.82067.441.camel@xenon> <4E5B3CF8.4020805@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline In-Reply-To: <4E5B3CF8.4020805@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.org} {sentby:smtp auth 24.8.180.234 authed with ren@apotheon.org} Cc: Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 14:47:45 -0000 --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 29, 2011 at 12:17:12AM -0700, Doug Barton wrote: > On 08/29/2011 00:07, Michal Varga wrote: > > On Sun, 2011-08-28 at 23:30 -0700, Doug Barton wrote: > >>> Testing only for "Does it still build?" won't help much anymore if > >>> the new version silently broke one of the APIs and while Apache > >>> still runs with it fine > >> > >> Believe it or not, I understand that. :) The problem is that > >> extensive run-time testing is not within the realm of possibility > >> without an army of volunteers. Do you want to organize that effort? > >=20 > > That would be the very opposite of the concept I just described. > > While extensive volunteer testing, if considered standalone, is > > surely not a bad idea (just that for some reason it never happens > > anywhere), it lies in a completely different scope than port > > maintainers *not* randomly upgrading dependencies just on their own > > without regard to other ports they will affect (and in many cases > > break, be it on build level, or run-time level). >=20 > Ok, I'll be more blunt. We don't do that on purpose, obviously. But > expecting maintainers to do what you're describing is unrealistic. The > only thing it would accomplish is a "stable" ports tree because nothing > would ever get updated. :) >=20 > Seriously ... I get what you're saying, I'm not even saying it's a bad > idea, I'm just saying that we lack the person-power to do it now, and > are unlikely to ever get to that point. I would also point out that > from a project management standpoint developers rarely make good QA > people. To do this right you really would want separate teams. Frankly, I think the one thing that would have the most dramatically and disproportionately positive effect on the quality and stability of ports would be an improvement in the toolsets available for porters -- not just the tools themselves, but the introduction to using them. Consider, for instance, the possibility of an automated system with minimal configuration and command syntax for pulling a port from a nonstandard source while still managing it using the standard ports system; it would make user testing much more palatable, even inviting, and thus make it easier for a port maintainer to encourage interested acquaintances to help test a port under varied conditions before it gets committed to the official ports tree. While I'm not a huge fan of the way the first chromium browser port's maintainer handled his "hybrid source" business model, I also think it would be nice to have a system for installation and management of nonstandard ports using the standard ports tools for purposes of offering a way for third-party software repositories to be offered for easy inclusion, too (let the buyer beware, of course). I'm pretty new to learning about how ports are maintained, so it's possible I've missed something -- but if I have, we're desperately lacking the sort of documentation that would make this stuff obvious and accessible to users and, perhaps, to port maintainers as well. I'd be happy to be shown where I am wrong about the lack of such facilities, of course. I'm sure that, if I am wrong about it, there are many other people out there who would be happy to discover that their inability to find reference to such facilities would be happy to be educated about the existence of such things, too. > >> > >> That sounds like PC-BSD to me. (Seriously, give it a try) > >=20 > > Now that's like saying I might want to try *Linux and OS X too (I > > occasionally use both, just not as my primary desktop, which is > > FreeBSD). >=20 > Those are good alternatives as well. I use FreeBSD as my desktop, but > it's painful, and I wouldn't do it at all if I didn't need to. >=20 > FreeBSD needs to get better in this area, but I seriously doubt it will > ever be as easy and painless as something like ubuntu. For a great many use cases, Ubuntu is one of the most painful "desktop" user experiences I have ever encountered. Please, *please* do not emulate Ubuntu. Fundamental operations change with the blowing of the wind in Ubuntu for no good reason; its "don't make the user think" philosophy is taken to an absurd extreme that often results in it not only making decisions against the user's interests, but also *changing* a user's choices later on down the road; it installs software and runs servers the user will never have any occasion to use, with no obvious way to deactivate them; and it essentially enforces the use of huge collections of software by way of hopelessly intertangled dependencies. There's more, but I need to stop some time, because this is not a forum for Ubuntu-related discussion. The difficulties of using a "desktop" system built on the Ubuntu way of doing things is not "easy" and "painless" for a nontrivial selection of users, especially developers. I know people who work for Canonical on Ubuntu development who lament some of the difficulties of dealing with Ubuntu and, as my girlfriend once said (paraphrased), "If I wanted to deal with this crap I'd be using Windows." I use FreeBSD on my laptops because it is the *least* painful system to use for "desktop" purposes, in my experience. I like a system that offers the software and capaibilities I need without taking away from me the ability to actually control the system's configuration to a reasonable degree. Note that the laptop on which I'm typing this is an exception, because I bought it with an Intel Core i5 before I knew about the graphics support issues. That does not mean that the OS I'm running on it instead it is less painful to use for such a purpose than FreeBSD would be. I have only barely continued to lean to the side of not dealing with a 4:3 resolution stretched to a 16:9 display aspect ratio (as I would get with FreeBSD). The hassles and frustrations of a constantly changing Linux-based software ecosystem that seems intent on growing more non-deterministic in its behavior over time are very nearly enough to make me choose the horribly stretched resolution over these technical annoyances that do things like prevent me from connecting reliably to certain wireless networks. It has gotten bad enough that I have recently started using an older laptop for close to half of what I do, just so I can have a sane, stable environment (relative to MS Windows and any modern Linux distribution I've encountered). That is not to say that FreeBSD does not have its own annoyances (as this thread has pointed out, sometimes even accurately) -- but please do not go pursuing the policies of a system that throws away all the benefits that drew me to FreeBSD in the first place in search of a more "painless" user experience. I do not, at the moment, feel a burning need to find excuses to switch to NetBSD or OpenBSD as my primary laptop OS of choice. Don't let me throw fuel on the fire, here, but please don't throw out the baby with the bathwater, either. --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --h31gzZEtNLTqOjlF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk5bokAACgkQ9mn/Pj01uKU5XACcDASbtAXBDxs/vr/97t5b692F kx4AnRsFJtqsIoKO1SUHZDQRse/ywtRB =eeLb -----END PGP SIGNATURE----- --h31gzZEtNLTqOjlF-- From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 15:10:30 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6C36106566B for ; Mon, 29 Aug 2011 15:10:30 +0000 (UTC) (envelope-from xaero@xaerolimit.net) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 81D9D8FC0C for ; Mon, 29 Aug 2011 15:10:30 +0000 (UTC) Received: by vws18 with SMTP id 18so6010688vws.13 for ; Mon, 29 Aug 2011 08:10:29 -0700 (PDT) Received: by 10.52.70.100 with SMTP id l4mr166531vdu.23.1314630629708; Mon, 29 Aug 2011 08:10:29 -0700 (PDT) Received: from [192.168.0.9] (ool-43529a81.dyn.optonline.net [67.82.154.129]) by mx.google.com with ESMTPS id q10sm18423vdv.30.2011.08.29.08.10.27 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 29 Aug 2011 08:10:28 -0700 (PDT) Message-ID: <4E5BABD0.9090300@xaerolimit.net> Date: Mon, 29 Aug 2011 11:10:08 -0400 From: Chris Brennan User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <20110828210511.3d2e0604@cox.net> In-Reply-To: <20110828210511.3d2e0604@cox.net> X-Enigmail-Version: 1.3.1 OpenPGP: id=D5B20C0C Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig162BE095E4E3961AA7E6E36E" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: MASTER_SITE_SOURCEFORGE: how do *you* handle it? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 15:10:30 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig162BE095E4E3961AA7E6E36E Content-Type: multipart/mixed; boundary="------------020504000704020102070705" This is a multi-part message in MIME format. --------------020504000704020102070705 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 8/28/2011 10:05 PM, Conrad J. Sabatier wrote: > I'm wondering how other ports maintainers are dealing with their=20 > definitions of MASTER_SITES=3D, DISTFILES=3D, DISTNAME=3D, etc. with > regards to Sourceforge. >=20 > In browsing a number of projects recently on Sourceforge, I've > noticed that the paths to project distfiles are now using the > element "projects" rather than "project". >=20 > What I'm looking for is how to declare things in a clean and elegant=20 > fashion in a port's Makefile to handle these cases, one that will=20 > hopefully not require any revisions for later upgrades. Is it > necessary to just scrap the "SF" definition entirely and hardcode the > URL? >=20 > In addition, I've run across a few projects that use slightly > differing versions of the project name, either somewhere in the path > or for the distfile name itself. For example, looking at the > "scidvspc" project earlier today, I noticed this: >=20 > The link for the distfile is defined as: >=20 > http://sourceforge.net/projects/scidvspc/files/source/scid_vs_pc-4.5.tg= z/download > > Clicking the download link, one is presented with alternatives in > case the download doesn't start automatically. >=20 > The "mirror" link: >=20 > https://sourceforge.net/settings/mirror_choices?projectname=3Dscidvspc&= filename=3Dsource/scid_vs_pc-4.5.tgz > > The "direct link": >=20 > https://downloads.sourceforge.net/project/scidvspc/source/scid_vs_pc-4.= 5.tgz?r=3D&ts=3D1314582468&use_mirror=3Dsuperb-sea2 > > Frankly, I'm baffled as to how our current definition of=20 > "MASTER_SITES=3DSF/" is supposed to handle all of this. >=20 > Can anyone point me towards a source of enlightenment? :-) >=20 > Thanks! >=20 Slightly related and unrelated at the same time. So sorry if I drifted too far. I was discussing this very concept about a month ago with a friend. I was trying to update my PortableApps.om installation and the script I had written to fetch updated apps broke because I couldn't figure out how to handle these new url's. It would see SF's idea of a direct link is a redirect, thus obfuscating the real servers even more and the path the project is in.... --=20 > Chris Brennan -- A: Yes. >> Q: Are you sure? >>> A: Because it reverses the logical flow of conversation. >>>> Q: Why is top posting frowned upon? > http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/=20 > GPG: D5B20C0C (6741 8EE4 6C7D 11FB 8DA8 9E4A EECD 9A84 D5B2 0C0C) ------------------------------------------------------------------------ --------------020504000704020102070705-- --------------enig162BE095E4E3961AA7E6E36E 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.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOW6vXAAoJEO7NmoTVsgwM0/oH/1IV5lTptFG0ArHqwGJ/0hnz RGuUGTU+DcJWYeppWFihjGlwjWpM/vRJ/gkRdve/HLv9kzeZBV8P4pA4+dg3lh0d 4o8VtVpFQfM5fff/y2MW/Dy3N2YG5J4lBdOIjXDYTtIdYrT26dlv7E5H/nWIa+RB TnpJG3lmULNHPxW7K/wBZcNHx7GviGmIulAXcPpzoeeLx+K0jvF8Sy8B9VLhDiJm DXx0tPCXXp5rOmslIobcRoSN37g4ehxTq+TdBZ4yDHEg9KAV4zdeMgA/4UIJWvga tyg2zxgS+iFcdfuvyotE0vKZTwG7OIX1p7HMbHhnsd8ysCPSF6OOSmIYQ/hV1b4= =RvHP -----END PGP SIGNATURE----- --------------enig162BE095E4E3961AA7E6E36E-- From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 15:33:15 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A65081065677 for ; Mon, 29 Aug 2011 15:33:15 +0000 (UTC) (envelope-from sjk4015@gmail.com) Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by mx1.freebsd.org (Postfix) with ESMTP id 84D7D8FC19 for ; Mon, 29 Aug 2011 15:33:15 +0000 (UTC) Received: by pzk33 with SMTP id 33so19451972pzk.18 for ; Mon, 29 Aug 2011 08:33:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=BtCQB2a2N21tx6JMEb5ECrkDEdNBfo6CNPGQiUCGjRw=; b=D1mpU8Immu9f2dffvGIhfyMX4dIJPbKRj+2hf27Ia3yYuF6f/XbL6ISAYvW35938Uz xdJTm68vrO8fUIcilVA+/Epf+ybVxY58JLreKzewjh8r/+ft5t8igWKkoukWB0nHk9J3 EKcR5WSvtzqXgQJBnJ8KJrbewUhr4WZFrOFw8= MIME-Version: 1.0 Received: by 10.142.196.4 with SMTP id t4mr2385918wff.173.1314630446618; Mon, 29 Aug 2011 08:07:26 -0700 (PDT) Sender: sjk4015@gmail.com Received: by 10.68.44.42 with HTTP; Mon, 29 Aug 2011 08:07:26 -0700 (PDT) Date: Mon, 29 Aug 2011 11:07:26 -0400 X-Google-Sender-Auth: SnB1Bg3znOVUyjMhPZRPvoH8LaI Message-ID: From: Steven Kreuzer To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Speling Mistakes X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 15:33:15 -0000 I would like to apply this patch (http://www.exit2shell.com/~skreuzer/patches/speling.diff) which fixes a few spelling mistakes in the COMMENT field for some unmaintained ports: games/qudos editors/ne misc/ftdi-eeprom games/egl devel/py-period devel/p5-Penguin-Easy games/r1q2 games/tremor textproc/mkcatalog databases/p5-DBIx-AnyDBD net/ncplib Anyone have any objections? From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 17:36:04 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E38AA106564A for ; Mon, 29 Aug 2011 17:36:04 +0000 (UTC) (envelope-from ohauer@FreeBSD.org) Received: from p578be941.dip0.t-ipconnect.de (p578be941.dip0.t-ipconnect.de [87.139.233.65]) by mx1.freebsd.org (Postfix) with ESMTP id A23718FC17 for ; Mon, 29 Aug 2011 17:36:04 +0000 (UTC) Received: from [192.168.0.100] (cde1100.uni.vrs [192.168.0.100]) (Authenticated sender: ohauer) by p578be941.dip0.t-ipconnect.de (Postfix) with ESMTPSA id 6E4C820823; Mon, 29 Aug 2011 19:35:56 +0200 (CEST) Message-ID: <4E5BCDF9.9080007@FreeBSD.org> Date: Mon, 29 Aug 2011 19:35:53 +0200 From: Olli Hauer User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: freebsd-ports@FreeBSD.org References: <20110828210511.3d2e0604@cox.net> In-Reply-To: <20110828210511.3d2e0604@cox.net> X-Enigmail-Version: 1.3.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Conrad J. Sabatier" Subject: Re: MASTER_SITE_SOURCEFORGE: how do *you* handle it? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ohauer@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 17:36:05 -0000 On 2011-08-29 04:05, Conrad J. Sabatier wrote: > I'm wondering how other ports maintainers are dealing with their > definitions of MASTER_SITES=, DISTFILES=, DISTNAME=, etc. with regards > to Sourceforge. > > In browsing a number of projects recently on Sourceforge, I've noticed > that the paths to project distfiles are now using the element > "projects" rather than "project". > > What I'm looking for is how to declare things in a clean and elegant > fashion in a port's Makefile to handle these cases, one that will > hopefully not require any revisions for later upgrades. Is it necessary > to just scrap the "SF" definition entirely and hardcode the URL? > > In addition, I've run across a few projects that use slightly differing > versions of the project name, either somewhere in the path or for the > distfile name itself. For example, looking at the "scidvspc" project > earlier today, I noticed this: > > The link for the distfile is defined as: > > http://sourceforge.net/projects/scidvspc/files/source/scid_vs_pc-4.5.tgz/download > > Clicking the download link, one is presented with alternatives in case > the download doesn't start automatically. > > The "mirror" link: > > https://sourceforge.net/settings/mirror_choices?projectname=scidvspc&filename=source/scid_vs_pc-4.5.tgz > > The "direct link": > > https://downloads.sourceforge.net/project/scidvspc/source/scid_vs_pc-4.5.tgz?r=&ts=1314582468&use_mirror=superb-sea2 > > Frankly, I'm baffled as to how our current definition of > "MASTER_SITES=SF/" is supposed to handle all of this. > > Can anyone point me towards a source of enlightenment? :-) > Hi Conrad, It depends a little on the port name, I will show two ways. 1) PORTNAME= scidvspc PORTVERSION= 4.5 CATEGORIES= games MASTER_SITES= SF MASTER_SITE_SUBDIR= scidvspc/source DISTNAME= scid_vs_pc-${PORTVERSION}.tgz 2) PORTNAME= scid_vs_pc PORTVERSION= 4.5 CATEGORIES= games MASTER_SITES= SF MASTER_SITE_SUBDIR= scidvspc/source EXTRACT_SUFX= .tgz If the source is not already in $distdir you can check the resulting url's with the command $> make fetch-list -- olli From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 17:36:46 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 951331065673; Mon, 29 Aug 2011 17:36:46 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward13.mail.yandex.net (forward13.mail.yandex.net [IPv6:2a02:6b8:0:801::3]) by mx1.freebsd.org (Postfix) with ESMTP id 19AD38FC1F; Mon, 29 Aug 2011 17:36:46 +0000 (UTC) Received: from smtp12.mail.yandex.net (smtp12.mail.yandex.net [95.108.131.191]) by forward13.mail.yandex.net (Yandex) with ESMTP id 8503B141779; Mon, 29 Aug 2011 21:36:44 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314639404; bh=u+aspIvzAbu50672lsVFxyWCB+jmCPsajG+o+5cR2cU=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:Content-Type: Content-Transfer-Encoding; b=TX7uz9/lxo8wH3/taI65g3dvHa+IL9Hjyo2ERWQ9LaLKzU9Af5zCuq/GBKfgHbcB+ cyhUhRXX40bZY+CvKgfSMldbDVqRrxEK+VaMYF0I/3xMcfBY2Tk0HNDPkE0hLVQ6NO 58T5f6niTUhaGdnL2IuEU2IjqMoWHq3gWVnX7K1M= Received: from smtp12.mail.yandex.net (localhost [127.0.0.1]) by smtp12.mail.yandex.net (Yandex) with ESMTP id 6FB6D16A0395; Mon, 29 Aug 2011 21:36:44 +0400 (MSD) Received: from unknown (unknown [178.76.212.172]) by smtp12.mail.yandex.net (nwsmtp/Yandex) with ESMTP id aik8ZarS; Mon, 29 Aug 2011 21:36:44 +0400 X-Yandex-Spam: 1 Message-ID: <4E5BCE2A.2050303@yandex.ru> Date: Mon, 29 Aug 2011 21:36:42 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: FreeBSD Ports Mailing List Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: mnag@FreeBSD.org Subject: Retiring of databases/py-pysqlite2x X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 17:36:46 -0000 He there. I'm finally finished the work of eliminating databases/py-pysqlite2x consumers. I mean this obsoleted ports: databases/py-pysqlite20 databases/py-pysqlite21 databases/py-pysqlite22 databases/py-pysqlite23 They are unmaintained upstream, not existed on mastersites (besides FreeBSD ones) peaces of software, deprecated upstream, that is for python24 and less. All the modern software uses databases/py-sqlite3, that is a part of python distribution since 2.5. They may be safely removed after all of this guys will be committed: audio/pytone ports/160053 commited databases/py-axiom ports/160260 wen@ databases/py-sqlobject ports/160059 wen@ deskutils/gourmet ports/160165 beech@ deskutils/griffith ports/160161 unassigned devel/bzr-git ports/160069 glarkin@ games/anki ports/160055 unassigned games/gcompris ports/160054 gnome@ multimedia/gpodder ports/160155 commited multimedia/miro ports/160070 unassigned approved security/umit ports/160072 unassigned security/zenmap ports/160071 unassigned sysutils/flyback ports/160157 commited textproc/translate-toolkit ports/160261 jpaetzel@ www/roundup ports/160220 sbz@ deskutils/conduit ports/160063 gnome@ multimedia/pyjama ports/160065 unassigned approved multimedia/py-openlp ports/160285 tabthorpe@ security/hotssh ports/160066 unassigned should be ashish@ security/pwman3 ports/160288 unassigned (I know you will hate me for this short urls, but it's to not break formatting. Here is the url that you may use to join pr's numbers to for convenience :) http://www.freebsd.org/cgi/query-pr.cgi?pr= ) So if anybody interested in moving some cruft from the tree, they may pick the pr's that is unassigned atm. Thanks. -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 17:58:19 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92BA7106566B for ; Mon, 29 Aug 2011 17:58:19 +0000 (UTC) (envelope-from ade@FreeBSD.org) Received: from panix.lovett.com (panix.lovett.com [166.84.7.128]) by mx1.freebsd.org (Postfix) with ESMTP id 6A4B78FC0C for ; Mon, 29 Aug 2011 17:58:19 +0000 (UTC) Received: from r74-192-180-219.htvlcmta01.hnvitx.tl.dh.suddenlink.net ([74.192.180.219] helo=lab.lovett.com) by panix.lovett.com with esmtpa (Exim 4.76 (FreeBSD)) (envelope-from ) id 1Qy5Pm-000EzP-Uq; Mon, 29 Aug 2011 17:14:27 +0000 Date: Mon, 29 Aug 2011 12:14:15 -0500 From: Ade Lovett To: Chris Rees Message-ID: <20110829121415.237a3571@lab.lovett.com> In-Reply-To: References: <4E5643A8.9060705@yandex.ru> <4E564DBE.1070700@yandex.ru> <4E574264.6020600@yandex.ru> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports Mailing List Subject: Re: tinderbox: how to drop unneded Jail and Build X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 17:58:19 -0000 On Fri, 26 Aug 2011 11:10:30 +0100 Chris Rees wrote: > http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/tinderweb/dbsrc/ > > Watch out, there be dragons :( But they're happy dragons ;) As an aside, if there's likely to be 'official' translations of the tinderbox documents, it may be useful to follow the way in which the Handbook is generated under /usr/doc, move (most of?) the current contents of dbsrc/ to dbsrc/en and go from there. -aDe From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 18:06:01 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 381671065674 for ; Mon, 29 Aug 2011 18:06:01 +0000 (UTC) (envelope-from pawelbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id B42268FC0A for ; Mon, 29 Aug 2011 18:06:00 +0000 (UTC) Received: by bkat8 with SMTP id t8so5923775bka.13 for ; Mon, 29 Aug 2011 11:05:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:date:from:to:subject:message-id:in-reply-to:references :x-mailer:mime-version:content-type:content-transfer-encoding; bh=lhQ+XIlI0Qu1zg1A9QwoA/JWXNkxGfFI1V3aViI+6Pc=; b=aPJvOfrgIabdTmVn9hyuX4/qstZ4qSbbXSQnXlyV3dt7/HY9DI8aex6T0GKi2ikxOJ 7ZwrlLNptjXoVGNx4bXpz9DKrRVJcbMcGEhDdLGgavsopYpqi2z4vZ6Jgm8gtiU7bi72 zDg1qN2XYve8tp5XAtNqHwkhbrHFUeJOfnA5E= Received: by 10.204.142.144 with SMTP id q16mr2501433bku.268.1314641159573; Mon, 29 Aug 2011 11:05:59 -0700 (PDT) Received: from localhost (adac25.neoplus.adsl.tpnet.pl [83.11.238.25]) by mx.google.com with ESMTPS id q1sm2781793faa.3.2011.08.29.11.05.57 (version=SSLv3 cipher=OTHER); Mon, 29 Aug 2011 11:05:57 -0700 (PDT) Sender: =?UTF-8?B?UGF3ZcWCIFDEmWthbGE=?= Date: Mon, 29 Aug 2011 20:05:25 +0200 From: Pawel Pekala To: freebsd-ports@freebsd.org Message-ID: <20110829200525.02d57b68@freebsd.org> In-Reply-To: References: X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable Subject: Re: claws-mail-fancy crashes after updating libproxy X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 18:06:01 -0000 Dnia 2011-08-26, o godz. 15:37:00 Carmel napisa=B3(a): >Since that is the only thing that has materially changed on my system, >I believe the problem can be traced to it. Has anyone else experienced >this phenomena? I can't reproduce it, at least with version 0.9.14 which I have committed today. --=20 pozdrawiam / with regards Pawe=B3 P=EAkala From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 18:14:09 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D1621065676 for ; Mon, 29 Aug 2011 18:14:09 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo203.cox.net (eastrmfepo203.cox.net [68.230.241.218]) by mx1.freebsd.org (Postfix) with ESMTP id 2725A8FC08 for ; Mon, 29 Aug 2011 18:14:08 +0000 (UTC) Received: from eastrmimpo02.cox.net ([68.1.16.120]) by eastrmfepo203.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20110829181408.HUJJ32702.eastrmfepo203.cox.net@eastrmimpo02.cox.net> for ; Mon, 29 Aug 2011 14:14:08 -0400 Received: from serene.no-ip.org ([98.164.83.25]) by eastrmimpo02.cox.net with bizsmtp id SJE71h00d0YnB6A02JE8ha; Mon, 29 Aug 2011 14:14:08 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020208.4E5BD6F0.00AA,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=ax4i8a8snyEA9uWfgWYmXW+3D+RWNhitQWxcW0Jxd9c= c=1 sm=1 a=wWrJEvAoo_wA:10 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=2vO5UZG1h46htWAnE/rx2g==:17 a=G0q-payyAAAA:8 a=FP58Ms26AAAA:8 a=kviXuzpPAAAA:8 a=PcoLsz3Ql31y4TSCaOEA:9 a=hdlFTQfFunIibjB3DHYA:7 a=CjuIK1q_8ugA:10 a=673AGJE-P7wA:10 a=4vB-4DCPJfMA:10 a=GhoF0X3YURPxc8pE:21 a=8FYdWz4nTSjzamoM:21 a=2vO5UZG1h46htWAnE/rx2g==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from cox.net (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id p7TIE7oa033786 for ; Mon, 29 Aug 2011 13:14:07 -0500 (CDT) (envelope-from conrads@cox.net) Date: Mon, 29 Aug 2011 13:14:02 -0500 From: "Conrad J. Sabatier" To: freebsd-ports@freebsd.org Message-ID: <20110829131402.15dad07b@cox.net> In-Reply-To: <4E5BABD0.9090300@xaerolimit.net> References: <20110828210511.3d2e0604@cox.net> <4E5BABD0.9090300@xaerolimit.net> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: MASTER_SITE_SOURCEFORGE: how do *you* handle it? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 18:14:09 -0000 On Mon, 29 Aug 2011 11:10:08 -0400 Chris Brennan wrote: > On 8/28/2011 10:05 PM, Conrad J. Sabatier wrote: > > > > In browsing a number of projects recently on Sourceforge, I've > > noticed that the paths to project distfiles are now using the > > element "projects" rather than "project". > > > > What I'm looking for is how to declare things in a clean and > > elegant fashion in a port's Makefile to handle these cases, one > > that will hopefully not require any revisions for later upgrades. > > Is it necessary to just scrap the "SF" definition entirely and > > hardcode the URL? > > > > In addition, I've run across a few projects that use slightly > > differing versions of the project name, either somewhere in the path > > or for the distfile name itself. For example, looking at the > > "scidvspc" project earlier today, I noticed this: > > > > The link for the distfile is defined as: > > > > http://sourceforge.net/projects/scidvspc/files/source/scid_vs_pc-4.5.tgz/download > > > > Clicking the download link, one is presented with alternatives in > > case the download doesn't start automatically. > > > > The "mirror" link: > > > > https://sourceforge.net/settings/mirror_choices?projectname=scidvspc&filename=source/scid_vs_pc-4.5.tgz > > > > The "direct link": > > > > https://downloads.sourceforge.net/project/scidvspc/source/scid_vs_pc-4.5.tgz?r=&ts=1314582468&use_mirror=superb-sea2 > > > > Frankly, I'm baffled as to how our current definition of > > "MASTER_SITES=SF/" is supposed to handle all of this. > > Slightly related and unrelated at the same time. So sorry if I drifted > too far. I was discussing this very concept about a month ago with a > friend. I was trying to update my PortableApps.om installation and the > script I had written to fetch updated apps broke because I couldn't > figure out how to handle these new url's. It would see SF's idea of a > direct link is a redirect, thus obfuscating the real servers even more > and the path the project is in.... Yes, it's kind of crazy what's going on with Sourceforge these days. Used to be that the URL for a given project's file(s) was a pretty straightforward, standard affair, with the URL invariably ending with the name of the file. Now they're using all these "download" links instead, with redirects automatically being invoked, as well as unexpectedly inconsistent elements within the URL. I'm surprised there haven't been a lot of reports already of unfetchable distfiles and/or broken links in ports' Makefiles. I had to step back from it for a while, as after numerous attempts to find a clean and simple way to handle the new URL scheme, I got dizzy. :-) Maybe I'll get back to it sometime today. It may turn out that there is, in fact, no general, one-size-fits-all solution for this. I don't know. Isn't anyone else (ports maintainers in particular) running into any trouble with this? -- Conrad J. Sabatier conrads@cox.net From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 18:47:53 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 166DD106564A for ; Mon, 29 Aug 2011 18:47:53 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id C31C28FC0A for ; Mon, 29 Aug 2011 18:47:52 +0000 (UTC) Received: by vws18 with SMTP id 18so6249123vws.13 for ; Mon, 29 Aug 2011 11:47:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5lwxMsB3VxKleJJE6nEC/CcdZBAFUagRSxlT2yxrwKo=; b=OKsW7U50q8uYDGIrKIr23Fz0S7fO7kAO//q339YB27jgllcsW7YbymoTHFKO9ygahE w29mOhwDx5ahATjCT2E/iovMIvZbJAiHxvuot6U+Wj1NWBgJMsCzZKF7pGpCGPO+JhCb 8jQaMaKxiMDJa59OiLZ4MkJrNxQZgOqYI1cJk= MIME-Version: 1.0 Received: by 10.220.99.140 with SMTP id u12mr1995337vcn.19.1314642137725; Mon, 29 Aug 2011 11:22:17 -0700 (PDT) Received: by 10.220.201.135 with HTTP; Mon, 29 Aug 2011 11:22:17 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Aug 2011 11:22:17 -0700 Message-ID: From: Freddie Cash To: srn@k66.ru Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: ports@freebsd.org Subject: Re: freevrrpd X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 18:47:53 -0000 2011/8/26 > Hello, my name is Mihail Suhorosov, Im from Russia and I use you port for > FreeBSD freevrrpd.(My BSD version is 8.2) > > I have some problem. I can't start this programm. My config is: > [VRID] > serverid = 1 > interface = re0 > priority = 255 > addr = 10.50.40.8/32 > #masterscript = /usr/local/bin/master_script.**sh > #backupscript = /usr/local/bin/backup_script.**sh > #password = vrid1 > > After start I see in log: > Aug 26 17:31:52 tim freevrrpd[1687]: launching daemon in background mode > Aug 26 17:31:52 tim freevrrpd[1688]: initializing threads and all VRID > Aug 26 17:31:52 tim freevrrpd[1688]: reading configuration file > /usr/local/etc/freevrrpd.conf > Aug 26 17:31:52 tim freevrrpd[1688]: cannot create a bridge device: No such > file or directory > Aug 26 17:31:52 tim freevrrpd[1688]: aborting... > > So i think it cant connetct to interface. But why i dont know.... > In my netcard i have alias 10.50.40.8 > Do not assign an IP address to the interface in /etc/rc.conf. Just mark it as "up": ifconfig_re0="up" Then, when freevrrpd starts, it will create a new pseudo-interface via netgraph, and assign the IP to that interface automatically. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 18:49:22 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6BD3106564A for ; Mon, 29 Aug 2011 18:49:22 +0000 (UTC) (envelope-from carmel_ny@hotmail.com) Received: from blu0-omc3-s27.blu0.hotmail.com (blu0-omc3-s27.blu0.hotmail.com [65.55.116.102]) by mx1.freebsd.org (Postfix) with ESMTP id 8EA4A8FC13 for ; Mon, 29 Aug 2011 18:49:22 +0000 (UTC) Received: from BLU0-SMTP445 ([65.55.116.72]) by blu0-omc3-s27.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 29 Aug 2011 11:49:22 -0700 X-Originating-IP: [174.109.142.1] X-Originating-Email: [carmel_ny@hotmail.com] Message-ID: Received: from scorpio.seibercom.net ([174.109.142.1]) by BLU0-SMTP445.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 29 Aug 2011 11:49:20 -0700 Received: from scorpio (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: carmel_ny@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3Rnhpm0F2Dz2CG44 for ; Mon, 29 Aug 2011 14:49:20 -0400 (EDT) Date: Mon, 29 Aug 2011 14:49:19 -0400 From: Carmel To: freebsd-ports@freebsd.org In-Reply-To: <20110829200525.02d57b68@freebsd.org> References: <20110829200525.02d57b68@freebsd.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 29 Aug 2011 18:49:21.0039 (UTC) FILETIME=[5D12C1F0:01CC667C] Subject: Re: claws-mail-fancy crashes after updating libproxy X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 18:49:22 -0000 On Mon, 29 Aug 2011 20:05:25 +0200 Pawel Pekala articulated: > I can't reproduce it, at least with version 0.9.14 which I have > committed today. I just updated and the new version works as expected. I had filed a bug report with the claws-mail crew; however, I am not aware of them having actually done anything. -- Carmel ✌ carmel_ny@hotmail.com From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 19:32:08 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADFD7106564A for ; Mon, 29 Aug 2011 19:32:08 +0000 (UTC) (envelope-from freebsd-ports@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 686A58FC17 for ; Mon, 29 Aug 2011 19:32:08 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Qy7Yy-0006HR-4F for freebsd-ports@freebsd.org; Mon, 29 Aug 2011 21:32:04 +0200 Received: from 189.61.193.250 ([189.61.193.250]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Aug 2011 21:32:04 +0200 Received: from rakuco by 189.61.193.250 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Aug 2011 21:32:04 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-ports@freebsd.org From: Raphael Kubo da Costa Date: Mon, 29 Aug 2011 16:31:48 -0300 Lines: 14 Message-ID: <87pqjoggkb.fsf@FreeBSD.org> References: <4E385E09.20208@FreeBSD.org> <20110812110703.GA52137@bonjour.sunpoet.net> <4E5B6525.2020604@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 189.61.193.250 User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.3 (berkeley-unix) Cancel-Lock: sha1:gfKytcxUhY27hqlhV6ii0YUpD60= Subject: Re: Any progress on updating boost? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 19:32:08 -0000 Doug Barton writes: > rebuilt those 2 against the new boost libs. qbittorrrent starts up Ok, > but then it ends up freezing solid, needing to be killed. On the console > I get a whole bunch of these: > > WARNING pid 86327 (qbittorrent): ioctl sign-extension ioctl ffffffff8004667e > > This is on recent 9-current amd64. The only boost OPTION I have enabled > is the one for optimized cflags. Perhaps this one could be related to [1]? [1] http://mail.kde.org/pipermail/kde-freebsd/2010-June/008681.html From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 20:44:31 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2691106564A for ; Mon, 29 Aug 2011 20:44:31 +0000 (UTC) (envelope-from talon@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 4A9FF8FC13 for ; Mon, 29 Aug 2011 20:44:30 +0000 (UTC) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.14.4/jtpda-5.4) with ESMTP id p7TKhpfY001907 for ; Mon, 29 Aug 2011 22:43:51 +0200 (CEST) X-Ids: 164 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id E11AB21C64 for ; Mon, 29 Aug 2011 22:44:27 +0200 (CEST) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id 9E61A4ADF; Mon, 29 Aug 2011 22:44:27 +0200 (CEST) Date: Mon, 29 Aug 2011 22:44:27 +0200 From: Michel Talon To: freebsd-ports@FreeBSD.org Message-ID: <20110829204427.GA63528@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Miltered: at jchkmail.jussieu.fr with ID 4E5BFA2D.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4E5BFA2D.000/134.157.10.1/parthe.lpthe.jussieu.fr/parthe.lpthe.jussieu.fr/ Cc: Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 20:44:31 -0000 >Chad Perrin said: > >On Mon, Aug 29, 2011 at 12:17:12AM -0700, Doug Barton wrote: >> FreeBSD needs to get better in this area, but I seriously doubt it >> will >> ever be as easy and painless as something like ubuntu. > >For a great many use cases, Ubuntu is one of the most painful "desktop" >user experiences I have ever encountered. Please, *please* do not >emulate Ubuntu. Any discussion on such subjects should begin by switching off the reality distortion field. For *my own experience* Ubuntu works perfectly OK, in particular all the hardware on my laptop works, suspend works, i have zero problem keeping the "ports" updated, etc. It is the completely no fuss solution. Wether FreeBSD needs to go in a direction or another is a different subject, but *please* be objective in your descriptions. By the way: >it installs software and runs >servers the user will never have any occasion to use, with no obvious >way >to deactivate them; and it essentially enforces the use of huge >collections of software by way of hopelessly intertangled dependencies. is a sentence you can easily apply to any modern system. And most users could not care less that there is *bloat* on their hard disk. Anyways you can find a functional and installable desktop Ubuntu system on a simple CDROM, show me the same for FreeBSD and i will happily conclude it is less bloated. And for the same price you have on said CDROM a live system and an installer which is not a joke like FreeBSD one. Wonder why one system has more users than the other ... -- Michel TALON From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 20:51:38 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EFC71065672 for ; Mon, 29 Aug 2011 20:51:38 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id B720E8FC12 for ; Mon, 29 Aug 2011 20:51:37 +0000 (UTC) Received: by fxe4 with SMTP id 4so6231492fxe.13 for ; Mon, 29 Aug 2011 13:51:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=R3FNW420097B4z/KxSgkprQ6cp5Oin92tQLzKGuP3D0=; b=XCzdLWBP20nUY8mZXho3rfaga6EiZOwXgEIsKmiiumSHYYkPPvEoAmQzIZy6Aq7ZCD Kf/S8t/fbK/gXvSXsyVhFAHIztB3FOPOZYO63IhxsuvdAsFmZSAKR7RzC8qtp5jzKtTC oKLNHNU+YX0gL2gWtcDTBWwhOZ7U17BeNPaZg= MIME-Version: 1.0 Received: by 10.223.55.205 with SMTP id v13mr4606770fag.88.1314651096598; Mon, 29 Aug 2011 13:51:36 -0700 (PDT) Received: by 10.223.120.72 with HTTP; Mon, 29 Aug 2011 13:51:36 -0700 (PDT) In-Reply-To: <20110829204427.GA63528@lpthe.jussieu.fr> References: <20110829204427.GA63528@lpthe.jussieu.fr> Date: Mon, 29 Aug 2011 15:51:36 -0500 Message-ID: From: Adam Vande More To: Michel Talon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-ports@freebsd.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 20:51:38 -0000 On Mon, Aug 29, 2011 at 3:44 PM, Michel Talon wrote: > > > Any discussion on such subjects should begin by switching off the reality > distortion field. For *my own experience* Ubuntu works perfectly OK, in > particular all the hardware on my laptop works, suspend works, i have > zero problem keeping the "ports" updated, etc. It is the completely no > fuss solution. Wether FreeBSD needs to go in a direction or another is a > different subject, but *please* be objective in your descriptions. > I can cite more anecdotal evidence to the contrary but that will just perpetuate this infinite regression. > is a sentence you can easily apply to any modern system. And most users > could not care less that there is *bloat* on their hard disk. Anyways > you can find a functional and installable desktop Ubuntu system > on a simple CDROM, show me the same for FreeBSD and i will happily > conclude it is less bloated. > ftp://mirrors.isc.org/pub/pcbsd/9.0-BETA1.5/i386/PCBSD9.0-BETA1.5-x86-CD.iso Your other concerns are just as easily answered if you look. -- Adam Vande More From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 20:51:58 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D46A0106564A for ; Mon, 29 Aug 2011 20:51:58 +0000 (UTC) (envelope-from jeroen@virtualhost.nl) Received: from mail.virtualhost.nl (mail.virtualhost.nl [89.200.201.133]) by mx1.freebsd.org (Postfix) with ESMTP id 1D1068FC19 for ; Mon, 29 Aug 2011 20:51:57 +0000 (UTC) Received: (qmail 62730 invoked by uid 1141); 29 Aug 2011 22:51:56 +0200 Received: from ip120-12-208-87.adsl2.static.versatel.nl (HELO blue.myspectrum.nl) (87.208.12.120) (smtp-auth username jeroen@virtualhost.nl, mechanism plain) by mail.virtualhost.nl (qpsmtpd/0.84) with (CAMELLIA256-SHA encrypted) ESMTPSA; Mon, 29 Aug 2011 22:51:56 +0200 Message-ID: <4E5BFBEB.4020900@virtualhost.nl> Date: Mon, 29 Aug 2011 22:51:55 +0200 From: Jeroen User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:5.0) Gecko/20110801 Thunderbird/5.0 MIME-Version: 1.0 To: Ruslan Mahmatkhanov References: <4E5AB569.4060703@virtualhost.nl> <4E5B604B.1090902@yandex.ru> In-Reply-To: <4E5B604B.1090902@yandex.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org, david@catwhisker.org Subject: Re: firefox 6: mercurial seems to be missing as depency X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 20:51:58 -0000 >> When updating firefox to the latest version (from ports) it complained >> about hg not being found. Apparently a dependency to mercurial is >> missing. I haven't checked why, installing it resolved it. > Can you please show us exact error message for further investigation? > Hi, I don't have a rational for this. I can explain what I did. Portaudit said there's a vulnerability in Firefox 5, so I did a make in /usr/ports/www/firefox (from within gnome). And it stopped somewhere at 'hg not found' or similiar, so I blindly installed mercurial and hit make again; and make install, and all went fine after doing that. Afterwards I though this was a bit strange and decided to send a mail to ports@. Don't know what really happened though, hence the '*seems*' . This evening I removed /usr/ports/ completely and mecurial. Did a portsnap and tried to make firefox, resulting in similar errors: like hg not found, repeated twice, followed by a sed error about a missing file. I lost the raw output though since switching between gnome and console does not recover gnome properly while I had the output there... So currently I have not something useful to add, building again from console, but don't dare to switch, at the moment. Regards, Jeroen From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 21:48:10 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FE091065672 for ; Mon, 29 Aug 2011 21:48:10 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D4B878FC17; Mon, 29 Aug 2011 21:48:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p7TLm9Ep081466; Mon, 29 Aug 2011 21:48:09 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p7TLm9ch081463; Mon, 29 Aug 2011 21:48:09 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Mon, 29 Aug 2011 23:48:05 +0200 From: Baptiste Daroussin To: Ruslan Mahmatkhanov Message-ID: <20110829214805.GF68812@azathoth.lan> References: <4E5BCE2A.2050303@yandex.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="juZjCTNxrMaZdGZC" Content-Disposition: inline In-Reply-To: <4E5BCE2A.2050303@yandex.ru> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Ports Mailing List Subject: Re: Retiring of databases/py-pysqlite2x X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 21:48:10 -0000 --juZjCTNxrMaZdGZC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 29, 2011 at 09:36:42PM +0400, Ruslan Mahmatkhanov wrote: > He there. >=20 > I'm finally finished the work of eliminating databases/py-pysqlite2x=20 > consumers. I mean this obsoleted ports: >=20 > databases/py-pysqlite20 > databases/py-pysqlite21 > databases/py-pysqlite22 > databases/py-pysqlite23 >=20 > They are unmaintained upstream, not existed on mastersites (besides=20 > FreeBSD ones) peaces of software, deprecated upstream, that is for=20 > python24 and less. All the modern software uses databases/py-sqlite3, > that is a part of python distribution since 2.5. >=20 > They may be safely removed after all of this guys will be committed: > audio/pytone ports/160053 commited > databases/py-axiom ports/160260 wen@ > databases/py-sqlobject ports/160059 wen@ > deskutils/gourmet ports/160165 beech@ > deskutils/griffith ports/160161 unassigned > devel/bzr-git ports/160069 glarkin@ > games/anki ports/160055 unassigned > games/gcompris ports/160054 gnome@ > multimedia/gpodder ports/160155 commited > multimedia/miro ports/160070 unassigned approved > security/umit ports/160072 unassigned > security/zenmap ports/160071 unassigned > sysutils/flyback ports/160157 commited > textproc/translate-toolkit ports/160261 jpaetzel@ > www/roundup ports/160220 sbz@ > deskutils/conduit ports/160063 gnome@ > multimedia/pyjama ports/160065 unassigned approved > multimedia/py-openlp ports/160285 tabthorpe@ > security/hotssh ports/160066 unassigned should be ashish@ > security/pwman3 ports/160288 unassigned >=20 > (I know you will hate me for this short urls, but it's to not break=20 > formatting. Here is the url that you may use to join pr's numbers to for= =20 > convenience :) http://www.freebsd.org/cgi/query-pr.cgi?pr=3D ) >=20 > So if anybody interested in moving some cruft from the tree, they may=20 > pick the pr's that is unassigned atm. Thanks. Thank you very much for that work, I should have time soon to work on this = if noone already did it. regards, Bapt --juZjCTNxrMaZdGZC Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk5cCRUACgkQ8kTtMUmk6EzBSQCfem2U8I64nB8UQL/iRZoAyWSn 7lAAn0Hh10CsIDTammgOYGYv59vq8wSw =cRay -----END PGP SIGNATURE----- --juZjCTNxrMaZdGZC-- From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 22:04:57 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0DAE106564A; Mon, 29 Aug 2011 22:04:57 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BAD588FC0C; Mon, 29 Aug 2011 22:04:57 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p7TM4vDf098478; Mon, 29 Aug 2011 22:04:57 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p7TM4vSw098477; Mon, 29 Aug 2011 22:04:57 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Tue, 30 Aug 2011 00:04:53 +0200 From: Baptiste Daroussin To: Steven Kreuzer Message-ID: <20110829220453.GA71669@azathoth.lan> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-ports@FreeBSD.org Subject: Re: Speling Mistakes X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 22:04:57 -0000 --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 29, 2011 at 11:07:26AM -0400, Steven Kreuzer wrote: > I would like to apply this patch > (http://www.exit2shell.com/~skreuzer/patches/speling.diff) which fixes > a few spelling mistakes in the COMMENT field for some > unmaintained ports: >=20 > games/qudos > editors/ne > misc/ftdi-eeprom > games/egl > devel/py-period > devel/p5-Penguin-Easy > games/r1q2 > games/tremor > textproc/mkcatalog > databases/p5-DBIx-AnyDBD > net/ncplib >=20 > Anyone have any objections? I think noone would object on this, just go ahead :) regards, Bapt --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk5cDQUACgkQ8kTtMUmk6EzpGACdFOmzcGWuQHUmkiiQ7xDBlTuF 10sAnigUIyr01fBYEPkqZgNkhaR6i2+0 =GLOf -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP-- From owner-freebsd-ports@FreeBSD.ORG Mon Aug 29 23:46:32 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF723106564A for ; Mon, 29 Aug 2011 23:46:32 +0000 (UTC) (envelope-from code@apotheon.net) Received: from oproxy7-pub.bluehost.com (oproxy7.bluehost.com [IPv6:2605:dc00:100:2::a7]) by mx1.freebsd.org (Postfix) with SMTP id 821848FC08 for ; Mon, 29 Aug 2011 23:46:32 +0000 (UTC) Received: (qmail 14038 invoked by uid 0); 29 Aug 2011 23:46:30 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by oproxy7.bluehost.com with SMTP; 29 Aug 2011 23:46:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.net; s=default; h=In-Reply-To:Content-Type:Mime-Version:References:Message-ID:Subject:To:From:Date; bh=KqFblNYaLAQIxtApb1jJlfK5J1GR794kdC1JaPy1zeA=; b=GhQxP41mRVoU8QmWbF4+Xoxi+oSvIft0WzsMtPbJ71Rl6itty4Spr96AzDXBycUFqSqlMbzcC0+vDQLl9WYblOrUZXE33cCL8SX9uoz1usjeRFMEsKJCiE+fQdd+KIv+; Received: from c-24-8-180-234.hsd1.co.comcast.net ([24.8.180.234] helo=kukaburra.hydra) by box543.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1QyBXA-0006Xa-RO for freebsd-ports@FreeBSD.org; Mon, 29 Aug 2011 17:46:29 -0600 Received: by kukaburra.hydra (sSMTP sendmail emulation); Mon, 29 Aug 2011 17:28:05 -0600 Date: Mon, 29 Aug 2011 17:28:05 -0600 From: Chad Perrin To: freebsd-ports@FreeBSD.org Message-ID: <20110829232805.GA66332@guilt.hydra> Mail-Followup-To: freebsd-ports@FreeBSD.org References: <20110829204427.GA63528@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99" Content-Disposition: inline In-Reply-To: <20110829204427.GA63528@lpthe.jussieu.fr> User-Agent: Mutt/1.4.2.3i X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.org} {sentby:smtp auth 24.8.180.234 authed with ren@apotheon.org} Cc: Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 23:46:32 -0000 --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 29, 2011 at 10:44:27PM +0200, Michel Talon wrote: > >Chad Perrin said: > > > >On Mon, Aug 29, 2011 at 12:17:12AM -0700, Doug Barton wrote: > >> FreeBSD needs to get better in this area, but I seriously doubt it > >> will > >> ever be as easy and painless as something like ubuntu. > > > >For a great many use cases, Ubuntu is one of the most painful "desktop" > >user experiences I have ever encountered. Please, *please* do not > >emulate Ubuntu. >=20 > Any discussion on such subjects should begin by switching off the reality > distortion field. For *my own experience* Ubuntu works perfectly OK, in > particular all the hardware on my laptop works, suspend works, i have > zero problem keeping the "ports" updated, etc. It is the completely no > fuss solution. Wether FreeBSD needs to go in a direction or another is a > different subject, but *please* be objective in your descriptions. There's no reality distortion field here, unless it's yours. Neither Ubuntu nor FreeBSD is objectively better. Each is better for specific use cases. Your *subjective* experience of no fuss is based on a wildly different set of priorities than me. If you prefer Ubuntu's usability priorities, I wish you'd just use Ubuntu, rather than try to convince people that it's "objectively" better than FreeBSD -- thus implying FreeBSD should emulate as if it is without flaws. >=20 > By the way: > >it installs software and runs > >servers the user will never have any occasion to use, with no obvious > >way > >to deactivate them; and it essentially enforces the use of huge > >collections of software by way of hopelessly intertangled dependencies. >=20 > is a sentence you can easily apply to any modern system. And most users > could not care less that there is *bloat* on their hard disk. Anyways > you can find a functional and installable desktop Ubuntu system > on a simple CDROM, show me the same for FreeBSD and i will happily > conclude it is less bloated. And for the same price you have on said > CDROM a live system and an installer which is not a joke like FreeBSD > one. Wonder why one system has more users than the other ... That would have been much shorter if you just said: "I can't tell the difference between the two where it matters, and I have different priorities than you." Of course, your goal is apparently to convince me that yours are the "correct" priorities. --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --5vNYLRcllDrimb99 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk5cIIUACgkQ9mn/Pj01uKXa7gCg5Eksh67Iu6a01DUSZ3WZogxT P5cAnj0Xb5j+c0xCHKEUT3wdlEifm/Qq =NqpP -----END PGP SIGNATURE----- --5vNYLRcllDrimb99-- From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 00:17:47 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74317106566B for ; Tue, 30 Aug 2011 00:17:47 +0000 (UTC) (envelope-from amistry@am-productions.biz) Received: from mail.united-ware.com (svr20881129-177.ihostservers.net [208.81.129.177]) by mx1.freebsd.org (Postfix) with ESMTP id 0C59E8FC15 for ; Tue, 30 Aug 2011 00:17:46 +0000 (UTC) Received: from bigguy.am-productions.biz (adsl-75-60-187-59.dsl.wotnoh.sbcglobal.net [75.60.187.59]) (authenticated bits=0) by mail.united-ware.com (8.14.4/8.14.4) with ESMTP id p7TNmMYs026661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Aug 2011 19:48:23 -0400 (EDT) (envelope-from amistry@am-productions.biz) From: Anish Mistry To: Brandon Gooch Date: Mon, 29 Aug 2011 19:50:26 -0400 User-Agent: KMail/1.13.7 (FreeBSD/8.2-RELEASE-p1; KDE/4.6.5; amd64; ; ) References: <4E3EE2CB.6050704@protected-networks.net> <20110807211700.20043883@fabiankeil.de> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2100347.WmilFbGKsp"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201108291950.33685.amistry@am-productions.biz> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.united-ware.com [208.81.129.177]); Mon, 29 Aug 2011 19:48:23 -0400 (EDT) Cc: ports@freebsd.org, Michael Butler Subject: Re: fusefs-kmod on recent -current X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 00:17:47 -0000 --nextPart2100347.WmilFbGKsp Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Saturday 27 August 2011 22:28:08 Brandon Gooch wrote: > On Sun, Aug 7, 2011 at 2:17 PM, Fabian Keil >=20 > wrote: > > Michael Butler wrote: > >> Seems that the change to the mount flags in recent -current has > >> broken the compilation of sysutils/fusefs-kmod :-( > >>=20 > >> It now needs something like the attached to compile, > >=20 > > The attachment didn't make it. Anyway, there's already a PR about > > it: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/159322 > >=20 > > Fabian >=20 > There are several patches actually: >=20 > http://www.freebsd.org/cgi/query-pr-summary.cgi?category=3D&severity=3D&p > riority=3D&class=3D&state=3D&sort=3Dnone&text=3Dfusefs-kmod&responsible= =3D&multit > ext=3D&originator=3D&release=3D >=20 > An appropriate one should be chosen that contains a check for the > FreeBSD version. >=20 > Getting the appropriate one committed seems to be the issue. Has > anyone heard from this amistry@am-productions.biz? Can we get a > manual override here? >=20 > Main point of this simple-to-fix issue is that as 9.0-RELEASE > approaches, having a broken fusefs-kmod is just bad news for a lot of > users -- and it looks bad for FreeBSD too. Yes, please. I'm currently swamped and don't have the time to attend to=20 these. Thanks, =2D-=20 Anish Mistry --nextPart2100347.WmilFbGKsp Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEABECAAYFAk5cJckACgkQxqA5ziudZT1vmgCeM9fqO7F7M4n1bm/nJSW5DCvw FV0AoNcND1JkXR3+MdJyvnwOxh44UcVL =3bjW -----END PGP SIGNATURE----- --nextPart2100347.WmilFbGKsp-- From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 00:41:47 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 255E5106566B for ; Tue, 30 Aug 2011 00:41:47 +0000 (UTC) (envelope-from rfarmer@predatorlabs.net) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id D89A48FC12 for ; Tue, 30 Aug 2011 00:41:46 +0000 (UTC) Received: by vws18 with SMTP id 18so6550034vws.13 for ; Mon, 29 Aug 2011 17:41:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=predatorlabs.net; s=google; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=7v3KPLNYT3SMYIMOFXaZQ1Y64CAKR4GNUyvpEXt23Kw=; b=HmytkyN+zZDLKcH6cVIKlEAjyChOLtJ67WS9Na0yi2/seZPLPuKfWYlSbhHxoW9+DQ qaLUF9KkqP4SaL86l7LJ5D+J8mgfXzlTkq/Jbnxz1wBE1xlK1h03Gs2mOuLtnEQ00sZ1 jXvB6JLvA5owlmKZz1qGelvJeWDXPiZgOU7vg= MIME-Version: 1.0 Received: by 10.52.92.148 with SMTP id cm20mr794149vdb.109.1314663538797; Mon, 29 Aug 2011 17:18:58 -0700 (PDT) Received: by 10.220.191.195 with HTTP; Mon, 29 Aug 2011 17:18:58 -0700 (PDT) X-Originating-IP: [67.232.77.3] In-Reply-To: <20110829131402.15dad07b@cox.net> References: <20110828210511.3d2e0604@cox.net> <4E5BABD0.9090300@xaerolimit.net> <20110829131402.15dad07b@cox.net> Date: Mon, 29 Aug 2011 17:18:58 -0700 Message-ID: From: Rob Farmer To: "Conrad J. Sabatier" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ports@freebsd.org Subject: Re: MASTER_SITE_SOURCEFORGE: how do *you* handle it? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 00:41:47 -0000 On Mon, Aug 29, 2011 at 11:14 AM, Conrad J. Sabatier wrot= e: > Yes, it's kind of crazy what's going on with Sourceforge these days. > Used to be that the URL for a given project's file(s) was a pretty > straightforward, standard affair, with the URL invariably ending with > the name of the file. =A0Now they're using all these "download" links > instead, with redirects automatically being invoked, as well as > unexpectedly inconsistent elements within the URL. =A0I'm surprised there > haven't been a lot of reports already of unfetchable distfiles and/or > broken links in ports' Makefiles. > > I had to step back from it for a while, as after numerous attempts to > find a clean and simple way to handle the new URL scheme, I got > dizzy. =A0:-) =A0Maybe I'll get back to it sometime today. =A0It may turn= out > that there is, in fact, no general, one-size-fits-all solution for this. > > I don't know. =A0Isn't anyone else (ports maintainers in particular) > running into any trouble with this? > Download it in your browser so that you can see the real url after all the redirect business is done: http://superb-sea2.dl.sourceforge.net/project/scidvspc/source/scid_vs_pc-4.= 5.tgz Now you can figure out the SF/whatever expansion with trial and error. I think they trying to discourage what we are doing - direct linking to specific mirrors and bypassing the load balancer. Right now all ports hit Heanet first (unless the user has set RANDOMIZE_MASTER_SITES or another override). --=20 Rob Farmer From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 01:08:29 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 3889D106564A for ; Tue, 30 Aug 2011 01:08:29 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id E9ACD14DFF8 for ; Tue, 30 Aug 2011 01:08:28 +0000 (UTC) Message-ID: <4E5C380F.4020207@FreeBSD.org> Date: Mon, 29 Aug 2011 18:08:31 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4E385E09.20208@FreeBSD.org> <20110812110703.GA52137@bonjour.sunpoet.net> <4E5B6525.2020604@FreeBSD.org> <87pqjoggkb.fsf@FreeBSD.org> In-Reply-To: <87pqjoggkb.fsf@FreeBSD.org> X-Enigmail-Version: 1.3.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Any progress on updating boost? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 01:08:29 -0000 On 8/29/2011 12:31 PM, Raphael Kubo da Costa wrote: > Doug Barton writes: > >> rebuilt those 2 against the new boost libs. qbittorrrent starts up Ok, >> but then it ends up freezing solid, needing to be killed. On the console >> I get a whole bunch of these: >> >> WARNING pid 86327 (qbittorrent): ioctl sign-extension ioctl ffffffff8004667e >> >> This is on recent 9-current amd64. The only boost OPTION I have enabled >> is the one for optimized cflags. > > Perhaps this one could be related to [1]? > > [1] http://mail.kde.org/pipermail/kde-freebsd/2010-June/008681.html I certainly wouldn't rule it out, but the only things that I changed when testing were as described in my previous post. I didn't touch qt4-network. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 01:14:06 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id D7997106564A for ; Tue, 30 Aug 2011 01:14:06 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 8527B14DAB0 for ; Tue, 30 Aug 2011 01:14:06 +0000 (UTC) Message-ID: <4E5C3961.3020100@FreeBSD.org> Date: Mon, 29 Aug 2011 18:14:09 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: In-Reply-To: X-Enigmail-Version: 1.3.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Speling Mistakes X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 01:14:06 -0000 On 8/29/2011 8:07 AM, Steven Kreuzer wrote: > I would like to apply this patch > (http://www.exit2shell.com/~skreuzer/patches/speling.diff) which fixes > a few spelling mistakes in the COMMENT field for some > unmaintained ports: Thank you for taking this on. :) -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 01:51:03 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBB9E106567B for ; Tue, 30 Aug 2011 01:51:03 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 624348FC12 for ; Tue, 30 Aug 2011 01:51:03 +0000 (UTC) Received: by wwi36 with SMTP id 36so6372400wwi.31 for ; Mon, 29 Aug 2011 18:51:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/Q72loJR5J/Lm/5A5ODKX35qnUlxZgTqYwlJdK4iRU4=; b=XybEXYkD+kSzLKL9pXJKL3e62QAa6ccw2Djoq9QmMX5ajYz3g/kalaPSizyPC5LT0o Tp1CPhO4WqlqgbP9n4C/A8A+kQEOX5N7ehlG1QzLtu9TxMIRghzPpPhMxih+myJRwXT4 BYnDNNy+4LbNwIqgOvMGn9rsAA57qCRL0ixyA= MIME-Version: 1.0 Received: by 10.216.210.206 with SMTP id u56mr2791351weo.21.1314669062013; Mon, 29 Aug 2011 18:51:02 -0700 (PDT) Received: by 10.216.74.5 with HTTP; Mon, 29 Aug 2011 18:51:01 -0700 (PDT) In-Reply-To: <201108291950.33685.amistry@am-productions.biz> References: <4E3EE2CB.6050704@protected-networks.net> <20110807211700.20043883@fabiankeil.de> <201108291950.33685.amistry@am-productions.biz> Date: Mon, 29 Aug 2011 20:51:01 -0500 Message-ID: From: Brandon Gooch To: Anish Mistry Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: ports@freebsd.org, Michael Butler Subject: Re: fusefs-kmod on recent -current X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 01:51:03 -0000 On Mon, Aug 29, 2011 at 6:50 PM, Anish Mistry wrote: > On Saturday 27 August 2011 22:28:08 Brandon Gooch wrote: >> On Sun, Aug 7, 2011 at 2:17 PM, Fabian Keil >> >> wrote: >> > Michael Butler wrote: >> >> Seems that the change to the mount flags in recent -current has >> >> broken the compilation of sysutils/fusefs-kmod :-( >> >> >> >> It now needs something like the attached to compile, >> > >> > The attachment didn't make it. Anyway, there's already a PR about >> > it: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/159322 >> > >> > Fabian >> >> There are several patches actually: >> >> http://www.freebsd.org/cgi/query-pr-summary.cgi?category=3D&severity=3D&= p >> riority=3D&class=3D&state=3D&sort=3Dnone&text=3Dfusefs-kmod&responsible= =3D&multit >> ext=3D&originator=3D&release=3D >> >> An appropriate one should be chosen that contains a check for the >> FreeBSD version. >> >> Getting the appropriate one committed seems to be the issue. Has >> anyone heard from this amistry@am-productions.biz? Can we get a >> manual override here? >> >> Main point of this simple-to-fix issue is that as 9.0-RELEASE >> approaches, having a broken fusefs-kmod is just bad news for a lot of >> users -- and it looks bad for FreeBSD too. > > Yes, please. =A0I'm currently swamped and don't have the time to attend t= o > these. > > Thanks, > > -- > Anish Mistry > Excellent, thanks for replying Anish. Anyone know what the next step is? -Brandon From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 04:14:59 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FE5C106566B; Tue, 30 Aug 2011 04:14:59 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward6.mail.yandex.net (forward6.mail.yandex.net [IPv6:2a02:6b8:0:202::1]) by mx1.freebsd.org (Postfix) with ESMTP id C7B218FC0C; Tue, 30 Aug 2011 04:14:58 +0000 (UTC) Received: from smtp9.mail.yandex.net (smtp9.mail.yandex.net [77.88.61.35]) by forward6.mail.yandex.net (Yandex) with ESMTP id 4179CF820E8; Tue, 30 Aug 2011 08:14:57 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314677697; bh=uAk7CHrlM/YE8kuOq8rSi5rx2R/PeIQblHRZdh9oAa8=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=dOsf7uPvYPY5ele54jENk9wEZsUtIpedxVq8//XI/m1irhtPP3mNBev5Qunp0r6re fbeaJTnXfi6cxYuF83hK1l8vtPI7el5HjWwbp55iSfd8jSbWqSkdYa+F3+og9M/5Pw XQRpvHHSYXivx9BW+yVp1UG+mn0cv6dtwVz460X8= Received: from smtp9.mail.yandex.net (localhost [127.0.0.1]) by smtp9.mail.yandex.net (Yandex) with ESMTP id 2D1DD1520258; Tue, 30 Aug 2011 08:14:57 +0400 (MSD) Received: from unknown (unknown [213.138.88.133]) by smtp9.mail.yandex.net (nwsmtp/Yandex) with ESMTP id Eu040DTT; Tue, 30 Aug 2011 08:14:57 +0400 X-Yandex-Spam: 1 Message-ID: <4E5C63BE.8060609@yandex.ru> Date: Tue, 30 Aug 2011 08:14:54 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: Baptiste Daroussin References: <4E5BCE2A.2050303@yandex.ru> <20110829214805.GF68812@azathoth.lan> In-Reply-To: <20110829214805.GF68812@azathoth.lan> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports Mailing List Subject: Re: Retiring of databases/py-pysqlite2x X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 04:14:59 -0000 Baptiste Daroussin wrote on 30.08.2011 01:48: >> They may be safely removed after all of this guys will be committed: >> audio/pytone ports/160053 commited >> databases/py-axiom ports/160260 wen@ >> databases/py-sqlobject ports/160059 wen@ >> deskutils/gourmet ports/160165 beech@ >> deskutils/griffith ports/160161 unassigned >> devel/bzr-git ports/160069 glarkin@ >> games/anki ports/160055 eadler@ >> games/gcompris ports/160054 gnome@ >> multimedia/gpodder ports/160155 commited >> multimedia/miro ports/160070 unassigned approved >> security/umit ports/160072 unassigned >> security/zenmap ports/160071 unassigned >> sysutils/flyback ports/160157 commited >> textproc/translate-toolkit ports/160261 jpaetzel@ >> www/roundup ports/160220 sbz@ >> deskutils/conduit ports/160063 gnome@ >> multimedia/pyjama ports/160065 eadler@ >> multimedia/py-openlp ports/160285 tabthorpe@ >> security/hotssh ports/160066 unassigned should be ashish@ >> security/pwman3 ports/160288 unassigned >> > Thank you very much for that work, I should have time soon to work on this if > noone already did it. > > regards, > Bapt eadler@ taken two of them, so i've updated the aforementioned list. Thank you. -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 05:48:33 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id BBB861065674; Tue, 30 Aug 2011 05:48:33 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id B0E6B152931; Tue, 30 Aug 2011 05:48:32 +0000 (UTC) Message-ID: <4E5C79AF.6000408@FreeBSD.org> Date: Mon, 29 Aug 2011 22:48:31 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0 MIME-Version: 1.0 To: "freebsd-ports@FreeBSD.org" , secteam@FreeBSD.org X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Why do we not mark vulnerable ports DEPRECATED? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 05:48:33 -0000 I'm doing some updates and came across mail/postfix-policyd-spf which relies on mail/libspf2-10. The latter had a vuxml entry added on 2008-10-27. So my question is, why has mail/libspf2-10 been allowed to remain in the tree vulnerable for almost 3 years? Wouldn't it make more sense to mark vulnerable ports DEPRECATED immediately with a short expiration? When they get fixed they get un-deprecated. If they don't, they get removed. Can someone explain why this would be a bad idea? Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 06:25:42 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDFC0106566B; Tue, 30 Aug 2011 06:25:42 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id BC6778FC0A; Tue, 30 Aug 2011 06:25:41 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 499155615E; Tue, 30 Aug 2011 01:25:41 -0500 (CDT) Date: Tue, 30 Aug 2011 01:25:41 -0500 From: Mark Linimon To: Doug Barton Message-ID: <20110830062541.GA5538@lonesome.com> References: <4E5C79AF.6000408@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E5C79AF.6000408@FreeBSD.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: secteam@FreeBSD.org, "freebsd-ports@FreeBSD.org" Subject: Re: Why do we not mark vulnerable ports DEPRECATED? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 06:25:42 -0000 On Mon, Aug 29, 2011 at 10:48:31PM -0700, Doug Barton wrote: > Can someone explain why this would be a bad idea? Very early in my committer career, I marked a port BROKEN that kde depended on. I was quickly chastisted by people trying to install kde :-) So, the right answer may be "it depends". For unmaintained leaf or leaf-ish ports like you're talking about, I think the answer is exactly correct -- such ports do nothing but cause users problems. But I think it would be counterproductive to mark e.g. php5 and firefox as such whenever a new vulnerability is found. It's just simply too common* an occurrence. A different but related topic: I don't think we've been sufficiently rigorous about marking DEPRECATED or BROKEN ports with EXPIRATION_DATEs. That could be a Junior Committer Task. (I know that Pav has swept some out in the past.) mcl * never mind that some secteam members will grumble that they should be marked as permanentlky insecure anyways From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 06:28:20 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6E70106566C; Tue, 30 Aug 2011 06:28:20 +0000 (UTC) (envelope-from ade@FreeBSD.org) Received: from panix.lovett.com (panix.lovett.com [166.84.7.128]) by mx1.freebsd.org (Postfix) with ESMTP id A04F08FC1D; Tue, 30 Aug 2011 06:28:20 +0000 (UTC) Received: from r74-192-180-219.htvlcmta01.hnvitx.tl.dh.suddenlink.net ([74.192.180.219] helo=lab.lovett.com) by panix.lovett.com with esmtpa (Exim 4.76 (FreeBSD)) (envelope-from ) id 1QyHJk-000GN4-FI; Tue, 30 Aug 2011 05:57:00 +0000 Date: Tue, 30 Aug 2011 00:56:48 -0500 From: Ade Lovett To: Doug Barton Message-ID: <20110830005648.4fdcf144@lab.lovett.com> In-Reply-To: <4E5C79AF.6000408@FreeBSD.org> References: <4E5C79AF.6000408@FreeBSD.org> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: secteam@FreeBSD.org, "freebsd-ports@FreeBSD.org" Subject: Re: Why do we not mark vulnerable ports DEPRECATED? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 06:28:20 -0000 On Mon, 29 Aug 2011 22:48:31 -0700 Doug Barton wrote: > I'm doing some updates and came across mail/postfix-policyd-spf which > relies on mail/libspf2-10. The latter had a vuxml entry added on > 2008-10-27. So my question is, why has mail/libspf2-10 been allowed to > remain in the tree vulnerable for almost 3 years? That's a little excessive, I agree. > Wouldn't it make more sense to mark vulnerable ports DEPRECATED > immediately with a short expiration? When they get fixed they get > un-deprecated. If they don't, they get removed. Can someone explain > why this would be a bad idea? Probably excessive on the other side, at least as far as the auto-deletion is concerned. We've had cases where libraries with a non-trivial number of upward dependencies have had issues - libpng springs to mind for some reason. Of course, things were fixed relatively promptly in that particular case so it's a little bit of a non-sequitor -- perhaps I'm focusing too much on "they get removed" being an automated process, which I think it would have need to be in order to be effective. -aDe > > > Doug > From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 08:17:16 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 63490106564A; Tue, 30 Aug 2011 08:17:16 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 5590915405A; Tue, 30 Aug 2011 08:17:15 +0000 (UTC) Message-ID: <4E5C9C8A.1010105@FreeBSD.org> Date: Tue, 30 Aug 2011 01:17:14 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0 MIME-Version: 1.0 To: Mark Linimon References: <4E5C79AF.6000408@FreeBSD.org> <20110830062541.GA5538@lonesome.com> In-Reply-To: <20110830062541.GA5538@lonesome.com> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: secteam@FreeBSD.org, "freebsd-ports@FreeBSD.org" Subject: Re: Why do we not mark vulnerable ports DEPRECATED? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 08:17:16 -0000 On 08/29/2011 23:25, Mark Linimon wrote: > So, the right answer may be "it depends". I think my point is, it shouldn't. If a port is important/popular than it will be quickly fixed. If not, it goes away. Everyone wins. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 08:37:50 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60F3C1065676; Tue, 30 Aug 2011 08:37:50 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) by mx1.freebsd.org (Postfix) with ESMTP id 443B28FC17; Tue, 30 Aug 2011 08:37:50 +0000 (UTC) Received: from delta.delphij.net (c-76-102-50-245.hsd1.ca.comcast.net [76.102.50.245]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id C0807F371; Tue, 30 Aug 2011 01:37:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1314693470; bh=k2qAPIxoRLSuikIO2c5J/NJNgW1PkGGIgvzqhm6UyjA=; h=Message-ID:Date:From:Reply-To:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=hXVE8LFnjiWNvPawMqZIrA2iOTIq/oMXCpLBh0ZDDdd3LFvYQ3qjFuvtnWsdL8WuZ A/soKi+D8jCAVe8zyGRQLwXr6M8IpgGBeivkxFtqy3tC2vHPj7qkyGVNMCq9JEyl2r WMlMnJ4MExvKNnS/eTRmUacYnazdzHm03Ann272Y= Message-ID: <4E5CA159.4010404@delphij.net> Date: Tue, 30 Aug 2011 01:37:45 -0700 From: Xin LI Organization: The FreeBSD Project MIME-Version: 1.0 To: Doug Barton References: <4E5C79AF.6000408@FreeBSD.org> <20110830062541.GA5538@lonesome.com> <4E5C9C8A.1010105@FreeBSD.org> In-Reply-To: <4E5C9C8A.1010105@FreeBSD.org> OpenPGP: id=3FCA37C1; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Mark Linimon , "freebsd-ports@FreeBSD.org" , secteam@FreeBSD.org Subject: Re: Why do we not mark vulnerable ports DEPRECATED? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 08:37:50 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 08/30/11 01:17, Doug Barton wrote: > On 08/29/2011 23:25, Mark Linimon wrote: >> So, the right answer may be "it depends". > > I think my point is, it shouldn't. If a port is important/popular > than it will be quickly fixed. If not, it goes away. Everyone > wins. Personally I do support this idea. By the way vuxml is essentially a BROKEN if portaudit is installed. Perhaps we should have that in base system or the build cluster? Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAEBCAAGBQJOXKFYAAoJEATO+BI/yjfBwkYH/2hDRqHEHztCDybJ4pE6u682 tURpASOWJgxkFn0xT1GF0VL9iwULWbboPdKVhWWPKAZiOWezJbepPeQv4Lcvbqqs GB28I6DPyRIDES1eqAVJ9RbjP8LgUCTMBu2LU8YCkB1Zrbg9fXD5I0amEXaDTVoc vBPM2uiWjx49/vgBRjSYKo2KG4MxOAt0PS+SlxXD5eeNodJmMLq8ipL6nA0ptA03 /l8ymf5wbNIWTmBm98CY1bIzxtVb1zcvkHPZRe4fPPXCFElrh6qCou09XJxoWg3P sTaf6kIpCxTcPsKCdAipo5OvcnXh66Kn4hlKpvc3mKwYr5jMN69d9KqSaLw0HM4= =02aU -----END PGP SIGNATURE----- From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 09:14:27 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83FAF1065676 for ; Tue, 30 Aug 2011 09:14:27 +0000 (UTC) (envelope-from talon@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 1B8DD8FC1B for ; Tue, 30 Aug 2011 09:14:26 +0000 (UTC) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.14.4/jtpda-5.4) with ESMTP id p7U9DPk9062173 for ; Tue, 30 Aug 2011 11:13:38 +0200 (CEST) X-Ids: 168 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 26F1A21C64 for ; Tue, 30 Aug 2011 11:13:59 +0200 (CEST) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id 1747D4FFD; Tue, 30 Aug 2011 11:13:59 +0200 (CEST) Date: Tue, 30 Aug 2011 11:13:58 +0200 From: Michel Talon To: freebsd-ports@FreeBSD.org Message-ID: <20110830091358.GA83706@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Miltered: at jchkmail.jussieu.fr with ID 4E5CA9D8.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4E5CA9D8.001/134.157.10.1/parthe.lpthe.jussieu.fr/parthe.lpthe.jussieu.fr/ Cc: Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 09:14:27 -0000 Chad Perrin wrote: >Of course, your goal is apparently to >convince me that yours are the "correct" priorities. Indeed i think having the correct priorities is essential when choosing between different options, and i am sincerely convinced that my choices are shared by a lot more people than yours. For example, having "less bloat" in the system doesn't even appear in the radar of most people. I value much more that hardware is supported, that installation and upgrade are easy, troubleless. Like everyone else i am irritated by some developments in the Ubuntu experience, for example the parallel booting stuff, which doesn't work well (but that people would like to imitate in FreeBSD), but all those problems remain minor. A few days ago i went to a store to buy a new laptop, i went with two CDROMs, an Ubuntu one and a FreeBSD one. Guess which of the two supported the network controllers in the laptops i tried? -- Michel TALON From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 09:35:59 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D9B91065676 for ; Tue, 30 Aug 2011 09:35:59 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.31.28]) by mx1.freebsd.org (Postfix) with ESMTP id E14F98FC12 for ; Tue, 30 Aug 2011 09:35:58 +0000 (UTC) Received: from [78.34.129.95] (helo=fabiankeil.de) by smtprelay01.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1QyKZt-0004OL-Lj for freebsd-ports@freebsd.org; Tue, 30 Aug 2011 11:25:53 +0200 Date: Tue, 30 Aug 2011 11:25:48 +0200 From: Fabian Keil To: freebsd-ports@freebsd.org Message-ID: <20110830112548.073ce249@fabiankeil.de> In-Reply-To: <4E5C79AF.6000408@FreeBSD.org> References: <4E5C79AF.6000408@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/CQSSQ+Wl_7FiXH9rtAf/4re"; protocol="application/pgp-signature" X-Df-Sender: 775067 Subject: Re: Why do we not mark vulnerable ports DEPRECATED? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 09:35:59 -0000 --Sig_/CQSSQ+Wl_7FiXH9rtAf/4re Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Doug Barton wrote: > I'm doing some updates and came across mail/postfix-policyd-spf which > relies on mail/libspf2-10. The latter had a vuxml entry added on > 2008-10-27. So my question is, why has mail/libspf2-10 been allowed to > remain in the tree vulnerable for almost 3 years? >=20 > Wouldn't it make more sense to mark vulnerable ports DEPRECATED > immediately with a short expiration? When they get fixed they get > un-deprecated. If they don't, they get removed. Can someone explain why > this would be a bad idea? Many vulnerabilities are only an issue for certain program configurations, for example most Firefox vulnerabilities seem to require JavaScript being enabled for a site or connection controlled by the attacker. I haven't checked what the problems with mail/libspf2-10 are (or were), but I don't think all vulnerabilities should be treated the same. In my opinion having a vuxml entry is sufficient, the rest is up to the user. I agree with Xin Li's suggestion that it may make sense to import portaudit to make sure the user is actually aware of the entry, though. Fabian --Sig_/CQSSQ+Wl_7FiXH9rtAf/4re Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk5crKMACgkQBYqIVf93VJ0MxwCfVGPLvX6UlrIV0IGbLDw4goiA OHIAoJIV3+8fr7M38a8qwN7yHOxl4+Do =hvDs -----END PGP SIGNATURE----- --Sig_/CQSSQ+Wl_7FiXH9rtAf/4re-- From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 09:48:58 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1818B106566B for ; Tue, 30 Aug 2011 09:48:58 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id D93B18FC1C for ; Tue, 30 Aug 2011 09:48:57 +0000 (UTC) Received: by iadx2 with SMTP id x2so1899159iad.13 for ; Tue, 30 Aug 2011 02:48:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7be0vVGpKoO2ltNalNHZhj0ZHucsL6oR9B+RmDCUQpg=; b=wbJOv99b5TJ3T/D7SISe8CsKjgxSkgEbe59HJBtPzBPuQ9cDF8ibljj5NXPQGjgc89 J74MKtmLs8dC7bRzCx9NlK35PeibENnjfTItmS1beX5teS6VAXj9tYN8Zj7guOAoch1e GwSp5t+GYYBccg5SRlhSZp0fDeG8IiSgdIIUs= MIME-Version: 1.0 Received: by 10.231.45.204 with SMTP id g12mr12842029ibf.79.1314697737247; Tue, 30 Aug 2011 02:48:57 -0700 (PDT) Received: by 10.231.61.148 with HTTP; Tue, 30 Aug 2011 02:48:57 -0700 (PDT) Received: by 10.231.61.148 with HTTP; Tue, 30 Aug 2011 02:48:57 -0700 (PDT) In-Reply-To: <20110830091358.GA83706@lpthe.jussieu.fr> References: <20110830091358.GA83706@lpthe.jussieu.fr> Date: Tue, 30 Aug 2011 10:48:57 +0100 Message-ID: From: Chris Rees To: Michel Talon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-ports@freebsd.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 09:48:58 -0000 On 30 Aug 2011 10:15, "Michel Talon" wrote: > > Chad Perrin wrote: > > >Of course, your goal is apparently to > >convince me that yours are the "correct" priorities. > > Indeed i think having the correct priorities is essential when choosing > between different options, and i am sincerely convinced that my choices > are shared by a lot more people than yours. For example, having "less > bloat" in the system doesn't even appear in the radar of most people. > I value much more that hardware is supported, that installation and > upgrade are easy, troubleless. Like everyone else i am irritated by > some developments in the Ubuntu experience, for example the parallel > booting stuff, which doesn't work well (but that people would like to > imitate in FreeBSD), but all those problems remain minor. A few days ago > i went to a store to buy a new laptop, i went with two CDROMs, an Ubuntu > one and a FreeBSD one. Guess which of the two supported the network > controllers in the laptops i tried? > Did you deliberately pick the laptops with strange network controllers, or just use an old version of FreeBSD? Which version did you use? Chris From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 09:52:53 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A582A1065672 for ; Tue, 30 Aug 2011 09:52:53 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail13.syd.optusnet.com.au (mail13.syd.optusnet.com.au [211.29.132.194]) by mx1.freebsd.org (Postfix) with ESMTP id 36EF68FC1B for ; Tue, 30 Aug 2011 09:52:52 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c220-239-116-103.belrs4.nsw.optusnet.com.au [220.239.116.103]) by mail13.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p7U9qoHc014447 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Aug 2011 19:52:51 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.4/8.14.4) with ESMTP id p7U9qnv4064412; Tue, 30 Aug 2011 19:52:49 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.4/8.14.4/Submit) id p7U9qmMu064411; Tue, 30 Aug 2011 19:52:48 +1000 (EST) (envelope-from peter) Date: Tue, 30 Aug 2011 19:52:48 +1000 From: Peter Jeremy To: Ruslan Mahmatkhanov Message-ID: <20110830095247.GA64372@server.vk2pj.dyndns.org> References: <20110826050535.GB64576@server.vk2pj.dyndns.org> <20110829032905.GA84993@server.vk2pj.dyndns.org> <4E5B5FBE.8040905@yandex.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: <4E5B5FBE.8040905@yandex.ru> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-ports@freebsd.org Subject: Re: Problems building devel/gobject-introspection X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 09:52:53 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2011-Aug-29 13:45:34 +0400, Ruslan Mahmatkhanov wrot= e: >Peter Jeremy wrote on 29.08.2011 07:29: >> Turns out that my python was dodgy. =2E.. >And did you realize what python option had triggered that? I'm curious=20 >since i'm wasn't able to reproduce it here. For me it looks like=20 >upstream bug dealing with unicode() vs str() output, since errors like=20 >that you provide in original message may be fixed by `setenv LANG C` in=20 >most of cases. I've done some experiments but have not been able to reproduce the problem - which is annoying. I agree it looks locale-related but I don't have any locale-related variables set. --=20 Peter Jeremy --envbJBWh7q8WU6mo Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk5csu8ACgkQ/opHv/APuIfg/ACePipjbkxpYZnPfYdtHyAL0VWa LiEAoMN3qiMN2jcqCmA6UStkRf298/NN =exf1 -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo-- From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 10:03:42 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 491DC1065670; Tue, 30 Aug 2011 10:03:42 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 2988D23CF4F; Mon, 29 Aug 2011 11:40:25 +0200 (CEST) Message-ID: <4E5B5E89.3000700@FreeBSD.org> Date: Mon, 29 Aug 2011 11:40:25 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4E5A48AC.6050201@eskk.nu> <4E5A7DAE.8090904@FreeBSD.org> <20110828174640.GC277@magic.hamla.org> <4E5AA844.5030501@FreeBSD.org> In-Reply-To: <4E5AA844.5030501@FreeBSD.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: dinoex@freebsd.org Subject: Re: OPTIONS framework bug vs. SSL issues X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 10:03:42 -0000 Am 28.08.2011 22:42, schrieb Doug Barton: > On 8/28/2011 10:46 AM, Sahil Tandon wrote: >> On Sun, 2011-08-28 at 19:41:02 +0200, Matthias Andree wrote: >> >>> just a brain flash: bsd.port.mk currently re-prompts OPTIONS if >>> they've changed, for instance, through addition. >>> >>> Should we change this feature in b.p.mk so that it also re-prompt the >>> user when the defaults have changed? > > The way that (for example) portmaster works now is that if the user has > already answered the questions for that port they don't get the dialog > again unless a knob has been added or deleted. Personally I would find > it surprising to be presented with the dialog again if there were no > changes to the set of options. I wouldn't see a change in defaults in > this case since my answers are already going to be filled in. > > For this specific case I probably would have changed the language of the > gnutls option to make it clear that it needs to be un-selected, and > added a no-op OPTION to make sure that users saw the dialog. Euhm, while workable I don't like that approach. And I conclude that the way the OPTIONS system currently works has a serious shortcoming, in that it does not report changed defaults to the user. Basically in this situation ("default changed") we'd need to: 1. present the options form again 2. mention to the user that the default has changed 3. let him choose. What might help in the longer term is having sort of tree/four-state options, with "user-set to off" "user-set to on", "user does not care" and/or "user said go with whatever the default is". Arguably we might have wanted to kill the OPTIONS on cups* altogether, and waive the BROKEN tag this time Dirk, do we have any hints that the CUPS-refuses-GNUTLS will be resolved in the foreseeable future? If not, can we just bite the bullet and remove the OPTIONS and force OpenSSL builds even though it might cause license concerns deeper down the dependency tree? From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 10:05:12 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E5371065672 for ; Tue, 30 Aug 2011 10:05:12 +0000 (UTC) (envelope-from kaspars@bankovskis.lv) Received: from mail.kei.lv (mail.kei.lv [85.31.99.210]) by mx1.freebsd.org (Postfix) with ESMTP id BDE798FC16 for ; Tue, 30 Aug 2011 10:05:11 +0000 (UTC) Received: from numeri.kei.local (lvfw.delfi.lv [62.85.29.84]) (authenticated bits=0) by mail.kei.lv (8.14.5/8.14.4) with ESMTP id p7U9rNIc042487 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 30 Aug 2011 12:53:29 +0300 (EEST) (envelope-from kaspars@bankovskis.lv) Date: Tue, 30 Aug 2011 12:53:23 +0300 From: Kaspars Bankovskis To: freebsd-ports@FreeBSD.org Message-ID: <20110830095323.GA2595@numeri.kei.local> References: <20110830091358.GA83706@lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110830091358.GA83706@lpthe.jussieu.fr> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=0.9 required=3.0 tests=SPF_FAIL autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.kei.lv Cc: Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 10:05:12 -0000 On Tue, Aug 30, 2011 at 11:13:58AM +0200, Michel Talon wrote: > i went to a store to buy a new laptop, i went with two CDROMs, an Ubuntu > one and a FreeBSD one. Guess which of the two supported the network > controllers in the laptops i tried? And guess which of them ran binary blobs. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 10:26:37 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 992C31065674 for ; Tue, 30 Aug 2011 10:26:37 +0000 (UTC) (envelope-from freebsd-ports@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 565578FC15 for ; Tue, 30 Aug 2011 10:26:37 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QyLWe-00084y-6K for freebsd-ports@freebsd.org; Tue, 30 Aug 2011 12:26:36 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 30 Aug 2011 12:26:36 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 30 Aug 2011 12:26:36 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-ports@freebsd.org From: Ivan Voras Date: Tue, 30 Aug 2011 12:26:25 +0200 Lines: 8 Message-ID: References: <1c58e33bebcbbd9d7c06a5c635259ba7@etoilebsd.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101102 Thunderbird/3.1.6 In-Reply-To: <1c58e33bebcbbd9d7c06a5c635259ba7@etoilebsd.net> X-Enigmail-Version: 1.1.2 Subject: Re: Libreoffice plan X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 10:26:37 -0000 On 24/08/2011 12:13, Baptiste Daroussin wrote: > libreoffice as openoffice are difficult ports to maintain, to not > hesitate to join the office@ team to help, test, discuss about the > office related task. Not volunteering but just wanted to thank you - I really couldn't use FreeBSD on any desktop without OOo/LO! From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 10:38:56 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EA75106566B for ; Tue, 30 Aug 2011 10:38:56 +0000 (UTC) (envelope-from fwall@inotronic.de) Received: from mail.inotronic.de (mail.inotronic.de [77.73.248.111]) by mx1.freebsd.org (Postfix) with ESMTP id F36458FC12 for ; Tue, 30 Aug 2011 10:38:55 +0000 (UTC) Received: from phosphorus (mail [77.73.248.111]) by mail.inotronic.de (8.14.5/8.14.3) with ESMTP id p7UASiVQ047671 for ; Tue, 30 Aug 2011 12:28:44 +0200 (CEST) (envelope-from fwall@inotronic.de) X-Filter-Status: scanned by inotronic CheckMAIL Received: from boron.inotronic.de (boron.inotronic-intern.de [10.1.2.10]) by mail.inotronic.de (8.14.5/8.14.3) with ESMTP id p7UASUUb047650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 30 Aug 2011 12:28:30 +0200 (CEST) (envelope-from fwall@inotronic.de) X-Receipient-To: Received: from pcfw2 (pcfw2.inotronic-intern.de [10.1.2.235]) by boron.inotronic.de (8.14.4/8.14.4) with ESMTP id p7UASTXc025820; Tue, 30 Aug 2011 12:28:30 +0200 (CEST) (envelope-from fwall@inotronic.de) Date: Tue, 30 Aug 2011 12:28:29 +0200 From: Frank Wall To: freebsd-ports@freebsd.org Message-ID: <20110830102829.GN2084@pcfw2> References: <4E5A48AC.6050201@eskk.nu> <4E5A7DAE.8090904@FreeBSD.org> <20110828174640.GC277@magic.hamla.org> <4E5AA844.5030501@FreeBSD.org> <4E5B5E89.3000700@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E5B5E89.3000700@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: OPTIONS framework bug vs. SSL issues X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 10:38:56 -0000 On Mon, Aug 29, 2011 at 11:40:25AM +0200, Matthias Andree wrote: > Euhm, while workable I don't like that approach. And I conclude that > the way the OPTIONS system currently works has a serious shortcoming, in > that it does not report changed defaults to the user. > > Basically in this situation ("default changed") we'd need to: > > 1. present the options form again > 2. mention to the user that the default has changed > 3. let him choose. I don't think that this is the right way to go. You are forcing the user to rethink his past decision(s). Why would I want to do this? The user decided to go a specific path by initially choosing a specific set of OPTIONs. We *must* assume that the user had good reasons to do so. We should *not* assume the user has no idea what he's doing and needs to be guided. The latter would make make the update process just more complicated. To me the Ports System is mainly for expert users. Most of them will track changes and test (port/software) updates before installing this update on important systems. Bye - Frank From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 11:06:53 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id AFC61106566C; Tue, 30 Aug 2011 11:06:53 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id B735623CF4F; Tue, 30 Aug 2011 13:06:52 +0200 (CEST) Message-ID: <4E5CC44C.3070604@FreeBSD.org> Date: Tue, 30 Aug 2011 13:06:52 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: Sunpoet Po-Chuan Hsieh References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> In-Reply-To: <201108300823.p7U8NIfD038098@repoman.freebsd.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 11:06:54 -0000 Am 30.08.2011 10:23, schrieb Sunpoet Po-Chuan Hsieh: > sunpoet 2011-08-30 08:23:18 UTC > > FreeBSD ports repository > > Modified files: > mail/procmail Makefile > Log: > - Take maintainership > > Revision Changes Path > 1.60 +1 -1 ports/mail/procmail/Makefile I was just about to grab the port, deprecate and set two months expiration date. Now that you're maintaining it I seek you to please let this unmaintained unclean code from our FreeBSD ports world and deprecate it. The code is unmaintainable, hasn't seen maintenance in a decade, is hard to use properly because of its fall-through "error handling" (actually nonhandling) behaviour, and should finally disappear. Please add DEPRECATED= use mail/maildrop instead EXPIRATION_DATE= 2011-10-31 maildrop (courier's filtering agent) has been around for nearly as long and works well. Thank you. Best, Matthias From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 11:09:49 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6A8A1065672 for ; Tue, 30 Aug 2011 11:09:49 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id 461918FC0A for ; Tue, 30 Aug 2011 11:09:48 +0000 (UTC) Received: (qmail invoked by alias); 30 Aug 2011 11:09:47 -0000 Received: from g227000177.adsl.alicedsl.de (EHLO apollo.emma.line.org) [92.227.0.177] by mail.gmx.net (mp066) with SMTP; 30 Aug 2011 13:09:47 +0200 X-Authenticated: #428038 X-Provags-ID: V01U2FsdGVkX1/S9WxqVsHS3et9FLbeF+YY8sB8WC4YmtEjg1wp/O vCvgoALwmLDMcP Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 3075123CF4F for ; Tue, 30 Aug 2011 13:09:46 +0200 (CEST) Message-ID: <4E5CC4FA.8000302@gmx.de> Date: Tue, 30 Aug 2011 13:09:46 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4E5A48AC.6050201@eskk.nu> <4E5A7DAE.8090904@FreeBSD.org> <20110828174640.GC277@magic.hamla.org> <4E5AA844.5030501@FreeBSD.org> <4E5B5E89.3000700@FreeBSD.org> <20110830102829.GN2084@pcfw2> In-Reply-To: <20110830102829.GN2084@pcfw2> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: OPTIONS framework bug vs. SSL issues X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 11:09:49 -0000 Am 30.08.2011 12:28, schrieb Frank Wall: > On Mon, Aug 29, 2011 at 11:40:25AM +0200, Matthias Andree wrote: >> Euhm, while workable I don't like that approach. And I conclude that >> the way the OPTIONS system currently works has a serious shortcoming, in >> that it does not report changed defaults to the user. >> >> Basically in this situation ("default changed") we'd need to: >> >> 1. present the options form again >> 2. mention to the user that the default has changed >> 3. let him choose. > > I don't think that this is the right way to go. You are forcing > the user to rethink his past decision(s). Why would I want to do this? Because you must, the former default configuration, even if you've acknowledged it as an informed decision you've made, no longer works. > The user decided to go a specific path by initially choosing a > specific set of OPTIONs. We *must* assume that the user had good > reasons to do so. We should *not* assume the user has no idea what > he's doing and needs to be guided. The latter would make make the > update process just more complicated. The point is, most users just agree to the defaults, and in that situation, there is reason to re-prompt. One might argue that we don't need to reprompt if the new default matches the old configuration, but the OPTIONS framework currently doesn't know "user set this deliberately" or "user just stuck to the defaults". From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 11:11:48 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECD901065670; Tue, 30 Aug 2011 11:11:48 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id B04368FC19; Tue, 30 Aug 2011 11:11:48 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QyMES-000J4M-HX; Tue, 30 Aug 2011 13:11:52 +0200 Date: Tue, 30 Aug 2011 13:11:52 +0200 From: Kurt Jaeger To: Matthias Andree Message-ID: <20110830111152.GF28186@home.opsec.eu> References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E5CC44C.3070604@FreeBSD.org> Cc: Sunpoet Po-Chuan Hsieh , ports@freebsd.org Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 11:11:49 -0000 Hi! > > Modified files: > > mail/procmail Makefile [...] > Now that you're maintaining it I seek you to please let this > unmaintained unclean code from our FreeBSD ports world and deprecate it. [...] > maildrop (courier's filtering agent) has been around for nearly as long > and works well. - Can maildrop be used with other MTAs like exim ? - Can it use the 700+ lines long .procmailrc I have running in a criticial application or do I have to migrate that ? Thanks! -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 11:12:38 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76A1C1065674; Tue, 30 Aug 2011 11:12:38 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward11.mail.yandex.net (forward11.mail.yandex.net [IPv6:2a02:6b8:0:801::1]) by mx1.freebsd.org (Postfix) with ESMTP id EDB368FC18; Tue, 30 Aug 2011 11:12:37 +0000 (UTC) Received: from smtp13.mail.yandex.net (smtp13.mail.yandex.net [95.108.130.68]) by forward11.mail.yandex.net (Yandex) with ESMTP id 5E26EE8299A; Tue, 30 Aug 2011 15:12:36 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314702756; bh=TvZOxYpJ8Mi10gOEgjR6c6AcG8w0zeMPntNmDK0GPPI=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=deiUZurmXHqei04k3Ue1rVBUVp9gu8GwRV5tS5QD5cTglbBGtj2Kf86312nz6TaPl ADDVnVv9RBhMp+cTUSsV/mIhjdEZc4UgWXf1dnx3g13w5hVFihAaIFGrgOuHnZmb0P J/UkCHo4nUbRxlloTW0tgUHtbwBk7Rlvi3PbSpZ4= Received: from smtp13.mail.yandex.net (localhost [127.0.0.1]) by smtp13.mail.yandex.net (Yandex) with ESMTP id 3C32AE402B6; Tue, 30 Aug 2011 15:12:36 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp13.mail.yandex.net (nwsmtp/Yandex) with ESMTP id CZm4XZHF; Tue, 30 Aug 2011 15:12:35 +0400 X-Yandex-Spam: 1 Message-ID: <4E5CC5A1.6080602@yandex.ru> Date: Tue, 30 Aug 2011 15:12:33 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: Matthias Andree References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> In-Reply-To: <4E5CC44C.3070604@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Sunpoet Po-Chuan Hsieh , ports@freebsd.org Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 11:12:38 -0000 Matthias Andree wrote on 30.08.2011 15:06: > Am 30.08.2011 10:23, schrieb Sunpoet Po-Chuan Hsieh: >> sunpoet 2011-08-30 08:23:18 UTC >> >> FreeBSD ports repository >> >> Modified files: >> mail/procmail Makefile >> Log: >> - Take maintainership >> >> Revision Changes Path >> 1.60 +1 -1 ports/mail/procmail/Makefile > > I was just about to grab the port, deprecate and set two months > expiration date. > > Now that you're maintaining it I seek you to please let this > unmaintained unclean code from our FreeBSD ports world and deprecate it. > > The code is unmaintainable, hasn't seen maintenance in a decade, > is hard to use properly because of its fall-through "error handling" > (actually nonhandling) behaviour, and should finally disappear. > > Please add > > DEPRECATED= use mail/maildrop instead > EXPIRATION_DATE= 2011-10-31 or mail/getmail > > > maildrop (courier's filtering agent) has been around for nearly as long > and works well. > > Thank you. > > Best, > Matthias -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 12:08:29 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 689DE1065672; Tue, 30 Aug 2011 12:08:29 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 3B96D23CF2B; Tue, 30 Aug 2011 14:07:38 +0200 (CEST) Message-ID: <4E5CD28A.1080809@FreeBSD.org> Date: Tue, 30 Aug 2011 14:07:38 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: Kurt Jaeger References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> <20110830111152.GF28186@home.opsec.eu> In-Reply-To: <20110830111152.GF28186@home.opsec.eu> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Sunpoet Po-Chuan Hsieh , ports@FreeBSD.org Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 12:08:29 -0000 Am 30.08.2011 13:11, schrieb Kurt Jaeger: > Hi! > >>> Modified files: >>> mail/procmail Makefile > [...] >> Now that you're maintaining it I seek you to please let this >> unmaintained unclean code from our FreeBSD ports world and deprecate it. > [...] >> maildrop (courier's filtering agent) has been around for nearly as long >> and works well. > > - Can maildrop be used with other MTAs like exim ? Yes. > - Can it use the 700+ lines long .procmailrc I have running > in a criticial application or do I have to migrate that ? You'd have to migrate that. On the other hand, a 700+ line long .procmailrc "in a critical application" is usually a mistake in itself already and always was, unless you're one of the few who has a recipe like :0e { EXITCODE=75 HOST } after each and every single recipe that can fail in some way (most importantly, delivering recipes). Few people know it's necessary, as it's not explicitly documented, but just working around documented fall-through behaviour -- and as a side effect it voids the "else"-style recipes. Beyond that, there are pending bug fixes that never made it into a release, check the 3.23pre announcement at Bottom line: the sooner we get rid from procmail the better. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 12:14:27 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDF971065675 for ; Tue, 30 Aug 2011 12:14:27 +0000 (UTC) (envelope-from fwall@inotronic.de) Received: from mail.inotronic.de (mail.inotronic.de [77.73.248.111]) by mx1.freebsd.org (Postfix) with ESMTP id 513148FC08 for ; Tue, 30 Aug 2011 12:14:27 +0000 (UTC) Received: from phosphorus (mail [77.73.248.111]) by mail.inotronic.de (8.14.5/8.14.3) with ESMTP id p7UC4EDB054670; Tue, 30 Aug 2011 14:04:14 +0200 (CEST) (envelope-from fwall@inotronic.de) X-Filter-Status: scanned by inotronic CheckMAIL Received: from boron.inotronic.de (boron.inotronic-intern.de [10.1.2.10]) by mail.inotronic.de (8.14.5/8.14.3) with ESMTP id p7UC3r5N054621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Aug 2011 14:03:53 +0200 (CEST) (envelope-from fwall@inotronic.de) X-Receipient-To: Received: from pcfw2 (pcfw2.inotronic-intern.de [10.1.2.235]) by boron.inotronic.de (8.14.4/8.14.4) with ESMTP id p7UC3qAX029204; Tue, 30 Aug 2011 14:03:52 +0200 (CEST) (envelope-from fwall@inotronic.de) Date: Tue, 30 Aug 2011 14:03:52 +0200 From: Frank Wall To: Kurt Jaeger Message-ID: <20110830120352.GO2084@pcfw2> References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> <20110830111152.GF28186@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110830111152.GF28186@home.opsec.eu> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@freebsd.org Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 12:14:27 -0000 On Tue, Aug 30, 2011 at 01:11:52PM +0200, Kurt Jaeger wrote: > - Can it use the 700+ lines long .procmailrc I have running > in a criticial application or do I have to migrate that ? I would suggest to migrate to something new. While searching for a procmail replacement myself, I've even found a script to migrate procmail rules to SIEVE instructions: http://www.dovecot.org/tools/procmail2sieve.pl Bye - Frank From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 12:27:22 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79261106564A for ; Tue, 30 Aug 2011 12:27:22 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 3A7C88FC0C for ; Tue, 30 Aug 2011 12:27:22 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QyNPa-000KF3-PF for ports@FreeBSD.org; Tue, 30 Aug 2011 14:27:26 +0200 Date: Tue, 30 Aug 2011 14:27:26 +0200 From: Kurt Jaeger To: ports@FreeBSD.org Message-ID: <20110830122726.GG28186@home.opsec.eu> References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> <20110830111152.GF28186@home.opsec.eu> <4E5CD28A.1080809@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E5CD28A.1080809@FreeBSD.org> Cc: Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 12:27:22 -0000 [maildrop] > > - Can it use the 700+ lines long .procmailrc I have running > > in a criticial application or do I have to migrate that ? > > You'd have to migrate that. That's what I assumed. > Bottom line: the sooner we get rid from procmail the better. There are many other applications that have issues, as well. It's already a lot of work just to keep up with the bug-de-jour and the upgrade-de-jour and doing it all in parallel does not scale very well. Therefore, one has to choose what one can work on. If the fbsd ports drop procmail, it will just add more on my plate that I have to do myself. Similar to many other apps and ports and you-name-it. While I dislike bitrot like anyone else, I have an issue with the dropping of ports in general, because that will not scale. I'm aware, that the other approach (keeping everything) does not scale either. I've read the recent mail flood on ports etc. I maintain approx. 200 boxes, so I know the issues at hand, but right now, I can't offer solutions. It's just not looking good either way. -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 12:29:38 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8020E1065672 for ; Tue, 30 Aug 2011 12:29:38 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 31C6E8FC14 for ; Tue, 30 Aug 2011 12:29:37 +0000 (UTC) Received: from mr16.lnh.mail.rcn.net ([207.172.157.36]) by smtp02.lnh.mail.rcn.net with ESMTP; 30 Aug 2011 08:29:37 -0400 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr16.lnh.mail.rcn.net (MOS 4.2.3-GA) with ESMTP id BGR26441; Tue, 30 Aug 2011 08:29:36 -0400 Received-SPF: None identity=pra; client-ip=209.6.41.114; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="roberthuff@rcn.com"; x-conformance=sidf_compatible Received-SPF: None identity=mailfrom; client-ip=209.6.41.114; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="roberthuff@rcn.com"; x-conformance=sidf_compatible Received-SPF: None identity=helo; client-ip=209.6.41.114; receiver=smtp01.lnh.mail.rcn.net; envelope-from="roberthuff@rcn.com"; x-sender="postmaster@jerusalem.litteratus.org.litteratus.org"; x-conformance=sidf_compatible Received: from 209-6-41-114.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.41.114]) by smtp01.lnh.mail.rcn.net with ESMTP; 30 Aug 2011 08:29:37 -0400 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20060.55201.970048.970478@jerusalem.litteratus.org> Date: Tue, 30 Aug 2011 08:29:21 -0400 To: Matthias Andree In-Reply-To: <4E5CC4FA.8000302@gmx.de> References: <4E5A48AC.6050201@eskk.nu> <4E5A7DAE.8090904@FreeBSD.org> <20110828174640.GC277@magic.hamla.org> <4E5AA844.5030501@FreeBSD.org> <4E5B5E89.3000700@FreeBSD.org> <20110830102829.GN2084@pcfw2> <4E5CC4FA.8000302@gmx.de> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr16.lnh.mail.rcn.net) Cc: freebsd-ports@freebsd.org Subject: Re: OPTIONS framework bug vs. SSL issues X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 12:29:38 -0000 Matthias Andree writes: > > The user decided to go a specific path by initially choosing a > > specific set of OPTIONs. We *must* assume that the user had good > > reasons to do so. We should *not* assume the user has no idea what > > he's doing and needs to be guided. The latter would make make the > > update process just more complicated. > > The point is, most users just agree to the defaults, Which makes me one of "most users". I'll even confess to occasionally changing OPTIONS (during initial installation) more-or-less on a whim, usually but not always of the "of course this should have IPv6/threads/xml enabled" variety. (Which may remove me from "most". :-) > and in that > situation, there is reason to re-prompt. Agreed. An alternative - which might not be much less work - would be simple notification, e.g. "The default build options for port foo/bar have changed.". > One might argue that we don't need to reprompt if the new default > matches the old configuration, but the OPTIONS framework > currently doesn't know "user set this deliberately" or "user just > stuck to the defaults". Reprompting/notifying will be a pain. The alternative is users whose expected installation differs from reality. Robert Huff From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 13:05:33 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 726C01065743 for ; Tue, 30 Aug 2011 13:05:33 +0000 (UTC) (envelope-from glarkin@FreeBSD.org) Received: from mail1.sourcehosting.net (mail1.sourcehosting.net [74.205.51.45]) by mx1.freebsd.org (Postfix) with ESMTP id 481388FC08 for ; Tue, 30 Aug 2011 13:05:33 +0000 (UTC) Received: from 68-189-245-235.dhcp.oxfr.ma.charter.com ([68.189.245.235] helo=cube.entropy.prv) by mail1.sourcehosting.net with esmtp (Exim 4.73 (FreeBSD)) (envelope-from ) id 1QyNzn-00031k-7J; Tue, 30 Aug 2011 09:04:57 -0400 Received: from v104.entropy.prv (v104.entropy.prv [192.168.1.104]) by cube.entropy.prv (Postfix) with ESMTP id F2159521500B; Tue, 30 Aug 2011 09:05:25 -0400 (EDT) Message-ID: <4E5CE015.70803@FreeBSD.org> Date: Tue, 30 Aug 2011 09:05:25 -0400 From: Greg Larkin Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.20) Gecko/20110804 Lightning/1.0b2 Thunderbird/3.1.12 MIME-Version: 1.0 To: miwi@FreeBSD.org X-Enigmail-Version: 1.1.1 OpenPGP: id=1C940290 X-SA-Exim-Connect-IP: 68.189.245.235 X-SA-Exim-Mail-From: glarkin@FreeBSD.org X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail1.sourcehosting.net X-Spam-Level: *** X-Spam-Status: No, score=3.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RCVD_IN_RP_RNBL, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC, TVD_RCVD_IP autolearn=no version=3.3.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.sourcehosting.net) Cc: FreeBSD Ports Mailing List Subject: Python min version bumped from 2.4+ to 2.5+ X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: glarkin@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 13:05:33 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Martin, I have a question about a commit you made in February 2011: http://www.freshports.org/commit.php?message_id=201102250750.p1P7ofDg016541@repoman.freebsd.org&files=yes Part of the commit changed: USE_PYTHON= 2.4+ to USE_PYTHON= 2.5+ Was there a specific reason for doing so? I am running various tinderbox builds to check on port usage of the USE_PYTHON variable, and I noticed that devel/py-setuptools no longer builds if Python 2.4 is selected. I'd like to restore that capability, but before I send a PR, I wanted to check with you first. Thank you, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5c4BUACgkQ0sRouByUApDZKwCeMcUjlshPkFhNZrTQtQ1+Ywyu bNQAnjkkk0Sf1ntQXawhiMyhamPz0haz =aOJw -----END PGP SIGNATURE----- From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 13:38:08 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA6A8106564A; Tue, 30 Aug 2011 13:38:08 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward13.mail.yandex.net (forward13.mail.yandex.net [IPv6:2a02:6b8:0:801::3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DF038FC0C; Tue, 30 Aug 2011 13:38:08 +0000 (UTC) Received: from smtp11.mail.yandex.net (smtp11.mail.yandex.net [95.108.130.67]) by forward13.mail.yandex.net (Yandex) with ESMTP id E5E5D142A7B; Tue, 30 Aug 2011 17:38:06 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314711486; bh=H8TWzu6HzA7nezJHrcCS31IcQFGRq4KO2ntIMmduPHQ=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Dw6R0XIv0IPvF2/JANiZPMriO6cVLmMEaBECWln1+nbmXiClhDuWlzj41kU+mIZnV vQvJMoeRRgz+Da301rZFj2fu1NZPkg8ksBzusfl5tHvgTIamVW3sj9TeSLe8mcVlxg IF1sZtZIuzLtqj2WdoXh1lYVXMiWe3rmtTQ5h90s= Received: from smtp11.mail.yandex.net (localhost [127.0.0.1]) by smtp11.mail.yandex.net (Yandex) with ESMTP id C81EE7E0307; Tue, 30 Aug 2011 17:38:06 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp11.mail.yandex.net (nwsmtp/Yandex) with ESMTP id c6EWwbRv; Tue, 30 Aug 2011 17:38:06 +0400 X-Yandex-Spam: 1 Message-ID: <4E5CE7BB.8050808@yandex.ru> Date: Tue, 30 Aug 2011 17:38:03 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: glarkin@FreeBSD.org References: <4E5CE015.70803@FreeBSD.org> In-Reply-To: <4E5CE015.70803@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports Mailing List , miwi@FreeBSD.org Subject: Re: Python min version bumped from 2.4+ to 2.5+ X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 13:38:08 -0000 Greg Larkin wrote on 30.08.2011 17:05: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Martin, > > I have a question about a commit you made in February 2011: > http://www.freshports.org/commit.php?message_id=201102250750.p1P7ofDg016541@repoman.freebsd.org&files=yes > > Part of the commit changed: > > USE_PYTHON= 2.4+ > > to > > USE_PYTHON= 2.5+ > > Was there a specific reason for doing so? I am running various > tinderbox builds to check on port usage of the USE_PYTHON variable, and > I noticed that devel/py-setuptools no longer builds if Python 2.4 is > selected. > > I'd like to restore that capability, but before I send a PR, I wanted to > check with you first. > > Thank you, > Greg > - -- > Greg Larkin > > http://www.FreeBSD.org/ - The Power To Serve > http://www.sourcehosting.net/ - Ready. Set. Code. > http://twitter.com/cpucycle/ - Follow you, follow me I'm sorry for sail in, but i think that the reason is that python24 is reached it's EOL long time ago. Actually the only supported python releases atm according to python.org are - 2.7.2 and 3.2.1, and developers highly encourages the users to move to this versions. 2.5 and 2.6 are in security-fix-only mode, there will be no ANY releases for this branches after October 2011 and October 2013 respectively, while 2.4 does not get security-fixes even. There is also this answer from Martin in this pr: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/155526: python24 goes to the end of month, this port is on the todo for removal -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 13:39:52 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F295106564A for ; Tue, 30 Aug 2011 13:39:52 +0000 (UTC) (envelope-from m.tsatsenko@gmail.com) Received: from mx.tsatsenko.ru (y7nz.x.rootbsd.net [204.109.61.86]) by mx1.freebsd.org (Postfix) with ESMTP id 24ACB8FC12 for ; Tue, 30 Aug 2011 13:39:51 +0000 (UTC) Received: from [92.255.201.25] (helo=[192.168.0.5]) by mx.tsatsenko.ru with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1QyNzY-000MzV-IM for ports@FreeBSD.org; Tue, 30 Aug 2011 17:04:36 +0400 Message-ID: <4E5CDFDF.6070705@gmail.com> Date: Tue, 30 Aug 2011 17:04:31 +0400 From: Mikhail Tsatsenko User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110827 Thunderbird/6.0 MIME-Version: 1.0 To: ports@FreeBSD.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: mail/popper, mail/premail and mail/miltergreylist maintainership X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 13:39:52 -0000 Hi, I'd like to take maintainership of following unmaintained now ports: mail/popper mail/miltergreylist mail/milter-greylist-devel mail/premail -- Mikhail m.tsatsenko@gmail.com From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 13:56:54 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60BD71065670; Tue, 30 Aug 2011 13:56:54 +0000 (UTC) (envelope-from glarkin@FreeBSD.org) Received: from mail1.sourcehosting.net (mail1.sourcehosting.net [74.205.51.45]) by mx1.freebsd.org (Postfix) with ESMTP id 3614B8FC14; Tue, 30 Aug 2011 13:56:53 +0000 (UTC) Received: from 68-189-245-235.dhcp.oxfr.ma.charter.com ([68.189.245.235] helo=cube.entropy.prv) by mail1.sourcehosting.net with esmtp (Exim 4.73 (FreeBSD)) (envelope-from ) id 1QyOnT-0003NL-TB; Tue, 30 Aug 2011 09:56:18 -0400 Received: from v104.entropy.prv (v104.entropy.prv [192.168.1.104]) by cube.entropy.prv (Postfix) with ESMTP id C8963521559A; Tue, 30 Aug 2011 09:56:46 -0400 (EDT) Message-ID: <4E5CEC1E.5010209@FreeBSD.org> Date: Tue, 30 Aug 2011 09:56:46 -0400 From: Greg Larkin Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.20) Gecko/20110804 Lightning/1.0b2 Thunderbird/3.1.12 MIME-Version: 1.0 To: Ruslan Mahmatkhanov References: <4E5CE015.70803@FreeBSD.org> <4E5CE7BB.8050808@yandex.ru> In-Reply-To: <4E5CE7BB.8050808@yandex.ru> X-Enigmail-Version: 1.1.1 OpenPGP: id=1C940290 X-SA-Exim-Connect-IP: 68.189.245.235 X-SA-Exim-Mail-From: glarkin@FreeBSD.org X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail1.sourcehosting.net X-Spam-Level: *** X-Spam-Status: No, score=3.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RCVD_IN_RP_RNBL, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC, TVD_RCVD_IP autolearn=no version=3.3.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.sourcehosting.net) Cc: FreeBSD Ports Mailing List , miwi@FreeBSD.org Subject: Re: Python min version bumped from 2.4+ to 2.5+ X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: glarkin@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 13:56:54 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 8/30/11 9:38 AM, Ruslan Mahmatkhanov wrote: > Greg Larkin wrote on 30.08.2011 17:05: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi Martin, >> >> I have a question about a commit you made in February 2011: >> http://www.freshports.org/commit.php?message_id=201102250750.p1P7ofDg016541@repoman.freebsd.org&files=yes >> >> >> Part of the commit changed: >> >> USE_PYTHON= 2.4+ >> >> to >> >> USE_PYTHON= 2.5+ >> >> Was there a specific reason for doing so? I am running various >> tinderbox builds to check on port usage of the USE_PYTHON variable, and >> I noticed that devel/py-setuptools no longer builds if Python 2.4 is >> selected. >> >> I'd like to restore that capability, but before I send a PR, I wanted to >> check with you first. >> >> Thank you, >> Greg >> - -- >> Greg Larkin >> >> http://www.FreeBSD.org/ - The Power To Serve >> http://www.sourcehosting.net/ - Ready. Set. Code. >> http://twitter.com/cpucycle/ - Follow you, follow me > > I'm sorry for sail in, but i think that the reason is that python24 is > reached it's EOL long time ago. Actually the only supported python > releases atm according to python.org are - 2.7.2 and 3.2.1, and > developers highly encourages the users to move to this versions. > > 2.5 and 2.6 are in security-fix-only mode, there will be no ANY releases > for this branches after October 2011 and October 2013 respectively, > while 2.4 does not get security-fixes even. > > There is also this answer from Martin in this pr: > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/155526: > > python24 goes to the end of month, this port is on the todo for removal > Hi Ruslan, Ok, thank you for the explanation. Shall I mark python24 for removal from the tree or file a PR for python@ to do it? FYI, I have been running tinderbox builds with PYTHON_VERSION and PYTHON_DEFAULT_VERSION set to python2.4, python2.5, etc. to find out if ports with USE_PYTHON=yes need to be constrained a bit more. I figured that python2.4 was supported since it was still in the tree and wasn't marked for removal yet, but I admin that I didn't check python.org for confirmation. Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5c7B4ACgkQ0sRouByUApAZOQCcC0YgAzDxDj78I9u35+H53fur be8AmQFjWrGJ/xmjYpPp6ZkKB+ejDfq9 =tK4y -----END PGP SIGNATURE----- From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 14:26:13 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 322F81065674; Tue, 30 Aug 2011 14:26:13 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward11.mail.yandex.net (forward11.mail.yandex.net [IPv6:2a02:6b8:0:801::1]) by mx1.freebsd.org (Postfix) with ESMTP id 497088FC0C; Tue, 30 Aug 2011 14:26:12 +0000 (UTC) Received: from smtp13.mail.yandex.net (smtp13.mail.yandex.net [95.108.130.68]) by forward11.mail.yandex.net (Yandex) with ESMTP id E49DFE829BA; Tue, 30 Aug 2011 18:26:10 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314714370; bh=nJr1MNayoE61hgTZ593mWr9zcbOC/38rNlMXQ7OVtuc=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=kLoSt3RWyB3aEqhCP1+WeYiZuZlxvjmVRB9esxlvJWIePYHRSktzYSF9qz4zGiku5 WaIFnqJB9nmkOka/n3Pv7GTB8BXCyEIGW/q3yl+Pt7KZ1IlWlgRcqlTwNQpI9A2k7z qlDF0/a2o9XxTdpCQZK0GP+wTjt5iBo7Tw6WZUzg= Received: from smtp13.mail.yandex.net (localhost [127.0.0.1]) by smtp13.mail.yandex.net (Yandex) with ESMTP id C4BF4E402B6; Tue, 30 Aug 2011 18:26:10 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp13.mail.yandex.net (nwsmtp/Yandex) with ESMTP id QAmSaNin; Tue, 30 Aug 2011 18:26:10 +0400 X-Yandex-Spam: 1 Message-ID: <4E5CF2FF.5080302@yandex.ru> Date: Tue, 30 Aug 2011 18:26:07 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: glarkin@FreeBSD.org References: <4E5CE015.70803@FreeBSD.org> <4E5CE7BB.8050808@yandex.ru> <4E5CEC1E.5010209@FreeBSD.org> In-Reply-To: <4E5CEC1E.5010209@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports Mailing List , miwi@FreeBSD.org Subject: Re: Python min version bumped from 2.4+ to 2.5+ X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 14:26:13 -0000 Greg Larkin wrote on 30.08.2011 17:56: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 8/30/11 9:38 AM, Ruslan Mahmatkhanov wrote: >> Greg Larkin wrote on 30.08.2011 17:05: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Hi Martin, >>> >>> I have a question about a commit you made in February 2011: >>> http://www.freshports.org/commit.php?message_id=201102250750.p1P7ofDg016541@repoman.freebsd.org&files=yes >>> >>> >>> Part of the commit changed: >>> >>> USE_PYTHON= 2.4+ >>> >>> to >>> >>> USE_PYTHON= 2.5+ >>> >>> Was there a specific reason for doing so? I am running various >>> tinderbox builds to check on port usage of the USE_PYTHON variable, and >>> I noticed that devel/py-setuptools no longer builds if Python 2.4 is >>> selected. >>> >>> I'd like to restore that capability, but before I send a PR, I wanted to >>> check with you first. >>> >>> Thank you, >>> Greg >>> - -- >>> Greg Larkin >>> >>> http://www.FreeBSD.org/ - The Power To Serve >>> http://www.sourcehosting.net/ - Ready. Set. Code. >>> http://twitter.com/cpucycle/ - Follow you, follow me >> >> I'm sorry for sail in, but i think that the reason is that python24 is >> reached it's EOL long time ago. Actually the only supported python >> releases atm according to python.org are - 2.7.2 and 3.2.1, and >> developers highly encourages the users to move to this versions. >> >> 2.5 and 2.6 are in security-fix-only mode, there will be no ANY releases >> for this branches after October 2011 and October 2013 respectively, >> while 2.4 does not get security-fixes even. >> >> There is also this answer from Martin in this pr: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/155526: >> >> python24 goes to the end of month, this port is on the todo for removal >> > > Hi Ruslan, Hi Greg > > Ok, thank you for the explanation. Shall I mark python24 for removal > from the tree or file a PR for python@ to do it? It's not so easy actually, since we have many ports in the tree that still depend on 2.4 (notably all that zope/plone stuff) and i believe it was the reason why python24 still not be removed in the first place. I do some work about eliminating python24 usage in the tree (yesterdays py-pysqlite2x stuff - one of it), but it's not that fast. I also working on porting zope2.13/plone4 (that supports python 2.6 and 2.7) and i'm planing to finish it this weekend after proper testing. After that we can deprecate/remove existing zope/plone (not longer supported upstream). > > FYI, I have been running tinderbox builds with PYTHON_VERSION and > PYTHON_DEFAULT_VERSION set to python2.4, python2.5, etc. to find out if > ports with USE_PYTHON=yes need to be constrained a bit more. Yes, there is a lot of work. We have USE_PYTHON with bogus values like 1.5+, 1.6+, 2.0+ etc :). And most of python ports will not work with python3x so they should be constrained with -2.7 too. > I figured that python2.4 was supported since it was still in the tree > and wasn't marked for removal yet, but I admin that I didn't check > python.org for confirmation. As i already stated, i believe it's still there because there is dependent ports. And as far i know in linux world noone shipping python24 this days. Even RHEL/CentOS finally switched to 2.6.5 in their 6.x branches. > > Regards, > Greg > - -- > Greg Larkin > > http://www.FreeBSD.org/ - The Power To Serve > http://www.sourcehosting.net/ - Ready. Set. Code. > http://twitter.com/cpucycle/ - Follow you, follow me -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 15:23:30 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 045DD106566B; Tue, 30 Aug 2011 15:23:30 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id B4E1C8FC15; Tue, 30 Aug 2011 15:23:29 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id p7UFNS50047214; Tue, 30 Aug 2011 09:23:28 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id p7UFNSKX047211; Tue, 30 Aug 2011 09:23:28 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 30 Aug 2011 09:23:28 -0600 (MDT) From: Warren Block To: Matthias Andree In-Reply-To: <4E5CC44C.3070604@FreeBSD.org> Message-ID: References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Tue, 30 Aug 2011 09:23:28 -0600 (MDT) Cc: Sunpoet Po-Chuan Hsieh , ports@freebsd.org Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 15:23:30 -0000 On Tue, 30 Aug 2011, Matthias Andree wrote: > Am 30.08.2011 10:23, schrieb Sunpoet Po-Chuan Hsieh: >> sunpoet 2011-08-30 08:23:18 UTC >> >> FreeBSD ports repository >> >> Modified files: >> mail/procmail Makefile >> Log: >> - Take maintainership >> >> Revision Changes Path >> 1.60 +1 -1 ports/mail/procmail/Makefile > > I was just about to grab the port, deprecate and set two months > expiration date. > > Now that you're maintaining it I seek you to please let this > unmaintained unclean code from our FreeBSD ports world and deprecate it. > > The code is unmaintainable, hasn't seen maintenance in a decade, > is hard to use properly because of its fall-through "error handling" > (actually nonhandling) behaviour, and should finally disappear. > > Please add > > DEPRECATED= use mail/maildrop instead > EXPIRATION_DATE= 2011-10-31 Even if there was a drop-in replacement, that seems way too early to let people get it deployed. Some initial searching shows that maildrop is a functional replacement and can be used with sendmail's local_procmail feature, but the rules are different. There could be other functionality which users depend on, like formail, which a replacement might not have. For now, a pkg-message for mail/procmail that suggests alternates, and why, would give users some time to prepare. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 15:25:00 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26D21106564A; Tue, 30 Aug 2011 15:25:00 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 8E3338FC17; Tue, 30 Aug 2011 15:24:58 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBF75C.dip.t-dialin.net [217.251.247.92]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p7UFOuBF041052; Tue, 30 Aug 2011 15:24:57 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 p7UFOifb010155; Tue, 30 Aug 2011 17:24:45 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id p7UFOc6Q008169; Tue, 30 Aug 2011 15:24:44 GMT (envelope-from jhs@fire.js.berklix.net) Message-Id: <201108301524.p7UFOc6Q008169@fire.js.berklix.net> To: Sunpoet Po-Chuan Hsieh From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Tue, 30 Aug 2011 13:06:52 +0200." <4E5CC44C.3070604@FreeBSD.org> Date: Tue, 30 Aug 2011 17:24:38 +0200 Sender: jhs@berklix.com Cc: ports@freebsd.org, Matthias Andree Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 15:25:00 -0000 Matthias Andree wrote: > Am 30.08.2011 10:23, schrieb Sunpoet Po-Chuan Hsieh: > > sunpoet 2011-08-30 08:23:18 UTC > > > > FreeBSD ports repository > > > > Modified files: > > mail/procmail Makefile > > Log: > > - Take maintainership > > > > Revision Changes Path > > 1.60 +1 -1 ports/mail/procmail/Makefile > > I was just about to grab the port, deprecate and set two months > expiration date. Sorry No, it would be most irresponsible to consider a timeout of 2 months ! Procmail has been compiling regularly, working fine & vitaly necessary here for a decade. If one were considering to toss out such a vital tool, one should give a warning of a release or 2. (*) > Now that you're maintaining it I seek you to please let this > unmaintained unclean code from our FreeBSD ports world and deprecate it. Sunpoet please ignore Matthias ! Take your time. > The code is unmaintainable, hasn't seen maintenance in a decade, > is hard to use properly because of its fall-through "error handling" > (actually nonhandling) behaviour, It's not hard to use, Read the manual & learn. Examples http://www.berklix.com/~jhs/dots/.procmailrc http://www.berklix.com/~jhs/dots/.procmailrc.lists more in: http://www.berklix.com/~jhs/dots/ > and should finally disappear. No > Please add > > DEPRECATED= use mail/maildrop instead No, > EXPIRATION_DATE= 2011-10-31 (*) Irresponsible lack of warning ! Lots of users of releases dont even read ports@ ( Reminds me of the Hitch Hikers Guide episode where the vogons come to destroy the earth, & claim due warning was lodged in Alpha Centauri ;-) Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 15:36:51 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B971410656A7 for ; Tue, 30 Aug 2011 15:36:51 +0000 (UTC) (envelope-from code@apotheon.net) Received: from oproxy4-pub.bluehost.com (oproxy4.bluehost.com [IPv6:2605:dc00:100:2::a4]) by mx1.freebsd.org (Postfix) with SMTP id 7BDE48FC1B for ; Tue, 30 Aug 2011 15:36:51 +0000 (UTC) Received: (qmail 9751 invoked by uid 0); 30 Aug 2011 15:36:51 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by cpoproxy1.bluehost.com with SMTP; 30 Aug 2011 15:36:51 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.net; s=default; h=In-Reply-To:Content-Type:Mime-Version:References:Message-ID:Subject:To:From:Date; bh=32MO+CXseLugLdq9rJjHJsSgEeqox2GRM7X9O3YDJ9s=; b=JMpjAg6IxUwS4MFPegeKcm4H3aXBN+DEq3yYOcRTbkXx8k0ntQlg0x5o+GTT4SlSPJq6B9K7XfTFdEc9mtLpwsvQkrbeiajYTmDnWZfZeilFheOpRvpbi0IdFPoDDgWI; Received: from c-24-8-180-234.hsd1.co.comcast.net ([24.8.180.234] helo=kukaburra.hydra) by box543.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1QyQMr-0007NZ-To for freebsd-ports@FreeBSD.org; Tue, 30 Aug 2011 09:36:50 -0600 Received: by kukaburra.hydra (sSMTP sendmail emulation); Tue, 30 Aug 2011 09:18:23 -0600 Date: Tue, 30 Aug 2011 09:18:23 -0600 From: Chad Perrin To: freebsd-ports@FreeBSD.org Message-ID: <20110830151823.GA69850@guilt.hydra> Mail-Followup-To: freebsd-ports@FreeBSD.org References: <20110830091358.GA83706@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline In-Reply-To: <20110830091358.GA83706@lpthe.jussieu.fr> User-Agent: Mutt/1.4.2.3i X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.org} {sentby:smtp auth 24.8.180.234 authed with ren@apotheon.org} Cc: Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 15:36:51 -0000 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 30, 2011 at 11:13:58AM +0200, Michel Talon wrote: > Chad Perrin wrote: > > > >Of course, your goal is apparently to > >convince me that yours are the "correct" priorities. >=20 > Indeed i think having the correct priorities is essential when choosing > between different options, and i am sincerely convinced that my choices > are shared by a lot more people than yours. You're right that having the "correct" priorities is good. You're probably right that more people have your OS preference priorities than I do. Popularity doesn't mean something is "correct", though, and popularity of particular priorities for OS choice doesn't mean a given OS project should emulate those priorities. Would you suggest that every high-quality steakhouse in the United States should emulate the food preparation policies of McDonald's? The world needs an OS that serves the preferences FreeBSD serves so much better than Ubuntu, because the fact that a set of priorities favoring Ubuntu is more popular is not synonymous with the notion that it's ubiquitous. --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk5c/z8ACgkQ9mn/Pj01uKUtEACgpxxeq7uds5wxxhj0xx/vtsNO opoAoJz/wNVpV7xpmOWIaYoNaNE0j/aV =kH8E -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi-- From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 15:47:47 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC2F4106564A for ; Tue, 30 Aug 2011 15:47:47 +0000 (UTC) (envelope-from code@apotheon.net) Received: from oproxy6-pub.bluehost.com (oproxy6.bluehost.com [IPv6:2605:dc00:100:2::a6]) by mx1.freebsd.org (Postfix) with SMTP id 8DA2A8FC12 for ; Tue, 30 Aug 2011 15:47:47 +0000 (UTC) Received: (qmail 17555 invoked by uid 0); 30 Aug 2011 15:47:47 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by cpoproxy3.bluehost.com with SMTP; 30 Aug 2011 15:47:47 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.net; s=default; h=In-Reply-To:Content-Type:Mime-Version:References:Message-ID:Subject:To:From:Date; bh=LyOsuhMnbuLQN4TNsrKqiRfXGGCUdviPb/xqmPlWJh4=; b=uALMTfJbMCM0zwND7tMk+05BufglPdLXuadBqLQbpFEIpm0T2d0oS8qeml8m0LTSTV53FlUeMEKZ2HRKj44bgfz4BfO5JGY6cyXpBGuXOOF2HcfmCMz0VdqSO2R3w0A8; Received: from c-24-8-180-234.hsd1.co.comcast.net ([24.8.180.234] helo=kukaburra.hydra) by box543.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1QyQXS-0004zR-4t for freebsd-ports@FreeBSD.org; Tue, 30 Aug 2011 09:47:47 -0600 Received: by kukaburra.hydra (sSMTP sendmail emulation); Tue, 30 Aug 2011 09:29:20 -0600 Date: Tue, 30 Aug 2011 09:29:20 -0600 From: Chad Perrin To: "freebsd-ports@FreeBSD.org" Message-ID: <20110830152920.GB69850@guilt.hydra> Mail-Followup-To: "freebsd-ports@FreeBSD.org" References: <4E5C79AF.6000408@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Pd0ReVV5GZGQvF3a" Content-Disposition: inline In-Reply-To: <4E5C79AF.6000408@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.org} {sentby:smtp auth 24.8.180.234 authed with ren@apotheon.org} Cc: Subject: Re: Why do we not mark vulnerable ports DEPRECATED? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 15:47:47 -0000 --Pd0ReVV5GZGQvF3a Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 29, 2011 at 10:48:31PM -0700, Doug Barton wrote: > I'm doing some updates and came across mail/postfix-policyd-spf which > relies on mail/libspf2-10. The latter had a vuxml entry added on > 2008-10-27. So my question is, why has mail/libspf2-10 been allowed to > remain in the tree vulnerable for almost 3 years? >=20 > Wouldn't it make more sense to mark vulnerable ports DEPRECATED > immediately with a short expiration? When they get fixed they get > un-deprecated. If they don't, they get removed. Can someone explain why > this would be a bad idea? Might that not interfere with the process of getting a new maintainer for a popular port when its previous maintainer has been lax (or hit by a bus)? --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --Pd0ReVV5GZGQvF3a Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk5dAdAACgkQ9mn/Pj01uKXUhwCfd97T/7PGcPPreozRhQTZaOrk iNwAoONQx/zcf3nZD7iweK1gNdG9E2CQ =mPm0 -----END PGP SIGNATURE----- --Pd0ReVV5GZGQvF3a-- From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 15:48:28 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id A23921065670; Tue, 30 Aug 2011 15:48:28 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id D4C5123CF2B; Tue, 30 Aug 2011 17:48:26 +0200 (CEST) Message-ID: <4E5D064A.8030703@FreeBSD.org> Date: Tue, 30 Aug 2011 17:48:26 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: Mikhail Tsatsenko References: <4E5CDFDF.6070705@gmail.com> In-Reply-To: <4E5CDFDF.6070705@gmail.com> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org Subject: Re: mail/popper, mail/premail and mail/miltergreylist maintainership X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 15:48:28 -0000 Am 30.08.2011 15:04, schrieb Mikhail Tsatsenko: > I'd like to take maintainership of following unmaintained now ports: > mail/popper > mail/miltergreylist > mail/milter-greylist-devel > mail/premail Hi Mikhail, thanks for volunteering! You are now the maintainer of these four ports (actually the 2nd ist mail/milter-greylist). Best regards, Matthias From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 15:57:12 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 59E3D106566B for ; Tue, 30 Aug 2011 15:57:12 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 4D9FB23CF2B for ; Tue, 30 Aug 2011 17:57:10 +0200 (CEST) Message-ID: <4E5D0856.8080505@FreeBSD.org> Date: Tue, 30 Aug 2011 17:57:10 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> <20110830111152.GF28186@home.opsec.eu> <4E5CD28A.1080809@FreeBSD.org> <20110830122726.GG28186@home.opsec.eu> In-Reply-To: <20110830122726.GG28186@home.opsec.eu> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 15:57:12 -0000 Am 30.08.2011 14:27, schrieb Kurt Jaeger: > [maildrop] >>> - Can it use the 700+ lines long .procmailrc I have running >>> in a criticial application or do I have to migrate that ? >> >> You'd have to migrate that. > > That's what I assumed. > >> Bottom line: the sooner we get rid from procmail the better. > > There are many other applications that have issues, as well. > > It's already a lot of work just to keep up with the bug-de-jour > and the upgrade-de-jour and doing it all in parallel does > not scale very well. > > Therefore, one has to choose what one can work on. > > If the fbsd ports drop procmail, it will just add more on > my plate that I have to do myself. Similar to many other > apps and ports and you-name-it. > > While I dislike bitrot like anyone else, I have an issue with > the dropping of ports in general, because that will not scale. I understand that keeping unchanging software can sometimes be necessary, if you're working around its quirks. At the same time I'd like to discourage new installations of dead software so that it disappears over time, rather than haunt fresh systems. How about if we added a new tag "OBSOLESCENT" or so that permits building the software only if it's already installed but refuses new installations? Of course there could be a switch to override that, like TRYBROKEN that can override BROKEN= tags. I'm not sure if it's feasible for packages (but OBSOLESCENT could imply "do not package") but for ports it would be possible. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 15:58:58 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 24050106566C for ; Tue, 30 Aug 2011 15:58:58 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 56B9D23CF2B for ; Tue, 30 Aug 2011 17:58:56 +0200 (CEST) Message-ID: <4E5D08C0.90404@FreeBSD.org> Date: Tue, 30 Aug 2011 17:58:56 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 15:58:58 -0000 On the procmail depracation topic, Warren Block wrote: > Some initial searching shows that maildrop is a functional replacement > and can be used with sendmail's local_procmail feature, but the rules > are different. There could be other functionality which users depend > on, like formail, which a replacement might not have. maildrop comes with reformail. It, too, has different options than procmail, but by and large it fits the bill. > For now, a pkg-message for mail/procmail that suggests alternates, and > why, would give users some time to prepare. OK. Good suggestion. Thank you. Best regards, Matthias From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 16:06:18 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id C5D50106564A for ; Tue, 30 Aug 2011 16:06:17 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 058E423CF2B for ; Tue, 30 Aug 2011 18:06:16 +0200 (CEST) Message-ID: <4E5D0A77.3070304@FreeBSD.org> Date: Tue, 30 Aug 2011 18:06:15 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <201108301524.p7UFOc6Q008169@fire.js.berklix.net> In-Reply-To: <201108301524.p7UFOc6Q008169@fire.js.berklix.net> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 16:06:18 -0000 Am 30.08.2011 17:24, schrieb Julian H. Stacey: > Matthias Andree wrote: >> Am 30.08.2011 10:23, schrieb Sunpoet Po-Chuan Hsieh: >>> sunpoet 2011-08-30 08:23:18 UTC >>> >>> FreeBSD ports repository >>> >>> Modified files: >>> mail/procmail Makefile >>> Log: >>> - Take maintainership >>> >>> Revision Changes Path >>> 1.60 +1 -1 ports/mail/procmail/Makefile >> >> I was just about to grab the port, deprecate and set two months >> expiration date. > > Sorry No, it would be most irresponsible to consider a timeout of > 2 months ! Procmail has been compiling regularly, working fine & > vitaly necessary here for a decade. If one were considering to > toss out such a vital tool, one should give a warning of a release or 2. (*) It should have been tossed out half a decade ago, but if people feel it's so hard to migrate away from it we should extend the period. But we should really deprecate dead software. > It's not hard to use, Read the manual & learn. Examples > http://www.berklix.com/~jhs/dots/.procmailrc WARNING - DO NOT USE THOSE. Essentially all those examples have no error handling for delivering recipes (see my earlier post in this thread for a remedy that limits usefulness of some recipes), but the all-too-typical problem that in temporary disk-full condition, mail can end up anywhere, because procmail silently proceeds to the next recipe after the previous one has failed. And that's extactly the reason why procmail must die. I don't mean to disrupt existing installations, but I do mean to discourage new ones. >> DEPRECATED= use mail/maildrop instead > > No, > >> EXPIRATION_DATE= 2011-10-31 > > (*) > Irresponsible lack of warning ! No need, we can bump the PORTREVISION so it appears on the users' radars. > Lots of users of releases dont even read ports@ > ( Reminds me of the Hitch Hikers Guide episode where the vogons > come to destroy the earth, & claim due warning was lodged in Alpha Centauri ;-) We're not trying to build an Intergalactic Expressway through Earth though, but my goal is to prevent nasty surprises. Once you have the necessary error handling in place in your .procmailrc, a .mailfilter file of equal usefulness in maildrop is shorter and more concise. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 16:23:48 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D283106566B for ; Tue, 30 Aug 2011 16:23:48 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id A7D248FC16 for ; Tue, 30 Aug 2011 16:23:47 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBF75C.dip.t-dialin.net [217.251.247.92]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p7UGCHk9041595; Tue, 30 Aug 2011 16:12:17 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 p7UGC5rS010347; Tue, 30 Aug 2011 18:12:05 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id p7UGBrwa008677; Tue, 30 Aug 2011 16:11:59 GMT (envelope-from jhs@fire.js.berklix.net) Message-Id: <201108301611.p7UGBrwa008677@fire.js.berklix.net> To: Chad Perrin From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Sun, 28 Aug 2011 18:21:37 MDT." <20110829002137.GA61876@guilt.hydra> Date: Tue, 30 Aug 2011 18:11:53 +0200 Sender: jhs@berklix.com Cc: freebsd-ports@freebsd.org Subject: Re: Time to remove the GNUTLS option in the print/cups-client port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 16:23:48 -0000 > ... the US > patent system has become horribly broken in practice. The world's > biggest patent-holders that actually produce anything pretty much all > agree that the system is horribly broken, and mostly collect patents for > defensive use. Not just USA but Europe too, etc. A European Patent Office examiner morosely & sarcasticly speculated that big patent holders might drive lorries (trucks) of patents up to weigh bridges, approach competitors & say eg "We have seven tons, if you have over 6 lets cross licence" Examiners are under time pressure to grant by default unless they can quickly find a reason not to. Politicians of leading countries see a future of increasingly sellling intangible exports, so want more patents, not less. International free software groups have no rich lobby groups, so ignored. Sat 17th Sept in 600+ cities round the world, is a chance for free software movements not just to promote Linux & BSD etc, but also to address software patents - see FSF & FSFE logos among BSD & Penguins etc on http://softwarefreedomday.org/ Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 16:24:44 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BC07106567A for ; Tue, 30 Aug 2011 16:24:44 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 7E85C8FC21 for ; Tue, 30 Aug 2011 16:24:44 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id D7B475615B; Tue, 30 Aug 2011 11:24:43 -0500 (CDT) Date: Tue, 30 Aug 2011 11:24:43 -0500 From: Mark Linimon To: "Julian H. Stacey" Message-ID: <20110830162443.GA17573@lonesome.com> References: <20110829002137.GA61876@guilt.hydra> <201108301611.p7UGBrwa008677@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201108301611.p7UGBrwa008677@fire.js.berklix.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Chad Perrin , freebsd-ports@freebsd.org Subject: Re: Time to remove the GNUTLS option in the print/cups-client port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 16:24:44 -0000 Could we please change the Subject line to match the content now? mcl From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 16:34:39 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E645E106566B for ; Tue, 30 Aug 2011 16:34:38 +0000 (UTC) (envelope-from sterling@camdensoftware.com) Received: from wh1.interactivevillages.com (ca.2e.7bae.static.theplanet.com [174.123.46.202]) by mx1.freebsd.org (Postfix) with ESMTP id AD4168FC15 for ; Tue, 30 Aug 2011 16:34:38 +0000 (UTC) Received: from 184-78-197-203.war.clearwire-wmx.net ([184.78.197.203] helo=_HOSTNAME_) by wh1.interactivevillages.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1QyRGl-0000XF-FE for freebsd-ports@freebsd.org; Tue, 30 Aug 2011 09:34:12 -0700 Received: by _HOSTNAME_ (sSMTP sendmail emulation); Tue, 30 Aug 2011 09:34:33 -0700 Date: Tue, 30 Aug 2011 09:34:33 -0700 From: Chip Camden To: freebsd-ports@freebsd.org Message-ID: <20110830163433.GC34744@libertas.local.camdensoftware.com> Mail-Followup-To: freebsd-ports@freebsd.org References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> <20110830111152.GF28186@home.opsec.eu> <4E5CD28A.1080809@FreeBSD.org> <20110830122726.GG28186@home.opsec.eu> <4E5D0856.8080505@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="raC6veAxrt5nqIoY" Content-Disposition: inline In-Reply-To: <4E5D0856.8080505@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Company: Camden Software Consulting URL: http://camdensoftware.com X-PGP-Key: http://pgp.mit.edu:11371/pks/lookup?search=0xD6DBAF91 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - wh1.interactivevillages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - camdensoftware.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 16:34:39 -0000 --raC6veAxrt5nqIoY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoth Matthias Andree on Tuesday, 30 August 2011: > Am 30.08.2011 14:27, schrieb Kurt Jaeger: > > [maildrop] > >>> - Can it use the 700+ lines long .procmailrc I have running > >>> in a criticial application or do I have to migrate that ? > >> > >> You'd have to migrate that. > >=20 > > That's what I assumed. > >=20 > >> Bottom line: the sooner we get rid from procmail the better. > >=20 > > There are many other applications that have issues, as well. > >=20 > > It's already a lot of work just to keep up with the bug-de-jour > > and the upgrade-de-jour and doing it all in parallel does > > not scale very well. > >=20 > > Therefore, one has to choose what one can work on. > >=20 > > If the fbsd ports drop procmail, it will just add more on > > my plate that I have to do myself. Similar to many other > > apps and ports and you-name-it. > >=20 > > While I dislike bitrot like anyone else, I have an issue with > > the dropping of ports in general, because that will not scale. >=20 > I understand that keeping unchanging software can sometimes be > necessary, if you're working around its quirks. >=20 > At the same time I'd like to discourage new installations of dead > software so that it disappears over time, rather than haunt fresh systems. >=20 >=20 > How about if we added a new tag "OBSOLESCENT" or so that permits > building the software only if it's already installed but refuses new > installations? Of course there could be a switch to override that, like > TRYBROKEN that can override BROKEN=3D tags. >=20 > I'm not sure if it's feasible for packages (but OBSOLESCENT could imply > "do not package") but for ports it would be possible. I like this idea. But please call it OBSOLETE, instead of OBSOLESCENT. Gratuitous suffixes are as much of a bane to the language as obsolete software is to an OS. --=20 =2EO. | Sterling (Chip) Camden | http://camdensoftware.com =2E.O | sterling@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com --raC6veAxrt5nqIoY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJOXREZAAoJEIpckszW26+RgGIH/i2hZqIiomNlu+4Bff0vYuCK wpMew8hbg89M11X5IH1hcNbWUWIfSU0uW5IblXL9PRf+Vv3xcNTYkJrIKrUBYKoN RcFQ0Fj0vPK/u7rjsTsvhUgaMJ2B5yKnggcSYk4FPa0J/c/GO84J0Q5IAyOsNVzE hUx1JdR0ZI+uy9gccTV0Sv2HFanFNRlz5Y1CkrKUTkO7YOxfe1lxdIdevHSAziC7 JO0xpFm2u+a/AifV1pqP1seHNlwhbZTVFcWAKNoI/OJR7JKP1AN9/mQlAG3z10bc y+MH4He36DzKdoCY0mXBSIB2Gw+nX+9DyI8G3iYP98qTwwLPoNCfx4P9eJGuReE= =dSbo -----END PGP SIGNATURE----- --raC6veAxrt5nqIoY-- From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 16:39:34 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 378171065670; Tue, 30 Aug 2011 16:39:34 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 18A1B8FC14; Tue, 30 Aug 2011 16:39:33 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 988325615B; Tue, 30 Aug 2011 11:39:33 -0500 (CDT) Date: Tue, 30 Aug 2011 11:39:33 -0500 From: Mark Linimon To: Matthias Andree Message-ID: <20110830163933.GC17573@lonesome.com> References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> <20110830111152.GF28186@home.opsec.eu> <4E5CD28A.1080809@FreeBSD.org> <20110830122726.GG28186@home.opsec.eu> <4E5D0856.8080505@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E5D0856.8080505@FreeBSD.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-ports@freebsd.org Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 16:39:34 -0000 On Tue, Aug 30, 2011 at 05:57:10PM +0200, Matthias Andree wrote: > How about if we added a new tag "OBSOLESCENT" or so that permits > building the software only if it's already installed but refuses new > installations? Right now if you set DEPRECATED you'll get a warning. Shouldn't that be sufficient without introducing a new mechanism that enforces a policy? mcl From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 16:40:43 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3BD0D106566C for ; Tue, 30 Aug 2011 16:40:43 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id E9D3E8FC1D for ; Tue, 30 Aug 2011 16:40:42 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 6E36128424; Tue, 30 Aug 2011 18:40:41 +0200 (CEST) Received: from [192.168.1.2] (ip-86-49-61-235.net.upcbroadband.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 8B0E028423; Tue, 30 Aug 2011 18:40:40 +0200 (CEST) Message-ID: <4E5D1288.9010104@quip.cz> Date: Tue, 30 Aug 2011 18:40:40 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: mandree@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org Subject: FreeBSD Port: openvpn-2.2.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 16:40:43 -0000 Hi, I noticed a problem with rc script for openvpn-2.2.1 on recent FreeBSD 8-STABLE (Aug 13 20:33:31 CEST 2011). It failed to restart if I have the following in rc.conf openvpn_bp_office_if="tap bridge" # service openvpn_bp_office restart Stopping openvpn_bp_office. Waiting for PIDS: 75580. kldload: can't load if_bridge: File exists /usr/local/etc/rc.d/openvpn_bp_office: WARNING: Could not load bridge module. /usr/local/etc/rc.d/openvpn_bp_office: WARNING: failed precmd routine for openvpn_bp_office The problem is, that if_bridge.ko is already loaded, but the kldload routine in rc script will not detect it, because if_bridge has not debug.if_bridge_debug sysctl entry. (older version of rc script works fine with kldstat -m if_bridge) So I have a question - why the rc script is not using required_modules variable from /etc/rc.subr which is there exactly for this purpose? Miroslav Lachman From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 17:13:54 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id BE5B0106566B for ; Tue, 30 Aug 2011 17:13:53 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id CBDCC23CF4F for ; Tue, 30 Aug 2011 19:13:52 +0200 (CEST) Message-ID: <4E5D1A50.10406@FreeBSD.org> Date: Tue, 30 Aug 2011 19:13:52 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <4E5D1288.9010104@quip.cz> In-Reply-To: <4E5D1288.9010104@quip.cz> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD Port: openvpn-2.2.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 17:13:54 -0000 Am 30.08.2011 18:40, schrieb Miroslav Lachman: > Hi, > > I noticed a problem with rc script for openvpn-2.2.1 on recent FreeBSD > 8-STABLE (Aug 13 20:33:31 CEST 2011). > It failed to restart if I have the following in rc.conf > > openvpn_bp_office_if="tap bridge" > > > # service openvpn_bp_office restart > Stopping openvpn_bp_office. > Waiting for PIDS: 75580. > kldload: can't load if_bridge: File exists > /usr/local/etc/rc.d/openvpn_bp_office: WARNING: Could not load bridge > module. > /usr/local/etc/rc.d/openvpn_bp_office: WARNING: failed precmd routine > for openvpn_bp_office > > The problem is, that if_bridge.ko is already loaded, but the kldload > routine in rc script will not detect it, because if_bridge has not > debug.if_bridge_debug sysctl entry. (older version of rc script works > fine with kldstat -m if_bridge) > > So I have a question - why the rc script is not using required_modules > variable from /etc/rc.subr which is there exactly for this purpose? Miroslav, thanks for your required_modules suggestion. The script dates back to 2005, when required_modules didn't exist (it was merged to a stable version in August 2007). I have fixed the openvpn20 and openvpn ports. Revisions 2.2.1_1 and 2.0.9_2 (respectively) have the fix. Thanks for the report and suggestion! Best regards, Matthias From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 17:30:14 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EC941065670; Tue, 30 Aug 2011 17:30:14 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id CBD698FC08; Tue, 30 Aug 2011 17:30:13 +0000 (UTC) Received: by gxk28 with SMTP id 28so7033906gxk.13 for ; Tue, 30 Aug 2011 10:30:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=M333fO8duDcT674md2pkRRVLFLTuajQziBsa5DzO0zc=; b=ZxK7k39Cm21O5JEuPAJ5yKLqqTTL6z99ns1oW7aSKp8W1TG/L4gqN7ZgtVrQYNFl8U y77tOz/vLKhcNfU22qw08TLFD4e0zoXDz5o3IUhviuZM8aHJnEPVYrsuMzjfFXerIgmH LBXbVFBCw9qsFs3nDTpScjoCCCKRLnVJxN+jI= Received: by 10.43.59.142 with SMTP id wo14mr38448icb.373.1314725413127; Tue, 30 Aug 2011 10:30:13 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.61.148 with HTTP; Tue, 30 Aug 2011 10:29:43 -0700 (PDT) In-Reply-To: <20110830163933.GC17573@lonesome.com> References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> <20110830111152.GF28186@home.opsec.eu> <4E5CD28A.1080809@FreeBSD.org> <20110830122726.GG28186@home.opsec.eu> <4E5D0856.8080505@FreeBSD.org> <20110830163933.GC17573@lonesome.com> From: Chris Rees Date: Tue, 30 Aug 2011 18:29:43 +0100 X-Google-Sender-Auth: IOuFp2kM0Ec1ij-FfSMO1sta2Kc Message-ID: To: Mark Linimon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ports@freebsd.org, Matthias Andree Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 17:30:14 -0000 On 30 August 2011 17:39, Mark Linimon wrote: > On Tue, Aug 30, 2011 at 05:57:10PM +0200, Matthias Andree wrote: >> How about if we added a new tag "OBSOLESCENT" or so that permits >> building the software only if it's already installed but refuses new >> installations? > > Right now if you set DEPRECATED you'll get a warning. =A0Shouldn't > that be sufficient without introducing a new mechanism that enforces > a policy? +1 I agree-- isn't that what DEPRECATED is for?? Chris From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 17:43:41 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 745991065670 for ; Tue, 30 Aug 2011 17:43:41 +0000 (UTC) (envelope-from jeroen@virtualhost.nl) Received: from mail.virtualhost.nl (mail.virtualhost.nl [89.200.201.133]) by mx1.freebsd.org (Postfix) with ESMTP id C9D668FC19 for ; Tue, 30 Aug 2011 17:43:40 +0000 (UTC) Received: (qmail 57282 invoked by uid 1141); 30 Aug 2011 19:43:39 +0200 Received: from ip120-12-208-87.adsl2.static.versatel.nl (HELO blue.myspectrum.nl) (87.208.12.120) (smtp-auth username jeroen@virtualhost.nl, mechanism plain) by mail.virtualhost.nl (qpsmtpd/0.84) with (CAMELLIA256-SHA encrypted) ESMTPSA; Tue, 30 Aug 2011 19:43:39 +0200 Message-ID: <4E5D214A.3090308@virtualhost.nl> Date: Tue, 30 Aug 2011 19:43:38 +0200 From: Jeroen User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:5.0) Gecko/20110801 Thunderbird/5.0 MIME-Version: 1.0 To: Ruslan Mahmatkhanov References: <4E5AB569.4060703@virtualhost.nl> <4E5B604B.1090902@yandex.ru> In-Reply-To: <4E5B604B.1090902@yandex.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org, david@catwhisker.org Subject: Re: firefox 6: mercurial seems to be missing as dependency X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 17:43:41 -0000 >> >> When updating firefox to the latest version (from ports) it complained >> about hg not being found. Apparently a dependency to mercurial is >> missing. I haven't checked why, installing it resolved it. >> > > Can you please show us exact error message for further investigation? > Turns out this is an (almost) non-issue. make ends with some errors as shown below. I assumed it was needed for the build, and installed it. However it is not a build error, which I took it for, Firefox is build correctly and installs fine without Mercurial, it just shows some errors. Regards, Jeroen gmake[4]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/browser/app' gmake[3]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/browser' gmake[2]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release' gmake tools_tier_app gmake[2]: Entering directory `/usr/ports/www/firefox/work/mozilla-release' hg: not found tools_tier_app gmake[3]: Entering directory `/usr/ports/www/firefox/work/mozilla-release' gmake[3]: `extensions/Makefile' is up to date. gmake[3]: `browser/branding/official/Makefile' is up to date. [....] gmake[6]: Nothing to be done for `tools'. gmake[6]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/browser/components/migration/src' gmake[5]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/browser/components/migration' gmake[5]: Entering directory `/usr/ports/www/firefox/work/mozilla-release/browser/components/build' gmake[5]: Nothing to be done for `tools'. gmake[5]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/browser/components/build' gmake[4]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/browser/components' hg: not found gmake[4]: Entering directory `/usr/ports/www/firefox/work/mozilla-release/browser/app' gmake[5]: Entering directory `/usr/ports/www/firefox/work/mozilla-release/browser/app/profile/extensions' gmake[6]: Entering directory `/usr/ports/www/firefox/work/mozilla-release/browser/app/profile/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}' gmake[6]: Nothing to be done for `tools'. gmake[6]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/browser/app/profile/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}' gmake[5]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/browser/app/profile/extensions' gmake[4]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/browser/app' gmake[3]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/browser' gmake[2]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release' gmake[1]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release' if test -d ./dist/bin ; then touch ./dist/bin/.purgecaches ; fi hg: not found sed: /usr/ports/www/firefox/work/mozilla-release/build/unix/*.pc: No such file or directory From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 17:44:15 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 056FE106567E; Tue, 30 Aug 2011 17:44:15 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id E8E4B23CF4F; Tue, 30 Aug 2011 19:44:13 +0200 (CEST) Message-ID: <4E5D216C.6070801@FreeBSD.org> Date: Tue, 30 Aug 2011 19:44:12 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: ports@FreeBSD.org References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> <20110830111152.GF28186@home.opsec.eu> <4E5CD28A.1080809@FreeBSD.org> <20110830122726.GG28186@home.opsec.eu> <4E5D0856.8080505@FreeBSD.org> <20110830163933.GC17573@lonesome.com> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Chris Rees Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 17:44:15 -0000 Am 30.08.2011 19:29, schrieb Chris Rees: > On 30 August 2011 17:39, Mark Linimon wrote: >> On Tue, Aug 30, 2011 at 05:57:10PM +0200, Matthias Andree wrote: >>> How about if we added a new tag "OBSOLESCENT" or so that permits >>> building the software only if it's already installed but refuses new >>> installations? >> >> Right now if you set DEPRECATED you'll get a warning. Shouldn't >> that be sufficient without introducing a new mechanism that enforces >> a policy? > > +1 > > I agree-- isn't that what DEPRECATED is for?? It only warns, it does not prevent fresh installs on systems that don't have the same port/package already installed. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 17:57:40 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8ECCF1065673; Tue, 30 Aug 2011 17:57:40 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 5607C8FC15; Tue, 30 Aug 2011 17:57:40 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 0F89D5615B; Tue, 30 Aug 2011 12:57:40 -0500 (CDT) Date: Tue, 30 Aug 2011 12:57:40 -0500 From: Mark Linimon To: Matthias Andree Message-ID: <20110830175740.GA19289@lonesome.com> References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> <20110830111152.GF28186@home.opsec.eu> <4E5CD28A.1080809@FreeBSD.org> <20110830122726.GG28186@home.opsec.eu> <4E5D0856.8080505@FreeBSD.org> <20110830163933.GC17573@lonesome.com> <4E5D216C.6070801@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E5D216C.6070801@FreeBSD.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: ports@FreeBSD.org, Chris Rees Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 17:57:40 -0000 On Tue, Aug 30, 2011 at 07:44:12PM +0200, Matthias Andree wrote: > It only warns, it does not prevent fresh installs on systems that don't > have the same port/package already installed. "code, not policy" ... ? mcl From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 18:07:33 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A0711065673 for ; Tue, 30 Aug 2011 18:07:33 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id BB2DC8FC17 for ; Tue, 30 Aug 2011 18:07:32 +0000 (UTC) Received: (qmail invoked by alias); 30 Aug 2011 18:07:31 -0000 Received: from g227000177.adsl.alicedsl.de (EHLO apollo.emma.line.org) [92.227.0.177] by mail.gmx.net (mp004) with SMTP; 30 Aug 2011 20:07:31 +0200 X-Authenticated: #428038 X-Provags-ID: V01U2FsdGVkX19GbExhXlpG9JFvsfCjQaG2wMrh6CXnR1nw14WcmX fRDX2RT8D9QL5X Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 3601E23CF4F for ; Tue, 30 Aug 2011 20:07:30 +0200 (CEST) Message-ID: <4E5D26E2.7040300@gmx.de> Date: Tue, 30 Aug 2011 20:07:30 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> <20110830111152.GF28186@home.opsec.eu> <4E5CD28A.1080809@FreeBSD.org> <20110830122726.GG28186@home.opsec.eu> <4E5D0856.8080505@FreeBSD.org> <20110830163933.GC17573@lonesome.com> <4E5D216C.6070801@FreeBSD.org> <20110830175740.GA19289@lonesome.com> In-Reply-To: <20110830175740.GA19289@lonesome.com> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 18:07:33 -0000 Am 30.08.2011 19:57, schrieb Mark Linimon: > On Tue, Aug 30, 2011 at 07:44:12PM +0200, Matthias Andree wrote: >> It only warns, it does not prevent fresh installs on systems that don't >> have the same port/package already installed. > > "code, not policy" ... ? Well... is _is_ policy and meant as such. We make decisions for ports users all the time, and this is no exception. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 18:34:43 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1413106566C for ; Tue, 30 Aug 2011 18:34:43 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 61FD38FC19 for ; Tue, 30 Aug 2011 18:34:43 +0000 (UTC) Received: by vxh11 with SMTP id 11so6951236vxh.13 for ; Tue, 30 Aug 2011 11:34:42 -0700 (PDT) Received: by 10.52.23.113 with SMTP id l17mr1791833vdf.57.1314729282626; Tue, 30 Aug 2011 11:34:42 -0700 (PDT) Received: from scorpio.seibercom.net (cpe-098-026-084-161.nc.res.rr.com [98.26.84.161]) by mx.google.com with ESMTPS id bw9sm158888vcb.39.2011.08.30.11.34.41 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 30 Aug 2011 11:34:41 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jerry@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3RpJRN2Y8sz2CG5G for ; Tue, 30 Aug 2011 14:34:40 -0400 (EDT) Date: Tue, 30 Aug 2011 14:34:39 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110830143439.306cd375@seibercom.net> In-Reply-To: <20110830162443.GA17573@lonesome.com> References: <20110829002137.GA61876@guilt.hydra> <201108301611.p7UGBrwa008677@fire.js.berklix.net> <20110830162443.GA17573@lonesome.com> Organization: seibercom.net X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: Time to remove the GNUTLS option in the print/cups-client port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 18:34:43 -0000 On Tue, 30 Aug 2011 11:24:43 -0500 Mark Linimon articulated: > Could we please change the Subject line to match the content now? That would probably not be the best idea. All things considered, the new posts may well end up threaded along with the older posts. Starting a entirely new post would be a better solution. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ Actors will happen even in the best-regulated families. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 18:55:26 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id DA4E1106566B for ; Tue, 30 Aug 2011 18:55:26 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 56CD814FEA9 for ; Tue, 30 Aug 2011 18:55:26 +0000 (UTC) Message-ID: <4E5D321D.9020209@FreeBSD.org> Date: Tue, 30 Aug 2011 11:55:25 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110824 Thunderbird/6.0 MIME-Version: 1.0 To: "freebsd-ports@FreeBSD.org" References: <4E5C79AF.6000408@FreeBSD.org> <20110830152920.GB69850@guilt.hydra> In-Reply-To: <20110830152920.GB69850@guilt.hydra> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: Why do we not mark vulnerable ports DEPRECATED? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 18:55:26 -0000 On 08/30/2011 08:29, Chad Perrin wrote: > On Mon, Aug 29, 2011 at 10:48:31PM -0700, Doug Barton wrote: >> I'm doing some updates and came across mail/postfix-policyd-spf which >> relies on mail/libspf2-10. The latter had a vuxml entry added on >> 2008-10-27. So my question is, why has mail/libspf2-10 been allowed to >> remain in the tree vulnerable for almost 3 years? >> >> Wouldn't it make more sense to mark vulnerable ports DEPRECATED >> immediately with a short expiration? When they get fixed they get >> un-deprecated. If they don't, they get removed. Can someone explain why >> this would be a bad idea? > > Might that not interfere with the process of getting a new maintainer for > a popular port when its previous maintainer has been lax (or hit by a > bus)? Sorry if I'm being dense, but I'm not seeing the connection. Can you elaborate? Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 19:23:16 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2A5B1065672 for ; Tue, 30 Aug 2011 19:23:16 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 9DC2E8FC08 for ; Tue, 30 Aug 2011 19:23:16 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id EF51028424; Tue, 30 Aug 2011 21:05:54 +0200 (CEST) Received: from [192.168.1.2] (ip-86-49-61-235.net.upcbroadband.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id BB90F28423; Tue, 30 Aug 2011 21:05:53 +0200 (CEST) Message-ID: <4E5D3491.6000903@quip.cz> Date: Tue, 30 Aug 2011 21:05:53 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: Matthias Andree References: <4E5D1288.9010104@quip.cz> <4E5D1A50.10406@FreeBSD.org> In-Reply-To: <4E5D1A50.10406@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: FreeBSD Port: openvpn-2.2.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 19:23:17 -0000 Matthias Andree wrote: > Am 30.08.2011 18:40, schrieb Miroslav Lachman: >> Hi, [...] >> So I have a question - why the rc script is not using required_modules >> variable from /etc/rc.subr which is there exactly for this purpose? > > Miroslav, > > thanks for your required_modules suggestion. The script dates back to > 2005, when required_modules didn't exist (it was merged to a stable > version in August 2007). > > I have fixed the openvpn20 and openvpn ports. Revisions 2.2.1_1 and > 2.0.9_2 (respectively) have the fix. > > Thanks for the report and suggestion! Thank you for your quick response and fix of the issue! Miroslav Lachman From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 19:33:05 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1ED9106566B for ; Tue, 30 Aug 2011 19:33:05 +0000 (UTC) (envelope-from ted@io-tx.com) Received: from io-tx.com (io-tx.com [209.198.147.18]) by mx1.freebsd.org (Postfix) with ESMTP id 739508FC13 for ; Tue, 30 Aug 2011 19:33:05 +0000 (UTC) Received: from io-tx.com (io-tx.com [209.198.147.18]) (authenticated bits=0) by io-tx.com (8.14.4/8.14.4) with ESMTP id p7UJ1IsG066990 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Aug 2011 14:01:18 -0500 (CDT) (envelope-from ted@io-tx.com) Date: Tue, 30 Aug 2011 14:01:18 -0500 (CDT) From: Ted Hatfield To: Matthias Andree In-Reply-To: <4E5D26E2.7040300@gmx.de> Message-ID: References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> <20110830111152.GF28186@home.opsec.eu> <4E5CD28A.1080809@FreeBSD.org> <20110830122726.GG28186@home.opsec.eu> <4E5D0856.8080505@FreeBSD.org> <20110830163933.GC17573@lonesome.com> <4E5D216C.6070801@FreeBSD.org> <20110830175740.GA19289@lonesome.com> <4E5D26E2.7040300@gmx.de> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: clamav-milter 0.97.1 at io-tx.com X-Virus-Status: Clean Cc: freebsd-ports@freebsd.org Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 19:33:05 -0000 On Tue, 30 Aug 2011, Matthias Andree wrote: > Am 30.08.2011 19:57, schrieb Mark Linimon: >> On Tue, Aug 30, 2011 at 07:44:12PM +0200, Matthias Andree wrote: >>> It only warns, it does not prevent fresh installs on systems that don't >>> have the same port/package already installed. >> >> "code, not policy" ... ? > > Well... is _is_ policy and meant as such. We make decisions for ports > users all the time, and this is no exception. If procmail has no ongoing security issues and it compiles and installs with no problems what's the reasoning behind removing it from the ports tree? As far as I can see the reasoning advocated at this time is that procmail hasn't been in active development since 2001. Shouldn't that be seen as a sign of stability. I'm not a software developer so maybe I'm missing something obvious about this situation. Feel free to educate/convice me that I should make the effort to switch from procmail to maildrop. I've been using procmail now for 16 years and I'm very happy with it's performance. Moving to maildrop would be a significant amount of effort for both me and my users. Ted Hatfield From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 20:07:32 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C6C3106564A; Tue, 30 Aug 2011 20:07:32 +0000 (UTC) (envelope-from glarkin@FreeBSD.org) Received: from mail1.sourcehosting.net (mail1.sourcehosting.net [74.205.51.45]) by mx1.freebsd.org (Postfix) with ESMTP id 5FDA78FC17; Tue, 30 Aug 2011 20:07:32 +0000 (UTC) Received: from 68-189-245-235.dhcp.oxfr.ma.charter.com ([68.189.245.235] helo=cube.entropy.prv) by mail1.sourcehosting.net with esmtp (Exim 4.73 (FreeBSD)) (envelope-from ) id 1QyUa8-0005og-JW; Tue, 30 Aug 2011 16:06:55 -0400 Received: from v104.entropy.prv (v104.entropy.prv [192.168.1.104]) by cube.entropy.prv (Postfix) with ESMTP id CBB965217CD5; Tue, 30 Aug 2011 16:07:24 -0400 (EDT) Message-ID: <4E5D42FC.6060600@FreeBSD.org> Date: Tue, 30 Aug 2011 16:07:24 -0400 From: Greg Larkin Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.20) Gecko/20110804 Lightning/1.0b2 Thunderbird/3.1.12 MIME-Version: 1.0 To: Ruslan Mahmatkhanov References: <4E5CE015.70803@FreeBSD.org> <4E5CE7BB.8050808@yandex.ru> <4E5CEC1E.5010209@FreeBSD.org> <4E5CF2FF.5080302@yandex.ru> In-Reply-To: <4E5CF2FF.5080302@yandex.ru> X-Enigmail-Version: 1.1.1 OpenPGP: id=1C940290 X-SA-Exim-Connect-IP: 68.189.245.235 X-SA-Exim-Mail-From: glarkin@FreeBSD.org X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail1.sourcehosting.net X-Spam-Level: *** X-Spam-Status: No, score=3.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RCVD_IN_RP_RNBL, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC, TVD_RCVD_IP autolearn=no version=3.3.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.sourcehosting.net) Cc: FreeBSD Ports Mailing List , miwi@FreeBSD.org Subject: Re: Python min version bumped from 2.4+ to 2.5+ X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: glarkin@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 20:07:32 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 8/30/11 10:26 AM, Ruslan Mahmatkhanov wrote: > Greg Larkin wrote on 30.08.2011 17:56: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 8/30/11 9:38 AM, Ruslan Mahmatkhanov wrote: >>> Greg Larkin wrote on 30.08.2011 17:05: >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA1 >>>> >>>> Hi Martin, >>>> >>>> I have a question about a commit you made in February 2011: >>>> http://www.freshports.org/commit.php?message_id=201102250750.p1P7ofDg016541@repoman.freebsd.org&files=yes >>>> >>>> >>>> >>>> Part of the commit changed: >>>> >>>> USE_PYTHON= 2.4+ >>>> >>>> to >>>> >>>> USE_PYTHON= 2.5+ >>>> >>>> Was there a specific reason for doing so? I am running various >>>> tinderbox builds to check on port usage of the USE_PYTHON variable, and >>>> I noticed that devel/py-setuptools no longer builds if Python 2.4 is >>>> selected. >>>> >>>> I'd like to restore that capability, but before I send a PR, I >>>> wanted to >>>> check with you first. >>>> >>>> Thank you, >>>> Greg >>>> - -- >>>> Greg Larkin >>>> >>>> http://www.FreeBSD.org/ - The Power To Serve >>>> http://www.sourcehosting.net/ - Ready. Set. Code. >>>> http://twitter.com/cpucycle/ - Follow you, follow me >>> >>> I'm sorry for sail in, but i think that the reason is that python24 is >>> reached it's EOL long time ago. Actually the only supported python >>> releases atm according to python.org are - 2.7.2 and 3.2.1, and >>> developers highly encourages the users to move to this versions. >>> >>> 2.5 and 2.6 are in security-fix-only mode, there will be no ANY releases >>> for this branches after October 2011 and October 2013 respectively, >>> while 2.4 does not get security-fixes even. >>> >>> There is also this answer from Martin in this pr: >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/155526: >>> >>> python24 goes to the end of month, this port is on the todo for removal >>> >> >> Hi Ruslan, > > Hi Greg > >> >> Ok, thank you for the explanation. Shall I mark python24 for removal >> from the tree or file a PR for python@ to do it? > > It's not so easy actually, since we have many ports in the tree that > still depend on 2.4 (notably all that zope/plone stuff) and i believe it > was the reason why python24 still not be removed in the first place. > I do some work about eliminating python24 usage in the tree (yesterdays > py-pysqlite2x stuff - one of it), but it's not that fast. I also working > on porting zope2.13/plone4 (that supports python 2.6 and 2.7) and i'm > planing to finish it this weekend after proper testing. After that we > can deprecate/remove existing zope/plone (not longer supported upstream). Ok, it's a bigger job than I realized! > >> >> FYI, I have been running tinderbox builds with PYTHON_VERSION and >> PYTHON_DEFAULT_VERSION set to python2.4, python2.5, etc. to find out if >> ports with USE_PYTHON=yes need to be constrained a bit more. > > Yes, there is a lot of work. We have USE_PYTHON with bogus values like > 1.5+, 1.6+, 2.0+ etc :). And most of python ports will not work with > python3x so they should be constrained with -2.7 too. Do you think it's helpful then to run these builds with different Python versions enforced? I thought that getting the version ranges in the USE_PYTHON variable tightened up might help reduce the number of folks who run into build problems. I would like to do the same thing with Perl, GCC, and others. > >> I figured that python2.4 was supported since it was still in the tree >> and wasn't marked for removal yet, but I admin that I didn't check >> python.org for confirmation. > > As i already stated, i believe it's still there because there is > dependent ports. And as far i know in linux world noone shipping > python24 this days. Even RHEL/CentOS finally switched to 2.6.5 in their > 6.x branches. > >> >> Regards, >> Greg >> - -- >> Greg Larkin >> >> http://www.FreeBSD.org/ - The Power To Serve >> http://www.sourcehosting.net/ - Ready. Set. Code. >> http://twitter.com/cpucycle/ - Follow you, follow me > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5dQvsACgkQ0sRouByUApDH2wCgjulXl1vUHOGO4ubs4rZKLTlQ kMMAoLKBSArHGQkCT75iBQuLUQmsDuXb =i3ak -----END PGP SIGNATURE----- From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 20:25:57 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD30E106564A; Tue, 30 Aug 2011 20:25:57 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward13.mail.yandex.net (forward13.mail.yandex.net [IPv6:2a02:6b8:0:801::3]) by mx1.freebsd.org (Postfix) with ESMTP id DE6CB8FC15; Tue, 30 Aug 2011 20:25:56 +0000 (UTC) Received: from smtp14.mail.yandex.net (smtp14.mail.yandex.net [95.108.131.192]) by forward13.mail.yandex.net (Yandex) with ESMTP id 5389C142BC0; Wed, 31 Aug 2011 00:25:55 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314735955; bh=Tqv7kmatW7urwwK72Mu9aPz0dj2lB9KqEiPW3QOoVc4=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=u3cwfAojs6p9sGGYgaLd6Y1EN0pGV7rsPN1Bf3jkwEkGbUS5bEOMLoNw49GzISjno TpMwWXjmv7tMOQHXOw9x/njkQvYI1oFwtVsv3jMNi/j0GVU+WRtTyud/tJ4ICJeSWL kb1MYeSTzlb5NdrMJJX2E2sgn6xLEQUa9q7aevzc= Received: from smtp14.mail.yandex.net (localhost [127.0.0.1]) by smtp14.mail.yandex.net (Yandex) with ESMTP id 356FE1B603AE; Wed, 31 Aug 2011 00:25:55 +0400 (MSD) Received: from unknown (unknown [213.138.88.133]) by smtp14.mail.yandex.net (nwsmtp/Yandex) with ESMTP id PsUWE8Di; Wed, 31 Aug 2011 00:25:55 +0400 X-Yandex-Spam: 1 Message-ID: <4E5D4750.2010507@yandex.ru> Date: Wed, 31 Aug 2011 00:25:52 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: glarkin@FreeBSD.org References: <4E5CE015.70803@FreeBSD.org> <4E5CE7BB.8050808@yandex.ru> <4E5CEC1E.5010209@FreeBSD.org> <4E5CF2FF.5080302@yandex.ru> <4E5D42FC.6060600@FreeBSD.org> In-Reply-To: <4E5D42FC.6060600@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports Mailing List , miwi@FreeBSD.org Subject: Re: Python min version bumped from 2.4+ to 2.5+ X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 20:25:57 -0000 Greg Larkin wrote on 31.08.2011 00:07: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 8/30/11 10:26 AM, Ruslan Mahmatkhanov wrote: >> Greg Larkin wrote on 30.08.2011 17:56: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On 8/30/11 9:38 AM, Ruslan Mahmatkhanov wrote: >>>> Greg Larkin wrote on 30.08.2011 17:05: >>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>> Hash: SHA1 >>>>> >>>>> Hi Martin, >>>>> >>>>> I have a question about a commit you made in February 2011: >>>>> http://www.freshports.org/commit.php?message_id=201102250750.p1P7ofDg016541@repoman.freebsd.org&files=yes >>>>> >>>>> >>>>> >>>>> Part of the commit changed: >>>>> >>>>> USE_PYTHON= 2.4+ >>>>> >>>>> to >>>>> >>>>> USE_PYTHON= 2.5+ >>>>> >>>>> Was there a specific reason for doing so? I am running various >>>>> tinderbox builds to check on port usage of the USE_PYTHON variable, and >>>>> I noticed that devel/py-setuptools no longer builds if Python 2.4 is >>>>> selected. >>>>> >>>>> I'd like to restore that capability, but before I send a PR, I >>>>> wanted to >>>>> check with you first. >>>>> >>>>> Thank you, >>>>> Greg >>>>> - -- >>>>> Greg Larkin >>>>> >>>>> http://www.FreeBSD.org/ - The Power To Serve >>>>> http://www.sourcehosting.net/ - Ready. Set. Code. >>>>> http://twitter.com/cpucycle/ - Follow you, follow me >>>> >>>> I'm sorry for sail in, but i think that the reason is that python24 is >>>> reached it's EOL long time ago. Actually the only supported python >>>> releases atm according to python.org are - 2.7.2 and 3.2.1, and >>>> developers highly encourages the users to move to this versions. >>>> >>>> 2.5 and 2.6 are in security-fix-only mode, there will be no ANY releases >>>> for this branches after October 2011 and October 2013 respectively, >>>> while 2.4 does not get security-fixes even. >>>> >>>> There is also this answer from Martin in this pr: >>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/155526: >>>> >>>> python24 goes to the end of month, this port is on the todo for removal >>>> >>> >>> Hi Ruslan, >> >> Hi Greg >> >>> >>> Ok, thank you for the explanation. Shall I mark python24 for removal >>> from the tree or file a PR for python@ to do it? >> >> It's not so easy actually, since we have many ports in the tree that >> still depend on 2.4 (notably all that zope/plone stuff) and i believe it >> was the reason why python24 still not be removed in the first place. >> I do some work about eliminating python24 usage in the tree (yesterdays >> py-pysqlite2x stuff - one of it), but it's not that fast. I also working >> on porting zope2.13/plone4 (that supports python 2.6 and 2.7) and i'm >> planing to finish it this weekend after proper testing. After that we >> can deprecate/remove existing zope/plone (not longer supported upstream). > > Ok, it's a bigger job than I realized! > >> >>> >>> FYI, I have been running tinderbox builds with PYTHON_VERSION and >>> PYTHON_DEFAULT_VERSION set to python2.4, python2.5, etc. to find out if >>> ports with USE_PYTHON=yes need to be constrained a bit more. >> >> Yes, there is a lot of work. We have USE_PYTHON with bogus values like >> 1.5+, 1.6+, 2.0+ etc :). And most of python ports will not work with >> python3x so they should be constrained with -2.7 too. > > Do you think it's helpful then to run these builds with different Python > versions enforced? I thought that getting the version ranges in the > USE_PYTHON variable tightened up might help reduce the number of folks > who run into build problems. I would like to do the same thing with > Perl, GCC, and others. I, personally, believe that this almost can't help to identify version-specific problems, since commonly there is almost no build problems on different python versions (it's rarely when setup.py actually checking which python version it was run with). The problems arises on runtime stage, when apps starting to import modules, that may not exist in this particular python version or that installed by missing dependencies, etc. Such problems may be identified only with manual checking/greping/app docs reading. But this is just my point. You'd better to ask Martin - he is committer that skilled with python stuff in ports, and i'm not proper person to take responsibility for decisions like that :). I just can to sound my point on this. However, it definitely will help to identify gcc version-specific build problems. >> >>> I figured that python2.4 was supported since it was still in the tree >>> and wasn't marked for removal yet, but I admin that I didn't check >>> python.org for confirmation. >> >> As i already stated, i believe it's still there because there is >> dependent ports. And as far i know in linux world noone shipping >> python24 this days. Even RHEL/CentOS finally switched to 2.6.5 in their >> 6.x branches. >> >>> >>> Regards, >>> Greg >>> - -- >>> Greg Larkin >>> >>> http://www.FreeBSD.org/ - The Power To Serve >>> http://www.sourcehosting.net/ - Ready. Set. Code. >>> http://twitter.com/cpucycle/ - Follow you, follow me -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 20:45:08 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EBB51065674 for ; Tue, 30 Aug 2011 20:45:08 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward9.mail.yandex.net (forward9.mail.yandex.net [77.88.61.48]) by mx1.freebsd.org (Postfix) with ESMTP id C08088FC0A for ; Tue, 30 Aug 2011 20:45:03 +0000 (UTC) Received: from smtp8.mail.yandex.net (smtp8.mail.yandex.net [77.88.61.54]) by forward9.mail.yandex.net (Yandex) with ESMTP id E1AE5CE2438; Wed, 31 Aug 2011 00:45:01 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314737101; bh=qrVmjvoInzQcKFVo0S2avz1eeT4RcJiFH95ixoph/4M=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=f4bEjJe/99GqA6EJrEI9tPOOS1GdLlH7nPfscnxhwNtFGQ2WORWCnkbZzYB8cmso/ lowBF8kjjdxhAHoRtECf6buvPASQ4ohcZHCv5o3rq6a9XVKs6wCjKYCPF5IsMAdn9C Tr+1Xt14+Dq+hKVhhufvIEpMPrhiCfjGdotIUWAc= Received: from smtp8.mail.yandex.net (localhost [127.0.0.1]) by smtp8.mail.yandex.net (Yandex) with ESMTP id C46271B60344; Wed, 31 Aug 2011 00:45:01 +0400 (MSD) Received: from unknown (unknown [213.138.88.133]) by smtp8.mail.yandex.net (nwsmtp/Yandex) with ESMTP id j1amF6u9; Wed, 31 Aug 2011 00:45:01 +0400 X-Yandex-Spam: 1 Message-ID: <4E5D4BCB.80008@yandex.ru> Date: Wed, 31 Aug 2011 00:44:59 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: Koop Mast References: <201108240538.50514.lumiwa@gmail.com> <4E54D63B.3050900@yandex.ru> <1314188442.1830.7.camel@crashalot.rainbow-runner.nl> In-Reply-To: <1314188442.1830.7.camel@crashalot.rainbow-runner.nl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: ajtiM , freebsd-ports@freebsd.org Subject: gimp-gmic-plugin unbreak (Was: Re: libnotify) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 20:45:08 -0000 Koop Mast wrote on 24.08.2011 16:20: > On Wed, 2011-08-24 at 14:45 +0400, Ruslan Mahmatkhanov wrote: >> ajtiM wrote on 24.08.2011 14:38: >> >>> Stop in /usr/ports/graphics/gimp-gmic-plugin. >>> *** Error code 1 >>> >>> Stop in /usr/ports/graphics/gimp-gmic-plugin. >>> >>> ===>>> make failed for graphics/gimp-gmic-plugin >>> ===>>> Aborting update >> >> Too bad. I did not deal with recent updates yet, so >> i'll try to realize what is wrong some time later this week. >> > > This build failure seems to be caused by the recent opencv update to > 2.3.1. > > -Koop I just disabled OpenCV completely for now to unbreak the port: http://www.freebsd.org/cgi/query-pr.cgi?pr=160321 Anybody with free hands - please, commit. -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 21:12:47 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78FCC106566B for ; Tue, 30 Aug 2011 21:12:47 +0000 (UTC) (envelope-from code@apotheon.net) Received: from oproxy1-pub.bluehost.com (oproxy1.bluehost.com [IPv6:2605:dc00:100:2::a1]) by mx1.freebsd.org (Postfix) with SMTP id 3A12D8FC12 for ; Tue, 30 Aug 2011 21:12:47 +0000 (UTC) Received: (qmail 23297 invoked by uid 0); 30 Aug 2011 21:12:46 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by oproxy1.bluehost.com with SMTP; 30 Aug 2011 21:12:46 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.net; s=default; h=In-Reply-To:Content-Type:Mime-Version:References:Message-ID:Subject:To:From:Date; bh=qzaHIRegYHXg697RHZjkpXhKdZwdewW1/28+PtmalhY=; b=loCrq4ciGs6J29hMYuQhFtQcDQtU8EFj2GA3q158fj1UX3aVhg4iB0bNEA7OPemDvESP7lKyRrEqlo4DKQkW+HZM/1v9c+mHezlwUA5ARYRF+nOFW4fa7n+FTRJ27O4k; Received: from c-24-8-180-234.hsd1.co.comcast.net ([24.8.180.234] helo=kukaburra.hydra) by box543.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1QyVbx-0006tj-3p for freebsd-ports@FreeBSD.org; Tue, 30 Aug 2011 15:12:46 -0600 Received: by kukaburra.hydra (sSMTP sendmail emulation); Tue, 30 Aug 2011 14:54:19 -0600 Date: Tue, 30 Aug 2011 14:54:19 -0600 From: Chad Perrin To: "freebsd-ports@FreeBSD.org" Message-ID: <20110830205419.GA70668@guilt.hydra> Mail-Followup-To: "freebsd-ports@FreeBSD.org" References: <4E5C79AF.6000408@FreeBSD.org> <20110830152920.GB69850@guilt.hydra> <4E5D321D.9020209@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline In-Reply-To: <4E5D321D.9020209@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.org} {sentby:smtp auth 24.8.180.234 authed with ren@apotheon.org} Cc: Subject: Re: Why do we not mark vulnerable ports DEPRECATED? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 21:12:47 -0000 --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 30, 2011 at 11:55:25AM -0700, Doug Barton wrote: > On 08/30/2011 08:29, Chad Perrin wrote: > >=20 > > Might that not interfere with the process of getting a new maintainer f= or > > a popular port when its previous maintainer has been lax (or hit by a > > bus)? >=20 > Sorry if I'm being dense, but I'm not seeing the connection. Can you > elaborate? I'll put it another way: Wouldn't it be easier for a new maintainer to pick up maintenance of a port if (s)he doesn't have to start over from scratch? --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk5dTfsACgkQ9mn/Pj01uKUpRgCZAcvnMShlnKh0bIsuFj46XIq7 cI4AoI9QvbPgzDLYo4yym0gg7y/+DoA2 =Secg -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/-- From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 21:31:15 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27A0F106564A for ; Tue, 30 Aug 2011 21:31:15 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id E74C08FC0A for ; Tue, 30 Aug 2011 21:31:14 +0000 (UTC) Received: by iadx2 with SMTP id x2so56772iad.13 for ; Tue, 30 Aug 2011 14:31:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=4XrlMdDvl1CAqJ982AYvATliEtgaWp3B5K2oNfXEHQc=; b=tTC0IPCi2BCV2UdP3Zk8nq5+j1u3xXl4qDUbkS9BOqBc81FgVCMirKgsB7+BpXzFAx koMi0RjrCvevo/xbg88pNahH8ymO3xwT2/6PZ1zyCeRbNiorUx2aYRBIITRs5TJ2onpw J7JxHXHLzBZVSAzkdKhnsXMZFduqjetMWa0cs= MIME-Version: 1.0 Received: by 10.231.66.85 with SMTP id m21mr14052278ibi.53.1314739874557; Tue, 30 Aug 2011 14:31:14 -0700 (PDT) Received: by 10.231.61.148 with HTTP; Tue, 30 Aug 2011 14:31:14 -0700 (PDT) Received: by 10.231.61.148 with HTTP; Tue, 30 Aug 2011 14:31:14 -0700 (PDT) In-Reply-To: <20110830205419.GA70668@guilt.hydra> References: <4E5C79AF.6000408@FreeBSD.org> <20110830152920.GB69850@guilt.hydra> <4E5D321D.9020209@FreeBSD.org> <20110830205419.GA70668@guilt.hydra> Date: Tue, 30 Aug 2011 22:31:14 +0100 Message-ID: From: Chris Rees To: "freebsd-ports@FreeBSD.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Why do we not mark vulnerable ports DEPRECATED? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 21:31:15 -0000 On 30 Aug 2011 22:13, "Chad Perrin" wrote: > > On Tue, Aug 30, 2011 at 11:55:25AM -0700, Doug Barton wrote: > > On 08/30/2011 08:29, Chad Perrin wrote: > > > > > > Might that not interfere with the process of getting a new maintainer for > > > a popular port when its previous maintainer has been lax (or hit by a > > > bus)? > > > > Sorry if I'm being dense, but I'm not seeing the connection. Can you > > elaborate? > > I'll put it another way: > > Wouldn't it be easier for a new maintainer to pick up maintenance of a > port if (s)he doesn't have to start over from scratch? > That's what the cvs Attic is for. Stuff doesn't disappear! Chris From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 21:45:28 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE805106566B for ; Tue, 30 Aug 2011 21:45:28 +0000 (UTC) (envelope-from beech@freebsd.org) Received: from bsdevel2.freebsdnorth.com (unknown [IPv6:2001:470:7:d77::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7D3248FC15 for ; Tue, 30 Aug 2011 21:45:28 +0000 (UTC) Received: from maximum3.maximumdata.biz (akbeech-2-pt.tunnel.tserv14.sea1.ipv6.he.net [IPv6:2001:470:a:2e9::2]) by bsdevel2.freebsdnorth.com (Postfix) with ESMTP id 5E0AEC3B0A; Mon, 29 Aug 2011 21:40:48 +0000 (UTC) From: Beech Rintoul Organization: FreeBSD To: freebsd-ports@freebsd.org Date: Tue, 30 Aug 2011 13:45:25 -0800 User-Agent: KMail/1.13.7 (FreeBSD/9.0-BETA2; KDE/4.6.5; i386; ; ) References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5D26E2.7040300@gmx.de> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3649567.VCpAAKgml0"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201108301345.25661.beech@freebsd.org> Cc: Matthias Andree , Ted Hatfield Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 21:45:28 -0000 --nextPart3649567.VCpAAKgml0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Tuesday 30 August 2011 11:01:18 Ted Hatfield wrote: > On Tue, 30 Aug 2011, Matthias Andree wrote: > > Am 30.08.2011 19:57, schrieb Mark Linimon: > >> On Tue, Aug 30, 2011 at 07:44:12PM +0200, Matthias Andree wrote: > >>> It only warns, it does not prevent fresh installs on systems that don= 't > >>> have the same port/package already installed. > >>=20 > >> "code, not policy" ... ? > >=20 > > Well... is _is_ policy and meant as such. We make decisions for ports > > users all the time, and this is no exception. >=20 > If procmail has no ongoing security issues and it compiles and installs > with no problems what's the reasoning behind removing it from the ports > tree? >=20 > As far as I can see the reasoning advocated at this time is that > procmail hasn't been in active development since 2001. Shouldn't that > be seen as a sign of stability. >=20 > I'm not a software developer so maybe I'm missing something obvious > about this situation. Feel free to educate/convice me that I should > make the effort to switch from procmail to maildrop. >=20 > I've been using procmail now for 16 years and I'm very happy with it's > performance. Moving to maildrop would be a significant amount of effort > for both me and my users. >=20 > Ted Hatfield I second that, I also have it installed in several places and haven't had a= ny=20 problems. I don't want to have to move to another app just because someone= =20 feels like deprecating a mature port. I think the old addage "if it ain't=20 broke" applies here. Beech =2D-=20 =2D------------------------------------------------------------------------= =2D------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/8.2R/announce.html =2D------------------------------------------------------------------------= =2D------------- --nextPart3649567.VCpAAKgml0 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEABECAAYFAk5dWfUACgkQFrTqt+y/3EQatACeOUzutUqiiDHoMRTHFDV9Z+Bp sqEAoIGvAcqj9WW76bgpMU3PBcnYLQLw =vOze -----END PGP SIGNATURE----- --nextPart3649567.VCpAAKgml0-- From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 22:39:31 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CFC5106566C; Tue, 30 Aug 2011 22:39:31 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 4896E8FC14; Tue, 30 Aug 2011 22:39:31 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p7UMdU4g013272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Aug 2011 15:39:30 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p7UMdUGg013271; Tue, 30 Aug 2011 15:39:30 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA21779; Tue, 30 Aug 11 15:28:15 PDT Date: Tue, 30 Aug 2011 22:28:11 -0700 From: perryh@pluto.rain.com To: mandree@freebsd.org Message-Id: <4e5dc66b.yG7fFB738rgdzrhe%perryh@pluto.rain.com> References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> <20110830111152.GF28186@home.opsec.eu> <4E5CD28A.1080809@FreeBSD.org> <20110830122726.GG28186@home.opsec.eu> <4E5D0856.8080505@FreeBSD.org> In-Reply-To: <4E5D0856.8080505@FreeBSD.org> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 22:39:31 -0000 Matthias Andree wrote: > I understand that keeping unchanging software can sometimes be > necessary, if you're working around its quirks. > > At the same time I'd like to discourage new installations of dead > software so that it disappears over time, rather than haunt fresh > systems. > > How about if we added a new tag "OBSOLESCENT" or so that permits > building the software only if it's already installed but refuses > new installations? Of course there could be a switch to override > that, like TRYBROKEN that can override BROKEN= tags. > > I'm not sure if it's feasible for packages (but OBSOLESCENT could > imply "do not package") but for ports it would be possible. +1. This would also address the python 2.4 problem mentioned in another thread. BTW (if it is not already being done) it would be good for the -recursive targets to check for BROKEN, FORBIDDEN, OBSOLESCENT, (others?) in the dependencies _before_ starting the actual work, since the presence of a problematic dependency may well affect the user's decision to install/build/whatever the leaf port. From owner-freebsd-ports@FreeBSD.ORG Tue Aug 30 22:39:34 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAF07106566B; Tue, 30 Aug 2011 22:39:34 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id AED268FC16; Tue, 30 Aug 2011 22:39:34 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p7UMdVcp013282 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Aug 2011 15:39:33 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p7UMdVqS013281; Tue, 30 Aug 2011 15:39:31 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA21808; Tue, 30 Aug 11 15:29:07 PDT Date: Tue, 30 Aug 2011 22:29:03 -0700 From: perryh@pluto.rain.com To: ports@freebsd.org Message-Id: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: acm@freebsd.org, cwhiteh@onetel.com Subject: editors/zim X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 22:39:34 -0000 Forwarding to ports@, which seems more likely to yield an answer to this particular inquiry than questions@ Please keep the OP, who is probably not subscribed to ports@, in the Cc: list. ==================================================================== Date: Tue, 30 Aug 2011 13:52:12 +0100 From: Chris Whitehouse To: User Questions Subject: editors/zim Hi, I have a problem with Zim which I wrote to the author about he replied and said; "I'm afraid version 0.29 is no longer supported. This was the last version in the Perl branch, since we moved to Python there have been already 10 more releases. So please try the latest version (0.52)." Are there any plans to bump it to Python and a recent release? I emailed the maintainer a while back but got no response. thanks Chris From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 00:51:21 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09FBE106566B for ; Wed, 31 Aug 2011 00:51:21 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo102.cox.net (eastrmfepo102.cox.net [68.230.241.214]) by mx1.freebsd.org (Postfix) with ESMTP id A94FF8FC16 for ; Wed, 31 Aug 2011 00:51:20 +0000 (UTC) Received: from eastrmimpo02.cox.net ([68.1.16.120]) by eastrmfepo102.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20110831005120.GQAV3919.eastrmfepo102.cox.net@eastrmimpo02.cox.net> for ; Tue, 30 Aug 2011 20:51:20 -0400 Received: from serene.no-ip.org ([98.164.83.25]) by eastrmimpo02.cox.net with bizsmtp id SorK1h00P0YnB6A02orKJf; Tue, 30 Aug 2011 20:51:19 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020206.4E5D8587.0122,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=ax4i8a8snyEA9uWfgWYmXW+3D+RWNhitQWxcW0Jxd9c= c=1 sm=1 a=NHFOSxFzArsA:10 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=2vO5UZG1h46htWAnE/rx2g==:17 a=kviXuzpPAAAA:8 a=XNrl3o2TI6vkDnK6UNoA:9 a=CjuIK1q_8ugA:10 a=4vB-4DCPJfMA:10 a=2vO5UZG1h46htWAnE/rx2g==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from cox.net (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id p7V0pJJ3007276 for ; Tue, 30 Aug 2011 19:51:19 -0500 (CDT) (envelope-from conrads@cox.net) Date: Tue, 30 Aug 2011 19:51:14 -0500 From: "Conrad J. Sabatier" To: freebsd-ports@FreeBSD.org Message-ID: <20110830195114.56a8f255@cox.net> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: (maintainer question) Possible bug in cvs: cvs diff -uN: -N switch being ignored (disappearing, actually) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 00:51:21 -0000 Odd little problem here I'm noticing with cvs. When I do a "cvs diff -uN", for some reason the -N switch is being ignored. It vanishes completely in the header of the resulting output. I've been trying to rename one of my patch files to conform to portlint's recommendations, but unless I can get -N to work properly, this is a no-go. Whether I add 'cvs diff -uN' to my .cvsrc, or explicitly add it at the command line, makes no difference. For instance: [root@serene /usr/ports/net-p2p/lopster]# cvs diff -uN cvs diff: Diffing . Index: Makefile =================================================================== RCS file: /home/ncvs/ports/net-p2p/lopster/Makefile,v retrieving revision 1.44 diff -u -r1.44 Makefile ^ |__ What happened to -N? [snip remainder of diff output] Incidentally, this problem started before I upgraded two days ago from 9.0-BETA1 to 9.0-BETA1, so it's not OS version-related. Any idea what could be causing this and how to correct it? Is this a bug in cvs? Should I send-pr it? Thanks! -- Conrad J. Sabatier conrads@cox.net From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 01:59:50 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC3031065672; Wed, 31 Aug 2011 01:59:50 +0000 (UTC) (envelope-from miwi.freebsd@googlemail.com) Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by mx1.freebsd.org (Postfix) with ESMTP id 96B708FC08; Wed, 31 Aug 2011 01:59:50 +0000 (UTC) Received: by pzk33 with SMTP id 33so713639pzk.18 for ; Tue, 30 Aug 2011 18:59:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:x-mailer:from:subject:date:to; bh=FGfyVQVKiYnMD+WbidrQGYbYljDUhc0t+TUFdhnIovQ=; b=lhrsFGSTtleBnATwgeO5eHMAZPMp/HRbuZctSzNpd1xJfyC3NrVlb9TdzS9Xx3bbyv 5BSUrYpIR8eTAa16d8lFklMWZXjKDorULGT2w/PlCL45DCDcAo9mpcKIXu3y7o5aR73O magGO9pJFBmfpQBozOF2qCJjsUzFYJu4lIQOk= Received: by 10.68.66.167 with SMTP id g7mr111301pbt.31.1314754265121; Tue, 30 Aug 2011 18:31:05 -0700 (PDT) Received: from [10.14.189.179] ([113.210.253.39]) by mx.google.com with ESMTPS id u2sm26769964pbq.9.2011.08.30.18.31.00 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 30 Aug 2011 18:31:03 -0700 (PDT) References: <4E5CE015.70803@FreeBSD.org> <4E5CE7BB.8050808@yandex.ru> <4E5CEC1E.5010209@FreeBSD.org> In-Reply-To: <4E5CEC1E.5010209@FreeBSD.org> Mime-Version: 1.0 (1.0) Content-Type: text/plain; charset=us-ascii Message-Id: <6F11B9EB-86E5-4A65-90BF-256E101CC24D@googlemail.com> Content-Transfer-Encoding: quoted-printable X-Mailer: iPhone Mail (9A5302b) From: Martin Wilke Date: Wed, 31 Aug 2011 09:30:55 +0800 To: "glarkin@FreeBSD.org" Cc: FreeBSD Ports Mailing List , Ruslan Mahmatkhanov , "miwi@FreeBSD.org" Subject: Re: Python min version bumped from 2.4+ to 2.5+ X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 01:59:50 -0000 In fact if use use_python=3Dyes default is 27 we cant set python24 for remo= val yet because we have fix first all zope stuff. Am back to the game after Holiday Sent from my iPhone On Aug 30, 2011, at 21:56, Greg Larkin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > On 8/30/11 9:38 AM, Ruslan Mahmatkhanov wrote: >> Greg Larkin wrote on 30.08.2011 17:05: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>>=20 >>> Hi Martin, >>>=20 >>> I have a question about a commit you made in February 2011: >>> http://www.freshports.org/commit.php?message_id=3D201102250750.p1P7ofDg0= 16541@repoman.freebsd.org&files=3Dyes >>>=20 >>>=20 >>> Part of the commit changed: >>>=20 >>> USE_PYTHON=3D 2.4+ >>>=20 >>> to >>>=20 >>> USE_PYTHON=3D 2.5+ >>>=20 >>> Was there a specific reason for doing so? I am running various >>> tinderbox builds to check on port usage of the USE_PYTHON variable, and >>> I noticed that devel/py-setuptools no longer builds if Python 2.4 is >>> selected. >>>=20 >>> I'd like to restore that capability, but before I send a PR, I wanted to= >>> check with you first. >>>=20 >>> Thank you, >>> Greg >>> - --=20 >>> Greg Larkin >>>=20 >>> http://www.FreeBSD.org/ - The Power To Serve >>> http://www.sourcehosting.net/ - Ready. Set. Code. >>> http://twitter.com/cpucycle/ - Follow you, follow me >>=20 >> I'm sorry for sail in, but i think that the reason is that python24 is >> reached it's EOL long time ago. Actually the only supported python >> releases atm according to python.org are - 2.7.2 and 3.2.1, and >> developers highly encourages the users to move to this versions. >>=20 >> 2.5 and 2.6 are in security-fix-only mode, there will be no ANY releases >> for this branches after October 2011 and October 2013 respectively, >> while 2.4 does not get security-fixes even. >>=20 >> There is also this answer from Martin in this pr: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/155526: >>=20 >> python24 goes to the end of month, this port is on the todo for removal >>=20 >=20 > Hi Ruslan, >=20 > Ok, thank you for the explanation. Shall I mark python24 for removal > from the tree or file a PR for python@ to do it? >=20 > FYI, I have been running tinderbox builds with PYTHON_VERSION and > PYTHON_DEFAULT_VERSION set to python2.4, python2.5, etc. to find out if > ports with USE_PYTHON=3Dyes need to be constrained a bit more. >=20 > I figured that python2.4 was supported since it was still in the tree > and wasn't marked for removal yet, but I admin that I didn't check > python.org for confirmation. >=20 > Regards, > Greg > - --=20 > Greg Larkin >=20 > http://www.FreeBSD.org/ - The Power To Serve > http://www.sourcehosting.net/ - Ready. Set. Code. > http://twitter.com/cpucycle/ - Follow you, follow me > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >=20 > iEYEARECAAYFAk5c7B4ACgkQ0sRouByUApAZOQCcC0YgAzDxDj78I9u35+H53fur > be8AmQFjWrGJ/xmjYpPp6ZkKB+ejDfq9 > =3DtK4y > -----END PGP SIGNATURE----- From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 02:14:52 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44E37106564A for ; Wed, 31 Aug 2011 02:14:52 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo102.cox.net (eastrmfepo102.cox.net [68.230.241.214]) by mx1.freebsd.org (Postfix) with ESMTP id DFBA68FC0C for ; Wed, 31 Aug 2011 02:14:51 +0000 (UTC) Received: from eastrmimpo02.cox.net ([68.1.16.120]) by eastrmfepo102.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20110831021446.JBYO3919.eastrmfepo102.cox.net@eastrmimpo02.cox.net> for ; Tue, 30 Aug 2011 22:14:46 -0400 Received: from serene.no-ip.org ([98.164.83.25]) by eastrmimpo02.cox.net with bizsmtp id SqEl1h00J0YnB6A02qEl3u; Tue, 30 Aug 2011 22:14:46 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A02020B.4E5D9916.0004,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=ax4i8a8snyEA9uWfgWYmXW+3D+RWNhitQWxcW0Jxd9c= c=1 sm=1 a=-pwuJQO3sf0A:10 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=2vO5UZG1h46htWAnE/rx2g==:17 a=kviXuzpPAAAA:8 a=l-gom1c5dNioWGX7s6AA:9 a=CjuIK1q_8ugA:10 a=4vB-4DCPJfMA:10 a=2vO5UZG1h46htWAnE/rx2g==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from cox.net (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id p7V2EjS3007719 for ; Tue, 30 Aug 2011 21:14:45 -0500 (CDT) (envelope-from conrads@cox.net) Date: Tue, 30 Aug 2011 21:14:40 -0500 From: "Conrad J. Sabatier" To: freebsd-ports@freebsd.org Message-ID: <20110830211440.1f53465d@cox.net> In-Reply-To: <20110830195114.56a8f255@cox.net> References: <20110830195114.56a8f255@cox.net> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: (maintainer question) Possible bug in cvs: cvs diff -uN: -N switch being ignored (disappearing, actually) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 02:14:52 -0000 On Tue, 30 Aug 2011 19:51:14 -0500 "Conrad J. Sabatier" wrote: > Incidentally, this problem started before I upgraded two days ago from > 9.0-BETA1 to 9.0-BETA1, so it's not OS version-related. ^ |__ Errr, I meant "BETA2, of course :-) -- Conrad J. Sabatier conrads@cox.net From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 05:43:50 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FAFE106564A for ; Wed, 31 Aug 2011 05:43:50 +0000 (UTC) (envelope-from ade@FreeBSD.org) Received: from panix.lovett.com (panix.lovett.com [166.84.7.128]) by mx1.freebsd.org (Postfix) with ESMTP id 08BD28FC0A for ; Wed, 31 Aug 2011 05:43:49 +0000 (UTC) Received: from r74-192-180-219.htvlcmta01.hnvitx.tl.dh.suddenlink.net ([74.192.180.219] helo=lab.lovett.com) by panix.lovett.com with esmtpa (Exim 4.76 (FreeBSD)) (envelope-from ) id 1QydaW-000KGV-Su for freebsd-ports@freebsd.org; Wed, 31 Aug 2011 05:43:49 +0000 Date: Wed, 31 Aug 2011 00:43:37 -0500 From: Ade Lovett To: freebsd-ports@freebsd.org Message-ID: <20110831004337.2deb368e@lab.lovett.com> In-Reply-To: <4E5D0A77.3070304@FreeBSD.org> References: <201108301524.p7UFOc6Q008169@fire.js.berklix.net> <4E5D0A77.3070304@FreeBSD.org> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 05:43:50 -0000 On Tue, 30 Aug 2011 18:06:15 +0200 Matthias Andree wrote: > Once you have the necessary error handling in place in > your .procmailrc, a .mailfilter file of equal usefulness in maildrop > is shorter and more concise. 1. In the context of a FreeBSD port, there is absolutely nothing wrong with mail/procmail as it stands. That is to say, it compiles and runs on all supported OS releases and architectures. 2. I'd hazard a guess that procmail is used (with or without a view to it's "interesting" view of error handling) on a large number of systems. Whilst there have been recent, shall we say, discussions, on the viability of the ports tree, one should not expect to be punched into a nearby wall when attempting to lose such a piece of software when the issues, such as they are, are with the software itself, not the port. 3. Particularly when there's no magic tool to convert all the .procmailrc's out there to mail/whizzy-new-thing. 4. Assuming for a minute that y'all are just on a deprecation kick, there's considerably more interesting low-hanging fruit. gtk1, qt3, kde3, gnome1, etc.. etc.. 5. Don't make me put RUN_DEPENDS= procmail:${PORTSDIR}/mail/procmail somewhere in the bowels of autotools ;) #3 is the important point. If you do want to send mail/procmail to the great bitbucket in the sky, then please provide that magic tool. I'm sure lots of folks will be willing to test it for you. -aDe From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 07:11:19 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF29A106564A; Wed, 31 Aug 2011 07:11:19 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward15.mail.yandex.net (forward15.mail.yandex.net [IPv6:2a02:6b8:0:801::5]) by mx1.freebsd.org (Postfix) with ESMTP id DEEDE8FC13; Wed, 31 Aug 2011 07:11:18 +0000 (UTC) Received: from smtp14.mail.yandex.net (smtp14.mail.yandex.net [95.108.131.192]) by forward15.mail.yandex.net (Yandex) with ESMTP id 402E69E2389; Wed, 31 Aug 2011 11:11:17 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314774677; bh=Qm4ClbhE6iNRKTGB6cMz6jg3pL4Ady7ognyd+cmza0Q=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=lz7EwAp5Oa2nse6NE8Tw1pD++aB7Ipg4bPbemc2Y9EtcmE93PBaqZz+DJMeygSXQ5 7g0s3+x8RuxFozXrklXRVsqAZsDlqL115P/U1OVGQQgWeYM0x4QnwisYq8aIK1xjnh yiX6dKV3sLrrpYz83ep4zLaPAEsm7qz6Z5FsyuAY= Received: from smtp14.mail.yandex.net (localhost [127.0.0.1]) by smtp14.mail.yandex.net (Yandex) with ESMTP id 21E6F1B603AB; Wed, 31 Aug 2011 11:11:17 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp14.mail.yandex.net (nwsmtp/Yandex) with ESMTP id BGUK0EhM; Wed, 31 Aug 2011 11:11:16 +0400 X-Yandex-Spam: 1 Message-ID: <4E5DDE91.80500@yandex.ru> Date: Wed, 31 Aug 2011 11:11:13 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: FreeBSD Ports Mailing List References: <4E4A8AB7.5080501@yandex.ru> <4E4C0048.5090509@yandex.ru> In-Reply-To: <4E4C0048.5090509@yandex.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Chris Rees , Palle Girgensohn Subject: Re: Some concerns about our postgresql and plpython ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 07:11:20 -0000 So... two weeks are now passed and i still see no objections from maintainer. Can please anybody commit? It will be terrible sad if work that took so much time and energy will remains unfinished. Thanks. Ruslan Mahmatkhanov wrote on 17.08.2011 21:54: > > So i split this up to three pr's as was suggested by Mark: > 1. Python pkg-plist fix for WITHOUT_THREADS case: > http://www.freebsd.org/cgi/query-pr.cgi?pr=159842 > 2. postgresql-plpython unbreak: > http://www.freebsd.org/cgi/query-pr.cgi?pr=159843 > 3. postgresql9x-client unbreak: > http://www.freebsd.org/cgi/query-pr.cgi?pr=159844 > > Palle (maintainer of postgresql ports) cc'ed. > > Thanks in advance for handling this. > > PS. I just found that the similar plist fix was submitted for python26 a > year ago: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/148406 > > > Ruslan Mahmatkhanov wrote on 16.08.2011 19:20: >> Hi there. >> >> We have databases/postgresql-plpython, that is marked as broken with >> this message: "Does not configure without threaded Python", but this is >> totally wrong - it actually does. I checked the internets and found >> this: [1] and [2]. People are actually had problems when building it >> WITH threaded python (that is built with threads support by default). >> Rebuilding python w/o threads support do the trick actually. But if you >> will try to build this port with threads-aware python, you'll get this >> error message: >> >> """ >> checking whether Python is compiled with thread support... yes >> configure: error: threaded Python not supported on this platform >> """ >> >> But the funny thing that it actually builds and works fine with threaded >> python too :). We just need to apply this patch to postgresqlXX-server's >> configure: >> >> - openbsd*|freebsd*) >> + openbsd*) >> >> And then there is no error: >> >> """ >> checking whether Python is compiled with thread support... yes >> checking for main in -lm... yes >> """ >> >> So what i did - i have tested the build and runtime of 8.4, 9.0, 9.1b3. >> both with threads-aware python and threadless python (version 2.7.2, >> runtime is tested only on 9-CURRENT, but with all the three PostgreSQL >> versions). >> And all of this configurations works well. For testing i'm used sample >> function (pymax.sql) from PosgreSQL manual and simple script >> (plpython.sh), that adds/removes and runs the function: >> >> """ >> [mrk@smeshariki2 plpython]> cat pymax.sql >> CREATE FUNCTION pymax (a integer, b integer) >> RETURNS integer >> AS $$ >> if a > b: >> return a >> return b >> $$ LANGUAGE plpythonu; >> """ >> >> """ >> [mrk@smeshariki2 plpython]> cat plpython.sh >> #!/bin/sh >> >> createlang -U pgsql plpythonu test >> psql -U pgsql test -f pymax.sql >> psql -U pgsql test -c "select pymax(1,2)" >> psql -U pgsql test -c "drop function pymax(a integer, b integer)" >> droplang -U pgsql plpythonu test >> """ >> >> To build databases/postgresql-plpython with PostgreSQL 9.1b3 i've used >> patch from [4] by Martin Neubauer , >> it is also included into my patch [3]. Updated regexp also working >> fine with 8.4 and 9.0. >> >> plpython module for 9.0 and 9.1 was renamed to plpython2.so, but there >> is also plpython.so symlink in 9.0 that points to plpython2.so. 9.1 also >> installs some extension files, so i fixed pkg-plists accordingly. >> >> Since 9.0 PostgreSQL guys use docbook for building all the >> documentation, including man-pages. They ever listed all the >> dependencies needed on FreeBSD to make it build. See [5]. But because >> our postgresql-client ports didn't include needed dependencies, their >> build are broken. In particular: >> >> postgresql91-client is broken on FreeBSD-8.2 >> postgresql90-client is broken on FreeBSD-7.4 >> postgresql91-client is broken on FreeBSD-7.4 >> >> So i have fixed this too by adding this deps to the ports. And i'm not >> see another solution. We need man-pages for postgresql9x-client, and >> man-pages needs all that docbook stuff. >> >> To make lang/python27 build without threads under tinderbox, i was >> forced to fix it's plist. Please see patch [6]. Probably similar patch >> should be applied against other python versions. >> >> The plpython port is unmantained, so please commit this anybody. >> Below are build logs of various configurations. >> >> Threads-aware python: >> --------------------- >> 8.2: >> http://happy-nation.by.ru/ports/tb/8.2/postgresql-plpython-8.4.8_1.log >> 8.2: >> http://happy-nation.by.ru/ports/tb/8.2/postgresql-plpython-9.0.4_1.log >> 8.2: >> http://happy-nation.by.ru/ports/tb/8.2/postgresql-plpython-9.1.b3_1.log >> 7.4: >> http://happy-nation.by.ru/ports/tb/7.4/postgresql-plpython-8.4.8_1.log >> 7.4: http://happy-nation.by.ru/ports/tb/7.4/postgresql-client-9.0.4_1.log >> 7.4: >> http://happy-nation.by.ru/ports/tb/7.4/postgresql-plpython-9.1.b3_1.log >> >> Threadless python: >> ------------------ >> 8.2: >> http://happy-nation.by.ru/ports/tb/8.2/postgresql-plpython-8.4.8_1-wo-threads.log >> >> >> 8.2: >> http://happy-nation.by.ru/ports/tb/8.2/postgresql-plpython-9.0.4_1-wo-threads.log >> >> >> 8.2: >> http://happy-nation.by.ru/ports/tb/8.2/postgresql-plpython-9.1.b3_1-wo-threads.log >> >> >> 7.4: >> http://happy-nation.by.ru/ports/tb/7.4/postgresql-plpython-8.4.8_1-wo-threads.log >> >> >> 7.4: >> http://happy-nation.by.ru/ports/tb/7.4/postgresql-plpython-9.0.4_1-wo-threads.log >> >> >> 7.4: >> http://happy-nation.by.ru/ports/tb/7.4/postgresql-plpython-9.1.b3_1-wo-threads.log >> >> >> >> To sum up what is included into patch [3]: >> - databases/postgresql-plpython no more marked as broken, since it >> builds both with threaded and threaless python on all supported >> FreeBSD versions with three major PostgreSQL branches >> - added configure patch for PostgreSQL 8.4, 9.0, 9.1 to make it able to >> build plpython threads-aware python >> - merge changed regexp to make plpython built with 9.1b3 from [4] >> - fix plists for postgresql9x-server/pkg-plist-plpython (plpython2.so >> and extensions) >> - fix build of postgresql9x-client (docbook related deps added) >> - portrevisions for -client and -plpython bumped >> >> I know that 8.2 and 8.3 are still supported branches, but i'm not much >> interested in them, so hadn't ever tried them, but believe that the same >> fixes applies. >> Please let me know if anybody actually need them, so i'll take a look >> at it in my spare time. >> >> Sorry for the long letter and my engrish :) >> >> [1] http://forums.freebsd.org/showthread.php?t=19472 >> [2] >> http://postgresql.1045698.n5.nabble.com/Threaded-python-on-FreeBSD-td1955052.html >> >> >> [3] http://happy-nation.by.ru/ports/postgresql-plpython-unbreak.diff.txt >> [4] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/159319 >> [5] http://www.postgresql.org/docs/9.0/static/docguide-toolsets.html >> [6] >> http://happy-nation.by.ru/ports/fix-python27-plist-without-threads.diff.txt -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 07:38:00 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDB32106564A for ; Wed, 31 Aug 2011 07:38:00 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo202.cox.net (eastrmfepo202.cox.net [68.230.241.217]) by mx1.freebsd.org (Postfix) with ESMTP id 8C4308FC0C for ; Wed, 31 Aug 2011 07:38:00 +0000 (UTC) Received: from eastrmimpo01.cox.net ([68.1.16.119]) by eastrmfepo202.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20110831073754.EEHB32466.eastrmfepo202.cox.net@eastrmimpo01.cox.net> for ; Wed, 31 Aug 2011 03:37:54 -0400 Received: from serene.no-ip.org ([98.164.83.25]) by eastrmimpo01.cox.net with bizsmtp id Svdu1h0060YnB6A02vduP2; Wed, 31 Aug 2011 03:37:54 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020204.4E5DE4D2.00B8,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=5AHg1zS6fKBk64vkGL/stHpTKznySuNzRq0QOAs0BF0= c=1 sm=1 a=ELdGOjK-_lUA:10 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=2vO5UZG1h46htWAnE/rx2g==:17 a=6I5d2MoRAAAA:8 a=kviXuzpPAAAA:8 a=p0VQEO97_es8_aGrhwMA:9 a=CjuIK1q_8ugA:10 a=SV7veod9ZcQA:10 a=4vB-4DCPJfMA:10 a=2vO5UZG1h46htWAnE/rx2g==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from cox.net (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id p7V7bsAI047174 for ; Wed, 31 Aug 2011 02:37:54 -0500 (CDT) (envelope-from conrads@cox.net) Date: Wed, 31 Aug 2011 02:37:48 -0500 From: "Conrad J. Sabatier" To: freebsd-ports@freebsd.org Message-ID: <20110831023748.704a9edb@cox.net> In-Reply-To: <4E5D0856.8080505@FreeBSD.org> References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5CC44C.3070604@FreeBSD.org> <20110830111152.GF28186@home.opsec.eu> <4E5CD28A.1080809@FreeBSD.org> <20110830122726.GG28186@home.opsec.eu> <4E5D0856.8080505@FreeBSD.org> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 07:38:01 -0000 On Tue, 30 Aug 2011 17:57:10 +0200 Matthias Andree wrote: > > I understand that keeping unchanging software can sometimes be > necessary, if you're working around its quirks. > > At the same time I'd like to discourage new installations of dead > software so that it disappears over time, rather than haunt fresh > systems. That makes perfect sense, yes. > How about if we added a new tag "OBSOLESCENT" or so that permits > building the software only if it's already installed but refuses new > installations? Of course there could be a switch to override that, > like TRYBROKEN that can override BROKEN= tags. You had me on the edge of my seat for a while there, talking about removing my beloved procmail. Now this suggestion I could easily live with. :-) > I'm not sure if it's feasible for packages (but OBSOLESCENT could > imply "do not package") but for ports it would be possible. I like it. :-) -- Conrad J. Sabatier conrads@cox.net From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 08:17:53 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A55251065672 for ; Wed, 31 Aug 2011 08:17:53 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 70E1E8FC25 for ; Wed, 31 Aug 2011 08:17:53 +0000 (UTC) Received: by iadx2 with SMTP id x2so697364iad.13 for ; Wed, 31 Aug 2011 01:17:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RYQF0b9p36SCS8N6ytdMt3B8cSITnaa7LoREOWRWveg=; b=HJqT36OPNMXSRnmEYq4jjCZl+OUI03XqjCqy4ofEZox0NxKYEEpGbVyfykr4b9aTm9 R6mieqwBW4pQvMQMKf7MyoyoEtMdEQPGQYeEZY9za9i/UzDZnfC4phgAJzE0aLRPYDJy vRrWI769vinH88rynytfe7sq3TwY31tuvPriE= MIME-Version: 1.0 Received: by 10.231.66.85 with SMTP id m21mr245757ibi.53.1314778672802; Wed, 31 Aug 2011 01:17:52 -0700 (PDT) Received: by 10.231.61.148 with HTTP; Wed, 31 Aug 2011 01:17:52 -0700 (PDT) Received: by 10.231.61.148 with HTTP; Wed, 31 Aug 2011 01:17:52 -0700 (PDT) In-Reply-To: <20110830195114.56a8f255@cox.net> References: <20110830195114.56a8f255@cox.net> Date: Wed, 31 Aug 2011 09:17:52 +0100 Message-ID: From: Chris Rees To: "Conrad J. Sabatier" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-ports@freebsd.org Subject: Re: (maintainer question) Possible bug in cvs: cvs diff -uN: -N switch being ignored (disappearing, actually) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 08:17:53 -0000 On 31 Aug 2011 01:51, "Conrad J. Sabatier" wrote: > > Odd little problem here I'm noticing with cvs. > > When I do a "cvs diff -uN", for some reason the -N switch is being > ignored. It vanishes completely in the header of the resulting > output. I've been trying to rename one of my patch files to conform to > portlint's recommendations, but unless I can get -N to work properly, > this is a no-go. Whether I add 'cvs diff -uN' to my .cvsrc, or > explicitly add it at the command line, makes no difference. > > For instance: > > [root@serene /usr/ports/net-p2p/lopster]# cvs diff -uN > cvs diff: Diffing . > Index: Makefile > =================================================================== > RCS file: /home/ncvs/ports/net-p2p/lopster/Makefile,v > retrieving revision 1.44 > diff -u -r1.44 Makefile > ^ > |__ What happened to -N? > > [snip remainder of diff output] > > Incidentally, this problem started before I upgraded two days ago from > 9.0-BETA1 to 9.0-BETA1, so it's not OS version-related. > > Any idea what could be causing this and how to correct it? Is this a > bug in cvs? Should I send-pr it? Did you remember to cvs add / rm the files you're adding/removing? Do you know what -N does? Chris From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 08:50:11 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE73A106564A for ; Wed, 31 Aug 2011 08:50:11 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo202.cox.net (eastrmfepo202.cox.net [68.230.241.217]) by mx1.freebsd.org (Postfix) with ESMTP id 48A018FC18 for ; Wed, 31 Aug 2011 08:50:10 +0000 (UTC) Received: from eastrmimpo01.cox.net ([68.1.16.119]) by eastrmfepo202.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20110831085010.FDHE32466.eastrmfepo202.cox.net@eastrmimpo01.cox.net>; Wed, 31 Aug 2011 04:50:10 -0400 Received: from serene.no-ip.org ([98.164.83.25]) by eastrmimpo01.cox.net with bizsmtp id Swq91h00F0YnB6A02wqA7X; Wed, 31 Aug 2011 04:50:10 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A02020A.4E5DF5C2.00BB,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=5AHg1zS6fKBk64vkGL/stHpTKznySuNzRq0QOAs0BF0= c=1 sm=1 a=-pwuJQO3sf0A:10 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=2vO5UZG1h46htWAnE/rx2g==:17 a=pGLkceISAAAA:8 a=kviXuzpPAAAA:8 a=W-qyeiMjH2dNeHUwBn4A:9 a=ouG4ARSO6WSsNT7HlfsA:7 a=CjuIK1q_8ugA:10 a=MSl-tDqOz04A:10 a=4vB-4DCPJfMA:10 a=2vO5UZG1h46htWAnE/rx2g==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from cox.net (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id p7V8o9QC091396; Wed, 31 Aug 2011 03:50:09 -0500 (CDT) (envelope-from conrads@cox.net) Date: Wed, 31 Aug 2011 03:50:04 -0500 From: "Conrad J. Sabatier" To: Chris Rees Message-ID: <20110831035004.600ed21c@cox.net> In-Reply-To: References: <20110830195114.56a8f255@cox.net> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: (maintainer question) Possible bug in cvs: cvs diff -uN: -N switch being ignored (disappearing, actually) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 08:50:11 -0000 On Wed, 31 Aug 2011 09:17:52 +0100 Chris Rees wrote: > On 31 Aug 2011 01:51, "Conrad J. Sabatier" wrote: > > > > Odd little problem here I'm noticing with cvs. > > > > When I do a "cvs diff -uN", for some reason the -N switch is being > > ignored. It vanishes completely in the header of the resulting > > output. I've been trying to rename one of my patch files to > > conform to portlint's recommendations, but unless I can get -N to > > work properly, this is a no-go. Whether I add 'cvs diff -uN' to > > my .cvsrc, or explicitly add it at the command line, makes no > > difference. > > > > For instance: > > > > [root@serene /usr/ports/net-p2p/lopster]# cvs diff -uN > > cvs diff: Diffing . > > Index: Makefile > > =================================================================== > > RCS file: /home/ncvs/ports/net-p2p/lopster/Makefile,v > > retrieving revision 1.44 > > diff -u -r1.44 Makefile > > ^ > > |__ What happened to -N? > > > > [snip remainder of diff output] > > > > Incidentally, this problem started before I upgraded two days ago > > from 9.0-BETA1 to 9.0-BETA1, so it's not OS version-related. > > > > Any idea what could be causing this and how to correct it? Is this > > a bug in cvs? Should I send-pr it? > > Did you remember to cvs add / rm the files you're adding/removing? Do > you know what -N does? > > Chris Well, I'm using a local copy of the FreeBSD CVS repository which I maintain via csup (from which I do checkouts/updates of /usr/{doc,ports,src}, so I don't try to do anything that modifies the repo, but I do like having it around to check log messages and, in the case of ports maintenance, to create patches. If I understand correctly, the -N switch to cvs diff should note if a file has been removed or a new file added, or am I mistaken? At any rate, doesn't it seem peculiar that the switch would just be silently dropped like this? Anyway, while we're on the subject: since I don't have any commit privileges (I suppose I could change that on my local copy of the repo, but I prefer to keep it in a pristine "official" state), what *is* the proper way to create a diff/patch that incorporates new files, or renames/deletes old ones? I understand the add/rm functions, having used them on my own personal cvs repo that I use for software projects I'm hacking on, but in dealing with the official repo, some other approach is needed, I think. Thanks. -- Conrad J. Sabatier conrads@cox.net From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 09:08:39 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B209106566B for ; Wed, 31 Aug 2011 09:08:39 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from thyme.infocus-llc.com (server.infocus-llc.com [206.156.254.44]) by mx1.freebsd.org (Postfix) with ESMTP id BA5CD8FC0C for ; Wed, 31 Aug 2011 09:08:38 +0000 (UTC) Received: from draco.over-yonder.net (c-174-50-4-38.hsd1.ms.comcast.net [174.50.4.38]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by thyme.infocus-llc.com (Postfix) with ESMTPSA id AF38B37B49F; Wed, 31 Aug 2011 03:51:27 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 1EE2361C51; Wed, 31 Aug 2011 03:51:27 -0500 (CDT) Date: Wed, 31 Aug 2011 03:51:27 -0500 From: "Matthew D. Fuller" To: "Conrad J. Sabatier" Message-ID: <20110831085127.GO2493@over-yonder.net> References: <20110830195114.56a8f255@cox.net> <20110831035004.600ed21c@cox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110831035004.600ed21c@cox.net> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.21-fullermd.4 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.2 at thyme.infocus-llc.com X-Virus-Status: Clean Cc: freebsd-ports@freebsd.org, Chris Rees Subject: Re: (maintainer question) Possible bug in cvs: cvs diff -uN: -N switch being ignored (disappearing, actually) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 09:08:39 -0000 On Wed, Aug 31, 2011 at 03:50:04AM -0500 I heard the voice of Conrad J. Sabatier, and lo! it spake thus: > > [...] so I don't try to do anything that modifies the repo, cvs add doesn't affect the repository, just the working tree state. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 09:13:32 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 215741065673 for ; Wed, 31 Aug 2011 09:13:32 +0000 (UTC) (envelope-from Johan@double-l.nl) Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by mx1.freebsd.org (Postfix) with ESMTP id 91F638FC0C for ; Wed, 31 Aug 2011 09:13:31 +0000 (UTC) Received: from remote.double-l.nl (double-l.xs4all.nl [80.126.205.144]) by smtp-vbr15.xs4all.nl (8.13.8/8.13.8) with ESMTP id p7V9Cxvp093631 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Wed, 31 Aug 2011 11:13:00 +0200 (CEST) (envelope-from Johan@double-l.nl) Received: from SRV01.double-l.local ([fe80::1128:e7bc:ba4a:a89a]) by SRV01.double-l.local ([fe80::1128:e7bc:ba4a:a89a%13]) with mapi id 14.01.0218.012; Wed, 31 Aug 2011 11:13:56 +0200 From: Johan Hendriks To: "freebsd-ports@freebsd.org" Thread-Topic: libproxy and libnotify the story continues :D Thread-Index: Acxnvk9roqb0kXcWQu+oXXu6HuBu3A== Date: Wed, 31 Aug 2011 09:13:56 +0000 Message-ID: <6C3F8332272B7D4DA26909F15F1C90E1E5CD31@SRV01.double-l.local> Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.50.200] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Scanned: by XS4ALL Virus Scanner Subject: libproxy and libnotify the story continues :D X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 09:13:32 -0000 Hello all, i also ran into the libproxy upgrade problems. So i tried al the stuff i found on the mailling list so far. I tried the solution from j.kim find /usr/local/lib -name "*.la" | \ xargs grep -l /usr/local/lib/libproxy.la | \ xargs -L 1 pkg_info -W | \ awk '{ print $6 }' | \ sort | \ uniq | \ xargs portupgrade -f But this ends like the following. /usr/include/machine/endian.h:130: syntax error, unexpected ';' in ' return= (__extension__ ({ register __uint32_t __X =3D (_x); __asm ("bswap %0" : "+= r" (__X)); __X; }));' at ';' /libexec/ld-elf.so.1: Shared object "libproxy.so.0" not found, required by = "libchamplain-0.8.so.1" Command '['/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champla= in-gtk/tmp-introspectpyOYLR/GtkChamplain-0.8', '--introspect-dump=3D/usr/po= rts/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk/tmp-introsp= ectpyOYLR/types.txt,/usr/ports/graphics/libchamplain/work/libchamplain-0.8.= 1/champlain-gtk/tmp-introspectpyOYLR/dump.xml']' returned non-zero exit sta= tus 1 gmake[3]: *** [GtkChamplain-0.8.gir] Error 1 gmake[3]: Leaving directory `/usr/ports/graphics/libchamplain/work/libchamp= lain-0.8.1/champlain-gtk' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/graphics/libchamplain/work/libchamp= lain-0.8.1/champlain-gtk' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/libchamplain/work/libchamp= lain-0.8.1' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/graphics/libchamplain. I reinstalled libproxy, i reinstalled libgweather and so on, also the poor = mans portmaster solution from doug. But i can not get past this. Also did a recompile off all the evolution stuff, Then tried portmaster lib* in the hope there was a library not installed o= k, but that ends with the same error as above. I am struggling for a day or 4 now with this. Could someone please help me :D=20 regards Johan= From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 09:13:46 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67F05106564A; Wed, 31 Aug 2011 09:13:46 +0000 (UTC) (envelope-from christer.solskogen@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 108778FC08; Wed, 31 Aug 2011 09:13:45 +0000 (UTC) Received: by vxh11 with SMTP id 11so349587vxh.13 for ; Wed, 31 Aug 2011 02:13:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=LvR+0xPIbmvIBj+XD3AS9RMJjgfM42vocfzlKlNRIIE=; b=xijs3Xs4B0A0/joAg4t5wJ6fOXGD1dfUI/oZOGklXtYm3VWeKkO25nr2I0Im1RRd44 r97Db5SyWg63GNGXVUB+W0GFH256Whk7eOK+dv3nl5tp0MVzqI0oVU69leRhWrNt30VD 3Em2/1omDxMMk7wScT0kWh32+ra3FiPaIC6as= Received: by 10.52.99.71 with SMTP id eo7mr124679vdb.152.1314780146042; Wed, 31 Aug 2011 01:42:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.107.68 with HTTP; Wed, 31 Aug 2011 01:42:06 -0700 (PDT) From: Christer Solskogen Date: Wed, 31 Aug 2011 10:42:06 +0200 Message-ID: To: anders@freebsd.org, freebsd-ports Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: varnish 3.0.1 build error X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 09:13:46 -0000 This is the output from building varnish 3.0.1 on 8.2-RELEASE. I recently built 3.0.0 without any problems. /bin/sh ../../libtool --tag=CC --mode=link cc -std=gnu99 -O2 -pipe -march=nocona -fno-strict-aliasing -D_THREAD_SAFE -pthread -Wextra -Wno-missing-field-initializers -Wno-sign-compare -o varnishadm varnishadm-varnishadm.o varnishadm-assert.o varnishadm-tcp.o varnishadm-vss.o ../../lib/libvarnishapi/libvarnishapi.la ../../lib/libvarnishcompat/libvarnishcompat.la -ledit -lm libtool: link: cc -std=gnu99 -O2 -pipe -march=nocona -fno-strict-aliasing -D_THREAD_SAFE -pthread -Wextra -Wno-missing-field-initializers -Wno-sign-compare -o .libs/varnishadm varnishadm-varnishadm.o varnishadm-assert.o varnishadm-tcp.o varnishadm-vss.o ../../lib/libvarnishapi/.libs/libvarnishapi.so -L/usr/local/lib /usr/local/lib/libpcre.so ../../lib/libvarnishcompat/.libs/libvarnishcompat.so -ledit -lm -pthread -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath -Wl,/usr/local/lib/varnish varnishadm-varnishadm.o(.text+0x79): In function `cli_write': : undefined reference to `rl_callback_handler_remove' varnishadm-varnishadm.o(.text+0x706): In function `main': : undefined reference to `rl_already_prompted' varnishadm-varnishadm.o(.text+0x728): In function `main': : undefined reference to `rl_callback_handler_install' varnishadm-varnishadm.o(.text+0x86e): In function `main': : undefined reference to `rl_forced_update_display' varnishadm-varnishadm.o(.text+0x881): In function `main': : undefined reference to `rl_callback_read_char' varnishadm-varnishadm.o(.text+0x8c5): In function `main': : undefined reference to `rl_callback_handler_remove' varnishadm-varnishadm.o(.text+0x8d9): In function `main': : undefined reference to `rl_callback_handler_install' varnishadm-varnishadm.o(.text+0x93c): In function `main': : undefined reference to `rl_callback_handler_remove' varnishadm-varnishadm.o(.text+0x97d): In function `send_line': : undefined reference to `rl_callback_handler_remove' varnishadm-varnishadm.o(.text+0x978): In function `send_line': : undefined reference to `add_history' gmake[3]: *** [varnishadm] Error 1 gmake[3]: Leaving directory `/usr/obj/usr/ports/www/varnish/work/varnish-3.0.1/bin/varnishadm' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/obj/usr/ports/www/varnish/work/varnish-3.0.1/bin' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/obj/usr/ports/www/varnish/work/varnish-3.0.1' gmake: *** [all] Error 2 *** Error code 1 -- chs, From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 09:13:51 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E1391065672 for ; Wed, 31 Aug 2011 09:13:51 +0000 (UTC) (envelope-from Johan@double-l.nl) Received: from smtp-vbr5.xs4all.nl (smtp-vbr5.xs4all.nl [194.109.24.25]) by mx1.freebsd.org (Postfix) with ESMTP id 043C68FC16 for ; Wed, 31 Aug 2011 09:13:50 +0000 (UTC) Received: from remote.double-l.nl (double-l.xs4all.nl [80.126.205.144]) by smtp-vbr5.xs4all.nl (8.13.8/8.13.8) with ESMTP id p7V9DFPj028479 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Wed, 31 Aug 2011 11:13:19 +0200 (CEST) (envelope-from Johan@double-l.nl) Received: from SRV01.double-l.local ([fe80::1128:e7bc:ba4a:a89a]) by SRV01.double-l.local ([fe80::1128:e7bc:ba4a:a89a%13]) with mapi id 14.01.0218.012; Wed, 31 Aug 2011 11:14:08 +0200 From: Johan Hendriks To: "freebsd-ports@freebsd.org" Thread-Topic: libproxy and libnotify the story continues :D Thread-Index: AcxnvlZd5vgCFFX6Q9a8FEbO1+S4/g== Date: Wed, 31 Aug 2011 09:14:07 +0000 Message-ID: <6C3F8332272B7D4DA26909F15F1C90E1E5CD3E@SRV01.double-l.local> Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.50.200] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Scanned: by XS4ALL Virus Scanner Subject: libproxy and libnotify the story continues :D X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 09:13:51 -0000 Hello all, i also ran into the libproxy upgrade problems. So i tried al the stuff i found on the mailling list so far. I tried the solution from j.kim find /usr/local/lib -name "*.la" | \ xargs grep -l /usr/local/lib/libproxy.la | \ xargs -L 1 pkg_info -W | \ awk '{ print $6 }' | \ sort | \ uniq | \ xargs portupgrade -f But this ends like the following. /usr/include/machine/endian.h:130: syntax error, unexpected ';' in ' return= (__extension__ ({ register __uint32_t __X =3D (_x); __asm ("bswap %0" : "+= r" (__X)); __X; }));' at ';' /libexec/ld-elf.so.1: Shared object "libproxy.so.0" not found, required by = "libchamplain-0.8.so.1" Command '['/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champla= in-gtk/tmp-introspectpyOYLR/GtkChamplain-0.8', '--introspect-dump=3D/usr/po= rts/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk/tmp-introsp= ectpyOYLR/types.txt,/usr/ports/graphics/libchamplain/work/libchamplain-0.8.= 1/champlain-gtk/tmp-introspectpyOYLR/dump.xml']' returned non-zero exit sta= tus 1 gmake[3]: *** [GtkChamplain-0.8.gir] Error 1 gmake[3]: Leaving directory `/usr/ports/graphics/libchamplain/work/libchamp= lain-0.8.1/champlain-gtk' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/graphics/libchamplain/work/libchamp= lain-0.8.1/champlain-gtk' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/libchamplain/work/libchamp= lain-0.8.1' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/graphics/libchamplain. I reinstalled libproxy, i reinstalled libgweather and so on, also the poor = mans portmaster solution from doug. But i can not get past this. Also did a recompile off all the evolution stuff, Then tried portmaster lib* in the hope there was a library not installed o= k, but that ends with the same error as above. I am struggling for a day or 4 now with this. Could someone please help me :D=20 regards Johan= From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 09:19:11 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 354BD106564A for ; Wed, 31 Aug 2011 09:19:11 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id B99E48FC15 for ; Wed, 31 Aug 2011 09:19:10 +0000 (UTC) Received: by bkat8 with SMTP id t8so859902bka.13 for ; Wed, 31 Aug 2011 02:19:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=honxkqrw7/k67YJotBahZzfCDYRJWl/LSRVeqCeUswI=; b=A5HI2A6UO3D+7K/V13kGhcTow1FU1hCAqJV//CQGP3ZvOph+Vx0HYofJrc3NPHL8L2 39IBUdkotGfOXlUS8yNXvdFuLJRGdqv+zxDQqufT9N/hUr6WB5pMwqDPxQGfn0RgLP2G kYOkzrJMksFNnEljyX6JT76wXikRzfa+TxLzU= Received: by 10.204.155.81 with SMTP id r17mr129241bkw.19.1314782349506; Wed, 31 Aug 2011 02:19:09 -0700 (PDT) Received: from [10.0.101.2] (254.166.broadband10.iol.cz [90.177.166.254]) by mx.google.com with ESMTPS id v1sm281770bkd.55.2011.08.31.02.19.07 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 02:19:08 -0700 (PDT) From: Michal Varga To: Johan Hendriks In-Reply-To: <6C3F8332272B7D4DA26909F15F1C90E1E5CD31@SRV01.double-l.local> References: <6C3F8332272B7D4DA26909F15F1C90E1E5CD31@SRV01.double-l.local> Content-Type: text/plain; charset="UTF-8" Organization: Stonehenge Date: Wed, 31 Aug 2011 11:19:05 +0200 Message-ID: <1314782345.82067.465.camel@xenon> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-ports@freebsd.org" Subject: Re: libproxy and libnotify the story continues :D X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 09:19:11 -0000 On Wed, 2011-08-31 at 09:13 +0000, Johan Hendriks wrote: > Hello all, i also ran into the libproxy upgrade problems. > > So i tried al the stuff i found on the mailling list so far. > > I tried the solution from j.kim > > find /usr/local/lib -name "*.la" | \ > xargs grep -l /usr/local/lib/libproxy.la | \ > xargs -L 1 pkg_info -W | \ > awk '{ print $6 }' | \ > sort | \ > uniq | \ > xargs portupgrade -f > > But this ends like the following. > > /usr/include/machine/endian.h:130: syntax error, unexpected ';' in ' return (__extension__ ({ register __uint32_t __X = (_x); __asm ("bswap %0" : "+r" (__X)); __X; }));' at ';' > /libexec/ld-elf.so.1: Shared object "libproxy.so.0" not found, required by "libchamplain-0.8.so.1" > Command '['/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk/tmp-introspectpyOYLR/GtkChamplain-0.8', '--introspect-dump=/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk/tmp-introspectpyOYLR/types.txt,/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk/tmp-introspectpyOYLR/dump.xml']' returned non-zero exit status 1 > gmake[3]: *** [GtkChamplain-0.8.gir] Error 1 > gmake[3]: Leaving directory `/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk' > gmake[2]: *** [all] Error 2 > gmake[2]: Leaving directory `/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1' > gmake: *** [all] Error 2 > *** Error code 1 > > Stop in /usr/ports/graphics/libchamplain. > > I reinstalled libproxy, i reinstalled libgweather and so on, also the poor mans portmaster solution from doug. > > But i can not get past this. > > Also did a recompile off all the evolution stuff, > Then tried portmaster lib* in the hope there was a library not installed ok, but that ends with the same error as above. > > I am struggling for a day or 4 now with this. > > Could someone please help me :D This is another iteration of the same old issue: http://www.mail-archive.com/freebsd-ports@freebsd.org/msg34214.html m. -- Michal Varga, Stonehenge (Gmail account) From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 09:33:32 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73C75106564A for ; Wed, 31 Aug 2011 09:33:32 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo103.cox.net (eastrmfepo103.cox.net [68.230.241.215]) by mx1.freebsd.org (Postfix) with ESMTP id 12B398FC17 for ; Wed, 31 Aug 2011 09:33:31 +0000 (UTC) Received: from eastrmimpo02.cox.net ([68.1.16.120]) by eastrmfepo103.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20110831093331.USJL3924.eastrmfepo103.cox.net@eastrmimpo02.cox.net> for ; Wed, 31 Aug 2011 05:33:31 -0400 Received: from serene.no-ip.org ([98.164.83.25]) by eastrmimpo02.cox.net with bizsmtp id SxZW1h00V0YnB6A02xZXaA; Wed, 31 Aug 2011 05:33:31 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A02020A.4E5DFFEB.0059,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=ax4i8a8snyEA9uWfgWYmXW+3D+RWNhitQWxcW0Jxd9c= c=1 sm=1 a=-pwuJQO3sf0A:10 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=2vO5UZG1h46htWAnE/rx2g==:17 a=HjEgb3SSAAAA:8 a=kviXuzpPAAAA:8 a=B70D82nufMpIEnd-LUcA:9 a=CjuIK1q_8ugA:10 a=__daLkwkpeoA:10 a=4vB-4DCPJfMA:10 a=2vO5UZG1h46htWAnE/rx2g==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from cox.net (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id p7V9XUG0091825 for ; Wed, 31 Aug 2011 04:33:30 -0500 (CDT) (envelope-from conrads@cox.net) Date: Wed, 31 Aug 2011 04:33:25 -0500 From: "Conrad J. Sabatier" To: freebsd-ports@freebsd.org Message-ID: <20110831043325.3c44bc4e@cox.net> In-Reply-To: <20110831085127.GO2493@over-yonder.net> References: <20110830195114.56a8f255@cox.net> <20110831035004.600ed21c@cox.net> <20110831085127.GO2493@over-yonder.net> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: (maintainer question) Possible bug in cvs: cvs diff -uN: -N switch being ignored (disappearing, actually) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 09:33:32 -0000 On Wed, 31 Aug 2011 03:51:27 -0500 "Matthew D. Fuller" wrote: > On Wed, Aug 31, 2011 at 03:50:04AM -0500 I heard the voice of > Conrad J. Sabatier, and lo! it spake thus: > > > > [...] so I don't try to do anything that modifies the repo, > > cvs add doesn't affect the repository, just the working tree state. OK, looks like I had a major misunderstanding going on here. :-) After using cvs add/delete, the diff is coming out as expected now. Sorry for the noise, folks. :-) -- Conrad J. Sabatier conrads@cox.net From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 09:53:38 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E802106566B for ; Wed, 31 Aug 2011 09:53:38 +0000 (UTC) (envelope-from Johan@double-l.nl) Received: from smtp-vbr16.xs4all.nl (smtp-vbr16.xs4all.nl [194.109.24.36]) by mx1.freebsd.org (Postfix) with ESMTP id 21D098FC0C for ; Wed, 31 Aug 2011 09:53:37 +0000 (UTC) Received: from remote.double-l.nl (double-l.xs4all.nl [80.126.205.144]) by smtp-vbr16.xs4all.nl (8.13.8/8.13.8) with ESMTP id p7V9r6hO090343 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 31 Aug 2011 11:53:06 +0200 (CEST) (envelope-from Johan@double-l.nl) Received: from SRV01.double-l.local ([fe80::1128:e7bc:ba4a:a89a]) by SRV01.double-l.local ([fe80::1128:e7bc:ba4a:a89a%13]) with mapi id 14.01.0218.012; Wed, 31 Aug 2011 11:53:59 +0200 From: Johan Hendriks To: Michal Varga Thread-Topic: libproxy and libnotify the story continues :D Thread-Index: Acxnvk9roqb0kXcWQu+oXXu6HuBu3P//3+mAgAAqup0= Date: Wed, 31 Aug 2011 09:53:59 +0000 Message-ID: <6C3F8332272B7D4DA26909F15F1C90E1E5CDC7@SRV01.double-l.local> References: <6C3F8332272B7D4DA26909F15F1C90E1E5CD31@SRV01.double-l.local>, <1314782345.82067.465.camel@xenon> In-Reply-To: <1314782345.82067.465.camel@xenon> Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.50.200] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: "freebsd-ports@freebsd.org" Subject: RE: libproxy and libnotify the story continues :D X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 09:53:38 -0000 ________________________________________ Van: Michal Varga [varga.michal@gmail.com] Verzonden: woensdag 31 augustus 2011 11:19 Aan: Johan Hendriks CC: freebsd-ports@freebsd.org Onderwerp: Re: libproxy and libnotify the story continues :D >This is another iteration of the same old issue: >http://www.mail-archive.com/freebsd-ports@freebsd.org/msg34214.html >m. >-- >Michal Varga, >Stonehenge (Gmail account) Thanks that was it. Because i was so busy with the whole libproxy.la thing i did not look any f= urther anymore. Well fingers crossed and hope it continues now. regards Johan From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 11:38:19 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A2101065676; Wed, 31 Aug 2011 11:38:19 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward11.mail.yandex.net (forward11.mail.yandex.net [IPv6:2a02:6b8:0:801::1]) by mx1.freebsd.org (Postfix) with ESMTP id E3AAA8FC1A; Wed, 31 Aug 2011 11:38:18 +0000 (UTC) Received: from smtp12.mail.yandex.net (smtp12.mail.yandex.net [95.108.131.191]) by forward11.mail.yandex.net (Yandex) with ESMTP id 4D3E3E826CB; Wed, 31 Aug 2011 15:38:17 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314790697; bh=PvnPIPRpfJayW0+29M0l0dBThTz3uUXCJbZHTRXU/LM=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=oyFr7Uh4gFJTNcaxfz6T/5ao2zSbNmq+hDvoceqckwo1Q1KH5ACmsXtlJKmltW+8u WfHEn4ZSXwZ+Ep5mdeUSSyqcRk8LqELkgklRPsajgaBHe3UXgzawi7O7/1xhZxk6pZ 6vC8vyukX4wcBE1y5kngyeQcFvpQ3p8dXl9uUcws= Received: from smtp12.mail.yandex.net (localhost [127.0.0.1]) by smtp12.mail.yandex.net (Yandex) with ESMTP id 2354816A0442; Wed, 31 Aug 2011 15:38:17 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp12.mail.yandex.net (nwsmtp/Yandex) with ESMTP id cGkKFjUs; Wed, 31 Aug 2011 15:38:16 +0400 X-Yandex-Spam: 1 Message-ID: <4E5E1D25.3060602@yandex.ru> Date: Wed, 31 Aug 2011 15:38:13 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: perryh@pluto.rain.com References: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> In-Reply-To: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, acm@freebsd.org, cwhiteh@onetel.com Subject: Re: editors/zim X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 11:38:19 -0000 perryh@pluto.rain.com wrote on 31.08.2011 09:29: > Forwarding to ports@, which seems more likely to yield an answer to > this particular inquiry than questions@ > > Please keep the OP, who is probably not subscribed to ports@, in the > Cc: list. > > ==================================================================== > > Date: Tue, 30 Aug 2011 13:52:12 +0100 > From: Chris Whitehouse > To: User Questions > Subject: editors/zim > > Hi, > > I have a problem with Zim which I wrote to the author about he > replied and said; > > "I'm afraid version 0.29 is no longer supported. This was the last > version in the Perl branch, since we moved to Python there have been > already 10 more releases. So please try the latest version (0.52)." > > Are there any plans to bump it to Python and a recent release? > I emailed the maintainer a while back but got no response. > > thanks > > Chris Hi, Chris. I looked at the requirements and it seems easy to port. I'll look at this today and then let you know. -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 11:44:27 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C6CC106564A; Wed, 31 Aug 2011 11:44:27 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id E8F158FC08; Wed, 31 Aug 2011 11:44:26 +0000 (UTC) Received: by iadx2 with SMTP id x2so922851iad.13 for ; Wed, 31 Aug 2011 04:44:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=8TLjnqzLghpuR/GSkk/gL9tKEfBz1jzn2d3qn6tTeZc=; b=iuQP/aYjvR8/IdxigFnk+dyruyLDdk5y86qnfCd7hx4CQ6PNkXoykNaSeHxlxyzbZl k0ndlH9Yt5zYrJei2718asIi4R4jAx1WuOH0YSTsHdVYp7nDBTlLlw3Y+8da2iFdGbFF Mll7HXFO8hcQ7A1R86WCZSdwSKsVUfTn20Ahg= Received: by 10.231.26.68 with SMTP id d4mr576337ibc.66.1314791066113; Wed, 31 Aug 2011 04:44:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.61.148 with HTTP; Wed, 31 Aug 2011 04:43:56 -0700 (PDT) In-Reply-To: References: <1B4FC0D8-60E6-49DA-BC52-688052C4DA51@langille.org> <20110819232125.GA4965@icarus.home.lan> <20110820032438.GA21925@icarus.home.lan> <4774BC00-F32B-4BF4-A955-3728F885CAA1@langille.org> <4E4FF4D6.1090305@os2.kiev.ua> <20110820183456.GA38317@icarus.home.lan> <4e50c931.gCNlQFqn5sVQXXax%perryh@pluto.rain.com> <20110821050051.GA47415@icarus.home.lan> <4e5141dd.mmh6t9R/knnc8Jll%perryh@pluto.rain.com> <4e55153e.Tj16zX3SskfuVesE%perryh@pluto.rain.com> From: Chris Rees Date: Wed, 31 Aug 2011 12:43:56 +0100 Message-ID: To: perryh@pluto.rain.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: vincepoy@gmail.com, freebsd-stable@freebsd.org, freebsd-ports@freebsd.org, freebsd@jdc.parodius.com Subject: Re: ports/sysutils/diskcheckd (Re: bad sector in gmirror HDD) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 11:44:27 -0000 On 25 August 2011 18:54, Chris Rees wrote: > On 24 August 2011 16:14, =A0 wrote: >>> When the specified or calculated rate exceeds 64KB/sec, the >>> required sleep interval between 64KB chunks is less than one >>> second. =A0Since diskcheckd calculates the interval in whole seconds >>> -- because it calls sleep() rather than usleep() or nanosleep() >>> -- an interval of less than one second is calculated as zero ... >>> I suspect the fix will be to calculate in microseconds, and call >>> usleep() instead of sleep(). >> >> I think I may have this fixed. >> >> Could one of you try the attached patch? =A0I'm especially interested >> to see if this also clears up the issues reported as connected with >> gmirror (http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/143566), >> since I haven't been able to reproduce that part here. >> >> Summary of changes: >> >> * Calculate delays in microseconds, so that delays of less than >> =A0one second between reads (needed to implement rates exceeding >> =A064KB/sec) do not get rounded down to zero. >> >> * Fix a reinitialization problem when handling SIGHUP. >> >> * Additional debug messages (only with -d). >> >> * Comment and manpage improvememts. >> > > Hi Perry, > > The changes look good, so if there's no response for a few days I'll > commit the changes. > > Thanks for rescuing the port :) > Committed. Thanks! --=20 Chris Rees =A0 =A0 =A0 =A0 =A0| FreeBSD Developer crees@FreeBSD.org =A0 | http://people.freebsd.org/~crees From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 12:07:54 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F2511065670 for ; Wed, 31 Aug 2011 12:07:54 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id CD6F18FC0A for ; Wed, 31 Aug 2011 12:07:53 +0000 (UTC) Received: by qyk4 with SMTP id 4so870615qyk.13 for ; Wed, 31 Aug 2011 05:07:53 -0700 (PDT) Received: by 10.224.197.133 with SMTP id ek5mr210631qab.281.1314792471997; Wed, 31 Aug 2011 05:07:51 -0700 (PDT) Received: from scorpio.seibercom.net (cpe-076-182-105-057.nc.res.rr.com [76.182.105.57]) by mx.google.com with ESMTPS id w12sm4825988qct.36.2011.08.31.05.07.50 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 05:07:51 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jerry@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3RplpY56zzz2CG5G; Wed, 31 Aug 2011 08:07:49 -0400 (EDT) Date: Wed, 31 Aug 2011 08:07:49 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110831080749.51f36daa@seibercom.net> Organization: seibercom.net X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: novel@FreeBSD.org Subject: Update GnuTLS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 12:07:54 -0000 GnuTLS has been updated. URL: I was wondering if there is any work being done on getting the new version into the ports tree. GnuTLS 3.0.x branch replaces the GnuTLS 2.12.x branch as the supported stable branch. The experimental 2.99.x branch is now probably comatose as well. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ Last week's pet, this week's special. From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 12:42:51 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1033) id A33091065675; Wed, 31 Aug 2011 12:42:51 +0000 (UTC) Date: Wed, 31 Aug 2011 12:42:51 +0000 From: Alexey Dokuchaev To: freebsd-ports@freebsd.org Message-ID: <20110831124251.GC82908@FreeBSD.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Subject: Re: Problem with nvidia-driver and "X" after upgrade X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 12:42:51 -0000 On Fri, Aug 26, 2011 at 03:30:47PM -0400, Carmel wrote: > After updating my system as per the UPDATING file, I now find that the > Nvidia driver no longer works with Xorg. I've just updated the driver to version 280.13; perhaps you should update your ports free, rebuild the driver, and see if the problem goes away. ./danfe From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 13:13:18 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFB751065672; Wed, 31 Aug 2011 13:13:18 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward12.mail.yandex.net (forward12.mail.yandex.net [IPv6:2a02:6b8:0:801::2]) by mx1.freebsd.org (Postfix) with ESMTP id 43B708FC14; Wed, 31 Aug 2011 13:13:18 +0000 (UTC) Received: from smtp12.mail.yandex.net (smtp12.mail.yandex.net [95.108.131.191]) by forward12.mail.yandex.net (Yandex) with ESMTP id 9E94CC221B3; Wed, 31 Aug 2011 17:13:16 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314796396; bh=BBvHiYSBxpGK8eoG4rShZ1uOenOQtcwNJCIkkWB/m3c=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=FEute3RcsfjcLTw02G7H2mpVmjZ0T4yD4cGRXa9YeECTsre2/vozTQTLzQFi2OuYc iz6Vgz/6OnYPJ8frsL3p4dbRoTKpuvlhz/9SEt2DmPkU7wXJuheTKKi6fvR04QLfcf LBbDp0/m36NY3OCeDmUCQ1Pz90uukCLXWZNRcXcY= Received: from smtp12.mail.yandex.net (localhost [127.0.0.1]) by smtp12.mail.yandex.net (Yandex) with ESMTP id 6FE0E16A0015; Wed, 31 Aug 2011 17:13:16 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp12.mail.yandex.net (nwsmtp/Yandex) with ESMTP id DDkKL16a; Wed, 31 Aug 2011 17:13:13 +0400 X-Yandex-Spam: 1 Message-ID: <4E5E3364.7050308@yandex.ru> Date: Wed, 31 Aug 2011 17:13:08 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: perryh@pluto.rain.com References: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> In-Reply-To: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, acm@freebsd.org, cwhiteh@onetel.com Subject: Re: editors/zim X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 13:13:18 -0000 perryh@pluto.rain.com wrote on 31.08.2011 09:29: > Forwarding to ports@, which seems more likely to yield an answer to > this particular inquiry than questions@ > > Please keep the OP, who is probably not subscribed to ports@, in the > Cc: list. > > ==================================================================== > > Date: Tue, 30 Aug 2011 13:52:12 +0100 > From: Chris Whitehouse > To: User Questions > Subject: editors/zim > > Hi, > > I have a problem with Zim which I wrote to the author about he > replied and said; > > "I'm afraid version 0.29 is no longer supported. This was the last > version in the Perl branch, since we moved to Python there have been > already 10 more releases. So please try the latest version (0.52)." > > Are there any plans to bump it to Python and a recent release? > I emailed the maintainer a while back but got no response. > > thanks > > Chris Here is: a) diff to a previous port: http://happy-nation.by.ru/ports/zim-0.52.diff.txt b) updated port tarball: http://happy-nation.by.ru/ports/zim-0.52.tgz.txt (Just rename it to zim-0.52.tgz and unpack instead of current zim port directory). It works fine to me. Please test and report back is all is alright. If it does, i'll sent problem report to update it in teh tree. -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 13:28:43 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72253106566C; Wed, 31 Aug 2011 13:28:43 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 35E068FC0A; Wed, 31 Aug 2011 13:28:43 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QykqR-000Jaf-Ic; Wed, 31 Aug 2011 15:28:43 +0200 Date: Wed, 31 Aug 2011 15:28:43 +0200 From: Kurt Jaeger To: freebsd-ports@freebsd.org Message-ID: <20110831132843.GI28186@home.opsec.eu> References: <20110831080749.51f36daa@seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110831080749.51f36daa@seibercom.net> Cc: novel@FreeBSD.org Subject: Re: Update GnuTLS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 13:28:43 -0000 Hi! > GnuTLS has been updated. URL: > > > I was wondering if there is any work being done on getting the new > version into the ports tree. GnuTLS 3.0.x branch replaces the GnuTLS > 2.12.x branch as the supported stable branch. The experimental 2.99.x > branch is now probably comatose as well. gnutls-3.0.1 needs p11-kit in version 0.4 or newer, maybe that's why we're still at 2.x ? And re-testing the whole dependencies on that -- sounds like a close call for 9.0-REL... -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 13:30:35 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1576106567E for ; Wed, 31 Aug 2011 13:30:35 +0000 (UTC) (envelope-from carmel_ny@hotmail.com) Received: from blu0-omc3-s34.blu0.hotmail.com (blu0-omc3-s34.blu0.hotmail.com [65.55.116.109]) by mx1.freebsd.org (Postfix) with ESMTP id 504AA8FC17 for ; Wed, 31 Aug 2011 13:30:35 +0000 (UTC) Received: from BLU0-SMTP145 ([65.55.116.73]) by blu0-omc3-s34.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 31 Aug 2011 06:30:34 -0700 X-Originating-IP: [76.182.105.57] X-Originating-Email: [carmel_ny@hotmail.com] Message-ID: Received: from scorpio.seibercom.net ([76.182.105.57]) by BLU0-SMTP145.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 31 Aug 2011 06:30:33 -0700 Received: from scorpio (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: carmel_ny@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3Rpnf03Pcdz2CG5G for ; Wed, 31 Aug 2011 09:30:32 -0400 (EDT) Date: Wed, 31 Aug 2011 09:30:31 -0400 From: Carmel To: freebsd-ports@freebsd.org In-Reply-To: <20110831124251.GC82908@FreeBSD.org> References: <20110831124251.GC82908@FreeBSD.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 31 Aug 2011 13:30:33.0531 (UTC) FILETIME=[290428B0:01CC67E2] Subject: Re: Problem with nvidia-driver and "X" after upgrade X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 13:30:35 -0000 On Wed, 31 Aug 2011 12:42:51 +0000 Alexey Dokuchaev articulated: > On Fri, Aug 26, 2011 at 03:30:47PM -0400, Carmel wrote: > > After updating my system as per the UPDATING file, I now find that > > the Nvidia driver no longer works with Xorg. > > I've just updated the driver to version 280.13; perhaps you should > update your ports free, rebuild the driver, and see if the problem > goes away. Thanks, but the problem was solved several days ago. You might want to check the archives for further details. -- Carmel ✌ carmel_ny@hotmail.com From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 13:55:44 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 083DB1065673 for ; Wed, 31 Aug 2011 13:55:44 +0000 (UTC) (envelope-from carmel_ny@hotmail.com) Received: from blu0-omc3-s25.blu0.hotmail.com (blu0-omc3-s25.blu0.hotmail.com [65.55.116.100]) by mx1.freebsd.org (Postfix) with ESMTP id B0F2C8FC27 for ; Wed, 31 Aug 2011 13:55:43 +0000 (UTC) Received: from BLU0-SMTP410 ([65.55.116.72]) by blu0-omc3-s25.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 31 Aug 2011 06:55:42 -0700 X-Originating-IP: [76.182.105.57] X-Originating-Email: [carmel_ny@hotmail.com] Message-ID: Received: from scorpio.seibercom.net ([76.182.105.57]) by BLU0-SMTP410.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 31 Aug 2011 06:55:40 -0700 Received: from scorpio (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: carmel_ny@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3RppBz1vW1z2CG5G for ; Wed, 31 Aug 2011 09:55:39 -0400 (EDT) Date: Wed, 31 Aug 2011 09:55:38 -0400 From: Carmel To: freebsd-ports@freebsd.org In-Reply-To: <20110831132843.GI28186@home.opsec.eu> References: <20110831080749.51f36daa@seibercom.net> <20110831132843.GI28186@home.opsec.eu> Organization: seibercom.net X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 31 Aug 2011 13:55:40.0701 (UTC) FILETIME=[AB5C0CD0:01CC67E5] Subject: Re: Update GnuTLS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 13:55:44 -0000 On Wed, 31 Aug 2011 15:28:43 +0200 Kurt Jaeger articulated: > > GnuTLS has been updated. URL: > > > > > > I was wondering if there is any work being done on getting the new > > version into the ports tree. GnuTLS 3.0.x branch replaces the GnuTLS > > 2.12.x branch as the supported stable branch. The experimental > > 2.99.x branch is now probably comatose as well. > > gnutls-3.0.1 needs p11-kit in version 0.4 or newer, maybe that's why > we're still at 2.x ? I am not even going to pretend to know what the problem is there. Perhaps you can enlighten me as to why the "p11-kit" port cannot be updated to the latest version. > And re-testing the whole dependencies on that -- sounds like a > close call for 9.0-REL... That doesn't sound so good either. -- Carmel ✌ carmel_ny@hotmail.com From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 14:00:04 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19EF710656E8 for ; Wed, 31 Aug 2011 14:00:04 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id B95648FC08 for ; Wed, 31 Aug 2011 14:00:03 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QylKm-000K5X-Pb for freebsd-ports@freebsd.org; Wed, 31 Aug 2011 16:00:04 +0200 Date: Wed, 31 Aug 2011 16:00:04 +0200 From: Kurt Jaeger To: freebsd-ports@freebsd.org Message-ID: <20110831140004.GJ28186@home.opsec.eu> References: <20110831080749.51f36daa@seibercom.net> <20110831132843.GI28186@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: Update GnuTLS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 14:00:04 -0000 Hi! > > gnutls-3.0.1 needs p11-kit in version 0.4 or newer, maybe that's why > > we're still at 2.x ? > > I am not even going to pretend to know what the problem is there. > Perhaps you can enlighten me as to why the "p11-kit" port cannot be > updated to the latest version. I can't enlighten you, but submitted http://www.freebsd.org/cgi/query-pr.cgi?pr=160334 to update it to 0.5. But I have not checked its dependencies. > > And re-testing the whole dependencies on that -- sounds like a > > close call for 9.0-REL... > > That doesn't sound so good either. I tested gnutls-3.0.1 and it had compilation issues in nettle/. Had no time to dig deeper. -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 14:05:32 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 206C9106566B for ; Wed, 31 Aug 2011 14:05:32 +0000 (UTC) (envelope-from anders@FreeBSD.org) Received: from fupp.net (totem.fix.no [80.91.36.20]) by mx1.freebsd.org (Postfix) with ESMTP id 9DCDA8FC17 for ; Wed, 31 Aug 2011 14:05:31 +0000 (UTC) Received: from totem.fix.no (totem.fix.no [80.91.36.20]) by fupp.net (Postfix) with ESMTP id 71D5E430D6; Wed, 31 Aug 2011 15:46:11 +0200 (CEST) Received: from fupp.net ([80.91.36.20]) by totem.fix.no (totem.fix.no [80.91.36.20]) (amavisd-new, port 10024) with LMTP id hGIvmc6PR4Dv; Wed, 31 Aug 2011 15:46:10 +0200 (CEST) Received: by fupp.net (Postfix, from userid 1000) id 1372D430D5; Wed, 31 Aug 2011 15:46:10 +0200 (CEST) Date: Wed, 31 Aug 2011 15:46:09 +0200 From: Anders Nordby To: Christer Solskogen Message-ID: <20110831134609.GA38206@fupp.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-PGP-Key: http://anders.fix.no/pgp/ X-PGP-Key-FingerPrint: 1E0F C53C D8DF 6A8F EAAD 19C5 D12A BC9F 0083 5956 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-ports Subject: Re: varnish 3.0.1 build error X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 14:05:32 -0000 Hi, I just committed an update, please do try. I had some problems with 3.0.1, so be careful before you upgrade all your servers: https://www.varnish-cache.org/trac/ticket/1001 Anders. On ons, aug 31, 2011 at 10:42:06am +0200, Christer Solskogen wrote: > This is the output from building varnish 3.0.1 on 8.2-RELEASE. I > recently built 3.0.0 without any problems. > > /bin/sh ../../libtool --tag=CC --mode=link cc -std=gnu99 -O2 -pipe > -march=nocona -fno-strict-aliasing -D_THREAD_SAFE -pthread -Wextra > -Wno-missing-field-initializers -Wno-sign-compare -o varnishadm > varnishadm-varnishadm.o varnishadm-assert.o varnishadm-tcp.o > varnishadm-vss.o ../../lib/libvarnishapi/libvarnishapi.la > ../../lib/libvarnishcompat/libvarnishcompat.la -ledit -lm > libtool: link: cc -std=gnu99 -O2 -pipe -march=nocona > -fno-strict-aliasing -D_THREAD_SAFE -pthread -Wextra > -Wno-missing-field-initializers -Wno-sign-compare -o .libs/varnishadm > varnishadm-varnishadm.o varnishadm-assert.o varnishadm-tcp.o > varnishadm-vss.o ../../lib/libvarnishapi/.libs/libvarnishapi.so > -L/usr/local/lib /usr/local/lib/libpcre.so > ../../lib/libvarnishcompat/.libs/libvarnishcompat.so -ledit -lm > -pthread -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath > -Wl,/usr/local/lib/varnish > varnishadm-varnishadm.o(.text+0x79): In function `cli_write': > : undefined reference to `rl_callback_handler_remove' > varnishadm-varnishadm.o(.text+0x706): In function `main': > : undefined reference to `rl_already_prompted' > varnishadm-varnishadm.o(.text+0x728): In function `main': > : undefined reference to `rl_callback_handler_install' > varnishadm-varnishadm.o(.text+0x86e): In function `main': > : undefined reference to `rl_forced_update_display' > varnishadm-varnishadm.o(.text+0x881): In function `main': > : undefined reference to `rl_callback_read_char' > varnishadm-varnishadm.o(.text+0x8c5): In function `main': > : undefined reference to `rl_callback_handler_remove' > varnishadm-varnishadm.o(.text+0x8d9): In function `main': > : undefined reference to `rl_callback_handler_install' > varnishadm-varnishadm.o(.text+0x93c): In function `main': > : undefined reference to `rl_callback_handler_remove' > varnishadm-varnishadm.o(.text+0x97d): In function `send_line': > : undefined reference to `rl_callback_handler_remove' > varnishadm-varnishadm.o(.text+0x978): In function `send_line': > : undefined reference to `add_history' > gmake[3]: *** [varnishadm] Error 1 > gmake[3]: Leaving directory > `/usr/obj/usr/ports/www/varnish/work/varnish-3.0.1/bin/varnishadm' > gmake[2]: *** [all-recursive] Error 1 > gmake[2]: Leaving directory > `/usr/obj/usr/ports/www/varnish/work/varnish-3.0.1/bin' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/obj/usr/ports/www/varnish/work/varnish-3.0.1' > gmake: *** [all] Error 2 > *** Error code 1 > > -- > chs, > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" -- Anders. From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 14:20:47 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 859B0106564A; Wed, 31 Aug 2011 14:20:47 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward13.mail.yandex.net (forward13.mail.yandex.net [IPv6:2a02:6b8:0:801::3]) by mx1.freebsd.org (Postfix) with ESMTP id 8A6D78FC12; Wed, 31 Aug 2011 14:20:46 +0000 (UTC) Received: from smtp13.mail.yandex.net (smtp13.mail.yandex.net [95.108.130.68]) by forward13.mail.yandex.net (Yandex) with ESMTP id B60E8142D5E; Wed, 31 Aug 2011 18:20:44 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314800444; bh=bkpw2fsTrV5rZrBVXo2I6AyrmUY0bZZCtiXMzaQWBqI=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=mnCvBrWNtjJO/CFyy/bM27JrBuTkQg/8Dw2UpsVRg1Yx5gXPSs55vdGSNrHrBCTd1 Dgf4yx8ws+YAULdAbjSHY8EIqtX3i9ou+qioEu5hnk6iFByEdhN5Snm+PE6l4Jd9vw rq5+FX9btiMY81Jcc31oJT8ZG/fmnnWEou+LlMWc= Received: from smtp13.mail.yandex.net (localhost [127.0.0.1]) by smtp13.mail.yandex.net (Yandex) with ESMTP id 83227E40015; Wed, 31 Aug 2011 18:20:44 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp13.mail.yandex.net (nwsmtp/Yandex) with ESMTP id Kim4mYwM; Wed, 31 Aug 2011 18:20:44 +0400 X-Yandex-Spam: 1 Message-ID: <4E5E4338.7070607@yandex.ru> Date: Wed, 31 Aug 2011 18:20:40 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: wen heping References: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> <4E5E3364.7050308@yandex.ru> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, acm@freebsd.org, perryh@pluto.rain.com, cwhiteh@onetel.com Subject: Re: editors/zim X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 14:20:47 -0000 wen heping wrote on 31.08.2011 18:00: > 2011/8/31 Ruslan Mahmatkhanov: >> perryh@pluto.rain.com wrote on 31.08.2011 09:29: >>> >>> Forwarding to ports@, which seems more likely to yield an answer to >>> this particular inquiry than questions@ >>> >>> Please keep the OP, who is probably not subscribed to ports@, in the >>> Cc: list. >>> >>> ==================================================================== >>> >>> Date: Tue, 30 Aug 2011 13:52:12 +0100 >>> From: Chris Whitehouse >>> To: User Questions >>> Subject: editors/zim >>> >>> Hi, >>> >>> I have a problem with Zim which I wrote to the author about he >>> replied and said; >>> >>> "I'm afraid version 0.29 is no longer supported. This was the last >>> version in the Perl branch, since we moved to Python there have been >>> already 10 more releases. So please try the latest version (0.52)." >>> >>> Are there any plans to bump it to Python and a recent release? >>> I emailed the maintainer a while back but got no response. >>> >>> thanks >>> >>> Chris >> >> Here is: >> >> a) diff to a previous port: >> http://happy-nation.by.ru/ports/zim-0.52.diff.txt >> b) updated port tarball: >> http://happy-nation.by.ru/ports/zim-0.52.tgz.txt > > Great work! > > It build well on my tb: > http://wen.freebsd.your.org/tb/index.php?action=describe_port&id=1635 > > wen Thanks for that. """ ===> Applying FreeBSD patches for zim-0.52 I can't seem to find a patch in there anywhere. ===> Ignoring patchfile /a/ports/editors/zim/files/patch-Build.PL.orig """ It seems you forget to remove files/ subdirectory (or patch -p0) """No handlers could be found for logger "zim.fs"""" This can be avoided too, but i it will be hacky and i actually don't this it worth too. > > > > >> >> (Just rename it to zim-0.52.tgz and unpack instead of current zim port >> directory). >> >> It works fine to me. Please test and report back is all is alright. If it >> does, i'll sent problem report to update it in teh tree. >> >> -- >> Regards, >> Ruslan >> >> Tinderboxing kills... the drives. -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 14:29:09 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E32F106566B; Wed, 31 Aug 2011 14:29:09 +0000 (UTC) (envelope-from wenheping@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 24E108FC12; Wed, 31 Aug 2011 14:29:08 +0000 (UTC) Received: by qyk9 with SMTP id 9so518476qyk.13 for ; Wed, 31 Aug 2011 07:29:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Y2zfske6ncl295gbvRWfXWF290RE8Ou7IW9JQ9BkVaM=; b=w7TWO2PiBWkjjTFHSiy4e+fBn/N1LdOBi3t5No1bdEMomOV6oNICbxObWuzmAD0BgK tn1ubmraZZ4EGDAUUKRPSQKDXNqFn15tKFxmq0N5HPLa7VfRzOsaCQ1lJ/JupEoqnS/C fPF/xm/z0fiGb7pap56OZqBduOq4E3rkpnVBc= MIME-Version: 1.0 Received: by 10.224.199.6 with SMTP id eq6mr311575qab.260.1314799243728; Wed, 31 Aug 2011 07:00:43 -0700 (PDT) Received: by 10.224.20.15 with HTTP; Wed, 31 Aug 2011 07:00:43 -0700 (PDT) In-Reply-To: <4E5E3364.7050308@yandex.ru> References: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> <4E5E3364.7050308@yandex.ru> Date: Wed, 31 Aug 2011 22:00:43 +0800 Message-ID: From: wen heping To: Ruslan Mahmatkhanov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: ports@freebsd.org, acm@freebsd.org, perryh@pluto.rain.com, cwhiteh@onetel.com Subject: Re: editors/zim X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 14:29:09 -0000 2011/8/31 Ruslan Mahmatkhanov : > perryh@pluto.rain.com wrote on 31.08.2011 09:29: >> >> Forwarding to ports@, which seems more likely to yield an answer to >> this particular inquiry than questions@ >> >> Please keep the OP, who is probably not subscribed to ports@, in the >> Cc: list. >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >> Date: Tue, 30 Aug 2011 13:52:12 +0100 >> From: Chris Whitehouse >> To: User Questions >> Subject: editors/zim >> >> Hi, >> >> I have a problem with Zim which I wrote to the author about he >> replied and said; >> >> "I'm afraid version 0.29 is no longer supported. This was the last >> version in the Perl branch, since we moved to Python there have been >> already 10 more releases. So please try the latest version (0.52)." >> >> Are there any plans to bump it to Python and a recent release? >> I emailed the maintainer a while back but got no response. >> >> thanks >> >> Chris > > Here is: > > a) diff to a previous port: > =C2=A0 http://happy-nation.by.ru/ports/zim-0.52.diff.txt > b) updated port tarball: > =C2=A0 http://happy-nation.by.ru/ports/zim-0.52.tgz.txt Great work! It build well on my tb: http://wen.freebsd.your.org/tb/index.php?action=3Ddescribe_port&id=3D1635 wen > > (Just rename it to zim-0.52.tgz and unpack instead of current zim port > directory). > > It works fine to me. Please test and report back is all is alright. If it > does, i'll sent problem report to update it in teh tree. > > -- > Regards, > Ruslan > > Tinderboxing kills... the drives. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 14:34:47 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F3CF106566B for ; Wed, 31 Aug 2011 14:34:47 +0000 (UTC) (envelope-from lars@larseighner.com) Received: from mail.team1internet.com (mail.team1internet.com [216.110.13.10]) by mx1.freebsd.org (Postfix) with ESMTP id 42AE18FC16 for ; Wed, 31 Aug 2011 14:34:46 +0000 (UTC) Received: from larseighner.com (unknown [216.110.13.73]) by mail.team1internet.com (Postfix) with SMTP id 3682C16B50E for ; Wed, 31 Aug 2011 09:09:26 -0500 (CDT) Received: by larseighner.com (nbSMTP-1.00) for uid 1001 lars@larseighner.com; Wed, 31 Aug 2011 09:08:59 -0500 (CDT) Date: Wed, 31 Aug 2011 09:08:58 -0500 (CDT) From: Lars Eighner X-X-Sender: lars@noos.6dollardialup To: freebsd-ports Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Subject: Zgv on AMD64 - Will computer blow up X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 14:34:47 -0000 So zgv 5.9 in the 8.2R ports is marked i386. I commented the ONLY_FOR_ARCHS line. It compiles and seems to run like a charm in amd64. Will my computer blow up? -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 15:27:08 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37681106564A; Wed, 31 Aug 2011 15:27:08 +0000 (UTC) (envelope-from glarkin@FreeBSD.org) Received: from mail1.sourcehosting.net (mail1.sourcehosting.net [74.205.51.45]) by mx1.freebsd.org (Postfix) with ESMTP id 09A328FC0A; Wed, 31 Aug 2011 15:27:07 +0000 (UTC) Received: from 68-189-245-235.dhcp.oxfr.ma.charter.com ([68.189.245.235] helo=cube.entropy.prv) by mail1.sourcehosting.net with esmtp (Exim 4.73 (FreeBSD)) (envelope-from ) id 1QymgI-000ELM-Au; Wed, 31 Aug 2011 11:26:28 -0400 Received: from v104.entropy.prv (v104.entropy.prv [192.168.1.104]) by cube.entropy.prv (Postfix) with ESMTP id 407D5521F87E; Wed, 31 Aug 2011 11:27:01 -0400 (EDT) Message-ID: <4E5E52C4.4090308@FreeBSD.org> Date: Wed, 31 Aug 2011 11:27:00 -0400 From: Greg Larkin Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.20) Gecko/20110804 Lightning/1.0b2 Thunderbird/3.1.12 MIME-Version: 1.0 To: Ruslan Mahmatkhanov References: <4E5CE015.70803@FreeBSD.org> <4E5CE7BB.8050808@yandex.ru> <4E5CEC1E.5010209@FreeBSD.org> <4E5CF2FF.5080302@yandex.ru> <4E5D42FC.6060600@FreeBSD.org> <4E5D4750.2010507@yandex.ru> In-Reply-To: <4E5D4750.2010507@yandex.ru> X-Enigmail-Version: 1.1.1 OpenPGP: id=1C940290 X-SA-Exim-Connect-IP: 68.189.245.235 X-SA-Exim-Mail-From: glarkin@FreeBSD.org X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail1.sourcehosting.net X-Spam-Level: *** X-Spam-Status: No, score=3.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RCVD_IN_RP_RNBL, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC, TVD_RCVD_IP autolearn=no version=3.3.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail1.sourcehosting.net) Cc: FreeBSD Ports Mailing List , miwi@FreeBSD.org Subject: Re: Python min version bumped from 2.4+ to 2.5+ X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: glarkin@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 15:27:08 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 8/30/11 4:25 PM, Ruslan Mahmatkhanov wrote: > Greg Larkin wrote on 31.08.2011 00:07: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 8/30/11 10:26 AM, Ruslan Mahmatkhanov wrote: >>> Greg Larkin wrote on 30.08.2011 17:56: >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA1 >>>> >>>> On 8/30/11 9:38 AM, Ruslan Mahmatkhanov wrote: >>>>> Greg Larkin wrote on 30.08.2011 17:05: >>>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>>> Hash: SHA1 >>>>>> >>>>>> Hi Martin, >>>>>> >>>>>> I have a question about a commit you made in February 2011: >>>>>> http://www.freshports.org/commit.php?message_id=201102250750.p1P7ofDg016541@repoman.freebsd.org&files=yes >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Part of the commit changed: >>>>>> >>>>>> USE_PYTHON= 2.4+ >>>>>> >>>>>> to >>>>>> >>>>>> USE_PYTHON= 2.5+ >>>>>> >>>>>> Was there a specific reason for doing so? I am running various >>>>>> tinderbox builds to check on port usage of the USE_PYTHON >>>>>> variable, and >>>>>> I noticed that devel/py-setuptools no longer builds if Python 2.4 is >>>>>> selected. >>>>>> >>>>>> I'd like to restore that capability, but before I send a PR, I >>>>>> wanted to >>>>>> check with you first. >>>>>> >>>>>> Thank you, >>>>>> Greg >>>>>> - -- >>>>>> Greg Larkin >>>>>> >>>>>> http://www.FreeBSD.org/ - The Power To Serve >>>>>> http://www.sourcehosting.net/ - Ready. Set. Code. >>>>>> http://twitter.com/cpucycle/ - Follow you, follow me >>>>> >>>>> I'm sorry for sail in, but i think that the reason is that python24 is >>>>> reached it's EOL long time ago. Actually the only supported python >>>>> releases atm according to python.org are - 2.7.2 and 3.2.1, and >>>>> developers highly encourages the users to move to this versions. >>>>> >>>>> 2.5 and 2.6 are in security-fix-only mode, there will be no ANY >>>>> releases >>>>> for this branches after October 2011 and October 2013 respectively, >>>>> while 2.4 does not get security-fixes even. >>>>> >>>>> There is also this answer from Martin in this pr: >>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/155526: >>>>> >>>>> python24 goes to the end of month, this port is on the todo for >>>>> removal >>>>> >>>> >>>> Hi Ruslan, >>> >>> Hi Greg >>> >>>> >>>> Ok, thank you for the explanation. Shall I mark python24 for removal >>>> from the tree or file a PR for python@ to do it? >>> >>> It's not so easy actually, since we have many ports in the tree that >>> still depend on 2.4 (notably all that zope/plone stuff) and i believe it >>> was the reason why python24 still not be removed in the first place. >>> I do some work about eliminating python24 usage in the tree (yesterdays >>> py-pysqlite2x stuff - one of it), but it's not that fast. I also working >>> on porting zope2.13/plone4 (that supports python 2.6 and 2.7) and i'm >>> planing to finish it this weekend after proper testing. After that we >>> can deprecate/remove existing zope/plone (not longer supported >>> upstream). >> >> Ok, it's a bigger job than I realized! >> >>> >>>> >>>> FYI, I have been running tinderbox builds with PYTHON_VERSION and >>>> PYTHON_DEFAULT_VERSION set to python2.4, python2.5, etc. to find out if >>>> ports with USE_PYTHON=yes need to be constrained a bit more. >>> >>> Yes, there is a lot of work. We have USE_PYTHON with bogus values like >>> 1.5+, 1.6+, 2.0+ etc :). And most of python ports will not work with >>> python3x so they should be constrained with -2.7 too. >> >> Do you think it's helpful then to run these builds with different Python >> versions enforced? I thought that getting the version ranges in the >> USE_PYTHON variable tightened up might help reduce the number of folks >> who run into build problems. I would like to do the same thing with >> Perl, GCC, and others. > > I, personally, believe that this almost can't help to identify > version-specific problems, since commonly there is almost no build > problems on different python versions (it's rarely when setup.py > actually checking which python version it was run with). The problems > arises on runtime stage, when apps starting to import modules, that may > not exist in this particular python version or that installed by missing > dependencies, etc. Such problems may be identified only with manual > checking/greping/app docs reading. But this is just my point. > You'd better to ask Martin - he is committer that skilled with python > stuff in ports, and i'm not proper person to take responsibility for > decisions like that :). I just can to sound my point on this. However, > it definitely will help to identify gcc version-specific build problems. I have found some build problems with ports that use USE_PYTHON=yes instead of restricting it to a specific version, e.g. > copying build/lib/mpd.py -> /usr/local/lib/python2.4/site-packages > byte-compiling /usr/local/lib/python2.4/site-packages/mpd.py to mpd.pyc > File "/usr/local/lib/python2.4/site-packages/mpd.py", line 293 > yield retval() > SyntaxError: 'yield' not allowed in a 'try' block with a 'finally' clause > writing byte-compilation script '/tmp/tmpoLWlQC.py' > /usr/local/bin/python2.4 -O /tmp/tmpoLWlQC.py > File "/usr/local/lib/python2.4/site-packages/mpd.py", line 293 > yield retval() > SyntaxError: 'yield' not allowed in a 'try' block with a 'finally' clause > removing /tmp/tmpoLWlQC.py > /bin/mkdir -p /usr/local/share/doc/py24-mpd Admittedly, this particular error was encountered while using Python 2.4 as the default version, but I plan to run builds with all of the other versions looking for similar build problems. Regards, Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5eUsQACgkQ0sRouByUApAF1ACdE1AbE5ARnnL8n7eVLbC9iQeW qH0An2UQChPo0ezhPBsIt5a3PmlGYe1D =4OEZ -----END PGP SIGNATURE----- From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 15:50:32 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBB68106564A for ; Wed, 31 Aug 2011 15:50:32 +0000 (UTC) (envelope-from nospam@flipmode.dk) Received: from smtp.fullrate.dk (smtp.fullrate.dk [90.185.1.42]) by mx1.freebsd.org (Postfix) with ESMTP id A1E6A8FC0C for ; Wed, 31 Aug 2011 15:50:32 +0000 (UTC) Received: from [192.168.4.179] (0604ds1-oel.1.fullrate.dk [90.184.211.141]) by smtp.fullrate.dk (Postfix) with ESMTP id 7F0779D02E for ; Wed, 31 Aug 2011 17:33:22 +0200 (CEST) Message-ID: <4E5E5441.3020109@flipmode.dk> Date: Wed, 31 Aug 2011 17:33:21 +0200 From: Carsten Jensen User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Thunderbird/3.1.12 MIME-Version: 1.0 To: ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: rid.so missing in samba34/35 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 15:50:32 -0000 Hello. I've just compiled samba35 from ports with the extra config settings ADS/SWAT/DNSUPDATE, no default settings were removed. After joining the samba as a stand alone server in a windows AD. settings in smb.conf are idmap backend = rid:domain=15000-20000 (edit: idmap_rid:... is deprecated in 3.5) idmap uid = 15000-20000 the samba backend doesn't seem to work, as I get a user/password auth box on the windows computers when trying to connect. looking in the logs I get the error message "failed to open /usr/local/lib/samba/idmap/rid.so" as the file doesn't exist there. I noticed this folder was empty for 3.4, but had some modules there in 3.5 (which ones, I don't remember now) running FreeBSD 8.2 AMD64 anyone know if this is missing from ports, compile issue or.. ?? cheers Carsten From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 16:01:17 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A821106564A for ; Wed, 31 Aug 2011 16:01:17 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 99E708FC08 for ; Wed, 31 Aug 2011 16:01:16 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QynE5-000M3i-ID for ports@freebsd.org; Wed, 31 Aug 2011 18:01:17 +0200 Date: Wed, 31 Aug 2011 18:01:17 +0200 From: Kurt Jaeger To: ports@freebsd.org Message-ID: <20110831160117.GK28186@home.opsec.eu> References: <4E5E5441.3020109@flipmode.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E5E5441.3020109@flipmode.dk> Cc: Subject: Re: rid.so missing in samba34/35 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 16:01:17 -0000 Hi! > I've just compiled samba35 from ports with the extra config settings > ADS/SWAT/DNSUPDATE, no default settings were removed. I looked at the port and http://www.linuxhacker.at/bugs/all/hoary-samba-idmap-rid.so-error Maybe this works: do a make config and add with experimental modules to the modules to compile with. Recompile, try again. This should produce/install an idmap/rid.so file ? I'm not sure whether this error message solves your problem. > looking in the logs I get the error message "failed to open > /usr/local/lib/samba/idmap/rid.so" as the file doesn't exist there. > I noticed this folder was empty for 3.4, but had some modules there in > 3.5 (which ones, I don't remember now) > > running FreeBSD 8.2 AMD64 > > anyone know if this is missing from ports, compile issue or.. ?? -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 16:11:16 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8997106564A for ; Wed, 31 Aug 2011 16:11:16 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 94B348FC13 for ; Wed, 31 Aug 2011 16:11:16 +0000 (UTC) Received: by iadx2 with SMTP id x2so1219453iad.13 for ; Wed, 31 Aug 2011 09:11:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=7/maHXPPl+0CG0D+whIlHFfWhzNqfHmtkcNCkR5C1iE=; b=xGaNrsyUwGpB9vbw8lNj4YHam7Czx/OFmyKYUX8tBZr6fX8e87625+bR0jb9gX8+un ns5cWoNYRQpsNYS8lGhYj4+wKD0e8bE818YvpIIn3KmDe5ixyfRiTS45Wx14RMUct3wC sTVxoIQRQzmTSwavuk2G2waiHEvT7WKdIGM6A= Received: by 10.231.66.85 with SMTP id m21mr997302ibi.53.1314807076121; Wed, 31 Aug 2011 09:11:16 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.61.148 with HTTP; Wed, 31 Aug 2011 09:10:46 -0700 (PDT) In-Reply-To: References: From: Chris Rees Date: Wed, 31 Aug 2011 17:10:46 +0100 X-Google-Sender-Auth: No4REiyMXE4YI2U_7hQxqWjMV2g Message-ID: To: Lars Eighner Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ports Subject: Re: Zgv on AMD64 - Will computer blow up X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 16:11:16 -0000 On 31 August 2011 15:08, Lars Eighner wrote: > > So zgv 5.9 in the 8.2R ports is marked i386. =A0I commented the > ONLY_FOR_ARCHS line. =A0It compiles and seems to run like a charm > in amd64. =A0Will my computer blow up? Perhaps you should look upstream to see. The original port had that line 7 years ago, it's possible times have chang= ed ;) http://www.freebsd.org/cgi/query-pr.cgi?pr=3D65577 Chris From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 16:27:12 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 458551065670; Wed, 31 Aug 2011 16:27:12 +0000 (UTC) (envelope-from gahr@gahr.no-ip.org) Received: from cpanel05.rubas-s05.net (cpanel05.rubas-s05.net [195.182.222.75]) by mx1.freebsd.org (Postfix) with ESMTP id B0B1B8FC20; Wed, 31 Aug 2011 16:27:11 +0000 (UTC) Received: from 175-3.192-178.cust.bluewin.ch ([178.192.3.175] helo=gahr.no-ip.org) by cpanel05.rubas-s05.net with esmtpa (Exim 4.69) (envelope-from ) id 1QymOH-0004Iy-UU; Wed, 31 Aug 2011 17:07:45 +0200 Received: by gahr.no-ip.org (Postfix, from userid 1001) id 6F9554505F; Wed, 31 Aug 2011 17:07:45 +0200 (CEST) Date: Wed, 31 Aug 2011 17:07:45 +0200 From: Pietro Cerutti To: Beech Rintoul , freebsd-ports@FreeBSD.org Message-ID: <20110831150744.GI45443@gahrfit.gahr.ch> References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5D26E2.7040300@gmx.de> <201108301345.25661.beech@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="c7hkjup166d4FzgN" Content-Disposition: inline In-Reply-To: <201108301345.25661.beech@freebsd.org> X-PGP-Key: 0x9571F78E X-PGP-Fingerprint: 1203 92B5 3919 AF84 9B97 28D6 C0C2 6A98 9571 F78E User-Agent: Mutt/1.5.21 (2010-09-15) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cpanel05.rubas-s05.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - gahr.no-ip.org X-Source: X-Source-Args: X-Source-Dir: Cc: Matthias Andree , Ted Hatfield Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gahr@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 16:27:12 -0000 --c7hkjup166d4FzgN Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2011-Aug-30, 13:45, Beech Rintoul wrote: > On Tuesday 30 August 2011 11:01:18 Ted Hatfield wrote: > > On Tue, 30 Aug 2011, Matthias Andree wrote: > > > Am 30.08.2011 19:57, schrieb Mark Linimon: > > >> On Tue, Aug 30, 2011 at 07:44:12PM +0200, Matthias Andree wrote: > > >>> It only warns, it does not prevent fresh installs on systems that d= on't > > >>> have the same port/package already installed. > > >>=20 > > >> "code, not policy" ... ? > > >=20 > > > Well... is _is_ policy and meant as such. We make decisions for ports > > > users all the time, and this is no exception. > >=20 > > If procmail has no ongoing security issues and it compiles and installs > > with no problems what's the reasoning behind removing it from the ports > > tree? > >=20 > > As far as I can see the reasoning advocated at this time is that > > procmail hasn't been in active development since 2001. Shouldn't that > > be seen as a sign of stability. > >=20 > > I'm not a software developer so maybe I'm missing something obvious > > about this situation. Feel free to educate/convice me that I should > > make the effort to switch from procmail to maildrop. > >=20 > > I've been using procmail now for 16 years and I'm very happy with it's > > performance. Moving to maildrop would be a significant amount of effort > > for both me and my users. > >=20 > > Ted Hatfield >=20 > I second that, I also have it installed in several places and haven't had= any=20 > problems. I don't want to have to move to another app just because someon= e=20 > feels like deprecating a mature port. I think the old addage "if it ain't= =20 > broke" applies here. +1 here! Please stop this deprecation madness and stop thinking that our users are a bunch of stupids. I use procmail daily and I don't have any problems with it. If we want to deprecate ports basing on the potential damage caused by their misuse, I'd start with everything prefixed with lang/ or devel/. --=20 Pietro Cerutti The FreeBSD Project gahr@FreeBSD.org PGP Public Key: http://gahr.ch/pgp --c7hkjup166d4FzgN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk5eTj8ACgkQwMJqmJVx9455JgCglpiC3kLOEJcx8DvWFGowfQ7l gsMAniKBZSJ7mQxEfhdkq7aduGgtG70n =b4eu -----END PGP SIGNATURE----- --c7hkjup166d4FzgN-- From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 16:48:36 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C2DF106566B; Wed, 31 Aug 2011 16:48:36 +0000 (UTC) (envelope-from beech@freebsd.org) Received: from bsdevel2.freebsdnorth.com (unknown [IPv6:2001:470:7:d77::2]) by mx1.freebsd.org (Postfix) with ESMTP id EE7B58FC13; Wed, 31 Aug 2011 16:48:35 +0000 (UTC) Received: from maximum3.maximumdata.biz (akbeech-2-pt.tunnel.tserv14.sea1.ipv6.he.net [IPv6:2001:470:a:2e9::2]) by bsdevel2.freebsdnorth.com (Postfix) with ESMTP id 4C202C3A9F; Tue, 30 Aug 2011 16:43:32 +0000 (UTC) From: Beech Rintoul Organization: FreeBSD To: freebsd-ports@freebsd.org Date: Wed, 31 Aug 2011 08:48:33 -0800 User-Agent: KMail/1.13.7 (FreeBSD/9.0-BETA2; KDE/4.6.5; i386; ; ) References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5D0856.8080505@FreeBSD.org> <20110831023748.704a9edb@cox.net> In-Reply-To: <20110831023748.704a9edb@cox.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1914077.21XkLfqOP4"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201108310848.33692.beech@freebsd.org> Cc: "Conrad J. Sabatier" , Matthias Andree Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 16:48:36 -0000 --nextPart1914077.21XkLfqOP4 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Tuesday 30 August 2011 23:37:48 Conrad J. Sabatier wrote: > On Tue, 30 Aug 2011 17:57:10 +0200 >=20 > Matthias Andree wrote: > > I understand that keeping unchanging software can sometimes be > > necessary, if you're working around its quirks. > >=20 > > At the same time I'd like to discourage new installations of dead > > software so that it disappears over time, rather than haunt fresh > > systems. This passive idea will do nothing but generate a lot of confusion. If a por= t=20 is actually broken then it should be either fixed or deprecated with the=20 proper advance notice. The idea of a port that disappears over time will ca= tch=20 a lot of users unprepared. This whole issue has been addressed by portmgr o= n=20 several occasions that I can remember and the consensus was to leave alone= =20 mature working ports. As for procmail, has anyone bothered to talk to the=20 maintainer? >=20 > That makes perfect sense, yes. >=20 > > How about if we added a new tag "OBSOLESCENT" or so that permits > > building the software only if it's already installed but refuses new > > installations? Of course there could be a switch to override that, > > like TRYBROKEN that can override BROKEN=3D tags. We don't need another tag even if it can be overridden. We already have a=20 method of dealing with "dead" ports. >=20 > You had me on the edge of my seat for a while there, talking about > removing my beloved procmail. Now this suggestion I could easily live > with. :-) >=20 > > I'm not sure if it's feasible for packages (but OBSOLESCENT could > > imply "do not package") but for ports it would be possible. >=20 > I like it. :-) I don't! Beech =2D-=20 =2D------------------------------------------------------------------------= =2D------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/8.2R/announce.html =2D------------------------------------------------------------------------= =2D------------- --nextPart1914077.21XkLfqOP4 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEABECAAYFAk5eZeEACgkQFrTqt+y/3EQwYQCfSgGE/2TasTG1wwSGdP0f8OWI r9YAn0Ken97L949ScqksryP0CTBoC3iQ =UKO3 -----END PGP SIGNATURE----- --nextPart1914077.21XkLfqOP4-- From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 17:06:28 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54B40106564A for ; Wed, 31 Aug 2011 17:06:28 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by mx1.freebsd.org (Postfix) with ESMTP id DBA698FC0C for ; Wed, 31 Aug 2011 17:06:27 +0000 (UTC) Received: from p5796f14c.dip.t-dialin.net ([87.150.241.76] helo=krabat.raven.hur) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1QyoF7-0005N8-LZ; Wed, 31 Aug 2011 19:06:25 +0200 Message-ID: <4E5E6A0E.9070100@gwdg.de> Date: Wed, 31 Aug 2011 19:06:22 +0200 From: Rainer Hurling User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110825 Thunderbird/6.0 MIME-Version: 1.0 To: Johan Hendriks References: <6C3F8332272B7D4DA26909F15F1C90E1E5CD3E@SRV01.double-l.local> In-Reply-To: <6C3F8332272B7D4DA26909F15F1C90E1E5CD3E@SRV01.double-l.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: "freebsd-ports@freebsd.org" Subject: Re: libproxy and libnotify the story continues :D X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 17:06:28 -0000 On 31.08.2011 11:14 (UTC+1), Johan Hendriks wrote: > Hello all, i also ran into the libproxy upgrade problems. > > So i tried al the stuff i found on the mailling list so far. > > I tried the solution from j.kim > > find /usr/local/lib -name "*.la" | \ > xargs grep -l /usr/local/lib/libproxy.la | \ > xargs -L 1 pkg_info -W | \ > awk '{ print $6 }' | \ > sort | \ > uniq | \ > xargs portupgrade -f > > But this ends like the following. > > /usr/include/machine/endian.h:130: syntax error, unexpected ';' in ' return (__extension__ ({ register __uint32_t __X = (_x); __asm ("bswap %0" : "+r" (__X)); __X; }));' at ';' > /libexec/ld-elf.so.1: Shared object "libproxy.so.0" not found, required by "libchamplain-0.8.so.1" > Command '['/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk/tmp-introspectpyOYLR/GtkChamplain-0.8', '--introspect-dump=/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk/tmp-introspectpyOYLR/types.txt,/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk/tmp-introspectpyOYLR/dump.xml']' returned non-zero exit status 1 > gmake[3]: *** [GtkChamplain-0.8.gir] Error 1 > gmake[3]: Leaving directory `/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk' > gmake[2]: *** [all] Error 2 > gmake[2]: Leaving directory `/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1' > gmake: *** [all] Error 2 > *** Error code 1 > > Stop in /usr/ports/graphics/libchamplain. > > I reinstalled libproxy, i reinstalled libgweather and so on, also the poor mans portmaster solution from doug. I had to deinstall libchamplain, rebuild and reinstall libchamplain (in this order!) and then could continue with the upgrade. libchamplain is not able to build if it is installed for some reason. Hope this helps, Rainer Hurling > But i can not get past this. > > Also did a recompile off all the evolution stuff, > Then tried portmaster lib* in the hope there was a library not installed ok, but that ends with the same error as above. > > I am struggling for a day or 4 now with this. > > Could someone please help me :D > > regards > Johan_______________________________________________ From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 17:08:16 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id DCF7A106564A; Wed, 31 Aug 2011 17:08:15 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 1CEC123CF4F; Wed, 31 Aug 2011 19:08:15 +0200 (CEST) Message-ID: <4E5E6A7E.3040606@FreeBSD.org> Date: Wed, 31 Aug 2011 19:08:14 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: Beech Rintoul References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5D26E2.7040300@gmx.de> <201108301345.25661.beech@freebsd.org> In-Reply-To: <201108301345.25661.beech@freebsd.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 17:08:17 -0000 Am 30.08.2011 23:45, schrieb Beech Rintoul: > I second that, I also have it installed in several places and haven't had any > problems. I don't want to have to move to another app just because someone > feels like deprecating a mature port. I think the old addage "if it ain't > broke" applies here. If everyone cared to read not just the past three posts but what was written earlier in this whole thread, and ceased adding to the meaningless "I've had no problems", that would help. Just because someone hasn't tripped over the bugs yet, is not a reason to keep a port known to have massive bugs. It's like security bugs, many people won't notice them and believe the software to be in proper working order until after it's too late. There's a difference between "mature" and abandoned-and-known-buggy. Not everything that hasn't changed in years is mature, there are a number of projects that have simply died and not been picked up by somebody else. From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 17:09:22 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44C86106566B for ; Wed, 31 Aug 2011 17:09:22 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by mx1.freebsd.org (Postfix) with ESMTP id 0497E8FC13 for ; Wed, 31 Aug 2011 17:09:21 +0000 (UTC) Received: from p5796f14c.dip.t-dialin.net ([87.150.241.76] helo=krabat.raven.hur) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1QyoHw-0005jE-Je; Wed, 31 Aug 2011 19:09:20 +0200 Message-ID: <4E5E6AC0.90708@gwdg.de> Date: Wed, 31 Aug 2011 19:09:20 +0200 From: Rainer Hurling User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110825 Thunderbird/6.0 MIME-Version: 1.0 To: Johan Hendriks References: <6C3F8332272B7D4DA26909F15F1C90E1E5CD3E@SRV01.double-l.local> <4E5E6A0E.9070100@gwdg.de> In-Reply-To: <4E5E6A0E.9070100@gwdg.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: "freebsd-ports@freebsd.org" Subject: Re: libproxy and libnotify the story continues :D X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 17:09:22 -0000 Oops, I just realized that this was answered in another mail from Michal Varga. Sorry for the noise. On 31.08.2011 19:06 (UTC+1), Rainer Hurling wrote: > On 31.08.2011 11:14 (UTC+1), Johan Hendriks wrote: >> Hello all, i also ran into the libproxy upgrade problems. >> >> So i tried al the stuff i found on the mailling list so far. >> >> I tried the solution from j.kim >> >> find /usr/local/lib -name "*.la" | \ >> xargs grep -l /usr/local/lib/libproxy.la | \ >> xargs -L 1 pkg_info -W | \ >> awk '{ print $6 }' | \ >> sort | \ >> uniq | \ >> xargs portupgrade -f >> >> But this ends like the following. >> >> /usr/include/machine/endian.h:130: syntax error, unexpected ';' in ' >> return (__extension__ ({ register __uint32_t __X = (_x); __asm ("bswap >> %0" : "+r" (__X)); __X; }));' at ';' >> /libexec/ld-elf.so.1: Shared object "libproxy.so.0" not found, >> required by "libchamplain-0.8.so.1" >> Command >> '['/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk/tmp-introspectpyOYLR/GtkChamplain-0.8', >> '--introspect-dump=/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk/tmp-introspectpyOYLR/types.txt,/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk/tmp-introspectpyOYLR/dump.xml']' >> returned non-zero exit status 1 >> gmake[3]: *** [GtkChamplain-0.8.gir] Error 1 >> gmake[3]: Leaving directory >> `/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk' >> gmake[2]: *** [all] Error 2 >> gmake[2]: Leaving directory >> `/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1/champlain-gtk' >> gmake[1]: *** [all-recursive] Error 1 >> gmake[1]: Leaving directory >> `/usr/ports/graphics/libchamplain/work/libchamplain-0.8.1' >> gmake: *** [all] Error 2 >> *** Error code 1 >> >> Stop in /usr/ports/graphics/libchamplain. >> >> I reinstalled libproxy, i reinstalled libgweather and so on, also the >> poor mans portmaster solution from doug. > > I had to deinstall libchamplain, rebuild and reinstall libchamplain (in > this order!) and then could continue with the upgrade. libchamplain is > not able to build if it is installed for some reason. > > Hope this helps, > Rainer Hurling > >> But i can not get past this. >> >> Also did a recompile off all the evolution stuff, >> Then tried portmaster lib* in the hope there was a library not >> installed ok, but that ends with the same error as above. >> >> I am struggling for a day or 4 now with this. >> >> Could someone please help me :D >> >> regards >> Johan_______________________________________________ From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 17:11:03 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 6492E106566B for ; Wed, 31 Aug 2011 17:11:03 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 9F89E23CF4F for ; Wed, 31 Aug 2011 19:11:02 +0200 (CEST) Message-ID: <4E5E6B26.4040007@FreeBSD.org> Date: Wed, 31 Aug 2011 19:11:02 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Mnenhy/0.8.3 Thunderbird/3.1.12 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <201108301524.p7UFOc6Q008169@fire.js.berklix.net> <4E5D0A77.3070304@FreeBSD.org> <20110831004337.2deb368e@lab.lovett.com> In-Reply-To: <20110831004337.2deb368e@lab.lovett.com> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 17:11:03 -0000 Am 31.08.2011 07:43, schrieb Ade Lovett: > On Tue, 30 Aug 2011 18:06:15 +0200 > Matthias Andree wrote: >> Once you have the necessary error handling in place in >> your .procmailrc, a .mailfilter file of equal usefulness in maildrop >> is shorter and more concise. > > 1. In the context of a FreeBSD port, there is absolutely nothing wrong > with mail/procmail as it stands. That is to say, it compiles and runs > on all supported OS releases and architectures. Which is insufficient in the light of known design flaws and bugs. > 3. Particularly when there's no magic tool to convert all > the .procmailrc's out there to mail/whizzy-new-thing. Cleaning up every 7 years or so is a good idea actually. > #3 is the important point. If you do want to send mail/procmail to the > great bitbucket in the sky, then please provide that magic tool. I'm > sure lots of folks will be willing to test it for you. OK. I've asked that on the courier-maildrop list. From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 17:15:58 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02C3E106566B for ; Wed, 31 Aug 2011 17:15:57 +0000 (UTC) (envelope-from cmeyer1969@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 508C38FC14 for ; Wed, 31 Aug 2011 17:15:57 +0000 (UTC) Received: by bkat8 with SMTP id t8so1436415bka.13 for ; Wed, 31 Aug 2011 10:15:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=ABEegIZcaBKOZgVu0m/TIIdbraGHshzhOGMl2XFif0w=; b=fBW5BlcO00S1UDh2n23g6922lADgYca8zB8llPDu3XBKGQD1IlYY5pQnwFxAQ2WoqT 8PrYFKcEj2KSrAVpcI83yE17wEnnWxif5yPF5MiFufAfjE1oU3gyNnlP0M3g12lOUmLB 6xD2R1Zjdo+CY+sZ2cA8G2bs9ol6DK2YnUBqE= MIME-Version: 1.0 Received: by 10.204.8.71 with SMTP id g7mr390726bkg.271.1314809608186; Wed, 31 Aug 2011 09:53:28 -0700 (PDT) Sender: cmeyer1969@gmail.com Received: by 10.204.10.88 with HTTP; Wed, 31 Aug 2011 09:53:28 -0700 (PDT) Date: Wed, 31 Aug 2011 09:53:28 -0700 X-Google-Sender-Auth: QOk9sTVx82-beutNaZf7E7W15wU Message-ID: From: Chris Meyer To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Where is php5-5.3.6? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 17:15:58 -0000 We need to upgrade to php5-5.3.6 or later for PCI compliance. When I check the ports list (http://www.freebsd.org/ports/lang.html), the latest version is php5-5.3.3. What happened to 5.3.6, which was released in March? From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 17:18:10 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F78E1065670; Wed, 31 Aug 2011 17:18:10 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward9.mail.yandex.net (forward9.mail.yandex.net [77.88.61.48]) by mx1.freebsd.org (Postfix) with ESMTP id E2E248FC18; Wed, 31 Aug 2011 17:18:09 +0000 (UTC) Received: from smtp8.mail.yandex.net (smtp8.mail.yandex.net [77.88.61.54]) by forward9.mail.yandex.net (Yandex) with ESMTP id 0E59BCE2F3C; Wed, 31 Aug 2011 21:02:54 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314810174; bh=/h9kESpkh5SAHz6u+ynb/g/+Rz806ue6+PCwsdvlEfk=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=JB86E+Y8HXSb7UMmN2U6nGNV3XW/EDWJZtAJQsKRgUwU1Z5a05l6OsAtwKRPsis+s G3topvEKUgLKNmtxXtfsaLCtRo75S2m6reFuBtc+SC1XrxUcdoieJIzv5iK6jg4W6/ xCo+whu7erbDfUKaGy6x827btVm3wGsJdL0aLWmA= Received: from smtp8.mail.yandex.net (localhost [127.0.0.1]) by smtp8.mail.yandex.net (Yandex) with ESMTP id E19551B603CD; Wed, 31 Aug 2011 21:02:53 +0400 (MSD) Received: from unknown (unknown [213.138.88.133]) by smtp8.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 2ra0co9b; Wed, 31 Aug 2011 21:02:53 +0400 X-Yandex-Spam: 1 Message-ID: <4E5E693A.8060608@yandex.ru> Date: Wed, 31 Aug 2011 21:02:50 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: glarkin@FreeBSD.org References: <4E5CE015.70803@FreeBSD.org> <4E5CE7BB.8050808@yandex.ru> <4E5CEC1E.5010209@FreeBSD.org> <4E5CF2FF.5080302@yandex.ru> <4E5D42FC.6060600@FreeBSD.org> <4E5D4750.2010507@yandex.ru> <4E5E52C4.4090308@FreeBSD.org> In-Reply-To: <4E5E52C4.4090308@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: FreeBSD Ports Mailing List , miwi@FreeBSD.org Subject: Re: Python min version bumped from 2.4+ to 2.5+ X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 17:18:10 -0000 Greg Larkin wrote on 31.08.2011 19:27: >>>>>>> Hi Martin, >>>>>>> >>>>>>> I have a question about a commit you made in February 2011: >>>>>>> http://www.freshports.org/commit.php?message_id=201102250750.p1P7ofDg016541@repoman.freebsd.org&files=yes >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Part of the commit changed: >>>>>>> >>>>>>> USE_PYTHON= 2.4+ >>>>>>> >>>>>>> to >>>>>>> >>>>>>> USE_PYTHON= 2.5+ >>>>>>> >>>>>>> Was there a specific reason for doing so? I am running various >>>>>>> tinderbox builds to check on port usage of the USE_PYTHON >>>>>>> variable, and >>>>>>> I noticed that devel/py-setuptools no longer builds if Python 2.4 is >>>>>>> selected. >>>>>>> >>>>>>> I'd like to restore that capability, but before I send a PR, I >>>>>>> wanted to >>>>>>> check with you first. >>>>>>> >>>>>>> Thank you, >>>>>>> Greg >>>>>>> - -- >>>>>>> Greg Larkin >>>>>>> >>>>>>> http://www.FreeBSD.org/ - The Power To Serve >>>>>>> http://www.sourcehosting.net/ - Ready. Set. Code. >>>>>>> http://twitter.com/cpucycle/ - Follow you, follow me >>>>>> >>>>>> I'm sorry for sail in, but i think that the reason is that python24 is >>>>>> reached it's EOL long time ago. Actually the only supported python >>>>>> releases atm according to python.org are - 2.7.2 and 3.2.1, and >>>>>> developers highly encourages the users to move to this versions. >>>>>> >>>>>> 2.5 and 2.6 are in security-fix-only mode, there will be no ANY >>>>>> releases >>>>>> for this branches after October 2011 and October 2013 respectively, >>>>>> while 2.4 does not get security-fixes even. >>>>>> >>>>>> There is also this answer from Martin in this pr: >>>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/155526: >>>>>> >>>>>> python24 goes to the end of month, this port is on the todo for >>>>>> removal >>>>>> >>>>> >>>>> Hi Ruslan, >>>> >>>> Hi Greg >>>> >>>>> >>>>> Ok, thank you for the explanation. Shall I mark python24 for removal >>>>> from the tree or file a PR for python@ to do it? >>>> >>>> It's not so easy actually, since we have many ports in the tree that >>>> still depend on 2.4 (notably all that zope/plone stuff) and i believe it >>>> was the reason why python24 still not be removed in the first place. >>>> I do some work about eliminating python24 usage in the tree (yesterdays >>>> py-pysqlite2x stuff - one of it), but it's not that fast. I also working >>>> on porting zope2.13/plone4 (that supports python 2.6 and 2.7) and i'm >>>> planing to finish it this weekend after proper testing. After that we >>>> can deprecate/remove existing zope/plone (not longer supported >>>> upstream). >>> >>> Ok, it's a bigger job than I realized! >>> >>>> >>>>> >>>>> FYI, I have been running tinderbox builds with PYTHON_VERSION and >>>>> PYTHON_DEFAULT_VERSION set to python2.4, python2.5, etc. to find out if >>>>> ports with USE_PYTHON=yes need to be constrained a bit more. >>>> >>>> Yes, there is a lot of work. We have USE_PYTHON with bogus values like >>>> 1.5+, 1.6+, 2.0+ etc :). And most of python ports will not work with >>>> python3x so they should be constrained with -2.7 too. >>> >>> Do you think it's helpful then to run these builds with different Python >>> versions enforced? I thought that getting the version ranges in the >>> USE_PYTHON variable tightened up might help reduce the number of folks >>> who run into build problems. I would like to do the same thing with >>> Perl, GCC, and others. >> >> I, personally, believe that this almost can't help to identify >> version-specific problems, since commonly there is almost no build >> problems on different python versions (it's rarely when setup.py >> actually checking which python version it was run with). The problems >> arises on runtime stage, when apps starting to import modules, that may >> not exist in this particular python version or that installed by missing >> dependencies, etc. Such problems may be identified only with manual >> checking/greping/app docs reading. But this is just my point. >> You'd better to ask Martin - he is committer that skilled with python >> stuff in ports, and i'm not proper person to take responsibility for >> decisions like that :). I just can to sound my point on this. However, >> it definitely will help to identify gcc version-specific build problems. > > I have found some build problems with ports that use USE_PYTHON=yes > instead of restricting it to a specific version, e.g. > >> copying build/lib/mpd.py -> /usr/local/lib/python2.4/site-packages >> byte-compiling /usr/local/lib/python2.4/site-packages/mpd.py to mpd.pyc >> File "/usr/local/lib/python2.4/site-packages/mpd.py", line 293 >> yield retval() >> SyntaxError: 'yield' not allowed in a 'try' block with a 'finally' clause >> writing byte-compilation script '/tmp/tmpoLWlQC.py' >> /usr/local/bin/python2.4 -O /tmp/tmpoLWlQC.py >> File "/usr/local/lib/python2.4/site-packages/mpd.py", line 293 >> yield retval() >> SyntaxError: 'yield' not allowed in a 'try' block with a 'finally' clause >> removing /tmp/tmpoLWlQC.py >> /bin/mkdir -p /usr/local/share/doc/py24-mpd > > Admittedly, this particular error was encountered while using Python 2.4 > as the default version, but I plan to run builds with all of the other > versions looking for similar build problems. > > Regards, > Greg Ok, this particular error is well known and 24-specific: http://docs.python.org/reference/simple_stmts.html """ As of Python version 2.5, the yield statement is now allowed in the try clause of a try ... finally construct. If the generator is not resumed before it is finalized (by reaching a zero reference count or by being garbage collected), the generator-iterator’s close() method will be called, allowing any pending finally clauses to execute. """ I checked the docs, i checked the code for audio/py-mpd - there is nothing about python versions. Authors just not assumed that anybody will try to run this code with 2.4. So may be it has the point to build such ports to check them. But i'd rather concentrate on eliminating explicit 24-specific consumers so we can deprecate lang/python24 to avoid such situations in principle. And however, now we know that the left edge for SUE_PYTHON for this port would be 2.5+, but what about the right edge? Even if it will builds successfully with 3.x in tinderbox run, who can guarantee that it will RUN with 3.x? -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 17:19:37 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E40D3106566B for ; Wed, 31 Aug 2011 17:19:37 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward7.mail.yandex.net (forward7.mail.yandex.net [IPv6:2a02:6b8:0:202::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6220D8FC16 for ; Wed, 31 Aug 2011 17:19:37 +0000 (UTC) Received: from smtp6.mail.yandex.net (smtp6.mail.yandex.net [77.88.61.56]) by forward7.mail.yandex.net (Yandex) with ESMTP id C278D1C170B; Wed, 31 Aug 2011 21:19:35 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314811175; bh=KbQTrY6JOk6baSgFTkzR+0YLxkmUIIrJe8rYEWUbjt4=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=uP/+LwT6yx805MX0lzGpIX45c0MgiAO5TI+wHtURJkJAhp2RxD1+DxDmP1O8puG3t ZkbWdTCqDtK0hsnLXgugMGUCAdmhpqw3jXfLQCshBX9u6JYAKs5HK0GmqWIzshsKpo xvPHDLipao0m5MiE3/pEVfk+M6UznL8FXkNKa2gE= Received: from smtp6.mail.yandex.net (localhost [127.0.0.1]) by smtp6.mail.yandex.net (Yandex) with ESMTP id AE37316403D5; Wed, 31 Aug 2011 21:19:35 +0400 (MSD) Received: from unknown (unknown [213.138.88.133]) by smtp6.mail.yandex.net (nwsmtp/Yandex) with ESMTP id JZOeuuRI; Wed, 31 Aug 2011 21:19:35 +0400 X-Yandex-Spam: 1 Message-ID: <4E5E6D24.3030802@yandex.ru> Date: Wed, 31 Aug 2011 21:19:32 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: Chris Meyer References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: Where is php5-5.3.6? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 17:19:38 -0000 Chris Meyer wrote on 31.08.2011 20:53: > We need to upgrade to php5-5.3.6 or later for PCI compliance. > > When I check the ports list (http://www.freebsd.org/ports/lang.html), > the latest version is php5-5.3.3. > > What happened to 5.3.6, which was released in March? It's 5.3.8 actually. You may consult with `make search name=php5` in the ports tree or, for example, there: http://www.freshports.org/lang/php5 It looks like this section on freebsd.org uses old INDEX file. -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 18:50:57 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41B03106566C; Wed, 31 Aug 2011 18:50:57 +0000 (UTC) (envelope-from cwhiteh@onetel.com) Received: from april.london.02.net (april.london.02.net [87.194.255.143]) by mx1.freebsd.org (Postfix) with ESMTP id EF28C8FC0A; Wed, 31 Aug 2011 18:50:56 +0000 (UTC) Received: from muji2.config (93.97.24.219) by april.london.02.net (8.5.140) id 4E261E720154AD08; Wed, 31 Aug 2011 19:34:18 +0100 Message-ID: <4E5E7EAA.4030303@onetel.com> Date: Wed, 31 Aug 2011 19:34:18 +0100 From: Chris Whitehouse User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100924 Thunderbird/3.1.4 MIME-Version: 1.0 To: ports@FreeBSD.org, acm@FreeBSD.org, Ruslan Mahmatkhanov , perryh@pluto.rain.com References: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> <4E5E3364.7050308@yandex.ru> In-Reply-To: <4E5E3364.7050308@yandex.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: editors/zim X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 18:50:57 -0000 On 31/08/2011 14:13, Ruslan Mahmatkhanov wrote: > perryh@pluto.rain.com wrote on 31.08.2011 09:29: >> Forwarding to ports@, which seems more likely to yield an answer to >> this particular inquiry than questions@ >> >> Please keep the OP, who is probably not subscribed to ports@, in the >> Cc: list. >> >> ==================================================================== >> >> Date: Tue, 30 Aug 2011 13:52:12 +0100 >> From: Chris Whitehouse >> To: User Questions >> Subject: editors/zim >> >> Hi, >> >> I have a problem with Zim which I wrote to the author about he >> replied and said; >> >> "I'm afraid version 0.29 is no longer supported. This was the last >> version in the Perl branch, since we moved to Python there have been >> already 10 more releases. So please try the latest version (0.52)." >> >> Are there any plans to bump it to Python and a recent release? >> I emailed the maintainer a while back but got no response. >> >> thanks >> >> Chris > > Here is: > > a) diff to a previous port: > http://happy-nation DOT by DOT ru/ports/zim-0.52.diff.txt > b) updated port tarball: > http://happy-nation DOT by DOT ru/ports/zim-0.52.tgz.txt > > (Just rename it to zim-0.52.tgz and unpack instead of current zim port > directory). > > It works fine to me. Please test and report back is all is alright. If > it does, i'll sent problem report to update it in teh tree. > Hi Ruslan, first thanks for an amazing quick response and to Perry for forwarding to the right place. On a tinderbox with src from a snapshot of 9.0-CURRENT and recent ports it builds fine, also on the host which has the same src and ports tree it builds and installs fine - but nothing happens when I run the command at least as non-root user. The prompt returns after a moment and that's it. There is no zim process running and ~/.zim is not created. Running as root there are some error messages which I can report if required which seem to relate to sqlite3. And there is a zim process but still no ~/.zim. Python on this machine is 2.7.2 However the computer I really want to run it on is running 8.1-RELEASE and ports from around Sept 2010. Python is version 2.6.6. That's my laptop and main day-to-day machine. I'm having problems with the more recent ports on the other machine in relation to nvidia driver and/or flash and/or firefox and would prefer not to upgrade the laptop until those are working. Here's what I did for the laptop. muji2# cd /usr/ports/editors/ muji2# mv zim zim-0.29 muji2# fetch http://happy-nation DOT by DOT ru/ports/zim-0.52.tgz.txt # munged by me as blocked by my ISP :( zim-0.52.tgz.txt 100% of 3476 B 11 MBps muji2# mv zim-0.52.tgz.txt zim-0.52.tgz muji2# tar xvf zim-0.52.tgz x zim/ x zim/Makefile x zim/distinfo x zim/pkg-descr x zim/pkg-plist muji2# cd zim muji2# ls Makefile distinfo pkg-descr pkg-plist muji2# pwd /usr/ports/editors/zim muji2# make ===> zim-0.52 cannot install: Unknown component pygobject. *** Error code 1 Stop in /usr/ports/editors/zim. muji2# pkg_info -Ix py py26-cairo-1.8.8_1 Python bindings for Cairo py26-coverage-3.4 Code coverage measurement for Python py26-gobject-2.21.1 Python bindings for GObject py26-gtk-2.17.0_4 A set of Python bindings for GTK+ py26-setuptools-0.6c11 Download, build, install, upgrade, and uninstall Python pac py26-tkinter-2.6.6_3 Python bindings to the Tk widget set py26-xdg-0.19 A python library to access freedesktop.org standards pysol-4.82_1 Solitaire game, written in Python pysol-sound-server-3.01_4 Python extension module to play sounds and background music python26-2.6.6 An interpreted object-oriented programming language xdpyinfo-1.1.0 Display information utility for X cheers Chris From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 19:00:12 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7047F106566C; Wed, 31 Aug 2011 19:00:12 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward7.mail.yandex.net (forward7.mail.yandex.net [IPv6:2a02:6b8:0:202::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9114D8FC12; Wed, 31 Aug 2011 19:00:11 +0000 (UTC) Received: from smtp7.mail.yandex.net (smtp7.mail.yandex.net [77.88.61.55]) by forward7.mail.yandex.net (Yandex) with ESMTP id 8FF761C04EC; Wed, 31 Aug 2011 23:00:08 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314817208; bh=LbavWt8tXhhf/e5Lism/6A4pp5YnNbCVHVHZgws84No=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=aCzbJi1UqSW3kJOSheHXv1hotd4VvqMVa7J81TShTSr8JQQOO5NmZid8GmBhha6kI 5cumQqFGRA/mo5gGYdaYgBQ1nm9RHebTj4uUELBfrCPPpQ6GsdrfpFhxpU1O+jEpmf 2/5tbrLkYbMHWLZM6nLhBuw0eOBYoF6TaeW8ndO8= Received: from smtp7.mail.yandex.net (localhost [127.0.0.1]) by smtp7.mail.yandex.net (Yandex) with ESMTP id 67B0A15803E1; Wed, 31 Aug 2011 23:00:08 +0400 (MSD) Received: from unknown (unknown [213.138.88.133]) by smtp7.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 08tu3x2K; Wed, 31 Aug 2011 23:00:08 +0400 X-Yandex-Spam: 1 Message-ID: <4E5E84B4.6040200@yandex.ru> Date: Wed, 31 Aug 2011 23:00:04 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: Chris Whitehouse References: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> <4E5E3364.7050308@yandex.ru> <4E5E7EAA.4030303@onetel.com> In-Reply-To: <4E5E7EAA.4030303@onetel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, acm@FreeBSD.org, perryh@pluto.rain.com Subject: Re: editors/zim X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 19:00:12 -0000 Chris Whitehouse wrote on 31.08.2011 22:34: > On 31/08/2011 14:13, Ruslan Mahmatkhanov wrote: >> perryh@pluto.rain.com wrote on 31.08.2011 09:29: >>> Forwarding to ports@, which seems more likely to yield an answer to >>> this particular inquiry than questions@ >>> >>> Please keep the OP, who is probably not subscribed to ports@, in the >>> Cc: list. >>> >>> ==================================================================== >>> >>> Date: Tue, 30 Aug 2011 13:52:12 +0100 >>> From: Chris Whitehouse >>> To: User Questions >>> Subject: editors/zim >>> >>> Hi, >>> >>> I have a problem with Zim which I wrote to the author about he >>> replied and said; >>> >>> "I'm afraid version 0.29 is no longer supported. This was the last >>> version in the Perl branch, since we moved to Python there have been >>> already 10 more releases. So please try the latest version (0.52)." >>> >>> Are there any plans to bump it to Python and a recent release? >>> I emailed the maintainer a while back but got no response. >>> >>> thanks >>> >>> Chris >> >> Here is: >> >> a) diff to a previous port: >> http://happy-nation DOT by DOT ru/ports/zim-0.52.diff.txt >> b) updated port tarball: >> http://happy-nation DOT by DOT ru/ports/zim-0.52.tgz.txt >> >> (Just rename it to zim-0.52.tgz and unpack instead of current zim port >> directory). >> >> It works fine to me. Please test and report back is all is alright. If >> it does, i'll sent problem report to update it in teh tree. >> > > Hi Ruslan, > > first thanks for an amazing quick response and to Perry for forwarding > to the right place. > > On a tinderbox with src from a snapshot of 9.0-CURRENT and recent ports > it builds fine, also on the host which has the same src and ports tree > it builds and installs fine - but nothing happens when I run the command > at least as non-root user. The prompt returns after a moment and that's > it. There is no zim process running and ~/.zim is not created. About ~/.zim. It now holds it's settings in ~/.config/zim and the actual data in ~/Notes (the name of notebook) by default. You also can run zim from gnome menu. > Running as root there are some error messages which I can report if > required which seem to relate to sqlite3. And there is a zim process but > still no ~/.zim. > Python on this machine is 2.7.2 And you are right - it uses databases/py-sqlite3 to hold the data, but i already have it installed so i overlooked it. Please try to install databases/py-sqlite3 first and report back if it helped. It obviously a missing dependency and i'll add it before submitting pr. Thanks for pointing this out. > > However the computer I really want to run it on is running 8.1-RELEASE > and ports from around Sept 2010. Python is version 2.6.6. That's my > laptop and main day-to-day machine. I'm having problems with the more > recent ports on the other machine in relation to nvidia driver and/or > flash and/or firefox and would prefer not to upgrade the laptop until > those are working. Ok, i understand. I'm using intel so can't actually help with this one. But i just saw that nvidia-drivers in ports tree were updated to latest versions today. > > Here's what I did for the laptop. > > muji2# cd /usr/ports/editors/ > muji2# mv zim zim-0.29 > muji2# fetch http://happy-nation DOT by DOT ru/ports/zim-0.52.tgz.txt > # munged by me as blocked by my ISP :( > zim-0.52.tgz.txt 100% of 3476 B 11 MBps > muji2# mv zim-0.52.tgz.txt zim-0.52.tgz > muji2# tar xvf zim-0.52.tgz > x zim/ > x zim/Makefile > x zim/distinfo > x zim/pkg-descr > x zim/pkg-plist > muji2# cd zim > muji2# ls > Makefile distinfo pkg-descr pkg-plist > muji2# pwd > /usr/ports/editors/zim > muji2# make > ===> zim-0.52 cannot install: Unknown component pygobject. > *** Error code 1 You may just remove pygobject from USE_GNOME in Makefile since you already have py26-gobject-2.21.1 installed, or you may add this to RUN_DEPENDS instead (but still removing pygobject from USE_GNOME): pygobject-codegen-2.0:${PORTSDIR}/devel/py-gobject > Stop in /usr/ports/editors/zim. > > muji2# pkg_info -Ix py > py26-cairo-1.8.8_1 Python bindings for Cairo > py26-coverage-3.4 Code coverage measurement for Python > py26-gobject-2.21.1 Python bindings for GObject > py26-gtk-2.17.0_4 A set of Python bindings for GTK+ > py26-setuptools-0.6c11 Download, build, install, upgrade, and uninstall > Python pac > py26-tkinter-2.6.6_3 Python bindings to the Tk widget set > py26-xdg-0.19 A python library to access freedesktop.org standards > pysol-4.82_1 Solitaire game, written in Python > pysol-sound-server-3.01_4 Python extension module to play sounds and > background music > python26-2.6.6 An interpreted object-oriented programming language > xdpyinfo-1.1.0 Display information utility for X > > cheers > > Chris -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Wed Aug 31 22:30:10 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C381A106568C; Wed, 31 Aug 2011 22:30:10 +0000 (UTC) (envelope-from cwhiteh@onetel.com) Received: from anakin.london.02.net (anakin.london.02.net [87.194.255.134]) by mx1.freebsd.org (Postfix) with ESMTP id 760F88FC28; Wed, 31 Aug 2011 22:30:08 +0000 (UTC) Received: from muji2.config (93.97.24.219) by anakin.london.02.net (8.5.140) id 4E1D604001470C0E; Wed, 31 Aug 2011 22:30:05 +0000 Message-ID: <4E5EB5ED.9080506@onetel.com> Date: Wed, 31 Aug 2011 23:30:05 +0100 From: Chris Whitehouse User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100924 Thunderbird/3.1.4 MIME-Version: 1.0 To: Ruslan Mahmatkhanov References: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> <4E5E3364.7050308@yandex.ru> <4E5E7EAA.4030303@onetel.com> <4E5E84B4.6040200@yandex.ru> In-Reply-To: <4E5E84B4.6040200@yandex.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, acm@FreeBSD.org, perryh@pluto.rain.com Subject: Re: editors/zim X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2011 22:30:10 -0000 On 31/08/2011 20:00, Ruslan Mahmatkhanov wrote: > Chris Whitehouse wrote on 31.08.2011 22:34: >> On 31/08/2011 14:13, Ruslan Mahmatkhanov wrote: >>> perryh@pluto.rain.com wrote on 31.08.2011 09:29: >>>> Forwarding to ports@, which seems more likely to yield an answer to >>>> this particular inquiry than questions@ >>>> >>>> Please keep the OP, who is probably not subscribed to ports@, in the >>>> Cc: list. >>>> >>>> ==================================================================== >>>> >>>> Are there any plans to bump it to Python and a recent release? >>>> I emailed the maintainer a while back but got no response. >>>> >>>> thanks >>>> >>>> Chris >>> >>> Here is: >>> >>> a) diff to a previous port: >>> http://happy-nation DOT by DOT ru/ports/zim-0.52.diff.txt >>> b) updated port tarball: >>> http://happy-nation DOT by DOT ru/ports/zim-0.52.tgz.txt >>> >>> (Just rename it to zim-0.52.tgz and unpack instead of current zim port >>> directory). >>> >>> It works fine to me. Please test and report back is all is alright. If >>> it does, i'll sent problem report to update it in teh tree. >>> >> >> Hi Ruslan, >> >> first thanks for an amazing quick response and to Perry for forwarding >> to the right place. >> >> On a tinderbox with src from a snapshot of 9.0-CURRENT and recent ports >> it builds fine, also on the host which has the same src and ports tree >> it builds and installs fine - but nothing happens when I run the command >> at least as non-root user. The prompt returns after a moment and that's >> it. There is no zim process running and ~/.zim is not created. > > About ~/.zim. It now holds it's settings in ~/.config/zim and the actual > data in ~/Notes (the name of notebook) by default. You also can run zim > from gnome menu. Yes they are there now. > >> Running as root there are some error messages which I can report if >> required which seem to relate to sqlite3. And there is a zim process but >> still no ~/.zim. >> Python on this machine is 2.7.2 > > And you are right - it uses databases/py-sqlite3 to hold the data, but i > already have it installed so i overlooked it. Please try to install > databases/py-sqlite3 first and report back if it helped. It obviously a > missing dependency and i'll add it before submitting pr. Thanks for > pointing this out. Built it in my tinderbox and added it as a package on the 9.0-CURRENT box and now zim works there. I haven't done any testing on this box beyond starting it as non-root and letting it make a default notebook. > >> >> However the computer I really want to run it on is running 8.1-RELEASE >> and ports from around Sept 2010. Python is version 2.6.6. That's my >> laptop and main day-to-day machine. I'm having problems with the more >> recent ports on the other machine in relation to nvidia driver and/or >> flash and/or firefox and would prefer not to upgrade the laptop until >> those are working. > > Ok, i understand. I'm using intel so can't actually help with this one. > But i just saw that nvidia-drivers in ports tree were updated to latest > versions today. Might be time to have another go thanks. > >> >> Here's what I did for the laptop. >> >> muji2# cd /usr/ports/editors/ >> muji2# mv zim zim-0.29 >> muji2# fetch http://happy-nation DOT by DOT ru/ports/zim-0.52.tgz.txt >> # munged by me as blocked by my ISP :( >> zim-0.52.tgz.txt 100% of 3476 B 11 MBps >> muji2# mv zim-0.52.tgz.txt zim-0.52.tgz >> muji2# tar xvf zim-0.52.tgz >> x zim/ >> x zim/Makefile >> x zim/distinfo >> x zim/pkg-descr >> x zim/pkg-plist >> muji2# cd zim >> muji2# ls >> Makefile distinfo pkg-descr pkg-plist >> muji2# pwd >> /usr/ports/editors/zim >> muji2# make >> ===> zim-0.52 cannot install: Unknown component pygobject. >> *** Error code 1 > > You may just remove pygobject from USE_GNOME in Makefile since you > already have py26-gobject-2.21.1 installed, or you may add this to > RUN_DEPENDS instead (but still removing pygobject from USE_GNOME): > pygobject-codegen-2.0:${PORTSDIR}/devel/py-gobject I added to RUN-DEPENDS. Next problem was: muji2# make fetch ===> Vulnerability check disabled, database not found ===> License accepted by the user => zim-0.52.tar.gz is not in /usr/ports/editors/zim/distinfo. => Either /usr/ports/editors/zim/distinfo is out of date, or => zim-0.52.tar.gz is spelled incorrectly. *** Error code 1 Stop in /usr/ports/editors/zim. I fixed this just by putting the md5 in distinfo, the other lines were correct. distinfo is now MD5 (zim-0.52.tar.gz) = fddba2cab1eb4762aa5125a3f4e15fe8 SHA256 (zim-0.52.tar.gz) = 30fb65d5ff54c29d9d36fa499ffc93f277b0a2a575578226b8402c1c4ecbbbdb SIZE (zim-0.52.tar.gz) = 1195768 Now it builds and installs and is working fine, _and_ my original problem has gone away. thanks very much for your help. I'll drop the author a line to say it's been fixed. Chris From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 00:12:50 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72E12106564A for ; Thu, 1 Sep 2011 00:12:50 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (unknown [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 4986D8FC12 for ; Thu, 1 Sep 2011 00:12:50 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p810Cnlp075133 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 31 Aug 2011 17:12:50 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p810CnCj075132; Wed, 31 Aug 2011 17:12:49 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA26334; Wed, 31 Aug 11 17:02:29 PDT Date: Thu, 01 Sep 2011 00:02:23 -0700 From: perryh@pluto.rain.com To: utisoft@gmail.com Message-Id: <4e5f2dff.BxgZocoUYYb74+Ul%perryh@pluto.rain.com> References: <1B4FC0D8-60E6-49DA-BC52-688052C4DA51@langille.org> <20110819232125.GA4965@icarus.home.lan> <20110820032438.GA21925@icarus.home.lan> <4774BC00-F32B-4BF4-A955-3728F885CAA1@langille.org> <4E4FF4D6.1090305@os2.kiev.ua> <20110820183456.GA38317@icarus.home.lan> <4e50c931.gCNlQFqn5sVQXXax%perryh@pluto.rain.com> <20110821050051.GA47415@icarus.home.lan> <4e5141dd.mmh6t9R/knnc8Jll%perryh@pluto.rain.com> <4e55153e.Tj16zX3SskfuVesE%perryh@pluto.rain.com> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=_4e5f2dff.4GWkznJSrzlFqWciFy5gqlBWnH86P1SOhWKUpywEo741S9P/" Cc: freebsd-ports@freebsd.org Subject: Re: ports/sysutils/diskcheckd (Re: bad sector in gmirror HDD) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 00:12:50 -0000 This is a multi-part message in MIME format. --=_4e5f2dff.4GWkznJSrzlFqWciFy5gqlBWnH86P1SOhWKUpywEo741S9P/ Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Chris Rees wrote: > Committed. Thanks! Oops. There was another file (not needing testing, since the changes are only in the comments) that I was also going to include in a "final" patch after the functional changes got whatever testing they were going to get :) The attached also includes the Makefile, although you've probably already taken care of that. --=_4e5f2dff.4GWkznJSrzlFqWciFy5gqlBWnH86P1SOhWKUpywEo741S9P/ Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="2011-0825.other.diff" diff -ruN diskcheckd.old/files/diskcheckd.conf diskcheckd.new/files/diskcheckd.conf --- diskcheckd.old/files/diskcheckd.conf 2001-07-04 11:33:01.000000000 -0700 +++ diskcheckd.new/files/diskcheckd.conf 2011-08-21 03:07:40.000000000 -0700 @@ -1,6 +1,6 @@ # $FreeBSD: ports/sysutils/diskcheckd/files/diskcheckd.conf,v 1.3 2001/07/04 18:33:01 ben Exp $ # -# Configuration file for diskcheckd, refer to the diskcheckd.conf(5) manual +# Configuration file for diskcheckd, refer to the diskcheckd(8) manual # page for further information. # # First, a line starting with an exclamation mark should contain only one @@ -21,10 +21,11 @@ # The size may be specified as "*", in which case the size is automatically # determined from the disklabel. # -# One of either "Days" or "Rate" must be specified, to specify a complete -# scan should happen once every n days, or that scanning should take place -# at n KB/s. Note that the "Days" value will not cause a scan exactly every -# n days since diskcheckd will always read in power-of-2 size blocks. +# One of either "Days" or "Rate" must be specified, to specify scanning at +# a rate which will accomplish a complete scan in the space of n days, or +# that scanning should take place at n KB/s. Note that the "Days" value +# will not cause a scan exactly every n days since diskcheckd will always +# read in power-of-2 size blocks. # # Device Size Days Rate * * 28 * diff -ruN diskcheckd.old/Makefile diskcheckd.new/Makefile --- diskcheckd.old/Makefile 2011-08-17 18:31:40.000000000 -0700 +++ diskcheckd.new/Makefile 2011-08-26 02:28:30.000000000 -0700 @@ -8,18 +8,15 @@ PORTNAME= diskcheckd PORTVERSION= 20010823 -PORTREVISION= 5 +PORTREVISION= 6 CATEGORIES= sysutils MASTER_SITES= # part of port DISTFILES= # part of port EXTRACT_ONLY= # part of port -MAINTAINER= ports@FreeBSD.org +MAINTAINER= perryh@pluto.rain.com COMMENT= Daemon to check for disk read errors -DEPRECATED= Unmaintained, broken (ports/143566) -EXPIRATION_DATE=2011-10-17 - MAN8= diskcheckd.8 MLINKS= diskcheckd.8 diskcheckd.conf.5 --=_4e5f2dff.4GWkznJSrzlFqWciFy5gqlBWnH86P1SOhWKUpywEo741S9P/-- From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 02:50:19 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44A1B1065674 for ; Thu, 1 Sep 2011 02:50:19 +0000 (UTC) (envelope-from ade@FreeBSD.org) Received: from panix.lovett.com (panix.lovett.com [166.84.7.128]) by mx1.freebsd.org (Postfix) with ESMTP id 1E98E8FC17 for ; Thu, 1 Sep 2011 02:50:18 +0000 (UTC) Received: from r74-192-180-219.htvlcmta01.hnvitx.tl.dh.suddenlink.net ([74.192.180.219] helo=lab.lovett.com) by panix.lovett.com with esmtpa (Exim 4.76 (FreeBSD)) (envelope-from ) id 1QyxMA-000O7G-0D for freebsd-ports@freebsd.org; Thu, 01 Sep 2011 02:50:18 +0000 Date: Wed, 31 Aug 2011 21:50:05 -0500 From: Ade Lovett To: freebsd-ports@freebsd.org Message-ID: <20110831215005.00843ec9@lab.lovett.com> In-Reply-To: <4E5E6B26.4040007@FreeBSD.org> References: <201108301524.p7UFOc6Q008169@fire.js.berklix.net> <4E5D0A77.3070304@FreeBSD.org> <20110831004337.2deb368e@lab.lovett.com> <4E5E6B26.4040007@FreeBSD.org> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 02:50:19 -0000 On Wed, 31 Aug 2011 19:11:02 +0200 Matthias Andree wrote: > Am 31.08.2011 07:43, schrieb Ade Lovett: > > On Tue, 30 Aug 2011 18:06:15 +0200 > > 1. In the context of a FreeBSD port, there is absolutely nothing > > wrong with mail/procmail as it stands. That is to say, it compiles > > and runs on all supported OS releases and architectures. > > Which is insufficient in the light of known design flaws and bugs. Hardly. Unless, of course you have empirical proof that mail/procmail is the only such port that suffers from bugs. > > 3. Particularly when there's no magic tool to convert all > > the .procmailrc's out there to mail/whizzy-new-thing. > > Cleaning up every 7 years or so is a good idea actually. Jolly good. I'll go nuke autoconf-2.13 (January 1999) and automake-1.4 (July 2002). We'll ignore the emacs, xemacs, thunderbird users when their stuff doesn't build any more. > > #3 is the important point. If you do want to send mail/procmail to > > the great bitbucket in the sky, then please provide that magic > > tool. I'm sure lots of folks will be willing to test it for you. > > OK. I've asked that on the courier-maildrop list. Remember, it has to be a complete drop-in replacement. MTA agnostic, handle all the various command line arguments, and be totally backwards compatible. Seriously. Find something more useful to do. -aDe From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 04:11:36 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F7951065670 for ; Thu, 1 Sep 2011 04:11:36 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 45FCC8FC12 for ; Thu, 1 Sep 2011 04:11:36 +0000 (UTC) Received: by iadx2 with SMTP id x2so1974256iad.13 for ; Wed, 31 Aug 2011 21:11:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=PnDbfT0p8X8RXxSaECNd/maLXh1hbN4oay8/plKADpQ=; b=kMWebpCAsQSYmJBuErrgOPCvTFjB2YX8AFKVHc0uT6rfCI7sM24ah5LfOqVnyjphf0 Gprylr7JGEr8DDvvFSdFl7a14As+2ftYQvLekxVkJhB2cj1xpbXP1Be/S3CW7EoNqzDc FnFTO2yAlmSf4NaRZMPEiQZXdkn1cQqtXzzmY= Received: by 10.231.4.100 with SMTP id 36mr1968667ibq.99.1314848762792; Wed, 31 Aug 2011 20:46:02 -0700 (PDT) Received: from reemsky ([12.204.99.172]) by mx.google.com with ESMTPS id y8sm121254ibt.53.2011.08.31.20.46.01 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 20:46:01 -0700 (PDT) Sender: Roman Bogorodskiy Date: Wed, 31 Aug 2011 20:45:54 -0700 From: Roman Bogorodskiy To: Kurt Jaeger Message-ID: <20110901034552.GB2633@reemsky> References: <20110831080749.51f36daa@seibercom.net> <20110831132843.GI28186@home.opsec.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TRYliJ5NKNqkz5bu" Content-Disposition: inline In-Reply-To: <20110831132843.GI28186@home.opsec.eu> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-ports@freebsd.org Subject: Re: Update GnuTLS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 04:11:36 -0000 --TRYliJ5NKNqkz5bu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Kurt Jaeger wrote: > > GnuTLS has been updated. URL: > > > >=20 > > I was wondering if there is any work being done on getting the new > > version into the ports tree. GnuTLS 3.0.x branch replaces the GnuTLS > > 2.12.x branch as the supported stable branch. The experimental 2.99.x > > branch is now probably comatose as well. >=20 > gnutls-3.0.1 needs p11-kit in version 0.4 or newer, maybe that's why > we're still at 2.x ? >=20 > And re-testing the whole dependencies on that -- sounds like a > close call for 9.0-REL... Hello, p11-kit is not a main issue indeed.=20 First of all, I'd prefer to wait some time and see what kind of problems gnutls users have with the new branch since it's quite new still, the first 3.0 release was just about one months ago. And yes, it takes some time to build-test all the dependencies and additionally it's nice to be able to run-test all the stuff (which I obviously cannot do), so I just test a number of more or less popular ports in runtime, but it almost always happens that some of the ports end up broken after update. So I would prefer to wait with the update a couple of weeks. Or, if there's an urgent need I may consider adding it as gnutls3 meanwhile. Roman Bogorodskiy --TRYliJ5NKNqkz5bu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJOXv/wAAoJEMltX/4IwiJqerwH/RgvwLBeGXCYXOib79BX/GCo GNaVjunLNFsBpyn5eIF/TT4XwebAq9WMDSQOUXW8sjjSwlWSy7T5/y/teo1ajgol vqo9IdzSj4Ic4RvkfqR8VXSgWMHWNr/pe8muwq/PTXdIy0bs3QWw9K7hbD/ayHHh DSWAVCdmhTIuy0RKLM2bIvyCQHmWQj7S+ZtLbaJN0RsoJSrz9+jiYMfms8MsKJZH PATwb3BC3nMo9CKSyCfI/RclGGo8ScemEGnZXdjedHb85AD9+kv42qCrK6a9991j sisrQl5Zh0qLseaeZR2oTqN+LniUeTdk9DM+3uC8Mk5wyhL2OR4joMDCTm16IAw= =ZXk5 -----END PGP SIGNATURE----- --TRYliJ5NKNqkz5bu-- From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 06:24:28 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3ECB6106564A for ; Thu, 1 Sep 2011 06:24:28 +0000 (UTC) (envelope-from alp@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.freebsd.org (Postfix) with ESMTP id 8F1B68FC14 for ; Thu, 1 Sep 2011 06:24:26 +0000 (UTC) Received: from pyhalov.cc.rsu.ru (pyhalov.cc.rsu.ru [195.208.252.128]) (authenticated bits=0) by mail.r61.net (8.14.4/8.14.4) with ESMTP id p8169FDW032026 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for ; Thu, 1 Sep 2011 10:09:15 +0400 (MSD) (envelope-from alp@rsu.ru) Message-ID: <4E5F2195.5070205@rsu.ru> Date: Thu, 01 Sep 2011 10:09:25 +0400 From: Alexander Pyhalov User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.14) Gecko/20110306 Thunderbird/3.1.8 MIME-Version: 1.0 To: freebsd-ports@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: ports/160313: New port:databases/pg_reorg X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 06:24:28 -0000 Hello. Could someone look at ports/160313 ? It is a port for pg_reorg, which is used to rebuild your PostgreSQL tables, for example, to eliminate table bloat. -- Best regards, Alexander Pyhalov, system administrator of Computer Center of Southern Federal University From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 06:51:49 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A4531065670 for ; Thu, 1 Sep 2011 06:51:49 +0000 (UTC) (envelope-from endzed@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id DC1B28FC15 for ; Thu, 1 Sep 2011 06:51:48 +0000 (UTC) Received: by ewy1 with SMTP id 1so1139829ewy.13 for ; Wed, 31 Aug 2011 23:51:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=sGaFDtA9c5KlfX5F08k8VLkc+0yqgR5FDRkEzWkGNzQ=; b=gXOkBLlFkwaM7+k92maKrXVcNLPUUMzWSU4AnKLpuCIE/PkwZnAFOUCpPlA0ZYoeA1 KckhO6pNInSY5N5BK2XEJvwTjAlmLEuyH40FiIUypCDI0xdJJ3DPQJs7L5slXOxtY7vs sDIFquMzwb1D+iabtl+gT69dzAilb6lqDKWbk= Received: by 10.213.114.12 with SMTP id c12mr166759ebq.142.1314858335062; Wed, 31 Aug 2011 23:25:35 -0700 (PDT) Received: from [10.0.1.6] (178-211-254-181.dhcp.sevj.net [178.211.254.181]) by mx.google.com with ESMTPS id z15sm205605eem.59.2011.08.31.23.25.32 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 23:25:33 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=iso-8859-1 From: endzed@gmail.com In-Reply-To: <20110808124304.GB16138@goofy.cultdeadsheep.org> Date: Thu, 1 Sep 2011 08:25:31 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20110808091432.GA16138@goofy.cultdeadsheep.org> <20110808124304.GB16138@goofy.cultdeadsheep.org> To: Clement Laforet X-Mailer: Apple Mail (2.1244.3) Cc: freebsd-ports@FreeBSD.org Subject: Re: [CFT] Hadoop preliminary port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 06:51:49 -0000 Le 8 ao=FBt 2011 =E0 14:43, Clement Laforet a =E9crit : > On Mon, Aug 08, 2011 at 11:14:32AM +0200, Clement Laforet wrote: >> Hi, >>=20 >> You can find a preliminary port of hadoop 0.20.203.0 here: >> http://people.freebsd.org/~clement/hadoop/ >=20 > Basic hive and pig ports are available here too. Hello Clem, I'm currently trying your preliminary port for hadoop and pig For hadoop I had to launch su -m hadoop -c 'hadoop namenode -format' = afterwhat all's running fine :) =3D> Maybe some namenodeformat rc command would help for 1st time users = (similar to the postgresql initdb rc command) Pig was a little bit more complex to run, since I needed to setup = /usr/local/etc/hadoop in HADOOP_CONF_DIR and PIG_CLASSPATH env vars for = it to run (so if it is possible to make this path the default would be = great ?), and I'm still unable to run with hadoop, only pig -x local is = running Here's what happen : %pig -x local --version Apache Pig version 0.9.0 (r1148983)=20 compiled Jul 20 2011, 17:49:23 %pig -x local=20 2011-09-01 06:16:25,649 [main] INFO org.apache.pig.Main - Logging error = messages to: /usr/home/hadoop/pig_1314857785643.log 2011-09-01 06:16:26,020 [main] INFO = org.apache.pig.backend.hadoop.executionengine.HExecutionEngine - = Connecting to hadoop file system at: file:/// grunt> quit; %pig 2011-09-01 06:16:35,671 [main] INFO org.apache.pig.Main - Logging error = messages to: /usr/home/hadoop/pig_1314857795666.log 2011-09-01 06:16:36,096 [main] INFO = org.apache.pig.backend.hadoop.executionengine.HExecutionEngine - = Connecting to hadoop file system at: hdfs://localhost:9000 2011-09-01 06:16:36,436 [main] ERROR org.apache.pig.Main - ERROR 2999: = Unexpected internal error. Failed to create DataStorage Details at logfile: /usr/home/hadoop/pig_1314857795666.log %cat /usr/home/hadoop/pig_1314857795666.log Error before Pig is launched ---------------------------- ERROR 2999: Unexpected internal error. Failed to create DataStorage java.lang.RuntimeException: Failed to create DataStorage at = org.apache.pig.backend.hadoop.datastorage.HDataStorage.init(HDataStorage.j= ava:75) at = org.apache.pig.backend.hadoop.datastorage.HDataStorage.(HDataStorage= .java:58) at = org.apache.pig.backend.hadoop.executionengine.HExecutionEngine.init(HExecu= tionEngine.java:196) at = org.apache.pig.backend.hadoop.executionengine.HExecutionEngine.init(HExecu= tionEngine.java:116) at org.apache.pig.impl.PigContext.connect(PigContext.java:184) at org.apache.pig.PigServer.(PigServer.java:243) at org.apache.pig.PigServer.(PigServer.java:228) at org.apache.pig.tools.grunt.Grunt.(Grunt.java:46) at org.apache.pig.Main.run(Main.java:484) at org.apache.pig.Main.main(Main.java:108) Caused by: java.io.IOException: Call to localhost/127.0.0.1:9000 failed = on local exception: java.io.EOFException at org.apache.hadoop.ipc.Client.wrapException(Client.java:775) at org.apache.hadoop.ipc.Client.call(Client.java:743) at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:220) at $Proxy0.getProtocolVersion(Unknown Source) at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:359) at = org.apache.hadoop.hdfs.DFSClient.createRPCNamenode(DFSClient.java:106) at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:207) at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:170) at = org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSys= tem.java:82) at = org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:1378) at = org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:66) at = org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:1390) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:196) at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:95) at = org.apache.pig.backend.hadoop.datastorage.HDataStorage.init(HDataStorage.j= ava:72) ... 9 more Caused by: java.io.EOFException at java.io.DataInputStream.readInt(DataInputStream.java:375) at = org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:501) at org.apache.hadoop.ipc.Client$Connection.run(Client.java:446) = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D I understand that this has something to do with hadoop and pig version = compatibility, but since I'm only an enduser (i.e. don't know about ant = or java stuffs) I'm a little bit lost as you can guess... Can you help with this ?=20 please notice that for lazy reason I'm working with hadoop user directly = (I had to set it home and shell btw), I didn't tried to run pig under = another user for the moment. Thanks, David From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 08:55:42 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0DE61065670 for ; Thu, 1 Sep 2011 08:55:42 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 5E9AB8FC12 for ; Thu, 1 Sep 2011 08:55:42 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-ports@freebsd.org with esmtp (envelope-from ) id <1Qz2lz-0003UZ-Rv>; Thu, 01 Sep 2011 10:37:19 +0200 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-ports@freebsd.org with esmtpsa (envelope-from ) id <1Qz2lz-0004Rd-Pz>; Thu, 01 Sep 2011 10:37:19 +0200 Message-ID: <4E5F443F.7000001@zedat.fu-berlin.de> Date: Thu, 01 Sep 2011 10:37:19 +0200 From: "O. Hartmann" Organization: Freie =?ISO-8859-1?Q?Universit=E4t_Berlin?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110829 Thunderbird/6.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 Subject: portmaster -dav, , ===>>> The value of DISTDIR cannot be empty, ===>>> Aborting update X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 08:55:42 -0000 The most resent update of the ports tree resulted in this failure: [~] portmaster -dav ===>>> The value of DISTDIR cannot be empty ===>>> Aborting update Minutes ago, I performed an update and everything was smooth. The another portsnap seems to have killed something. Oliver From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 08:57:47 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCD0B106566B for ; Thu, 1 Sep 2011 08:57:47 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward12.mail.yandex.net (forward12.mail.yandex.net [IPv6:2a02:6b8:0:801::2]) by mx1.freebsd.org (Postfix) with ESMTP id 082F48FC08 for ; Thu, 1 Sep 2011 08:57:47 +0000 (UTC) Received: from smtp14.mail.yandex.net (smtp14.mail.yandex.net [95.108.131.192]) by forward12.mail.yandex.net (Yandex) with ESMTP id 73C46C2250A; Thu, 1 Sep 2011 12:57:45 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314867465; bh=E3eWvMv4pHAYhTvdKrQfzR3QXrMWTiTs7rF03KfWWtQ=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=vGr7LBEdumpXQZbkEZP3pBPR/v8Z79mVEYQpYVovY3peXezy9H1+3mwcrxv3Hcg9A OQ8SJINeP4zfsubLgNXjLJPW0AOa4A6d7vqNX5fhEwDDgXeTktYLHqWs7PnqycIJJw MwVviMeR2N+LmVn2LDs2Dgj0RcO1/NbiItRj6VoM= Received: from smtp14.mail.yandex.net (localhost [127.0.0.1]) by smtp14.mail.yandex.net (Yandex) with ESMTP id 5DC601B603E4; Thu, 1 Sep 2011 12:57:45 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp14.mail.yandex.net (nwsmtp/Yandex) with ESMTP id vjUu01Hj; Thu, 1 Sep 2011 12:57:45 +0400 X-Yandex-Spam: 1 Message-ID: <4E5F4905.8000109@yandex.ru> Date: Thu, 01 Sep 2011 12:57:41 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: "O. Hartmann" References: <4E5F443F.7000001@zedat.fu-berlin.de> In-Reply-To: <4E5F443F.7000001@zedat.fu-berlin.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: portmaster -dav, , ===>>> The value of DISTDIR cannot be empty, ===>>> Aborting update X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 08:57:47 -0000 O. Hartmann wrote on 01.09.2011 12:37: > The most resent update of the ports tree resulted in this failure: > > > [~] portmaster -dav > > ===>>> The value of DISTDIR cannot be empty > ===>>> Aborting update > > Minutes ago, I performed an update and everything was smooth. The > another portsnap seems to have killed something. > > Oliver I already wrote about this. You are runing portmaster from the directory that doesn't exist anymore. Just do `cd` and run portmaster again. -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 09:23:50 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 612FE106566C; Thu, 1 Sep 2011 09:23:50 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 3F8D98FC08; Thu, 1 Sep 2011 09:23:50 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id C20135615B; Thu, 1 Sep 2011 04:23:49 -0500 (CDT) Date: Thu, 1 Sep 2011 04:23:49 -0500 From: Mark Linimon To: Michal Varga Message-ID: <20110901092349.GB9509@lonesome.com> References: <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314585798.82067.338.camel@xenon> <4E5B0EFB.6000900@FreeBSD.org> <1314596096.82067.419.camel@xenon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1314596096.82067.419.camel@xenon> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Doug Barton , freebsd-ports@FreeBSD.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 09:23:50 -0000 On Mon, Aug 29, 2011 at 07:34:56AM +0200, Michal Varga wrote: > - While nobody probably cares much about that guy and his missing > browser images, what would you tell to the GIMP guy? That he should have > waited longer before upgrading the (for him, 30 levels deep) "Foo" > dependency? With furious client breathing down his neck and everything? > Either we want to have ports as a "big repository of colorful stuff that > even builds", or we want to have some actual products that people can > use after they build them. And that needs an additional level of quality > control that FreeBSD currently, and horribly, lacks (patches welcome, I > know). In that case, you should not be updating that rapidly. IMHO you should look at installing PC-BSD, who has a release process where they go through the apps based on a stable state of the ports tree, based on paid employees. > - That particular maintainer of Foo graphics library should be forced, > by threats of violence [...] And what happens if he doesn't respond to the threat? We fire him? Look: you can't fire volunteers. Only employees. And let's say that I, as portmgr, tried to impose some kind of rule about what's going to happen to you if you don't do things my way. The upshot? The volunteers will just leave. (They get mad when portmgr tries to bring some sanity to certain chaos-filled areas, as it is.) And why would anyone new agree volunteer to maintain a port if they knew that someone was just going to dump on them when it didn't work? You're not looking at this from the point of view of the people who actually do the work to bring you this system. mcl From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 10:20:51 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44A23106566B; Thu, 1 Sep 2011 10:20:51 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 27C8E8FC1C; Thu, 1 Sep 2011 10:20:49 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA07065; Thu, 01 Sep 2011 13:20:48 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E5F5C7F.6090109@FreeBSD.org> Date: Thu, 01 Sep 2011 13:20:47 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110705 Thunderbird/5.0 MIME-Version: 1.0 To: Matthias Andree References: <201108300823.p7U8NIfD038098@repoman.freebsd.org> <4E5D26E2.7040300@gmx.de> <201108301345.25661.beech@freebsd.org> <4E5E6A7E.3040606@FreeBSD.org> In-Reply-To: <4E5E6A7E.3040606@FreeBSD.org> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Beech Rintoul , freebsd-ports@FreeBSD.org Subject: Re: cvs commit: ports/mail/procmail Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 10:20:51 -0000 on 31/08/2011 20:08 Matthias Andree said the following: > If everyone cared to read not just the past three posts but what was > written earlier in this whole thread, and ceased adding to the > meaningless "I've had no problems", that would help. > > Just because someone hasn't tripped over the bugs yet, is not a reason > to keep a port known to have massive bugs. It's like security bugs, > many people won't notice them and believe the software to be in proper > working order until after it's too late. > > There's a difference between "mature" and abandoned-and-known-buggy. > Not everything that hasn't changed in years is mature, there are a > number of projects that have simply died and not been picked up by > somebody else. Not everything that has bugs is useless. Not everything that appears to be abandoned is useless and can't/won't be picked up. If you don't want to use this port - fine. But let other people use it if they want. -- Andriy Gapon From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 10:48:46 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E492D1065673; Thu, 1 Sep 2011 10:48:45 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward12.mail.yandex.net (forward12.mail.yandex.net [IPv6:2a02:6b8:0:801::2]) by mx1.freebsd.org (Postfix) with ESMTP id 08A7B8FC08; Thu, 1 Sep 2011 10:48:44 +0000 (UTC) Received: from smtp12.mail.yandex.net (smtp12.mail.yandex.net [95.108.131.191]) by forward12.mail.yandex.net (Yandex) with ESMTP id C3467C22F9E; Thu, 1 Sep 2011 14:48:43 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314874123; bh=scL0gIEA1MrhXGVMvU1QjnGqE68Uvd4MtAPF9Df0Izk=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type; b=nvF5J9Gc5GWm7RtQdBQna4tNlqXyFsRr/P6qLrWbd+Ti0/KPO9oo7gD83QNv0Xafc SeN54xsCVa35Tf55nUsJswkmIozZ0B7XfsCls/p+mkPgjz6Pz3OW4s5dMElNM2E+mo 19szSLZaqkFx5+6lKZ/VCUePXigXEfFAOGF+WOns= Received: from smtp12.mail.yandex.net (localhost [127.0.0.1]) by smtp12.mail.yandex.net (Yandex) with ESMTP id A2FBA16A0442; Thu, 1 Sep 2011 14:48:43 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp12.mail.yandex.net (nwsmtp/Yandex) with ESMTP id mhkulD3q; Thu, 1 Sep 2011 14:48:43 +0400 X-Yandex-Spam: 1 Message-ID: <4E5F6307.7040101@yandex.ru> Date: Thu, 01 Sep 2011 14:48:39 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: Alexander Pyhalov References: <4E5F2195.5070205@rsu.ru> In-Reply-To: <4E5F2195.5070205@rsu.ru> Content-Type: multipart/mixed; boundary="------------020601020900050206000505" Cc: bug-followup@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: ports/160313: New port:databases/pg_reorg X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 10:48:46 -0000 This is a multi-part message in MIME format. --------------020601020900050206000505 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Alexander Pyhalov wrote on 01.09.2011 10:09: > Hello. > Could someone look at ports/160313 ? It is a port for pg_reorg, which is > used to rebuild your PostgreSQL tables, for example, to eliminate table > bloat. Hi Alexander, please consider patch attached. Major changes are: - do not depend on postresql90 explicitly, use USE_PGSQL instead Minor changes: - fix tabs, portname and $FreeBSD$ string in Makefile's header - remove PORTREVISION and DISTNAME that is not needed actually - do not list each documentation file, install - add LICENSE - remove some unneded tabs, sort knobs - use ${PORTNAME} in ${WRKSRC} - do not list each documentation filem install them with COPYTREE_SHARE The port runs fine here with postgresql84. -- Regards, Ruslan Tinderboxing kills... the drives. --------------020601020900050206000505 Content-Type: text/plain; name="pg_reorg.diff.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="pg_reorg.diff.txt" ZGlmZiAtcnVOYSBwZ19yZW9yZy5vcmlnL01ha2VmaWxlIHBnX3Jlb3JnL01ha2VmaWxlCi0t LSBwZ19yZW9yZy5vcmlnL01ha2VmaWxlCTIwMTEtMDktMDEgMTQ6MTQ6NTEuMDAwMDAwMDAw ICswNDAwCisrKyBwZ19yZW9yZy9NYWtlZmlsZQkyMDExLTA5LTAxIDE0OjQwOjU3LjAwMDAw MDAwMCArMDQwMApAQCAtMSwzNCArMSwyOCBAQAotIyBOZXcgcG9ydHMgY29sbGVjdGlvbiBt YWtlZmlsZSBmb3I6ICAJcGdyZW9yZwotIyBEYXRlIGNyZWF0ZWQ6ICAgICAgICAgICAgICAg IAkJSmFudWFyeSAxNSwgMjAxMQorIyBOZXcgcG9ydHMgY29sbGVjdGlvbiBtYWtlZmlsZSBm b3I6CXBnX3Jlb3JnCisjIERhdGUgY3JlYXRlZDoJCQlKYW51YXJ5IDE1LCAyMDExCiAjIFdo b206CQkJCQlhbHBAc2ZlZHUucnUKLSMgJEZyZWVCU0Q6IHBvcnRzL2RhdGFiYXNlcy9wZ3Jl b3JnL01ha2VmaWxlCisjICRGcmVlQlNEJAogCi1QT1JUTkFNRT0JCXBnX3Jlb3JnCi1QT1JU VkVSU0lPTj0JCTEuMS43Ci1QT1JUUkVWSVNJT049CQkwCi1DQVRFR09SSUVTPQkJZGF0YWJh c2VzCi1NQVNURVJfU0lURVM9CQlodHRwOi8vcGdmb3VuZHJ5Lm9yZy9mcnMvZG93bmxvYWQu cGhwLzMxMDQvCi1ESVNUTkFNRT0JCXBnX3Jlb3JnLSR7UE9SVFZFUlNJT059CitQT1JUTkFN RT0JcGdfcmVvcmcKK1BPUlRWRVJTSU9OPQkxLjEuNworQ0FURUdPUklFUz0JZGF0YWJhc2Vz CitNQVNURVJfU0lURVM9CWh0dHA6Ly9wZ2ZvdW5kcnkub3JnL2Zycy9kb3dubG9hZC5waHAv MzEwNC8KIAotTUFJTlRBSU5FUj0JCWFscEBzZmVkdS5ydQotQ09NTUVOVD0JCVBvc3RncmVT UUwgdXRpbGl0eSB0byByZW9yZ2FuaXplIHRhYmxlcworTUFJTlRBSU5FUj0JYWxwQHNmZWR1 LnJ1CitDT01NRU5UPQlQb3N0Z3JlU1FMIHV0aWxpdHkgdG8gcmVvcmdhbml6ZSB0YWJsZXMK IAotQlVJTERfREVQRU5EUys9CQlwb3N0Z3Jlc3FsLWNsaWVudD49OS4wOiR7UE9SVFNESVJ9 L2RhdGFiYXNlcy9wb3N0Z3Jlc3FsOTAtY2xpZW50Ci1SVU5fREVQRU5EUz0JCXBvc3RncmVz cWwtc2VydmVyPj05LjA6JHtQT1JUU0RJUn0vZGF0YWJhc2VzL3Bvc3RncmVzcWw5MC1zZXJ2 ZXIKK0xJQ0VOU0U9CUJTRAogCi1VU0VfR01BS0U9CQl5ZXMKLU1BS0VfRU5WPQkJVVNFX1BH WFM9MAorTUFLRV9FTlY9CVVTRV9QR1hTPTAKK1VTRV9HTUFLRT0JeWVzCitVU0VfUEdTUUw9 CXllcwogCi1XUktTUkM9CQkJJHtXUktESVJ9L3BnX3Jlb3JnCitXUktTUkM9CQkke1dSS0RJ Un0vJHtQT1JUTkFNRX0KIAogcG9zdC1pbnN0YWxsOgogLmlmICFkZWZpbmVkKE5PUE9SVERP Q1MpCi0JJHtNS0RJUn0gJHtET0NTRElSfQotCSR7SU5TVEFMTF9EQVRBfSAke1dSS1NSQ30v ZG9jL2luZGV4LWphLmh0bWwgICAgJHtET0NTRElSfQotCSR7SU5TVEFMTF9EQVRBfSAke1dS S1NSQ30vZG9jL2luZGV4Lmh0bWwgICAgJHtET0NTRElSfQotCSR7SU5TVEFMTF9EQVRBfSAk e1dSS1NSQ30vZG9jL3BnX3Jlb3JnLWphLmh0bWwgICAgJHtET0NTRElSfQotCSR7SU5TVEFM TF9EQVRBfSAke1dSS1NSQ30vZG9jL3BnX3Jlb3JnLmh0bWwgICAgJHtET0NTRElSfQotCSR7 SU5TVEFMTF9EQVRBfSAke1dSS1NSQ30vZG9jL3N0eWxlLmNzcyAgICAke0RPQ1NESVJ9CisJ QCR7TUtESVJ9ICR7RE9DU0RJUn0KKwlAKGNkICR7V1JLU1JDfS9kb2MgJiYgJHtDT1BZVFJF RV9TSEFSRX0gXCogJHtET0NTRElSfS8pCiAuZW5kaWYKIAogLmluY2x1ZGUgPGJzZC5wb3J0 Lm1rPgo= --------------020601020900050206000505-- From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 10:51:45 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 976CB106564A for ; Thu, 1 Sep 2011 10:51:45 +0000 (UTC) (envelope-from carmel_ny@hotmail.com) Received: from blu0-omc3-s10.blu0.hotmail.com (blu0-omc3-s10.blu0.hotmail.com [65.55.116.85]) by mx1.freebsd.org (Postfix) with ESMTP id 4C0338FC16 for ; Thu, 1 Sep 2011 10:51:45 +0000 (UTC) Received: from BLU0-SMTP176 ([65.55.116.73]) by blu0-omc3-s10.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 1 Sep 2011 03:51:44 -0700 X-Originating-IP: [76.182.105.57] X-Originating-Email: [carmel_ny@hotmail.com] Message-ID: Received: from scorpio.seibercom.net ([76.182.105.57]) by BLU0-SMTP176.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 1 Sep 2011 03:51:43 -0700 Received: from scorpio (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: carmel_ny@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3RqL4G0mgdz2CG4t for ; Thu, 1 Sep 2011 06:51:42 -0400 (EDT) Date: Thu, 1 Sep 2011 06:51:41 -0400 From: Carmel To: freebsd-ports@freebsd.org In-Reply-To: <20110901034552.GB2633@reemsky> References: <20110831080749.51f36daa@seibercom.net> <20110831132843.GI28186@home.opsec.eu> <20110901034552.GB2633@reemsky> Organization: seibercom.net X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 01 Sep 2011 10:51:43.0451 (UTC) FILETIME=[230F1AB0:01CC6895] Subject: Re: Update GnuTLS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 10:51:45 -0000 On Wed, 31 Aug 2011 20:45:54 -0700 Roman Bogorodskiy articulated: > Kurt Jaeger wrote: > > > > GnuTLS has been updated. URL: > > > > > > > > > I was wondering if there is any work being done on getting the new > > > version into the ports tree. GnuTLS 3.0.x branch replaces the > > > GnuTLS 2.12.x branch as the supported stable branch. The > > > experimental 2.99.x branch is now probably comatose as well. > > > > gnutls-3.0.1 needs p11-kit in version 0.4 or newer, maybe that's why > > we're still at 2.x ? > > > > And re-testing the whole dependencies on that -- sounds like a > > close call for 9.0-REL... > > Hello, > > p11-kit is not a main issue indeed. > > First of all, I'd prefer to wait some time and see what kind of > problems gnutls users have with the new branch since it's quite new > still, the first 3.0 release was just about one months ago. > > And yes, it takes some time to build-test all the dependencies and > additionally it's nice to be able to run-test all the stuff (which I > obviously cannot do), so I just test a number of more or less popular > ports in runtime, but it almost always happens that some of the ports > end up broken after update. > > So I would prefer to wait with the update a couple of weeks. Or, if > there's an urgent need I may consider adding it as gnutls3 meanwhile. IMHO, renaming the existing port to gnutls2 would leave the "gnutls" port name available for the new 3.x version. Personally, I think it would eliminate a lot of confusion. I know on the "claws-mail" forum, there has been chatter from the developers about work they did to insure that the app works with the 3.x version and still be compatible with the older 2.x version. Other than that, I have no actual knowledge of how other programs will interact with it. In any case, releasing this into the ports system with the advanced notice that its compatibility with existing ports is still undetermined as well as expressly requesting feedback on ports that break or otherwise fail with this new version would be advisable and welcome. Way too many ports are being released lately with no advanced warning that they were not tested properly. Just my 2¢. -- Carmel ✌ carmel_ny@hotmail.com From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 11:18:14 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08AB1106566C for ; Thu, 1 Sep 2011 11:18:14 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id C85F38FC13 for ; Thu, 1 Sep 2011 11:18:13 +0000 (UTC) Received: by iadx2 with SMTP id x2so2440187iad.13 for ; Thu, 01 Sep 2011 04:18:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; bh=1xgepgaCLFHzGk/FHulbCOqChoNiEsdJxCw1zJE/AYE=; b=YNc8+dHV8vX4QVbigagB6n/HNAfw2AFUaPQwxM45AH7oRBXKJV4wE/y0TvvLSsePbi OmBZ2X9aLNANjrNqBcnfczaLfmXYi5VZuhqj0KyufkT46DaedGfekZKNSnymnIvrUY2e WkWjyuNJdoaWNYqNZt/+p5vbC6EE7H5h1/UYw= Received: by 10.231.26.68 with SMTP id d4mr141942ibc.66.1314875893100; Thu, 01 Sep 2011 04:18:13 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.61.148 with HTTP; Thu, 1 Sep 2011 04:17:43 -0700 (PDT) In-Reply-To: References: <20110831080749.51f36daa@seibercom.net> <20110831132843.GI28186@home.opsec.eu> <20110901034552.GB2633@reemsky> From: Chris Rees Date: Thu, 1 Sep 2011 12:17:43 +0100 X-Google-Sender-Auth: hw8MUB2Q7352iBY_fLj-h6L6wfc Message-ID: To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Update GnuTLS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 11:18:14 -0000 On 1 September 2011 11:51, Carmel wrote: > On Wed, 31 Aug 2011 20:45:54 -0700 > Roman Bogorodskiy articulated: > >> =A0 Kurt Jaeger wrote: >> >> > > GnuTLS has been updated. URL: >> > > >> > > >> > > I was wondering if there is any work being done on getting the new >> > > version into the ports tree. GnuTLS 3.0.x branch replaces the >> > > GnuTLS 2.12.x branch as the supported stable branch. The >> > > experimental 2.99.x branch is now probably comatose as well. >> > >> > gnutls-3.0.1 needs p11-kit in version 0.4 or newer, maybe that's why >> > we're still at 2.x ? >> > >> > And re-testing the whole dependencies on that -- sounds like a >> > close call for 9.0-REL... >> >> Hello, >> >> p11-kit is not a main issue indeed. >> >> First of all, I'd prefer to wait some time and see what kind of >> problems gnutls users have with the new branch since it's quite new >> still, the first 3.0 release was just about one months ago. >> >> And yes, it takes some time to build-test all the dependencies and >> additionally it's nice to be able to run-test all the stuff (which I >> obviously cannot do), so I just test a number of more or less popular >> ports in runtime, but it almost always happens that some of the ports >> end up broken after update. >> >> So I would prefer to wait with the update a couple of weeks. Or, if >> there's an urgent need I may consider adding it as gnutls3 meanwhile. > > IMHO, renaming the existing port to gnutls2 would leave the "gnutls" > port name available for the new 3.x version. Personally, I think it > would eliminate a lot of confusion. I know on the "claws-mail" forum, > there has been chatter from the developers about work they did to > insure that the app works with the 3.x version and still be compatible > with the older 2.x version. Other than that, I have no actual knowledge > of how other programs will interact with it. > > In any case, releasing this into the ports system with the advanced > notice that its compatibility with existing ports is still > undetermined as well as expressly requesting feedback on ports that > break or otherwise fail with this new version would be advisable and > welcome. Way too many ports are being released lately with no advanced > warning that they were not tested properly. At the risk of another flamewar, this has been covered repeatedly, so please stop bringing it up. The ports in question have all had advance notice on the mailing list, with requests for testing and feedback -- as you have just suggested. None was received, so it must be assumed that there were no problems. Chris From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 13:33:27 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A72D106564A for ; Thu, 1 Sep 2011 13:33:27 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 91D0A8FC0A for ; Thu, 1 Sep 2011 13:33:25 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBD7EB.dip.t-dialin.net [93.203.215.235]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p81DXNvL085077; Thu, 1 Sep 2011 13:33:24 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 p81DX8Lm011928; Thu, 1 Sep 2011 15:33:08 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id p81DX2sN081775; Thu, 1 Sep 2011 13:33:08 GMT (envelope-from jhs@fire.js.berklix.net) Message-Id: <201109011333.p81DX2sN081775@fire.js.berklix.net> To: Sergey Matveychuk From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Linux Unix Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com/~jhs/cv/ Date: Thu, 01 Sep 2011 15:33:02 +0200 Sender: jhs@berklix.com Cc: ports@FreeBSD.org Subject: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 13:33:27 -0000 Hi, Suggestion: pkgdb is too cryptic even with -v, it needs more explanation what it is up to & particularly what decisions it asks from user (I started with 8.2-Release pkgdb then moved to current pkgdb, some fragments of run examples below): % pkgdb -F -v Checking for origin duplicates ...... Checking linkchecker-6.3 Stale dependency: linkchecker-6.3 -> tidy-lib-090315.c_1 (www/tidy-lib): Disclose depends for linkchecker-6.3 tidy-20000804_2 (score:19%) ? ([y]es/[n]o/[a]ll) [no] No clue is given what score means or what decision program wants user to make. % cd /var/db/pkg % echo linkchecker* linkchecker-6.3 % echo *tidy* py26-utidy-0.2_1 tidy-20000804_2 % pkg_info -r linkchecker-6.3 Depends on: Dependency: tidy-lib-090315.c_1 % vi -c/score: `which pkgdb` ruby. Oh well, read that source later meanwhile take default & rerun pkgdb again later, after its cleaned up some Pushed return Install stale dependency? ([y]es/[n]o/[a]ll) [yes] % pkgdb -F -v Checking docproj-1.17_4 Stale dependency: docproj-1.17_4 -> tidy-20000804_2 (www/tidy): Disclose depends for docproj-1.17_4 Install stale dependency? ([y]es/[n]o/[a]ll) [yes] .... Disclose depends for py26-utidy-0.2_1 tidy-lib-090315.c_1 ? ([y]es/[n]o/[a]ll) [yes] What ? Even 'stale dependency' is not clear. Is it missing or what. Doubtless could be figured out with enough other pkg commands & ls, but slightly extending various print commands within pkgdb would be nice. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct. From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 14:39:26 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04687106566C for ; Thu, 1 Sep 2011 14:39:26 +0000 (UTC) (envelope-from talon@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 98D028FC0C for ; Thu, 1 Sep 2011 14:39:25 +0000 (UTC) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.14.4/jtpda-5.4) with ESMTP id p81EcNL5081041 for ; Thu, 1 Sep 2011 16:38:36 +0200 (CEST) X-Ids: 168 Received: from asmodee.lpthe.jussieu.fr (asmodee.lpthe.jussieu.fr [134.157.10.34]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 8B30521C7D for ; Thu, 1 Sep 2011 16:38:57 +0200 (CEST) Received: by asmodee.lpthe.jussieu.fr (Postfix, from userid 2005) id 73D2B33C35; Thu, 1 Sep 2011 16:38:57 +0200 (CEST) Date: Thu, 1 Sep 2011 16:38:57 +0200 From: Michel TALON To: ports@FreeBSD.org Message-ID: <20110901143857.GB56708@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Miltered: at jchkmail.jussieu.fr with ID 4E5F9902.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4E5F9902.003/134.157.10.1/parthe.lpthe.jussieu.fr/parthe.lpthe.jussieu.fr/ Cc: Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 14:39:26 -0000 Julian H. Stacey wrote: > Suggestion: pkgdb is too cryptic even with -v, > it needs more explanation what it is up to & > particularly what decisions it asks from user > ..... This is a point i have studied a long time, notably i have read the ruby code doing that. There are a lot of heuristics doing automatic choices, when they fail they ask the end user. The whole stuff is quite complicated, and asking questions to the user is certainly not the solution, since he has no business knowing the necessary details. In practice he does arbitrary (usually bad) choices and the system degrades. In general one should always be able to make these decisions automatically using the MOVED file, which is what portmaster does (barring some exceptions which occur from time to time and are supposed to be documented in UPDATING - which is an offense to the automaticity of the system). I thing that portupgrade should be modified to remove all those heuristics and use MOVED, but the code is not so obvious to understand, and ruby (as far as i am concerned) doesn't help. Finally the file UPDATING should be forcefully removed from the system, and ports maintainers should get at the same effect through means which don't prevent automatisation (for example upping the revision levels of all appropriate ports, even if they are very numerous). At the end of the day, portupgrade is so awfully slow that i think moving away from ruby could also help in this respect. -- Michel TALON From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 14:42:25 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA6E9106566C for ; Thu, 1 Sep 2011 14:42:25 +0000 (UTC) (envelope-from aponomarenko@ispras.ru) Received: from smtp.ispras.ru (smtp.ispras.ru [83.149.198.202]) by mx1.freebsd.org (Postfix) with ESMTP id 8D0508FC14 for ; Thu, 1 Sep 2011 14:42:25 +0000 (UTC) Received: from ispserv.ispras.ru (ispserv.ispras.ru [83.149.198.72]) by smtp.ispras.ru (Postfix) with ESMTP id 72B355D4046 for ; Thu, 1 Sep 2011 18:12:33 +0400 (MSD) Received: from [10.10.2.130] (winnie.ispras.ru [83.149.198.236]) by ispserv.ispras.ru (Postfix) with ESMTP id 3A8FA3FC48 for ; Thu, 1 Sep 2011 18:23:29 +0400 (MSD) Message-ID: <4E5F952E.4010206@ispras.ru> Date: Thu, 01 Sep 2011 18:22:38 +0400 From: Andrey Ponomarenko User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101206 SUSE/3.1.7 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <20110831080749.51f36daa@seibercom.net> <20110831132843.GI28186@home.opsec.eu> <20110901034552.GB2633@reemsky> In-Reply-To: <20110901034552.GB2633@reemsky> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Update GnuTLS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 14:42:25 -0000 Hello, On 09/01/2011 07:45 AM, Roman Bogorodskiy wrote: > First of all, I'd prefer to wait some time and see what kind of > problems gnutls users have with the new branch since it's quite new > still, the first 3.0 release was just about one months ago. This table [1] may be of help to foresee problems. [1] http://linuxtesting.org/upstream-tracker/versions/gnutls.html -- Andrey Ponomarenko Department for Operating Systems at ISPRAS web: http://www.LinuxTesting.org mail: aponomarenko@ispras.ru From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 14:46:04 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FB21106566C for ; Thu, 1 Sep 2011 14:46:04 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 21A498FC12 for ; Thu, 1 Sep 2011 14:46:03 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id p81Ejf8a003731; Thu, 1 Sep 2011 16:45:58 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id p81EjeBj003730; Thu, 1 Sep 2011 16:45:41 +0200 (CEST) (envelope-from olli) Date: Thu, 1 Sep 2011 16:45:41 +0200 (CEST) Message-Id: <201109011445.p81EjeBj003730@lurza.secnetix.de> From: Oliver Fromme To: freebsd-ports@FreeBSD.ORG, conrads@cox.net In-Reply-To: <20110822232210.11df7099@cox.net> X-Newsgroups: list.freebsd-ports User-Agent: tin/1.9.6-20101126 ("Burnside") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (lurza.secnetix.de [127.0.0.1]); Thu, 01 Sep 2011 16:45:59 +0200 (CEST) Cc: Subject: Re: How to deal with conflict between graphics/libGL and x11/nvidia-driver? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 14:46:04 -0000 Conrad J. Sabatier wrote: > Does anyone have any suggestions on how to deal with the conflict > between the ports libGL and nvidia-driver? > > Both install their own version of /usr/local/lib/libGL.so.1. Obviously, > if you're using the nvidia driver, you need nvidia's version and not > libGL's version, but many other ports also depend on libGL. > > I'm not quite sure how to deal with this so that any portupgrades, etc. > won't keep trampling over my nvidia GL libraries. I was going to use > an ALT_PKGDEP for portupgrade, but the problem is that libGL also > installs some include files that nvidia-driver does not, so that's not > a sufficient solution. Maybe it would be helpful to add libGL as a dependency to the nvidia-driver port. That means, when the libGL port is updated, the nvidia-driver port will be rebuilt, too, because it depends on the libGL port, which means that the nvidia-driver's library will always override the one installed by the libGL port. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd Perl is worse than Python because people wanted it worse. -- Larry Wall From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 15:10:19 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EB441065673 for ; Thu, 1 Sep 2011 15:10:19 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 0E5BA8FC1A for ; Thu, 1 Sep 2011 15:10:18 +0000 (UTC) Received: from mr16.lnh.mail.rcn.net ([207.172.157.36]) by smtp02.lnh.mail.rcn.net with ESMTP; 01 Sep 2011 11:10:17 -0400 Received: from smtp04.lnh.mail.rcn.net (smtp04.lnh.mail.rcn.net [207.172.157.104]) by mr16.lnh.mail.rcn.net (MOS 4.2.3-GA) with ESMTP id BGU42804; Thu, 1 Sep 2011 11:10:17 -0400 Received: from 209-6-41-114.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.41.114]) by smtp04.lnh.mail.rcn.net with ESMTP; 01 Sep 2011 11:10:17 -0400 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20063.41049.375208.814611@jerusalem.litteratus.org> Date: Thu, 1 Sep 2011 11:10:17 -0400 To: ports@freebsd.org In-Reply-To: <20110901143857.GB56708@lpthe.jussieu.fr> References: <20110901143857.GB56708@lpthe.jussieu.fr> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr16.lnh.mail.rcn.net) Cc: Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 15:10:19 -0000 Michel TALON writes: > Finally > the file UPDATING should be forcefully removed from the system While I support all reasonable efforts to get automation to always Do The Right Thing(tm), my reaction to this is: absolutely not. Until you can show there are no, and will never again be, edge cases which break the system, documention for human invervention is always the right choice. Respectfully, Robert Huff From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 15:11:44 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4853C106566B; Thu, 1 Sep 2011 15:11:44 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo202.cox.net (eastrmfepo202.cox.net [68.230.241.217]) by mx1.freebsd.org (Postfix) with ESMTP id D29198FC17; Thu, 1 Sep 2011 15:11:43 +0000 (UTC) Received: from eastrmimpo01.cox.net ([68.1.16.119]) by eastrmfepo202.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20110901151143.TDZQ32466.eastrmfepo202.cox.net@eastrmimpo01.cox.net>; Thu, 1 Sep 2011 11:11:43 -0400 Received: from serene.no-ip.org ([98.164.83.25]) by eastrmimpo01.cox.net with bizsmtp id TTBi1h00Z0YnB6A02TBivd; Thu, 01 Sep 2011 11:11:43 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020205.4E5FA0AF.002B,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=5AHg1zS6fKBk64vkGL/stHpTKznySuNzRq0QOAs0BF0= c=1 sm=1 a=gedi4w8z0VAA:10 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=2vO5UZG1h46htWAnE/rx2g==:17 a=kviXuzpPAAAA:8 a=4m7mjnN_QDKCLyoXXTgA:9 a=CjuIK1q_8ugA:10 a=4vB-4DCPJfMA:10 a=2vO5UZG1h46htWAnE/rx2g==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from cox.net (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id p81FBfVd096359; Thu, 1 Sep 2011 10:11:41 -0500 (CDT) (envelope-from conrads@cox.net) Date: Thu, 1 Sep 2011 10:11:36 -0500 From: "Conrad J. Sabatier" To: Oliver Fromme Message-ID: <20110901101136.7ca784ec@cox.net> In-Reply-To: <201109011445.p81EjeBj003730@lurza.secnetix.de> References: <20110822232210.11df7099@cox.net> <201109011445.p81EjeBj003730@lurza.secnetix.de> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.5; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: danfe@freebsd.org, freebsd-ports@freebsd.org, Luca Pizzamiglio Subject: Re: How to deal with conflict between graphics/libGL and x11/nvidia-driver? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 15:11:44 -0000 On Thu, 1 Sep 2011 16:45:41 +0200 (CEST) Oliver Fromme wrote: > Conrad J. Sabatier wrote: > > Does anyone have any suggestions on how to deal with the conflict > > between the ports libGL and nvidia-driver? > > > > Both install their own version of /usr/local/lib/libGL.so.1. > > Obviously, if you're using the nvidia driver, you need nvidia's > > version and not libGL's version, but many other ports also depend > > on libGL. > > > > I'm not quite sure how to deal with this so that any portupgrades, > > etc. won't keep trampling over my nvidia GL libraries. I was > > going to use an ALT_PKGDEP for portupgrade, but the problem is > > that libGL also installs some include files that nvidia-driver > > does not, so that's not a sufficient solution. > > Maybe it would be helpful to add libGL as a dependency to > the nvidia-driver port. That means, when the libGL port > is updated, the nvidia-driver port will be rebuilt, too, > because it depends on the libGL port, which means that > the nvidia-driver's library will always override the one > installed by the libGL port. > > Best regards > Oliver Excellent idea! Hadn't thought of that. That also obviates the need for a new "AFFECTS" variable in ports that was discussed recently by myself and a few others. I'll Cc: this on to the nvidia-driver maintainer. Thanks, Conrad -- Conrad J. Sabatier conrads@cox.net From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 16:03:27 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4A57106564A for ; Thu, 1 Sep 2011 16:03:27 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id B6B5B8FC08 for ; Thu, 1 Sep 2011 16:03:27 +0000 (UTC) Received: by iadx2 with SMTP id x2so2762804iad.13 for ; Thu, 01 Sep 2011 09:03:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=qm36H3/xYI5pgQFL4c4+gCZwxd7qB+5wPpoeFNoj5QQ=; b=t5zWXiFieApzbcJlLcJc08/nO+4uN9u6tEwUcH7P6l0AFGouERIBItW7BR/aM7qU4a MQ3nUJyNFXHgbQ8SFCl/Q/HnMcpaicR9ZOUCO1+V7WGlboRdw2oePQezn7Ptpzlm0fiW VDJJXhaV/1AJRm/EfXzS5CesAT6pzud/ZD37U= Received: by 10.231.45.204 with SMTP id g12mr565155ibf.79.1314893007061; Thu, 01 Sep 2011 09:03:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.61.148 with HTTP; Thu, 1 Sep 2011 09:02:57 -0700 (PDT) From: Chris Rees Date: Thu, 1 Sep 2011 17:02:57 +0100 Message-ID: To: ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Why don't we split bsd.port.mk up? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 16:03:28 -0000 Hi all, I've been boring people on IRC with this and perhaps I need to widen participation to get some opinions. What do people think of this? http://wiki.freebsd.org/SimplifyingMkIncludes tl;dr -- bsd.port.mk is too big, Mk/ directory is cluttered, .including files from ${PORTSDIR}/Mk in ports is ugly. A preliminary patch is at [1], for the first part. Yes, I'm sure it'll break horribly somewhere, but hopefully that'll show what needs fixing/whether it's possible/practical. Chris [1] http://bugs.freebsd.org/160361 --=20 Chris Rees =A0 =A0 =A0 =A0 =A0| FreeBSD Developer crees@FreeBSD.org =A0 | http://people.freebsd.org/~crees From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 16:20:48 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 099FC106566B; Thu, 1 Sep 2011 16:20:48 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id BFC318FC24; Thu, 1 Sep 2011 16:20:47 +0000 (UTC) Received: by iadx2 with SMTP id x2so2781545iad.13 for ; Thu, 01 Sep 2011 09:20:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=w0vRI75k+HV38ola5JEyQR+DgmNeDq7qh6244JEZPho=; b=Y2mkHYA7hU9zKXiu7dgv/shvPHrPkZzbCvg/Dl4h0JFPseoyDeRbaCnzcQVl+YIXXG rKrGGa88b1tsuDM8MCHtR5h9cY4la2ENFwFBUp8Hs/K/HvxbQu5X3zpkPOrliSSFnc1/ V4gdMeoho/SV7NblIlQ52rYvYNRRlZweSc6io= Received: by 10.231.26.68 with SMTP id d4mr20665ibc.66.1314894047101; Thu, 01 Sep 2011 09:20:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.61.148 with HTTP; Thu, 1 Sep 2011 09:20:17 -0700 (PDT) In-Reply-To: References: From: Chris Rees Date: Thu, 1 Sep 2011 17:20:17 +0100 Message-ID: To: Eygene Ryabinkin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: ports@freebsd.org Subject: Re: Extra fields in INDEX X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 16:20:48 -0000 On 1 September 2011 17:12, Eygene Ryabinkin wrote: > Chris, good day. > > Fri, Aug 19, 2011 at 03:32:43PM +0100, Chris Rees wrote: >> I'm having a look at modifying INDEX to have a field at the end (to >> cause minimum breakage), but I've discovered that in a few ports there >> (6630 out of 22731) appears to be extra 'stuff' in fields past field >> 10 (which is for the first WWW: line in pkg-descr). >> >> Can anyone with knowledge of make index explain why this is happening? >> Using the command line at [1] gets a list >> >> [crees@hydra]~% alias findextrasinindex "< `make -C /usr/ports -V >> INDEXDIR`/`make -C /usr/ports -V INDEXFILE` grep -n >> '^\([^|]*|\)\{11\}[^|]\+'" > > This regexp won't catch empty field #12, so you're effectively counting > the number of entries with non-empty field #12: > {{{ > $ cat INDEX-9 | cut -f 12 -d '|' | grep -v '^$' | wc -l > =A0 =A06221 > $ grep -n '^\([^|]*|\)\{11\}[^|]\+' INDEX-9 | wc -l > =A0 =A06221 > }}} > > Every line in INDEX has 13 fields: > {{{ > $ grep -n '^\([^|]*|\)\{12\}[^|]*$' INDEX-9 | wc -l > =A0 22287 > $ wc -l INDEX-9 > =A0 22287 INDEX-9 > }}} > as every line in 'make describe': > {{{ > $ make -C archivers/fastjar describe | tr '|' '\n' | wc -l > =A0 =A0 =A013 > }}} > >> They have extra fields on the end ... Where have they come from?? > > There are no extra fields, but /usr/ports/Tools/make_index just > reorders them: the order becomes 0...6, 10, 11, 7...9, 12 if compared > to the initial field indices. =A0What is effectively done by 'make > index' in the case of fastjar index line is the following: > {{{ > (make -C archivers/fastjar describe; \ > =A0make -C lang/perl5.8 describe; \ > =A0make -C devel/gmake describe) | \ > perl /usr/ports/Tools/make_index 2>/dev/null | \ > sed -e 's/ =A0*/ /g' -e 's/| =A0*/|/g' -e 's/ =A0*|/|/g' -e 's./.^A.g' | = \ > sort -t '|' +1 -2 | sed -e 's.^A./.g' | grep ^fastjar > }}} > and '^A' here is the real '^A', not two chars '^' and 'A'. > > make_index respects the trailing fields (those that come after 13th) > and they will be put to the end, so if you will add something > as additional trailing field produced by 'make describe', it will > survive piping through make_index and will be in its place in the > INDEX file. Thanks very much Eygene -- I'd tracked down all these by talking to linimon, and neglected to reply to this email. I'm sorry I've wasted your time :( Also, you're right about the regexp, damnit! Chris --=20 Chris Rees =A0 =A0 =A0 =A0 =A0| FreeBSD Developer crees@FreeBSD.org =A0 | http://people.freebsd.org/~crees From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 16:28:23 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1E4F1065675 for ; Thu, 1 Sep 2011 16:28:22 +0000 (UTC) (envelope-from rea@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id A3F828FC29 for ; Thu, 1 Sep 2011 16:28:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=codelabs.ru; s=two; h=Sender:In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=utgAwSI/8jzJa/R/46/VELU6kXKhjYTWRYiD8HIbSwo=; b=NNKxoOh+wDeOcvp6/knWLcSf30ptgOXLrbG5JE51I3HeUt1esiax9q64qqLkVUCa739CRg9RJCKuh2IeCTNtCPJWyO6rQ22UOcAwQPZMLg9/McREGfrac4fqaviQX4rSgLZlapVOMraYGe5w0KXKMjnnq6zHOZq8+YKZKbBAzCpE45/IK1ivt3R5hQnvpn8M5WsmaszQ1MAlqOZy5p5a+/I2EsnYo3ATCTzUzKKAKXFRJ3OI8iJO3TN6sOJZDuIuXTQrhPJuKG+9o1mau6jBDtSHyeOuEg549p59CWn32xWJvBdhQinpR4vIMJL5LYhMhs6nfC3uCzzHWKwzK6bvUA==; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1Qz9sA-000FMa-6i; Thu, 01 Sep 2011 20:12:10 +0400 Date: Thu, 1 Sep 2011 20:12:08 +0400 From: Eygene Ryabinkin To: Chris Rees Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="a+b56+3nqLzpiR9O" Content-Disposition: inline In-Reply-To: Sender: rea@codelabs.ru Cc: ports@freebsd.org Subject: Re: Extra fields in INDEX X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 16:28:23 -0000 --a+b56+3nqLzpiR9O Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Chris, good day. Fri, Aug 19, 2011 at 03:32:43PM +0100, Chris Rees wrote: > I'm having a look at modifying INDEX to have a field at the end (to > cause minimum breakage), but I've discovered that in a few ports there > (6630 out of 22731) appears to be extra 'stuff' in fields past field > 10 (which is for the first WWW: line in pkg-descr). >=20 > Can anyone with knowledge of make index explain why this is happening? > Using the command line at [1] gets a list >=20 > [crees@hydra]~% alias findextrasinindex "< `make -C /usr/ports -V > INDEXDIR`/`make -C /usr/ports -V INDEXFILE` grep -n > '^\([^|]*|\)\{11\}[^|]\+'" This regexp won't catch empty field #12, so you're effectively counting the number of entries with non-empty field #12: {{{ $ cat INDEX-9 | cut -f 12 -d '|' | grep -v '^$' | wc -l 6221 $ grep -n '^\([^|]*|\)\{11\}[^|]\+' INDEX-9 | wc -l 6221 }}} Every line in INDEX has 13 fields: {{{ $ grep -n '^\([^|]*|\)\{12\}[^|]*$' INDEX-9 | wc -l 22287 $ wc -l INDEX-9 22287 INDEX-9 }}} as every line in 'make describe': {{{ $ make -C archivers/fastjar describe | tr '|' '\n' | wc -l 13 }}} > They have extra fields on the end ... Where have they come from?? There are no extra fields, but /usr/ports/Tools/make_index just reorders them: the order becomes 0...6, 10, 11, 7...9, 12 if compared to the initial field indices. What is effectively done by 'make index' in the case of fastjar index line is the following: {{{ (make -C archivers/fastjar describe; \ make -C lang/perl5.8 describe; \ make -C devel/gmake describe) | \ perl /usr/ports/Tools/make_index 2>/dev/null | \ sed -e 's/ */ /g' -e 's/| */|/g' -e 's/ *|/|/g' -e 's./.^A.g' | \ sort -t '|' +1 -2 | sed -e 's.^A./.g' | grep ^fastjar }}} and '^A' here is the real '^A', not two chars '^' and 'A'. make_index respects the trailing fields (those that come after 13th) and they will be put to the end, so if you will add something as additional trailing field produced by 'make describe', it will survive piping through make_index and will be in its place in the INDEX file. --=20 Eygene Ryabinkin ,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ] --a+b56+3nqLzpiR9O Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iF4EAREIAAYFAk5frtgACgkQFq+eroFS7PtcGwD+J9ldH/HwEBp6YZ06Y1Wnz1Ky YSzDdfhDaGlc6qgpt8QA/jyRyHGREIkgcybfVOCZlALQFIVys8Ty/gELNM2vS0eM =7Ccg -----END PGP SIGNATURE----- --a+b56+3nqLzpiR9O-- From owner-freebsd-ports@FreeBSD.ORG Thu Sep 1 21:47:47 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 412D5106564A; Thu, 1 Sep 2011 21:47:47 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 93AC48FC13; Thu, 1 Sep 2011 21:47:46 +0000 (UTC) Received: by fxe4 with SMTP id 4so1440496fxe.13 for ; Thu, 01 Sep 2011 14:47:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=BigBrTMElw2YeSP56rK9LXKHhMty8NAj8odcnJE8ark=; b=d2JdN1KwT/ZyY/TScITwZ0V/Pht6a2OSaXGOFvFcpfKjgzjE8WT/Uu8G3f4cNrKMLf n+Ccf111/LLMLokYio/A1EvzsbnsT9rg5JTKbBRw0Z85NKaWQwigb0X2vWWYZlLdQ9WH kXP5X7wgqUfRqc/1a0oeYfdQ66F8eGDstBU28= Received: by 10.223.75.154 with SMTP id y26mr454349faj.104.1314913665551; Thu, 01 Sep 2011 14:47:45 -0700 (PDT) Received: from [10.0.101.2] (254.166.broadband10.iol.cz [90.177.166.254]) by mx.google.com with ESMTPS id c5sm136322fai.20.2011.09.01.14.47.42 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Sep 2011 14:47:43 -0700 (PDT) From: Michal Varga To: Mark Linimon In-Reply-To: <20110901092349.GB9509@lonesome.com> References: <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314585798.82067.338.camel@xenon> <4E5B0EFB.6000900@FreeBSD.org> <1314596096.82067.419.camel@xenon> <20110901092349.GB9509@lonesome.com> Content-Type: text/plain; charset="UTF-8" Organization: Stonehenge Date: Thu, 01 Sep 2011 23:47:40 +0200 Message-ID: <1314913660.1744.136.camel@xenon> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Doug Barton , freebsd-ports@FreeBSD.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2011 21:47:47 -0000 On Thu, 2011-09-01 at 04:23 -0500, Mark Linimon wrote: > On Mon, Aug 29, 2011 at 07:34:56AM +0200, Michal Varga wrote: > > - While nobody probably cares much about that guy and his missing > > browser images, what would you tell to the GIMP guy? That he should have > > waited longer before upgrading the (for him, 30 levels deep) "Foo" > > dependency? With furious client breathing down his neck and everything? > > Either we want to have ports as a "big repository of colorful stuff that > > even builds", or we want to have some actual products that people can > > use after they build them. And that needs an additional level of quality > > control that FreeBSD currently, and horribly, lacks (patches welcome, I > > know). > > In that case, you should not be updating that rapidly. I've covered that aspect earlier in the discussion. There is no option to 'upgrade less rapidly', as at any single point in time, there is *always* something that just hit the tree moments before. This would require all ports users always perfectly know every single port in their systems and have detailed knowledge about what exactly every single dependency does, affects, and when it's safe to upgrade this or that, and how soon to do it after a particular (and every single) commit. And letting other people get burned while simply "waiting it out" doesn't a quality control process make. Just stating the obvious. [And to cut it right here - no, answer to that is not "Ok, so everyone should be a tester then". This never worked anywhere outside of dreams and wishes. And no other sane project does, nor tries to go this way.] > IMHO you should look at installing PC-BSD, who has a release process > where they go through the apps based on a stable state of the ports tree, > based on paid employees. Telling people to go using different operating systems when they point out some shortcomings in FreeBSD was already pretty old some decade ago. While I'm not the kind of person to get in any way offended by it, I can easily imagine why so many get bittered by such 'suggestions' and eventually just leave for good. If I was looking for another OS, I wouldn't be wasting all this time pointing out what's broken on FreeBSD (or more specifically, in FreeBSD ports), I would be spending that time migrating, as I would have my options long time researched by then (which I have, actually, as significant part of my work depends on fully working desktop systems and FreeBSD no longer cuts it in that domain for some time). > > - That particular maintainer of Foo graphics library should be forced, > > by threats of violence [...] > > And what happens if he doesn't respond to the threat? We fire him? > > Look: you can't fire volunteers. Only employees. Yes, and you now single-handedly discovered what's the major point of failure in the current system (and I don't mean that as a sarcasm, nor making fun of anything). While I was making a hyperbole with all the violence and stuff, it still boils down to this. Nobody is really steering this ship anymore and it just happily rams icebergs along the way, with volunteers occasionally throwing buckets of water (and sometimes pieces of furniture) overboard to somehow keep it afloat for a while longer. The current mechanisms for dealing with ports (and their maintainers) were put in place ages ago in different times and with, frankly, somewhat different people around [citation needed]. Over the course of time, amount of ports grew by magnitudes, dependencies, especially for desktop environments grew by magnitudes, and maintainers are no longer the special dedicated bunch of highly motivated people that know every single port and their whole ecosystems inside-out. This is no longer even possible, among other issues (and there are few). But the system in place still pretends things work this way. They don't. Ports are failing, horribly. And it's not the concept that is wrong, it's the execution. Or more like, lack of any proper. But I'm all fine with pretending that nothing really happens and that few more automated -exp runs will save all and forever. Another five years from now, when FreeBSD definitely sinks into the realm of 'irrelevant' and when the finger pointing finally (and way too late) starts, I'll just bring some popcorn and quietly watch the show, just so that I don't offend someone again with my unsubstantiated whining. > And let's say that I, as portmgr, tried to impose some kind of rule > about what's going to happen to you if you don't do things my way. > The upshot? The volunteers will just leave. (They get mad when > portmgr tries to bring some sanity to certain chaos-filled areas, as > it is.) Yes, and I remember some of 'those' situations. As we - the people who 'don't actually do the work' but sometimes actually use this system - for this or that reason even somehow keep track on what's happening around, as it's affecting both our short- and long- time FreeBSD decisions too. But you're just not doing enough. Doug too doesn't realize he isn't doing enough, and only now tries fixing some of the consequences of the broken system instead of focusing on the root causes. But that's way too late, way too little. So in the long run, nothing will change and FreeBSD ports will just keep rotting, failing and breaking further. But at least, they will compile better. That's so 2011. > And why would anyone new agree volunteer to maintain a port if they knew > that someone was just going to dump on them when it didn't work? I would anytime, and in fact I would never expect any less than the approach you just described. I can't obviously speak for anyone else. For me, it's perfectly obvious that volunteering or not, by joining "the system", there comes responsibility - at least in the minimum - for not breaking other people's stuff. Maintaining a dependency means exactly that - other people are DEPENDENT on *you* (and your port). If one can't bear that responsibility and act accordingly to it, they shouldn't be doing that job in the first place (and yes, should be fired if they can't realize it on their own). Even if there is no one better to do it. Advertising (however randomly) breaking and failing stuff as working, only because there is currently no one else to do it proper, just, in minds of bystanders, turns FreeBSD into some kind of weird parody of Windows Millennium (yes, it's not that much fun advocating FreeBSD these days as it was 10 years ago). And this is not a way that will win you new volunteers, they will simply flock volunteering for projects that work better. > You're not looking at this from the point of view of the people who > actually do the work to bring you this system. > > mcl You would be surprised about how much I've done to bring me (or anyone else) this system even through my every odd post doesn't come with a full @freebsd resume for the past 15 years (hey Doug, don't take it any personally). My point of view is slightly wider than you're implying, but I'm not going to back that up by bullets of "what I have ever done". If what I wrote is not sufficient on its own, then that makes it one less reason to spend any time with it at all. I'm really not going to explain why. But not being part of the "golden club" allows me to speak more freely about things right as the are now, without fears of offending half of my @freebsd buddies (as I obviously don't have any) and getting torn apart on IRC after. That probably makes me state some things in ways that are not very popular these days, but honestly, I mean no offense. Just that padding my emails with "I really love FreeBSD!" and "All of you do a great job and I love you too!" every odd paragraph would make for even more boring reading than this here now. m. -- Michal Varga, Stonehenge (Gmail account) From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 00:09:49 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B333A106564A for ; Fri, 2 Sep 2011 00:09:49 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 440968FC14 for ; Fri, 2 Sep 2011 00:09:49 +0000 (UTC) Received: by ewy1 with SMTP id 1so1613540ewy.13 for ; Thu, 01 Sep 2011 17:09:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=cjB9r14mxvF1l7c300JeD3HQndMFTew8NcK1ei+Khmo=; b=OFBrYPAdO09ZIPxEXcysD5sEVMieJ9xFBquw/XwL3K2W47JpWqfkkleib6Niz5Yl0L 6hHPltMAp44uE/sJt7BuY1U36yjK28iyjtxQ6Bs2WkkHEYa1VPpCEd4o67JZ3yfkF4xt ARIBeAwKeBUXiHlzlT1mGmt4LluOyAVIcAoU4= Received: by 10.213.108.138 with SMTP id f10mr212283ebp.97.1314922188286; Thu, 01 Sep 2011 17:09:48 -0700 (PDT) Received: from gumby.homeunix.com (87-194-105-247.bethere.co.uk [87.194.105.247]) by mx.google.com with ESMTPS id d12sm120259eeb.8.2011.09.01.17.09.44 (version=SSLv3 cipher=OTHER); Thu, 01 Sep 2011 17:09:47 -0700 (PDT) Date: Fri, 2 Sep 2011 01:09:37 +0100 From: RW To: ports@freebsd.org Message-ID: <20110902010937.12d07e77@gumby.homeunix.com> In-Reply-To: <1314913660.1744.136.camel@xenon> References: <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <20110828184542.GE277@magic.hamla.org> <20110828152234.54cc9fac@seibercom.net> <20110828193046.GA668@magic.hamla.org> <1314564889.82067.89.camel@xenon> <4E5AB672.4020607@FreeBSD.org> <1314585798.82067.338.camel@xenon> <4E5B0EFB.6000900@FreeBSD.org> <1314596096.82067.419.camel@xenon> <20110901092349.GB9509@lonesome.com> <1314913660.1744.136.camel@xenon> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 00:09:49 -0000 On Thu, 01 Sep 2011 23:47:40 +0200 Michal Varga wrote: > On Thu, 2011-09-01 at 04:23 -0500, Mark Linimon wrote: > > In that case, you should not be updating that rapidly. > > I've covered that aspect earlier in the discussion. There is no option > to 'upgrade less rapidly', as at any single point in time, there is > *always* something that just hit the tree moments before. During a port's freeze or slush, maintainers are very careful about what's updated. If you only update during those periods there's very little risk of problems, and your packages will still be more up-to-date than in some Linux distros. > This would > require all ports users always perfectly know every single port in > their systems and have detailed knowledge about what exactly every > single dependency does, affects, and when it's safe to upgrade this > or that, and how soon to do it after a particular (and every single) > commit. You can still reduce the probability significantly. You can never reduce risk to zero. Personally, I don't recognise what you are saying. Over the last few years my desktop pc has fluctuated between 800 and 1400 installed ports, and upgrading has been very smooth. From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 01:08:11 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BE811065674 for ; Fri, 2 Sep 2011 01:08:11 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id AF4398FC15 for ; Fri, 2 Sep 2011 01:08:10 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBEA59.dip.t-dialin.net [217.251.234.89]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p82188Vg089628; Fri, 2 Sep 2011 01:08:09 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id p8217qXG059835; Fri, 2 Sep 2011 03:07:55 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id p8217eFJ089679; Fri, 2 Sep 2011 01:07:46 GMT (envelope-from jhs@fire.js.berklix.net) Message-Id: <201109020107.p8217eFJ089679@fire.js.berklix.net> To: Michal Varga From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Thu, 01 Sep 2011 23:47:40 +0200." <1314913660.1744.136.camel@xenon> Date: Fri, 02 Sep 2011 03:07:40 +0200 Sender: jhs@berklix.com Cc: freebsd-ports@freebsd.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 01:08:11 -0000 Michal, Nice analogy ! > Nobody is really steering this ship anymore and it just happily > rams icebergs along the way, with volunteers occasionally throwing > buckets of water (and sometimes pieces of furniture) overboard to > somehow keep it afloat for a while longer. Furniture like sysutils/diskcheckd, mail/procmail etc was recently under threat of discard, from misguided preference to toss code alleged problematic, rather than investigate send-prs others said were problematic. Tossing to CVS Attic is no excuse, it's not something many release users have to hand, nor will they read ports@ etc between releases. Release users are what a company would call valuable customers. For FreeBSD they should be valuable too, & include firms that use releases to create jobs, sponsor developers, & promote BSD. But FreeBSD ports@ degrades releases with: Give no warning, dont mark deprecated on one release then wait till next release before removal, just toss out ports between releases with no warning. No principle of least suprise. Unprofessional. I've not known a clean build of ports/ I use in 10 years ( http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/ports/jhs/Makefile.local ) But as I dont build in chroots, probably I should be grateful the can of worms is not bigger, with `/bin/ls -1 /var/db/pkg | wc -l` > 1000 The mass waste of time with all major Unix projects maintaining their own ports/ packages shims/ skeletons to build generic software is scarey. Microsoft must grin at all us BSD, Linux, maybe Solaris & presumably even now http://www.minix3.org free source enthusiasts reinventing similar old ports shims for same old 3rd party wheels:. A ports manager made a good point: there's a big investment of people skills in doing things the FreeBSD way. But that could also translate as: Our Titanic is too heavy to steer. FreeBSD ports infrastructure/ future history could be any of these: - Struggle on as is. - Accept we're in trouble, (as some NetBSD too accept), co-operate, & get someone [ SoC students ? ] to design *BSD *Linux, a new cross/ OS shim set. (too scarey letting students do that > pay some one else. ). - Get FreeBSD & NetBSD foundations & maybe wider to sponsor a new build structure with a limited number of demo ports. - Wait & see if a firm does a Cygnus on us. ie what Cygnus did for FSF UX tools on MS, remove some pain & charge some money. - Wait & see if someone ports their Linux NetBSD or whatever ports shims to also work on FreeBSD. (just as Linux tools on a BSD kernel came as a suprise to us). - See if someone who produces RFCs takes a crack at defining standards for ports/ shims BTW I call 'em shims, cos the word ports causes problems in the NetBSD hardware ports camp, Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct. From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 05:11:44 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C17F1065673 for ; Fri, 2 Sep 2011 05:11:44 +0000 (UTC) (envelope-from alp@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.freebsd.org (Postfix) with ESMTP id EB1B98FC14 for ; Fri, 2 Sep 2011 05:11:43 +0000 (UTC) Received: from pyhalov.cc.rsu.ru (pyhalov.cc.rsu.ru [195.208.252.128]) (authenticated bits=0) by mail.r61.net (8.14.4/8.14.4) with ESMTP id p825BfTN053311 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 2 Sep 2011 09:11:41 +0400 (MSD) (envelope-from alp@rsu.ru) Message-ID: <4E606596.8020903@rsu.ru> Date: Fri, 02 Sep 2011 09:11:50 +0400 From: Alexander Pyhalov User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.14) Gecko/20110306 Thunderbird/3.1.8 MIME-Version: 1.0 To: Ruslan Mahmatkhanov References: <4E5F2195.5070205@rsu.ru> <4E5F6307.7040101@yandex.ru> In-Reply-To: <4E5F6307.7040101@yandex.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: bug-followup@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: ports/160313: New port:databases/pg_reorg X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 05:11:44 -0000 Hello. Thanks for your patch. This port now looks better and works with 8.4. On 09/01/2011 14:48, Ruslan Mahmatkhanov wrote: > Alexander Pyhalov wrote on 01.09.2011 10:09: >> Hello. >> Could someone look at ports/160313 ? It is a port for pg_reorg, which is >> used to rebuild your PostgreSQL tables, for example, to eliminate table >> bloat. > > Hi Alexander, > please consider patch attached. -- Best regards, Alexander Pyhalov, system administrator of Computer Center of Southern Federal University From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 08:18:57 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CB27106566C; Fri, 2 Sep 2011 08:18:57 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward12.mail.yandex.net (forward12.mail.yandex.net [IPv6:2a02:6b8:0:801::2]) by mx1.freebsd.org (Postfix) with ESMTP id D248F8FC16; Fri, 2 Sep 2011 08:18:56 +0000 (UTC) Received: from smtp11.mail.yandex.net (smtp11.mail.yandex.net [95.108.130.67]) by forward12.mail.yandex.net (Yandex) with ESMTP id 46D05C20CA2; Fri, 2 Sep 2011 12:18:55 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1314951535; bh=czkdPu7sk6QXwRHxIJHfHg38zbI7GCaH6Je3Ep6L1dg=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=LHJSHElbxQG6trUUgCOwv1RtElYqAPvPfiTDL/gI3yOCFXKVJlb/LrCtMsRaLWFlh auq0b1EI/5RRcEC8ZR9fhOq+ENz5WfyHBMnAeItLerEKjb1Dugyn9kZAEqG/H73sMl kKx4fEdV9hhIt5Erb99gzk0FcRrlrZw91eDUCnLM= Received: from smtp11.mail.yandex.net (localhost [127.0.0.1]) by smtp11.mail.yandex.net (Yandex) with ESMTP id 1F6C77E0480; Fri, 2 Sep 2011 12:18:55 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp11.mail.yandex.net (nwsmtp/Yandex) with ESMTP id IsEKgoCL; Fri, 2 Sep 2011 12:18:54 +0400 X-Yandex-Spam: 1 Message-ID: <4E60916A.2020002@yandex.ru> Date: Fri, 02 Sep 2011 12:18:50 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: Chris Whitehouse References: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> <4E5E3364.7050308@yandex.ru> <4E5E7EAA.4030303@onetel.com> <4E5E84B4.6040200@yandex.ru> <4E5EB5ED.9080506@onetel.com> In-Reply-To: <4E5EB5ED.9080506@onetel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, acm@FreeBSD.org, perryh@pluto.rain.com Subject: Re: editors/zim X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 08:18:57 -0000 Chris Whitehouse wrote on 01.09.2011 02:30: [skipping the details since original problem was solved] > Now it builds and installs and is working fine, _and_ my original > problem has gone away. > > thanks very much for your help. I'll drop the author a line to say it's > been fixed. > > Chris Sorry for delay, i now added sqlite3 dependency and some optional dependencies for zim plugins (besides the gtkspell one, since the plugin needs python binding to gtkspell that we seems lacking in the ports tree). This pr was submitted: http://bugs.freebsd.org/160385. I also reupploaded port tarball and the diff. -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 09:24:33 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9090106566C for ; Fri, 2 Sep 2011 09:24:33 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 555858FC0A for ; Fri, 2 Sep 2011 09:24:33 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id p829OGZm000944; Fri, 2 Sep 2011 11:24:32 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id p829OGAG000943; Fri, 2 Sep 2011 11:24:16 +0200 (CEST) (envelope-from olli) Date: Fri, 2 Sep 2011 11:24:16 +0200 (CEST) Message-Id: <201109020924.p829OGAG000943@lurza.secnetix.de> From: Oliver Fromme To: freebsd-ports@FreeBSD.ORG In-Reply-To: <20110902010937.12d07e77@gumby.homeunix.com> X-Newsgroups: list.freebsd-ports User-Agent: tin/1.9.6-20101126 ("Burnside") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (lurza.secnetix.de [127.0.0.1]); Fri, 02 Sep 2011 11:24:32 +0200 (CEST) Cc: Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 09:24:34 -0000 (Not replying to any particular post in this thread.) I think the current ports system in FreeBSD is not bad. Sure, it could be better (but this would probably require more manpower, which is a problem in a volunteer project), but it also could be a *lot* worse. I know of several people who are typical "release users". They install a FreeBSD release from CD/DVD and use the ports or packages that came with that release. Usually that works very well because of the testing during the ports freeze that happens in preparation for every release. They never update (or maybe only when there are serious security issues) and happily keep using those very ports until they update to a newer release, one or two (or more) years later. The other extreme are people who run a cron job every night that updates /usr/ports (*) and runs "400.status-pkg" (from /etc/periodic/weekly), possibly even followed by an automated update (**). Of course this will sometimes break. That's normal and to be expected, because the ports collection is changed and modified constantly by many people, except during freeze. There is always something that's broken. If you're affected, you need to postpone the update of the respective ports until someone (possibly including yourself) unbreaks it. That's the price to pay when you want to be on the "bleeding edge" instead of waiting for the next freeze and updating the ports to the release tag only. Personally, on my workstation at home I make a complete update every few months (2 to 4 times a year). If there are any security vulnerabilities reported by portaudit, I update the affected ports immediately, of course. (By the way, I use neither portupgrade nor portmaster, but a self-made script. However, portmaster really isn't that bad and should work fine for most users. :-) Finally, I recommend to install ports-mgmt/pkg_cutleaves and run it regularly after updates. It helps removing ports that you don't need. Rule of thumb: The less ports you have, the less dependencies exist, so updates will be less complex, and you're less likely to be affected by breakage. With that in mind, I keep the ports count on my workstation on a moderate level: $ pkg_info | wc -l 559 Best regards Oliver (*) For example: http://www.secnetix.de/olli/scripts/ports-check-update (**) http://www.secnetix.de/olli/scripts/ports-update-list -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "If you think C++ is not overly complicated, just what is a protected abstract virtual base pure virtual private destructor, and when was the last time you needed one?" -- Tom Cargil, C++ Journal From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 09:30:12 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 4B308106564A for ; Fri, 2 Sep 2011 09:30:12 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 4F70A1516F6; Fri, 2 Sep 2011 09:30:11 +0000 (UTC) Message-ID: <4E60A222.9040304@FreeBSD.org> Date: Fri, 02 Sep 2011 02:30:10 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.1) Gecko/20110901 Thunderbird/6.0.1 MIME-Version: 1.0 To: Oliver Fromme References: <201109020924.p829OGAG000943@lurza.secnetix.de> In-Reply-To: <201109020924.p829OGAG000943@lurza.secnetix.de> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@FreeBSD.ORG Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 09:30:12 -0000 On 09/02/2011 02:24, Oliver Fromme wrote: > Finally, I recommend to install ports-mgmt/pkg_cutleaves and > run it regularly after updates portmaster -s does the same thing. FYI, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 09:39:26 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CD3D106564A for ; Fri, 2 Sep 2011 09:39:26 +0000 (UTC) (envelope-from talon@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id B81D98FC12 for ; Fri, 2 Sep 2011 09:39:25 +0000 (UTC) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.14.4/jtpda-5.4) with ESMTP id p829ckg6043517 for ; Fri, 2 Sep 2011 11:38:46 +0200 (CEST) X-Ids: 164 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 7D75C21C82 for ; Fri, 2 Sep 2011 11:39:14 +0200 (CEST) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id 5F87842B4; Fri, 2 Sep 2011 11:39:14 +0200 (CEST) Date: Fri, 2 Sep 2011 11:39:14 +0200 From: Michel Talon To: ports@freebsd.org Message-ID: <20110902093914.GA92386@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Miltered: at jchkmail.jussieu.fr with ID 4E60A44C.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4E60A44C.001/134.157.10.1/parthe.lpthe.jussieu.fr/parthe.lpthe.jussieu.fr/ Cc: Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 09:39:26 -0000 Robert Huff said: >Michel TALON writes: > >> Finally >> the file UPDATING should be forcefully removed from the system > > While I support all reasonable efforts to get automation to >always Do The Right Thing(tm), my reaction to this is: absolutely >not. > Until you can show there are no, and will never again be, edge >cases which break the system, documention for human invervention is >always the right choice. Your answer is very interesting and allows me to go further in the reasoning. Indeed the UPDATING file is here to solve edge cases. My point is that there shouldn't be any edge cases, if there are some it is because something somewhere has been ill designed, which is not so suprising since the system has been conceived by Jordan Hubbard when the number and complexity of ports was much smaller. I certainly don't have any precise idea of the things which should be changed so that edge cases disappear, only *very experienced* people having observed a lot of failure cases could give correct advices. It is not impossible to design a system which works automatically without having any recourse to manual intervention, after all, as much as it may displease some people here, it is a fact that Debian works this way (and Debian-like systems like Ubuntu). Having a file which documents manual intervention is a perpetual tentation to do the things the sloppy way, which in fact frequently occurs in FreeBSD. As long as such a behavior continues, the authors of portupgrade, portmaster etc. are building on sand. -- Michel TALON From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 09:43:48 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 2D0E81065678 for ; Fri, 2 Sep 2011 09:43:48 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 442E114E65E; Fri, 2 Sep 2011 09:43:47 +0000 (UTC) Message-ID: <4E60A552.8090306@FreeBSD.org> Date: Fri, 02 Sep 2011 02:43:46 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.1) Gecko/20110901 Thunderbird/6.0.1 MIME-Version: 1.0 To: Michel Talon References: <20110902093914.GA92386@lpthe.jussieu.fr> In-Reply-To: <20110902093914.GA92386@lpthe.jussieu.fr> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 09:43:48 -0000 On 09/02/2011 02:39, Michel Talon wrote: > Your answer is very interesting and allows me to go further in the > reasoning. Indeed the UPDATING file is here to solve edge cases. My > point is that there shouldn't be any edge cases, if there are some it is > because something somewhere has been ill designed, which is not so > suprising since the system has been conceived by Jordan Hubbard when the > number and complexity of ports was much smaller. I certainly don't have > any precise idea of the things which should be changed so that edge > cases disappear, ... then how about you stop talking about it for a while? Many people who have been heavily involved with the ports system for a very long time have already agreed that there are a ton of thorny issues that need to be worked out in order for it to improve. IOW, we agree with you. Continuing to beat this drum has no positive value, and frankly is getting old. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 09:50:11 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E9A31065672 for ; Fri, 2 Sep 2011 09:50:11 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 17E978FC15 for ; Fri, 2 Sep 2011 09:50:10 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBEF5A.dip.t-dialin.net [217.251.239.90]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p829o8uI001935 for ; Fri, 2 Sep 2011 09:50:09 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id p829nsXu061888 for ; Fri, 2 Sep 2011 11:49:54 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id p829nmla093997 for ; Fri, 2 Sep 2011 09:49:54 GMT (envelope-from jhs@fire.js.berklix.net) Message-Id: <201109020949.p829nmla093997@fire.js.berklix.net> to: freebsd-ports@freebsd.org From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Fri, 02 Sep 2011 03:07:40 +0200." <201109020107.p8217eFJ089679@fire.js.berklix.net> Date: Fri, 02 Sep 2011 11:49:48 +0200 Sender: jhs@berklix.com Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 09:50:11 -0000 Hi, Reference: > From: "Julian H. Stacey" > Date: Fri, 02 Sep 2011 03:07:40 +0200 > Message-id: <201109020107.p8217eFJ089679@fire.js.berklix.net> I wrote: > Microsoft must grin at all us BSD, Linux, maybe Solaris & presumably > even now http://www.minix3.org free source enthusiasts reinventing > similar old ports shims for same old 3rd party wheels:. FYI: http://www.minix3.org -> http://wiki.minix3.org/en/UsersGuide/InstallingBinaryPackages -> http://pkgin.net/ " pkgin is known to work and have been tested under the following platforms : * NetBSD 4.0 * NetBSD 5.{0,1} * NetBSD current * DragonFly BSD 2.0 to 2.8 * DragonFly BSD current * Solaris 10/SunOS 5.10 * Opensolaris/SunOS 5.11 * Debian GNU/Linux 5.0 * Mac OS X 10.{5,6} * MINIX 3.1.8 " No /pub/FreeBSD/branches/-current/ports/ports-mgmt/pkgin . I'm not familiar with pkgin, but nice to see OS co-operation. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct. From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 09:57:32 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC5EA1065674 for ; Fri, 2 Sep 2011 09:57:32 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 771958FC0C for ; Fri, 2 Sep 2011 09:57:32 +0000 (UTC) Received: by iadx2 with SMTP id x2so3873430iad.13 for ; Fri, 02 Sep 2011 02:57:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gbgtfDd+nxsuh9GneB5aZw1TF001cPq0tkiTKcOf/xk=; b=JpqmRcxM9lHd+5foMs82vtPGOmeCZjiahQPnWEym3jXkKRYV+dCwZp7ZScmoLYLMJc MU8irKr9mcveVx9KFYZ//jPJrf+Chf/3dJaZNynCcwy4JBqAQUxdr2QQbiYfaXYciVaP DPTqqVFmO549vp7niT8k5XMa+C2XwL8JiaMf8= MIME-Version: 1.0 Received: by 10.231.26.68 with SMTP id d4mr1686060ibc.66.1314957451368; Fri, 02 Sep 2011 02:57:31 -0700 (PDT) Received: by 10.231.61.148 with HTTP; Fri, 2 Sep 2011 02:57:31 -0700 (PDT) Received: by 10.231.61.148 with HTTP; Fri, 2 Sep 2011 02:57:31 -0700 (PDT) In-Reply-To: <201109020949.p829nmla093997@fire.js.berklix.net> References: <201109020107.p8217eFJ089679@fire.js.berklix.net> <201109020949.p829nmla093997@fire.js.berklix.net> Date: Fri, 2 Sep 2011 10:57:31 +0100 Message-ID: From: Chris Rees To: "Julian H. Stacey" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-ports@freebsd.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 09:57:32 -0000 On 2 Sep 2011 10:50, "Julian H. Stacey" wrote: > FYI: > http://www.minix3.org -> > http://wiki.minix3.org/en/UsersGuide/InstallingBinaryPackages -> > http://pkgin.net/ > " > pkgin is known to work and have been tested under the following platforms : > * NetBSD 4.0 > * NetBSD 5.{0,1} > * NetBSD current > * DragonFly BSD 2.0 to 2.8 > * DragonFly BSD current > * Solaris 10/SunOS 5.10 > * Opensolaris/SunOS 5.11 > * Debian GNU/Linux 5.0 > * Mac OS X 10.{5,6} > * MINIX 3.1.8 > " > > No /pub/FreeBSD/branches/-current/ports/ports-mgmt/pkgin . > I'm not familiar with pkgin, but nice to see OS co-operation. > So, what do you actually mean by this? Chris From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 10:04:01 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8462C1065672 for ; Fri, 2 Sep 2011 10:04:01 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 42A6B8FC0A for ; Fri, 2 Sep 2011 10:04:01 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QzQbR-000CH1-LB for freebsd-ports@freebsd.org; Fri, 02 Sep 2011 12:04:01 +0200 Date: Fri, 2 Sep 2011 12:04:01 +0200 From: Kurt Jaeger To: freebsd-ports@freebsd.org Message-ID: <20110902100401.GO28186@home.opsec.eu> References: <201109020107.p8217eFJ089679@fire.js.berklix.net> <201109020949.p829nmla093997@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 10:04:01 -0000 Hi! > > http://pkgin.net/ [...] > > pkgin is known to work and have been tested under the following platforms [...] > So, what do you actually mean by this? Probably just this: What about trying to port pkgin for FreeBSD, so that pkgin can also be used on FreeBSD ? If this solves the binary pkg-install problem in a generic way on many plattforms (I have not looked at the implementation), that might be a nice feature. -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 10:38:57 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E725106567A for ; Fri, 2 Sep 2011 10:38:57 +0000 (UTC) (envelope-from jlaffaye.freebsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 17EE48FC13 for ; Fri, 2 Sep 2011 10:38:56 +0000 (UTC) Received: by fxe4 with SMTP id 4so1991645fxe.13 for ; Fri, 02 Sep 2011 03:38:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=H7da3AE23KyEQcjcJsqN72AjJLiZ6PDvvjHlNdaL4os=; b=p+qDDafxN5Xk2kEO4Xo+yCsHyiY+YVgKgHoqaNlLnYeYh2nefZMaQ6ZARyXSzF8HXN d47WJKNeQFTjkoqB2XjNh/4441oxwIH3yf91+mhC992LVp40HSu47Tf3wA5Gp1TwAZz+ WYJ8N9W3shEqCJSTSG/GULz1H2okkKPkiKY84= Received: by 10.223.62.76 with SMTP id w12mr1468737fah.123.1314959936113; Fri, 02 Sep 2011 03:38:56 -0700 (PDT) Received: from chulak.jlaffaye.net (esc31-1-78-245-92-55.fbx.proxad.net [78.245.92.55]) by mx.google.com with ESMTPS id l20sm634382fad.12.2011.09.02.03.38.55 (version=SSLv3 cipher=OTHER); Fri, 02 Sep 2011 03:38:55 -0700 (PDT) Sender: Julien Laffaye Message-ID: <4E60B23F.7050102@FreeBSD.org> Date: Fri, 02 Sep 2011 12:38:55 +0200 From: Julien Laffaye User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <201109020107.p8217eFJ089679@fire.js.berklix.net> <201109020949.p829nmla093997@fire.js.berklix.net> <20110902100401.GO28186@home.opsec.eu> In-Reply-To: <20110902100401.GO28186@home.opsec.eu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 10:38:57 -0000 On 09/02/2011 12:04, Kurt Jaeger wrote: > Hi! > >>> http://pkgin.net/ > [...] >>> pkgin is known to work and have been tested under the following platforms > [...] >> So, what do you actually mean by this? > > Probably just this: What about trying to port pkgin for FreeBSD, so that > pkgin can also be used on FreeBSD ? > We are working on pkgng[1], which is a complete rewrite of pkg_install instead of a higher level tool on top of it. Stay tuned for the alpha2 announcement. > If this solves the binary pkg-install problem in a generic > way on many plattforms (I have not looked at the implementation), > that might be a nice feature. > [1]: https://github.com/pkgng/pkgng From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 11:01:31 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3ACA2106566B for ; Fri, 2 Sep 2011 11:01:31 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirj.bris.ac.uk (dirj.bris.ac.uk [137.222.10.78]) by mx1.freebsd.org (Postfix) with ESMTP id EF4D58FC14 for ; Fri, 2 Sep 2011 11:01:30 +0000 (UTC) Received: from ncsc.bris.ac.uk ([137.222.10.41]) by dirj.bris.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1QzRV3-0002tI-NE for freebsd-ports@freebsd.org; Fri, 02 Sep 2011 12:01:29 +0100 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by ncsc.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1QzRV3-0004c4-KN for freebsd-ports@freebsd.org; Fri, 02 Sep 2011 12:01:29 +0100 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.4/8.14.4) with ESMTP id p82B1T3x092497 for ; Fri, 2 Sep 2011 12:01:29 +0100 (BST) (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.4/8.14.4/Submit) id p82B1TZ1092493 for freebsd-ports@freebsd.org; Fri, 2 Sep 2011 12:01:29 +0100 (BST) (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Fri, 2 Sep 2011 12:01:29 +0100 From: Anton Shterenlikht To: freebsd-ports@freebsd.org Message-ID: <20110902110129.GA84126@mech-cluster241.men.bris.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: configure options X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 11:01:31 -0000 I'm having problems building www/firefox on ia64. I was advised to: https://bugzilla.mozilla.org/show_bug.cgi?id=683879 --- Comment #3 from Boris Zbarsky (:bz) 2011-09-01 10:36:27 PDT --- Do things work if you do use --disable-ipc? -- How should I specify this option within the ports framework? Should it be something like make disable-ipc=yes Thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 12:05:06 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28FCD106566C for ; Fri, 2 Sep 2011 12:05:06 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by mx1.freebsd.org (Postfix) with ESMTP id CCA318FC16 for ; Fri, 2 Sep 2011 12:05:05 +0000 (UTC) Received: by qwg2 with SMTP id 2so2037199qwg.17 for ; Fri, 02 Sep 2011 05:05:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type; bh=BYPIsTtVCV7X4HLOW7XxSnG0GSsyddi0sX6rAqIo2jY=; b=XJOrVTbRqTnxHingRZAZX2Fuj6KZe3hkxtwYg43FZvy+wmmsZ72zkIjNzbEePnI8V7 wUHv/x1phQ7ingASf8xg5t+bThSUUX+uCVgEIY/lL3DAlcp91MOfktK1AtmqqoTb8ios SJ/iNmbytlKENjLlhzkpE64dtl0YJTShXKx5A= Received: by 10.229.34.69 with SMTP id k5mr651285qcd.258.1314963248042; Fri, 02 Sep 2011 04:34:08 -0700 (PDT) Received: from schism.local (c-76-124-49-145.hsd1.pa.comcast.net. [76.124.49.145]) by mx.google.com with ESMTPS id hv19sm1279818qab.7.2011.09.02.04.34.05 (version=SSLv3 cipher=OTHER); Fri, 02 Sep 2011 04:34:06 -0700 (PDT) Message-ID: <4E60BF2D.8050105@gmail.com> Date: Fri, 02 Sep 2011 07:34:05 -0400 From: Glen Barber User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0.1) Gecko/20110830 Thunderbird/6.0.1 MIME-Version: 1.0 To: Anton Shterenlikht References: <20110902110129.GA84126@mech-cluster241.men.bris.ac.uk> In-Reply-To: <20110902110129.GA84126@mech-cluster241.men.bris.ac.uk> X-Enigmail-Version: 1.3.1 Content-Type: multipart/mixed; boundary="------------060205020002070607000201" Cc: freebsd-ports@freebsd.org Subject: Re: configure options X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 12:05:06 -0000 This is a multi-part message in MIME format. --------------060205020002070607000201 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 9/2/11 7:01 AM, Anton Shterenlikht wrote: > I'm having problems building www/firefox on ia64. > I was advised to: > > https://bugzilla.mozilla.org/show_bug.cgi?id=683879 > > --- Comment #3 from Boris Zbarsky (:bz) 2011-09-01 10:36:27 PDT --- > Do things work if you do use --disable-ipc? > > -- > > How should I specify this option within > the ports framework? Should it be something > like > make disable-ipc=yes > No, it would need to be specified in the port's Makefile. I haven't tried it, but the attached patch may work. (Again, I haven't tried it.) :) Regards, -- Glen Barber --------------060205020002070607000201 Content-Type: text/plain; name="www-firefox-Makefile.diff.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="www-firefox-Makefile.diff.txt" --- /usr/ports/www/firefox/Makefile 2011-08-31 17:26:12.000000000 -0400 +++ Makefile 2011-09-02 07:30:47.330998597 -0400 @@ -49,6 +49,7 @@ --enable-application=browser \ --enable-official-branding --disable-updater \ --enable-canvas --enable-libxul --disable-necko-wifi \ + --disable-ipc \ --with-system-libevent=${LOCALBASE} OPTIONS= DBUS "Enable D-BUS support" on \ --------------060205020002070607000201-- From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 12:06:38 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A04EC106564A for ; Fri, 2 Sep 2011 12:06:38 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 2E4068FC14 for ; Fri, 2 Sep 2011 12:06:37 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBEF5A.dip.t-dialin.net [217.251.239.90]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p82C6a2d003145; Fri, 2 Sep 2011 12:06:36 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 p82C6PlG062434; Fri, 2 Sep 2011 14:06:25 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id p82C6DLr003739; Fri, 2 Sep 2011 12:06:19 GMT (envelope-from jhs@fire.js.berklix.net) Message-Id: <201109021206.p82C6DLr003739@fire.js.berklix.net> To: Chris Rees From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Fri, 02 Sep 2011 10:57:31 BST." Date: Fri, 02 Sep 2011 14:06:13 +0200 Sender: jhs@berklix.com Cc: freebsd-ports@freebsd.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 12:06:38 -0000 > > No /pub/FreeBSD/branches/-current/ports/ports-mgmt/pkgin . > > I'm not familiar with pkgin, but nice to see OS co-operation. > > So, what do you actually mean by this? Re-read: ] Microsoft must grin at all us BSD, Linux, .... ] ... reinventing similar old ports shims for same old 3rd party wheels I found a URL to a rare sample of co-operation. There's a German phrase about "Tellerrand" ... Its wise to occasionaly look beyond ones own soup bowl :-) BSDs should co-operate more, or lose. Linux is the small brother that's already outgrown us, & offers more users & jobs. NetBSD & FreeBSD don't even speak the same language on ports. 17th Sept in ~600 cities globaly, will be http://www.softwarefreedomday.org Mostly Linux people last year here, with an occasional BSD person. ( BTW A Lot of Ubuntu CDROMs have been distributed world wide to cities ready for free give away; a few of us tried to arrange a BSD catch up, but time & lack of a rich BSD sponsor for global mailing limited that. Please consider joining SFD as a BSD exhibitor in your city that day. ) BSD loses to Linux when visitors first ask "Does it have packages for ... ? How to build/ install those ?" & Linux people tune out at different answers for *BSDs. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct. From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 12:57:12 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C0861065670; Fri, 2 Sep 2011 12:57:12 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id B2E278FC18; Fri, 2 Sep 2011 12:57:11 +0000 (UTC) Received: by iadx2 with SMTP id x2so4078215iad.13 for ; Fri, 02 Sep 2011 05:57:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=WCESdH3Wi8fr6oXCqh5+ZAETuvynYGPkA0+N1miMyvU=; b=P80jerAEE17b89YC0KnR1L1SSqgtHa9ochhauBau7CeU9iezJm2kGilGF51BAkI0Kn 9FV6jCzVjYpcnSgMWpNjGpin+S7Qat+B8V7X58qxQp4UUOsdp5xlNEyqOgm9C1dTf6B0 9xzXp8tunuqNB1rfyRiC+XHD7LlilLNx8tK9M= Received: by 10.231.66.85 with SMTP id m21mr1972302ibi.53.1314968231124; Fri, 02 Sep 2011 05:57:11 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.61.148 with HTTP; Fri, 2 Sep 2011 05:56:41 -0700 (PDT) In-Reply-To: <201109020618.p826I250069551@repoman.freebsd.org> References: <201109020618.p826I250069551@repoman.freebsd.org> From: Chris Rees Date: Fri, 2 Sep 2011 13:56:41 +0100 X-Google-Sender-Auth: 8kMT3go5_dWtB506FeDt9A4p_gg Message-ID: To: Ade Lovett Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: ports@freebsd.org, cvs-ports@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: ports/www/apache22 Makefile distinfo X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 12:57:12 -0000 On 2 September 2011 07:18, Ade Lovett wrote: > ade =A0 =A0 =A0 =A0 2011-09-02 06:18:02 UTC > > =A0FreeBSD ports repository > > =A0Modified files: > =A0 =A0www/apache22 =A0 =A0 =A0 =A0 Makefile distinfo > =A0Log: > =A0Emergency upgrade to 2.2.20 - CVE-2011-3192. =A0Any complaints, talk t= o me. The vuxml originally marked all versions of Apache vulnerable, if portaudit complains that 2.2.20 is vulnerable please run portaudit -F. Chris From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 13:25:57 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB153106564A; Fri, 2 Sep 2011 13:25:57 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id A8DF58FC12; Fri, 2 Sep 2011 13:25:57 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id p82DPt0a087293; Fri, 2 Sep 2011 07:25:55 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id p82DPtaU087268; Fri, 2 Sep 2011 07:25:55 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Fri, 2 Sep 2011 07:25:55 -0600 (MDT) From: Warren Block To: Doug Barton In-Reply-To: <4E60A222.9040304@FreeBSD.org> Message-ID: References: <201109020924.p829OGAG000943@lurza.secnetix.de> <4E60A222.9040304@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Fri, 02 Sep 2011 07:25:56 -0600 (MDT) Cc: Oliver Fromme , freebsd-ports@freebsd.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 13:25:58 -0000 On Fri, 2 Sep 2011, Doug Barton wrote: > On 09/02/2011 02:24, Oliver Fromme wrote: >> Finally, I recommend to install ports-mgmt/pkg_cutleaves and >> run it regularly after updates > > portmaster -s does the same thing. Well, sorta. How it chooses what to offer to remove is different. portmaster -s offers to remove just gle here, then nothing on subsequent uses. pkg_cutleaves offers to remove every root and leaf port that's not depended on by another port. From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 13:58:04 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B07EF106564A; Fri, 2 Sep 2011 13:58:04 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 339828FC12; Fri, 2 Sep 2011 13:58:04 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id p82Dvl54032448; Fri, 2 Sep 2011 15:58:03 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id p82Dvl3l032446; Fri, 2 Sep 2011 15:57:47 +0200 (CEST) (envelope-from olli) From: Oliver Fromme Message-Id: <201109021357.p82Dvl3l032446@lurza.secnetix.de> To: dougb@FreeBSD.org (Doug Barton) Date: Fri, 2 Sep 2011 15:57:47 +0200 (CEST) In-Reply-To: <4E60A222.9040304@FreeBSD.org> X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (lurza.secnetix.de [127.0.0.1]); Fri, 02 Sep 2011 15:58:03 +0200 (CEST) Cc: freebsd-ports@FreeBSD.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 13:58:04 -0000 Doug Barton wrote: > On 09/02/2011 02:24, Oliver Fromme wrote: > > Finally, I recommend to install ports-mgmt/pkg_cutleaves and > > run it regularly after updates > > portmaster -s does the same thing. No. pkg_cutleaves finds ports that I have installed at some point in the past and then forgot about (and never used again), and offers me to delete them. portmaster -s doesn't find those. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs." -- Robert Firth From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 14:13:29 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF2D11065740; Fri, 2 Sep 2011 14:13:29 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id AB3468FC13; Fri, 2 Sep 2011 14:13:29 +0000 (UTC) Received: by iadx2 with SMTP id x2so4164369iad.13 for ; Fri, 02 Sep 2011 07:13:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=YNuXigcdmJupAsCToxW0bFwYMrP5Owwjr4vua20vylA=; b=kI/GLIMahoa9yWYNSBNUlM/arQTkJLtZyKPeJBfohPjmI4AIe/qqevNVfZ84efKMUW 38/pX4WXKFKMXfd3a9hYyTvLNFEpojlUOqhvMdc5isIKD+9b+I9zkM6BuDFnOWo5M/Fm GhazopPIT7n/GuYt4Vp5Lhk26wX3/Kh2YJTzo= Received: by 10.42.144.1 with SMTP id z1mr948802icu.306.1314972808144; Fri, 02 Sep 2011 07:13:28 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.61.148 with HTTP; Fri, 2 Sep 2011 07:12:58 -0700 (PDT) In-Reply-To: <20110829121415.237a3571@lab.lovett.com> References: <4E5643A8.9060705@yandex.ru> <4E564DBE.1070700@yandex.ru> <4E574264.6020600@yandex.ru> <20110829121415.237a3571@lab.lovett.com> From: Chris Rees Date: Fri, 2 Sep 2011 15:12:58 +0100 X-Google-Sender-Auth: IbE7MlufcxFpfUD4PEgxBAEb220 Message-ID: To: Ade Lovett Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Ports Mailing List Subject: Re: tinderbox: how to drop unneded Jail and Build X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 14:13:30 -0000 On 29 August 2011 18:14, Ade Lovett wrote: > On Fri, 26 Aug 2011 11:10:30 +0100 > Chris Rees wrote: > >> http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/tinderweb/dbsrc/ >> >> Watch out, there be dragons :( > > But they're happy dragons ;) > > As an aside, if there's likely to be 'official' translations of the > tinderbox documents, it may be useful to follow the way in which the > Handbook is generated under /usr/doc, move (most of?) the current > contents of dbsrc/ to dbsrc/en and go from there. After some discussion on #bsdports, it was suggested that I work on the lovely task of using the current doc Makefiles to render the Tinderbox docs. Obviously this has several advantages; FreeBSD docs people will understand it rather than some horrible Makefile I hacked together, perhaps it'll properly support Tips, Notes and Warnings etc, translations would be properly supported. However, I am not a docs guy, and have finally given up on the Make structure that's there -- now I remember why I wrote my Makefile in the first place; I just can't work it out. Perhaps I'm just being thick. Any docs people happy to attempt to migrate the build system for the Tinderbox README to FreeBSD-doc format? I'm pretty sure marcus would rather keep it where it is; it's an upstream thing rather than an OS thing. Chris From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 14:50:58 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16915106564A; Fri, 2 Sep 2011 14:50:58 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id AB2E28FC0A; Fri, 2 Sep 2011 14:50:57 +0000 (UTC) Received: by qyk9 with SMTP id 9so1989805qyk.13 for ; Fri, 02 Sep 2011 07:50:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=WG9yvaR5MdAzzKzv0jcel7TOK6D+2fBDKMxnfOLeoyg=; b=U5xjh0ylfXIUJk6z336/nX0rTGCnUHePccIZsG8B0Ga79LcRBEkaOKA+X5xci0T1hw OENYNOi3NPkhL+edKY1voUeMQEOKXu9ryIYQ3wu/9i3xzvwkDQYNEnvZzSaUOAIjgfzM UYg7Wga1r9mFnw756sfkGuipEY9zJWhnos8WQ= Received: by 10.224.189.130 with SMTP id de2mr821900qab.43.1314973199021; Fri, 02 Sep 2011 07:19:59 -0700 (PDT) Received: from schism.local (75-146-225-65-Philadelphia.hfc.comcastbusiness.net. [75.146.225.65]) by mx.google.com with ESMTPS id if17sm1561597qab.23.2011.09.02.07.19.56 (version=SSLv3 cipher=OTHER); Fri, 02 Sep 2011 07:19:57 -0700 (PDT) Message-ID: <4E60E60C.6080700@gmail.com> Date: Fri, 02 Sep 2011 10:19:56 -0400 From: Glen Barber User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0.1) Gecko/20110830 Thunderbird/6.0.1 MIME-Version: 1.0 To: Chris Rees References: <4E5643A8.9060705@yandex.ru> <4E564DBE.1070700@yandex.ru> <4E574264.6020600@yandex.ru> <20110829121415.237a3571@lab.lovett.com> In-Reply-To: X-Enigmail-Version: 1.3.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports Mailing List , Ade Lovett Subject: Re: tinderbox: how to drop unneded Jail and Build X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 14:50:58 -0000 On 9/2/11 10:12 AM, Chris Rees wrote: > Any docs people happy to attempt to migrate the build system for the > Tinderbox README to FreeBSD-doc format? I'm pretty sure marcus would > rather keep it where it is; it's an upstream thing rather than an OS > thing. > I'll be happy to help. -- Glen Barber From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 19:53:09 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9DE07106564A for ; Fri, 2 Sep 2011 19:53:09 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 80D618FC13 for ; Fri, 2 Sep 2011 19:53:09 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 2D5FF5615B; Fri, 2 Sep 2011 14:53:09 -0500 (CDT) Date: Fri, 2 Sep 2011 14:53:09 -0500 From: Mark Linimon To: Michel Talon Message-ID: <20110902195309.GC19413@lonesome.com> References: <20110902093914.GA92386@lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110902093914.GA92386@lpthe.jussieu.fr> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: ports@freebsd.org Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 19:53:09 -0000 On Fri, Sep 02, 2011 at 11:39:14AM +0200, Michel Talon wrote: > My point is that there shouldn't be any edge cases In a perfect world: yes. > I certainly don't have any precise idea of the things which should be > changed so that edge cases disappear Well, then, we're right back where we started. > only *very experienced* people having observed a lot of failure cases > could give correct advices. And we haven't figured them out yet. As the tools get better (which they are), we can get more insight into this. But, as you already understand, it's really hard. > Having a file which documents manual intervention is a perpetual > tenptation to do the things the sloppy way I disagree with your logic. None of the FreeBSD committers _want_ this to be difficult. mcl From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 20:08:50 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EC11106566B for ; Fri, 2 Sep 2011 20:08:50 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 37F948FC14 for ; Fri, 2 Sep 2011 20:08:49 +0000 (UTC) Received: by iadx2 with SMTP id x2so4547260iad.13 for ; Fri, 02 Sep 2011 13:08:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ibm3QrN+N/awgo/Yitkn5xYJTqiqTYPVZzMwi169H4s=; b=lxk03vzKH0vcpAS2g/6JU0qUJG0Thmi3raWaol1aTNSYiWQ5MArHX3+8AwvdVmMNf9 BZLF2v675uWXutQws/rvi6sRYOC2xq60z8+MkOSHYCByr0IG4hIGVMAw4zv/hnxsb17L 6Mq9oaKqHQVmcDr2kfjiyEY6NJHdnmBwho2x0= MIME-Version: 1.0 Received: by 10.231.66.85 with SMTP id m21mr2678404ibi.53.1314994129378; Fri, 02 Sep 2011 13:08:49 -0700 (PDT) Received: by 10.231.61.148 with HTTP; Fri, 2 Sep 2011 13:08:49 -0700 (PDT) Received: by 10.231.61.148 with HTTP; Fri, 2 Sep 2011 13:08:49 -0700 (PDT) In-Reply-To: <20110902195309.GC19413@lonesome.com> References: <20110902093914.GA92386@lpthe.jussieu.fr> <20110902195309.GC19413@lonesome.com> Date: Fri, 2 Sep 2011 21:08:49 +0100 Message-ID: From: Chris Rees To: Mark Linimon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: ports@freebsd.org, Michel Talon Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 20:08:50 -0000 On 2 Sep 2011 20:53, "Mark Linimon" wrote: > > On Fri, Sep 02, 2011 at 11:39:14AM +0200, Michel Talon wrote: > > My point is that there shouldn't be any edge cases > > In a perfect world: yes. > > > I certainly don't have any precise idea of the things which should be > > changed so that edge cases disappear > > Well, then, we're right back where we started. > > > only *very experienced* people having observed a lot of failure cases > > could give correct advices. > > And we haven't figured them out yet. > > As the tools get better (which they are), we can get more insight into > this. But, as you already understand, it's really hard. > > > Having a file which documents manual intervention is a perpetual > > tenptation to do the things the sloppy way > > I disagree with your logic. None of the FreeBSD committers _want_ this > to be difficult. > +1. Most of us despise its very existence, but recognise that just sometimes, it saves some horribly fragile code from being written. Chris From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 20:30:07 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83E291065676 for ; Fri, 2 Sep 2011 20:30:07 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo203.cox.net (eastrmfepo203.cox.net [68.230.241.218]) by mx1.freebsd.org (Postfix) with ESMTP id 23C6C8FC0A for ; Fri, 2 Sep 2011 20:30:06 +0000 (UTC) Received: from eastrmimpo02.cox.net ([68.1.16.120]) by eastrmfepo203.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20110902203001.HDKA32702.eastrmfepo203.cox.net@eastrmimpo02.cox.net>; Fri, 2 Sep 2011 16:30:01 -0400 Received: from serene.no-ip.org ([98.164.87.41]) by eastrmimpo02.cox.net with bizsmtp id TwW01h00P0tX9KW02wW1Vz; Fri, 02 Sep 2011 16:30:01 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020207.4E613CC9.0050,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=ax4i8a8snyEA9uWfgWYmXW+3D+RWNhitQWxcW0Jxd9c= c=1 sm=1 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=HSeXd6ud8jGmpzpM0y1GZQ==:17 a=rZ1T3NJVAAAA:8 a=pQs5aej7AAAA:8 a=kviXuzpPAAAA:8 a=O4-tmol2Szh9qA0NEB8A:9 a=CjuIK1q_8ugA:10 a=4vB-4DCPJfMA:10 a=nNPicEwBKPexN_SG:21 a=USPOjXo8VZMCJkv5:21 a=HSeXd6ud8jGmpzpM0y1GZQ==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from cox.net (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id p82KU0TP002222; Fri, 2 Sep 2011 15:30:00 -0500 (CDT) (envelope-from conrads@cox.net) Date: Fri, 2 Sep 2011 15:29:55 -0500 From: "Conrad J. Sabatier" To: Anton Shterenlikht Message-ID: <20110902152955.2b92396a@cox.net> In-Reply-To: <20110902110129.GA84126@mech-cluster241.men.bris.ac.uk> References: <20110902110129.GA84126@mech-cluster241.men.bris.ac.uk> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: configure options X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 20:30:07 -0000 On Fri, 2 Sep 2011 12:01:29 +0100 Anton Shterenlikht wrote: > I'm having problems building www/firefox on ia64. > I was advised to: > > https://bugzilla.mozilla.org/show_bug.cgi?id=683879 > > --- Comment #3 from Boris Zbarsky (:bz) > 2011-09-01 10:36:27 PDT --- Do things work if you do use > --disable-ipc? > > -- > > How should I specify this option within > the ports framework? Should it be something > like > make disable-ipc=yes Anytime you need to tinker with the arguments to a port that uses a GNU configure script, you'll want to add a line to the top-level Makefile, somewhere after any existing CONFIGURE_ARGS definition(s), if any: CONFIGURE_ARGS+= --disable-ipc (Note the use of the "+=" operator. This will ensure that any configure options you add won't replace those already specified in the Makefile, but will be appended to them instead) If you cd to the port's WRKDIR, you can run "./configure --help" to see all of the possible options. HTH -- Conrad J. Sabatier conrads@cox.net From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 21:03:47 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C429106564A for ; Fri, 2 Sep 2011 21:03:47 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 2C7B68FC0A for ; Fri, 2 Sep 2011 21:03:46 +0000 (UTC) Received: from outgoing.leidinger.net (p4FC469A2.dip.t-dialin.net [79.196.105.162]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id DB01384400D; Fri, 2 Sep 2011 22:44:55 +0200 (CEST) Received: from webmail.leidinger.net (webmail.Leidinger.net [IPv6:fd73:10c7:2053:1::3:102]) by outgoing.leidinger.net (Postfix) with ESMTP id 2A709278F; Fri, 2 Sep 2011 22:44:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1314996293; bh=CcCvDYaQQfHoTODhcJdeW+dO2XSN8jXI5iNA6tV0H4A=; h=Message-ID:Date:From:To:Cc:Subject:References:In-Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding; b=ZMCI3dziMoNU2WM8zu9Cef6VMl8rbCCsTotBRwfZ7wsvJbX5/MPwienM6orjYDacf lFtSyDHulCRIjH+ff8pXyRUEzTxboigcNoycOIcT/CWR/44noZchifBTxIrs/bvKM7 gC3IKYdswdxw7ZJND7PD6z74g9fklsM3MFL7GxBPQ3PXA2XKoXtKJ9apngnamY0TVF SaEZKM+b+FNWmKy1OmHeBTM3sESUscJytoX/Ic5P7AwYM/M0EhwhnCExt5Dmfinrfa ljkqi6H/S5jrHYqwdwD0I57qUpRtPN+1NZ9oZmeyyWXBPkvlHiE9iKpo10wBgaWijO 8is7jL4TpPoyw== Received: (from www@localhost) by webmail.leidinger.net (8.14.4/8.14.4/Submit) id p82Kiqgv093681; Fri, 2 Sep 2011 22:44:52 +0200 (CEST) (envelope-from Alexander@Leidinger.net) X-Authentication-Warning: webmail.leidinger.net: www set sender to Alexander@Leidinger.net using -f Received: from fd73:10c7:2053:1:ccbf:a2a0:3f14:81ac ([fd73:10c7:2053:1:ccbf:a2a0:3f14:81ac]) by webmail.leidinger.net (Horde Framework) with HTTP; Fri, 02 Sep 2011 22:44:52 +0200 Message-ID: <20110902224452.68473liyjz7zutl0@webmail.leidinger.net> Date: Fri, 02 Sep 2011 22:44:52 +0200 From: Alexander Leidinger To: Oliver Fromme References: <201109020924.p829OGAG000943@lurza.secnetix.de> In-Reply-To: <201109020924.p829OGAG000943@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Dynamic Internet Messaging Program (DIMP) H3 (1.1.6) X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: DB01384400D.A2E03 X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-0.1, required 6, autolearn=disabled, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1315601096.34922@JiY2eagwai/RaFU7H6HUTw X-EBL-Spam-Status: No Cc: freebsd-ports@FreeBSD.ORG Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 21:03:47 -0000 Quoting Oliver Fromme (from Fri, 2 Sep 2011 11:24:16 +0200 (CEST)): > The other extreme are people who run a cron job every night > that updates /usr/ports (*) and runs "400.status-pkg" (from > /etc/periodic/weekly), possibly even followed by an automated > update (**). Of course this will sometimes break. That's > normal and to be expected, because the ports collection is > changed and modified constantly by many people, except during > freeze. There is always something that's broken. If you're > affected, you need to postpone the update of the respective > ports until someone (possibly including yourself) unbreaks it. > That's the price to pay when you want to be on the "bleeding > edge" instead of waiting for the next freeze and updating the > ports to the release tag only. No, that's the price to pay if you do not use all available tools. Personally I make a FS snapshot before updating. We should recomment to do this in all sensible places, and maybe even add code to portmaster/portupgrade which tells to make a snapshot if there is none (where possible). This way a rollback to a known good state is possible if someone gets hit by an instability (someone still can get hit, but the impact is a lot lower). Yes, I know that ZFS (the FS where it is very easy to snapshot and rollback) is not used everywhere, but the new installer for 9.0 offers now the possibility and we should tell the people what is possible now. Bye, Alexander. -- Important letters which contain no errors will develop errors in the mail. Corresponding errors will show up in the duplicate while the Boss is reading it. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 21:19:52 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B78BC1065679 for ; Fri, 2 Sep 2011 21:19:52 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 33D8D8FC23 for ; Fri, 2 Sep 2011 21:19:52 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id p82LJYUH050063; Fri, 2 Sep 2011 23:19:50 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id p82LJYbP050061; Fri, 2 Sep 2011 23:19:34 +0200 (CEST) (envelope-from olli) From: Oliver Fromme Message-Id: <201109022119.p82LJYbP050061@lurza.secnetix.de> To: Alexander@leidinger.net (Alexander Leidinger) Date: Fri, 2 Sep 2011 23:19:34 +0200 (CEST) In-Reply-To: <20110902224452.68473liyjz7zutl0@webmail.leidinger.net> X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.5 (lurza.secnetix.de [127.0.0.1]); Fri, 02 Sep 2011 23:19:50 +0200 (CEST) Cc: freebsd-ports@FreeBSD.ORG Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 21:19:52 -0000 Alexander Leidinger wrote: > Quoting Oliver Fromme (from Fri, 2 Sep 2011 > 11:24:16 +0200 (CEST)): > > > The other extreme are people who run a cron job every night > > that updates /usr/ports (*) and runs "400.status-pkg" (from > > /etc/periodic/weekly), possibly even followed by an automated > > update (**). Of course this will sometimes break. That's > > normal and to be expected, because the ports collection is > > changed and modified constantly by many people, except during > > freeze. There is always something that's broken. If you're > > affected, you need to postpone the update of the respective > > ports until someone (possibly including yourself) unbreaks it. > > That's the price to pay when you want to be on the "bleeding > > edge" instead of waiting for the next freeze and updating the > > ports to the release tag only. > > No, Yes, it is. :-) > that's the price to pay if you do not use all available tools. > Personally I make a FS snapshot before updating. We should recomment > to do this in all sensible places, and maybe even add code to > portmaster/portupgrade which tells to make a snapshot if there is none > (where possible). This way a rollback to a known good state is > possible if someone gets hit by an instability (someone still can get > hit, but the impact is a lot lower). Yes, I know that ZFS (the FS > where it is very easy to snapshot and rollback) is not used > everywhere, but the new installer for 9.0 offers now the possibility > and we should tell the people what is possible now. I wrote that the price to pay is that you have to postpone the update of respective ports. And this is true, no matter if you use snapshots or not (or something else). Having to roll back to a working system is a problem that I didn't talk about at all. Snapshots can be used for this, of course. Personally I cannot use snapshots, but I keep packages of all working ports (created with "make package" or "pkg_create -b"), so I can easily roll back if necessary. However, that happens very rarely because I watch the mailing lists carefully before updates, so I notice in advance if there is any major breakage. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "A language that doesn't have everything is actually easier to program in than some that do." -- Dennis M. Ritchie From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 21:22:00 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id F4080106564A for ; Fri, 2 Sep 2011 21:21:59 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id BF8FF152F01; Fri, 2 Sep 2011 21:21:58 +0000 (UTC) Message-ID: <4E6148F6.3020600@FreeBSD.org> Date: Fri, 02 Sep 2011 14:21:58 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.1) Gecko/20110901 Thunderbird/6.0.1 MIME-Version: 1.0 To: Warren Block References: <201109020924.p829OGAG000943@lurza.secnetix.de> <4E60A222.9040304@FreeBSD.org> In-Reply-To: X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Oliver Fromme , freebsd-ports@freebsd.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 21:22:00 -0000 On 09/02/2011 06:25, Warren Block wrote: > On Fri, 2 Sep 2011, Doug Barton wrote: > >> On 09/02/2011 02:24, Oliver Fromme wrote: >>> Finally, I recommend to install ports-mgmt/pkg_cutleaves and >>> run it regularly after updates >> >> portmaster -s does the same thing. > > Well, sorta. How it chooses what to offer to remove is different. > portmaster -s offers to remove just gle here, then nothing on subsequent > uses. > > pkg_cutleaves offers to remove every root and leaf port that's not > depended on by another port. Fair enough. My feeling on that is that it's dangerous, since even though something technically may not be a dependency of something it may still be needed. Users can do 'portmaster -l' and look at the list of roots and leaves to see what could possibly be deleted, and then 'portmaster -e unwanted-port' will remove it, and then run portmaster -s when it's done. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 21:40:54 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3EA8B106566C; Fri, 2 Sep 2011 21:40:54 +0000 (UTC) (envelope-from cwhiteh@onetel.com) Received: from woodbine.london.02.net (woodbine.london.02.net [87.194.255.145]) by mx1.freebsd.org (Postfix) with ESMTP id DB85B8FC0A; Fri, 2 Sep 2011 21:40:53 +0000 (UTC) Received: from muji2.config (93.97.24.219) by woodbine.london.02.net (8.5.140) id 4E261CD10169933A; Fri, 2 Sep 2011 22:40:50 +0100 Message-ID: <4E614D62.9050109@onetel.com> Date: Fri, 02 Sep 2011 22:40:50 +0100 From: Chris Whitehouse User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100924 Thunderbird/3.1.4 MIME-Version: 1.0 To: Ruslan Mahmatkhanov References: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> <4E5E3364.7050308@yandex.ru> <4E5E7EAA.4030303@onetel.com> <4E5E84B4.6040200@yandex.ru> <4E5EB5ED.9080506@onetel.com> <4E60916A.2020002@yandex.ru> In-Reply-To: <4E60916A.2020002@yandex.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, acm@FreeBSD.org, perryh@pluto.rain.com Subject: Re: editors/zim X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 21:40:54 -0000 On 02/09/2011 09:18, Ruslan Mahmatkhanov wrote: > Chris Whitehouse wrote on 01.09.2011 02:30: > > [skipping the details since original problem was solved] did you see that I had to add a line for MD5 to distinfo to make it work on my 8.1-R system? Though the last change was to remove MD5... > >> Now it builds and installs and is working fine, _and_ my original >> problem has gone away. >> >> thanks very much for your help. I'll drop the author a line to say it's >> been fixed. >> >> Chris > > Sorry for delay, i now added sqlite3 dependency and some optional > dependencies for zim plugins (besides the gtkspell one, since the plugin > needs python binding to gtkspell that we seems lacking in the ports > tree). This pr was submitted: http://bugs.freebsd.org/160385. > > I also reupploaded port tarball and the diff. Thanks for all that. I've put a watch on it on freshports so I'll get notified when it gets committed. Oh and the author says watch out for version 0.53 coming out in the next couple of weeks :P cheers Chris > From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 22:24:47 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCF50106566C; Fri, 2 Sep 2011 22:24:47 +0000 (UTC) (envelope-from lars@larseighner.com) Received: from mail.team1internet.com (mail.team1internet.com [216.110.13.10]) by mx1.freebsd.org (Postfix) with ESMTP id 67BAA8FC1A; Fri, 2 Sep 2011 22:24:47 +0000 (UTC) Received: from larseighner.com (unknown [216.110.13.82]) by mail.team1internet.com (Postfix) with SMTP id 21C2616B4BB; Fri, 2 Sep 2011 16:58:45 -0500 (CDT) Received: by larseighner.com (nbSMTP-1.00) for uid 1001 lars@larseighner.com; Fri, 2 Sep 2011 16:58:15 -0500 (CDT) Date: Fri, 2 Sep 2011 16:58:11 -0500 (CDT) From: Lars Eighner X-X-Sender: lars@noos.6dollardialup To: "Julian H. Stacey" In-Reply-To: <201109011333.p81DX2sN081775@fire.js.berklix.net> Message-ID: References: <201109011333.p81DX2sN081775@fire.js.berklix.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: ports@freebsd.org, Sergey Matveychuk Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 22:24:47 -0000 On Thu, 1 Sep 2011, Julian H. Stacey wrote: > Hi, > Suggestion: pkgdb is too cryptic even with -v, > it needs more explanation what it is up to & > particularly what decisions it asks from user Of course you never see messages from pkgdb unless something has gone wrong. Some things go wrong in common predicatable ways, and there really should be some kind of lint for those things (as for example when a package/port is moved). > Even 'stale dependency' is not clear. Is it missing or what. Essentially. > Doubtless could be figured out with enough other pkg commands & ls, > but slightly extending various print commands within pkgdb would be nice. The main thing here, of course, is that ports uses "dependency" in the exact opposite of its normal English sense (just as twitter uses "following" in the exact opposite of its normal English sense). In normal Engish 'X is a dependency of Y' means Y is necessary for X (X depends on Y), but instead in ports (and computer talk in general so far as I can tell) it means X is necessary for Y (Y depends on X). Because 'dependency' is used backwards, that leaves a variety of awkward expressions to be used when the meaning really is 'dependency.' > Checking for origin duplicates > ...... > Checking linkchecker-6.3 > Stale dependency: linkchecker-6.3 -> tidy-lib-090315.c_1 (www/tidy-lib): > Disclose depends for linkchecker-6.3 > tidy-20000804_2 (score:19%) ? ([y]es/[n]o/[a]ll) [no] > > No clue is given what score means or what decision program wants > user to make. Ignore the score for best results. This is a bit like a spell checker that gives only its first guess and calculates its confidence in that first guess. As with a spelling checker, if you do not recognize that first guess as right, you need to do your own research (such as opening a dead-tree dictionary and actually - gasp - looking it up for yourself). You will almost always immediately recognize as correct the suggestion when the dependency has simply bumped versions. Some other possibilities are: * Something (maybe you) has deleted the package/port that the subject needs. This can happen when two libs compete for the same space and you force the installation of a second one. * The package/port has been absorbed into another package/port or the base system. * The package/port a new name. * The package/port has been split. Maybe all of the parts are needed, and maybe only one. * A bad miracle hs occurred. Many of these thing could be fixed automagically with a ports lint, but maintaining it would be a big pain. If you want brain-dead, you can try Fedora 15 or its role-model hero Windows. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 23:34:11 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B806106566C for ; Fri, 2 Sep 2011 23:34:11 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by mx1.freebsd.org (Postfix) with ESMTP id E769A8FC08 for ; Fri, 2 Sep 2011 23:34:10 +0000 (UTC) Received: by qwg2 with SMTP id 2so2514612qwg.17 for ; Fri, 02 Sep 2011 16:34:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=U1nEWmTW1hBVirGkRpkP5VP7q9OQq4gfmGAmRe3DVXU=; b=XWP+vxHNm+SpTNWJ1yfZTq9yJmflzYT/0N1x/LIlP8ZdhE7SyMAwjwN8o6H2tFcxQh a7iN1FVDvrzXXs1UULjdgmk71wM+98zgQACoo5cDNPYTYhvTDnar4C6e4kfayHglAuuu +Fd5+GbhAmrZDSt/DU3u5PkSTzodAcriM2sXg= Received: by 10.224.31.7 with SMTP id w7mr1206638qac.191.1315006450184; Fri, 02 Sep 2011 16:34:10 -0700 (PDT) Received: from schism.local (c-76-124-49-145.hsd1.pa.comcast.net. [76.124.49.145]) by mx.google.com with ESMTPS id dr7sm437354qab.26.2011.09.02.16.34.08 (version=SSLv3 cipher=OTHER); Fri, 02 Sep 2011 16:34:08 -0700 (PDT) Message-ID: <4E6167EF.1010601@gmail.com> Date: Fri, 02 Sep 2011 19:34:07 -0400 From: Glen Barber User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0.1) Gecko/20110830 Thunderbird/6.0.1 MIME-Version: 1.0 To: Chris Whitehouse References: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> <4E5E3364.7050308@yandex.ru> <4E5E7EAA.4030303@onetel.com> <4E5E84B4.6040200@yandex.ru> <4E5EB5ED.9080506@onetel.com> <4E60916A.2020002@yandex.ru> <4E614D62.9050109@onetel.com> In-Reply-To: <4E614D62.9050109@onetel.com> X-Enigmail-Version: 1.3.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org Subject: Re: editors/zim X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 23:34:11 -0000 Hi Chris, On 9/2/11 5:40 PM, Chris Whitehouse wrote: > did you see that I had to add a line for MD5 to distinfo to make it work > on my 8.1-R system? Though the last change was to remove MD5... > It sounds to me parts of your ports tree may be out of sync. MD5 distfile validation was removed from ports some time ago. How do you update your ports tree? Regards, Glen -- Glen Barber From owner-freebsd-ports@FreeBSD.ORG Fri Sep 2 23:53:58 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id A40551065673 for ; Fri, 2 Sep 2011 23:53:58 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 751E014D829; Fri, 2 Sep 2011 23:53:57 +0000 (UTC) Message-ID: <4E616C94.8070907@FreeBSD.org> Date: Fri, 02 Sep 2011 16:53:56 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.1) Gecko/20110901 Thunderbird/6.0.1 MIME-Version: 1.0 To: jun-g@daemonfreaks.com References: <201109022344.p82NiiEd017750@repoman.freebsd.org> In-Reply-To: <201109022344.p82NiiEd017750@repoman.freebsd.org> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 X-Forwarded-Message-Id: <201109022344.p82NiiEd017750@repoman.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-ports@FreeBSD.org" Subject: Fwd: cvs commit: ports/www/pyblosxom Makefile X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2011 23:53:58 -0000 FYI. Maintainer, there is a new version available, are you interested in continuing to maintain this port, or would you like to release it? I forgot to include the expiration in this commit, but I subsequently set it to expire at the end of this month. Thanks, Doug -------- Original Message -------- Subject: cvs commit: ports/www/pyblosxom Makefile Date: Fri, 2 Sep 2011 23:44:44 +0000 (UTC) From: Doug Barton To: ports-committers@FreeBSD.org, cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org dougb 2011-09-02 23:44:44 UTC FreeBSD ports repository Modified files: www/pyblosxom Makefile Log: FORBIDDEN= Vulnerable since 2009-02-11 http://portaudit.freebsd.org/b07f3254-f83a-11dd-85a4-ea653f0746ab.html Revision Changes Path 1.16 +2 -0 ports/www/pyblosxom/Makefile http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/www/pyblosxom/Makefile.diff?&r1=1.15&r2=1.16&f=h From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 04:13:21 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 909761065673 for ; Sat, 3 Sep 2011 04:13:21 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 230078FC1F for ; Sat, 3 Sep 2011 04:13:20 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p834D72X047425 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 2 Sep 2011 21:13:10 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p834D7XX047424; Fri, 2 Sep 2011 21:13:07 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA05486; Fri, 2 Sep 11 21:03:44 PDT Date: Sat, 03 Sep 2011 04:03:37 -0700 From: perryh@pluto.rain.com To: jhs@berklix.com, pi@opsec.eu, lists@opsec.eu Message-Id: <4e620989.2u8JKPlqzj1SCewo%perryh@pluto.rain.com> References: <201109020107.p8217eFJ089679@fire.js.berklix.net> <201109020949.p829nmla093997@fire.js.berklix.net> <20110902100401.GO28186@home.opsec.eu> In-Reply-To: <20110902100401.GO28186@home.opsec.eu> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 04:13:21 -0000 Kurt Jaeger wrote: > Probably just this: What about trying to port pkgin for FreeBSD, > so that pkgin can also be used on FreeBSD ? Volunteers? From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 05:28:51 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 9815F106567D; Sat, 3 Sep 2011 05:28:51 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 18AA814E2CE; Sat, 3 Sep 2011 05:28:49 +0000 (UTC) Message-ID: <4E61BB11.9070007@FreeBSD.org> Date: Fri, 02 Sep 2011 22:28:49 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.1) Gecko/20110901 Thunderbird/6.0.1 MIME-Version: 1.0 To: Lars Eighner References: <201109011333.p81DX2sN081775@fire.js.berklix.net> In-Reply-To: X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, "Julian H. Stacey" , Sergey Matveychuk Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 05:28:51 -0000 On 09/02/2011 14:58, Lars Eighner wrote: > The main thing here, of course, is that ports uses "dependency" in the > exact > opposite of its normal English sense (just as twitter uses "following" in > the exact opposite of its normal English sense). > > In normal Engish 'X is a dependency of Y' means Y is necessary for X (X > depends on Y) I'm not sure why you believe this to be true. Can you give examples from non-technical English prose, and some dictionary definitions to back up your claim? Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 06:17:20 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50428106564A; Sat, 3 Sep 2011 06:17:20 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward6.mail.yandex.net (forward6.mail.yandex.net [IPv6:2a02:6b8:0:202::1]) by mx1.freebsd.org (Postfix) with ESMTP id C62788FC0C; Sat, 3 Sep 2011 06:17:19 +0000 (UTC) Received: from smtp8.mail.yandex.net (smtp8.mail.yandex.net [77.88.61.54]) by forward6.mail.yandex.net (Yandex) with ESMTP id EBD17F80C2A; Sat, 3 Sep 2011 10:17:17 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1315030638; bh=vQYUdadnfSNykQeL18rsR49KWFbIdjM5AR6pzgwp6C0=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=sn/VU02A9D7XYdzrjfjHsrggnpj+IBWiq1iccUS5Tkn3P4EUY7bfPevSVUEii5VZe yUcS7qYE0pGCJ0jmU+J9pkQCAvh1KaCTaiyErWNGogHxbM3lcTXtKzVYRX3GU09LnO K7PI6M1CMzsPIpeNkzt+0J+KcteQD01w/1p7z1Xs= Received: from smtp8.mail.yandex.net (localhost [127.0.0.1]) by smtp8.mail.yandex.net (Yandex) with ESMTP id C43A71B603D3; Sat, 3 Sep 2011 10:17:17 +0400 (MSD) Received: from unknown (unknown [213.138.88.133]) by smtp8.mail.yandex.net (nwsmtp/Yandex) with ESMTP id HHa0IKmB; Sat, 3 Sep 2011 10:17:17 +0400 X-Yandex-Spam: 1 Message-ID: <4E61C668.80403@yandex.ru> Date: Sat, 03 Sep 2011 10:17:12 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: Chris Whitehouse References: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> <4E5E3364.7050308@yandex.ru> <4E5E7EAA.4030303@onetel.com> <4E5E84B4.6040200@yandex.ru> <4E5EB5ED.9080506@onetel.com> <4E60916A.2020002@yandex.ru> <4E614D62.9050109@onetel.com> In-Reply-To: <4E614D62.9050109@onetel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, acm@FreeBSD.org, perryh@pluto.rain.com Subject: Re: editors/zim X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 06:17:20 -0000 Chris Whitehouse wrote on 03.09.2011 01:40: > On 02/09/2011 09:18, Ruslan Mahmatkhanov wrote: >> Chris Whitehouse wrote on 01.09.2011 02:30: >> >> [skipping the details since original problem was solved] > > did you see that I had to add a line for MD5 to distinfo to make it work > on my 8.1-R system? Though the last change was to remove MD5... Yes, but MD5 checksums in ports was retired some time ago, so it's not needed anymore, and actually ports system will complain about unknown hashing method. It's just your old ports tree issue (also as "Unknown component pygobject"). >>> Now it builds and installs and is working fine, _and_ my original >>> problem has gone away. >>> >>> thanks very much for your help. I'll drop the author a line to say it's >>> been fixed. >>> >>> Chris >> >> Sorry for delay, i now added sqlite3 dependency and some optional >> dependencies for zim plugins (besides the gtkspell one, since the plugin >> needs python binding to gtkspell that we seems lacking in the ports >> tree). This pr was submitted: http://bugs.freebsd.org/160385. >> >> I also reupploaded port tarball and the diff. > > Thanks for all that. I've put a watch on it on freshports so I'll get > notified when it gets committed. > > Oh and the author says watch out for version 0.53 coming out in the next > couple of weeks :P > > cheers > > Chris No problem. Updating 0.52 -> 0.53 will be more easy than 0.29 -> 0.52 anyway :) -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 06:28:51 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A89C106566B for ; Sat, 3 Sep 2011 06:28:51 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo102.cox.net (eastrmfepo102.cox.net [68.230.241.214]) by mx1.freebsd.org (Postfix) with ESMTP id 4823B8FC17 for ; Sat, 3 Sep 2011 06:28:50 +0000 (UTC) Received: from eastrmimpo01.cox.net ([68.1.16.119]) by eastrmfepo102.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20110903062845.TTVR3919.eastrmfepo102.cox.net@eastrmimpo01.cox.net> for ; Sat, 3 Sep 2011 02:28:45 -0400 Received: from serene.no-ip.org ([98.164.87.41]) by eastrmimpo01.cox.net with bizsmtp id U6Uk1h00M0tX9KW026UlGL; Sat, 03 Sep 2011 02:28:45 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020207.4E61C91D.0031,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=5AHg1zS6fKBk64vkGL/stHpTKznySuNzRq0QOAs0BF0= c=1 sm=1 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=HSeXd6ud8jGmpzpM0y1GZQ==:17 a=kviXuzpPAAAA:8 a=3oOIfbMXSEbnSg9n3LUA:9 a=CjuIK1q_8ugA:10 a=4vB-4DCPJfMA:10 a=HSeXd6ud8jGmpzpM0y1GZQ==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from cox.net (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id p836SiK3082850 for ; Sat, 3 Sep 2011 01:28:44 -0500 (CDT) (envelope-from conrads@cox.net) Date: Sat, 3 Sep 2011 01:28:39 -0500 From: "Conrad J. Sabatier" To: freebsd-ports@FreeBSD.org Message-ID: <20110903012839.7f244a62@cox.net> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Compiling for gtk3 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 06:28:51 -0000 I've been trying to compile pan2 from the master git repository, and am having problems getting a build that will actually run using the --with-gtk3 configure switch. The compilation goes OK, but execution fails with... [conrads@serene ~/build/pan2]$ pan/gui/pan Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported aborting... Abort trap: 6 (core dumped) What's the key to getting an app to work with gtk3? Obviously, I'm missing something here. Thanks. -- Conrad J. Sabatier conrads@cox.net From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 07:11:18 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01219106564A; Sat, 3 Sep 2011 07:11:18 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (unknown [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id D45A58FC13; Sat, 3 Sep 2011 07:11:17 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p837BB6l061863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 3 Sep 2011 00:11:11 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p837BBqc061862; Sat, 3 Sep 2011 00:11:11 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA05981; Sat, 3 Sep 11 00:09:32 PDT Date: Sat, 03 Sep 2011 07:09:24 -0700 From: perryh@pluto.rain.com To: dougb@freebsd.org Message-Id: <4e623514.yL1tB2EYfva/oUIW%perryh@pluto.rain.com> References: <201109011333.p81DX2sN081775@fire.js.berklix.net> <4E61BB11.9070007@FreeBSD.org> In-Reply-To: <4E61BB11.9070007@FreeBSD.org> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, jhs@berklix.com, portsuser@larseighner.com, sem@freebsd.org Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 07:11:18 -0000 Doug Barton wrote: > On 09/02/2011 14:58, Lars Eighner wrote: > > The main thing here, of course, is that ports uses "dependency" > > in the exact opposite of its normal English sense (just as > > twitter uses "following" in the exact opposite of its normal > > English sense). > > > > In normal Engish 'X is a dependency of Y' means Y is necessary > > for X (X depends on Y) > > I'm not sure why you believe this to be true. Can you give > examples from non-technical English prose, and some dictionary > definitions to back up your claim? In normal English, I would not expect "dependency" to be used that way at all. Instead, I would expect something along the lines of "a state of dependency exists between X and Y". To specify the direction of the relationship, I would expect "X depends on Y" or, equivalently, "X is a dependent of Y" -- the latter being more often seen as "X is Y's dependent". Example: in connection with income taxes, "my son is my dependent". From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 07:16:35 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 1BEF6106566C; Sat, 3 Sep 2011 07:16:35 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 90AB4151835; Sat, 3 Sep 2011 07:16:33 +0000 (UTC) Message-ID: <4E61D450.5070203@FreeBSD.org> Date: Sat, 03 Sep 2011 00:16:32 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.1) Gecko/20110901 Thunderbird/6.0.1 MIME-Version: 1.0 To: perryh@pluto.rain.com References: <201109011333.p81DX2sN081775@fire.js.berklix.net> <4E61BB11.9070007@FreeBSD.org> <4e623514.yL1tB2EYfva/oUIW%perryh@pluto.rain.com> In-Reply-To: <4e623514.yL1tB2EYfva/oUIW%perryh@pluto.rain.com> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, jhs@berklix.com, portsuser@larseighner.com, sem@freebsd.org Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 07:16:35 -0000 On 09/03/2011 07:09, perryh@pluto.rain.com wrote: > In normal English, I would not expect .... hence my recommendation to go do some research. :) -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 07:57:05 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3731106566C; Sat, 3 Sep 2011 07:57:04 +0000 (UTC) (envelope-from lars@larseighner.com) Received: from mail.team1internet.com (mail.team1internet.com [216.110.13.10]) by mx1.freebsd.org (Postfix) with ESMTP id C0B938FC08; Sat, 3 Sep 2011 07:57:04 +0000 (UTC) Received: from larseighner.com (unknown [216.110.13.90]) by mail.team1internet.com (Postfix) with SMTP id 920D716B4B8; Sat, 3 Sep 2011 02:57:01 -0500 (CDT) Received: by larseighner.com (nbSMTP-1.00) for uid 1001 lars@larseighner.com; Sat, 3 Sep 2011 02:56:34 -0500 (CDT) Date: Sat, 3 Sep 2011 02:56:32 -0500 (CDT) From: Lars Eighner X-X-Sender: lars@noos.6dollardialup To: Doug Barton In-Reply-To: <4E61BB11.9070007@FreeBSD.org> Message-ID: References: <201109011333.p81DX2sN081775@fire.js.berklix.net> <4E61BB11.9070007@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: ports@freebsd.org, "Julian H. Stacey" , Sergey Matveychuk Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 07:57:05 -0000 On Fri, 2 Sep 2011, Doug Barton wrote: > On 09/02/2011 14:58, Lars Eighner wrote: >> The main thing here, of course, is that ports uses "dependency" in the >> exact opposite of its normal English sense (just as twitter uses >> "following" in the exact opposite of its normal English sense). >> >> In normal English 'X is a dependency of Y' means Y is necessary for X (X >> depends on Y) > > I'm not sure why you believe this to be true. Because it is a fact. > Can you give examples from non-technical English prose, and some > dictionary definitions to back up your claim? I am a little hurt that my own authority does not suffice for both the New York Times Book Review and the Time Literary Supplement (that's in London, y'all) have remarked on my mastery of the English language. But much more than that, I am appalled at the state of education in this country that you do not immediately recognize for yourself that my point is correct, once I have made it. There are two senses of 'dependency' in normal English. One means 'the state of dependence, (MWCD11th expresses this as being a synonym for DEPENDENCE; this is the oldest sense in English because MWCD11th lists senses in historical order), and the other is something that is dependent on something else. Well, okay, there are three senses, as there is a relatively recent one meaning a small building (such as a stable, garage, or bike shed) adjacent to a larger one. Almost all of the examples I turn up from grepping my corpus relate to international relations except for the most recent entries where it is bound to 'Chemical.' Well, 'chemical dependency' is perfectly common modern English and of course it does not mean the chemical depends on the user, but just the opposite. So in normal English, if I write myperlscript.pl, it is a dependency of perl. My script cannot run without perl, but perl can go on happily without my script. Perl does not depend on my script, so it is not the dependency. My script does depend on perl, so my script is the dependency. The correct word for what computer people call a dependency is 'requisite.' Perl is a requisite of my script. My script is a dependency of perl. Why is there such a thing as emacs cramp? Because the person who wrote it considered himself such a genius that he did not have to think of ergonomics and so bound just about everything to ^X and ^C and combinations thereof (and subsequent geniuses have made the possibly of remapping merely theoretical). Why are most editors and word processors just about unusable (out of the box) for writers? Because programmers are such geniuses, the idea of consulting working writers before they begin such a project seems laughable to them. And that is why ports uses 'dependency' exactly backwards -- the authors are such geniuses that they cannot be bothered to open a dictionary for themselves. I can think of a case in point. Now it is possible that once upon a time there was a programmer who knew what dependency meant, and he might have said something like "My script has a dependency on perl." That is accurate, but very awkward compared with "Perl is a requisite of my script." And perhaps that awkward expression was passed around among the programmerlings, as in the game gossip, until it became "Perl is a dependency of my script," which is dead wrong, so if my script is a port, and perl is missing, the report "stale dependency" is entirely misleading. My script is the dependency. It is not stale. It is missing its requisite, namely perl. It is a constant source of confusion for native speakers of English, and to a degree a source of amusement that documentation which has not yet been expressed in correct English is being translated into dozens of languages which take up space in machines that accept the default install. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 08:21:23 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A82F106566C for ; Sat, 3 Sep 2011 08:21:23 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 19D088FC13; Sat, 3 Sep 2011 08:21:23 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p838LMZn078775; Sat, 3 Sep 2011 08:21:22 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p838LMbo078739; Sat, 3 Sep 2011 08:21:22 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Sat, 3 Sep 2011 10:21:18 +0200 From: Baptiste Daroussin To: "Julian H. Stacey" Message-ID: <20110903082118.GA89220@azathoth.lan> References: <201109020107.p8217eFJ089679@fire.js.berklix.net> <201109020949.p829nmla093997@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw" Content-Disposition: inline In-Reply-To: <201109020949.p829nmla093997@fire.js.berklix.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-ports@FreeBSD.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 08:21:23 -0000 --wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 02, 2011 at 11:49:48AM +0200, Julian H. Stacey wrote: > Hi, > Reference: > > From: "Julian H. Stacey" =20 > > Date: Fri, 02 Sep 2011 03:07:40 +0200=20 > > Message-id: <201109020107.p8217eFJ089679@fire.js.berklix.net>=20 >=20 > I wrote: > > Microsoft must grin at all us BSD, Linux, maybe Solaris & presumably > > even now http://www.minix3.org free source enthusiasts reinventing > > similar old ports shims for same old 3rd party wheels:.=20 >=20 > FYI: > http://www.minix3.org -> > http://wiki.minix3.org/en/UsersGuide/InstallingBinaryPackages -> > http://pkgin.net/ > " > pkgin is known to work and have been tested under the following platforms= : > * NetBSD 4.0 > * NetBSD 5.{0,1} > * NetBSD current > * DragonFly BSD 2.0 to 2.8 > * DragonFly BSD current > * Solaris 10/SunOS 5.10 > * Opensolaris/SunOS 5.11 > * Debian GNU/Linux 5.0 > * Mac OS X 10.{5,6} > * MINIX 3.1.8 > " >=20 > No /pub/FreeBSD/branches/-current/ports/ports-mgmt/pkgin . > I'm not familiar with pkgin, but nice to see OS co-operation. >=20 > Cheers, > Julian pkgin is mostly driven by a single person, I really know well pkgin, becaus= e I ported it to FreeBSD in the past. There are patches from Minix and Dragonfly users, but through mostly things are done by the original author, and to he= lp portability but no much. I have picked up some ideas from pkgin for pkgng and the last version of pk= gin picked up some idea from pkgng. (Me and Emile Heitor - the author of pkgin - discuss and share ideas quite often about pkgin and pkgng) regards, Bapt --wac7ysb48OaltWcw Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk5h434ACgkQ8kTtMUmk6EzGywCeKhtRQxjwiQVR+IhEXIo/fcZT w/8AoJhDMRbWwimRsVRi2EPMpoxD9H09 =P/pw -----END PGP SIGNATURE----- --wac7ysb48OaltWcw-- From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 08:23:29 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A58C1065670 for ; Sat, 3 Sep 2011 08:23:29 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 425948FC13; Sat, 3 Sep 2011 08:23:29 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p838NTNd083335; Sat, 3 Sep 2011 08:23:29 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p838NSwH083330; Sat, 3 Sep 2011 08:23:28 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Sat, 3 Sep 2011 10:23:25 +0200 From: Baptiste Daroussin To: Kurt Jaeger Message-ID: <20110903082325.GB89220@azathoth.lan> References: <201109020107.p8217eFJ089679@fire.js.berklix.net> <201109020949.p829nmla093997@fire.js.berklix.net> <20110902100401.GO28186@home.opsec.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Fba/0zbH8Xs+Fj9o" Content-Disposition: inline In-Reply-To: <20110902100401.GO28186@home.opsec.eu> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-ports@FreeBSD.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 08:23:29 -0000 --Fba/0zbH8Xs+Fj9o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 02, 2011 at 12:04:01PM +0200, Kurt Jaeger wrote: > Hi! >=20 > > > http://pkgin.net/ > [...] > > > pkgin is known to work and have been tested under the following platf= orms > [...] > > So, what do you actually mean by this? >=20 > Probably just this: What about trying to port pkgin for FreeBSD, so that > pkgin can also be used on FreeBSD ? >=20 > If this solves the binary pkg-install problem in a generic > way on many plattforms (I have not looked at the implementation), > that might be a nice feature. >=20 As I said I have done this, but finally went to pkgng because of some probl= em (version scheme between pkgsrc and freebsd differs) and other things. regards, Bapt --Fba/0zbH8Xs+Fj9o Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk5h4/0ACgkQ8kTtMUmk6EwYdgCeNoBsEMA05D66BhIfKO2Yk15m XqcAn1AEQ/rcF13tQHarM4+VT2hsZqyq =maQ9 -----END PGP SIGNATURE----- --Fba/0zbH8Xs+Fj9o-- From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 08:23:41 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06C161065701 for ; Sat, 3 Sep 2011 08:23:41 +0000 (UTC) (envelope-from jankyj@unfs.us) Received: from morbid.purplehat.org (morbid.purplehat.org [206.225.83.29]) by mx1.freebsd.org (Postfix) with ESMTP id DADC18FC0C for ; Sat, 3 Sep 2011 08:23:39 +0000 (UTC) Received: from localhost (morbid.purplehat.org [206.225.83.29]) by morbid.purplehat.org (Postfix) with ESMTP id 2FA2F85B0B3 for ; Sat, 3 Sep 2011 01:07:10 -0700 (PDT) Received: from morbid.purplehat.org ([206.225.83.29]) by localhost (morbid.purplehat.org [206.225.83.29]) (maiad, port 10024) with ESMTP id 21645-06 for ; Sat, 3 Sep 2011 01:07:09 -0700 (PDT) Received: from [192.168.1.3] (mx2.purplehat.org [174.51.182.248]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ek@purplehat.org) by morbid.purplehat.org (Postfix) with ESMTPSA id 90ED785B0AF for ; Sat, 3 Sep 2011 01:07:09 -0700 (PDT) Message-ID: <4E61E03A.7080502@unfs.us> Date: Sat, 03 Sep 2011 02:07:22 -0600 From: Janketh Jay User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.21) Gecko/20110831 Lightning/1.0b2 Thunderbird/3.1.13 MIME-Version: 1.0 To: ports@freebsd.org References: <201109011333.p81DX2sN081775@fire.js.berklix.net> <4E61BB11.9070007@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 08:23:41 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/03/2011 01:56 AM, Lars Eighner wrote: > On Fri, 2 Sep 2011, Doug Barton wrote: > >> On 09/02/2011 14:58, Lars Eighner wrote: > >>> The main thing here, of course, is that ports uses "dependency" in >>> the >>> exact opposite of its normal English sense (just as twitter uses >>> "following" in the exact opposite of its normal English sense). >>> >>> In normal English 'X is a dependency of Y' means Y is necessary >>> for X (X >>> depends on Y) >> >> I'm not sure why you believe this to be true. > > Because it is a fact. > >> Can you give examples from non-technical English prose, and some >> dictionary definitions to back up your claim? > > I am a little hurt that my own authority does not suffice for both > the New > York Times Book Review and the Time Literary Supplement (that's in > London, > y'all) have remarked on my mastery of the English language. But > much more > than that, I am appalled at the state of education in this country > that you > do not immediately recognize for yourself that my point is correct, > once I > have made it. > > There are two senses of 'dependency' in normal English. One means > 'the state > of dependence, (MWCD11th expresses this as being a synonym for > DEPENDENCE; > this is the oldest sense in English because MWCD11th lists senses in > historical order), and the other is something that is dependent on > something > else. Well, okay, there are three senses, as there is a relatively > recent > one meaning a small building (such as a stable, garage, or bike shed) > adjacent to a larger one. > > Almost all of the examples I turn up from grepping my corpus relate to > international relations except for the most recent entries where it > is bound > to 'Chemical.' Well, 'chemical dependency' is perfectly common modern > English and of course it does not mean the chemical depends on the > user, but > just the opposite. > > So in normal English, if I write myperlscript.pl, it is a dependency of > perl. My script cannot run without perl, but perl can go on happily > without > my script. Perl does not depend on my script, so it is not the > dependency. My script does depend on perl, so my script is the > dependency. > > The correct word for what computer people call a dependency is > 'requisite.' > Perl is a requisite of my script. My script is a dependency of perl. > > Why is there such a thing as emacs cramp? Because the person who > wrote it > considered himself such a genius that he did not have to think of > ergonomics > and so bound just about everything to ^X and ^C and combinations > thereof > (and subsequent geniuses have made the possibly of remapping merely > theoretical). Why are most editors and word processors just about > unusable > (out of the box) for writers? Because programmers are such > geniuses, the > idea of consulting working writers before they begin such a project > seems > laughable to them. > > And that is why ports uses 'dependency' exactly backwards -- the > authors are > such geniuses that they cannot be bothered to open a dictionary for > themselves. I can think of a case in point. > > Now it is possible that once upon a time there was a programmer who > knew > what dependency meant, and he might have said something like "My > script has > a dependency on perl." That is accurate, but very awkward compared > with > "Perl is a requisite of my script." And perhaps that awkward > expression was > passed around among the programmerlings, as in the game gossip, > until it > became "Perl is a dependency of my script," which is dead wrong, so if > my script is a port, and perl is missing, the report "stale > dependency" is > entirely misleading. My script is the dependency. It is not > stale. It is > missing its requisite, namely perl. > > It is a constant source of confusion for native speakers of English, > and to > a degree a source of amusement that documentation which has not yet > been > expressed in correct English is being translated into dozens of > languages > which take up space in machines that accept the default install. > One of the best most unnecessary replies to something unneeded I've read in a long, LONG time. Well done, sir! (It's a keeper!) - -Janky Jay, III -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5h4DoACgkQGK3MsUbJZn6q3QCePhBtBbUfd90ORira5YuZ+OYu F5oAnjzHraki17HKOccoOB4rUCly+g5D =CNIG -----END PGP SIGNATURE----- From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 08:25:16 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 452E7106566C for ; Sat, 3 Sep 2011 08:25:16 +0000 (UTC) (envelope-from kwm@rainbow-runner.nl) Received: from fep16.mx.upcmail.net (fep16.mx.upcmail.net [62.179.121.36]) by mx1.freebsd.org (Postfix) with ESMTP id 8C2B08FC08 for ; Sat, 3 Sep 2011 08:25:15 +0000 (UTC) Received: from edge02.upcmail.net ([192.168.13.237]) by viefep16-int.chello.at (InterMail vM.8.01.02.02 201-2260-120-106-20100312) with ESMTP id <20110903082513.SRHG1962.viefep16-int.chello.at@edge02.upcmail.net>; Sat, 3 Sep 2011 10:25:13 +0200 Received: from [127.0.0.1] ([178.84.137.57]) by edge02.upcmail.net with edge id U8RA1h03P1EUzH6028RBkM; Sat, 03 Sep 2011 10:25:13 +0200 X-SourceIP: 178.84.137.57 Message-ID: <4E61E462.6020909@rainbow-runner.nl> Date: Sat, 03 Sep 2011 10:25:06 +0200 From: Koop Mast User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.1) Gecko/20110830 Thunderbird/6.0.1 MIME-Version: 1.0 To: "Conrad J. Sabatier" References: <20110903012839.7f244a62@cox.net> In-Reply-To: <20110903012839.7f244a62@cox.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 110902-1, 02-09-2011), Outbound message X-Antivirus-Status: Clean X-Cloudmark-Analysis: v=1.1 cv=jqrf5qXv5urL2URZ3a9OklEvUdrM81ZtB3GWlHLPCVk= c=1 sm=0 a=lu-5kE5W7YQA:10 a=8nJEP1OIZ-IA:10 a=dfQV7xJKINCG7Ncl1VwA:9 a=oFhV3GyFwiJ2PDMubGgA:7 a=wPNLvfGTeEIA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Cc: freebsd-ports@FreeBSD.org Subject: Re: Compiling for gtk3 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 08:25:16 -0000 On 3-9-2011 8:28, Conrad J. Sabatier wrote: > I've been trying to compile pan2 from the master git repository, and am > having problems getting a build that will actually run using the > --with-gtk3 configure switch. > > The compilation goes OK, but execution fails with... > > [conrads@serene ~/build/pan2]$ pan/gui/pan > > Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in > the same process is not supported aborting... > Abort trap: 6 (core dumped) You will need to disable gtkspell. You can't mix GTK+ 2 and GTK+ 3 widgets in the same application. Since gtkspell is a GTK+ 2 library and pan is a GTK+ 3 apps. -Koop > What's the key to getting an app to work with gtk3? Obviously, I'm > missing something here. > > Thanks. > From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 09:26:09 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 0DE8B106566C for ; Sat, 3 Sep 2011 09:26:09 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 1DB4923CF4F for ; Sat, 3 Sep 2011 11:26:08 +0200 (CEST) Message-ID: <4E61F2AF.8000608@FreeBSD.org> Date: Sat, 03 Sep 2011 11:26:07 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Mnenhy/0.8.3 Thunderbird/3.1.13 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <201109011333.p81DX2sN081775@fire.js.berklix.net> <4E61BB11.9070007@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 09:26:09 -0000 Am 03.09.2011 09:56, schrieb Lars Eighner: > The correct word for what computer people call a dependency is 'requisite.' > Perl is a requisite of my script. My script is a dependency of perl. > ... > Because programmers are such geniuses, the > idea of consulting working writers before they begin such a project seems > laughable to them. > > And that is why ports uses 'dependency' exactly backwards -- the authors > are > such geniuses that they cannot be bothered to open a dictionary for > themselves. I can think of a case in point. > > Now it is possible that once upon a time there was a programmer who knew > what dependency meant, and he might have said something like "My script has > a dependency on perl." That is accurate, but very awkward compared with > "Perl is a requisite of my script." And perhaps that awkward expression was Being a non-native speaker, I am nonetheless aware of the difference between the rather noun-oriented style of my own native tongue, German, and the rather verb-oriented style of English. So, that latter quoted phrase of yours could be rewritten as "My script requires Perl", and one step further, "My script needs Perl" (not sure if you want to go that last step). It's clear, there is no passive voice, the sentence starts with the familiar, namely the script at the user's hand, does not need a cumbersome of-possessive construct. > It is a constant source of confusion for native speakers of English, and to > a degree a source of amusement that documentation which has not yet been > expressed in correct English is being translated into dozens of languages > which take up space in machines that accept the default install. It is not only a source of confusion for native speakers, but also to non-native speakers. I'd support a motion to replace "dependency" by "requisite" in port and package management tools to remove the ambiguity. From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 09:33:52 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33595106564A; Sat, 3 Sep 2011 09:33:52 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 90B538FC08; Sat, 3 Sep 2011 09:33:51 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBEA6B.dip.t-dialin.net [217.251.234.107]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p839Xm2h020314; Sat, 3 Sep 2011 09:33: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 p839XgMC067942; Sat, 3 Sep 2011 11:33:42 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id p839XbAu015390; Sat, 3 Sep 2011 09:33:43 GMT (envelope-from jhs@fire.js.berklix.net) Message-Id: <201109030933.p839XbAu015390@fire.js.berklix.net> To: Baptiste Daroussin From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Sat, 03 Sep 2011 10:21:18 +0200." <20110903082118.GA89220@azathoth.lan> Date: Sat, 03 Sep 2011 11:33:37 +0200 Sender: jhs@berklix.com Cc: freebsd-ports@freebsd.org Subject: Re: Ports system quality X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 09:33:52 -0000 Baptiste Daroussin wrote: > On Fri, Sep 02, 2011 at 11:49:48AM +0200, Julian H. Stacey wrote: > > Hi, > > Reference: > > > From: "Julian H. Stacey" =20 > > > Date: Fri, 02 Sep 2011 03:07:40 +0200=20 > > > Message-id: <201109020107.p8217eFJ089679@fire.js.berklix.net>=20 > >=20 > > I wrote: > > > Microsoft must grin at all us BSD, Linux, maybe Solaris & presumably > > > even now http://www.minix3.org free source enthusiasts reinventing > > > similar old ports shims for same old 3rd party wheels:.=20 > >=20 > > FYI: > > http://www.minix3.org -> > > http://wiki.minix3.org/en/UsersGuide/InstallingBinaryPackages -> > > http://pkgin.net/ > > " > > pkgin is known to work and have been tested under the following platforms= > : > > * NetBSD 4.0 > > * NetBSD 5.{0,1} > > * NetBSD current > > * DragonFly BSD 2.0 to 2.8 > > * DragonFly BSD current > > * Solaris 10/SunOS 5.10 > > * Opensolaris/SunOS 5.11 > > * Debian GNU/Linux 5.0 > > * Mac OS X 10.{5,6} > > * MINIX 3.1.8 > > " > >=20 > > No /pub/FreeBSD/branches/-current/ports/ports-mgmt/pkgin . > > I'm not familiar with pkgin, but nice to see OS co-operation. > >=20 > > Cheers, > > Julian > > pkgin is mostly driven by a single person, I really know well pkgin, becaus= > e I > ported it to FreeBSD in the past. There are patches from Minix and Dragonfly > users, but through mostly things are done by the original author, and to he= > lp > portability but no much. > I have picked up some ideas from pkgin for pkgng and the last version of pk= > gin > picked up some idea from pkgng. (Me and Emile Heitor - the author of pkgin - > discuss and share ideas quite often about pkgin and pkgng) > > regards, > Bapt OK :-) Suggestion: If He make some note about FreeBSD/pkgng on his page would help, you could both cross link a See Also type href. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct. From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 09:59:15 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C173E1065673 for ; Sat, 3 Sep 2011 09:59:15 +0000 (UTC) (envelope-from tingox@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 797A28FC14 for ; Sat, 3 Sep 2011 09:59:15 +0000 (UTC) Received: by vws18 with SMTP id 18so3756579vws.13 for ; Sat, 03 Sep 2011 02:59:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=G39smiMqb4us6wgFZy+ccX5TMLAJfS1R7afCxvdbFTM=; b=mFYeM8epumbwvYzLrD3HxX442FOtT2U5miPApMbzRNEiDMUy5lzWliHV+E47Z4DiEi 7hhckB9vRylZiBHydJw0YrSRGpmqkAWf18WmAX/NCojZffZIojGrl0Pl1urQrQY5OfaE zJsHzlwOJlXgnioy6w1aAQgHeWCqqWyFovhho= MIME-Version: 1.0 Received: by 10.52.28.80 with SMTP id z16mr1857590vdg.75.1315043954658; Sat, 03 Sep 2011 02:59:14 -0700 (PDT) Received: by 10.52.186.106 with HTTP; Sat, 3 Sep 2011 02:59:14 -0700 (PDT) In-Reply-To: References: <201109011333.p81DX2sN081775@fire.js.berklix.net> <4E61BB11.9070007@FreeBSD.org> Date: Sat, 3 Sep 2011 11:59:14 +0200 Message-ID: From: Torfinn Ingolfsen To: FreeBSD Ports ML Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 09:59:15 -0000 Hello, On Sat, Sep 3, 2011 at 9:56 AM, Lars Eighner wr= ote: > I am a little hurt that my own authority does not suffice for both the Ne= w > York Times Book Review and the Time Literary Supplement (that's in London= , > y'all) have remarked on my mastery of the English language. =A0But much m= ore > than that, I am appalled at the state of education in this country that y= ou > do not immediately recognize for yourself that my point is correct, once = I > have made it. Congratulations on being recommended (applauded? I'm sorry, but I am a non-native user of the English language). > The correct word for what computer people call a dependency is 'requisite= .' > Perl is a requisite of my script. =A0My script is a dependency of perl. If somebody decides to "fix" the language of these tools (or any tools for that matter), they should keep in mind that many users are non-native speakers of the English language. Correct English is good, but but plain, simple and common English is better= . No uncommon words please. --=20 Regards, Torfinn Ingolfsen From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 10:17:17 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3DA6106564A for ; Sat, 3 Sep 2011 10:17:17 +0000 (UTC) (envelope-from cwhiteh@onetel.com) Received: from woodbine.london.02.net (woodbine.london.02.net [87.194.255.145]) by mx1.freebsd.org (Postfix) with ESMTP id 8ED238FC15 for ; Sat, 3 Sep 2011 10:17:17 +0000 (UTC) Received: from muji2.config (93.97.24.219) by woodbine.london.02.net (8.5.140) id 4E261CD1016AEBB5 for ports@FreeBSD.org; Sat, 3 Sep 2011 11:17:16 +0100 Message-ID: <4E61FEAC.9020107@onetel.com> Date: Sat, 03 Sep 2011 11:17:16 +0100 From: Chris Whitehouse User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.9) Gecko/20100924 Thunderbird/3.1.4 MIME-Version: 1.0 To: ports@FreeBSD.org References: <4e5dc69f.y98a8wi3n/UYU+Z/%perryh@pluto.rain.com> <4E5E3364.7050308@yandex.ru> <4E5E7EAA.4030303@onetel.com> <4E5E84B4.6040200@yandex.ru> <4E5EB5ED.9080506@onetel.com> <4E60916A.2020002@yandex.ru> <4E614D62.9050109@onetel.com> <4E6167EF.1010601@gmail.com> In-Reply-To: <4E6167EF.1010601@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: editors/zim X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 10:17:18 -0000 oops not sent to list... On 03/09/2011 00:34, Glen Barber wrote: > Hi Chris, > > On 9/2/11 5:40 PM, Chris Whitehouse wrote: >> did you see that I had to add a line for MD5 to distinfo to make it work >> on my 8.1-R system? Though the last change was to remove MD5... >> > > It sounds to me parts of your ports tree may be out of sync. MD5 > distfile validation was removed from ports some time ago. You're right in a sense. It's ports from late 2010 with the new port of zim which I've added manually. I didn't realise MD5 had been removed. Chris > > How do you update your ports tree? > > Regards, > > Glen > From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 10:39:39 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01AAF1065673 for ; Sat, 3 Sep 2011 10:39:39 +0000 (UTC) (envelope-from lars@larseighner.com) Received: from mail.team1internet.com (mail.team1internet.com [216.110.13.10]) by mx1.freebsd.org (Postfix) with ESMTP id D23E88FC17 for ; Sat, 3 Sep 2011 10:39:36 +0000 (UTC) Received: from larseighner.com (unknown [216.110.13.99]) by mail.team1internet.com (Postfix) with SMTP id 0F0A216B4CB; Sat, 3 Sep 2011 05:39:35 -0500 (CDT) Received: by larseighner.com (nbSMTP-1.00) for uid 1001 lars@larseighner.com; Sat, 3 Sep 2011 05:39:07 -0500 (CDT) Date: Sat, 3 Sep 2011 05:39:06 -0500 (CDT) From: Lars Eighner X-X-Sender: lars@noos.6dollardialup To: Torfinn Ingolfsen In-Reply-To: Message-ID: References: <201109011333.p81DX2sN081775@fire.js.berklix.net> <4E61BB11.9070007@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="21774345-1110645530-1315046307=:41273" Cc: FreeBSD Ports ML Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 10:39:39 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --21774345-1110645530-1315046307=:41273 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Sat, 3 Sep 2011, Torfinn Ingolfsen wrote: >> The correct word for what computer people call a dependency is 'requisit= e.' >> Perl is a requisite of my script. =A0My script is a dependency of perl. > > If somebody decides to "fix" the language of these tools (or any tools > for that matter), they should keep in mind that many users are > non-native speakers of the English language. > Correct English is good, but but plain, simple and common English is bett= er. > No uncommon words please. Curiously enough, the man page for portupgrade begins by defining "required= " and "dependent" accurately. These are adjectives, but a step in the right direction. "Requirement" might do better than "requisite." Unfortunately, the messages emitted by parts of the portupgrade package do not achieve a similar level of clarity. For example, in certain circumstances, portuprade says "Gathering depends." "Depends" is a verb (and now a proprietary name for adult diapers) -- it does not have a sense as a common noun. I understand why such abbreviated messages may be useful in programming and debugging. But it does not belong in the production copy. Either it shoul= d be meaningful to the user or it should be eliminated. --=20 Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 --21774345-1110645530-1315046307=:41273-- From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 11:38:47 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91638106566B for ; Sat, 3 Sep 2011 11:38:47 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 20CFC8FC08 for ; Sat, 3 Sep 2011 11:38:46 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBEA6B.dip.t-dialin.net [217.251.234.107]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p83BcjFf021110; Sat, 3 Sep 2011 11:38:45 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 p83BcebG068387; Sat, 3 Sep 2011 13:38:40 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id p83BcY9g016430; Sat, 3 Sep 2011 11:38:40 GMT (envelope-from jhs@fire.js.berklix.net) Message-Id: <201109031138.p83BcY9g016430@fire.js.berklix.net> To: mm@FreeBSD.org, ports@FreeBSD.org From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Linux Unix Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com/~jhs/cv/ Date: Sat, 03 Sep 2011 13:38:34 +0200 Sender: jhs@berklix.com Cc: Subject: x11-toolkits/tk84 install can't stat: /usr/local/man/man3/3DBorder.3 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 11:38:47 -0000 Hi I see this error (on current too) cd /usr/ports/x11-toolkits/tk84 printenv PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/bin TERM=xterm PWD=/usr/ports uname -a FreeBSD blak.js.berklix.net 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu May 19 13:49:29 CEST 2011 jhs@blak.js.berklix.net:/ad6s4/release/8.2-RELEASE/src/sys/amd64/compile/BLAK.small amd64 Variants of: make clean ; .... make install .... make clean ; .... make WITH_TK84_DOC=YES FORCE_PKG_REGISTER=YES reinstall always bomb with: ..... install -o root -g wheel -m 444 /ad6s4/release/8.2-RELEASE/ports/x11-toolkits/tk84/work/tk8.4.19/unix/../doc/wish.1 /usr/local/man/man1/wish8.4.1 ===> Compressing manual pages for tk-8.4.19_2,2 gzip: can't stat: /usr/local/man/man3/3DBorder.3: No such file or directory gzip: can't stat: /usr/local/man/man3/AddOption.3: No such file or directory gzip: can't stat: /usr/local/man/man3/BindTable.3: No such file or directory ... ober 100 lines deleted. gzip: can't stat: /usr/local/man/mann/wm.n: No such file or directory ===> Running ldconfig /sbin/ldconfig -m /usr/local/lib ===> Registering installation for tk-8.4.19_2,2 Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct. From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 14:21:41 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B009106564A for ; Sat, 3 Sep 2011 14:21:41 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id DCC928FC0C for ; Sat, 3 Sep 2011 14:21:40 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBEA6B.dip.t-dialin.net [217.251.234.107]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p83ELcpf022298; Sat, 3 Sep 2011 14:21:39 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 p83ELXiB068992; Sat, 3 Sep 2011 16:21:34 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id p83ELLXf018613; Sat, 3 Sep 2011 14:21:27 GMT (envelope-from jhs@fire.js.berklix.net) Message-Id: <201109031421.p83ELLXf018613@fire.js.berklix.net> To: Torfinn Ingolfsen From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Sat, 03 Sep 2011 11:59:14 +0200." Date: Sat, 03 Sep 2011 16:21:21 +0200 Sender: jhs@berklix.com Cc: FreeBSD Ports ML Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 14:21:41 -0000 Torfinn Ingolfsen wrote: > ... but I am a > non-native user of the English language). ... > Correct English is good, but but plain, simple and common English is better. Yes :-) (I'm native English, but in Germany). I also believe shorter sentences work better (in either language). Easy to forget though, as local societies condition us to use more complex grammar for written than verbal communication. Those with the most complex articulation mostly win top professional status / income. > No uncommon words please. Yes, except eg "NEED =" as a Makefile key word would be too short, with false matches with find & grep, "RUN_DEPENDS" & "BUILD_DEPENDS" OK. "REQUISITE" some natives would mis-spell. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct. From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 15:32:50 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 837CB106566B; Sat, 3 Sep 2011 15:32:50 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward15.mail.yandex.net (forward15.mail.yandex.net [IPv6:2a02:6b8:0:801::5]) by mx1.freebsd.org (Postfix) with ESMTP id 0520D8FC08; Sat, 3 Sep 2011 15:32:50 +0000 (UTC) Received: from smtp14.mail.yandex.net (smtp14.mail.yandex.net [95.108.131.192]) by forward15.mail.yandex.net (Yandex) with ESMTP id 44CCB9E2882; Sat, 3 Sep 2011 19:32:48 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1315063968; bh=mQbh2XIDV4hby+nPI308DtrfHUEYAI3Dfj30mWT2MjU=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=JHEt3ugHvbwt+15gptEuisJ/0SQmpgdM7cZONYXA9ZI0ohZvxSgHQ6It/ZQivjDkd NMobipUb1jfEdKqt3ja+I7WUuTuq93SQRawbrufliU5peV/OpTZIz4JTFVGxwbHFin uSbtwivIzP4WSvpsA465yN6rnlC4BR2mxgRAPHmA= Received: from smtp14.mail.yandex.net (localhost [127.0.0.1]) by smtp14.mail.yandex.net (Yandex) with ESMTP id 258AA1B604A2; Sat, 3 Sep 2011 19:32:48 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp14.mail.yandex.net (nwsmtp/Yandex) with ESMTP id WlUaGllX; Sat, 3 Sep 2011 19:32:47 +0400 X-Yandex-Spam: 1 Message-ID: <4E62489A.2050409@yandex.ru> Date: Sat, 03 Sep 2011 19:32:42 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: "Julian H. Stacey" References: <201109031138.p83BcY9g016430@fire.js.berklix.net> In-Reply-To: <201109031138.p83BcY9g016430@fire.js.berklix.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, mm@FreeBSD.org Subject: Re: x11-toolkits/tk84 install can't stat: /usr/local/man/man3/3DBorder.3 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 15:32:50 -0000 Julian H. Stacey wrote on 03.09.2011 15:38: > Hi > I see this error (on current too) > cd /usr/ports/x11-toolkits/tk84 > printenv > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/bin > TERM=xterm > PWD=/usr/ports > uname -a > FreeBSD blak.js.berklix.net 8.2-RELEASE FreeBSD 8.2-RELEASE > #0: Thu May 19 13:49:29 CEST 2011 > jhs@blak.js.berklix.net:/ad6s4/release/8.2-RELEASE/src/sys/amd64/compile/BLAK.small > amd64 > Variants of: > make clean ; .... make install .... > make clean ; .... make WITH_TK84_DOC=YES FORCE_PKG_REGISTER=YES reinstall > always bomb with: > > ..... > install -o root -g wheel -m 444 /ad6s4/release/8.2-RELEASE/ports/x11-toolkits/tk84/work/tk8.4.19/unix/../doc/wish.1 /usr/local/man/man1/wish8.4.1 > ===> Compressing manual pages for tk-8.4.19_2,2 > gzip: can't stat: /usr/local/man/man3/3DBorder.3: No such file or directory > gzip: can't stat: /usr/local/man/man3/AddOption.3: No such file or directory > gzip: can't stat: /usr/local/man/man3/BindTable.3: No such file or directory > ... ober 100 lines deleted. > > gzip: can't stat: /usr/local/man/mann/wm.n: No such file or directory > ===> Running ldconfig > /sbin/ldconfig -m /usr/local/lib > ===> Registering installation for tk-8.4.19_2,2 > > Cheers, > Julian I can reproduce this behavior with TK84_DOC is on (default off). The problem is that this port doesn't actually install man-pages from ${MAN3} and ${MANN}, so this option is bogus. -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 16:51:53 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F151106564A for ; Sat, 3 Sep 2011 16:51:53 +0000 (UTC) (envelope-from jos@catnook.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 17FCA8FC15 for ; Sat, 3 Sep 2011 16:51:52 +0000 (UTC) Received: by vws18 with SMTP id 18so3944787vws.13 for ; Sat, 03 Sep 2011 09:51:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.92.2 with SMTP id ci2mr2177361vdb.428.1315068711962; Sat, 03 Sep 2011 09:51:51 -0700 (PDT) Received: by 10.52.111.104 with HTTP; Sat, 3 Sep 2011 09:51:51 -0700 (PDT) In-Reply-To: References: <201109011333.p81DX2sN081775@fire.js.berklix.net> <4E61BB11.9070007@FreeBSD.org> Date: Sat, 3 Sep 2011 09:51:51 -0700 Message-ID: From: Jos Backus To: Lars Eighner Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Torfinn Ingolfsen , FreeBSD Ports ML Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 16:51:53 -0000 On Sat, Sep 3, 2011 at 3:39 AM, Lars Eighner wrote: > On Sat, 3 Sep 2011, Torfinn Ingolfsen wrote: > > The correct word for what computer people call a dependency is >>> 'requisite.' >>> Perl is a requisite of my script. My script is a dependency of perl. >>> >> >> If somebody decides to "fix" the language of these tools (or any tools >> for that matter), they should keep in mind that many users are >> non-native speakers of the English language. >> Correct English is good, but but plain, simple and common English is >> better. >> No uncommon words please. >> > > Curiously enough, the man page for portupgrade begins by defining > "required" > and "dependent" accurately. These are adjectives, but a step in the right > direction. "Requirement" might do better than "requisite." > I suggested that verbiage, and I'm Dutch. http://cvsup.hu.freebsd.org/viewvc/FreeBSD/ports/ports-mgmt/portupgrade/distinfo?sortby=log&view=log > -- Jos Backus jos at catnook.com From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 17:42:12 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2572C106566C for ; Sat, 3 Sep 2011 17:42:12 +0000 (UTC) (envelope-from code@apotheon.net) Received: from oproxy5-pub.bluehost.com (oproxy5.bluehost.com [IPv6:2605:dc00:100:2::a5]) by mx1.freebsd.org (Postfix) with SMTP id D88488FC17 for ; Sat, 3 Sep 2011 17:42:11 +0000 (UTC) Received: (qmail 14323 invoked by uid 0); 3 Sep 2011 17:42:11 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by cpoproxy2.bluehost.com with SMTP; 3 Sep 2011 17:42:11 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.net; s=default; h=In-Reply-To:Content-Type:Mime-Version:References:Message-ID:Subject:To:From:Date; bh=Sj7B3ujyvrxVilp8Oo1naa5JCcaniz/Qh+EkVeiUm7w=; b=YmrZdOhyvPKs60BKCCoBAFngePqXUP0ve/8bOZdkVrVLEdy3TkbPieTad7tHhyX6TQUZIlN+amLrAZKeh0anWas15T2v+oE0FrV6Efs/Pn45HC9N4uUAe8BSVJ/LEeA4; Received: from c-24-8-180-234.hsd1.co.comcast.net ([24.8.180.234] helo=kukaburra.hydra) by box543.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1QzuEM-00034Z-Ac for freebsd-ports@freebsd.org; Sat, 03 Sep 2011 11:42:11 -0600 Received: by kukaburra.hydra (sSMTP sendmail emulation); Sat, 03 Sep 2011 11:23:33 -0600 Date: Sat, 3 Sep 2011 11:23:33 -0600 From: Chad Perrin To: freebsd-ports@freebsd.org Message-ID: <20110903172333.GA89227@guilt.hydra> Mail-Followup-To: freebsd-ports@freebsd.org References: <201109011333.p81DX2sN081775@fire.js.berklix.net> <4E61BB11.9070007@FreeBSD.org> <4E61F2AF.8000608@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw" Content-Disposition: inline In-Reply-To: <4E61F2AF.8000608@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.org} {sentby:smtp auth 24.8.180.234 authed with ren@apotheon.org} Subject: Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 17:42:12 -0000 --wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 03, 2011 at 11:26:07AM +0200, Matthias Andree wrote: >=20 > I'd support a motion to replace "dependency" by "requisite" in port and > package management tools to remove the ambiguity. I think that's a terrible idea. If we are going to change the terms used for such things, we should angle more toward an E-Prime approach to phrasing in such cases. Don't misunderstand -- I think that trying to write or speak in E-Prime all the time is an even worse idea. There are contexts where it's a great idea, though, and this is one of them. Using terms like "dependency" and "requisite" in this context tends toward tortuous sentence construction and other Byzantine absurdities. If we're going to change the phrasing, go with this like "Foo depends on bar," and "Bar requires foo." Aruing over whether it should be "Foo is a dependency of bar," or "Foo is a requisite of bar," utterly misses the most important point here: both of them suck. By the way, "dependency" in simplest terms just means that the thing in question is dependent or subordinate upon something else. That, to me, means that "stale dependency" says the dependency information for the dependent port is stale. That doesn't sound wrong at all. --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --wac7ysb48OaltWcw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk5iYpUACgkQ9mn/Pj01uKWDBgCgwPmr07rLx+legTiJudZf/4ZP sAcAoJ7dWlw2hVm5em3gvmVBZqHPyxXk =c0Ld -----END PGP SIGNATURE----- --wac7ysb48OaltWcw-- From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 18:21:36 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55D59106564A for ; Sat, 3 Sep 2011 18:21:36 +0000 (UTC) (envelope-from rosti.bsd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id E3FF68FC12 for ; Sat, 3 Sep 2011 18:21:35 +0000 (UTC) Received: by wwi36 with SMTP id 36so3958726wwi.31 for ; Sat, 03 Sep 2011 11:21:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=0UzLPXMFiugRWK39KdOkM1cW4GjsNqcET45iD3tOQHY=; b=ifvi/iBe42687GMbCl3HwzWS8C+Ivg2Gywp6G3dqjI1p8ifnhGfbZPR20/NEuuBNDL a1edwYI2dJwQYaDB2k47dWeMGqemeFlnU8k5nnzfWQTUUdBJ3jQlFgqOf28iqXUvhy1p 2fa9wbIgvnBNBR0wGRP1nKFK8SPPWVQTwfUkU= MIME-Version: 1.0 Received: by 10.216.220.168 with SMTP id o40mr2139096wep.75.1315072390664; Sat, 03 Sep 2011 10:53:10 -0700 (PDT) Received: by 10.216.36.207 with HTTP; Sat, 3 Sep 2011 10:53:10 -0700 (PDT) Date: Sat, 3 Sep 2011 20:53:10 +0300 Message-ID: From: Rostislav Krasny To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: portsnap: one metadata file is corrupted X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 18:21:36 -0000 Hi there, Could anyone explain why this may happen and what should I do? My system is 7.4-STABLE, built from today's sources. Thank you. mercury# portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found. Fetching snapshot tag from portsnap5.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Wed Oct 13 17:09:57 IST 2010 to Sat Sep 3 20:15:14 IDT 2011. Fetching 4 metadata patches... done. Applying metadata patches... done. Fetching 4 metadata files... gunzip: (stdin): unexpected end of file metadata is corrupt. mercury# portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found. Fetching snapshot tag from portsnap6.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Wed Oct 13 17:09:57 IST 2010 to Sat Sep 3 20:25:27 IDT 2011. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... gunzip: (stdin): unexpected end of file metadata is corrupt. mercury# From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 19:41:07 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 885BD106564A; Sat, 3 Sep 2011 19:41:07 +0000 (UTC) (envelope-from ehaupt@FreeBSD.org) Received: from mx.critical.ch (cl-8.zrh-02.ch.sixxs.net [IPv6:2001:1620:f00:7::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0C6B58FC08; Sat, 3 Sep 2011 19:41:06 +0000 (UTC) Received: from beaver.home.critical.ch (beaver.critical.ch [IPv6:2001:1620:f06:0:21e:8cff:fe7d:e7ea] (may be forged)) (authenticated bits=0) by mx.critical.ch (8.14.4/8.14.4/critical-1.0) with ESMTP id p83Jf5nM013693; Sat, 3 Sep 2011 21:41:05 +0200 (CEST) (envelope-from ehaupt@FreeBSD.org) Date: Sat, 3 Sep 2011 21:41:00 +0200 From: Emanuel Haupt To: ports@FreeBSD.org Message-Id: <20110903214100.096d8366.ehaupt@FreeBSD.org> X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: cperciva@FreeBSD.org Subject: INDEX-9 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 19:41:07 -0000 In light of the upcoming release of 9.0-RELEASE it might be a good idea to start providing INDEX-9 via portsnap. Especially since we want people to try the BETA releases. Thoughts? Emanuel From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 20:56:48 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32283106564A; Sat, 3 Sep 2011 20:56:48 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward13.mail.yandex.net (forward13.mail.yandex.net [IPv6:2a02:6b8:0:801::3]) by mx1.freebsd.org (Postfix) with ESMTP id A6AF68FC12; Sat, 3 Sep 2011 20:56:47 +0000 (UTC) Received: from smtp12.mail.yandex.net (smtp12.mail.yandex.net [95.108.131.191]) by forward13.mail.yandex.net (Yandex) with ESMTP id 3B74B1428FE; Sun, 4 Sep 2011 00:56:46 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1315083406; bh=2NU7K1w/T2VrZV+5/GmO2gkrWz75v0A4rz+o6aohoJg=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=t+5XEtdHpEhYQS+CLYOstcNqZr9RrrsiT9vJ37Vp0U2J8i59Co0oe8R8nYPnzXFmG FNfmPKradAls/Lf3KjaPUdM/6Uq7GUFvv6fLCeh7ndY7+M7JLfPkRUc1qRfSm3coZH Vylc39zON6J28HdJWUGzAV6hi2R3S47MOHuvffd8= Received: from smtp12.mail.yandex.net (localhost [127.0.0.1]) by smtp12.mail.yandex.net (Yandex) with ESMTP id 2487416A03CD; Sun, 4 Sep 2011 00:56:46 +0400 (MSD) Received: from unknown (unknown [213.138.88.133]) by smtp12.mail.yandex.net (nwsmtp/Yandex) with ESMTP id ujkWtrcv; Sun, 4 Sep 2011 00:56:45 +0400 X-Yandex-Spam: 1 Message-ID: <4E629488.4090706@yandex.ru> Date: Sun, 04 Sep 2011 00:56:40 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: Chris Rees References: <4E5643A8.9060705@yandex.ru> <4E564DBE.1070700@yandex.ru> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports Mailing List Subject: Re: tinderbox: how to drop unneded Jail and Build X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 20:56:48 -0000 Chris Rees wrote on 25.08.2011 19:52: > On 25 August 2011 14:27, Ruslan Mahmatkhanov wrote: >> Chris Rees wrote on 25.08.2011 16:51: >>> >>> On 25 August 2011 13:44, Ruslan Mahmatkhanov wrote: >>>> >>>> How to correctly remove Jail and Build, created by ./tc createJail and >>>> ./tc >>>> createBuild accordingly? I have 7.3-FreeBSD, that was needed to one-time >>>> test single port. As far i understand, it's not enough to remove >>>> directory >>>> ${pb}/7.3-FreeBSD, since there is logs/packages/build >>>> etc for this build and database records also. How to deal with this >>>> correctly? >>> >>> cd ${pb}/scripts&& ./tc rmBuild -b ${build}&& ./tc rmJail -j ${jail} >>> >>> rm -r ${pb}/*/${jail_name} ${pb}/*/${build_name} ${pb}/${build_name} >>> >>> PLEASE check the globbing using echo first.... >>> >>> You may want to join tinderbox-list@marcuscom.com too ;) >>> >>> Chris >> >> Nice, thank you. I believe that this should be added to the Tinderbox >> Manual. And what about creating 9.0-BETA1 jail with -u LFTP question? >> > > I've added it to the README, thanks for the suggestion [1]. By the way, i believe that README.html#CHINSTALLATION should be updated (or added as option) with -u CSUP instead of -u CVSUP there in step 12: # cd ${pb}/scripts && ./tc createJail -j 8.2 -d "FreeBSD 8.2-RELEASE" \ -t RELENG_8_2_0_RELEASE -u CVSUP Since csup is now available in all supported FreeBSD versions. May be add example for -CURRENT too. > For now I think you need to use csup and make world method for 9-, > sorry. I'm talking to re about what the future plans are regarding ftp > -- not sure if this xz distribution is The Future. > > Chris > > [1] http://marcuscom.com/pipermail/tinderbox-cvs/2011-August/001527.html > > -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-ports@FreeBSD.ORG Sat Sep 3 23:42:29 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D67EB106564A for ; Sat, 3 Sep 2011 23:42:29 +0000 (UTC) (envelope-from bounces+73574-5af0-ports=freebsd.org@sendgrid.info) Received: from o3.sendgrid.info (o3.sendgrid.info [67.228.50.51]) by mx1.freebsd.org (Postfix) with SMTP id 69ED38FC0A for ; Sat, 3 Sep 2011 23:42:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h= message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=N56eVHhqKO7MJcHFyEstqNp7iWc=; b=T5KpfUuPzmLgPH59bmiNId/JRgL2 RnivjV9r4Tyo/S5MEzkhwCp0Gf815z26/L3fUtv+E6b5w0ezXwygk2pCSzFfpiku liKRCUMkjTlmjmJbEwLi/GSS9extmfrnTq8Q7ALxbFcZF5qTIXUYiW+/r6T1/Nc2 gLxLt7IlodbBWV4= Received: by 10.16.69.120 with SMTP id mf6.16259.4E62B38FA Sat, 03 Sep 2011 18:09:03 -0500 (CDT) Received: from mail.tarsnap.com (unknown [10.9.180.5]) by mi8 (SG) with ESMTP id 4e62b38f.4032.89aafe4 for ; Sat, 03 Sep 2011 18:09:03 -0500 (CST) Received: (qmail 92534 invoked from network); 3 Sep 2011 23:08:35 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by mail.tarsnap.com with ESMTP; 3 Sep 2011 23:08:35 -0000 Received: (qmail 58296 invoked from network); 3 Sep 2011 23:08:08 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 3 Sep 2011 23:08:08 -0000 Message-ID: <4E62B358.2070507@freebsd.org> Date: Sat, 03 Sep 2011 16:08:08 -0700 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110827 Thunderbird/6.0 MIME-Version: 1.0 To: Emanuel Haupt References: <20110903214100.096d8366.ehaupt@FreeBSD.org> In-Reply-To: <20110903214100.096d8366.ehaupt@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Sendgrid-EID: D4wkNorddCAWKCgJp5FEWT7T0/FI8quQhYe9JglV2zsPwMouQ8EB1n0cV+5fsLdR7ct3nhHgfgqgCLD0yNq+3ZoBJVDc5FIO6mIC9sXwUQIRt+duvIVRZFPj433hHpyampI90/Gvf04/Zs22ihOh5w== Cc: ports@FreeBSD.org Subject: Re: INDEX-9 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2011 23:42:29 -0000 On 09/03/11 12:41, Emanuel Haupt wrote: > In light of the upcoming release of 9.0-RELEASE it might be a good idea > to start providing INDEX-9 via portsnap. Especially since we want > people to try the BETA releases. Yes, this will happen soon. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid