From owner-freebsd-ports@freebsd.org Sun May 29 00:23:01 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27015B4526B for ; Sun, 29 May 2016 00:23:01 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.auburn.protected-networks.net (mail.auburn.protected-networks.net [IPv6:2001:470:1f07:4e1::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.auburn.protected-networks.net", Issuer "Protected Networks Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EDCF41F4A; Sun, 29 May 2016 00:23:00 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.auburn.protected-networks.net) by mail.auburn.protected-networks.net (Postfix) with ESMTPSA id 055741CC07; Sat, 28 May 2016 20:22:58 -0400 (EDT) To: FreeBSD Ports , riggs@freebsd.org From: Michael Butler Subject: vlc fails to compile on current? Openpgp: id=6F63E6399DCC8E3E94D60F0642FF6BAE0442D492 Message-ID: <60061558-2ba9-c0fa-f274-d791483f8f11@protected-networks.net> Date: Sat, 28 May 2016 20:22:57 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 00:23:01 -0000 Is anyone else seeing this? ../doltlibtool --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I. -I.. -DMODULE_STRING=\"$(p="demux/mkv/libmkv_plugin_la-virtual_segment.lo"; p="${p##*/}"; p="${p#lib}"; p="${p%_plugin*}"; p="${p%.lo}"; echo "$p")\" -D__PLUGIN__ -I./access -I./codec -I../include -I../include -I/usr/local/include -DLIBICONV_PLUG -O2 -pipe -march=core2 -DLIBICONV_PLUG -fstack-protector -fno-strict-aliasing -DLIBICONV_PLUG -Wall -Wextra -Wsign-compare -Wundef -Wpointer-arith -Wvolatile-register-var -fvisibility=hidden -O4 -ffast-math -funroll-loops -fomit-frame-pointer -MT demux/mkv/libmkv_plugin_la-virtual_segment.lo -MD -MP -MF demux/mkv/.deps/libmkv_plugin_la-virtual_segment.Tpo -c -o demux/mkv/libmkv_plugin_la-virtual_segment.lo `test -f 'demux/mkv/virtual_segment.cpp' || echo './'`demux/mkv/virtual_segment.cpp c++: warning: -O4 is equivalent to -O3 In file included from demux/mkv/util.cpp:24: In file included from demux/mkv/mkv.hpp:56: In file included from /usr/include/c++/v1/iostream:38: In file included from /usr/include/c++/v1/ios:216: In file included from /usr/include/c++/v1/__locale:15: In file included from /usr/include/c++/v1/string:439: In file included from /usr/include/c++/v1/algorithm:628: In file included from /usr/include/c++/v1/memory:616: /usr/include/c++/v1/atomic:823:1: error: expected unqualified-id kill_dependency(_Tp __y) _NOEXCEPT ^ ../include/vlc_atomic.h:45:7: note: expanded from macro 'kill_dependency' ((void)0) ^ In file included from demux/mkv/util.cpp:24: In file included from demux/mkv/mkv.hpp:56: In file included from /usr/include/c++/v1/iostream:38: In file included from /usr/include/c++/v1/ios:216: In file included from /usr/include/c++/v1/__locale:15: In file included from /usr/include/c++/v1/string:439: In file included from /usr/include/c++/v1/algorithm:628: In file included from /usr/include/c++/v1/memory:616: /usr/include/c++/v1/atomic:823:1: error: expected ')' From owner-freebsd-ports@freebsd.org Sun May 29 04:05:41 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D10DBB50A5A for ; Sun, 29 May 2016 04:05:41 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 906D71761; Sun, 29 May 2016 04:05:41 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1b6ryq-0002Bl-Ml; Sun, 29 May 2016 06:05:36 +0200 Date: Sun, 29 May 2016 06:05:36 +0200 From: Kurt Jaeger To: Michael Butler Cc: FreeBSD Ports , riggs@freebsd.org Subject: Re: vlc fails to compile on current? Message-ID: <20160529040536.GS41922@home.opsec.eu> References: <60061558-2ba9-c0fa-f274-d791483f8f11@protected-networks.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <60061558-2ba9-c0fa-f274-d791483f8f11@protected-networks.net> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 04:05:41 -0000 Hi! > Is anyone else seeing this? vlc builds for me on r299224M. -- pi@opsec.eu +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Sun May 29 04:50:14 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69D13B4F325 for ; Sun, 29 May 2016 04:50:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3BEFB1BDD for ; Sun, 29 May 2016 04:50:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22e.google.com with SMTP id l63so17740657ita.1 for ; Sat, 28 May 2016 21:50:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=ruanxs6t+dBMtT5ehzs+ZxHsFfXkGJfzBOf1K6ZpQP4=; b=nO85F9FUrc/nRP24ZtJdz6gipvLtsYrPYJ6SUFVmq822njLtNqI8cDwxF77gwgqXd/ GOoHAcxC6XhZ0YrcJieO8saoVVPEGmaXW776bhGr8HnV6fharVeUNk/nQ2OZ5tt2R4xZ CRkQZXepoLO09XWgKgjlL7DWIk6XpCfVlILBF/NU3FyLujqwy/eHZ4gwCU+pfHr/fMV/ FrpT5ETDqde0LPKZZcuTXnYowXPCNu7cMckwwAW48iN2OY1A3myeAGtjYkfAnjXOarFk hNuN4xQ97uJYpE+zeixuctVrevkI98Uswng0FtWUG44unuF6T0ggl4VpQKpXTLCQ3/LW CiEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=ruanxs6t+dBMtT5ehzs+ZxHsFfXkGJfzBOf1K6ZpQP4=; b=WnG5TK4MwOMmRvdJiMWa9vxo/a5UZTwWIDq5DLFmWOfyAViGCnA0w5lASnJ/eLfFBq gTv9t54qHWZPrucnEPOSn4B4h544A3n9ZNz6kD6Npum5q0j/CMXirCRe6++OO0mZ+968 wftbLPUQ/q+urRuMma82xRkGKEFfOIgSFYiLymolHe6XFMOUYSCAhmu4WR1FuJIX+1pj 1RCw1nieE2KfK36NkY6xIwXj+1NXAtcPscI9j/Nh8UN6ee2AqOtIJxuiFiCg0fWSvCnp 8NiueY80FsC72I23pEWAdnb+boaCPhh0+N81rVJ9V13C6yrhEKtYGmQQw8CmrNpvC8zv KY+Q== X-Gm-Message-State: ALyK8tJxrq6YiPrl5OXrfTewWlKywNNvYqYxLxoul01k/oM2BGB816Zjtfm3FEtV3vr7YG6M9M1GJ+oly+QNXA== MIME-Version: 1.0 X-Received: by 10.36.46.67 with SMTP id i64mr4329040ita.60.1464497413416; Sat, 28 May 2016 21:50:13 -0700 (PDT) Sender: wlosh@bsdimp.com Received: by 10.79.75.68 with HTTP; Sat, 28 May 2016 21:50:13 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: <1E66E56C-E615-4180-A3F2-E8E48E26B6CD@dsl-only.net> References: <1E66E56C-E615-4180-A3F2-E8E48E26B6CD@dsl-only.net> Date: Sat, 28 May 2016 22:50:13 -0600 X-Google-Sender-Auth: WOtrra4rDRn6xBzlme7RvuSlv1k Message-ID: Subject: Re: 11.0-CURRENT: lang/gcc, lang/gcc5, lang/gcc6-devel, lang/llvm38, etc. do not build on/for armv6 (now implicitly hard float) From: Warner Losh To: Mark Millard Cc: Gerald Pfeifer , Brooks Davis , FreeBSD Ports , FreeBSD Toolchain Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 04:50:14 -0000 On Wed, May 25, 2016 at 10:12 AM, Mark Millard wrote: > I'm not sure that Gerald or Brooks were CC'd on a report made to the arm list about armv6 builds of gcc and llvm being broken now because of hard float now being implicit: > (the first report listed below has more detail directly visible for gcc examples) > > https://lists.freebsd.org/pipermail/freebsd-arm/2016-May/013931.html > and: > https://lists.freebsd.org/pipermail/freebsd-arm/2016-May/013930.html > https://lists.freebsd.org/pipermail/freebsd-arm/2016-May/013932.html > https://lists.freebsd.org/pipermail/freebsd-arm/2016-May/013933.html > > The first (013931.html) shows that xgcc for configure:3686 for contest.c ends up with the likes of: > > /usr/local/bin/ld: error: a.out uses VFP register arguments, > /wrkdirs/usr/ports/lang/gcc/work/.build/./gcc/crtbegin.o does not > /usr/local/bin/ld: failed to merge target specific data of file > /wrkdirs/usr/ports/lang/gcc/work/.build/./gcc/crtbegin.o > /usr/local/bin/ld: error: a.out uses VFP register arguments, > /tmp//cchNL2QG.o does not > /usr/local/bin/ld: failed to merge target specific data of file /tmp//cchNL2QG.o > /usr/local/bin/ld: error: a.out uses VFP register arguments, > /wrkdirs/usr/ports/lang/gcc/work/.build/./gcc/crtend.o does not > /usr/local/bin/ld: failed to merge target specific data of file > /wrkdirs/usr/ports/lang/gcc/work/.build/./gcc/crtend.o > collect2: error: ld returned 1 exit status > > and points to gcc/config.gcc only having TARGET_FREEBSD_ARM_HARD_FLOAT=1 for arm*hf-*-freebsd* . But now armv6*-*-freebsd* is also hard float for 11.0-CURRENT. armv6*-*-freebsd is only hard float ABI for FreeBSD 11. > Of course until everyone updates to modern enough armv6 context a mix of softfloat and hardfloat will be around. Are you saying that we need to get these changes to the ports in place to support hard float? Are you saying we need to support a mix better (which is unlikely to happen, btw, without a passionate champion)? Is there some other point I'm missing? Warner From owner-freebsd-ports@freebsd.org Sun May 29 09:13:06 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB654B51D6A for ; Sun, 29 May 2016 09:13:06 +0000 (UTC) (envelope-from elferdo@gmail.com) Received: from mail-io0-x244.google.com (mail-io0-x244.google.com [IPv6:2607:f8b0:4001:c06::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 88FD217B0 for ; Sun, 29 May 2016 09:13:06 +0000 (UTC) (envelope-from elferdo@gmail.com) Received: by mail-io0-x244.google.com with SMTP id d197so9102643ioe.1 for ; Sun, 29 May 2016 02:13:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=y4XNKzgh7cSDzYfatRksDhnpHvAGIiljgLrE3pxR9g8=; b=epHkmfMnrNBaxrqyFYPvcda9weQocAELRlIjLVEgM2YfhxSXVS5LDSz6WAQJbpVCvJ baAnzJ6H/Uncw9/epdNtGugTMIewqaI83h3MW8KafmZ502PQKEtTiGZfEuC6FTkTw3JO /ezxpjkKqxWN9cwk3wSTWr2vCZEt8Yl897bID+qEhBNb7bBpoC6l2O8KGL+TUVgG6RTw C4eaT1VG/b/iMjwgMB6kDd77Ev8KF+HoUVAGjyOZmeRzegvcXP8jBFybc981VX/VmRLu bf0LIV4ogtseZpb3xAz/OquhBW1BlUDLpD9xZ0ltGfCv0gH9STnjZoSC4gq9C4rPTT2O s9bg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=y4XNKzgh7cSDzYfatRksDhnpHvAGIiljgLrE3pxR9g8=; b=jqItyl5/kd13WCSN618mOSAvoRQU1/E3ZJNhw5HwO1Mao7YDxTC41s0Mu4WTWRc3II Len/2hgYArEsyRq7C56T8PxmJOF/KeoxEi/6XbVFnuC9bIaiJGXN3t2ZooDu716eLVwO OZck+sOYlBw26H0qgDzmuJJFqiUBg5WPOc0P3rc1BVrMOVcLdTbUWy6oSZZU8Gu8vh4Z uHkMa2EpTWc5KqvVJ/uEinWau/gehYDwG744VyLrq59w/KHuRmgFTxDZFpe4cWIlfdJu wh/qgFFakZARftW3LOKToN3QdOPuSGabXY1W908NYERJQiYxn2tVTNBOzlDS0c5zCQMa qWNg== X-Gm-Message-State: ALyK8tLl42gcy36fpB8nM8+toOwA7r4qpBORQ8wNMsVTOuYBQfAc7xQvfVQ80/KWW1dYg6u/DglN5qEyege3IA== MIME-Version: 1.0 X-Received: by 10.107.55.196 with SMTP id e187mr9924183ioa.18.1464513185978; Sun, 29 May 2016 02:13:05 -0700 (PDT) Received: by 10.36.206.3 with HTTP; Sun, 29 May 2016 02:13:05 -0700 (PDT) Date: Sun, 29 May 2016 11:13:05 +0200 Message-ID: Subject: math/openblas + poudriere + manual building From: =?UTF-8?Q?Fernando_Herrero_Carr=C3=B3n?= To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 09:13:06 -0000 Hi everyone, I am using poudriere for the first time to test some patches to math/R. One new feature will be the ability to link against math/openblas. My portstree was updated yesterday (28/05). math/openblas is one of the de-facto, open source, high performance basic linear algebra packages (including paralellism, architecture specific code and so on). For my purposes right now I only want to build math/openblas (0.2.18,1) for my computer, so I uncheck the DYNAMIC_ARCH option, which I suppose will generate code for many architectures. I see there is a closed PR [1] suggesting that the port would automatically set this option as default if bulk building. However, since I have manually unset it, poudriere bails out suggesting that I build the package manually because the port optimizes for the build machine Finished build of math/openblas: Ignored: has to be built manually: Optimizes for the local machine Here come two questions: * After searching a bit, I have not found how to *manually* build a package in poudriere. Does that mean: build the port in your ports tree outside poudriere? Should that message be reworded? Is there something missing in the documentation? Am I missing something? * I see some people are manually editing the Makefile of math/atlas to tune to their machines [2]. My solution with math/openblas has been to finally enable DYNAMIC_ARCH, which probably compiles more code than I need to. I am fairly comfortable with the package optimizing for the build machine. Isn't there any easy way to force poudriere to go on? Setting NO_IGNORE in the environment or something like that (which, surprisingly, allows building of forbidden, but not ignored ports)? Cheers, Fernando [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209190 [2] https://lists.freebsd.org/pipermail/freebsd-ports/2014-December/097102.html From owner-freebsd-ports@freebsd.org Sun May 29 09:37:02 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CA0CB4E0BE for ; Sun, 29 May 2016 09:37:02 +0000 (UTC) (envelope-from mnd999@gmail.com) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 97CA91738 for ; Sun, 29 May 2016 09:37:01 +0000 (UTC) (envelope-from mnd999@gmail.com) Received: by mail-wm0-x22a.google.com with SMTP id z87so38781456wmh.0 for ; Sun, 29 May 2016 02:37:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:user-agent:mime-version :content-transfer-encoding; bh=8fusn/j4SJiGvJ8TMs3feKmrzCbMVZwI5FCFqgHB3iI=; b=uyfM0+3QDK5nvC9aj3aIGKfQ0Emu9kHoUmh5YcQja0YnDC2r2Xh+QN7QG6lJx+/1FQ jCFZlDyQ9ybFbGhdwW0gu8aNX/HDt0uEpC+1jfht/F66IhMbWLqufTFIEzvmcCTfW5ms bYZCQDaGuWutc+6s+17cr/Y2rTK2VmVyD8CAaWa5bdMeR/nvgVe+3ECUKYshjEftO2yK woktcGqi5o9hKUVwp7k8Y0WeA8i5cjQhKC1BuTYs19W3D+GPUSfe11ts1ezcqR4KNIGe /WK8H/2FOf/HyuwSpLbEc92wclmtCf9N6U1K0FsXc9xP6EHAAZjsd8R5ZaKfsL0TL1+v EaJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:date:message-id:user-agent :mime-version:content-transfer-encoding; bh=8fusn/j4SJiGvJ8TMs3feKmrzCbMVZwI5FCFqgHB3iI=; b=FJ/I2TlDeza2brHIpIXAXDjQ2+luvjss9fQtXLjmVNIqIzL8I1wGIfB2Bygn3NILRr W97xZKVtdLibuTg2op8jpm+5F7E0gNJCvlCcUPZkTzrY5H3Dzc7cysZg+NOwkhoSRBOu /lbOTK4lFLmDRzhY7Oj46d90DEBb+sjKk3d0JtUShwQTfY0A/khCNe08Kh0gxQ9Hquz3 OM+wFloRfsiucDFwidi7Hv5Dy0t4xRTc2BSyqZ55OjRaY8Tb4DKCpde9JWn60logUzQW sLqsQYj3MWOmSbhRNyiXemqcMGK4/mDXIlZkUDQvpFPgEQWN9zC2Hw+RrDT8O+Zj2cNt HuEw== X-Gm-Message-State: ALyK8tKR2M8aEx34yiqah8zssj0kvLVdyn1c7H90Qdopc/4VaIYa+HJOckMv7jlPDPo/uA== X-Received: by 10.28.230.87 with SMTP id d84mr6361963wmh.50.1464514619667; Sun, 29 May 2016 02:36:59 -0700 (PDT) Received: from markspc.local (5.0.2.b.b.a.9.e.d.c.7.9.b.a.d.f.2.a.6.7.3.a.d.0.0.b.8.0.1.0.0.2.ip6.arpa. [2001:8b0:da3:76a2:fdab:97cd:e9ab:b205]) by smtp.googlemail.com with ESMTPSA id o76sm17795954wme.0.2016.05.29.02.36.58 for (version=TLSv1/SSLv3 cipher=OTHER); Sun, 29 May 2016 02:36:58 -0700 (PDT) From: Mark Dixon To: freebsd-ports@freebsd.org Subject: Port with sbt build (archivers/snappy-java) Date: Sun, 29 May 2016 10:36:58 +0100 Message-ID: <3285429.1DVW0n9D9h@markspc.local> User-Agent: KMail/4.14.3 (FreeBSD/10.3-RELEASE-p3; KDE/4.14.3; amd64; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 09:37:02 -0000 Hi porters, I'm looking at a long overdue update of archivers/snappy-java which I have kinda fallen into maintaining. The current version of the port is a Maven build which uses a zipped up maven repository and runs maven in offline mode as is common for Maven builds. The new version of snappy/java however seems to use an sbt build, which is quite different. Has anyone got any experience of porting anything with an sbt build. I've got something going (link below) but it's very much an online build in that sbt fetches all sorts of dependenices from the internet in the build phase and this is not ideal. https://github.com/freebsd/freebsd-ports/compare/master...mnd999:snappy-java-1.1.2.4?expand=1 Regards, Mark From owner-freebsd-ports@freebsd.org Sun May 29 06:00:42 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 674C5B521D9 for ; Sun, 29 May 2016 06:00:42 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-184.reflexion.net [208.70.211.184]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2CA9618CE for ; Sun, 29 May 2016 06:00:41 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 4252 invoked from network); 29 May 2016 06:00:41 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 29 May 2016 06:00:41 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.90.3) with SMTP; Sun, 29 May 2016 02:01:17 -0400 (EDT) Received: (qmail 16367 invoked from network); 29 May 2016 06:01:17 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 29 May 2016 06:01:17 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id D45E1B1E001; Sat, 28 May 2016 23:00:32 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: 11.0-CURRENT: lang/gcc, lang/gcc5, lang/gcc6-devel, lang/llvm38, etc. do not build on/for armv6 (now implicitly hard float) From: Mark Millard In-Reply-To: Date: Sat, 28 May 2016 23:00:39 -0700 Cc: Gerald Pfeifer , Brooks Davis , FreeBSD Ports , FreeBSD Toolchain Content-Transfer-Encoding: quoted-printable Message-Id: <93022D2B-29D1-4422-A7B0-5366C0182973@dsl-only.net> References: <1E66E56C-E615-4180-A3F2-E8E48E26B6CD@dsl-only.net> To: Warner Losh X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 06:00:42 -0000 On 2016-May-28, at 9:50 PM, Warner Losh wrote: > On Wed, May 25, 2016 at 10:12 AM, Mark Millard = wrote: >> I'm not sure that Gerald or Brooks were CC'd on a report made to the = arm list about armv6 builds of gcc and llvm being broken now because of = hard float now being implicit: >> (the first report listed below has more detail directly visible for = gcc examples) >>=20 >> https://lists.freebsd.org/pipermail/freebsd-arm/2016-May/013931.html >> and: >> https://lists.freebsd.org/pipermail/freebsd-arm/2016-May/013930.html >> https://lists.freebsd.org/pipermail/freebsd-arm/2016-May/013932.html >> https://lists.freebsd.org/pipermail/freebsd-arm/2016-May/013933.html >>=20 >> The first (013931.html) shows that xgcc for configure:3686 for = contest.c ends up with the likes of: >>=20 >> /usr/local/bin/ld: error: a.out uses VFP register arguments, >> /wrkdirs/usr/ports/lang/gcc/work/.build/./gcc/crtbegin.o does not >> /usr/local/bin/ld: failed to merge target specific data of file >> /wrkdirs/usr/ports/lang/gcc/work/.build/./gcc/crtbegin.o >> /usr/local/bin/ld: error: a.out uses VFP register arguments, >> /tmp//cchNL2QG.o does not >> /usr/local/bin/ld: failed to merge target specific data of file = /tmp//cchNL2QG.o >> /usr/local/bin/ld: error: a.out uses VFP register arguments, >> /wrkdirs/usr/ports/lang/gcc/work/.build/./gcc/crtend.o does not >> /usr/local/bin/ld: failed to merge target specific data of file >> /wrkdirs/usr/ports/lang/gcc/work/.build/./gcc/crtend.o >> collect2: error: ld returned 1 exit status >>=20 >> and points to gcc/config.gcc only having = TARGET_FREEBSD_ARM_HARD_FLOAT=3D1 for arm*hf-*-freebsd* . But now = armv6*-*-freebsd* is also hard float for 11.0-CURRENT. >=20 > armv6*-*-freebsd is only hard float ABI for FreeBSD 11. My understanding is that the older rpi's are ARM1176JZF-S, "which IS = armv6" to quote Ian Lepore. I've not used such under 10.x at all so I = may be making some implicit bad assumptions below. Feel free to correct = my stupidities. . . Unless 10.x FreeBSD is also switching to hardfloat I do not expect that = the above part of your note is fully descriptive for compiler ports. = (Presumes continued targeting of 10.x armv6 for rpi.) armv6*-*-freebsd10* (such as for a 10.x rpi) is softfloat and stays that = way in 10.x . armv6*-*-freebsd11* (such as for a 11.x rpi or rpi2) is hardfloat now. (I'm guessing those naming patterns.) The compiler ports and their supporting runtime files deal with both = targeting contexts for some amount of time (until 10.x can be dropped by = ports). (Forms of on-the-fly code generation might also have such = issues.) >> Of course until everyone updates to modern enough armv6 context a mix = of softfloat and hardfloat will be around. >=20 > Are you saying that we need to get these changes to the ports in place > to support hard float? Are you saying we need to support a mix better > (which is unlikely to happen, btw, without a passionate champion)? Is > there some other point I'm missing? >=20 > Warner A compiler toolchain in ports that targeted softfloat ABI before now = needs to target the hardfloat ABI for 11.0 --and that apparently now = uses "VFP register arguments". gcc/crtbegin.o , gcc/crtend.o , and the like for hardfloat contexts need = to handle at least "VFP register arguments" now but do not yet do so. The old armv6*-*-freebsd* pattern used to identify a softfloat context = and some text matching that pattern now identifies a hardfloat context ( = armv6*-*-freebsd11* as far as I can tell). The toolchain example above = is/was based on the pattern arm*hf-*-freebsd* to identify hardfloat vs. = armv6*-*-freebsd* for softfloat (both 10.x and 11.0?). This is no longer = sufficient. Of course until someone rebuilds and installs replacing an older 11.0 = build that had text matching the pattern armv6*-*-freebsd11*, the build = it really is still softfloat so there is a transition-time issue because = the text used does not uniquely identify the context: Once the ports = they needed are ready folks then need to upgrade the 11.0 vintage to = track. Before then the lack of ports might break their context if they = update the 11.0 vintage.=20 So I think the answer to the first question is: Yes there are changes = that need to be made for the compiler ports to work for 11.0 and its = hardfloat use. I'm guessing that building the ports for targeting 10.x = is also to be possible for some time. For the second question: hardfloat is not supported yet in ports. It = needs to be for targeting armv6*-*-freebsd11* (11.0). Softfloat needs to = be supported for targeting armv6*-*-freebsd10* (10.x). I do not see 11.0 = supporting softfloat going forward. I do not see 10.x supporting = hardfloat going forward. The relevant ports have 2 contexts to span = unless 10.x ( armv6*-*-freebsd10* ) support is to be dropped now. Am I clearer this time? (I leave the 3rd question to you: Did I make any = new points here?) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ports@freebsd.org Sun May 29 09:58:02 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C38FEB4F1D6 for ; Sun, 29 May 2016 09:58:02 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B218519E2 for ; Sun, 29 May 2016 09:58:02 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id B1754B4F1D3; Sun, 29 May 2016 09:58:02 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AEB71B4F1D2 for ; Sun, 29 May 2016 09:58:02 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org (portscout.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A0C5719E1 for ; Sun, 29 May 2016 09:58:02 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.15.2/8.15.2) with ESMTP id u4T9w2PZ059224 for ; Sun, 29 May 2016 09:58:02 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.15.2/8.15.2/Submit) id u4T9w2ha059222; Sun, 29 May 2016 09:58:02 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201605290958.u4T9w2ha059222@portscout.freebsd.org> X-Authentication-Warning: portscout.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Sun, 29 May 2016 09:58:02 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 09:58:02 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ archivers/xar | 1.5.2 | 1.6.1 ------------------------------------------------+-----------------+------------ lang/sbcl | 1.3.1 | 1.3.6 ------------------------------------------------+-----------------+------------ sysutils/fusefs-s3fs | 1.78 | v1.80 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Sun May 29 10:01:50 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED42EB4F53E for ; Sun, 29 May 2016 10:01:50 +0000 (UTC) (envelope-from c.brinkhaus@t-online.de) Received: from mailout06.t-online.de (mailout06.t-online.de [194.25.134.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B2A961EAB for ; Sun, 29 May 2016 10:01:50 +0000 (UTC) (envelope-from c.brinkhaus@t-online.de) Received: from fwd10.aul.t-online.de (fwd10.aul.t-online.de [172.20.26.152]) by mailout06.t-online.de (Postfix) with SMTP id 4865941C7620; Sun, 29 May 2016 12:01:46 +0200 (CEST) Received: from esprimo.local (TW0GbcZBoh4Gh-yKHhI9q7CueTpTFt2RW29ttUNLOxp7IlfFEH-tfCrRiSL4RzZQul@[217.81.128.197]) by fwd10.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1b6xXM-2RGp5E0; Sun, 29 May 2016 12:01:36 +0200 Received: from esprimo.local (localhost [127.0.0.1]) by esprimo.local (Postfix) with ESMTP id 85DAD45CD8A; Sun, 29 May 2016 12:01:35 +0200 (CEST) Received: (from chris@localhost) by esprimo.local (8.15.2/8.15.2/Submit) id u4TA1Zgo087475; Sun, 29 May 2016 12:01:35 +0200 (CEST) (envelope-from chris) Date: Sun, 29 May 2016 12:01:35 +0200 From: Christoph Brinkhaus To: Alphons van Werven Cc: Marko =?utf-8?B?Q3VwYe+/vT8=?= , freebsd-ports@FreeBSD.org Subject: Re: mail/ssmtp: mailer.conf instruction in handbook differs from pkg-message Message-ID: <20160529100135.GA28863@esprimo.local> References: <20160525125702.21cee03d@mephala.kappastar.com> <20160525122257.GB81950@spectrum.skysmurf.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160525122257.GB81950@spectrum.skysmurf.nl> User-Agent: Mutt/1.6.1 (2016-04-27) X-ID: TW0GbcZBoh4Gh-yKHhI9q7CueTpTFt2RW29ttUNLOxp7IlfFEH-tfCrRiSL4RzZQul X-TOI-MSGID: af514efa-a79c-40ac-868f-c7b5c5e03a40 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 10:01:51 -0000 On Wed, May 25, 2016 at 02:22:57PM +0200, Alphons van Werven wrote: Dear Alphons, > Marko Cupa? wrote: > > > Are they both correct, or one of them needs to be updated? > > I recommend doing what the port says. The Handbook appears to be incorrect > at this point and probably needs updating. > I have created a patch as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209831 and referred to this discussion. Kind regards, Christoph From owner-freebsd-ports@freebsd.org Sun May 29 11:24:17 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 497CDB53011 for ; Sun, 29 May 2016 11:24:17 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 05EB11B26 for ; Sun, 29 May 2016 11:24:17 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1b6ypN-0002hw-0s; Sun, 29 May 2016 13:24:17 +0200 Date: Sun, 29 May 2016 13:24:17 +0200 From: Kurt Jaeger To: Fernando Herrero =?iso-8859-1?Q?Carr=F3n?= Cc: freebsd-ports@freebsd.org Subject: Re: math/openblas + poudriere + manual building Message-ID: <20160529112416.GU41922@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 11:24:17 -0000 Hi! > I am using poudriere for the first time to test some patches to math/R. One > new feature will be the ability to link against math/openblas. My portstree > was updated yesterday (28/05). > For my purposes right now I only want to build math/openblas (0.2.18,1) for > my computer, so I uncheck the DYNAMIC_ARCH option, which I suppose will > generate code for many architectures. Use DYNAMIC_ARCH, otherwise the port is configured to not build in poudriere. As far as I understand, those BLAS related codes all try either to build for multiple CPUs or try to build for a specific CPU. So what should the poor port maintainer do ? Either she allows to build anyway, which produces a optimized port for the CPU of the builder host, or she says: We can't, build it manually. It's a mess. From my point of view, it should always build with DYNAMIC_ARCH, which is not always the fastest binary, but at least it builds 8-} > * After searching a bit, I have not found how to *manually* build a package > in poudriere. Does that mean: build the port in your ports tree outside > poudriere? Yes. > Should that message be reworded? Is there something missing in > the documentation? Am I missing something? It's a difficult topic, so it's difficult to reword. Do you have suggestions ? > * I see some people are manually editing the Makefile of math/atlas to tune > to their machines [2]. My solution with math/openblas has been to finally > enable DYNAMIC_ARCH, which probably compiles more code than I need to. I am > fairly comfortable with the package optimizing for the build machine. Isn't > there any easy way to force poudriere to go on? You are asking for an easy way to override MANUAL_PACKAGE_BUILD. > Setting NO_IGNORE in the > environment or something like that (which, surprisingly, allows building of > forbidden, but not ignored ports)? It would be useful, yes. Probably submit a PR for poudriere to add some flag like this. -- pi@opsec.eu +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Sun May 29 11:48:44 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E775B536B0 for ; Sun, 29 May 2016 11:48:44 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from mail.skysmurf.nl (spectrum.skysmurf.nl [83.162.175.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.skysmurf.nl", Issuer "mail.skysmurf.nl" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 13E421987 for ; Sun, 29 May 2016 11:48:42 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from spectrum.skysmurf.nl (mail.skysmurf.nl [192.168.42.4]) by mail.skysmurf.nl (8.15.2/8.15.2) with SMTP id u4TBmXES011628; Sun, 29 May 2016 13:48:33 +0200 (CEST) (envelope-from freebsd@skysmurf.nl) Received: by spectrum.skysmurf.nl (sSMTP sendmail emulation); Sun, 29 May 2016 13:48:33 +0200 Date: Sun, 29 May 2016 13:48:33 +0200 From: Alphons van Werven To: Christoph Brinkhaus Cc: freebsd-ports@FreeBSD.org Subject: Re: mail/ssmtp: mailer.conf instruction in handbook differs from pkg-message Message-ID: <20160529114833.GA11528@spectrum.skysmurf.nl> References: <20160525125702.21cee03d@mephala.kappastar.com> <20160525122257.GB81950@spectrum.skysmurf.nl> <20160529100135.GA28863@esprimo.local> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline In-Reply-To: <20160529100135.GA28863@esprimo.local> X-PGP-Key: http://www.skysmurf.nl/~fonz/fonz_pubkey.asc User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 11:48:44 -0000 --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Christoph Brinkhaus wrote: >> I recommend doing what the port says. The Handbook appears to be incorre= ct >> at this point and probably needs updating. >=20 > I have created a patch as > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209831 > and referred to this discussion. Thanks. There really is no need for any of the mailer.conf entries to point to sendmail when one actually uses sSMTP. In fact, in some cases that's just plain wrong. AvW --=20 A.J. "Fonz" van Werven mailsig: Ob technicas difficultates, lux in fine cuniculum non operatur. --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJXStcRAAoJEAfP7gJTaCe80gwQANSAY7ecgI682r+cFhGFWxo7 XA99jYe5nj2b85vgBMomBYyySsmz3iO8yeqK5mYHHhLZBDqBBlTxy9dSKP2DKSb4 VkNdU3obvG8xoBIvan7ibgVJHytVult8SIQbnd2hm8flbpLpHBtZCQ1wBF3b/AFH UpRrBfcrE67F8DCxqxo0SOHkBu4FnmjyGAF3EiMJzkztcZZ7w6N3AMtdoIS3h0nl eBkXIR7KT63xvyygp6Q91qEPsJaX6OfLGUAm2VbOtGFdEn2chELGKYvgBVRZMNF8 BChOLDBBLTx2T5o/7P7rwIjCv+Bi3MdBkluwqe9Nwpn4ZZd9oNoyyIN9zRgzn2AL 0B4xMtsJgyD59YWPz537ZpItqf6AFkhcu1OA4/WYXPGi9PGWC8JfcXopo63v/7+n qjPASAxm8MDha1vtacU/bjGeuYtc0entX1J4gAj65KEJM5efint/+eBVxqWz+80/ QPcXxupV0JXr8jeWe6ctV1Z3WWmqyZR40/jbh24eyqZs+bNbYSkTFOgvsmCshGTN bRIPGh62sfyzsRhXiFZCnF8B+Mv1vz1cVRcfWVnVEvaWVGKQS1hfZF2up2htZ04R Vvvw5evs2I/vfVaNrPY3AaYkmxtQSgEKHjDVbesvfzn8i0dMx6FSC7dApj8RUwBK mjdFMJGY1FSKzSJnMPiM =IKRS -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl-- From owner-freebsd-ports@freebsd.org Sun May 29 11:59:26 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B53B6B53959 for ; Sun, 29 May 2016 11:59:26 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from lab.alexdupre.com (lab.alexdupre.com [81.174.31.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E8F551EA0 for ; Sun, 29 May 2016 11:59:25 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: (qmail 19651 invoked from network); 29 May 2016 11:52:39 -0000 Received: from unknown (HELO ?192.168.178.149?) (sysadmin@alexdupre.com@192.168.178.149) by lab.alexdupre.com with ESMTPSA; 29 May 2016 11:52:39 -0000 Subject: Re: Port with sbt build (archivers/snappy-java) To: Mark Dixon , freebsd-ports@freebsd.org References: <3285429.1DVW0n9D9h@markspc.local> From: Alex Dupre Message-ID: <574AD80A.4080302@FreeBSD.org> Date: Sun, 29 May 2016 13:52:42 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 MIME-Version: 1.0 In-Reply-To: <3285429.1DVW0n9D9h@markspc.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 11:59:26 -0000 Mark Dixon ha scritto: > The new version of snappy/java however seems to use an sbt build, which is quite > different. Has anyone got any experience of porting anything with an sbt build. No experience, but have you seen this? https://github.com/sbt/sbt/wiki/User-Stories:--Offline-mode-and-Dependency-Locking -- Alex Dupre From owner-freebsd-ports@freebsd.org Sun May 29 12:57:18 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63187B4F019 for ; Sun, 29 May 2016 12:57:18 +0000 (UTC) (envelope-from thomas.e.zander@googlemail.com) Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA5921EBD for ; Sun, 29 May 2016 12:57:17 +0000 (UTC) (envelope-from thomas.e.zander@googlemail.com) Received: by mail-lf0-x22e.google.com with SMTP id b73so39938224lfb.3 for ; Sun, 29 May 2016 05:57:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=x+Ppo8QjuEITmYCDH4oF5wJMiDOsJtxxyD7taCjt4oM=; b=l0/T4jPOjT+Ka2yQKxURHvguvwXD/lDUUeDK6pDpEPiaDAWOFodae12gWpTxrQJsap tlWulPr89FwtM2fMk/7PoBEKZiHA7Tf83oW38xL42GLkgAbU/3qe98Gw03GPMnl7oQFY aZ7H9zgot4EIbkWsJcvBZudxYCpF0JGYvLt/+XdMC61M/X/c+FFPYK6HntDo+8NnJAJM gZl+4He1svsi1nBIW5+YLWWmJ1qucRlcHkz9b0x9d6CVKZRBtt0UKEP2zGnAsyy6m7Lr 0O4Ws6mY0jS26ecbtJ1VPw1Reg3JrcbOQ9WjOkRLnrouC+03ekAaM05oWPVUMvJ7WLgJ kB3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=x+Ppo8QjuEITmYCDH4oF5wJMiDOsJtxxyD7taCjt4oM=; b=VDDjeoSJ5NQRZH1TaTtbP/a7qK6EiyBIIhIAje2UeS0RFvvXucZagQgN+8+H5Vh3It UDRzSMpRDNvVy36CIPXvJEGEYjAiszzbEleecoZFKqdbjT697KM3hfHSH4m6nIR4UhNU fHxbU23x2nOZbLHQDYHOdlrFQCekPoOeE9YgZ4LH7qvhIfbwMLcDq5zNjLjc5hPUElgG WwHt/XM9CjWmbKc0L9mHzI45YhkyKvVAwTKXbEKdrzgBqAJ488v8QJNqoLnUiju/Z7E7 eM8pTko5Z+b7z5ne96wggh9lvRkkANSkJhb6W2uUaqm6egmfn+PYjzuqsYgK/luRwIpI Hbag== X-Gm-Message-State: ALyK8tLodBUWvp8djJyxv5WZ8qg7tPoFgavuk81fOA6zbJnKJzkh912htjay1U9LSSTIawjTtfcOUYm0rh5VeQ== MIME-Version: 1.0 X-Received: by 10.25.26.204 with SMTP id a195mr5957508lfa.217.1464526635458; Sun, 29 May 2016 05:57:15 -0700 (PDT) Sender: thomas.e.zander@googlemail.com Received: by 10.25.17.219 with HTTP; Sun, 29 May 2016 05:57:15 -0700 (PDT) In-Reply-To: <60061558-2ba9-c0fa-f274-d791483f8f11@protected-networks.net> References: <60061558-2ba9-c0fa-f274-d791483f8f11@protected-networks.net> Date: Sun, 29 May 2016 14:57:15 +0200 X-Google-Sender-Auth: yBY6kbSeufrixvhDbZ0CqT-crQ4 Message-ID: Subject: Re: vlc fails to compile on current? From: Thomas Zander To: Michael Butler Cc: FreeBSD Ports Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 12:57:18 -0000 On 29 May 2016 at 02:22, Michael Butler wrote: > Is anyone else seeing this? > [...] > In file included from demux/mkv/util.cpp:24: > In file included from demux/mkv/mkv.hpp:56: > In file included from /usr/include/c++/v1/iostream:38: > In file included from /usr/include/c++/v1/ios:216: > In file included from /usr/include/c++/v1/__locale:15: > In file included from /usr/include/c++/v1/string:439: > In file included from /usr/include/c++/v1/algorithm:628: > In file included from /usr/include/c++/v1/memory:616: > /usr/include/c++/v1/atomic:823:1: error: expected unqualified-id > kill_dependency(_Tp __y) _NOEXCEPT This looks like you hit https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209722 Dimitry has proposed a patch for this issue. Will test it and see that we get a solution committed asap. Best regards Riggs From owner-freebsd-ports@freebsd.org Sun May 29 15:10:08 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 092E0B5369F for ; Sun, 29 May 2016 15:10:08 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.auburn.protected-networks.net (mail.auburn.protected-networks.net [IPv6:2001:470:1f07:4e1::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.auburn.protected-networks.net", Issuer "Protected Networks Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CD5641875; Sun, 29 May 2016 15:10:07 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.auburn.protected-networks.net) by mail.auburn.protected-networks.net (Postfix) with ESMTPSA id 7C6301CCD8; Sun, 29 May 2016 11:10:05 -0400 (EDT) Subject: Re: vlc fails to compile on current? To: Thomas Zander References: <60061558-2ba9-c0fa-f274-d791483f8f11@protected-networks.net> Cc: FreeBSD Ports From: Michael Butler Openpgp: id=6F63E6399DCC8E3E94D60F0642FF6BAE0442D492 Message-ID: <50947637-0b82-c815-724f-5a8cc1034c25@protected-networks.net> Date: Sun, 29 May 2016 11:10:03 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 May 2016 15:10:08 -0000 On 05/29/16 08:57, Thomas Zander wrote: > On 29 May 2016 at 02:22, Michael Butler wrote: >> Is anyone else seeing this? >> [...] > >> In file included from demux/mkv/util.cpp:24: >> In file included from demux/mkv/mkv.hpp:56: >> In file included from /usr/include/c++/v1/iostream:38: >> In file included from /usr/include/c++/v1/ios:216: >> In file included from /usr/include/c++/v1/__locale:15: >> In file included from /usr/include/c++/v1/string:439: >> In file included from /usr/include/c++/v1/algorithm:628: >> In file included from /usr/include/c++/v1/memory:616: >> /usr/include/c++/v1/atomic:823:1: error: expected unqualified-id >> kill_dependency(_Tp __y) _NOEXCEPT > > This looks like you hit > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209722 > > Dimitry has proposed a patch for this issue. Will test it and see that > we get a solution committed asap. Thanks - I patched as proposed and it now compiles and runs as hoped :-) imb From owner-freebsd-ports@freebsd.org Mon May 30 01:37:24 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9AF84B515B7 for ; Mon, 30 May 2016 01:37:24 +0000 (UTC) (envelope-from db@db.net) Received: from diana.db.net (unknown [IPv6:2620:64:0:1:223:7dff:fea2:c8f2]) by mx1.freebsd.org (Postfix) with ESMTP id 8A67C1491 for ; Mon, 30 May 2016 01:37:24 +0000 (UTC) (envelope-from db@db.net) Received: from night.db.net (localhost [127.0.0.1]) by diana.db.net (Postfix) with ESMTP id 77A622AA355; Sun, 29 May 2016 19:36:46 -0600 (MDT) Received: by night.db.net (Postfix, from userid 1000) id 9ED641CDE4; Sun, 29 May 2016 21:37:20 -0400 (EDT) Date: Sun, 29 May 2016 21:37:20 -0400 From: Diane Bruce To: Chris H Cc: "freebsd-ports@freebsd.org" , Marin Bernard Subject: Re: Poudriere testport failure but manual jailed build success Message-ID: <20160530013720.GA76698@night.db.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2016 01:37:24 -0000 On Tue, Mar 03, 2015 at 05:24:15PM -0800, Chris H wrote: > On Tue, 3 Mar 2015 23:37:30 +0100 Marin Bernard wrote > > > Hi, > > > > I've been banging my head for several days on what follows and I've come to > > the point where I have to get some help. Here's the point. > > > > I'm trying to port LizardFS (a distributed file system for Unix/Linux) on > > FreeBSD and I built a port candidate I would like to submit. But first I > > needed to be sure everything was OK, so I ran some tests. As of now: > > - The port builds fine on FreeBSD 10.1-RELEASE amd64 host. > > - portlint does not report any issue (on the same host as above) > > - port test (from porttools) happily validates the port (on the same host > > as above) - BUT poudriere fails to build the port. > > > > I'm using poudriere 3.1.1 on FreeBSD 11-Current, and failure occurs within a > > FreeBSD 10.1-RELEASE amd64 jail. > > > > What basically happens is that the build process runs fine until it reaches > > man page generation. There, a2x throws an error because xlstproc returns with > > return code 5 (= "error in the stylesheet"), whereas it shouldn't. What kills > > me here is that if I enter the jail after the failure and try to build the > > port manually, everything builds fine! You'll find poudriere log at the end > > of this message. > > > Any reason you couldn't simply lower the risk of failure based > on tools you have no control over; by simply creating a valid > man page to begin with? In other words; if the man is already > properly formatted groff/troff/mandoc (take your pick). You > wouldn't ever need to worry again. :) > > Just a thought, and hope it helps. I just ran into this one. Here is the fix. (months late) You need a LIBDEPENDS on libxslt.so:textproc/libxslt This probably should be documented in the porters handbook. > > --Chris > .. > > Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db From owner-freebsd-ports@freebsd.org Mon May 30 09:40:20 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7EB06B546C9 for ; Mon, 30 May 2016 09:40:20 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6D9691AE3 for ; Mon, 30 May 2016 09:40:20 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 67548B546C7; Mon, 30 May 2016 09:40:20 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6704AB546C6 for ; Mon, 30 May 2016 09:40:20 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org (portscout.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5B6571AE2 for ; Mon, 30 May 2016 09:40:20 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.15.2/8.15.2) with ESMTP id u4U9eKwO048981 for ; Mon, 30 May 2016 09:40:20 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.15.2/8.15.2/Submit) id u4U9eK5l048979; Mon, 30 May 2016 09:40:20 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201605300940.u4U9eK5l048979@portscout.freebsd.org> X-Authentication-Warning: portscout.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Mon, 30 May 2016 09:40:20 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2016 09:40:20 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ biology/phyml | 3.2.0 | v3.2.20160529 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Mon May 30 19:01:23 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8B59B54A8C for ; Mon, 30 May 2016 19:01:23 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B10CF1C9F for ; Mon, 30 May 2016 19:01:23 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id u4UJ1H07093068 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 30 May 2016 12:01:17 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id u4UJ1Hac093067 for freebsd-ports@freebsd.org; Mon, 30 May 2016 12:01:17 -0700 (PDT) (envelope-from sgk) Date: Mon, 30 May 2016 12:01:16 -0700 From: Steve Kargl To: freebsd-ports@freebsd.org Subject: science/hdf5 ABI broken Message-ID: <20160530190116.GA92928@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2016 19:01:23 -0000 The recent update from hdf5 1.8.16 to 1.10.0 has introduced an issue with ABI incompatibility. Thus, anyone that has code written to the 1.8.16 ABI may find that their code no longer functions with 1.10.0. This should have been noted in ports/UPDATING. To fix the problem (currently under testin), one needs to apply the following patches. Index: Makefile =================================================================== --- Makefile (revision 415194) +++ Makefile (working copy) @@ -23,7 +23,8 @@ CONFIGURE_ARGS= --enable-cxx \ --enable-hl \ --enable-instrument \ - --enable-strict-format-checks + --enable-strict-format-checks \ + --with-default-api-version=v18 GNU_CONFIGURE= yes INSTALL_TARGET= install-strip MAKE_JOBS_UNSAFE= yes --- work/hdf5-1.10.0/fortran/src/H5_f.c.orig 2016-05-30 11:51:55.838813000 -0700 +++ work/hdf5-1.10.0/fortran/src/H5_f.c 2016-05-30 11:52:46.901739000 -0700 @@ -227,14 +227,14 @@ /* * FIND H5T_NATIVE_REAL_C_LONG_DOUBLE */ -#if H5_FORTRAN_C_LONG_DOUBLE_IS_UNIQUE!=0 +#if FORTRAN_C_LONG_DOUBLE_IS_UNIQUE!=0 if (sizeof(real_C_LONG_DOUBLE_f) == sizeof(float)) { if ((types[12] = (hid_t_f)H5Tcopy(H5T_NATIVE_FLOAT)) < 0) return ret_value; } /*end if */ else if (sizeof(real_C_LONG_DOUBLE_f) == sizeof(double)) { if ((types[12] = (hid_t_f)H5Tcopy(H5T_NATIVE_DOUBLE)) < 0) return ret_value; } /*end if */ -# if H5_FORTRAN_HAVE_C_LONG_DOUBLE!=0 +# if FORTRAN_HAVE_C_LONG_DOUBLE!=0 else if (sizeof(real_C_LONG_DOUBLE_f) == sizeof(long double)) { if ( H5_PAC_C_MAX_REAL_PRECISION >= H5_PAC_FC_MAX_REAL_PRECISION) { if ((types[12] = (hid_t_f)H5Tcopy(H5T_NATIVE_LDOUBLE)) < 0) return ret_value; Please supply either a science/hdf5-1.8 port, revert the 1.10.0 update, or consider the above patches. -- Steve From owner-freebsd-ports@freebsd.org Mon May 30 19:12:57 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60F7FB54DEC for ; Mon, 30 May 2016 19:12:57 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from mail.skysmurf.nl (spectrum.skysmurf.nl [83.162.175.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.skysmurf.nl", Issuer "mail.skysmurf.nl" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0745E13D0 for ; Mon, 30 May 2016 19:12:55 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from spectrum.skysmurf.nl (mail.skysmurf.nl [192.168.42.4]) by mail.skysmurf.nl (8.15.2/8.15.2) with SMTP id u4UJCk4e023718; Mon, 30 May 2016 21:12:46 +0200 (CEST) (envelope-from freebsd@skysmurf.nl) Received: by spectrum.skysmurf.nl (sSMTP sendmail emulation); Mon, 30 May 2016 21:12:46 +0200 Date: Mon, 30 May 2016 21:12:46 +0200 From: Alphons van Werven To: Steve Kargl Cc: FreeBSD ports mailing list Subject: Re: science/hdf5 ABI broken Message-ID: <20160530191246.GA534@spectrum.skysmurf.nl> References: <20160530190116.GA92928@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline In-Reply-To: <20160530190116.GA92928@troutmask.apl.washington.edu> X-PGP-Key: http://www.skysmurf.nl/~fonz/fonz_pubkey.asc User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2016 19:12:57 -0000 --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Steve Kargl wrote: > Please supply either a science/hdf5-1.8 port, revert the 1.10.0 > update, or consider the above patches. Sounds like a job for the port's maintainer... % make -C /usr/ports/science/hdf5 maintainer HTH, AvW --=20 A.J. "Fonz" van Werven mailsig: Ob technicas difficultates, lux in fine cuniculum non operatur. --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJXTJCtAAoJEAfP7gJTaCe8KDYP/2fV896sqUS6xRwOUHweHkmn t8OLWuP3VScmakeOW3kue3v1AIJEdAOrbuh0oS/1NhppFGa0Mbry5/D5pZQhXu/b YantHGTgbzUf4g75G1AW8AP2AF+6ZO4YpIAPedNMacSlbuqKLBXHDrcu65w77ZTj YQgIve4yaDThnmr/yyoRUXWyevgDHibGzMIkOW8KNFCncaIrrTl8jT4QMRF52dX0 sPYEMHP53cd1WKImYU+867FWBa2rdskTDRdy0BMe63DsNtZEApzjwFPeJDKxeeVh II1mD+3jSa7V2DzLAo8q5p7jWWbOnDcNPSGj9sNRnltGPbg3MDvmF2qud40KFXEk bcc+cb0jRNnqenY98UToQazPySO+dr883aTnfP/g88qa4+HEAhS5n6kF/VfIHCLW xjaCdgnuU7NGJ0gTILNxHEN+43Bn8F55itjTIy9AVEvo0FdRt+nbkKUqDGrSkLY4 0e7/m/4E5kmHysniYNfaw0VNLjfzXgcfHThqPfN3zF6rV/+mQHjbO3DSIwRu+bQZ OO+t1sTL+abfLB+x0UiVkJedo7fRBfK10SKeJZlrXAmuW//PJzDN0oQjs7Rv/fs5 R2EU5mDJ8ZQxYHwdCDGJ2+fDrDNBcOpzJb7ndEnhn0juyh2jaWinTsdnr1HRIhsf Gmtnh+jKGvxQUBIsqiOj =YSga -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn-- From owner-freebsd-ports@freebsd.org Tue May 31 09:20:14 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93B0BB55A4E for ; Tue, 31 May 2016 09:20:14 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 823FE1FD3 for ; Tue, 31 May 2016 09:20:14 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 81819B55A4D; Tue, 31 May 2016 09:20:14 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7EB10B55A4B for ; Tue, 31 May 2016 09:20:14 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org (portscout.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 701001FD1 for ; Tue, 31 May 2016 09:20:14 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.15.2/8.15.2) with ESMTP id u4V9KEqX079592 for ; Tue, 31 May 2016 09:20:14 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.15.2/8.15.2/Submit) id u4V9KEbf079590; Tue, 31 May 2016 09:20:14 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201605310920.u4V9KEbf079590@portscout.freebsd.org> X-Authentication-Warning: portscout.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Tue, 31 May 2016 09:20:14 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2016 09:20:14 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ biology/phyml | 3.2.0 | v3.2.20160530 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Tue May 31 13:17:29 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86001B557CC for ; Tue, 31 May 2016 13:17:29 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from toco-domains.de (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1AF20177F for ; Tue, 31 May 2016 13:17:29 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id 17F831AAF01E; Tue, 31 May 2016 13:17:18 +0200 (CEST) Subject: Re: old ports/packages To: Grzegorz Junka , freebsd-ports@freebsd.org References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> From: Torsten Zuehlsdorff Message-ID: <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> Date: Tue, 31 May 2016 15:17:18 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2016 13:17:29 -0000 On 04.05.2016 19:17, Grzegorz Junka wrote: Please excuse my late answer. I was right into vacation and need to handle some work right afterwards. >>> What you cannot do is create old-style packages from a new ports >>> tree. This is because the ports infrastructure has been changing >>> since pkg_install was deprecated, and pkg_install simply will not >>> work with the current ports tree (and, as I understand it, cannot >>> practically be modified in order to work with it). >> >> You are mostly correct. It is possible to modify and old ports-tree to >> get the new software in. I have at least two customer paying me for >> exact this work. But to be fair: it is no fun and harder with every >> new release :D >> >> I suppose what some customer need is an LTS version. Missing one is a >> show stopper for FreeBSD usage in many firms i talked to. I do not >> think this is a good idea from a technical point - but firms are slow >> and want stability. > > LTS of the base system or ports? The base system is already quite well > supported long-term. This is a very good question, because it is not that clear. But let me state right here: No, the base system has not a good long-term support! Yes, we have 2 years for the latest release, but 2 years seems to be very short for firms. Often they want 5 years. And you are forced to update. You can't stay on say 10.1 or 10.2 because the support will end 2016. Which is short, because 10.2 was released in august 2015. This is only one and a half year. Also on same points base system and ports are tied together. There were already changes in ports-tree which renders him unavailable for a older release just a couple of days after the version becomes unsupported. > In this particular case it's probably not ports per > se but more the package manager? Because ports are not really FreeBSD's, > they are separate applications, each one of which is supported as long > as its author is willing to do so. Yes - but the infrastructure changes. The ports are not really FreeBSD, the ports-tree is. > Unless you mean the model adopted by some Linux companies, namely taking > the ports tree, freezing applications at some specific versions, and > only apply security and critical bug fixes to those applications? That > would mean creating and maintaining sources for all applications listed > in ports, rather than the ports tree itself! And that would be quite a > task considering that many applications have multiple configurable > compilation options. Not sure if it would be worth the effort if most > companies only need a limited set of applications from the whole tree. > On the other hand, if that was done then you would be left with no work :) Like i said: LTS is not a good idea from a technical point. But a missing LTS version is a main problem when trying to convince firms to change to FreeBSD. Greetings, Torsten From owner-freebsd-ports@freebsd.org Tue May 31 13:59:31 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3174B543B2 for ; Tue, 31 May 2016 13:59:31 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from vm.unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6717E1175 for ; Tue, 31 May 2016 13:59:30 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from Vincents-MacBook-Pro-2.local (lon.namesco.net [195.7.254.102]) by vm.unsane.co.uk (Postfix) with ESMTPSA id ECF6230023 for ; Tue, 31 May 2016 14:59:29 +0100 (BST) Subject: Re: old ports/packages To: freebsd-ports@freebsd.org References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> From: Vincent Hoffman-Kazlauskas Message-ID: <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> Date: Tue, 31 May 2016 14:59:29 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2016 13:59:31 -0000 On 31/05/2016 14:17, Torsten Zuehlsdorff wrote: > On 04.05.2016 19:17, Grzegorz Junka wrote: > > Please excuse my late answer. I was right into vacation and need to > handle some work right afterwards. > >>>> What you cannot do is create old-style packages from a new ports >>>> tree. This is because the ports infrastructure has been changing >>>> since pkg_install was deprecated, and pkg_install simply will not >>>> work with the current ports tree (and, as I understand it, cannot >>>> practically be modified in order to work with it). >>> >>> You are mostly correct. It is possible to modify and old ports-tree to >>> get the new software in. I have at least two customer paying me for >>> exact this work. But to be fair: it is no fun and harder with every >>> new release :D >>> >>> I suppose what some customer need is an LTS version. Missing one is a >>> show stopper for FreeBSD usage in many firms i talked to. I do not >>> think this is a good idea from a technical point - but firms are slow >>> and want stability. >> >> LTS of the base system or ports? The base system is already quite well >> supported long-term. > > This is a very good question, because it is not that clear. But let me > state right here: No, the base system has not a good long-term support! > > Yes, we have 2 years for the latest release, but 2 years seems to be > very short for firms. Often they want 5 years. > > And you are forced to update. You can't stay on say 10.1 or 10.2 because > the support will end 2016. Which is short, because 10.2 was released in > august 2015. This is only one and a half year. To be fair the support is last release + 2 years, supporting a minor version for more than 2 years seems unreasonable, compare to say redhat a major commercial vendor. They provide up to 10 years sure but for a major version ie 6 not a minor version ie 6.1. In fact their policy page(1*) says "Under a Red Hat Enterprise Linux subscription, all available RHSAs and RHBAs are provided for the current active minor release until the availability of the next minor release" and that if you want a minor release supported for longer you pay more and even then its only approx 2 years, (example 6.7 (released 2015-07-22) ends July 31, 2017) So far for me updating freebsd minor releases has been much the same experience as upgrading Centos/RHEL minor releases. Vince (1*) https://access.redhat.com/support/policy/updates/errata#Extended_Update_Support > > Also on same points base system and ports are tied together. There were > already changes in ports-tree which renders him unavailable for a older > release just a couple of days after the version becomes unsupported. > >> In this particular case it's probably not ports per >> se but more the package manager? Because ports are not really FreeBSD's, >> they are separate applications, each one of which is supported as long >> as its author is willing to do so. > > Yes - but the infrastructure changes. The ports are not really FreeBSD, > the ports-tree is. > >> Unless you mean the model adopted by some Linux companies, namely taking >> the ports tree, freezing applications at some specific versions, and >> only apply security and critical bug fixes to those applications? That >> would mean creating and maintaining sources for all applications listed >> in ports, rather than the ports tree itself! And that would be quite a >> task considering that many applications have multiple configurable >> compilation options. Not sure if it would be worth the effort if most >> companies only need a limited set of applications from the whole tree. >> On the other hand, if that was done then you would be left with no >> work :) > > Like i said: LTS is not a good idea from a technical point. But a > missing LTS version is a main problem when trying to convince firms to > change to FreeBSD. > > Greetings, > Torsten > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-ports@freebsd.org Tue May 31 17:24:38 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE264B57637 for ; Tue, 31 May 2016 17:24:38 +0000 (UTC) (envelope-from alexhelenalex@rambler.ru) Received: from huan3.mail.rambler.ru (huan3.mail.rambler.ru [81.19.66.33]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AC8071D2E for ; Tue, 31 May 2016 17:24:38 +0000 (UTC) (envelope-from alexhelenalex@rambler.ru) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=rambler.ru; s=mail; h=Content-Type:MIME-Version:Date:Subject:To:From:Reply-To:Message-ID; bh=axY7+8cWkRw4mCO5DnVoSUTPCJ6ir/xZ+kJcTYN0P2g=; b=eb9Vu1QVHwxWI7sg4zs2R+saVcTBNR7ia/y/jNOwbAa6/2tAe6yzQ0fFyPZ8Q86MH2YNd8BVJpVzBnPulOxmDXpk2wm6xQLfuV1+fuwhWHNAimoe6282XhDhldznCAMQww7Oc7SuHDEMIGsap2sQqhh1DAb1thG0AZMog8xgICE=; Received: from [UNAVAILABLE] ([197.217.101.252]:6477 helo=yrw.net) by huan3.mail.rambler.ru with esmtpa (Exim 4.76) (envelope-from ) id 1b7nP7-0006XZ-08 for freebsd-ports@freebsd.org; Tue, 31 May 2016 20:24:36 +0300 Message-ID: <4AB0FCB5FD2907B4686D249ACEECFCC9@rambler.ru> Reply-To: =?koi8-r?Q?=F2=C5=CE=C1=D4=C1_=E2=C1=C2=C5=CE=CB=CF?= From: =?koi8-r?Q?=F2=C5=CE=C1=D4=C1_=E2=C1=C2=C5=CE=CB=CF?= To: Subject: =?koi8-r?Q?=F3a=CC=C0=D4!?= Date: Tue, 31 May 2016 21:25:46 +0400 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3528.331 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331 X-Rambler-User: alexhelenalex@rambler.ru/197.217.101.252 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2016 17:24:39 -0000 From owner-freebsd-ports@freebsd.org Wed Jun 1 09:07:59 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E865FB564BF for ; Wed, 1 Jun 2016 09:07:59 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from toco-domains.de (mail.toco-domains.de [176.9.39.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7A08B1BE8 for ; Wed, 1 Jun 2016 09:07:58 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id 35BF61AAF050; Wed, 1 Jun 2016 09:07:55 +0200 (CEST) Subject: Re: old ports/packages To: Vincent Hoffman-Kazlauskas , freebsd-ports@freebsd.org References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> From: Torsten Zuehlsdorff Message-ID: Date: Wed, 1 Jun 2016 11:07:55 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 09:08:00 -0000 On 31.05.2016 15:59, Vincent Hoffman-Kazlauskas wrote: >>>>> What you cannot do is create old-style packages from a new ports >>>>> tree. This is because the ports infrastructure has been changing >>>>> since pkg_install was deprecated, and pkg_install simply will not >>>>> work with the current ports tree (and, as I understand it, cannot >>>>> practically be modified in order to work with it). >>>> >>>> You are mostly correct. It is possible to modify and old ports-tree to >>>> get the new software in. I have at least two customer paying me for >>>> exact this work. But to be fair: it is no fun and harder with every >>>> new release :D >>>> >>>> I suppose what some customer need is an LTS version. Missing one is a >>>> show stopper for FreeBSD usage in many firms i talked to. I do not >>>> think this is a good idea from a technical point - but firms are slow >>>> and want stability. >>> >>> LTS of the base system or ports? The base system is already quite well >>> supported long-term. >> >> This is a very good question, because it is not that clear. But let me >> state right here: No, the base system has not a good long-term support! >> >> Yes, we have 2 years for the latest release, but 2 years seems to be >> very short for firms. Often they want 5 years. >> >> And you are forced to update. You can't stay on say 10.1 or 10.2 because >> the support will end 2016. Which is short, because 10.2 was released in >> august 2015. This is only one and a half year. > > > To be fair the support is last release + 2 years, supporting a minor > version for more than 2 years seems unreasonable, compare to say redhat > a major commercial vendor. If you want to be fair: this is not true. This would be true, if 10.1, 10.2 or 10.3 for example were minor-updates. But they were not. The "minor updates" needs installing thousands of patches, updating all your jails and sometimes all your ports too. It sometimes throw you out of your server, because an SSH-Update changed the config and no key will work anymore. In the last years i encounter a number of such unpleasant issues in such "minor updates". And if i calculate the time for such an "minor update" and hold it against the time needed for a "major update" there is nearly no difference. Same for occurred problems, needed changes, etc. There is just no difference between an update from for example 9.2 to 9.3 or 9.3 to 10.0. At least its the same. And therefore: no, there is no real long term supported. It is just stated, but in practice its like there is none. Maybe i just see this wrong. But than i need to adjust my arguments for a discussion. What to say when discussing if the OS should be FreeBSD or Ubuntu for example and somebody referrers to the 5 year LTS support of Ubuntu? Greetings, Torsten From owner-freebsd-ports@freebsd.org Wed Jun 1 12:19:03 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8AED6B60C05 for ; Wed, 1 Jun 2016 12:19:03 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4BEF11AB7 for ; Wed, 1 Jun 2016 12:19:02 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id ADC4728458; Wed, 1 Jun 2016 14:12:54 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id DB30E28455; Wed, 1 Jun 2016 14:12:52 +0200 (CEST) Message-ID: <574ED144.1050603@quip.cz> Date: Wed, 01 Jun 2016 14:12:52 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Torsten Zuehlsdorff , Vincent Hoffman-Kazlauskas , freebsd-ports@freebsd.org Subject: Re: old ports/packages References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 12:19:03 -0000 Torsten Zuehlsdorff wrote on 06/01/2016 11:07: > On 31.05.2016 15:59, Vincent Hoffman-Kazlauskas wrote: [...] >> To be fair the support is last release + 2 years, supporting a minor >> version for more than 2 years seems unreasonable, compare to say redhat >> a major commercial vendor. > > If you want to be fair: this is not true. This would be true, if 10.1, > 10.2 or 10.3 for example were minor-updates. But they were not. The > "minor updates" needs installing thousands of patches, updating all your > jails and sometimes all your ports too. It sometimes throw you out of > your server, because an SSH-Update changed the config and no key will > work anymore. In the last years i encounter a number of such unpleasant > issues in such "minor updates". Yes, there are issues with SSH config changes but I think they are not intended and was made by human errors. > And if i calculate the time for such an "minor update" and hold it > against the time needed for a "major update" there is nearly no > difference. Same for occurred problems, needed changes, etc. There is > just no difference between an update from for example 9.2 to 9.3 or 9.3 > to 10.0. At least its the same. There is a main difference - if you upgraded from 9.2 to 9.3, you don't need to recompile (reinstall) all ports, but if you upgraded from 9.3 to 10.x you need to reinstall all your packages and then remove old 9.x libraries from the base system. If I should count the number of problems with updates / upgrades, there are few of them with base system upgrades from 6.x - 8.x to 9.x to 10.1 to 10.2 to 10.3 (yes we run machines originally installed as 6.x now running 10.3 with many intermediate upgrades) but there are really many of them with ports / packages. Ports are moving target and you need to upgrade them more often because of security related fixes in newer versions. So even if FreeBSD releases will have 5 years of security patches support, our main work time will still be spent with upgrading packages and solving problems with versions & config changes for each package. Miroslav Lachman From owner-freebsd-ports@freebsd.org Wed Jun 1 13:47:03 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3534FB608BD for ; Wed, 1 Jun 2016 13:47:03 +0000 (UTC) (envelope-from rs+freebsd-ports@trust64.com) Received: from t64ammx01.trust64.com (t64ammx01.trust64.com [54.93.84.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F14391C05 for ; Wed, 1 Jun 2016 13:47:02 +0000 (UTC) (envelope-from rs+freebsd-ports@trust64.com) Received: from [192.168.3.25] (37-128-172-130.bp-lan.es [37.128.172.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by t64ammx01.trust64.com (Postfix) with ESMTPSA id D9374B0D0B for ; Wed, 1 Jun 2016 15:59:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=trust64.com; s=20150428; t=1464789552; bh=pqrGAST4KgnNS/CKQQHQuvKiG0eZX77EObwWyoeOfU8=; h=To:Reply-To:From:Subject:Date:From; b=u62byahD6RffH/7tifdrHq2KdlvtSBstgvlsrT72pg4149JI4oslLy4Svjl6HC/kH WLMikemtQcUhtDSa9BNZUrmwbOMJKRCADF4iG3kYk0ph8nuHepjTdkc3cLvz+Gp0Kf cqEc/ZwQwzdEBEH+LKRXqFzr3TB92149mmor5N50= To: freebsd-ports@freebsd.org Reply-To: rs+freebsd-ports@trust64.com From: rs Subject: Zimbra Port Message-ID: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> Date: Wed, 1 Jun 2016 15:47:00 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 13:47:03 -0000 Hello List, I am trying to create a port of the zimbra collaboration suite. I am in contact with upstream and they are actively helping in making a port happen. It would be my first FreeBSD port (although I have a lot of linux knowledge and know how to create packages for .deb). My first steps involve right now making everything compile (Zimbra includes *a lot* of libraries themselves instead of relying on the OS to provide them). I have a couple of questions though: * Zimbra expects itself to be installed to /opt/zimbra. It is not easy to change that, /opt/zimbra is hardcoded in a lot of places. Its a longterm goal of mine to help clean that up, but it is not possible right now. Are there any problems with a package which installs to /opt? * The Zimbra source is huge, a git clone is about 13 GigaBytes. I am not sure on how source that big is handled correctly in ports. (e.g. is it OK that every make does a git clone and you have to wait until you get the 13 GB of data? Would this be a problem for the FreeBSD build cluster infrastructure to create the packages?, ...) * On the porters handbook it says to fetch a tarball from http/ftp, is it also possible to directly work with git and clone a repository? This is the right place to get help started in porting? FreeBSD has so much mailing lists :-) Thank you, Best RAy From owner-freebsd-ports@freebsd.org Wed Jun 1 14:01:22 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD693B60DFD for ; Wed, 1 Jun 2016 14:01:22 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7444113A0 for ; Wed, 1 Jun 2016 14:01:22 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1b86i0-000AJp-SK; Wed, 01 Jun 2016 16:01:20 +0200 Date: Wed, 1 Jun 2016 16:01:20 +0200 From: Kurt Jaeger To: rs Cc: freebsd-ports@freebsd.org Subject: Re: Zimbra Port Message-ID: <20160601140120.GA41922@home.opsec.eu> References: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 14:01:22 -0000 Hi! > I am trying to create a port of the zimbra collaboration suite. I am in > contact with upstream and they are actively helping in making a port > happen. Thank you for that. This can be an important application in the ports tree. > * Zimbra expects itself to be installed to /opt/zimbra. It is not easy > to change that, /opt/zimbra is hardcoded in a lot of places. Its a > longterm goal of mine to help clean that up, but it is not possible > right now. Are there any problems with a package which installs to /opt? It's uncommon and there are no other ports doing this. To get it to build it's OK, but in the long run, this has to adapt. > * The Zimbra source is huge, a git clone is about 13 GigaBytes. I am not > sure on how source that big is handled correctly in ports. >From what I know, this is approx. one magnitude (10x) larger than anything else. > (e.g. is it > OK that every make does a git clone and you have to wait until you get > the 13 GB of data? A make that does a git clone is probably a bad idea, the ports framework has no hooks for that, as far as I understand. Is there any kind of release process ? Some sort of code modularisation ? > Would this be a problem for the FreeBSD build cluster > infrastructure to create the packages?, ...) It would be a challenge, yes. > * On the porters handbook it says to fetch a tarball from http/ftp, is > it also possible to directly work with git and clone a repository? I've not found a port that does a git clone, so I think putting some git clone somewhere as a .tgz would be a easier start. > This is the right place to get help started in porting? FreeBSD has so > much mailing lists :-) Yes, it is. But I can tell you, this is a huge task! -- pi@opsec.eu +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Wed Jun 1 14:08:35 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 863A8B4F064 for ; Wed, 1 Jun 2016 14:08:35 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from toco-domains.de (mail.toco-domains.de [176.9.39.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 51BE71CDD for ; Wed, 1 Jun 2016 14:08:34 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id 39B551AAF050; Wed, 1 Jun 2016 14:08:26 +0200 (CEST) Subject: Re: Zimbra Port To: rs+freebsd-ports@trust64.com, freebsd-ports@freebsd.org References: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> From: Torsten Zuehlsdorff Message-ID: Date: Wed, 1 Jun 2016 16:08:26 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 14:08:35 -0000 Hello Ray, > I am trying to create a port of the zimbra collaboration suite. I am in > contact with upstream and they are actively helping in making a port > happen. That is really create. I wanted to start a Zimbra port myself, but was stuck with GitLab (and a bunch of others...) :D > I have a couple of questions though: > > * Zimbra expects itself to be installed to /opt/zimbra. It is not easy > to change that, /opt/zimbra is hardcoded in a lot of places. Its a > longterm goal of mine to help clean that up, but it is not possible > right now. Are there any problems with a package which installs to /opt? Normally we just change the pathes of such ports. > * The Zimbra source is huge, a git clone is about 13 GigaBytes. I am not > sure on how source that big is handled correctly in ports. (e.g. is it > OK that every make does a git clone and you have to wait until you get > the 13 GB of data? Would this be a problem for the FreeBSD build cluster > infrastructure to create the packages?, ...) A git clone contains the complete development *history*. If a try to fetch a packet from their homepage it is "just" around 850 MB which should not be a problem. > * On the porters handbook it says to fetch a tarball from http/ftp, is > it also possible to directly work with git and clone a repository? I'm not aware of such a way. But since there is a Git-Repo: isn't there a management tool like GitLab, which could provides tarballs? At least it is possible to set one up, clone the repo and provide it this way. > This is the right place to get help started in porting? FreeBSD has so > much mailing lists :-) Yes, this is the right place. Feel free to contact me, i would gladly help (but need to finish some more stuff before). Greetings, Torsten From owner-freebsd-ports@freebsd.org Wed Jun 1 14:19:59 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49A59B4F547 for ; Wed, 1 Jun 2016 14:19:59 +0000 (UTC) (envelope-from jim@ohlste.in) Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0D1A91892 for ; Wed, 1 Jun 2016 14:19:59 +0000 (UTC) (envelope-from jim@ohlste.in) Received: by mail-qk0-x234.google.com with SMTP id n63so15445431qkf.0 for ; Wed, 01 Jun 2016 07:19:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ohlste-in.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=3BZjZl9QqfgTmb2sZ0qL+RK5c6F4KEuKkm6ui4Cvcw4=; b=cknVrIlRa3sQffs6FBU3irEd1Ly/c7ZLI7AurqmEkTHcGzYalqXWOufHDM2HYHQC4T mGO5eu09Z1/VLQqgGHVomhwQU9nS8QlsPbWqqqlUFAQ27iv1e0GE8x0DAPzxynhEYP8I Vv3ajWjUWmxNbqH68xMxtshVtW74pX12kcnBx7QhPZhi4RaCOloerLfUxcm30ykwfiPY gcymaWzh7nb/+7u6qc+wuT66FvZ84b9DomYbKPgtvjnsBzlHC2S2LvdZPyjArP7uNkVL qlABzpR7HsiATAvc16bwuzJm5fUBxeZirT4L6n+3ZoZSCYQmwKCk/LHWqlZ0y1/NTZqr 9NrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=3BZjZl9QqfgTmb2sZ0qL+RK5c6F4KEuKkm6ui4Cvcw4=; b=LYBnrzdBCDwKrUaXKpY3ORAayxMsn7OxtzGIQTQaosm1BHpXS6jTqV0uD8gvElK4rW wo/EakT+fbR9ge/v2nSCKJb34bRyFR6EWQCDdyw71Cj5wgUArx/CmuJAv7KRW6XCsaOM qqO8QVnhaTUvY7vUtWdPQSk4qfJWkBp95QKD6LdkXGoKuGNreMcWlJUzg0q2UKwBGu/t YQ637/LkV1unofcwHhYuTqB9XGDRcvXbbITlFdizbQ4HBCwWOzNhWrCpqaUcM4J8HNAU MUjdPiDhTCxPGE6VUzATis52R2qanxQjR/hddqrsz+YO+pcVzslYVBggPplK8y6f8r1T 84og== X-Gm-Message-State: ALyK8tJ47I9oJ6Yzoul6j8KaNsiQjRORisG8xSvW848Q0nLQpZxvSJ2neA16RM2uczJvRA== X-Received: by 10.55.161.204 with SMTP id k195mr7174962qke.193.1464790798062; Wed, 01 Jun 2016 07:19:58 -0700 (PDT) Received: from [192.168.1.13] (pool-96-249-243-37.nrflva.fios.verizon.net. [96.249.243.37]) by smtp.gmail.com with ESMTPSA id y140sm1824414qky.19.2016.06.01.07.19.57 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 01 Jun 2016 07:19:57 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Zimbra Port From: Jim Ohlstein X-Mailer: iPhone Mail (13F69) In-Reply-To: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> Date: Wed, 1 Jun 2016 10:19:56 -0400 Cc: freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <9F871A7D-1A54-495D-B9E4-5056F2EECB91@ohlste.in> References: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> To: rs+freebsd-ports@trust64.com X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 14:19:59 -0000 Sorry for the top post.=20 We use Zimbra on an Ubuntu LTS VM with storage via iSCSI.=20 Given the magnitude, I honestly don't think ports or packages is really the w= ay to go. I believe that most people use a dedicated (to Zimbra) server or V= M.=20 If I were to approach this project, I'd do it outside of ports, maybe on git= hub, or possibly as a VM image.=20 That's not to say it can't be done, rather that a project of this size requi= res a layout that is not native to FreeBSD ports, and it's so massive with s= o many moving parts, having to comply with the ports infrastructure, and to m= aintain it, is probably far more effort than it's worth.=20 Jim Ohlstein > On Jun 1, 2016, at 9:47 AM, rs wrote: >=20 > Hello List, >=20 > I am trying to create a port of the zimbra collaboration suite. I am in co= ntact with upstream and they are actively helping in making a port happen. >=20 > It would be my first FreeBSD port (although I have a lot of linux knowledg= e and know how to create packages for .deb). >=20 > My first steps involve right now making everything compile (Zimbra include= s *a lot* of libraries themselves instead of relying on the OS to provide th= em). >=20 > I have a couple of questions though: >=20 > * Zimbra expects itself to be installed to /opt/zimbra. It is not easy to c= hange that, /opt/zimbra is hardcoded in a lot of places. Its a longterm goal= of mine to help clean that up, but it is not possible right now. Are there a= ny problems with a package which installs to /opt? >=20 > * The Zimbra source is huge, a git clone is about 13 GigaBytes. I am not s= ure on how source that big is handled correctly in ports. (e.g. is it OK tha= t every make does a git clone and you have to wait until you get the 13 GB o= f data? Would this be a problem for the FreeBSD build cluster infrastructure= to create the packages?, ...) >=20 > * On the porters handbook it says to fetch a tarball from http/ftp, is it a= lso possible to directly work with git and clone a repository? >=20 > This is the right place to get help started in porting? FreeBSD has so muc= h mailing lists :-) >=20 > Thank you, > Best > RAy > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Wed Jun 1 14:30:30 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51FB4B4FA58 for ; Wed, 1 Jun 2016 14:30:30 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 181661158 for ; Wed, 1 Jun 2016 14:30:29 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 0841428433; Wed, 1 Jun 2016 16:30:26 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 502FC2842F; Wed, 1 Jun 2016 16:30:25 +0200 (CEST) Message-ID: <574EF181.3050207@quip.cz> Date: Wed, 01 Jun 2016 16:30:25 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: rs+freebsd-ports@trust64.com, freebsd-ports@freebsd.org Subject: Re: Zimbra Port References: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> In-Reply-To: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 14:30:30 -0000 rs wrote on 06/01/2016 15:47: > Hello List, > > I am trying to create a port of the zimbra collaboration suite. I am in > contact with upstream and they are actively helping in making a port > happen. > > It would be my first FreeBSD port (although I have a lot of linux > knowledge and know how to create packages for .deb). I wish you a good luck with porting this beast! There were a couple of attempts to do this in the past but none succeeded. You can search the Zimbra and FreeBSD websites (forums). Anyway - it would be nice to have in working on top of FreeBSD with upstream support! Miroslav Lachman From owner-freebsd-ports@freebsd.org Wed Jun 1 14:33:22 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C2E7B4FCF2 for ; Wed, 1 Jun 2016 14:33:22 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from toco-domains.de (mail.toco-domains.de [176.9.39.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 66D33178A for ; Wed, 1 Jun 2016 14:33:22 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id 7B98B1AAF050; Wed, 1 Jun 2016 14:33:19 +0200 (CEST) Subject: Re: Zimbra Port To: Miroslav Lachman <000.fbsd@quip.cz>, rs+freebsd-ports@trust64.com, freebsd-ports@freebsd.org References: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> <574EF181.3050207@quip.cz> From: Torsten Zuehlsdorff Message-ID: <2f2765ab-59cc-8045-29e4-cb02e9976e28@toco-domains.de> Date: Wed, 1 Jun 2016 16:33:20 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <574EF181.3050207@quip.cz> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 14:33:22 -0000 On 01.06.2016 16:30, Miroslav Lachman wrote: > rs wrote on 06/01/2016 15:47: >> Hello List, >> >> I am trying to create a port of the zimbra collaboration suite. I am in >> contact with upstream and they are actively helping in making a port >> happen. >> >> It would be my first FreeBSD port (although I have a lot of linux >> knowledge and know how to create packages for .deb). > > I wish you a good luck with porting this beast! There were a couple of > attempts to do this in the past but none succeeded. You can search the > Zimbra and FreeBSD websites (forums). Hey - this was the same for GitLab. Sometimes i wish there is a funding for projects like this ;) Greetings, Torsten From owner-freebsd-ports@freebsd.org Wed Jun 1 15:31:18 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C48AFB61526 for ; Wed, 1 Jun 2016 15:31:18 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Received: from www94.your-server.de (www94.your-server.de [213.133.104.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8E8581269 for ; Wed, 1 Jun 2016 15:31:18 +0000 (UTC) (envelope-from Mathias.Picker@virtual-earth.de) Received: from [109.43.0.90] (helo=[100.81.250.60]) by www94.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.85_2) (envelope-from ) id 1b87g8-0003PI-5T; Wed, 01 Jun 2016 17:03:28 +0200 User-Agent: K-9 Mail for Android In-Reply-To: <9F871A7D-1A54-495D-B9E4-5056F2EECB91@ohlste.in> References: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> <9F871A7D-1A54-495D-B9E4-5056F2EECB91@ohlste.in> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: Zimbra Port From: Mathias Picker Date: Wed, 01 Jun 2016 17:03:19 +0200 To: Jim Ohlstein ,rs+freebsd-ports@trust64.com CC: freebsd-ports@freebsd.org Message-ID: <32E845C9-3FB8-4325-9C63-8E213DEA707F@virtual-earth.de> X-Authenticated-Sender: Mathias.Picker@virtual-earth.de X-Virus-Scanned: Clear (ClamAV 0.99/21651/Wed Jun 1 15:27:16 2016) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 15:31:18 -0000 Am 1. Juni 2016 16:19:56 MESZ, schrieb Jim Ohlstein : >Sorry for the top post. > >We use Zimbra on an Ubuntu LTS VM with storage via iSCSI. > >Given the magnitude, I honestly don't think ports or packages is really >the way to go. I believe that most people use a dedicated (to Zimbra) >server or VM. I second this. There allready is a version of zimbra on FreeBSD and it's intentionally not a real port https://wiki.zimbra.com/wiki/Zimbra_on_FreeBSD I used to use this, but I'm now running a CentOS instance just for zimbra. And I don't think zimbra outside of /opt is ever going to happen, it's coded into too many places. You might want to rethink this… Cheers, Mathias > >If I were to approach this project, I'd do it outside of ports, maybe >on github, or possibly as a VM image. > >That's not to say it can't be done, rather that a project of this size >requires a layout that is not native to FreeBSD ports, and it's so >massive with so many moving parts, having to comply with the ports >infrastructure, and to maintain it, is probably far more effort than >it's worth. > >Jim Ohlstein >> On Jun 1, 2016, at 9:47 AM, rs wrote: >> >> Hello List, >> >> I am trying to create a port of the zimbra collaboration suite. I am >in contact with upstream and they are actively helping in making a port >happen. >> >> It would be my first FreeBSD port (although I have a lot of linux >knowledge and know how to create packages for .deb). >> >> My first steps involve right now making everything compile (Zimbra >includes *a lot* of libraries themselves instead of relying on the OS >to provide them). >> >> I have a couple of questions though: >> >> * Zimbra expects itself to be installed to /opt/zimbra. It is not >easy to change that, /opt/zimbra is hardcoded in a lot of places. Its a >longterm goal of mine to help clean that up, but it is not possible >right now. Are there any problems with a package which installs to >/opt? >> >> * The Zimbra source is huge, a git clone is about 13 GigaBytes. I am >not sure on how source that big is handled correctly in ports. (e.g. is >it OK that every make does a git clone and you have to wait until you >get the 13 GB of data? Would this be a problem for the FreeBSD build >cluster infrastructure to create the packages?, ...) >> >> * On the porters handbook it says to fetch a tarball from http/ftp, >is it also possible to directly work with git and clone a repository? >> >> This is the right place to get help started in porting? FreeBSD has >so much mailing lists :-) >> >> Thank you, >> Best >> RAy >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to >"freebsd-ports-unsubscribe@freebsd.org" >_______________________________________________ >freebsd-ports@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-ports >To unsubscribe, send any mail to >"freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Wed Jun 1 16:27:54 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81FF6B6192F for ; Wed, 1 Jun 2016 16:27:54 +0000 (UTC) (envelope-from marquis@roble.com) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 74ECA1893 for ; Wed, 1 Jun 2016 16:27:54 +0000 (UTC) (envelope-from marquis@roble.com) Date: Wed, 1 Jun 2016 09:27:53 -0700 (PDT) From: Roger Marquis To: freebsd-ports@freebsd.org Subject: Re: old ports/packages In-Reply-To: <574ED144.1050603@quip.cz> References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 16:27:54 -0000 > To be fair the support is last release + 2 years, supporting a minor > version for more than 2 years seems unreasonable, compare to say redhat > a major commercial vendor. You can't really compare FreeBSD to a Redhat or Ubuntu LTS in this way because ports generally continue to be upgradeable after a bsd release has been EOL'd. That contrasts with Linux in so far as application versions are frozen _on_release_ rather than on EOL i.e., the apache httpd version you installed when 6 or 14.04 first came out is typically the apache httpd version you're stuck with until the system is upgraded to the next major LTS version (except for security backports). Freebsd's monolithic base is another matter and has been a red-flag at many organizations. Having endured 'buildworld; buildkernel; installkernal; reboot' and 'installworld; mergemaster' over the past few weeks I can say without exaggeration it is an order of magnitude more time consuming that 'yum update' or 'aptitude upgrade'. Many of us are eagerly await base packages to fix this bad situation AND enable an LTS model that is superior those in Linux (or any other OS for that matter). IMO, Roger From owner-freebsd-ports@freebsd.org Wed Jun 1 16:39:34 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8DCF7B61C4B for ; Wed, 1 Jun 2016 16:39:34 +0000 (UTC) (envelope-from rs+freebsd-ports@trust64.com) Received: from t64ammx01.trust64.com (t64ammx01.trust64.com [54.93.84.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2265C10EF for ; Wed, 1 Jun 2016 16:39:33 +0000 (UTC) (envelope-from rs+freebsd-ports@trust64.com) Received: from [192.168.3.25] (37-128-172-130.bp-lan.es [37.128.172.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by t64ammx01.trust64.com (Postfix) with ESMTPSA id 2B6EEB05D4; Wed, 1 Jun 2016 18:51:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=trust64.com; s=20150428; t=1464799903; bh=TMomzo8kpc/3uvwaeAaNQJ/qMv5OBbyCoK7HxHx7hVI=; h=Reply-To:Subject:References:To:Cc:From:Date:In-Reply-To:From; b=7RgVQ5z9eTzUsFPzym2/wURuaf8LkpHf2HhgP2JKxS+lvnYC4kQXoLDVEKAUOVpl/ qaIh6nJ/hBD8V0UXl7lSUmgajAkeD30On7GjKsF8gPMssBB41llQ79whLdam+f8/PO iuF8NzIzRBqDoAGoo53xCDffPfj4D+hHgDozhceg= Reply-To: rs+freebsd-ports@trust64.com Subject: Re: Zimbra Port References: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> <9F871A7D-1A54-495D-B9E4-5056F2EECB91@ohlste.in> To: Jim Ohlstein Cc: freebsd-ports@freebsd.org From: rs Message-ID: <247a148e-feb9-014c-429f-c9b7314315f9@trust64.com> Date: Wed, 1 Jun 2016 18:39:31 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <9F871A7D-1A54-495D-B9E4-5056F2EECB91@ohlste.in> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 16:39:34 -0000 Hi Jim, I never would have thought of taking upon such a huge project alone, but Zimbra is reaching out and they actively want Zimbra supported on FreeBSD (at least Zimbra-FOSS) and I can count on their help. Also they are restructuring their components because they want zimbra to be included in other repositories also (Ubuntu, Debian, RPM based, etc.). So with the help of Zimbra it may not be an impossible task. Best Ray On 06/01/16 16:19, Jim Ohlstein wrote: > Sorry for the top post. > > We use Zimbra on an Ubuntu LTS VM with storage via iSCSI. > > Given the magnitude, I honestly don't think ports or packages is really the way to go. I believe that most people use a dedicated (to Zimbra) server or VM. > > If I were to approach this project, I'd do it outside of ports, maybe on github, or possibly as a VM image. > > That's not to say it can't be done, rather that a project of this size requires a layout that is not native to FreeBSD ports, and it's so massive with so many moving parts, having to comply with the ports infrastructure, and to maintain it, is probably far more effort than it's worth. > > Jim Ohlstein >> On Jun 1, 2016, at 9:47 AM, rs wrote: >> >> Hello List, >> >> I am trying to create a port of the zimbra collaboration suite. I am in contact with upstream and they are actively helping in making a port happen. >> >> It would be my first FreeBSD port (although I have a lot of linux knowledge and know how to create packages for .deb). >> >> My first steps involve right now making everything compile (Zimbra includes *a lot* of libraries themselves instead of relying on the OS to provide them). >> >> I have a couple of questions though: >> >> * Zimbra expects itself to be installed to /opt/zimbra. It is not easy to change that, /opt/zimbra is hardcoded in a lot of places. Its a longterm goal of mine to help clean that up, but it is not possible right now. Are there any problems with a package which installs to /opt? >> >> * The Zimbra source is huge, a git clone is about 13 GigaBytes. I am not sure on how source that big is handled correctly in ports. (e.g. is it OK that every make does a git clone and you have to wait until you get the 13 GB of data? Would this be a problem for the FreeBSD build cluster infrastructure to create the packages?, ...) >> >> * On the porters handbook it says to fetch a tarball from http/ftp, is it also possible to directly work with git and clone a repository? >> >> This is the right place to get help started in porting? FreeBSD has so much mailing lists :-) >> >> Thank you, >> Best >> RAy >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Wed Jun 1 19:13:22 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2383B61B38 for ; Wed, 1 Jun 2016 19:13:22 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from mail.abinet.ru (mail.abinet.ru [136.243.72.227]) by mx1.freebsd.org (Postfix) with ESMTP id BF7831C50 for ; Wed, 1 Jun 2016 19:13:22 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from [10.0.0.1] (unknown [10.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.abinet.ru (Postfix) with ESMTPSA id 320851B755 for ; Wed, 1 Jun 2016 19:05:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=abinet.ru; s=dkim; t=1464807906; bh=0NT+NnweU5nPK6iwjUs6qdNTF4VuJT3IlxPJ///3kdY=; h=Date:From:To:Subject; b=Ntra8IIoLAPJuXf4fcjTvXQx/U2g4gxwLN8h+DFDReK4sqzcnFcLKZS42O498rCFE ejBzf2C+n8z1iSKB2FlBf/voZal0+y2ypKA67duQ0UJDcqw0FbK/odGU/Q484JMKZO OVESik6np0eebl6ozQNoc5Az6U1BikgFFdk41BSA= Message-ID: <574F31E1.3040806@abinet.ru> Date: Wed, 01 Jun 2016 22:05:05 +0300 From: abi User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:) Gecko/20160112 FossaMail/25.2.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Zoneminder - call for testers Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 19:13:23 -0000 Hello. I'm updating the ZoneMinder security camera solution (http://www.freshports.org/multimedia/zoneminder/). Developers made huge efforts to make it compatible with FreeBSD. As this is my first attempt, can you look into it before I open a PR ? :) https://github.com/abishai/Zoneminder-port https://github.com/abishai/Zoneminder-port/archive/master.zip Thanks! From owner-freebsd-ports@freebsd.org Wed Jun 1 19:27:24 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE0A1B61F2B for ; Wed, 1 Jun 2016 19:27:24 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 90503113A for ; Wed, 1 Jun 2016 19:27:24 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1b8Bnb-000AqM-FJ; Wed, 01 Jun 2016 21:27:27 +0200 Date: Wed, 1 Jun 2016 21:27:27 +0200 From: Kurt Jaeger To: abi Cc: freebsd-ports@freebsd.org Subject: Re: Zoneminder - call for testers Message-ID: <20160601192727.GD41922@home.opsec.eu> References: <574F31E1.3040806@abinet.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <574F31E1.3040806@abinet.ru> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 19:27:24 -0000 Hi! > I'm updating the ZoneMinder security camera solution > (http://www.freshports.org/multimedia/zoneminder/). Developers made huge > efforts to make it compatible with FreeBSD. > > As this is my first attempt, can you look into it before I open a PR ? :) It looks promising, but there's this cmake error coming up during the configure phase: -- Looking for mysql/mysql.h - not found CMake Error at CMakeLists.txt:396 (message): ZoneMinder requires MySQL headers - check that MySQL development packages are installed I do have mysql 5.7.12 installed, the file is in /usr/local/include/mysql/mysql.h Any idea how to allow cmake to find it ? Btw, I suggest you check the port with portlint -AC, as well. -- pi@opsec.eu +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Wed Jun 1 21:36:18 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7396B61273 for ; Wed, 1 Jun 2016 21:36:18 +0000 (UTC) (envelope-from rollingbits@gmail.com) Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A48B21EF9 for ; Wed, 1 Jun 2016 21:36:18 +0000 (UTC) (envelope-from rollingbits@gmail.com) Received: by mail-it0-x229.google.com with SMTP id i127so35355243ita.1 for ; Wed, 01 Jun 2016 14:36:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=tyQUU8mU6JiKOdEyL0AJKc/NjBImSlYcddDyiAp7DsA=; b=UUUqphs0jvVtuTM3czjY38tXnxesjL6cKCCyGtwgcfor8o4vZumXDow5YnxXfGZJnT KyK8ayHa3TNA/kars1CZn0gMI/6kxig7mrHLojFp0vyDr5VIHMEHZuEfbtWV0KFljvC6 dybqaaJ0NcGSDfZXsK6cz6MHcJXy2wQRuU65jHTE/ODLbOtMRPOar3zOPO0i5uoHzVD8 Ub39JeXsvHQU0oQArRrPkuBCfaOa0pR64H5bkCnhF/Mj0oHtzQ+8pg744pJb06wtZ0V2 k+hynl9sfUMNKDGl+OohVza649/HjThhFGOMof4ZjTb9ka4yLMESDhFSjhR1lANHlFWJ 1d2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=tyQUU8mU6JiKOdEyL0AJKc/NjBImSlYcddDyiAp7DsA=; b=E8rhrRVQf2Xq4DY2QJjAk7L+DLD4yxgp7CVlpiqsGfvHJTFcOqckdgm1MF0OwXytBT 63riZW5UegfvlTzLCeklf1Re7+uuAcbKH5WFFIqj/HVRjgdC5S1qDKYUH84QVYrAgai7 p/+GnDx4wd5Y6dDWws3NeChS69cM0imIAwex8PtPemWpgNWxyl5mKnQr/KkV+k6k6ZeU OwZhCWTII4W4I0zIsus7SWFu4clw/os0FY1UHhrtFfxlFpSYJoZJ6Wpe+GwfiARL+ZD/ M12916fYwWtnY1X36RAwWFmreRSQRi5qpNiJubvygdfDjvBMzg/EE3W9G1OJOGq+IhrW L10Q== X-Gm-Message-State: ALyK8tI+n7S2a5OkStPW/tBnXqpGd7rPxAPx+fRt9hSgBZYv/0k5ehNn+XWStxP6lwn+fcYfXYsE3FXNEyCZRg== MIME-Version: 1.0 X-Received: by 10.36.104.132 with SMTP id v126mr135772itb.17.1464816978097; Wed, 01 Jun 2016 14:36:18 -0700 (PDT) Received: by 10.79.31.69 with HTTP; Wed, 1 Jun 2016 14:36:17 -0700 (PDT) Received: by 10.79.31.69 with HTTP; Wed, 1 Jun 2016 14:36:17 -0700 (PDT) Date: Wed, 1 Jun 2016 18:36:17 -0300 Message-ID: Subject: pkg regressions and/or missing documentation From: "rollingbits (Lucas)" To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 21:36:18 -0000 Hi. I've a local package repository which I could access using pkg with the ssh scheme until the last update. I update the packages once a week. pkg went from 1.7.2 to 1.8.3 here. The error message is that repository has the wrong URL scheme. I think there was a regression or missing documentation in this case. This update came together with new db6 which required recompilation of dependant ports. After all finished, svn didn't work because portmaster "forgot" to follow all the dependency chain of db6. As portmaster wasn't updated, I think the fault is on another regression of pkg, then. While on here, I remember that I've to manually edit pkg database some times and my pkg was never happy if I forgot to recreate all the packages every time. So these are issues that could be investigated, too. I think the last one is related to the format of pkg packages. Last, I think that I've to inform that in this set of problems also have the fact I discovered that my machines got compromissed. I've a lot of things to do and will not be able to help much more soon. I wished I've patches but I don't have. Thanks for the attention, Lc -- rollingbits -- rollingbits@gmail.com, rollingbits@terra.com.br rollingbits@yahoo.com, rollingbits@globo.com From owner-freebsd-ports@freebsd.org Thu Jun 2 07:19:22 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84124B63F0A for ; Thu, 2 Jun 2016 07:19:22 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from toco-domains.de (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 50F341149 for ; Thu, 2 Jun 2016 07:19:22 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id 4200A1AAF051; Thu, 2 Jun 2016 07:19:19 +0200 (CEST) Subject: Re: Zimbra Port To: "Bradley T. Hughes" References: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> Cc: rs+freebsd-ports@trust64.com, freebsd-ports@freebsd.org From: Torsten Zuehlsdorff Message-ID: Date: Thu, 2 Jun 2016 09:19:19 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 07:19:22 -0000 On 02.06.2016 07:41, Bradley T. Hughes wrote: > >> On 01 Jun 2016, at 16:08, Torsten Zuehlsdorff wrote: >> >>> * The Zimbra source is huge, a git clone is about 13 GigaBytes. I am not >>> sure on how source that big is handled correctly in ports. (e.g. is it >>> OK that every make does a git clone and you have to wait until you get >>> the 13 GB of data? Would this be a problem for the FreeBSD build cluster >>> infrastructure to create the packages?, ...) >> >> A git clone contains the complete development *history*. If a try to fetch a packet from their homepage it is "just" around 850 MB which should not be a problem. >> >>> * On the porters handbook it says to fetch a tarball from http/ftp, is >>> it also possible to directly work with git and clone a repository? >> >> I'm not aware of such a way. But since there is a Git-Repo: isn't there a management tool like GitLab, which could provides tarballs? At least it is possible to set one up, clone the repo and provide it this way. > > There's also the --depth option to git clone that can help limit the size of the resulting checkout. > > --depth > Create a shallow clone with a history truncated to the specified > number of commits. Implies --single-branch unless > --no-single-branch is given to fetch the histories near the tips of > all branches. Yes, but i doubt this could be a solution. The ports ship a distinfo file, which contains size and checksum of the distfiles for the port. This is not possible with a pure git. But since this is open source: in the worst case we can create the distfiles by ourself and host them. I don't see this as stopper. Greetings, Torsten From owner-freebsd-ports@freebsd.org Thu Jun 2 05:41:42 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C7E7B6303A for ; Thu, 2 Jun 2016 05:41:42 +0000 (UTC) (envelope-from bradleythughes@fastmail.fm) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 432911200 for ; Thu, 2 Jun 2016 05:41:42 +0000 (UTC) (envelope-from bradleythughes@fastmail.fm) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id D73C621236; Thu, 2 Jun 2016 01:41:40 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 02 Jun 2016 01:41:40 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=k2kcQPPIcE2NTUPH6UYNRwakQhc=; b=Gs7qZX fmy1t9/+Z+OVOnAQpjlthn7rAl/r2bWIF6ZBq6l6v/caFnMQTGBYTN5NCpLB/qER cabXbFD4oKJnkNr55w7X+bN2tZ8kHw4S53rEx6bFR/mwaeDvQyZ94dQXxnG7ORf4 aXXoDdHAUyi0ap4sCBUW2KiGqIMmoZg2fKTwE= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=k2kcQPPIcE2NTUP H6UYNRwakQhc=; b=thrdwywYR/1YPRqF8NM/hnHeTajjaSKJpFfutJTrsCCeaTR FKvC+Qik919bT7Gm5cnz2dy2melmNz9304Y+GDcO0WLiRe2pu4XOWdixkHXwZr7r D4xmtIFIe5YWm5OGDUY28pzpKYx1abMHqXCM/b9HmfuhXKkRatsN8aqQv4xA= X-Sasl-enc: S247TaWJhAoFRA/irx0GW9oeTtd6utqU6dPzJkXMrZce 1464846100 Received: from [192.168.0.62] (ip84-247-143-250.breiband.no [84.247.143.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 1C46FCCD9A; Thu, 2 Jun 2016 01:41:39 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Zimbra Port From: "Bradley T. Hughes" In-Reply-To: Date: Thu, 2 Jun 2016 07:41:39 +0200 Cc: rs+freebsd-ports@trust64.com, freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> To: Torsten Zuehlsdorff X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 05:41:42 -0000 > On 01 Jun 2016, at 16:08, Torsten Zuehlsdorff = wrote: >=20 >> * The Zimbra source is huge, a git clone is about 13 GigaBytes. I am = not >> sure on how source that big is handled correctly in ports. (e.g. is = it >> OK that every make does a git clone and you have to wait until you = get >> the 13 GB of data? Would this be a problem for the FreeBSD build = cluster >> infrastructure to create the packages?, ...) >=20 > A git clone contains the complete development *history*. If a try to = fetch a packet from their homepage it is "just" around 850 MB which = should not be a problem. >=20 >> * On the porters handbook it says to fetch a tarball from http/ftp, = is >> it also possible to directly work with git and clone a repository? >=20 > I'm not aware of such a way. But since there is a Git-Repo: isn't = there a management tool like GitLab, which could provides tarballs? At = least it is possible to set one up, clone the repo and provide it this = way. There's also the --depth option to git clone that can help limit the = size of the resulting checkout. --depth Create a shallow clone with a history truncated to the = specified number of commits. Implies --single-branch unless --no-single-branch is given to fetch the histories near the = tips of all branches. -- Bradley T. Hughes bradleythughes@fastmail.fm From owner-freebsd-ports@freebsd.org Thu Jun 2 08:07:03 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 026C5B638F7 for ; Thu, 2 Jun 2016 08:07:03 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from mail.mimar.rs (mail1.mimar.rs [193.53.106.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AB4611D6F for ; Thu, 2 Jun 2016 08:07:01 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from mail1.mimar.rs (localhost [127.0.1.128]) by mail.mimar.rs (Postfix) with ESMTP id C4B5345CDB6A for ; Thu, 2 Jun 2016 09:56:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mimar.rs; h= content-transfer-encoding:content-type:content-type:mime-version :x-mailer:organization:references:message-id:subject:subject :from:from:date:date:received:received; s=mimar-0901; t= 1464854211; x=1466668612; bh=tNS3uCkM943DFFO2otQOxQtmxzpm5o0j0v8 XgEB9YFc=; b=L55GhjnOwbJEtSgdKkFPOZ7nPWbzKmJU0kCnuW+bUNtH4e8PknF aG2VxFR0sNdCmJIMcTyTKSB1xs6/LCz5gIfSvDgVpbQtipfjZm4oakmFdjZou1kO wTgggSWpjLsp4Ss1ttY+krseaou+ripgmQxONO4/fWWndAXN/+prKj+c= X-Virus-Scanned: amavisd-new at mimar.rs Received: from mail.mimar.rs ([127.0.1.128]) by mail1.mimar.rs (amavis.mimar.rs [127.0.1.128]) (amavisd-new, port 10026) with LMTP id JZf9zLEkdf54 for ; Thu, 2 Jun 2016 09:56:51 +0200 (CEST) Received: from mephala.kappastar.com (nat-nat.kappastar.com [193.53.106.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: marko.cupac@mimar.rs) by mail.mimar.rs (Postfix) with ESMTPSA id 1A27845CD851 for ; Thu, 2 Jun 2016 09:56:50 +0200 (CEST) Date: Thu, 2 Jun 2016 09:56:50 +0200 From: Marko =?UTF-8?B?Q3VwYcSH?= To: freebsd-ports@freebsd.org Subject: Re: old ports/packages Message-ID: <20160602095650.0f60b9b7@mephala.kappastar.com> References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> Organization: Mimar X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 08:07:03 -0000 On Wed, 1 Jun 2016 09:27:53 -0700 (PDT) Roger Marquis wrote: > Having endured 'buildworld; buildkernel; nstallkernal; reboot' and > 'installworld; mergemaster' over the past few weeks I can say without > exaggeration it is an order of magnitude more time consuming that > 'yum update' or 'aptitude upgrade'. How about "freebsd-update fetch; freebsd-update install; reboot"? --=20 Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupa=C4=87 https://www.mimar.rs/ From owner-freebsd-ports@freebsd.org Thu Jun 2 16:14:39 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5A00B61A42 for ; Thu, 2 Jun 2016 16:14:39 +0000 (UTC) (envelope-from marquis@roble.com) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A7B9A1311 for ; Thu, 2 Jun 2016 16:14:39 +0000 (UTC) (envelope-from marquis@roble.com) Date: Thu, 2 Jun 2016 09:14:32 -0700 (PDT) From: Roger Marquis To: =?ISO-8859-2?Q?Marko_Cupa=E6?= cc: freebsd-ports@freebsd.org Subject: Re: old ports/packages In-Reply-To: <20160602095650.0f60b9b7@mephala.kappastar.com> References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <20160602095650.0f60b9b7@mephala.kappastar.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 16:14:39 -0000 >> Having endured 'buildworld; buildkernel; nstallkernal; reboot' and >> 'installworld; mergemaster' over the past few weeks I can say without >> exaggeration it is an order of magnitude more time consuming that >> 'yum update' or 'aptitude upgrade'. > > How about "freebsd-update fetch; freebsd-update install; reboot"? Tried that but didn't find it reliable. Have also heard rumors of freebsd-update being deprecated at some point. Roger From owner-freebsd-ports@freebsd.org Wed Jun 1 21:42:14 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3636B65C78 for ; Wed, 1 Jun 2016 21:42:14 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from mail.abinet.ru (mail.abinet.ru [136.243.72.227]) by mx1.freebsd.org (Postfix) with ESMTP id BC0B21043 for ; Wed, 1 Jun 2016 21:42:14 +0000 (UTC) (envelope-from abi@abinet.ru) Received: from [10.0.0.1] (unknown [10.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.abinet.ru (Postfix) with ESMTPSA id E59B91B7CE for ; Wed, 1 Jun 2016 21:42:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=abinet.ru; s=dkim; t=1464817332; bh=sYBA5mYtjXZU9BE13Ugf6y+eLJlfBdCtnGeF7xke0I8=; h=Date:From:To:Subject:References:In-Reply-To; b=AZJDTn6HMjOTNxFlCbeZ4iOc8cThgiSjYhAF1pP80ha27oO0r5vceATXfXgzFSaPB ChY3diE9G+3KsAu8zfqNPSPdrsZFzkpixPisvAtAnUC5fWZokBH0/Aw9BiTfSeCnmx CXelrzGfXB+Xe/d+ELX6MiaNOptYzKt7Wi0eZ1HM= Message-ID: <574F56B3.3030707@abinet.ru> Date: Thu, 02 Jun 2016 00:42:11 +0300 From: abi User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:) Gecko/20160112 FossaMail/25.2.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: Zoneminder - call for testers References: <574F31E1.3040806@abinet.ru> <20160601192727.GD41922@home.opsec.eu> In-Reply-To: <20160601192727.GD41922@home.opsec.eu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2016 21:42:15 -0000 Looks like it doesn't work with mysql57-client :( mysql56-client works. On 01.06.2016 22:27, Kurt Jaeger wrote: > Hi! > >> I'm updating the ZoneMinder security camera solution >> (http://www.freshports.org/multimedia/zoneminder/). Developers made huge >> efforts to make it compatible with FreeBSD. >> >> As this is my first attempt, can you look into it before I open a PR ? :) > It looks promising, but there's this cmake error coming up during > the configure phase: > > -- Looking for mysql/mysql.h - not found > CMake Error at CMakeLists.txt:396 (message): > ZoneMinder requires MySQL headers - check that MySQL development packages > are installed > > I do have mysql 5.7.12 installed, the file is in > > /usr/local/include/mysql/mysql.h > > Any idea how to allow cmake to find it ? > > Btw, I suggest you check the port with portlint -AC, as well. > From owner-freebsd-ports@freebsd.org Thu Jun 2 02:23:40 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE768B62217 for ; Thu, 2 Jun 2016 02:23:40 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8F22B1660 for ; Thu, 2 Jun 2016 02:23:40 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id u522NX4e042695 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 1 Jun 2016 19:23:33 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id u522NXIE042694; Wed, 1 Jun 2016 19:23:33 -0700 (PDT) (envelope-from sgk) Date: Wed, 1 Jun 2016 19:23:33 -0700 From: Steve Kargl To: Alphons van Werven Cc: FreeBSD ports mailing list Subject: Re: science/hdf5 ABI broken Message-ID: <20160602022333.GA42451@troutmask.apl.washington.edu> References: <20160530190116.GA92928@troutmask.apl.washington.edu> <20160530191246.GA534@spectrum.skysmurf.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160530191246.GA534@spectrum.skysmurf.nl> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 02:23:40 -0000 On Mon, May 30, 2016 at 09:12:46PM +0200, Alphons van Werven wrote: > Steve Kargl wrote: > > > Please supply either a science/hdf5-1.8 port, revert the 1.10.0 > > update, or consider the above patches. > > Sounds like a job for the port's maintainer... > > % make -C /usr/ports/science/hdf5 maintainer > There is a patch for the Makefile, so I'm well aware of the maintainer line. I'm going under the assumption that if one is a maintainer, then s/he will be reading this list. I'm also going on the assumption that users of the hdf5 port cannot magically read the maintainer's email. You can take my original post as public service for the users of hdf5. I'll note that there are 2 bug reports about the breakage: [Bug 209242] math/matio broken by science/hd5 upgrade to 1.10 [Bug 209244] math/scilab broken by science/hd5 upgrade to 1.10 I doubt that the patches proposed in these PR apply to any Fortran codes, but I'm too disinterested to investigate further. I suspect that the breakage is going to affect more ports, and for the users of these port they may not even be aware of problem (i.e., they may produce corrupt data with no obvious warning or error). The very first entry under "New Features" in the Release Notes for HDF5 1.10.0 is - API Compatibility with HDF5 1.8 Flag Was Added The 1.10 version of the HDF5 Library can be configured to operate identically to the 1.8 library with the --with-default-api-version=v18 configure flag. This allows existing code to be compiled with the 1.10 library without requiring immediate changes to the application source code. For addtional configuration options and other details, see "API Compatibility Macros in HDF5" at https://www.hdfgroup.org/HDF5/doc/RM/APICompatMacros.html. This doesn't give one too much confidence that the maintainer actually looked at the documentation. S/he simply assumed that a point release update from 1.8.16 to 1.10.0 did not change the ABI/API. -- Steve From owner-freebsd-ports@freebsd.org Thu Jun 2 09:37:04 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B392FB6443F for ; Thu, 2 Jun 2016 09:37:04 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A228717E2 for ; Thu, 2 Jun 2016 09:37:04 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id A17D3B6443D; Thu, 2 Jun 2016 09:37:04 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9EC2EB6443B for ; Thu, 2 Jun 2016 09:37:04 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org (portscout.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 930E017E1 for ; Thu, 2 Jun 2016 09:37:04 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.15.2/8.15.2) with ESMTP id u529b4mt040866 for ; Thu, 2 Jun 2016 09:37:04 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.15.2/8.15.2/Submit) id u529b4Qm040865; Thu, 2 Jun 2016 09:37:04 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201606020937.u529b4Qm040865@portscout.freebsd.org> X-Authentication-Warning: portscout.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Thu, 2 Jun 2016 09:37:04 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 09:37:04 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ multimedia/gtk-youtube-viewer | 3.2.1 | 3.2.2 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Thu Jun 2 16:31:08 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CBF0CB63FC3 for ; Thu, 2 Jun 2016 16:31:08 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id AEFCF114B for ; Thu, 2 Jun 2016 16:31:08 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id AE575B63FC2; Thu, 2 Jun 2016 16:31:08 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE00AB63FC1 for ; Thu, 2 Jun 2016 16:31:08 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E7901148 for ; Thu, 2 Jun 2016 16:31:08 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: by mail-qk0-x235.google.com with SMTP id c140so35352527qke.2 for ; Thu, 02 Jun 2016 09:31:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=G1c8KWHI2Dtlai6K9eHrLcICqI6eNXxZi19XGtEJ8uI=; b=kyhPUyhGJwNWHwPpth7pa8+8+QQ7vAChgKNusp7f7uypdPEZUziGX/CA26ggM6gWEq KtFwrms3se9zFa44WhIK6+3Mt7snbvUVAMugh5WZ+KGFkKKG/jR4GJ3JXNoW6OMGQG3Q AC0eT09aAoJ5gDssXnUFvH3fa4I87i+cEFhkFzpfCsc4deNNQ3hN3+4Z1smhQtllijsh 5aKsZF0aIHyp0Dz/igB1OVp/PGtKc50aJ8WjStUiYNvkO014ARZsP3o1IV1/31IKim7i nTZJM9HF0OC0h64hwaORafHMFm4/B5f0Pxh4RHVkg+MENSihbfbySWg7m9Cy/GI2AhAe R32g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=G1c8KWHI2Dtlai6K9eHrLcICqI6eNXxZi19XGtEJ8uI=; b=TezoUB0DuhM5H9Cw0kwPGz+Kzd+ow/VpfsWZAMnCFl8Tbf0zcfxMobFirKelUxh+YT 8eUmUNk9cWZQ5WRxv+JtzESFRGNNmACOcCs64DFpfWf+6vLbxaSdjIXr/gjLOQU1e0Sw OwrZ4F2fVot/yqPrczKMEFvW1S2ylF9/PsIWTD7DnN6Fo9wQpS6lRPD29H36w4ao+0aS ix8HqbNSRDoqCxGTm7Vvi2Afjfpq9isTBcNhTcr+4mDbvI+IdkPt6dqxsIXKTBrEalDZ 9Coi5onN2BHA5O1UfpqdDfwMpmI7esWR31wEb9nhkEEDiq/agy6HMhFAW/MYZSU23iMx 9qdw== X-Gm-Message-State: ALyK8tJ3BufQEo1FV/c7NVNbx/wvDRFYIVjKJhZe7B4rQrWBzZjCryIOfXpEgUGchcOkAaS+dSAyoNlb58NMwA== MIME-Version: 1.0 X-Received: by 10.55.24.20 with SMTP id j20mr20505752qkh.168.1464885067708; Thu, 02 Jun 2016 09:31:07 -0700 (PDT) Received: by 10.55.77.135 with HTTP; Thu, 2 Jun 2016 09:31:07 -0700 (PDT) Date: Thu, 2 Jun 2016 18:31:07 +0200 Message-ID: Subject: PR needs care From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= To: ports FreeBSD Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 16:31:08 -0000 Hi, Could a committer please have a look at this PR? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209872 Thanks in advance. From owner-freebsd-ports@freebsd.org Thu Jun 2 16:51:49 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 388D9B62CB0 for ; Thu, 2 Jun 2016 16:51:49 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from mail.skysmurf.nl (spectrum.skysmurf.nl [83.162.175.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.skysmurf.nl", Issuer "mail.skysmurf.nl" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B71BC152D for ; Thu, 2 Jun 2016 16:51:48 +0000 (UTC) (envelope-from freebsd@skysmurf.nl) Received: from spectrum.skysmurf.nl (mail.skysmurf.nl [192.168.42.4]) by mail.skysmurf.nl (8.15.2/8.15.2) with SMTP id u52GpdH6078722; Thu, 2 Jun 2016 18:51:39 +0200 (CEST) (envelope-from freebsd@skysmurf.nl) Received: by spectrum.skysmurf.nl (sSMTP sendmail emulation); Thu, 02 Jun 2016 18:51:39 +0200 Date: Thu, 2 Jun 2016 18:51:39 +0200 From: Alphons van Werven To: Steve Kargl Cc: FreeBSD ports mailing list Subject: Re: science/hdf5 ABI broken Message-ID: <20160602165139.GA78519@spectrum.skysmurf.nl> References: <20160530190116.GA92928@troutmask.apl.washington.edu> <20160530191246.GA534@spectrum.skysmurf.nl> <20160602022333.GA42451@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="r5Pyd7+fXNt84Ff3" Content-Disposition: inline In-Reply-To: <20160602022333.GA42451@troutmask.apl.washington.edu> X-PGP-Key: http://www.skysmurf.nl/~fonz/fonz_pubkey.asc User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 16:51:49 -0000 --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Steve Kargl wrote: >> Sounds like a job for the port's maintainer... >=20 > I'm going under the assumption that if one is a maintainer, then s/he > will be reading this list. Ideally, yes. But in practice I doubt that every maintainer is subscribed to ports@ -- and reads it frequently. Hence, I always recommend to e-mail the maintainer, CC'ing ports@ if necessary/useful (such as in this case). Or to submit a PR, of course :-) > You can take my original post as public service for the users of hdf5. > I'll note that there are 2 bug reports about the breakage: >=20 > [Bug 209242] math/matio broken by science/hd5 upgrade to 1.10 =20 > [Bug 209244] math/scilab broken by science/hd5 upgrade to 1.10=20 The public service is of course appreciated, no doubts there. Has the maintainer of science/hdf5 been informed of these PRs? For example, is he on the CC list for any of those bugs? AvW --=20 A.J. "Fonz" van Werven mailsig: Ob technicas difficultates, lux in fine cuniculum non operatur. --r5Pyd7+fXNt84Ff3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJXUGQbAAoJEAfP7gJTaCe8mfgQAMO92QIJ26drDTd7bPjl4ryc MqoRKLuunLghBv7CVzPlA2z3tDrMV0uEH8aibOgchPp7AzOvZeW1o8InpINBWr1d w8dhFxRDqreCcBr/Zz4QZ+vUX4CMV9UPFeNFY0FflkgYWyvrm4PmTK3lfJXMNJ6x iWjqJieA927iSA86GSLSFZlsfevqpXzntq+1seqq6wI25ynXKpcnUEF4Bpk+TTbO kBQyZ5j+TkVr7Mh6BCIvmV9cUckNvtYZ6eutuz8d6OGMmDtOIB/S8+AI3SVPuo7d 7yMOm8cLhYhtmE48Nmg4ppi43COMxGGCidOyZr/J9q9HkOMy9kRgxJTsd1FXkunk 2SDwb/OC2Kqsm5v5msTq8+jIWaPV9BKQQVBSl/xCsbjz0m0AhLKHpkmC4ZgV/A6K dXlJlRacH35uxXrwvfNRaaObbOdUKLdhqKomE0OL8xJ8IwPdG6cwFsT/lk9HIoty 61+Bqt9XYtio25EX3EJEVGcLJi7vAiLnRDu3+qA543xGqxzZrhOb7d09OXbmq3SN E46hidiQrVsTmqANPSyQ37rmE6PwaqyYBgp3K0quMORcVXEKheUn/l6nBLMhcV8k DAf/A552RJ6x3uwqAUyLiMliobkp6RidULh6oy0UVfJiTMM6jknPjiXx+9LFm7CD OhgW2cqt3p9k+X6rPG7o =yy48 -----END PGP SIGNATURE----- --r5Pyd7+fXNt84Ff3-- From owner-freebsd-ports@freebsd.org Thu Jun 2 17:17:27 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF9B4B65725 for ; Thu, 2 Jun 2016 17:17:27 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49A4D1BB3 for ; Thu, 2 Jun 2016 17:17:27 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id u52HHIv7039819; Thu, 2 Jun 2016 10:17:22 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201606021717.u52HHIv7039819@gw.catspoiler.org> Date: Thu, 2 Jun 2016 10:17:18 -0700 (PDT) From: Don Lewis Subject: Re: science/hdf5 ABI broken To: sgk@troutmask.apl.washington.edu cc: freebsd@skysmurf.nl, freebsd-ports@freebsd.org In-Reply-To: <20160602022333.GA42451@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 17:17:28 -0000 On 1 Jun, Steve Kargl wrote: > On Mon, May 30, 2016 at 09:12:46PM +0200, Alphons van Werven wrote: >> Steve Kargl wrote: >> >> > Please supply either a science/hdf5-1.8 port, revert the 1.10.0 >> > update, or consider the above patches. >> >> Sounds like a job for the port's maintainer... >> >> % make -C /usr/ports/science/hdf5 maintainer >> > > There is a patch for the Makefile, so I'm well aware of the > maintainer line. I'm going under the assumption that if one > is a maintainer, then s/he will be reading this list. I'm > also going on the assumption that users of the hdf5 port cannot > magically read the maintainer's email. You can take my original > post as public service for the users of hdf5. I'll note that > there are 2 bug reports about the breakage: > > [Bug 209242] math/matio broken by science/hd5 upgrade to 1.10 > [Bug 209244] math/scilab broken by science/hd5 upgrade to 1.10 > > I doubt that the patches proposed in these PR apply to any > Fortran codes, but I'm too disinterested to investigate further. > > I suspect that the breakage is going to affect more ports, and for > the users of these port they may not even be aware of problem (i.e., > they may produce corrupt data with no obvious warning or error). > > The very first entry under "New Features" in the Release Notes > for HDF5 1.10.0 is > > - API Compatibility with HDF5 1.8 Flag Was Added > > The 1.10 version of the HDF5 Library can be configured to operate > identically to the 1.8 library with the --with-default-api-version=v18 > configure flag. This allows existing code to be compiled with the 1.10 > library without requiring immediate changes to the application source > code. For addtional configuration options and other details, see > "API Compatibility Macros in HDF5" at > https://www.hdfgroup.org/HDF5/doc/RM/APICompatMacros.html. > > This doesn't give one too much confidence that the maintainer actually > looked at the documentation. S/he simply assumed that a point release > update from 1.8.16 to 1.10.0 did not change the ABI/API. The matio and scilab ports would not build after hdf5 was upgraded. In addition to the configure flag that you mention, hdf5 can also be told to use one of its older API versions by specifying specific preprocessor defines when building software that pulls in its include files. The matio and scilab ports were modified to use the H5_USE_18_API preprocessor flag to get the version 1.8 API and they now succesfully build. Changing the default hdf5 API version will only help until we start getting ports that want the new API. That said, ports that use hdf5 should have been tested with new version and patches prepared to fix them before the new version was committed. From owner-freebsd-ports@freebsd.org Thu Jun 2 17:50:21 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01361B6528A for ; Thu, 2 Jun 2016 17:50:21 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E14721B4E; Thu, 2 Jun 2016 17:50:20 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id u52HoJeN054340 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 2 Jun 2016 10:50:19 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id u52HoJB4054339; Thu, 2 Jun 2016 10:50:19 -0700 (PDT) (envelope-from sgk) Date: Thu, 2 Jun 2016 10:50:19 -0700 From: Steve Kargl To: Don Lewis Cc: freebsd@skysmurf.nl, freebsd-ports@freebsd.org Subject: Re: science/hdf5 ABI broken Message-ID: <20160602175019.GA54080@troutmask.apl.washington.edu> Reply-To: kargl@uw.edu References: <20160602022333.GA42451@troutmask.apl.washington.edu> <201606021717.u52HHIv7039819@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201606021717.u52HHIv7039819@gw.catspoiler.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 17:50:21 -0000 On Thu, Jun 02, 2016 at 10:17:18AM -0700, Don Lewis wrote: > On 1 Jun, Steve Kargl wrote: > > On Mon, May 30, 2016 at 09:12:46PM +0200, Alphons van Werven wrote: > >> Steve Kargl wrote: > >> > >> > Please supply either a science/hdf5-1.8 port, revert the 1.10.0 > >> > update, or consider the above patches. > >> > >> Sounds like a job for the port's maintainer... > >> > >> % make -C /usr/ports/science/hdf5 maintainer > >> > > > > There is a patch for the Makefile, so I'm well aware of the > > maintainer line. I'm going under the assumption that if one > > is a maintainer, then s/he will be reading this list. I'm > > also going on the assumption that users of the hdf5 port cannot > > magically read the maintainer's email. You can take my original > > post as public service for the users of hdf5. I'll note that > > there are 2 bug reports about the breakage: > > > > [Bug 209242] math/matio broken by science/hd5 upgrade to 1.10 > > [Bug 209244] math/scilab broken by science/hd5 upgrade to 1.10 > > > > I doubt that the patches proposed in these PR apply to any > > Fortran codes, but I'm too disinterested to investigate further. > > > > I suspect that the breakage is going to affect more ports, and for > > the users of these port they may not even be aware of problem (i.e., > > they may produce corrupt data with no obvious warning or error). > > > > The very first entry under "New Features" in the Release Notes > > for HDF5 1.10.0 is > > > > - API Compatibility with HDF5 1.8 Flag Was Added > > > > The 1.10 version of the HDF5 Library can be configured to operate > > identically to the 1.8 library with the --with-default-api-version=v18 > > configure flag. This allows existing code to be compiled with the 1.10 > > library without requiring immediate changes to the application source > > code. For addtional configuration options and other details, see > > "API Compatibility Macros in HDF5" at > > https://www.hdfgroup.org/HDF5/doc/RM/APICompatMacros.html. > > > > This doesn't give one too much confidence that the maintainer actually > > looked at the documentation. S/he simply assumed that a point release > > update from 1.8.16 to 1.10.0 did not change the ABI/API. > > The matio and scilab ports would not build after hdf5 was upgraded. In > addition to the configure flag that you mention, hdf5 can also be told > to use one of its older API versions by specifying specific preprocessor > defines when building software that pulls in its include files. The > matio and scilab ports were modified to use the H5_USE_18_API > preprocessor flag to get the version 1.8 API and they now succesfully > build. The preprocessor flag may work for C (and C++). It will not work with Fortran. The Fortran interface for HDF5 will produce modules (e.g., /usr/local/include/hdf5.mod). You can think of a Fortran module as a pre-compiled header on steriods. > That said, ports that use hdf5 should have been tested with new version > and patches prepared to fix them before the new version was committed. I agree that further testing should have been done. But, building other ports that consume HDF5 may not be sufficient. There is a difference between "does it build" and "does it produce correct results". -- Steve From owner-freebsd-ports@freebsd.org Thu Jun 2 20:08:32 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E326B66812 for ; Thu, 2 Jun 2016 20:08:32 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [185.24.122.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 36BF61CF2 for ; Thu, 2 Jun 2016 20:08:31 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from crayon2.yoonka.com (crayon2.yoonka.com [192.168.1.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id u52K8MkI053544 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 2 Jun 2016 20:08:22 GMT (envelope-from list1@gjunka.com) Subject: Re: old ports/packages To: freebsd-ports@freebsd.org References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> From: Grzegorz Junka Message-ID: Date: Thu, 2 Jun 2016 20:08:22 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 20:08:32 -0000 On 31/05/2016 13:59, Vincent Hoffman-Kazlauskas wrote: > > On 31/05/2016 14:17, Torsten Zuehlsdorff wrote: >> On 04.05.2016 19:17, Grzegorz Junka wrote: >> >>> >>> LTS of the base system or ports? The base system is already quite well >>> supported long-term. >> This is a very good question, because it is not that clear. But let me >> state right here: No, the base system has not a good long-term support! >> >> Yes, we have 2 years for the latest release, but 2 years seems to be >> very short for firms. Often they want 5 years. >> >> And you are forced to update. You can't stay on say 10.1 or 10.2 because >> the support will end 2016. Which is short, because 10.2 was released in >> august 2015. This is only one and a half year. > > To be fair the support is last release + 2 years, supporting a minor > version for more than 2 years seems unreasonable, compare to say redhat > a major commercial vendor. They provide up to 10 years sure but for a > major version ie 6 not a minor version ie 6.1. In fact their policy > page(1*) says "Under a Red Hat Enterprise Linux subscription, all > available RHSAs and RHBAs are provided for the current active minor > release until the availability of the next minor release" and that if > you want a minor release supported for longer you pay more and even then > its only approx 2 years, (example 6.7 (released 2015-07-22) ends July > 31, 2017) > So far for me updating freebsd minor releases has been much the same > experience as upgrading Centos/RHEL minor releases. It's not fair to compare RedHat to FreeBSD. Companies pay good money to maintain the support for the systems they are using. They don't pay FreeBSD a penny. I think the real issue preventing a wider adoption at companies is not that there is no LTS but that there is no commercial entity that would maintain its own LTS version of FreeBSD base and packages and make it available to companies with paid support options. There are only companies who can provide general support for FreeBSD as a service. I recently worked at a company who did exactly that, they bought Red Hat specifically because they could pay for it and forget about updates and maintenance (at least that what the management thought - for the developers it was a pain in the ** because most packages were outdated or not available at all and to do any real development we had to compile the necessary applications from sources anyway). Grzegorz From owner-freebsd-ports@freebsd.org Thu Jun 2 20:29:00 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B434CB66F4B for ; Thu, 2 Jun 2016 20:29:00 +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]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 774DB1C6C for ; Thu, 2 Jun 2016 20:29:00 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-ports@freebsd.org with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1b8ZEg-000n34-Bn>; Thu, 02 Jun 2016 22:28:58 +0200 Received: from x5ce13ce8.dyn.telefonica.de ([92.225.60.232] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-ports@freebsd.org with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1b8ZEg-001lf8-1I>; Thu, 02 Jun 2016 22:28:58 +0200 Date: Thu, 2 Jun 2016 22:28:53 +0200 From: "O. Hartmann" To: FreeBSD Ports Subject: devel/beignet: build error: call to 'abs' is ambiguous insn->extra.longjmp = abs(index - origin) > 800 Message-ID: <20160602222853.085d82f7.ohartman@zedat.fu-berlin.de> Organization: FU Berlin X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/xghQI4p0dHADA/MUvFDG8aB"; protocol="application/pgp-signature" X-Originating-IP: 92.225.60.232 X-ZEDAT-Hint: A X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 20:29:00 -0000 --Sig_/xghQI4p0dHADA/MUvFDG8aB Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Building/updating port devel/beignet fails with [ 42%] Building CXX object backend/src/CMakeFiles/gbe.dir/llvm/llvm_unroll.= cpp.o [ 42%] Building C object backend/src/CMakeFiles/gbe.dir/backend/gen/gen_mes= a_disasm.c.o [ 42%] Building CXX object backend/src/CMakeFiles/gbe.dir/backend/gen_insn_= selection.cpp.o [ 43%] Building CXX object backend/src/CMakeFiles/gbe.dir/backend/gen_insn_scheduling.cpp.o [ 43%] Bui= lding CXX object backend/src/CMakeFiles/gbe.dir/backend/gen_reg_allocation.cpp.o /usr/ports/= lang/beignet/work/Beignet-1.1.2-Source/backend/src/backend/gen_insn_selecti= on.cpp:1156:27: error: call to 'abs' is ambiguous insn->extra.longjmp =3D abs(index - origi= n) > 800; ^~~ /usr/include/stdlib.h:83:6: note: candidate function int abs(int) __pure2; ^ /usr/include/c++/v1/stdlib.h:115:44: note: candidate function inline _LIBCPP_INLINE_VISIBILITY long abs( long __x) _NOEXCEPT {re= turn labs(__x);} ^ /usr/include/c++/v1/stdlib.h:117:44: note: candidate function inline _LIBCPP_INLINE_VISIBILITY long long abs(long long __x) _NOEXCEPT {re= turn llabs(__x);} ^ /usr/include/c++/v1/math.h:646:1: note: candidate function abs(float __lcpp_x) _NOEXCEPT {return fabsf(__lcpp_x);} ^ /usr/include/c++/v1/math.h:650:1: note: candidate function abs(double __lcpp_x) _NOEXCEPT {return fabs(__lcpp_x);} ^ /usr/include/c++/v1/math.h:654:1: note: candidate function abs(long double __lcpp_x) _NOEXCEPT {return fabsl(__lcpp_x);} Regards, oh --Sig_/xghQI4p0dHADA/MUvFDG8aB Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXUJcFAAoJEOgBcD7A/5N86HkIAMOQ3zWzXLkaM1u2ribpho5s 2qcmOf6MBJWf+mtLPeX5GwAy4x5KKzlWhem9bxYAKGuMMel9pkUJk5b6fTwsfgml WmNc6yZNgTN2EtgfXyNDgleJCSaW5okVkT1QxzebUrWLtdwXyxkuLjLH+XdsHrhV o1cBHCk7gfC+RwEIjKEHRFY47JQgc0v4/ugC6wKMDKcu1hmujnU3SuSU/aa+toaY vTZNg9AluPYdGQU9sThTbQ3+Ng+GRtmsRnBs0DXuPMBmOAnfPr//Grv0Xfqrr1/x 3DgIejIw0MtPL0qIl/LGbUsTci6Y3CBATWn0Jom5juK74EEZp73ygQQOIqLK1MM= =/ELB -----END PGP SIGNATURE----- --Sig_/xghQI4p0dHADA/MUvFDG8aB-- From owner-freebsd-ports@freebsd.org Fri Jun 3 07:26:24 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD056B68D6A for ; Fri, 3 Jun 2016 07:26:24 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 38BEA1947 for ; Fri, 3 Jun 2016 07:26:24 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 158C9C071 for ; Fri, 3 Jun 2016 07:26:21 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/158C9C071; dkim=none; dkim-atps=neutral Subject: Re: old ports/packages To: freebsd-ports@freebsd.org References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> From: Matthew Seaman Message-ID: <0df231f8-9f11-bb33-4189-b0e49a5eb1b4@FreeBSD.org> Date: Fri, 3 Jun 2016 08:26:20 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="uvSAScMb0jamha8rRptxXoBCC7bwgDXrG" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 07:26:24 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --uvSAScMb0jamha8rRptxXoBCC7bwgDXrG Content-Type: multipart/mixed; boundary="fml8QKMrVm3LJ5B9F52I59IgTF34KRp6e" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: <0df231f8-9f11-bb33-4189-b0e49a5eb1b4@FreeBSD.org> Subject: Re: old ports/packages References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> In-Reply-To: --fml8QKMrVm3LJ5B9F52I59IgTF34KRp6e Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 02/06/2016 21:08, Grzegorz Junka wrote: > It's not fair to compare RedHat to FreeBSD. Companies pay good money to= > maintain the support for the systems they are using. They don't pay > FreeBSD a penny. I think the real issue preventing a wider adoption at > companies is not that there is no LTS but that there is no commercial > entity that would maintain its own LTS version of FreeBSD base and > packages and make it available to companies with paid support options. > There are only companies who can provide general support for FreeBSD as= > a service. Have you heard about what Xinuos are doing with FreeBSD? http://www.xinuos.com/menu-products/openserver-10 Xinuos' whole ethos is in providing long term commercial support, and their new platform is built on FreeBSD. Cheers, Matthew --fml8QKMrVm3LJ5B9F52I59IgTF34KRp6e-- --uvSAScMb0jamha8rRptxXoBCC7bwgDXrG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXUTEcXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATN3sP/1hwUelOmCuqFMDqHnJ4EN8D joR664h83UHAI61uBa8G90OlDBf5fLQSNlvqvDbq33R+YbzprzoggphgecXvye0v UeKT5PHkI0Y+zqMgUTuH0LwpKGMvvSOXH2Tb1HjrZjjBlik9DnNi4U6cVxa2upao Nlq4vtIWBuRDQzy47SzkMz+Zj9wpmtdKp4r31MBvs+pdAUpNE2/GLxuHOvG7c2/J 8N1bUug6YbMwzyI7mCyvlZr+hjKkc0AdOSNQnwttHmwXWVCBa4qk42xwsSttl8o+ E3V/BhbhH3ycf4CDJqb2JmqvoFoSsNa4Q7q0mfElUHeDv7+e5ig6qKlfXOMRZdGL AcwBlMolJkYzJ9IIA3kmCD+HDlOF0/aj4Z2ygM62JfKhSEAOIPAZP2MUWgOwkUI2 3epxCSRQrFcu+SD9sVS4OMxFsYaK3aMtUsTNp1yT+MCliKt0PT/cdwo0qE0nS1B0 zD8qeGKzVw8p6mYt7NefRdyXM6w20iDdXIxr7XagDRAZEOlNjR6hg7/rkXrsqofn yAt5wgE7gnRGRNpK4a6QkeVoj1C3XzJdkjIDM+JKaueMOc7EVh01hZcwLH5NgM0m QLszkitOQ+OoQjot+jHC5utiR3xF8dC78gxf9ixa3GaahyYmkuIe5B4gAi9W8br7 hBKe+jpx4whTVs3Uza1r =go7L -----END PGP SIGNATURE----- --uvSAScMb0jamha8rRptxXoBCC7bwgDXrG-- From owner-freebsd-ports@freebsd.org Fri Jun 3 08:28:17 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A54B9B68E04 for ; Fri, 3 Jun 2016 08:28:17 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from mail.mimar.rs (mail1.mimar.rs [193.53.106.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5A8311BAD for ; Fri, 3 Jun 2016 08:28:16 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from mail1.mimar.rs (localhost [127.0.1.128]) by mail.mimar.rs (Postfix) with ESMTP id 29B0245CDB67 for ; Fri, 3 Jun 2016 10:28:07 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mimar.rs; h= content-transfer-encoding:content-type:content-type:mime-version :x-mailer:organization:references:message-id:subject:subject :from:from:date:date:received:received; s=mimar-0901; t= 1464942483; x=1466756884; bh=4GMRyo2AHUCF/MHW47lVv7a1pMf7z1t6zo3 6UZavyhA=; b=uBKhx/Bn3TxAa4SIpuRcksxWM48sKB2Js420uiodFcyLwgg1G1B LxlUp4det5vMb/WKGmqBEqEt11jhoN7OAZbIEdGym0f5CWc7vvI4Fa+4xbgLXXDe tllE4fS4Iwa+GC/9AiOvO/LzmHUIoWva0s3n910ssGEVZPm6q3QpJaMI= X-Virus-Scanned: amavisd-new at mimar.rs Received: from mail.mimar.rs ([127.0.1.128]) by mail1.mimar.rs (amavis.mimar.rs [127.0.1.128]) (amavisd-new, port 10026) with LMTP id EQGwwwCd4KkD for ; Fri, 3 Jun 2016 10:28:03 +0200 (CEST) Received: from mephala.kappastar.com (nat-nat.kappastar.com [193.53.106.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: marko.cupac@mimar.rs) by mail.mimar.rs (Postfix) with ESMTPSA id D062B45CD851 for ; Fri, 3 Jun 2016 10:28:03 +0200 (CEST) Date: Fri, 3 Jun 2016 10:28:03 +0200 From: Marko =?UTF-8?B?Q3VwYcSH?= To: freebsd-ports@freebsd.org Subject: Re: old ports/packages Message-ID: <20160603102803.11f1f6e4@mephala.kappastar.com> References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <20160602095650.0f60b9b7@mephala.kappastar.com> Organization: Mimar X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 08:28:17 -0000 On Thu, 2 Jun 2016 09:14:32 -0700 (PDT) Roger Marquis wrote: > > How about "freebsd-update fetch; freebsd-update install; reboot"? =20 >=20 > Tried that but didn't find it reliable. In what way was it unreliable? Did you report your problems in bugzilla, lists or forums? > Have also heard rumors of freebsd-update being deprecated at some > point. Even if those rumours were true I fail to see in which way possible future depreciation affects current possibility to use it. Regards, --=20 Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupa=C4=87 https://www.mimar.rs/ From owner-freebsd-ports@freebsd.org Fri Jun 3 09:45:40 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0D75B66241 for ; Fri, 3 Jun 2016 09:45:40 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 8FB551C61 for ; Fri, 3 Jun 2016 09:45:40 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8F1C3B6623E; Fri, 3 Jun 2016 09:45:40 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8ED2BB6623D for ; Fri, 3 Jun 2016 09:45:40 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org (portscout.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 832681C60 for ; Fri, 3 Jun 2016 09:45:40 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.15.2/8.15.2) with ESMTP id u539je1E012907 for ; Fri, 3 Jun 2016 09:45:40 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.15.2/8.15.2/Submit) id u539jeMk012906; Fri, 3 Jun 2016 09:45:40 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201606030945.u539jeMk012906@portscout.freebsd.org> X-Authentication-Warning: portscout.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Fri, 3 Jun 2016 09:45:40 +0000 From: portscout@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 09:45:40 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/ports@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ math/fxt | 2016.04.10 | 2016.06.02 ------------------------------------------------+-----------------+------------ multimedia/kmplayer-kde4 | 0.11.5 | 0.12.0 ------------------------------------------------+-----------------+------------ www/igal2 | 2.1 | 2.2 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-ports@freebsd.org Fri Jun 3 15:25:18 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 791A3B69709 for ; Fri, 3 Jun 2016 15:25:18 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.kissl.de (host64.kissl.de [213.239.241.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "*.shmhost.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 26FF6150A for ; Fri, 3 Jun 2016 15:25:17 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.homeoffice.local (ipservice-092-217-236-241.092.217.pools.vodafone-ip.de [92.217.236.241]) (Authenticated sender: web104p1) by host64.kissl.de (Postfix) with ESMTPSA id 86E8C6A606; Fri, 3 Jun 2016 17:17:55 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: old ports/packages From: Franco Fichtner In-Reply-To: <574ED144.1050603@quip.cz> Date: Fri, 3 Jun 2016 17:17:57 +0200 Cc: Torsten Zuehlsdorff , Vincent Hoffman-Kazlauskas , freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> To: Miroslav Lachman <000.fbsd@quip.cz> X-Mailer: Apple Mail (2.3124) X-Virus-Scanned: clamav-milter 0.99 at host64.kissl.de X-Virus-Status: Clean X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 15:25:18 -0000 Hi there, > On 01 Jun 2016, at 2:12 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >=20 > There is a main difference - if you upgraded from 9.2 to 9.3, you = don't need to recompile (reinstall) all ports, but if you upgraded from = 9.3 to 10.x you need to reinstall all your packages and then remove old = 9.x libraries from the base system. >=20 > On 01 Jun 2016, at 2:12 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >=20 > There is a main difference - if you upgraded from 9.2 to 9.3, you = don't need to recompile (reinstall) all ports, but if you upgraded from = 9.3 to 10.x you need to reinstall all your packages and then remove old = 9.x libraries from the base system. This is very much true for a single user point of view, but the devil is in the details. Let's go through the transition that we as the OPNsense project went through in the FreeBSD 10 series... Not a rant, just facts. The initial release was 10.0, which was phased out after a year, leaving us no choice but to go 10.1 just two months after our initial release in order to receive official security updates. Worst case it takes a few months to adapt to the major transition so that's 12 months minus X months of internal engineering, depending on your staff expertise. In that case we started in 2014, took us 4 months, that's 6 months including the time 10.0 was officially available, so 6 months left for support, when you actually start adapting to 10 as soon as it comes out. For many that's a luxury not going to happen. One can blame anyone for starting late, but it's not going to solve the real world problem. 10.1 went really well. When 10.2 happened for us in January 2016, however, we've already went testing 3 months before and had a number of issues that were not being addressed upstream for a longer amount of time: o HyperV disks stopped registering as ada(4) devices, killing installs that were not using labels. Never fixed. o Hyper-V NAT broken for a very long time, only fixed in 10.2 after active polling for an errata[1] o pf checksumming broke with offloading[2] But the kicker was that building pkg on 10.2 suddenly changed the ABI behaviour in at least two ways that we know of: (1) The reaper for package scripts was now suddenly active, making it a lot harder to restart a service on package upgrade from their own scripts. We hat do investigate and disable the reaper code in pkg itself in order to retain functionality. I would think that others ran into this silently as well. (2) 10.1 systems preloading the "new" pkg for 10.2 were unable to upgrade certain packages, in this instance isc-dhcp43-*. It took a few months to even get to the point of triggering this. In short, we pinned down the pkg ABI to 10.1[3] in order to allow our older 10.1 systems to upgrade. This should not be happening in a "ABI stable" environment. There is pkg-static, but at least in the scope of FreeBSD it's only used when pkg fails for this or that reason, which is very hard to explain to a GUI or backend script. Why not make it the default? 10.2 was the proverbial rollercoaster ride that some would not like to see repeated. 10.3 looks better, but what does that say about 10.4 or 11.0? But 10.3 already had a major speed regression during package installation only caught after the release[4]. Who knows what our users will be facing once we go live in a few months. For downstream projects, this is at least an order of magnitude worse than the simple user that sits in a shell and runs a magical fix command to amend its upgrade path. fir some it's even impossible to get into a shell. Most of downstream projects have automated processes, upgrade features that rely on certain behaviour, well, rely on behaviour to stay stable for at least 10.x, which would make sense. ;) And now we run for each 10.x, every time just run for it in order to make sure that we're not missing an iteration that would amplify the problems we'll be facing with upgrading later. And mind you, this is *with* rebuilding everything from scratch for each minor update just to be on the safe side. :) Cheers, Franco -- [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203630 [2] https://www.freebsd.org/security/advisories/FreeBSD-EN-16:02.pf.asc [3] https://github.com/opnsense/ports/commit/76975890103 [4] = https://www.freebsd.org/security/advisories/FreeBSD-EN-16:06.libc.asc= From owner-freebsd-ports@freebsd.org Fri Jun 3 15:54:49 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2437B680B6; Fri, 3 Jun 2016 15:54:49 +0000 (UTC) (envelope-from papowell@astart.com) Received: from astart2.astart.com (wsip-72-214-30-30.sd.sd.cox.net [72.214.30.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8FB301A76; Fri, 3 Jun 2016 15:54:49 +0000 (UTC) (envelope-from papowell@astart.com) Received: from laptop_103.private (localhost [127.0.0.1]) by astart2.astart.com (8.14.9/8.14.9) with ESMTP id u53FQP3l075731; Fri, 3 Jun 2016 08:26:25 -0700 (PDT) (envelope-from papowell@astart.com) Reply-To: papowell@astart.com To: FreeBSD Ports ML , freebsd-pkg@freebsd.org From: Patrick Powell Subject: how do you force make install to overwrite conflicting files from another port? Organization: Astart Technologies Message-ID: <5b020f89-8f29-5c52-e3de-6c067019b7e9@astart.com> Date: Fri, 3 Jun 2016 08:26:25 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 15:54:49 -0000 Suppose that you have a portA which is a dependency of a lot of other ports. You also have a portB which is a replacement/update/upgrade for portA. PortB provides replacements for the executables generated/supplied by PortA but for various reasons you still want to use some of PortA installed items such as libraries, etc. I tried doing the following: # pkg install PortA # cd /usr/ports/xxx/PortB # make install Installing PortB... pkg-static: PortB conflicts with PortA (installs files into the same place). Problematic file: /usr/local/bin/utilityl *** Error code 70 Is there an option, or a way similar to using 'make FORCE_PGK_REGISTER=YES install' to force overwriting the conflicting files? -- Patrick Powell Astart Technologies papowell@astart.com 1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com From owner-freebsd-ports@freebsd.org Fri Jun 3 16:09:11 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15A56B68426 for ; Fri, 3 Jun 2016 16:09:11 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [185.24.122.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 97039110B for ; Fri, 3 Jun 2016 16:09:10 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from crayon2.yoonka.com (crayon2.yoonka.com [192.168.1.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id u53G97WY077017 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 3 Jun 2016 16:09:08 GMT (envelope-from list1@gjunka.com) Subject: Re: old ports/packages To: freebsd-ports@freebsd.org References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <0df231f8-9f11-bb33-4189-b0e49a5eb1b4@FreeBSD.org> From: Grzegorz Junka Message-ID: Date: Fri, 3 Jun 2016 16:09:07 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <0df231f8-9f11-bb33-4189-b0e49a5eb1b4@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 16:09:11 -0000 On 03/06/2016 07:26, Matthew Seaman wrote: > On 02/06/2016 21:08, Grzegorz Junka wrote: >> It's not fair to compare RedHat to FreeBSD. Companies pay good money to >> maintain the support for the systems they are using. They don't pay >> FreeBSD a penny. I think the real issue preventing a wider adoption at >> companies is not that there is no LTS but that there is no commercial >> entity that would maintain its own LTS version of FreeBSD base and >> packages and make it available to companies with paid support options. >> There are only companies who can provide general support for FreeBSD as >> a service. > Have you heard about what Xinuos are doing with FreeBSD? > > http://www.xinuos.com/menu-products/openserver-10 > > Xinuos' whole ethos is in providing long term commercial support, and > their new platform is built on FreeBSD. > > Cheers, > > Matthew Well, that certainly looks very good and I am glad such companies exist, but it's not exactly what I was referring to. Do they actually maintain their own package repository? They mention Xinuos Application Collection for paid service but nowhere on the site I could find what is actually included in that set. And consider that the packages RedHat maintains are publicly available for anyone to download (as source, but still). CentOS is actually using them to create free binary-compatible RedHat replacements. I don't have anything against their business model and Linux environment is quite different to FreeBSD, not only because of the license. I am just noting that's hard to compare RedHat to FreeBSD companies and to me Xinuos doesn't look like RedHat like-for-like in the BSD world (yet). Grzegorz From owner-freebsd-ports@freebsd.org Fri Jun 3 16:33:19 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9AC81B68ABF for ; Fri, 3 Jun 2016 16:33:19 +0000 (UTC) (envelope-from rde@tavi.co.uk) Received: from kipling.tavi.co.uk (kipling.tavi.co.uk [81.187.145.130]) by mx1.freebsd.org (Postfix) with ESMTP id 5F2DA1049 for ; Fri, 3 Jun 2016 16:33:19 +0000 (UTC) (envelope-from rde@tavi.co.uk) Received: from raksha.tavi.co.uk (raksha.tavi.co.uk [81.187.145.139]) by kipling.tavi.co.uk (Postfix) with ESMTP id 58D399CC45 for ; Fri, 3 Jun 2016 17:23:13 +0100 (BST) Date: Fri, 3 Jun 2016 17:23:13 +0100 From: Bob Eager To: freebsd-ports@freebsd.org Subject: Re: old ports/packages Message-ID: <20160603172313.3b2353b0@raksha.tavi.co.uk> In-Reply-To: <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; i386-portbld-freebsd10.1) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAMFBMVEUwXjFLc0vD0cS7y7zw9PDZ4tkWSRaVrZZ+m39qi2tXfVj////7+/utwK4IPggAOAAJUUA7AAABKklEQVQ4jWPYjQMwDFYJp0NKEKCNJmEf9h8CsimXiL2e33s3/e7F7K2Cs3f3dCMkQkMKj4YuCY3K3iR+e7fMaiSjvkX0/5cFGrWpe2uLzOpaExUVqMS/8PX/Re5ey960OLBTZpFA8+IlSBKPQ92zNyUUBsosN58uIY0k8f+/ONCoYytkVuhWzVwNkYiYbqk5M3NmOVBi41YZ8RsGF7shEtFb5KJ3r969CyixM7OTPeFUxG2IxLO8/9/SvqXlc+/x3h295YzLlj2nIRJQj//nRvc5TEIal8RsXBLVuCQwIgoq/u80DomP6HEOk/iOS+IJLonZOCT+ReOQ+Lkbh0QKLonbOCR+7MYhsRqHBJrVcIl/1TgklqKLQyQ+tGKIgyQOqXpjig94diZRAgAXmDX6jyWafAAAAABJRU5ErkJggg====== MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 16:33:19 -0000 On Fri, 3 Jun 2016 17:17:57 +0200 Franco Fichtner wrote: > The initial release was 10.0, which was phased out after a > year, leaving us no choice but to go 10.1 just two months > after our initial release in order to receive official security > updates. Worst case it takes a few months to adapt to the > major transition so that's 12 months minus X months of internal > engineering, depending on your staff expertise. In that case > we started in 2014, took us 4 months, that's 6 months including > the time 10.0 was officially available, so 6 months left for > support, when you actually start adapting to 10 as soon as it > comes out. For many that's a luxury not going to happen. One > can blame anyone for starting late, but it's not going to solve > the real world problem. > > 10.1 went really well. When 10.2 happened for us in January > 2016, however, we've already went testing 3 months before and > had a number of issues that were not being addressed upstream > for a longer amount of time: Why not just use odd numbered releases? That's what I do. They have a longer support cycle. From owner-freebsd-ports@freebsd.org Fri Jun 3 16:44:33 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E306B68E02 for ; Fri, 3 Jun 2016 16:44:33 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.kissl.de (host64.kissl.de [213.239.241.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "*.shmhost.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 343FB180E for ; Fri, 3 Jun 2016 16:44:32 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.homeoffice.local (ipservice-092-217-236-241.092.217.pools.vodafone-ip.de [92.217.236.241]) (Authenticated sender: web104p1) by host64.kissl.de (Postfix) with ESMTPSA id ADC16600C8; Fri, 3 Jun 2016 18:44:30 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: old ports/packages From: Franco Fichtner In-Reply-To: <20160603172313.3b2353b0@raksha.tavi.co.uk> Date: Fri, 3 Jun 2016 18:44:34 +0200 Cc: freebsd-ports@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> <20160603172313.3b2353b0@raksha.tavi.co.uk> To: Bob Eager X-Mailer: Apple Mail (2.3124) X-Virus-Scanned: clamav-milter 0.99 at host64.kissl.de X-Virus-Status: Clean X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 16:44:33 -0000 > On 03 Jun 2016, at 6:23 PM, Bob Eager wrote: > > On Fri, 3 Jun 2016 17:17:57 +0200 > Franco Fichtner wrote: > >> The initial release was 10.0, which was phased out after a >> year, leaving us no choice but to go 10.1 just two months >> after our initial release in order to receive official security >> updates. Worst case it takes a few months to adapt to the >> major transition so that's 12 months minus X months of internal >> engineering, depending on your staff expertise. In that case >> we started in 2014, took us 4 months, that's 6 months including >> the time 10.0 was officially available, so 6 months left for >> support, when you actually start adapting to 10 as soon as it >> comes out. For many that's a luxury not going to happen. One >> can blame anyone for starting late, but it's not going to solve >> the real world problem. >> >> 10.1 went really well. When 10.2 happened for us in January >> 2016, however, we've already went testing 3 months before and >> had a number of issues that were not being addressed upstream >> for a longer amount of time: > > Why not just use odd numbered releases? That's what I do. They have a > longer support cycle. Why release even-numbered at all then? To get better odds? :) On a more serious note, that was actually the bottom line of internal discussions: wait longer, do less. Not sure if this is the best thing for FreeBSD as a whole to let others sit these ones out. Cheers, Franco From owner-freebsd-ports@freebsd.org Fri Jun 3 16:44:55 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52B08B68E79; Fri, 3 Jun 2016 16:44:55 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 110D11986; Fri, 3 Jun 2016 16:44:55 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-qk0-x236.google.com with SMTP id u1so9642610qkh.2; Fri, 03 Jun 2016 09:44:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9d1FkeYGjSB5LAae2kDZmEwHs0/zP2WK4x8QNIQCuj0=; b=boipw1xQNp3hPq+WtVZC8z81k1VxRNQ1qlfmTXMX71GABykHCajd67Uu6KEL44e1Rz FWVwSGCdp6ZYSIXbR+Ati61HHKeHjQh9vPEJa3KfwGcwrvddtPxXRlOoBXRdRVIAW1Ma kQUvRUzqH2ghJALqlAk79tS5pttUyM2PCxv9xNuW9dUJh75UPyF1ySai2NI/pmi99m9U KwWQK/ngm0MoixJvujBvIiNwc8H3rA9F/kJuE18ypMIx1MBf5mtDeJ0c2KKaOxMFp1++ yMlsHPkj/WX4wvg9PpuDsrPbPO5w0ZdWWdYsu92eB9KgvUK2qmCTQJNCjrJNBbgW37mC oK8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=9d1FkeYGjSB5LAae2kDZmEwHs0/zP2WK4x8QNIQCuj0=; b=EFxHl9SbNS19h+iZYTjphSfC7ZiAQdyzQ92jIm+uCRKeirFJtGxPyqm7QtJO7rjorv jEAqiefK2opedqhdR6dEohXcyp6AibyaZq7/HcopUU4anmwzJNn8VVcyrCnA5B8F7NDa FtSf2nFXy48EOYQ3uEizNUBGP0fvlCZ1QEb26Osxg8hyMJkJbi0dS1SJtp82eupcG5qQ ZMR0wJrKE5XtROk5gcBUrYqyA8HWgId9ii30/ydFSGlllGJp5PHFpHpkfoqTy/i4Db05 U7NPna3ObfOy4oMdg/F6v/QkzFCdwHymAwqF7Bu0zDNbvijQ28ZYGNWM9cVeCWX4Ulxj HkxQ== X-Gm-Message-State: ALyK8tIQmX5OyY3fDw5cMvmeOB6Zd61hC7FE+16C3aixPVxBO5M29E2M3TgMCuTPkZd3ZAbYzgaB0k9grZVrww== X-Received: by 10.55.119.66 with SMTP id s63mr4247861qkc.169.1464972294067; Fri, 03 Jun 2016 09:44:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.38.5 with HTTP; Fri, 3 Jun 2016 09:44:53 -0700 (PDT) In-Reply-To: <5b020f89-8f29-5c52-e3de-6c067019b7e9@astart.com> References: <5b020f89-8f29-5c52-e3de-6c067019b7e9@astart.com> From: Freddie Cash Date: Fri, 3 Jun 2016 09:44:53 -0700 Message-ID: Subject: Re: how do you force make install to overwrite conflicting files from another port? To: papowell@astart.com Cc: FreeBSD Ports ML , freebsd-pkg@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 16:44:55 -0000 On Fri, Jun 3, 2016 at 8:26 AM, Patrick Powell wrote: > Suppose that you have a portA which is a dependency of a lot of other > ports. > > You also have a portB which is a replacement/update/upgrade for portA. > > PortB provides replacements for the executables generated/supplied by > PortA but for various reasons you still want to use some of PortA install= ed > items such as libraries, etc. > > I tried doing the following: > > # pkg install PortA > # cd /usr/ports/xxx/PortB > # make install > > Installing PortB... > pkg-static: PortB conflicts with PortA (installs files into the same > place). Problematic file: /usr/local/bin/utilityl > *** Error code 70 > > Is there an option, or a way similar to using 'make FORCE_PGK_REGISTER=3D= YES > install' > to force overwriting the conflicting files? =E2=80=8BSplit portA into multiple ports that install the libraries and bin= aries and what-not separately, then create a meta-port that installs all of the new portA ports. Then create portB and have it CONFLICT with the portA-whatever port so that it's a drop-in replacement (uninstall portA-whatever, install portB).=E2=80= =8B --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-ports@freebsd.org Fri Jun 3 17:53:56 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF4BAB6837A; Fri, 3 Jun 2016 17:53:56 +0000 (UTC) (envelope-from freebsd-ports-local@be-well.ilk.org) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id 8E7B51BB1; Fri, 3 Jun 2016 17:53:56 +0000 (UTC) (envelope-from freebsd-ports-local@be-well.ilk.org) Received: from lowell-desk.lan (router.lan [172.30.250.2]) by be-well.ilk.org (Postfix) with ESMTP id AF7B233C26; Fri, 3 Jun 2016 13:53:37 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id 046C439828; Fri, 3 Jun 2016 13:53:36 -0400 (EDT) From: Lowell Gilbert To: Patrick Powell Cc: FreeBSD Ports ML , freebsd-pkg@freebsd.org Subject: Re: how do you force make install to overwrite conflicting files from another port? References: <5b020f89-8f29-5c52-e3de-6c067019b7e9@astart.com> Date: Fri, 03 Jun 2016 13:53:36 -0400 In-Reply-To: <5b020f89-8f29-5c52-e3de-6c067019b7e9@astart.com> (Patrick Powell's message of "Fri, 3 Jun 2016 08:26:25 -0700") Message-ID: <44poryi2fz.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 17:53:56 -0000 Patrick Powell writes: > Suppose that you have a portA which is a dependency of a lot of other ports. > > You also have a portB which is a replacement/update/upgrade for portA. > > PortB provides replacements for the executables generated/supplied by > PortA but for various reasons you still want to use some of PortA > installed items such as libraries, etc. > > I tried doing the following: > > # pkg install PortA > # cd /usr/ports/xxx/PortB > # make install > > Installing PortB... > pkg-static: PortB conflicts with PortA (installs files into the same > place). Problematic file: /usr/local/bin/utilityl > *** Error code 70 > > Is there an option, or a way similar to using 'make > FORCE_PGK_REGISTER=YES install' > to force overwriting the conflicting files? Not directly, no. The way to do it straight from the ports tree is to remove the "PortA" *first* (with "pkg delete -f"), and then install "PortB". You end up losing the dependency information that PortA had formerly had, but things will work. Upgrade tools (pkg, portmaster, portupgrade, at least) have a "-o" option that fixes up the dependency information. From owner-freebsd-ports@freebsd.org Fri Jun 3 23:18:43 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AC24B6939E for ; Fri, 3 Jun 2016 23:18:43 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E587011E9 for ; Fri, 3 Jun 2016 23:18:42 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [IPv6:2001:7b8:3a7::483a:c84a:9af8:ebbf] (unknown [IPv6:2001:7b8:3a7:0:483a:c84a:9af8:ebbf]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id E4F2C2A2EE; Sat, 4 Jun 2016 01:18:32 +0200 (CEST) Subject: Re: devel/beignet: build error: call to 'abs' is ambiguous insn->extra.longjmp = abs(index - origin) > 800 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: multipart/signed; boundary="Apple-Mail=_CBE950CF-81A6-4182-874F-6FF0A1AB80C3"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.6b2 (ebbf3ef) From: Dimitry Andric In-Reply-To: <20160602222853.085d82f7.ohartman@zedat.fu-berlin.de> Date: Sat, 4 Jun 2016 01:18:19 +0200 Cc: FreeBSD Ports Message-Id: References: <20160602222853.085d82f7.ohartman@zedat.fu-berlin.de> To: "O. Hartmann" X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 23:18:43 -0000 --Apple-Mail=_CBE950CF-81A6-4182-874F-6FF0A1AB80C3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 02 Jun 2016, at 22:28, O. Hartmann = wrote: >=20 > Building/updating port devel/beignet fails with >=20 > [ 42%] Building CXX object = backend/src/CMakeFiles/gbe.dir/llvm/llvm_unroll.cpp.o > [ 42%] Building C object = backend/src/CMakeFiles/gbe.dir/backend/gen/gen_mesa_disasm.c.o > [ 42%] Building CXX object = backend/src/CMakeFiles/gbe.dir/backend/gen_insn_selection.cpp.o > [ 43%] Building CXX object > backend/src/CMakeFiles/gbe.dir/backend/gen_insn_scheduling.cpp.o [ = 43%] Building CXX > object > backend/src/CMakeFiles/gbe.dir/backend/gen_reg_allocation.cpp.o = /usr/ports/lang/beignet/work/Beignet-1.1.2-Source/backend/src/backend/gen_= insn_selection.cpp:1156:27: > error: call to 'abs' is ambiguous insn->extra.longjmp =3D abs(index - = origin) > 800; ^~~ > /usr/include/stdlib.h:83:6: note: candidate function > int abs(int) __pure2; > ^ See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208908 -Dimitry --Apple-Mail=_CBE950CF-81A6-4182-874F-6FF0A1AB80C3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.30 iEYEARECAAYFAldSEEgACgkQsF6jCi4glqPm2ACdFMpvdVMEbO0bkB22olRUB/Xt z4AAoMOImRCug2ISCS+gepPliHu5oXCq =rtMJ -----END PGP SIGNATURE----- --Apple-Mail=_CBE950CF-81A6-4182-874F-6FF0A1AB80C3-- From owner-freebsd-ports@freebsd.org Sat Jun 4 12:52:32 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40429B69277; Sat, 4 Jun 2016 12:52:32 +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]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 045F31819; Sat, 4 Jun 2016 12:52:31 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1b9B42-002VDh-2T>; Sat, 04 Jun 2016 14:52:30 +0200 Received: from x4e348de0.dyn.telefonica.de ([78.52.141.224] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1b9B41-000XSv-Nj>; Sat, 04 Jun 2016 14:52:29 +0200 Date: Sat, 4 Jun 2016 14:52:26 +0200 From: "O. Hartmann" To: FreeBSD Ports , freebsd-x11@freebsd.org Subject: x11/nvidia-driver and CURRENT: update results in full fan blow on MSI GTX 960 Gaming 4G Message-ID: <20160604145226.57dd078e.ohartman@zedat.fu-berlin.de> Organization: FU Berlin X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/DDGh/V2d=dt6cZNf_U29rjq"; protocol="application/pgp-signature" X-Originating-IP: 78.52.141.224 X-ZEDAT-Hint: A X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 12:52:32 -0000 --Sig_/DDGh/V2d=dt6cZNf_U29rjq Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Three months ago I purchased a new GPU to replace a non-UEFI capable GTX560= Ti (MSI). The choice was the MSI GTX 960 Gaming 4G. Apart from the part, that this GPU do= esn't show the performance boost on FreeBSD CURRENT, even with the most recent BLOB from n= Vidia, 367.18, I realized that after the update from FreeBSD 11-CURRENT r300830 to r300956= (I guess, Forgot the exact revision number, but it was > 300950), the fans of that sp= ecific GPU blow at full speed when xdm/Xorg server has been started. This is annoying,= since the noise is incredible. I tried to recompile the whole ports xorg relies on via portmaster -df xorg xdm hoping, that some sort of bug or API incompatibility could have caused the = problems, but that wasn't at all the case. I run now r301300 and the "problem" is still present. The environmental conditions did not change - not in a way that the full sp= eed fan of the GPU could be explained by raised temperatures of the environment. I tried t= o find via Google some help, but it seems that I'm the first and only one having this = problem, especially with FreeBSD and this type of GPU. I also tried the official sup= ported x11/nvidia-driver (346.96 and the proposed 364.19) with no success. Below, You will find some data I picked up from the kernel environment (if = there are other ways, please tell me) and the logfile of Xorg/X server. [...] hw.nvidia.gpus.0.type: PCIe hw.nvidia.gpus.0.uuid: GPU-85fde95a-7974-9962-f1a4-d7c164413929 hw.nvidia.gpus.0.vbios: 84.06.26.00.21 hw.nvidia.gpus.0.irq: 270 hw.nvidia.gpus.0.model: GeForce GTX 960 hw.nvidia.registry.dwords:=20 hw.nvidia.registry.TCEBypassMode: 0 hw.nvidia.registry.MemoryPoolSize: 0 hw.nvidia.registry.EnablePCIeGen3: 1 hw.nvidia.registry.CheckPCIConfigSpace: 4294967295 hw.nvidia.registry.RegisterForACPIEvents: 1 hw.nvidia.registry.MapRegistersEarly: 0 hw.nvidia.registry.EnableMSI: 1 hw.nvidia.registry.UsePageAttributeTable: 4294967295 hw.nvidia.registry.InitializeSystemMemoryAllocations: 1 hw.nvidia.registry.UpdateMemoryTypes: 4294967295 hw.nvidia.registry.DeviceFileMode: 438 hw.nvidia.registry.DeviceFileGID: 0 hw.nvidia.registry.DeviceFileUID: 0 hw.nvidia.registry.ModifyDeviceFiles: 1 hw.nvidia.registry.RmLogonRC: 1 hw.nvidia.registry.ResmanDebugLevel: 4294967295 hw.nvidia.registry.Mobile: 4294967295 hw.nvidia.version: NVIDIA UNIX x86_64 Kernel Module 367.18 Mon May 16 18:= 13:16 PDT 2016 dev.nvidia.0.%parent: vgapci0 dev.nvidia.0.%pnpinfo:=20 dev.nvidia.0.%location:=20 dev.nvidia.0.%driver: nvidia dev.nvidia.0.%desc: GeForce GTX 960 dev.nvidia.%parent:=20 Hopefully someone can give some hints what could trigger the problem ... Thanks in advance and please CC me (due to not subscribing this list). Kind regards, Oliver --Sig_/DDGh/V2d=dt6cZNf_U29rjq Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXUs8LAAoJEOgBcD7A/5N8zlEH/0zUYxjzLOBd8JuCUG58iuiW mT6bb+7wDnjUsEUwlxUJiB9nKb7AqyqCb7PdxrqYJWyJsdtrk1r1WbAHhAueehYY 3E/A6CkY/gsgLRifpMagwmpIHy31c2QLjEUX8iNf5na9QpsIxbPUlPL5jpKsdXl3 Mncbk1ODNvePqi2NgAmE06tomkG8dwJYwMejLj4avaaIqJsnd8tjACMqsGBH9MkU Nz2gvFZnwA/KzgFmgbSLfWaLw3Nj+5GHeSF/7oRfqDUorvFBi21SeAh0icdhmo91 +REnfFJpi+XpJexAxo9HGV0KFK65UpYPiFNWx/3LLNkGxCVnxEZMj+qtdZsizDY= =rNcL -----END PGP SIGNATURE----- --Sig_/DDGh/V2d=dt6cZNf_U29rjq-- From owner-freebsd-ports@freebsd.org Sat Jun 4 13:45:54 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 728B7B690B0 for ; Sat, 4 Jun 2016 13:45:54 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D5E01F20 for ; Sat, 4 Jun 2016 13:45:53 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 5433AC868 for ; Sat, 4 Jun 2016 13:45:44 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/5433AC868; dkim=none; dkim-atps=neutral Subject: Re: old ports/packages To: freebsd-ports@freebsd.org References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> <20160603172313.3b2353b0@raksha.tavi.co.uk> From: Matthew Seaman Message-ID: Date: Sat, 4 Jun 2016 14:45:37 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <20160603172313.3b2353b0@raksha.tavi.co.uk> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="WhX6DkbenHvleneq4iwBgEeTVSeEGmRRT" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 13:45:54 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --WhX6DkbenHvleneq4iwBgEeTVSeEGmRRT Content-Type: multipart/mixed; boundary="NoNG7XCR5mj6gPEhq7gs2shF7KFwOTQrw" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: Subject: Re: old ports/packages References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> <20160603172313.3b2353b0@raksha.tavi.co.uk> In-Reply-To: <20160603172313.3b2353b0@raksha.tavi.co.uk> --NoNG7XCR5mj6gPEhq7gs2shF7KFwOTQrw Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 03/06/2016 17:23, Bob Eager wrote: > Why not just use odd numbered releases? That's what I do. They have a > longer support cycle. Remember though that this model is changing with 11.0 release. With the new model, it's the 11.x family as a whole that has the long term support and individual releases such as 11.0 or 11.1 will cease to be supported very shortly after the next release in that series comes out. The last release in that series will then have a long support life so that 11.x as a whole has something like a 5 year lifecycle[*]. The transitions from 11.0 -> 11.1 -> 11.2 -> ... are meant to be something you could apply pretty much routinely; much as you'ld apply a new patch-level today. Cheers, Matthew [*] which is pretty much the same length as the the lifecycle of previous major branches has been up to now. --NoNG7XCR5mj6gPEhq7gs2shF7KFwOTQrw-- --WhX6DkbenHvleneq4iwBgEeTVSeEGmRRT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXUtuIXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkAT+4IP/jraN0eKstwzoWf47AtbvrpJ gQ2X7X3uOBb0/2Z1esNf4JNQ9N7ajGpWL+fuOZlTi7p80Elh0NWG5PEbI4pp97r0 M8RFXHrzEbB7Np7C7LjQFJR8zV0Bk5C803KlCtbCKb1sVbRU1UjwQoT5KjMiIk/q F+ZPOt6IURfgyWM2o2qz5+N2XRVRGcqVHuUq74r8b6f4H0BAiwZTrAAJmH2oTeqU uePCBe7easzyF7k+wXhuGp5YRHkff/pOgiUWmjZ0XQmA6RNG20PskxihwvWy6IW9 jw8ewV0Nnpbb9ngo6dVmt5q35tiGiuYnsjqQXiZ1lXD32ghxahHrmhkA1UItgvBV 8Z2jYPI6vt+ZaezNcQF6Yo8pGNqTlFcfBtYpagf+7SjKYiYeuOG8o9uuNP8QVRam 2pctUS3noUx6oyxWQXcvIOAkgsCDU57QW13ChO/YquHtkfACpMQKfIrTdBRn5hI/ 1X2deFc9f3m1ETp6grsaN7BPAbSnxXeZXp5kS5qRK3uE51fwIS7WWNy94ZppElO1 O0aZ1fjv8ZGuRoQfCGQQym8N1ezj8kTtrMoHDn1RoB3vLIwU3OvCPNXa/misQVar CGLgUxr8NpFtSnt7a91zgVtf9XF64gf61LjAYknNPPqEVPnjsNFWxv1BgORbL83R IxzyfHWlJJD7b/hPg2wN =5fdp -----END PGP SIGNATURE----- --WhX6DkbenHvleneq4iwBgEeTVSeEGmRRT-- From owner-freebsd-ports@freebsd.org Sat Jun 4 13:50:51 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D32FFB69180 for ; Sat, 4 Jun 2016 13:50:51 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [185.24.122.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 772451093 for ; Sat, 4 Jun 2016 13:50:50 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from crayon2.yoonka.com (crayon2.yoonka.com [192.168.1.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id u54Doh4a005072 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sat, 4 Jun 2016 13:50:43 GMT (envelope-from list1@gjunka.com) Subject: Re: old ports/packages To: freebsd-ports@freebsd.org References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> <20160603172313.3b2353b0@raksha.tavi.co.uk> From: Grzegorz Junka Message-ID: Date: Sat, 4 Jun 2016 13:50:43 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 13:50:51 -0000 On 04/06/2016 13:45, Matthew Seaman wrote: > On 03/06/2016 17:23, Bob Eager wrote: >> Why not just use odd numbered releases? That's what I do. They have a >> longer support cycle. > Remember though that this model is changing with 11.0 release. With the > new model, it's the 11.x family as a whole that has the long term > support and individual releases such as 11.0 or 11.1 will cease to be > supported very shortly after the next release in that series comes out. > The last release in that series will then have a long support life so > that 11.x as a whole has something like a 5 year lifecycle[*]. The > transitions from 11.0 -> 11.1 -> 11.2 -> ... are meant to be something > you could apply pretty much routinely; much as you'ld apply a new > patch-level today. > > Cheers, > > Matthew > > [*] which is pretty much the same length as the the lifecycle of > previous major branches has been up to now. > Is there somewhere any more information available about this change? Cheers Greg From owner-freebsd-ports@freebsd.org Sat Jun 4 14:00:38 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 773CEB69315; Sat, 4 Jun 2016 14:00:38 +0000 (UTC) (envelope-from papowell@astart.com) Received: from astart2.astart.com (wsip-72-214-30-30.sd.sd.cox.net [72.214.30.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6182C14E4; Sat, 4 Jun 2016 14:00:37 +0000 (UTC) (envelope-from papowell@astart.com) Received: from laptop_103.private (localhost [127.0.0.1]) by astart2.astart.com (8.14.9/8.14.9) with ESMTP id u54DxKmm079718; Sat, 4 Jun 2016 06:59:20 -0700 (PDT) (envelope-from papowell@astart.com) Reply-To: papowell@astart.com Subject: Re: how do you force make install to overwrite conflicting files from another port? References: <5b020f89-8f29-5c52-e3de-6c067019b7e9@astart.com> <44poryi2fz.fsf@lowell-desk.lan> To: Lowell Gilbert Cc: FreeBSD Ports ML , freebsd-pkg@freebsd.org From: Patrick Powell Organization: Astart Technologies Message-ID: Date: Sat, 4 Jun 2016 06:59:20 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <44poryi2fz.fsf@lowell-desk.lan> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 14:00:38 -0000 On 06/03/16 10:53, Lowell Gilbert wrote: > Patrick Powell writes: > >> Suppose that you have a portA which is a dependency of a lot of other ports. >> >> You also have a portB which is a replacement/update/upgrade for portA. >> >> PortB provides replacements for the executables generated/supplied by >> PortA but for various reasons you still want to use some of PortA >> installed items such as libraries, etc. >> >> I tried doing the following: >> >> # pkg install PortA >> # cd /usr/ports/xxx/PortB >> # make install >> >> Installing PortB... >> pkg-static: PortB conflicts with PortA (installs files into the same >> place). Problematic file: /usr/local/bin/utilityl >> *** Error code 70 >> >> Is there an option, or a way similar to using 'make >> FORCE_PGK_REGISTER=YES install' >> to force overwriting the conflicting files? > Not directly, no. The way to do it straight from the ports tree is to > remove the "PortA" *first* (with "pkg delete -f"), and then install > "PortB". You end up losing the dependency information that PortA had > formerly had, but things will work. > > Upgrade tools (pkg, portmaster, portupgrade, at least) have a "-o" > option that fixes up the dependency information. > When you do the 'pkg delete -f PortA' then it will also delete the libraries installed by PortA. if you do 'cd ...PortB; make install' and it will now install the files that were in conflict, but there are now some libraries installed by PortA which are missing. I understand that this is on the outskirts of package/port management, but there are times when you want to install a test version of a utility which has only part of the functionality of another port. -- Patrick Powell Astart Technologies papowell@astart.com 1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting 858-874-6543 FAX 858-751-2435 Web: www.astart.com From owner-freebsd-ports@freebsd.org Sat Jun 4 14:18:35 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7699BB69DED for ; Sat, 4 Jun 2016 14:18:35 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 16EA21A8F for ; Sat, 4 Jun 2016 14:18:34 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (liminal.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3636:3bff:fed4:b0d6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 2206B10081 for ; Sat, 4 Jun 2016 14:18:31 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/2206B10081; dkim=none; dkim-atps=neutral Subject: Re: old ports/packages To: freebsd-ports@freebsd.org References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> <20160603172313.3b2353b0@raksha.tavi.co.uk> From: Matthew Seaman Message-ID: <2d6eddea-0de7-6963-c1ca-a734aaa5a75a@FreeBSD.org> Date: Sat, 4 Jun 2016 15:18:15 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="RNcpdXWm47Hmdhn1HoEj8Tc9vp51TTqtG" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 14:18:35 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --RNcpdXWm47Hmdhn1HoEj8Tc9vp51TTqtG Content-Type: multipart/mixed; boundary="t97Tjei93OxkLL1E2d8IfHrMeGbvvLxGm" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: <2d6eddea-0de7-6963-c1ca-a734aaa5a75a@FreeBSD.org> Subject: Re: old ports/packages References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> <20160603172313.3b2353b0@raksha.tavi.co.uk> In-Reply-To: --t97Tjei93OxkLL1E2d8IfHrMeGbvvLxGm Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 04/06/2016 14:50, Grzegorz Junka wrote: >=20 > On 04/06/2016 13:45, Matthew Seaman wrote: >> On 03/06/2016 17:23, Bob Eager wrote: >>> Why not just use odd numbered releases? That's what I do. They have a= >>> longer support cycle. >> Remember though that this model is changing with 11.0 release. With t= he >> new model, it's the 11.x family as a whole that has the long term >> support and individual releases such as 11.0 or 11.1 will cease to be >> supported very shortly after the next release in that series comes out= =2E >> The last release in that series will then have a long support life so >> that 11.x as a whole has something like a 5 year lifecycle[*]. The >> transitions from 11.0 -> 11.1 -> 11.2 -> ... are meant to be something= >> you could apply pretty much routinely; much as you'ld apply a new >> patch-level today. >> >> Cheers, >> >> Matthew >> >> [*] which is pretty much the same length as the the lifecycle of >> previous major branches has been up to now. >> >=20 > Is there somewhere any more information available about this change? >=20 https://lists.freebsd.org/pipermail/freebsd-announce/2015-February/001624= =2Ehtml https://news.ycombinator.com/item?id=3D8991960 Cheers, Matthew --t97Tjei93OxkLL1E2d8IfHrMeGbvvLxGm-- --RNcpdXWm47Hmdhn1HoEj8Tc9vp51TTqtG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXUuMuXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATm1UP/jT4ytjXOHmOFvx/tj3y4V3J eqUW59FllxsLmr55I+Db2PZ3S9CJ6EKUkW7hHRpIxiYSZrOqmDAcsmMB9rJKlRAG OjZWSBXmYGgnWMlcFV1tqIDy7kisT0TosW/OjK+LTS012EMU+xflh9TNjhFeuP9+ /kjGIJfCtVB8udQGhg3wrChq5yDq7m+mDIYlMGgsKc54g2bP+zg98GR7LPb7KqT3 CPd2Oz2rd5B52KVk18nQAT9etRWKS5+4QyrvtPyf4xNrY7JElbOZllAn1To10Aup +QYbnIArMboF10GCut9/zXaEJx8HOUmgs+1WCQX8xfe0ie3I7YHLGMQvqJPu7Lz7 PE5cFiWDP09hS+V4au0nNH73Eju36AgSsvCTsJl1Zujc07xzmXZgJKvI73D+z0J2 95JwvS+oAn0aSEdEG+0YfBPRgD7RFSDQiFDU9z/1x3ZivpbTkdWkThnKypl0l5hf N2zC6h4gFZHHMcSTogeyTiZwbhc524WPMUJTWj17hm8JxVRHKvkIAtdPzeI5XFh9 8myZmPyj09rR8VWd5iejBA7yBFvHeqgkx0fO7n0SBYRuKfLaqyjaXZe9FKPl6dLR T3tQeg9oDG9XjdDTEAowV9llSTVQuL0nrHTegzfgY2buSp3mLly1Bk2e+zhXaDQi G9JY00ggYLDU4I/KGtgG =/cKF -----END PGP SIGNATURE----- --RNcpdXWm47Hmdhn1HoEj8Tc9vp51TTqtG-- From owner-freebsd-ports@freebsd.org Sat Jun 4 15:15:56 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BA2B0B69A92 for ; Sat, 4 Jun 2016 15:15:56 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 86D0A1FB2 for ; Sat, 4 Jun 2016 15:15:56 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-209-65.knology.net [216.186.209.65] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id u54FFmgm023668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sat, 4 Jun 2016 10:15:49 -0500 Subject: Re: old ports/packages To: freebsd-ports@freebsd.org References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> <20160603172313.3b2353b0@raksha.tavi.co.uk> <2d6eddea-0de7-6963-c1ca-a734aaa5a75a@FreeBSD.org> From: "William A. Mahaffey III" Message-ID: <3ae2f03e-2753-0a75-0123-9f85c05b0eaf@hiwaay.net> Date: Sat, 4 Jun 2016 10:21:18 -0453.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <2d6eddea-0de7-6963-c1ca-a734aaa5a75a@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 15:15:56 -0000 On 06/04/16 09:24, Matthew Seaman wrote: > On 04/06/2016 14:50, Grzegorz Junka wrote: >> On 04/06/2016 13:45, Matthew Seaman wrote: >>> On 03/06/2016 17:23, Bob Eager wrote: >>>> Why not just use odd numbered releases? That's what I do. They have a >>>> longer support cycle. >>> Remember though that this model is changing with 11.0 release. With the >>> new model, it's the 11.x family as a whole that has the long term >>> support and individual releases such as 11.0 or 11.1 will cease to be >>> supported very shortly after the next release in that series comes out. >>> The last release in that series will then have a long support life so >>> that 11.x as a whole has something like a 5 year lifecycle[*]. The >>> transitions from 11.0 -> 11.1 -> 11.2 -> ... are meant to be something >>> you could apply pretty much routinely; much as you'ld apply a new >>> patch-level today. >>> >>> Cheers, >>> >>> Matthew >>> >>> [*] which is pretty much the same length as the the lifecycle of >>> previous major branches has been up to now. >>> >> Is there somewhere any more information available about this change? >> > https://lists.freebsd.org/pipermail/freebsd-announce/2015-February/001624.html > > https://news.ycombinator.com/item?id=8991960 > > Cheers, > > Matthew > > One point of order if I may: It was stated earlier in the thread that binary compatibility throughout a major release cycle (X.n-R, as 'n' varies) is a specification. That is not explicitly addressed in the above URL's, as far as I can see. Is that indeed considered a specification ? If so, it would seem to satisfy the LTS desire implicitly. TIA & have a good one. -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. From owner-freebsd-ports@freebsd.org Sat Jun 4 17:20:37 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 118B9B69CCF for ; Sat, 4 Jun 2016 17:20:37 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 918321D72 for ; Sat, 4 Jun 2016 17:20:35 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from zero-gravitas.local (vpn-1.adestra.com [46.236.37.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id DCA8110209 for ; Sat, 4 Jun 2016 17:20:30 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/DCA8110209; dkim=none; dkim-atps=neutral Subject: Re: old ports/packages To: freebsd-ports@freebsd.org References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> <20160603172313.3b2353b0@raksha.tavi.co.uk> <2d6eddea-0de7-6963-c1ca-a734aaa5a75a@FreeBSD.org> <3ae2f03e-2753-0a75-0123-9f85c05b0eaf@hiwaay.net> From: Matthew Seaman Message-ID: <57530DD8.9070605@FreeBSD.org> Date: Sat, 4 Jun 2016 18:20:24 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <3ae2f03e-2753-0a75-0123-9f85c05b0eaf@hiwaay.net> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="fw90bAwigfvt3xjLBoS3BdTo2cHENrlJ2" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 17:20:37 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --fw90bAwigfvt3xjLBoS3BdTo2cHENrlJ2 Content-Type: multipart/mixed; boundary="8C4FUHfiQJvetMcSqkCacEXrRWpXXIcJ6" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: <57530DD8.9070605@FreeBSD.org> Subject: Re: old ports/packages References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> <20160603172313.3b2353b0@raksha.tavi.co.uk> <2d6eddea-0de7-6963-c1ca-a734aaa5a75a@FreeBSD.org> <3ae2f03e-2753-0a75-0123-9f85c05b0eaf@hiwaay.net> In-Reply-To: <3ae2f03e-2753-0a75-0123-9f85c05b0eaf@hiwaay.net> --8C4FUHfiQJvetMcSqkCacEXrRWpXXIcJ6 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2016/06/04 16:14, William A. Mahaffey III wrote: > One point of order if I may: It was stated earlier in the thread that > binary compatibility throughout a major release cycle (X.n-R, as 'n' > varies) is a specification. That is not explicitly addressed in the > above URL's, as far as I can see. Is that indeed considered a > specification ? If so, it would seem to satisfy the LTS desire > implicitly. TIA & have a good one. At the moment we have a guarantee of binary compatibility for any software compiled on release X.n to be able to run on any release X.m where m >=3D n. This is not going to change with the new support model. ie. Something compiled for 11.0 will run on any subsequent 11.x release, but something compiled on 11.3 (say) would not necessarily run on 11.2. Now, in fact, that sort of backwards compatibility usually does work, but it isn't guaranteed. Putting in this sort of backwards incompatible change is something that is avoided unless there is some very good reason to introduce it. Also recognize that libc.so in 11.x will support ABI multi-versions -- so you can run anything that needs an earlier ABI version without any special configuration[*]. This does not apply to all of the shlibs provided by the system, so you may get mixed results depending on what your applications link against. This is why the FreeBSD packages are always built on the earliest still supported release from the same major branch. The difference implied by the new support model is that the package building machines would be updated more frequently as they track the earliest still-supported release. Practically speaking, as a pkg user you're unlikely to experience any difficulties even if you aren't up to date with your OS patching, but there may be some rare occasions where you will need to update your OS before you can update your ports. Cheers, Matthew [*] IIRC the available version history goes back to 10.0-RELEASE; you'll definitely need compat libs for anything compiled earlier than that, but you may well be able to run 10.x applications on an 11.x system with no compatibility shims required. --8C4FUHfiQJvetMcSqkCacEXrRWpXXIcJ6-- --fw90bAwigfvt3xjLBoS3BdTo2cHENrlJ2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJXUw3dXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnMt4P/Aq+/RzOjTChaWj4iVd1Z43r aacXu12oweWB9SUP+PQi58/uEXw+SByMEJMgn7gX5yPTk6/ukn0D7p5SEPSNRGaq aRMCIQsU9RYKCushIxOtVOieCKfriflZdTRBwPOviCehzXDRLCzExT3a/6n91JZT KVpuf3qJDOk/C6AbG7p37gkA7o+1DlTB8YE78ZZSGt2K76V71mW5+TxI/+4dr3se E6hzYcIKJv3CrwvRhsydQ9TsQ1Tuy2x1FxVXiyP1akvqouK5Un8+GdA+33vGldXa BiGZ+NlYx0OvCoep+LCGUQRWSFy13BnvxYRcaK2Alunj3vWs4yI3Mg6fLzIBjClU WOG6rchQJgRqhRBQyr9JkRD0tK/LmJddxf66nddz6mn+2vo3RqocOOuHQTjWCAfP KZ6SFZuHt85s8GsqT7FWpt0HXMAFnbGVA+Dyzokhd7Ho8HnP5WC7O5OSnNuGMbPJ CX06xj9aVurmkxDer+0pTCcm6XQlcvigie4z9iR6DsdUXkMtdM9KzDwSGRACQSYe 6p98ldn/dvvzY+5pq6Tq6abtGP/9d3JizTkP4C4TX2B/uNy7I7/BhoCoHX1RL+tw xv6jxIq/QY5oIsVvA5rIm2Bkz4W5eqtad8cMrXi+Zyd72nl+uuyAgtX66sI3fouv J5sAP4GKpFPm0VlkUAQc =IJxm -----END PGP SIGNATURE----- --fw90bAwigfvt3xjLBoS3BdTo2cHENrlJ2-- From owner-freebsd-ports@freebsd.org Sat Jun 4 17:55:25 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9665B6AA96 for ; Sat, 4 Jun 2016 17:55:25 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 81AC2110A; Sat, 4 Jun 2016 17:55:25 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u54HtJSi075547 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 4 Jun 2016 20:55:20 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u54HtJSi075547 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u54HtJRJ075546; Sat, 4 Jun 2016 20:55:19 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 4 Jun 2016 20:55:19 +0300 From: Konstantin Belousov To: Matthew Seaman Cc: freebsd-ports@freebsd.org Subject: Re: old ports/packages Message-ID: <20160604175519.GC38613@kib.kiev.ua> References: <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> <20160603172313.3b2353b0@raksha.tavi.co.uk> <2d6eddea-0de7-6963-c1ca-a734aaa5a75a@FreeBSD.org> <3ae2f03e-2753-0a75-0123-9f85c05b0eaf@hiwaay.net> <57530DD8.9070605@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57530DD8.9070605@FreeBSD.org> User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 17:55:25 -0000 On Sat, Jun 04, 2016 at 06:20:24PM +0100, Matthew Seaman wrote: > On 2016/06/04 16:14, William A. Mahaffey III wrote: > > One point of order if I may: It was stated earlier in the thread that > > binary compatibility throughout a major release cycle (X.n-R, as 'n' > > varies) is a specification. That is not explicitly addressed in the > > above URL's, as far as I can see. Is that indeed considered a > > specification ? If so, it would seem to satisfy the LTS desire > > implicitly. TIA & have a good one. > > At the moment we have a guarantee of binary compatibility for any > software compiled on release X.n to be able to run on any release X.m > where m >= n. This is not going to change with the new support model. > > ie. Something compiled for 11.0 will run on any subsequent 11.x release, > but something compiled on 11.3 (say) would not necessarily run on 11.2. > Now, in fact, that sort of backwards compatibility usually does work, > but it isn't guaranteed. Putting in this sort of backwards incompatible > change is something that is avoided unless there is some very good > reason to introduce it. > > Also recognize that libc.so in 11.x will support ABI multi-versions -- > so you can run anything that needs an earlier ABI version without any > special configuration[*]. This does not apply to all of the shlibs > provided by the system, so you may get mixed results depending on what > your applications link against. We ship libc.so+libpthread.so+libm.so+rtld which support backward compatibility up to FreeBSD 7.0. This means that the 'core' C runtime is ABI-stable. It is not true for the less 'core' FreeBSD shlibs indeed, but that other libraries are typically OS-depended and are used for system management or configuration. More severe cause of ABI breakage are the third-party shlibs, which ABI is not maintained by the project and which updates cause at least incompatible shlib version bumps. Examples are openssl and ncurses. This explains the reason why the packages are still have to be build per major branch. > > This is why the FreeBSD packages are always built on the earliest still > supported release from the same major branch. The difference implied by > the new support model is that the package building machines would be > updated more frequently as they track the earliest still-supported > release. Practically speaking, as a pkg user you're unlikely to > experience any difficulties even if you aren't up to date with your OS > patching, but there may be some rare occasions where you will need to > update your OS before you can update your ports. > > Cheers, > > Matthew > > [*] IIRC the available version history goes back to 10.0-RELEASE; you'll > definitely need compat libs for anything compiled earlier than that, but > you may well be able to run 10.x applications on an 11.x system with no > compatibility shims required. > From owner-freebsd-ports@freebsd.org Sat Jun 4 18:48:19 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF8A3B6A2EA for ; Sat, 4 Jun 2016 18:48:19 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from nm44-vm10.bullet.mail.bf1.yahoo.com (nm44-vm10.bullet.mail.bf1.yahoo.com [216.109.115.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 79D9718BB for ; Sat, 4 Jun 2016 18:48:19 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1465065987; bh=fluf48cX30cb3x+Lc0dXGvvDNvtXTSWp8tLYj2MzxGA=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From:Subject; b=cOkna7iBOXNMOwQ+ryWV3rraeLoalNx2mDv4LeLHiSZJZpasY4fSN1TCjhLrethrh3Cwftzz+TJepNQnur98/WshGZ70i02Ghpe5PX3xnzDWsc/XInOvKhEy/bkGktWkIyZIJiYtcgVGqQR0RKhAdM4U9kekpHSICj+GG02Ua1FaKfwpgWh7h57K6o3y9v3f6RczadK6clJcIdnVvQw8VKxkaeAop5sGiB6iqicT7Q1/pDh33GsOzto0JQ4FKPriAZjaGHDVS1fbsjjy0PXhRbzEDowxEi62F8EzHcVsf1flRhPdpzX4tnlnIatk3qDAdWLTKzA1+7LP2/w0/v+/aA== Received: from [98.139.170.178] by nm44.bullet.mail.bf1.yahoo.com with NNFMP; 04 Jun 2016 18:46:27 -0000 Received: from [98.139.211.203] by tm21.bullet.mail.bf1.yahoo.com with NNFMP; 04 Jun 2016 18:46:27 -0000 Received: from [127.0.0.1] by smtp212.mail.bf1.yahoo.com with NNFMP; 04 Jun 2016 18:46:26 -0000 X-Yahoo-Newman-Id: 992798.60923.bm@smtp212.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: Ki_UfrQVM1kGMM4Fzdv6vC14SJumo0via898g9ytn0eZ_ul MVHfoQh5VNS67RLGkdMNmuIPOar.QAqdgr3afZ5u9JDOdEK305HzAiDFI2P5 lqoQ3VtT810DRJdksngciQbAP0WfsFYe7z9tQtzsTK6W1W2YGTAYWkndsMwM QHkqP7X1CQtdEaEpwqpNlRbcuvIpmhL9rQTguzkyPL2FYRjkSLslBZd5FXuO Tu8hPiwecqEp4NPESGAd9A7Q6ZEwDELDW0Qex5Nn947Q5PG7i65MVjZF.tfG 4lOgMYcQ8Dyxjfi9xPp4wrBKDZmPuZKbyuq.3GGMo.7BXWW5jLJOb7ZC8.YC k5qpJ7mDcMn5A2vKv8256oeqT3nhovD8owvbedhPgZG0Y6W6OPQjEI9UvDKx ALnkzV1vm2AP_lB4khDkeHFsSeGr6CiYH6N5rB0v8Dh0GPRPXlyQCzScOM9u 4QhUilruxy4tlP9W5ZrGTdKowQuaF_JILqAwcAuPX2vBb4QXuGyIKJrK2zh5 C3L55G1xQfXS.iuuuZPOQpwhv9o0kl5flYoyqcw-- X-Yahoo-SMTP: 6IZaPQyswBAeyzp3urHRlQfBxGxx4Js3YAIn Subject: Re: old ports/packages To: Franco Fichtner , Miroslav Lachman <000.fbsd@quip.cz> References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> Cc: freebsd-ports@freebsd.org, Torsten Zuehlsdorff , Vincent Hoffman-Kazlauskas From: Jeffrey Bouquet Message-ID: <12b50783-f79b-56b6-25f8-91e23a902776@yahoo.com> Date: Sat, 4 Jun 2016 11:46:24 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 18:48:19 -0000 On 06/ 3/16 08:17 AM, Franco Fichtner wrote: > Hi there, > >> On 01 Jun 2016, at 2:12 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >> >> There is a main difference - if you upgraded from 9.2 to 9.3, you don't need to recompile (reinstall) all ports, but if you upgraded from 9.3 to 10.x you need to reinstall all your packages and then remove old 9.x libraries from the base system. >> On 01 Jun 2016, at 2:12 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >> >> There is a main difference - if you upgraded from 9.2 to 9.3, you don't need to recompile (reinstall) all ports, but if you upgraded from 9.3 to 10.x you need to reinstall all your packages and then remove old 9.x libraries from the base system. > This is very much true for a single user point of view, but > the devil is in the details. Let's go through the transition > that we as the OPNsense project went through in the FreeBSD 10 > series... Not a rant, just facts. > > The initial release was 10.0, which was phased out after a > year, leaving us no choice but to go 10.1 just two months > after our initial release in order to receive official security > updates. Worst case it takes a few months to adapt to the > major transition so that's 12 months minus X months of internal > engineering, depending on your staff expertise. In that case > we started in 2014, took us 4 months, that's 6 months including > the time 10.0 was officially available, so 6 months left for > support, when you actually start adapting to 10 as soon as it > comes out. For many that's a luxury not going to happen. One > can blame anyone for starting late, but it's not going to solve > the real world problem. > > 10.1 went really well. When 10.2 happened for us in January > 2016, however, we've already went testing 3 months before and > had a number of issues that were not being addressed upstream > for a longer amount of time: > > o HyperV disks stopped registering as ada(4) devices, killing > installs that were not using labels. Never fixed. > > o Hyper-V NAT broken for a very long time, only fixed in 10.2 > after active polling for an errata[1] > > o pf checksumming broke with offloading[2] > > But the kicker was that building pkg on 10.2 suddenly changed > the ABI behaviour in at least two ways that we know of: > > (1) The reaper for package scripts was now suddenly active, > making it a lot harder to restart a service on package upgrade > from their own scripts. We hat do investigate and disable the > reaper code in pkg itself in order to retain functionality. I > would think that others ran into this silently as well. > > (2) 10.1 systems preloading the "new" pkg for 10.2 were unable > to upgrade certain packages, in this instance isc-dhcp43-*. > It took a few months to even get to the point of triggering > this. In short, we pinned down the pkg ABI to 10.1[3] in order > to allow our older 10.1 systems to upgrade. This should not be > happening in a "ABI stable" environment. There is pkg-static, > but at least in the scope of FreeBSD it's only used when pkg > fails for this or that reason, which is very hard to explain to > a GUI or backend script. Why not make it the default? > > 10.2 was the proverbial rollercoaster ride that some would not > like to see repeated. 10.3 looks better, but what does that say > about 10.4 or 11.0? > > But 10.3 already had a major speed regression during package > installation only caught after the release[4]. Who knows what > our users will be facing once we go live in a few months. > > For downstream projects, this is at least an order of magnitude > worse than the simple user that sits in a shell and runs a magical > fix command to amend its upgrade path. fir some it's even impossible > to get into a shell. Most of downstream projects have automated > processes, upgrade features that rely on certain behaviour, well, > rely on behaviour to stay stable for at least 10.x, which would > make sense. ;) > > And now we run for each 10.x, every time just run for it in order > to make sure that we're not missing an iteration that would amplify > the problems we'll be facing with upgrading later. > > And mind you, this is *with* rebuilding everything from scratch > for each minor update just to be on the safe side. :) > > > Cheers, > Franco > > -- > [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203630 > [2] https://www.freebsd.org/security/advisories/FreeBSD-EN-16:02.pf.asc > [3] https://github.com/opnsense/ports/commit/76975890103 > [4] https://www.freebsd.org/security/advisories/FreeBSD-EN-16:06.libc.asc > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" I again wonder whether the old /var/db/pkg [ flat files rather than an ABI ] could serve as a secondary means to the pkg upgrade of port/packages that was problematic [above], reverse engineered back into place with say, portmanager [deprecated] and portupgrade and portmanager, so that if machines in production fail some way due to pkg, the older way would suffice for awhile, and on such machines in production, each upgrade would entail both methods, and in case the preferred one fails, somewhat like HAST or ZFS or Carp, the backup methodology to keep the services up after downtime could strengthen the case for FreeBSD vs other OS which only use a singular method, I know if I were much younger I'd set about learning C again and proceeding apace... all else being more favorable than is usually the case, of course, unless I thought of some easier way than /var/db/pkg once having learned sqlite3, of which I remain unlearned. From owner-freebsd-ports@freebsd.org Sat Jun 4 18:50:22 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A03FEB6A418 for ; Sat, 4 Jun 2016 18:50:22 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from nm45-vm1.bullet.mail.bf1.yahoo.com (nm45-vm1.bullet.mail.bf1.yahoo.com [216.109.115.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 62F8E1A49 for ; Sat, 4 Jun 2016 18:50:22 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1465066215; bh=6ADHnl8EELmDg7kDBlfTKeIY0pShZB+xQVX4G97GapI=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From:Subject; b=StBSrFdQLd2IPf+Q3YqlvDVEG/rNzTabTxMjpXlrfUIiK3Cx53/egX75gUkw90dJcSUDSseF9rOEBTWukORvhZX41PzgQSss25FJtn6S0un8KOIa//oh3SpGDamItnAsvBl8cYvvl0e/qDkD6HIJAgNssT8vkkr/HM7ezByxm0QcggEIYMDsV+tBe2pKOil2Ut6qvQZBLLPbpO/sQne9gecIhmheNFirjYCZaseNsgLs+g9SZdVa7Q9DC6lwcECo/nmeEBwWCWKJVvRCmyZrFvnpm/PlFC0XUfjubV8DdcO2tyn4cnofdj9xhRSXDBUd6LSq74KU3VChOz71gBnMVQ== Received: from [66.196.81.171] by nm45.bullet.mail.bf1.yahoo.com with NNFMP; 04 Jun 2016 18:50:15 -0000 Received: from [98.139.211.203] by tm17.bullet.mail.bf1.yahoo.com with NNFMP; 04 Jun 2016 18:50:15 -0000 Received: from [127.0.0.1] by smtp212.mail.bf1.yahoo.com with NNFMP; 04 Jun 2016 18:50:15 -0000 X-Yahoo-Newman-Id: 113391.79630.bm@smtp212.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: MYsj4r0VM1mBljJCN0.H66VX19_wUBwW0a2WcASew5olKpn EA4ppm3fiqTSwpETfFIgVFOsgHvsbZAvd5YvdahLrTkKIHhVqR5Ko4R5XaIR JdsRsRCtj.F9y5iLKNxJlsQhnQeOU18_S8To5vcxC8VEiGhzOddUoH75.ax_ KlzFzqfCOibLmXC5AxMRFA8290IKJ7ZRf9yLTslw.ZxXeLVg49YFrO6z8_hA XOssAEkxXC4K6WDsU3rmZHZaZPgWYHk6sdE_9VBOL74FasdUnzxGcJPOf2vX 99EQKC5DgSq0BfTxT3qwwhMxJ5X_JSMGtKxHxVto8c.vraskhVFCL2Kh0Q0n AfN0u2GaaoYeETl4jTcmXYGt_fZcge8ftfuoMKYUPL0MP2eXd3A3DNlrsqio 1VwkUWYNV1yJTccIewdWSBqIZAOZWZgkpd1Kfcwl0WQElngQVQ58e1rJ_RKG eiwA6Sch2S3uSs5E5feecWNannzO62VzjTv93bRl95N_ktvGZ02YTRiIDuAQ lxXXhPIWmNYfwm832kOnqzAIdCMpnH6zrug2qAA-- X-Yahoo-SMTP: 6IZaPQyswBAeyzp3urHRlQfBxGxx4Js3YAIn Subject: Re: old ports/packages To: Franco Fichtner , Miroslav Lachman <000.fbsd@quip.cz> References: <03cc4012-026e-c007-09e1-ee45524f1b95@elischer.org> <1FAFDF989841D03604BB448B@atuin.in.mat.cc> <7b8d22c6-1fed-d517-9f89-693b88dfc358@freebsd.org> <20160504070341.GV740@mail0.byshenk.net> <3dfd6fea-da32-b922-65d1-f64b8e113112@toco-domains.de> <6e340f95-6d10-4991-0cd6-95d336e2f044@gjunka.com> <3e55c7d8-801c-a2b3-e92e-9945e896142b@toco-domains.de> <5809f808-8b16-93ed-5351-828a7d68eb2b@unsane.co.uk> <574ED144.1050603@quip.cz> <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> Cc: freebsd-ports@freebsd.org, Torsten Zuehlsdorff , Vincent Hoffman-Kazlauskas From: Jeffrey Bouquet Message-ID: Date: Sat, 4 Jun 2016 11:50:14 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <9D785F08-AB0B-4324-B1B3-286D90AF9BF7@lastsummer.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 18:50:22 -0000 On 06/ 3/16 08:17 AM, Franco Fichtner wrote: > Hi there, > >> On 01 Jun 2016, at 2:12 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >> >> There is a main difference - if you upgraded from 9.2 to 9.3, you don't need to recompile (reinstall) all ports, but if you upgraded from 9.3 to 10.x you need to reinstall all your packages and then remove old 9.x libraries from the base system. >> On 01 Jun 2016, at 2:12 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: >> >> There is a main difference - if you upgraded from 9.2 to 9.3, you don't need to recompile (reinstall) all ports, but if you upgraded from 9.3 to 10.x you need to reinstall all your packages and then remove old 9.x libraries from the base system. > This is very much true for a single user point of view, but > the devil is in the details. Let's go through the transition > that we as the OPNsense project went through in the FreeBSD 10 > series... Not a rant, just facts. > > The initial release was 10.0, which was phased out after a > year, leaving us no choice but to go 10.1 just two months > after our initial release in order to receive official security > updates. Worst case it takes a few months to adapt to the > major transition so that's 12 months minus X months of internal > engineering, depending on your staff expertise. In that case > we started in 2014, took us 4 months, that's 6 months including > the time 10.0 was officially available, so 6 months left for > support, when you actually start adapting to 10 as soon as it > comes out. For many that's a luxury not going to happen. One > can blame anyone for starting late, but it's not going to solve > the real world problem. > > 10.1 went really well. When 10.2 happened for us in January > 2016, however, we've already went testing 3 months before and > had a number of issues that were not being addressed upstream > for a longer amount of time: > > o HyperV disks stopped registering as ada(4) devices, killing > installs that were not using labels. Never fixed. > > o Hyper-V NAT broken for a very long time, only fixed in 10.2 > after active polling for an errata[1] > > o pf checksumming broke with offloading[2] > > But the kicker was that building pkg on 10.2 suddenly changed > the ABI behaviour in at least two ways that we know of: > > (1) The reaper for package scripts was now suddenly active, > making it a lot harder to restart a service on package upgrade > from their own scripts. We hat do investigate and disable the > reaper code in pkg itself in order to retain functionality. I > would think that others ran into this silently as well. > > (2) 10.1 systems preloading the "new" pkg for 10.2 were unable > to upgrade certain packages, in this instance isc-dhcp43-*. > It took a few months to even get to the point of triggering > this. In short, we pinned down the pkg ABI to 10.1[3] in order > to allow our older 10.1 systems to upgrade. This should not be > happening in a "ABI stable" environment. There is pkg-static, > but at least in the scope of FreeBSD it's only used when pkg > fails for this or that reason, which is very hard to explain to > a GUI or backend script. Why not make it the default? > > 10.2 was the proverbial rollercoaster ride that some would not > like to see repeated. 10.3 looks better, but what does that say > about 10.4 or 11.0? > > But 10.3 already had a major speed regression during package > installation only caught after the release[4]. Who knows what > our users will be facing once we go live in a few months. > > For downstream projects, this is at least an order of magnitude > worse than the simple user that sits in a shell and runs a magical > fix command to amend its upgrade path. fir some it's even impossible > to get into a shell. Most of downstream projects have automated > processes, upgrade features that rely on certain behaviour, well, > rely on behaviour to stay stable for at least 10.x, which would > make sense. ;) > > And now we run for each 10.x, every time just run for it in order > to make sure that we're not missing an iteration that would amplify > the problems we'll be facing with upgrading later. > > And mind you, this is *with* rebuilding everything from scratch > for each minor update just to be on the safe side. :) > > > Cheers, > Franco > > -- > [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203630 > [2] https://www.freebsd.org/security/advisories/FreeBSD-EN-16:02.pf.asc > [3] https://github.com/opnsense/ports/commit/76975890103 > [4] https://www.freebsd.org/security/advisories/FreeBSD-EN-16:06.libc.asc > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" Yahoo mail refused to send my full reply to the recipients. Suffice to say I recommended a backup to the pkg problem by a secondary /var/db/pkg concurrent methodology. Sorry to be so terse. From owner-freebsd-ports@freebsd.org Sat Jun 4 19:16:14 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53339B6815A for ; Sat, 4 Jun 2016 19:16:14 +0000 (UTC) (envelope-from p.morsou@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 36E251507 for ; Sat, 4 Jun 2016 19:16:14 +0000 (UTC) (envelope-from p.morsou@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 31690B68158; Sat, 4 Jun 2016 19:16:14 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30D87B68157; Sat, 4 Jun 2016 19:16:14 +0000 (UTC) (envelope-from p.morsou@gmail.com) Received: from mail-io0-x241.google.com (mail-io0-x241.google.com [IPv6:2607:f8b0:4001:c06::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F316A1503; Sat, 4 Jun 2016 19:16:13 +0000 (UTC) (envelope-from p.morsou@gmail.com) Received: by mail-io0-x241.google.com with SMTP id k19so14911048ioi.2; Sat, 04 Jun 2016 12:16:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc; bh=R+jpI/+1O7d2Kq8p8k37DX+EAgs9QZxIkLxLzUfsa1E=; b=xrhBcWTkSmakIQh3zt2EENTVrTCKxZqD5ucrQHRCPzYuq3ugFNVSDsE0GbDtwa4aEK 9pq7fAZIfcm7gm1Cf8Y0WHasTrHtMpCXusC2k2Wze22o0WsE/dyaG5CefaKnbU+tggHv UAVRrXIEGJYmg4YH0LNMernGUw6kGMVhv8MQgLC+kDLSIu8Ir/3KNBbe/ZvdSJkiMNBP XkRpLrhVegrqSgod+OukiFcutZNHwYI0Du5xcxE409T9oo+GIgfro7s835qcVcatWLQU sO37i6z2BNgLMOBsczsOzZPmzWlFQaKHtVcoy308wHIJqVdh1O5ySm9QUbMEpoaskMt/ SDCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=R+jpI/+1O7d2Kq8p8k37DX+EAgs9QZxIkLxLzUfsa1E=; b=BQnQW7Y6k6dZma/jJeutZQFtJcCynKjDjEs8fpKmMn2OTCppxHMK9RaRr9XH1cv5c6 yDYpDjUjRawkXkS4X6KnDmggklkEIKCzRqET9Mvdru25HB3h/YsGKWnHOPKvZvCjMUpR Xf+WLQGybLBnSKNmhL3RgQy/3z7IkN4X+un/iFRdf/9qubWApxS7iUKcTOquT+pofLHE j4Um7/SO+6IkpHfuKS8qdtyuA7DRO0dcpEgLPMUfqfRlmFZvXmukr5AL8o37cgAhsbAB LTUi+mfDADfGJFsohzeM/nLBiU431Hik1WqdoAK8YdOqvlaJDvOco7LBbkPmZsKPM4Dw 7UrA== X-Gm-Message-State: ALyK8tIaYLb0OQCRqqcoqtPrbnMnEVIzhhHtd/iN+hxEXDeLRHMYY4K/HDn/NDzcNWy8r0YXmhS00QnNHDUnFA== X-Received: by 10.107.133.142 with SMTP id p14mr7058734ioi.71.1465067773490; Sat, 04 Jun 2016 12:16:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.91.199 with HTTP; Sat, 4 Jun 2016 12:16:13 -0700 (PDT) From: Peter M Souter Date: Sat, 4 Jun 2016 20:16:13 +0100 Message-ID: Subject: Facter 3.X questions To: ruby@freebsd.org Cc: ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 19:16:14 -0000 Hello Facter FreeBSD maintainers! Since Facter's move to a C/C++ codebase, a lot of facts have gone missing on FreeBSD machines. As a dabbler in FreeBSD I want to help fix this! :) I've opened a ticket to track it here ( https://tickets.puppetlabs.com/browse/FACT-1428) and I've been working on getting those missing facts back. So far I've managed to get the DMI (bios and manufacturer facts) and processor info working. I have a few questions: 1) Are there any FreeBSD Puppet users out there on Puppet 4 with Facter 3, who could give some feedback, see if there's anything else I've missed from Facter 3 that they've noticed? 2) If anyone has some C knowledge and wants to help hack on some of the more difficult missing areas such as determining swap space, networks and such, that would be greatly appreciated. Getting kenv and sysctl settings has been fairly simple, these ones have been a little bit more complex... 3) How difficult is it to become a maintainer? I notice that facter is currently under the ruby maintainer email namespace, but right now it's not released to Rubygems since 2.4 and the code is 85% C++ now. I wouldn't mind throwing my hat in and becoming a maintainer if that would help? :) Thanks! Regards Peter Souter PS. Sorry if this is the wrong way to do this, first time emailing to a port maintainer list. I asked in the FreeBSD freenode room and people said this was the way to do it and to CC the Ports mailing list also :) From owner-freebsd-ports@freebsd.org Sat Jun 4 19:36:05 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05596B68731 for ; Sat, 4 Jun 2016 19:36:05 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id EAC1D1FEE for ; Sat, 4 Jun 2016 19:36:04 +0000 (UTC) (envelope-from lists@opsec.eu) Received: by mailman.ysv.freebsd.org (Postfix) id EA28EB6872F; Sat, 4 Jun 2016 19:36:04 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9ABAB6872E; Sat, 4 Jun 2016 19:36:04 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AB6871FED; Sat, 4 Jun 2016 19:36:04 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1b9HMd-000Kl1-95; Sat, 04 Jun 2016 21:36:07 +0200 Date: Sat, 4 Jun 2016 21:36:07 +0200 From: Kurt Jaeger To: Peter M Souter Cc: ruby@freebsd.org, ports@freebsd.org Subject: Re: Facter 3.X questions Message-ID: <20160604193607.GK41922@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 19:36:05 -0000 Hi! > Since Facter's move to a C/C++ codebase, a lot of facts have gone missing > on FreeBSD machines. As a dabbler in FreeBSD I want to help fix this! :) Very nice! I'm no puppet or facter user, but I can probably help with the ports part. Can you explain the state of factor for us ? We have 3.1.3 in the ports, and upstream is @3.1.8. Have you tried to provide a patch to the ports to get the port up2date ? Then: What are those 'facts' ? Are they modules for facter to collect specific info on a system etc ? Are they part of facter itself or do you want to provide seperate ports for this ? What kind of facts are generally available ? The WWW in pkg-descr is https://puppetlabs.com/facter, which no longer works -- what would be the correct link ? How/when should facter replace rubygem-facter in the ports tree ? Right now puppet depends on rubygem-facter, which is only at 2.4.4 ? Upstream is at 2.4.6. > more difficult missing areas such as determining swap space, networks and > such, that would be greatly appreciated. Getting kenv and sysctl settings > has been fairly simple, these ones have been a little bit more complex... For this, we probably need more understanding of facter 8-} Any links that you can share that bring us up to speed ? > 3) How difficult is it to become a maintainer? Submit PRs for sysutils/facter and sysutils/rubygem-facter. robak@ is the maintainer for rubygem-facter, so maybe he's willing to step down ? > I notice that facter is > currently under the ruby maintainer email namespace, but right now it's not > released to Rubygems since 2.4 and the code is 85% C++ now. I wouldn't mind > throwing my hat in and becoming a maintainer if that would help? :) Submit PRs requesting maintainer, and if they come with patches that bring the ports up2date, you're maintainer if the previous maintainer agrees. > PS. Sorry if this is the wrong way to do this, first time emailing to a > port maintainer list. I asked in the FreeBSD freenode room and people said > this was the way to do it and to CC the Ports mailing list also :) Both lists are fine. As this is more a general ports question, -ports is probably fine for further discussion. There's not much discussion on -ruby. -- pi@opsec.eu +49 171 3101372 4 years to go ! From owner-freebsd-ports@freebsd.org Sat Jun 4 20:28:21 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28DECB6A659 for ; Sat, 4 Jun 2016 20:28:21 +0000 (UTC) (envelope-from elferdo@gmail.com) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E608A1F1F for ; Sat, 4 Jun 2016 20:28:20 +0000 (UTC) (envelope-from elferdo@gmail.com) Received: by mail-it0-x22e.google.com with SMTP id f67so15353934ith.1 for ; Sat, 04 Jun 2016 13:28:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ONOC1RdEpXlh96RIgkKcper9ZKLOwoMPbcLxpInWlZA=; b=g8iNqLYmNnKZgq3ZlvAcDSPr/ABKI965TtMKZnVIeh2+mgD7K3Ra8lCMHZBTcdk/6p Zk6TZoDLzao+Vwi3Ro0jdREWsE6MoAtKnwR/2nznNnS2fGz6Jbp2RjC00CBnm8qajK/n X3qKxnM/qQF583COqN5GJh3mjnFl/KDD/CuyV0vN2KCXK2aPcZxcc+mSGgl3QooHpfVm AVcOpxjZvAmzTK0L2ahQ5dxS04ThNBWVPmJFb3s7Zu9mHK+aus0YHRgRC4oOG1/MOwwq kcP36pyz63Gu7DRDdQdRyKQ8sEu6ICqt5qhgudxl6RFrf3+Oem3kC4sUQaCRHg86jBfl dyUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ONOC1RdEpXlh96RIgkKcper9ZKLOwoMPbcLxpInWlZA=; b=HgLipcx+jp3rsaNCCvHIW3JpeiUgwebHOK0MOy98/NwWXqFwfMIQE27CEQ1iovVIiP uEHQ0sVWoUGtSt7yKyU8tWtp1rV/UaGYHZfR4vRc0Wj6Ls8vrbDoQ9dPe55Uy4f/qsYM MHLTmV2tlOob8kXIoNKzk7K4/nv5QLttR5h36S21bXVKSbHQCfmsGI/64g9B9O2jkSk/ rKjHD7kTFs0auB8IrCx0GjYvou8aZ5S+akgPrrm/9sbnXJ6Z32dlz6n54AeD4DFYRTOu 58e/+Pncx2JQHLYldp96mGJeTCNiGke2bXn2O9mGeDYaF6t/1B3AFWVkXqEdoodhq/EE bnvQ== X-Gm-Message-State: ALyK8tJnXZ5TCW6nylRz1s3Wr/KoIRnzCMYbv/AZZOi/1uc50L5hLJCZam78v+sIJvefj4Zyb0ZKKynsjSIpQw== X-Received: by 10.36.137.131 with SMTP id s125mr7373961itd.93.1465072100345; Sat, 04 Jun 2016 13:28:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.206.3 with HTTP; Sat, 4 Jun 2016 13:28:19 -0700 (PDT) In-Reply-To: References: <20160522093727.GD41922@home.opsec.eu> <20160522094002.GE41922@home.opsec.eu> <20160522095930.GF41922@home.opsec.eu> From: =?UTF-8?Q?Fernando_Herrero_Carr=C3=B3n?= Date: Sat, 4 Jun 2016 22:28:19 +0200 Message-ID: Subject: Re: math/R maintenance To: Kurt Jaeger Cc: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2016 20:28:21 -0000 Hi, I submitted a new patch for math/R 3.3.0 ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207425). Could someone please take look at it? Thanks a lot! 2016-05-22 22:31 GMT+02:00 Fernando Herrero Carr=C3=B3n = : > > El 22 may. 2016 11:59 a. m., "Kurt Jaeger" escribi=C3=B3= : > > > > Hi! > > > > > > Ignore that, it was a simple ${PORTSDIR} removal. I'm testing right > now. > > > > > Thanks a lot, Kurt. I am rechecking in any case to see if it still > works. > > > > Turns out, there are quite a few other sleeper PRs for R, > > for example the one to update to 3.3.0. > > > > Can you provide a patch that's working with the state after > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209315 > > > > Thanks! > > > > I see the port has been updated today, I'll try to get a new patch this > week. > > Thanks! >