Re: multimedia/libva fails in configure stage, missing file?
On 01/09/15 18:29, Thomas Mueller wrote: You pointed to libtoolize, which is installed as part of devel/libtool, and I found something strange. Running ls -l /usr/local/bin/lib* produced -r-xr-xr-x 1 root wheel1952 Jul 16 00:31 /usr/local/bin/libIDL-config-2 -r-xr-xr-x 1 root wheel2528 Jul 4 2014 /usr/local/bin/libassuan-config -r-xr-xr-x 1 root wheel3988 Dec 27 13:50 /usr/local/bin/libgcrypt-config -rwxr-xr-x 1 root wheel 15731 Dec 30 08:47 /usr/local/bin/libnetcfg lrwxr-xr-x 1 root wheel 15 Dec 26 08:40 /usr/local/bin/libpng-config - libpng16-config -rwxr-xr-x 1 root wheel2320 Dec 26 08:39 /usr/local/bin/libpng16-config -r-xr-xr-x 1 root wheel 356578 Dec 30 08:34 /usr/local/bin/libtool -rwxr-xr-x 1 root wheel 0 Dec 30 08:34 /usr/local/bin/libtoolize -r-xr-xr-x 1 root wheel2485 Jul 16 00:48 /usr/local/bin/libwmf-config -r-xr-xr-x 1 root wheel 13101 Jul 16 00:48 /usr/local/bin/libwmf-fontmap -r-xr-xr-x 1 root wheel1448 Jul 18 22:10 /usr/local/bin/libwww-config So the scripts involved in building libva-1.5.0 found libtoolize but couldn't see if it was functional. I wonder what happened, how /usr/local/bin/libtoolize was truncated. So I guess that's why I got the message configure.ac:166: error: required file './ltmain.sh' not found Also, pkg gives no hint of files being corrupted. I also ran, from /usr/ports directory, tar tvf ../packages/All/libtool-2.4.2.418.txz and /usr/local/bin/libtoolize showed as 0 bytes. pkg-plist didn't show sizes of package files. For some reason that package has a truncated file. It looks definitely as a local problem on your system, if it was a general problems this list would be flooded by problem reports about this by now. You can mail a build log for devel/libtool to me and I can have a look and see what's wrong. You should try having a look yourself first though. You also have the option of grabbing the official package fro the FreeBSD mirrors, which are not showing this problem. I see libtool is now at v2.4.4. upstream (www.gnu.org/software/libtool) as of 29-Nov-2014. I could try to rebuild devel/libtool, but that won't improve anything if the port or package is defective. As I said if the port was defective we would be getting floods of reports about this by users, since this is not happening, the ports build cluster is building it successfully and I have not been able to reproduce the problem I guess it's a problem caused by something on your system. You should investigate why libtoolize is being created as an empty file. The ports, for example, depends on gm4 from devel/m4, have you tried also rebuilding that? I just tried, same result, no joy. I can try to help you, but please move further followups to private mail to me. I could have a look at a build log for libtool from your system. -- Guido Falsi madpi...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: bugzilla Error 503 Service Unavailable
Hi! Not sure who to alert to this: https://bugs.freebsd.org/bugzilla/ Error 503 Service Unavailable Backend status: Service Unavailable See https://lists.freebsd.org/pipermail/freebsd-ports/2015-January/097488.html During maintenance on bugzilla, the production database broke due to operator error and it's still broken 8-( No ETA for the fix. -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mypaint
On Sunday 11 January 2015 14:41:47 Ajtim wrote: On Sunday 11 January 2015 21:03:23 Vitaly Magerya wrote: On 01/11/15 16:30, Ajtim wrote: Hi! I like to install graphics/Mypaint on FreeBSD 10.1, p, amd64 and I got: --- scons: Reading SConscript files ... building for 'python2.7' (use scons python_binary=xxx to change) using 'python2.7-config' (use scons python_config=xxx to change) rm -f libmypaint-tests.so libmypaint.so libmypaintlib.so python2.7 generate.py Writing mypaint-brush-settings-gen.h Writing brushsettings-gen.h You need to have numpy installed. ImportError: /usr/local/lib/libalapack.so.2: Undefined symbol cblas_zswap: Do you have math/py-numpy with ATLAS option on? If so, try toggling that option, reinstalling numpy and installing mypaint again. I don't know if this is still the case, but there was some interaction between that option and mypaint the last time I tried it. I didn't have. I did turn on and mypaint compile :) and it works. Thank you. It works but application doesn't start: We are not correctly installed or compiled! script: /usr/local/bin/mypaint deduced prefix: /usr/local lib_shared: /usr/local/share/mypaint/ lib_compiled: /usr/local/lib/mypaint/ Traceback (most recent call last): File /usr/local/bin/mypaint, line 170, in module datapath, extradata, confpath, localepath, localepath_brushlib = get_paths() File /usr/local/bin/mypaint, line 111, in get_paths from lib import mypaintlib File /usr/local/share/mypaint/lib/mypaintlib.py, line 25, in module _mypaintlib = swig_import_helper() File /usr/local/share/mypaint/lib/mypaintlib.py, line 17, in swig_import_helper import _mypaintlib ImportError: /usr/local/lib/mypaint/_mypaintlib.so: Undefined symbol _ZN10BufferCompIL20BufferCompOutputType1ELj16384E12HueBlendModeE9blendfuncE Thank you. -- ajtiM http://www.redbubble.com/people/lumiwa ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: biber missing
Kurt Jaeger p...@opsec.eu writes: Hi! If the documentation is present texlive-docs, does it mean that Biber is missing from one of the texlive packages? Probably, yes. Or should it get a port on its own? There's an old (2012) discussion at https://lists.freebsd.org/pipermail/freebsd-ports/2012-May/075180.html which suggests that this should be done, yes. Thanks for the very useful link! Marek signature.asc Description: PGP signature
Re: Build Failure: webkit-gtk2
Hi! Is anyone besides me having a problem building webkit-gtk2? It fails with this error message: CXXLDlibWTF.la CXXLDPrograms/LLIntOffsetsExtractor /usr/bin/ld:./.libs/libWTF.a: file format not recognized; treating as linker script /usr/bin/ld:./.libs/libWTF.a:1: syntax error The webkit-gtk2 build fails if the ports 'ar' is found before the system 'ar'. Check $PATH and put /usr/bin before /usr/local/bin. -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: monitorings-plugin hangs on configure ICMPv6
+--On 11 janvier 2015 17:54:52 +0100 Stefan Bethke s...@lassitu.de wrote: | checking for ps syntax... /bin/ps axwo 'stat uid pid ppid vsz rss pcpu | comm args' checking for ping... /sbin/ping | checking for ping6... /sbin/ping6 | checking for ICMP ping syntax... /sbin/ping -n -c %d %s | checking for ICMPv6 ping syntax... ^C=== Script configure failed | unexpectedly. | | FreeBSD 9-stable, all ports up to date, inside a jail. | | Any suggestions? Could you test the patch there: https://reviews.freebsd.org/D1502 and tell me how good, or bad, it goes ? -- Mathieu Arnold ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mypaint
On Monday 12 January 2015 16:01:28 Vitaly Magerya wrote: On 2015-01-12 15:42, lum...@gmail.com wrote: It works but application doesn't start: We are not correctly installed or compiled! script: /usr/local/bin/mypaint deduced prefix: /usr/local lib_shared: /usr/local/share/mypaint/ lib_compiled: /usr/local/lib/mypaint/ Traceback (most recent call last): File /usr/local/bin/mypaint, line 170, in module datapath, extradata, confpath, localepath, localepath_brushlib = get_paths() File /usr/local/bin/mypaint, line 111, in get_paths from lib import mypaintlib File /usr/local/share/mypaint/lib/mypaintlib.py, line 25, in module _mypaintlib = swig_import_helper() File /usr/local/share/mypaint/lib/mypaintlib.py, line 17, in swig_import_helper import _mypaintlib ImportError: /usr/local/lib/mypaint/_mypaintlib.so: Undefined symbol _ZN10BufferCompIL20BufferCompOutputType1ELj16384E12HueBlendModeE9blendfun cE Yeah, I'm actually getting the same error myself now. There's even a bug report about this problem (PR 193429; bugzilla is down at the moment though). I'm currently updating my ports to see if the problem remains with the latest everything... (this will take a day or two on my hardware). Thank you very much. -- ajtiM http://www.redbubble.com/people/lumiwa ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
powerdns meta packages?
Hi guys, What is the process for adding/submitting meta packages for ports for example powerdns that have multiple backend options and the default isn't suitable, or failing that have the ability to install powerdns with default backend but allow the installation of others? Currently the port defaults to postgres, in this case I'd like sqlite backend for some servers (slaves), at the moment I'm just building that manually but it does mean I can't just do 'pkg upgrade' Cheers, J ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Build Failure: webkit-gtk2
FreeBSD 10.1 amd64 Is anyone besides me having a problem building webkit-gtk2? It fails with this error message: CXXLDlibWTF.la CXXLDPrograms/LLIntOffsetsExtractor /usr/bin/ld:./.libs/libWTF.a: file format not recognized; treating as linker script /usr/bin/ld:./.libs/libWTF.a:1: syntax error c++: error: linker command failed with exit code 1 (use -v to see invocation) GNUmakefile:40539: recipe for target 'Programs/LLIntOffsetsExtractor' failed gmake[1]: *** [Programs/LLIntOffsetsExtractor] Error 1 gmake[1]: Leaving directory '/usr/ports/www/webkit-gtk2/work/webkitgtk-2.4.8' *** Error code 1 Stop. make: stopped in /usr/ports/www/webkit-gtk2 The entire build log is available here: http://seibercom.net/logs/webkit-gtk2.txt -- Jerry pgplEVY8xFx80.pgp Description: OpenPGP digital signature
Re: BIND REPLACE_BASE option
Hi! No disputing that, just thinking, is FreeBSD being driven by user need, financial contributer need, developer need, security need, making things 'better' or just by people wanting to make their mark in a warped sense of it'll all get better...? Probably by developer *capacity* (not need) and fire-fighting, like most IT stuff 8-( -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: bugzilla Error 503 Service Unavailable
On Mon, 12 Jan 2015 04:35:53 -0800 (PST), Anton Shterenlikht stated: Not sure who to alert to this: https://bugs.freebsd.org/bugzilla/ Error 503 Service Unavailable Backend status: Service Unavailable It has been down for something like 48 hours now. You would have thought that someone would have posted a notice on the FreeBSD home page regarding that though. -- Jerry pgpslhR49K8sW.pgp Description: OpenPGP digital signature
Re: mypaint
On 2015-01-12 15:42, lum...@gmail.com wrote: It works but application doesn't start: We are not correctly installed or compiled! script: /usr/local/bin/mypaint deduced prefix: /usr/local lib_shared: /usr/local/share/mypaint/ lib_compiled: /usr/local/lib/mypaint/ Traceback (most recent call last): File /usr/local/bin/mypaint, line 170, in module datapath, extradata, confpath, localepath, localepath_brushlib = get_paths() File /usr/local/bin/mypaint, line 111, in get_paths from lib import mypaintlib File /usr/local/share/mypaint/lib/mypaintlib.py, line 25, in module _mypaintlib = swig_import_helper() File /usr/local/share/mypaint/lib/mypaintlib.py, line 17, in swig_import_helper import _mypaintlib ImportError: /usr/local/lib/mypaint/_mypaintlib.so: Undefined symbol _ZN10BufferCompIL20BufferCompOutputType1ELj16384E12HueBlendModeE9blendfuncE Yeah, I'm actually getting the same error myself now. There's even a bug report about this problem (PR 193429; bugzilla is down at the moment though). I'm currently updating my ports to see if the problem remains with the latest everything... (this will take a day or two on my hardware). ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: BIND REPLACE_BASE option
On Sun, Jan 11, 2015 at 10:38:50PM -0800, Craig Rodrigues wrote: Wrong. I've worked at 3 companies over the years that make direct use of the ports tree when creating an embedded product based on FreeBSD. OK, then this is the first I've heard of it. My mistake. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
bugzilla Error 503 Service Unavailable
Not sure who to alert to this: https://bugs.freebsd.org/bugzilla/ Error 503 Service Unavailable Backend status: Service Unavailable Anton ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: BIND REPLACE_BASE option
Mark Linimon wrote: On Mon, Jan 12, 2015 at 01:29:32PM +0100, Michelle Sullivan wrote: Just a thought: FreeNAS FreeNAS uses ports ... in their own way. Yes, they do contribute back changes as well. The point that I was trying to make, even though I used bad data, was that Ports aren't being driven by external influence. No disputing that, just thinking, is FreeBSD being driven by user need, financial contributer need, developer need, security need, making things 'better' or just by people wanting to make their mark in a warped sense of it'll all get better...? Questions people should ask are: Do we want to make things easier for existing users. Do we want to make things easier for users to convert from other OSes Do we want to develop for anyone paying for changes regardless of the cost (to users) Do we want people to develop what they want for their own purpose My thoughts on all those questions: We should not make anything harder for existing users, and make things easier if possible - however if they are existing users the chances are they already know how to make things work so we should not break stuff already working. We should make things easier for people to migrate to us, and that may mean the work should concentrate on fixing bugs and updating docs as a priority over new features (Microsoft for years went down the route of new features over security or docs, look where it got them) Develop for anyone? Yes and No, what is requested should be evaluated for benefit to the community as a whole and prioritized based on cost and contributions, and rejected out right if it is considered detrimental to the community as a whole (and we should listen to minorities when evaluating, because sometimes the smaller voices can provide saner/long term paths to the same goal.) People develop for their own purpose... well that's what the ports tree is therefore isn't it? ;-) Probably more questions and answers can be added, but they are the first to come to mind. Michelle -- Michelle Sullivan http://www.mhix.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: BIND REPLACE_BASE option
On Mon, Jan 12, 2015 at 01:29:32PM +0100, Michelle Sullivan wrote: Just a thought: FreeNAS FreeNAS uses ports ... in their own way. Yes, they do contribute back changes as well. The point that I was trying to make, even though I used bad data, was that Ports aren't being driven by external influence. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: BIND REPLACE_BASE option
I'm going to wade in with a +1 at the top for your original message, and add some thoughts of my own inline. Roger Marquis wrote: Mark Linimon wrote: It was believed to be a bad design pattern to let ports modify anything in base. Believed by who? Surely not those of us advocating FreeBSD in mixed environments where the Linux and Windows admins are pushing for something closer to a monoculture. Dunno about who believed what, however it has always struck me as odd that servers are installed in the base and then only patched with the OS. The notable exceptions are things like BIND where you could select a later BIND from the ports tree and install over the base version. This initially I found confusing and likely to cause more security issues than it resolved... However, I then thought about it, and realised that what should really have been considered is this (in my opinion): *NO* servers installed in Base (no sendmail, no NTPD, no BIND etc) then in the ports tree a dns/bind-base port where it would install a bind server into the base OS, a 'mail/postfix-base', a 'mail/sendmail-base' etc... or better still a /usr/ports/base where you can find postfix, sendmail, bind etc... This way there are no base ports installed by default, base packages are available with the OS and the specific '-base' port can always be patched as part of freebsd-update, it can be built as part of a /usr/src building/patching process and therefore it can be patched as the user needs in short order (particularly important when you have issues such as the latest root exploit for ntpd... not saying the way that security moved and patched it in a few days wasn't good, it was awesome... however the problem is I had servers ranging from 6.0 - 9.3 at various patch levels - I now have most of my servers either 6.x or 9.2+ (the 6.x servers are all behind firewalls with only specific services (apache and/or postfix) exposed where necessary so the exploit is mitigated)... BUT the patching from 7.3, 8.4 and 9.0 of 27 of the servers 15 of them became unbootable for a variety of reasons... Corrupt loader on 2 occasions, unable to initiate network interface or RAID card on several occasions and changing of critical permissions in others (9.3-RELEASE - 9.3-p5 broke sudo-1.8(latest) on 3 of the machines by changing permissions on 'something')... having /usr/ports/base where one could find 'ntpd' and install it in base would be an excellent solution as one could update/patch oneself if security@ didn't consider the priority as high as the user. It would also mean that the base source code is not polluted and one can install what one needs as and when needed. Apparently 10.0 seemed like the appropriate time to get rid of the bad pattern. seemed like the appropriate time isn't a business case and bad pattern it likely wasn't considering A) someone requested it, B) someone spent money and/or time writing it and C) many people were using it. Roger, you can forget arguing that, I've tried it falls on deaf ears and people just put you on ignore like they have with me... doesn't matter if you're right or not.. Some at the top have a mark to make and being right or wrong won't get in the way of that mark. We've been essentially rewriting the entire ports infrastructure in-place for the past 6 or 7 years. IMVHO this was entirely necessary: the old pkg_* tools were buggy, underdocumented, and no longer suited to the task Which is why pkg_* tools are now removed when you 'delete-old' and all the *.mk keep changing to remove pkg_* support even though those of us that have spent the time to put it back have found that it still works with little changes... Everything in the source seems to point to someone making their mark to remove the pkg_ tools rather than any specific need... Why it couldn't have been left for pre 10.x and then make 10.x pkgng only I don't know... oh wait I do.. it didn't have many people using it so it was decided to force people to change... Lets think of that for a moment... people tried it decided it wasn't ready and didn't migrate, so Bapt wrote patches and deployed on 1/9/2014 not to EOL pkg_* but specifically to break pkg_* then discouraged anyone from back patching (including security fixes) to the quarterly to force the upgrade on production systems. Not sure what this has to do with a small number of mission-critical ports that need to write to base to accommodate large, cross-platform, installed bases. Could you elaborate? Breaking out the servers from /usr/src is good idea, removing -base functionality (IMHO) is not... but it is a good idea to make it simpler because the -base options (especially when not always translated in version changes) did cause me a few issues in the past. They are mostly due to the idea of not shipping things that do not work consistently, and in the way one might expect. On rare occasion, yes, that will mean breaking POLA. Are you saying, then, that
Re: BIND REPLACE_BASE option
Mark Linimon wrote: On Sun, Jan 11, 2015 at 10:38:50PM -0800, Craig Rodrigues wrote: Wrong. I've worked at 3 companies over the years that make direct use of the ports tree when creating an embedded product based on FreeBSD. OK, then this is the first I've heard of it. My mistake. Just a thought: FreeNAS .. I know it uses ports, would one consider any (home NAS) device that ships with FreeNAS as it's OS as an embedded device? (Don't know if there are any, but it was the first thing that came to mind.) -- Michelle Sullivan http://www.mhix.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD ports you maintain which are out of date
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/po...@freebsd.org.html Port| Current version | New version +-+ sysutils/fusefs-smbnetfs| 0.5.3b | 0.6.0 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Opera, still functional, 'one cannot make new configs' etc since v9 v10
On 01/11/15 22:59, Fred Woods wrote: If you run opera from a terminal window, do you get something like the problem described in: http://stackoverflow.com/questions/2568408/pango-warning-failed-to-choose-a-font-expect-ugly-output If yes, then a possible work-around is: Move any pango compliant fonts to /usr/local/lib/X11/fonts mv /usr/loocal/share/fonts/* /usr/local/lib/X11/fonts Create a symlink to make /usr/loocal/share/fonts point to /usr/local/lib/X11/fonts. ln -sF /usr/local/lib/X11/fonts /usr/loocal/share/fonts ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Did not help, unfortunately. I've exactly two other ideas, but neither is certain to fix it, and a few others for which I am still clueless. Additionally, it seems few (openbsd? debian?) ship by default with opera... One of the more readable screenshots attached (email, may not make it to the list...) and inline... in the email. if that make sense. Newbie here with thunderbird terms. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: powerdns meta packages?
On Mon, 12 Jan 2015 15:10:12 + Joe Holden li...@rewt.org.uk wrote Hi guys, What is the process for adding/submitting meta packages for ports for example powerdns that have multiple backend options and the default isn't suitable, or failing that have the ability to install powerdns with default backend but allow the installation of others? Currently the port defaults to postgres, in this case I'd like sqlite backend for some servers (slaves), at the moment I'm just building that manually but it does mean I can't just do 'pkg upgrade' As I understand it, you want to create a custom meta-port. You might do well to have a look at some of the other meta-ports available, for the best way to accomplish it for your needs; x11/xorg x11/xorg-minimal x11/xorg-apps lang/php5-extensions are some that come to mind. Best wishes. --Chris Cheers, J ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: powerdns meta packages?
On 12/01/2015 16:05, Chris H wrote: On Mon, 12 Jan 2015 15:10:12 + Joe Holden li...@rewt.org.uk wrote Hi guys, What is the process for adding/submitting meta packages for ports for example powerdns that have multiple backend options and the default isn't suitable, or failing that have the ability to install powerdns with default backend but allow the installation of others? Currently the port defaults to postgres, in this case I'd like sqlite backend for some servers (slaves), at the moment I'm just building that manually but it does mean I can't just do 'pkg upgrade' As I understand it, you want to create a custom meta-port. You might do well to have a look at some of the other meta-ports available, for the best way to accomplish it for your needs; x11/xorg x11/xorg-minimal x11/xorg-apps lang/php5-extensions are some that come to mind. Best wishes. This is what I'd normally do but I was hoping with the new pkg stuff we could have some sort of virtual packages but this will do I guess! Will need to read up on package building now - seems a bit silly to have my own repo just for -mysql, -sqlite type packages though Cheers --Chris Cheers, J ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: BIND REPLACE_BASE option
On Mon, 12 Jan 2015 07:10:46 -0900 Royce Williams ro...@tycho.org wrote
On Mon, Jan 12, 2015 at 4:08 AM, Kurt Jaeger li...@opsec.eu wrote:
No disputing that, just thinking, is FreeBSD being driven by user need,
financial contributer need, developer need, security need, making things
'better' or just by people wanting to make their mark in a warped sense
of it'll all get better...?
Probably by developer *capacity* (not need) and fire-fighting,
like most IT stuff 8-(
But like most IT stuff, resources are being asymmetrically applied to
the root causes of the fires.
Read the list of projects from last quarter:
- Address Space Layout Randomization (ASLR)
- amd64 Xen Paravirtualization
- bhyve
- Chelsio iSCSI Offload Support
- Debian GNU/kFreeBSD
- FreeBSD Preseed Installation (PXE)
- Jenkins Continuous Integration for FreeBSD
- New Automounter
- QEMU bsd-user-Enabled Ports Building
- VMWare VAAI and Microsoft ODX Acceleration in CTL
- ZFSguru
- Intel GPU Driver Update
- SDIO Driver
- UEFI Boot
- Updated vt(4) System Console
- Updating OpenCrypto
- FreeBSD on Newer ARM Boards
- FreeBSD/arm64
- LLDB Debugger Port
- LLVM Address Sanitizer (Asan)
- SSE Variants of libc Routines for amd64
- FreeBSD Python Ports
- GNOME/FreeBSD
- KDE on FreeBSD
- The Graphics Stack on FreeBSD
- Xfce
The Foundation section also lists these items not overlapping with the above:
- FreeBSD Journal
- PostgreSQL performance improvements
- Ongoing release process
- Development snapshots
- VM images for releases
- Secure Boot planning
- Infrastructure hardware
- Java licensing
- Summits and summit sponsorship
- Travel grants, tutorials, and talks
- New Design and Implementation book
- Recruitment flyers
Are there long-term improvement projects that aren't being listed? If
so, they should be.
At face value, the main project list is heavily weighted towards
relatively esoteric OS features. The Foundation list is heavily
weighted towards advocacy and communication (as it should be).
What is missing are high-level projects to help sysadmins maintain and
use FreeBSD on an ongoing basis.
Here are some projects that would help to close the sysadmin gap:
- Automatic error reporting and analysis
- OS and port debugging tools for sysadmins
- Independent project-wide usability analysis
- Ports dependency isolation and reduction framework
- Ports system reliability parity with Linuxes
- Searchable, taggable project FAQ
- Searchable hardware support matrix integrated with bug tracker
- Wiki curation and platform improvements
These projects decentralize and improve support for sysadmins and new
adopters. As a business case for the Foundation, these projects
should also deeply free up developer resources to focus on other major
projects.
In the past, when I have pointed out this sysadmin gap, I receive
one of two answers:
1. Sounds great. Let us know when you have it finished.
2. We're too busy to do any of those things.
... to which I answer:
1. These projects require technical skill and political capital within
the project. They are ideally suited for well-established independent
FreeBSD consultants with large blocks of time sponsored by the FreeBSD
Foundation. I can help (especially with the wiki work), but cannot
tackle these deeper problems in the way that others can.
FWIW I'm already in the process of creating a wiki that will serve
as a FreeBSD Documentation Factory. I've created the wiki, and am
currently plugging in all the necessary bits. This will permit
live documentation creation, and editing -- including man(1)
pages. It's currently backed by git(1), but conversions to other
RCS, SCM, VCS, {...} are all possible. In fact, I already have the
conversion methods available. This all makes it possible to import
any revision of any doc/man page as an official doc set.
Point being; as FreeBSD is Open Source, it heavily depends on
user-contribution. I'm not attempting to discount your previous
points, however. Just saying. As to the sysadmin gap a look to
the ports tree seems to indicate quite a volume of sysadmin
related ports. Are some missing?
All the best.
--Chris
2. The reason you're busy is that you don't have these things.
I applaud recent work on Jenkins and cluster infrastructure. I also
appreciate Colin Percivals's automated error reporting work, because
it directly attacks the sysadmin gap. And I know that getting
releases out the door is time-consuming and keeps the lights on.
But the overall project list needed to be rebalanced towards system
administration. I request that the Foundation consider this when
calling for proposals for the next round of funded projects.
Royce
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Build Failure: webkit-gtk2
On Mon, 12 Jan 2015, Kurt Jaeger wrote: The webkit-gtk2 build fails if the ports 'ar' is found before the system 'ar'. Check $PATH and put /usr/bin before /usr/local/bin. Only temporarily, I would hope... -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: BIND REPLACE_BASE option
On Mon, 12 Jan 2015 11:57:26 -0700 (MST) Warren Block wbl...@wonkity.com wrote On Mon, 12 Jan 2015, Chris H wrote: Here is where we will clash; I've been riding *BSD for over 20yrs. It's *biggest* asset has been in it's flexibility -- it wasn't another Linux dist, that required me to essentially become a clone of every other Linux install. The Ports system, and /src allowed one to tailor my build/install to meet *my* needs. I wasn't required, in fact I was *encouraged*, to have a unique system. Frankly the new pkg(8) *requirement* was a complete 180 on this philosophy. Huh? It is the same as the old package system, required if you want to use ports or packages. The difference is that pkg is not in base, so it can be easily upgraded without doing an OS upgrade. Ports continue to work as they did with the old package system, only package operations are faster and more reliable. Sure, it's intended to *feel* like pkg_, but the (way) it's implemented bears little resemblance to pkg_, and it's implementation also *abruptly* pulled the rug out from under many years of development work, carefully crafted work by development shops to keep their stream flowing smoothly and more efficiently. [I'm kicking a dead horse here] My main complaint with pkg is the persistent misunderstanding that binary packages are a direct replacement for ports. http://www.wonkity.com/~wblock/docs/html/pkg.html I'd be inclined to agree here. As for the original topic, BIND in base had the same upgrade problems as the old package system. The port overwriting the base was a convenient but nasty hack. Not even that convenient, because all that changes with the port is the config files are in /usr/local/etc rather than /etc. A chroot adds little security or isolation, and if you want that it should be in a jail or other type of VM anyway. https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails-ezjail.html# Speaking of kicking dead horses; I'm still amazed that this topic still continues. I remember the initial discussion on this about 9mos ago, and thought; OK. That seems to make sense. I'd better see if I can cobble up something that mimic's the old setup, so I can keep things going, until I find a suitable replacement for the BIND. Took me less than 2hrs. Point being; there was a fair amount of time before the BIND got yanked (unlike the pkg change). So I'm amazed so many people are, well, amazed. --Chris --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: bugzilla Error 503 Service Unavailable
Hi! Not sure who to alert to this: https://bugs.freebsd.org/bugzilla/ Error 503 Service Unavailable Backend status: Service Unavailable Bugzilla is back -- 53 lost PRs have been re-created as best as can be done. There are updates to PRs missing, both to those 53, and to others. gavin@ is trying to fix those he finds more info about, but if you are aware of a PR you have updated since 2015-01-07 16:07:14 UTC it would be greatly appreciated if you could make the update again. -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: BIND REPLACE_BASE option
On Mon, 12 Jan 2015, Chris H wrote: Here is where we will clash; I've been riding *BSD for over 20yrs. It's *biggest* asset has been in it's flexibility -- it wasn't another Linux dist, that required me to essentially become a clone of every other Linux install. The Ports system, and /src allowed one to tailor my build/install to meet *my* needs. I wasn't required, in fact I was *encouraged*, to have a unique system. Frankly the new pkg(8) *requirement* was a complete 180 on this philosophy. Huh? It is the same as the old package system, required if you want to use ports or packages. The difference is that pkg is not in base, so it can be easily upgraded without doing an OS upgrade. Ports continue to work as they did with the old package system, only package operations are faster and more reliable. My main complaint with pkg is the persistent misunderstanding that binary packages are a direct replacement for ports. http://www.wonkity.com/~wblock/docs/html/pkg.html As for the original topic, BIND in base had the same upgrade problems as the old package system. The port overwriting the base was a convenient but nasty hack. Not even that convenient, because all that changes with the port is the config files are in /usr/local/etc rather than /etc. A chroot adds little security or isolation, and if you want that it should be in a jail or other type of VM anyway. https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails-ezjail.html#jails-ezjail-example-bind ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Build Failure: webkit-gtk2
On 2015-01-12 15:02, Jerry wrote: FreeBSD 10.1 amd64 Is anyone besides me having a problem building webkit-gtk2? It fails with this error message: CXXLDlibWTF.la CXXLDPrograms/LLIntOffsetsExtractor /usr/bin/ld:./.libs/libWTF.a: file format not recognized; treating as linker script /usr/bin/ld:./.libs/libWTF.a:1: syntax error c++: error: linker command failed with exit code 1 (use -v to see invocation) GNUmakefile:40539: recipe for target 'Programs/LLIntOffsetsExtractor' failed gmake[1]: *** [Programs/LLIntOffsetsExtractor] Error 1 gmake[1]: Leaving directory '/usr/ports/www/webkit-gtk2/work/webkitgtk-2.4.8' *** Error code 1 Stop. make: stopped in /usr/ports/www/webkit-gtk2 There is a Bugzilla entry concerning this https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196296 However: Due to a maintenance issue, changes to bugs between 2015-01-07 and 2015-01-10 were lost. Please resubmit any updates as appropriate. We apologize for the inconvenience. Anyway, to reliably build webkit-gtk you must enable BOTH WEBGL and WEBAUDIO, otherwise the build will fail. Cheers, //per ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: poudriere: reduce the number of rebuilt packages?
On 12.01.2015 18:55, Mathieu Arnold wrote: Well, no, there is not, and unless you figure out an algorithm to do it, and I'm saying algorithm in the mathematical sense, not heuristic, that is, one that is always right, feel free to submit a patch for it :-) Now, there's a good chance that it will be slower than rebuilding all the dependencies. What about the logic in pkg, aren't both programs solving the same problem? Regards, Karel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: poudriere-3.1.1 - issues with incremental sanity checks
Hey Bryan - Not sure where else to report this, but for awhile now, I’ve been having trouble doing incremental builds - the sanity checks are failing anytime the ports tree is updated. It’s unclear to me why the dependancies aren’t being found correctly, as they are all present in the port trees. I can manually do multiple passes with sanity checks off, adding the missing ports to my build lists, and eventually can get everything built. Once there, I can run a pass with sanity checks on, of course nothing to build, but the sanity checks then pass. Please let me know what kind of debugging information to provide or what I might be doing wrong. Thanks ! - David P. Discher http://davidpdischer.com/ AIM: DavidDPD | Y!M: daviddpdz Mobile: 408.368.3725 signature.asc Description: Message signed with OpenPGP using GPGMail
Re: bugzilla Error 503 Service Unavailable
El 12/01/2015 21:12, Kurt Jaeger li...@opsec.eu escribió: Hi! Not sure who to alert to this: https://bugs.freebsd.org/bugzilla/ Error 503 Service Unavailable Backend status: Service Unavailable Bugzilla is back -- 53 lost PRs have been re-created as best as can be done. There are updates to PRs missing, both to those 53, and to others. gavin@ is trying to fix those he finds more info about, but if you are aware of a PR you have updated since 2015-01-07 16:07:14 UTC it would be greatly appreciated if you could make the update again. Thanks for taking bugzilla back online! -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Please commit Bug 195956
Dear Committers, Would someone please commit Bug 195956 with maintainer timeout? Because this is security fix it should be committed ASAP. Bug 195956 - textproc/libyaml: Fix CVE-2014-9130 and Add LICENSE https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195956 Best Regards --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: poudriere: reduce the number of rebuilt packages?
On 12/01/2015 21:05, Karel Miklav wrote: On 12.01.2015 18:55, Mathieu Arnold wrote: Well, no, there is not, and unless you figure out an algorithm to do it, and I'm saying algorithm in the mathematical sense, not heuristic, that is, one that is always right, feel free to submit a patch for it :-) Now, there's a good chance that it will be slower than rebuilding all the dependencies. What about the logic in pkg, aren't both programs solving the same problem? No, the problems solved by pkg and poudriere are very different. pkg(8) has the massive advantage that it already has access to the built packages, including analysis of the dynamic linkage of all the binaries included there. That makes it relatively simple for pkg to work out if a change in some dependency has had a material effect on the package being considered. poudriere only knows that the dependency changed. In effect, to find out if the package of interest would be changed because of that, it has no other recourse than to build the package. Now, if you can come up with some heuristics whereby you can examine the changes to a port and determine that they will not cause significant downstream changes, and do that reliably and faster than just rebuilding the package, then I'm sure the poudriere developers would be eager to incorporate them. Failing that, poudriere re-building everything that might be affected is the sensible choice. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: bugzilla Error 503 Service Unavailable
in message 201501121235.t0cczqkn084...@mech-as221.men.bris.ac.uk, wrote Anton Shterenlikht thusly... Not sure who to alert to this: https://bugs.freebsd.org/bugzilla/ Error 503 Service Unavailable Backend status: Service Unavailable Mercifully now a message shows that people are apparently aware of the problem to try later. Thanks to whoever did that. - parv -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mypaint
Vitaly Magerya vmage...@gmail.com writes:
It works but application doesn't start:
We are not correctly installed or compiled!
script: /usr/local/bin/mypaint
deduced prefix: /usr/local
lib_shared: /usr/local/share/mypaint/
lib_compiled: /usr/local/lib/mypaint/
Traceback (most recent call last):
File /usr/local/bin/mypaint, line 170, in module
datapath, extradata, confpath, localepath, localepath_brushlib =
get_paths()
File /usr/local/bin/mypaint, line 111, in get_paths
from lib import mypaintlib
File /usr/local/share/mypaint/lib/mypaintlib.py, line 25, in module
_mypaintlib = swig_import_helper()
File /usr/local/share/mypaint/lib/mypaintlib.py, line 17, in
swig_import_helper
import _mypaintlib
ImportError: /usr/local/lib/mypaint/_mypaintlib.so: Undefined symbol
_ZN10BufferCompIL20BufferCompOutputType1ELj16384E12HueBlendModeE9blendfuncE
Yeah, I'm actually getting the same error myself now. There's even a
bug report about this problem (PR 193429; bugzilla is down at the
moment though).
Or maybe https://gna.org/bugs/index.php?21981
I'm currently updating my ports to see if the problem remains with the
latest everything... (this will take a day or two on my hardware).
I think the following are relevant patches from bugzilla.
Index: Mk/Uses/scons.mk
===
--- Mk/Uses/scons.mk(revision 376385)
+++ Mk/Uses/scons.mk(working copy)
@@ -17,6 +17,8 @@ IGNORE= Incorrect 'USES+= scons:${scons_ARGS}' sco
MAKEFILE= #
MAKE_FLAGS=#
ALL_TARGET=#
+CCFLAGS?= ${CFLAGS}
+LINKFLAGS?=${LDFLAGS}
LIBPATH?= ${LOCALBASE}/lib
CPPPATH?= ${LOCALBASE}/include
SCONS= ${LOCALBASE}/bin/scons
Index: graphics/mypaint/Makefile
===
--- graphics/mypaint/Makefile (revision 376385)
+++ graphics/mypaint/Makefile (working copy)
@@ -22,7 +22,7 @@ BUILD_DEPENDS:= ${RUN_DEPENDS} \
USE_GNOME= glib20 pygtk2
MAKE_ARGS= prefix=${PREFIX}
-USES= gettext pkgconfig scons tar:bzip2 python
+USES= compiler:gcc-c++11-lib gettext pkgconfig scons tar:bzip2 python
INSTALLS_ICONS=yes
SUB_FILES= pkg-install
-
VFEmail.net - http://www.vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: poudriere: reduce the number of rebuilt packages?
On 12.01.2015 18:45, Kurt Jaeger wrote: Hi! The option -S (Don't recrusively rebuild packages affected by other packages requiring incremental rebuild) looked promising. But automatic packages are not always rebuilt and I've also encountered build problems. I'll try this option now and would appreciate if you could describe the problems you had with it. Details help. Not all ports with new versions were rebuilt. That is kind of expected if there's no recursive rebuild. As a workaround I simply passed the output of pkg query %o to poudriere bulk -f. Now poudriere tried to build only the packages with newer versions - just as desired. But then there were build errors for some packages. Unfortunately, I no longer have the log files. But I think the problem was something like this: A --depends on-- B --depends on-- C * B was built depending on C version x * C is upgraded from version x to version y * rebuild of A is requested * poudriere tries to install B version x during build * installation of B fails because version x of C is not longer available ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: BIND REPLACE_BASE option
On Mon, Jan 12, 2015 at 4:08 AM, Kurt Jaeger li...@opsec.eu wrote: No disputing that, just thinking, is FreeBSD being driven by user need, financial contributer need, developer need, security need, making things 'better' or just by people wanting to make their mark in a warped sense of it'll all get better...? Probably by developer *capacity* (not need) and fire-fighting, like most IT stuff 8-( But like most IT stuff, resources are being asymmetrically applied to the root causes of the fires. Read the list of projects from last quarter: - Address Space Layout Randomization (ASLR) - amd64 Xen Paravirtualization - bhyve - Chelsio iSCSI Offload Support - Debian GNU/kFreeBSD - FreeBSD Preseed Installation (PXE) - Jenkins Continuous Integration for FreeBSD - New Automounter - QEMU bsd-user-Enabled Ports Building - VMWare VAAI and Microsoft ODX Acceleration in CTL - ZFSguru - Intel GPU Driver Update - SDIO Driver - UEFI Boot - Updated vt(4) System Console - Updating OpenCrypto - FreeBSD on Newer ARM Boards - FreeBSD/arm64 - LLDB Debugger Port - LLVM Address Sanitizer (Asan) - SSE Variants of libc Routines for amd64 - FreeBSD Python Ports - GNOME/FreeBSD - KDE on FreeBSD - The Graphics Stack on FreeBSD - Xfce The Foundation section also lists these items not overlapping with the above: - FreeBSD Journal - PostgreSQL performance improvements - Ongoing release process - Development snapshots - VM images for releases - Secure Boot planning - Infrastructure hardware - Java licensing - Summits and summit sponsorship - Travel grants, tutorials, and talks - New Design and Implementation book - Recruitment flyers Are there long-term improvement projects that aren't being listed? If so, they should be. At face value, the main project list is heavily weighted towards relatively esoteric OS features. The Foundation list is heavily weighted towards advocacy and communication (as it should be). What is missing are high-level projects to help sysadmins maintain and use FreeBSD on an ongoing basis. Here are some projects that would help to close the sysadmin gap: - Automatic error reporting and analysis - OS and port debugging tools for sysadmins - Independent project-wide usability analysis - Ports dependency isolation and reduction framework - Ports system reliability parity with Linuxes - Searchable, taggable project FAQ - Searchable hardware support matrix integrated with bug tracker - Wiki curation and platform improvements These projects decentralize and improve support for sysadmins and new adopters. As a business case for the Foundation, these projects should also deeply free up developer resources to focus on other major projects. In the past, when I have pointed out this sysadmin gap, I receive one of two answers: 1. Sounds great. Let us know when you have it finished. 2. We're too busy to do any of those things. ... to which I answer: 1. These projects require technical skill and political capital within the project. They are ideally suited for well-established independent FreeBSD consultants with large blocks of time sponsored by the FreeBSD Foundation. I can help (especially with the wiki work), but cannot tackle these deeper problems in the way that others can. 2. The reason you're busy is that you don't have these things. I applaud recent work on Jenkins and cluster infrastructure. I also appreciate Colin Percivals's automated error reporting work, because it directly attacks the sysadmin gap. And I know that getting releases out the door is time-consuming and keeps the lights on. But the overall project list needed to be rebalanced towards system administration. I request that the Foundation consider this when calling for proposals for the next round of funded projects. Royce ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: poudriere: reduce the number of rebuilt packages?
On 12.01.2015 18:08, Mathieu Arnold wrote: +--On 12 janvier 2015 17:59:36 +0100 Stefan Ehmann shoes...@gmx.net wrote: | | But it would be nice to have a poudriere option to avoid rebuilds of | ports without version bumps. If something should go horribly wrong every | now and then, you can still fall back to the default rebuild behavior. | | I think it should be possibly provided that port versions are bumped | correctly. But maybe I'm wrong. Like someone else said, you can use bulk -S, but don't complain if you end up with something that's horribly broken :-) bulk -S didn't really work well for me (see original post). But I think I my original question is answered by now: There's no supported way of avoiding excessive rebuilds with poudriere. What I'm now doing is: * Dry run of poudriere bulk with normal list of ports * make a list of ports that will be rebuilt because of new version * Run poudriere bulk with new list There are still some ports without version bump rebuilt, but it's a much smaller number. Especially libreoffice/KDE, etc. rebuilds are avoided. This procedure probably has some issues. But in case of problems I'll just do a normal incremental build. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: poudriere: reduce the number of rebuilt packages?
Hi! The option -S (Don't recrusively rebuild packages affected by other packages requiring incremental rebuild) looked promising. But automatic packages are not always rebuilt and I've also encountered build problems. I'll try this option now and would appreciate if you could describe the problems you had with it. Details help. -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: poudriere: reduce the number of rebuilt packages?
+--On 12 janvier 2015 18:45:06 +0100 Stefan Ehmann shoes...@gmx.net wrote: | On 12.01.2015 18:08, Mathieu Arnold wrote: | | | +--On 12 janvier 2015 17:59:36 +0100 Stefan Ehmann shoes...@gmx.net | wrote: | | | | But it would be nice to have a poudriere option to avoid rebuilds of | | ports without version bumps. If something should go horribly wrong | | every now and then, you can still fall back to the default rebuild | | behavior. | | | | I think it should be possibly provided that port versions are bumped | | correctly. But maybe I'm wrong. | | Like someone else said, you can use bulk -S, but don't complain if you | end up with something that's horribly broken :-) | | bulk -S didn't really work well for me (see original post). | | But I think I my original question is answered by now: | There's no supported way of avoiding excessive rebuilds with poudriere. Well, no, there is not, and unless you figure out an algorithm to do it, and I'm saying algorithm in the mathematical sense, not heuristic, that is, one that is always right, feel free to submit a patch for it :-) Now, there's a good chance that it will be slower than rebuilding all the dependencies. | What I'm now doing is: | * Dry run of poudriere bulk with normal list of ports | * make a list of ports that will be rebuilt because of new version | * Run poudriere bulk with new list | | There are still some ports without version bump rebuilt, but it's a much | smaller number. Especially libreoffice/KDE, etc. rebuilds are avoided. | | This procedure probably has some issues. But in case of problems I'll | just do a normal incremental build. -- Mathieu Arnold ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: BIND REPLACE_BASE option
On Mon, Jan 12, 2015 at 7:38 AM, Chris H bsd-li...@bsdforge.com wrote: As to the sysadmin gap a look to the ports tree seems to indicate quite a volume of sysadmin related ports. Are some missing? To the contrary -- there are too many. A good project would be to survey which ones people actually use, and why -- and then bring their best features into base. This would be difficult to do as a independent skunkworks project, and would be better suited as a high-level, Foundation-sponsored one. (For example, in the Debian ecosystem, for most people, there is no reason to use something other than apt-get, because it does what it should and does it well. Every time I upgrade a port, I have to study /usr/ports/UPDATING, read multiple mailing lists, and hold my breath. I cannot remember the last time I worried about running apt-get. Arguments about flexibility and diversity ecosystem don't hold up well when the basics fail on a regular basis.) Royce ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: BIND REPLACE_BASE option
On Mon, 12 Jan 2015 07:55:45 -0900 Royce Williams ro...@tycho.org wrote On Mon, Jan 12, 2015 at 7:38 AM, Chris H bsd-li...@bsdforge.com wrote: As to the sysadmin gap a look to the ports tree seems to indicate quite a volume of sysadmin related ports. Are some missing? To the contrary -- there are too many. A good project would be to survey which ones people actually use, and why -- and then bring their best features into base. I agree something like thishas value. But obtaining access to the usage matrix is the key. This would be difficult to do as a independent skunkworks project, and would be better suited as a high-level, Foundation-sponsored one. see above. (For example, in the Debian ecosystem, for most people, there is no reason to use something other than apt-get, because it does what it should and does it well. Every time I upgrade a port, I have to study /usr/ports/UPDATING, read multiple mailing lists, and hold my breath. I cannot remember the last time I worried about running apt-get. Arguments about flexibility and diversity ecosystem don't hold up well when the basics fail on a regular basis.) Here is where we will clash; I've been riding *BSD for over 20yrs. It's *biggest* asset has been in it's flexibility -- it wasn't another Linux dist, that required me to essentially become a clone of every other Linux install. The Ports system, and /src allowed one to tailor my build/install to meet *my* needs. I wasn't required, in fact I was *encouraged*, to have a unique system. Frankly the new pkg(8) *requirement* was a complete 180 on this philosophy. It's implementation was also flawed in many respects (which speaks to your point). I have no objection to pkg(8), per se; But it *should* have been optional, it *should* have been better (longer) tested, *before* pushed into the ecosystem, and should *not* have been implemented with a backend with single-point-of-failue (sqlite3(1). Honestly; why did pkg(8) have to be *required*? Is FreeBSD simply hoping to become a new distro? But, given it's there, and how it's there. You have/bring up some valid, points; it *is* a bit of a game of roulette. I *too* get a knot in my stomach even at the *thought* of an upgrade. Sure there are plenty of choices in an upgrade path/implementation. But, as it sits now, I'm not sure I can say it's gotten any easier, or trouble free, as a result of pkg(8). --Chris Royce ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org --Chris --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: BIND REPLACE_BASE option
On Mon, Jan 12, 2015 at 8:24 AM, Chris H bsd-li...@bsdforge.com wrote: On Mon, 12 Jan 2015 07:55:45 -0900 Royce Williams ro...@tycho.org wrote On Mon, Jan 12, 2015 at 7:38 AM, Chris H bsd-li...@bsdforge.com wrote: As to the sysadmin gap a look to the ports tree seems to indicate quite a volume of sysadmin related ports. Are some missing? To the contrary -- there are too many. A good project would be to survey which ones people actually use, and why -- and then bring their best features into base. I agree something like thishas value. But obtaining access to the usage matrix is the key. A fair point. Instrumenting the OS now to make this usage possible later would be a good idea. IIRC, PC-BSD integrated BSDstats a while back. If FreeBSD did the same, and prompted at install for Would you like to help the project by reporting anonymous hardware and software inventory information?, we could start to build that matrix. This would be difficult to do as a independent skunkworks project, and would be better suited as a high-level, Foundation-sponsored one. see above. (For example, in the Debian ecosystem, for most people, there is no reason to use something other than apt-get, because it does what it should and does it well. Every time I upgrade a port, I have to study /usr/ports/UPDATING, read multiple mailing lists, and hold my breath. I cannot remember the last time I worried about running apt-get. Arguments about flexibility and diversity ecosystem don't hold up well when the basics fail on a regular basis.) Here is where we will clash; I've been riding *BSD for over 20yrs. It's *biggest* asset has been in it's flexibility -- it wasn't another Linux dist, that required me to essentially become a clone of every other Linux install. The Ports system, and /src allowed one to tailor my build/install to meet *my* needs. I wasn't required, in fact I was *encouraged*, to have a unique system. Frankly the new pkg(8) *requirement* was a complete 180 on this philosophy. It's implementation was also flawed in many respects (which speaks to your point). I have no objection to pkg(8), per se; But it *should* have been optional, it *should* have been better (longer) tested, *before* pushed into the ecosystem, and should *not* have been implemented with a backend with single-point-of-failue (sqlite3(1). Honestly; why did pkg(8) have to be *required*? Is FreeBSD simply hoping to become a new distro? But, given it's there, and how it's there. You have/bring up some valid, points; it *is* a bit of a game of roulette. I *too* get a knot in my stomach even at the *thought* of an upgrade. Sure there are plenty of choices in an upgrade path/implementation. But, as it sits now, I'm not sure I can say it's gotten any easier, or trouble free, as a result of pkg(8). I basically agree. pkg(8)'s heart is in the right place, but it was not baked long enough. I like the idea of being flexible as a proving ground, and then selecting best of breed as the baseline. Royce ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: monitorings-plugin hangs on configure ICMPv6
Am 12.01.2015 um 16:04 schrieb Mathieu Arnold m...@freebsd.org: Could you test the patch there: https://reviews.freebsd.org/D1502 and tell me how good, or bad, it goes ? Builds just fine. And I see you’ve already commit it. Thanks for the quick help! Regards, Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: BIND REPLACE_BASE option
Hi! Honestly; why did pkg(8) have to be *required*? Because those that are really active in maintaining it had the choice of either - keeping the old system running, and breaking down on the burden of doing so or - migrating to the pkgng setup which allows to cope with the rate of change in the non-freebsd-base software world It's an economics question: Those players in the open-source OS market that have the resources to keep going will stay afloat. FreeBSD had the choice to loose more active maintainers trying to keep the old state or attract new ones with the new state. It's a gamble, and if enough people like the old style more, they probably have to fork. I've used both styles for a while and yes, the switchover takes time and patience, but it's not the end-of-the-world. -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: powerdns meta packages?
On Mon, 12 Jan 2015 16:42:45 + Joe Holden li...@rewt.org.uk wrote On 12/01/2015 16:05, Chris H wrote: On Mon, 12 Jan 2015 15:10:12 + Joe Holden li...@rewt.org.uk wrote Hi guys, What is the process for adding/submitting meta packages for ports for example powerdns that have multiple backend options and the default isn't suitable, or failing that have the ability to install powerdns with default backend but allow the installation of others? Currently the port defaults to postgres, in this case I'd like sqlite backend for some servers (slaves), at the moment I'm just building that manually but it does mean I can't just do 'pkg upgrade' As I understand it, you want to create a custom meta-port. You might do well to have a look at some of the other meta-ports available, for the best way to accomplish it for your needs; x11/xorg x11/xorg-minimal x11/xorg-apps lang/php5-extensions are some that come to mind. Best wishes. This is what I'd normally do but I was hoping with the new pkg stuff we could have some sort of virtual packages but this will do I guess! Will need to read up on package building now - seems a bit silly to have my own repo just for -mysql, -sqlite type packages though Well, I thought you might want to make the (meta)port, and submit it. Then other like-minded people could also benefit from your contribution. :) If you submit it as a port, the pkg(8) business takes care of itself. All the best. --Chris Cheers --Chris Cheers, J ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org --Chris --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: poudriere: reduce the number of rebuilt packages?
On 12.01.2015 01:27, Mathieu Arnold wrote: +--On 4 janvier 2015 18:24:24 +0100 Stefan Ehmann shoes...@gmx.net wrote: | On 02.01.2015 12:03, Stefan Ehmann wrote: | I've recently switched from portmaster to poudriere/'pkg upgrade' to | manage my port updates. Basically it works fine, but incremental builds | don't quite work as I expected. | | poudriere rebuilds all packages if any dependency has changed. If there | are only some ports with new versions, possibly hundreds of packages are | rebuilt. So far it looks like I'll end up rebuilding packages like | libreoffice/KDE/chromium several times a week. The rebuilt packages | won't even be installed by 'pkg upgrade' because their version number | has not changed. | | Here's an actual example from today. | | There are new versions for three ports. poudriere will rebuild 70 ports, | 67 of them will never be installed on the host. You can't know that. Say there is a shlib change in one of the updated packages, its version is bumped, or there is a new dependency, you need to rebuild the 67 ports, and pkg will detect and reinstall them. I remember one instance where a library change was detected (Can't remember which package was affected). The package was re-installed although the version number did not change. But like 99% of the time packages without version bump will not be installed. One could argue that the version number should have been bumped in the other case. I understand that conservative rebuilding is important for the official pkg repo. But it would be nice to have a poudriere option to avoid rebuilds of ports without version bumps. If something should go horribly wrong every now and then, you can still fall back to the default rebuild behavior. I think it should be possibly provided that port versions are bumped correctly. But maybe I'm wrong. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: poudriere: reduce the number of rebuilt packages?
+--On 12 janvier 2015 17:59:36 +0100 Stefan Ehmann shoes...@gmx.net wrote: | | But it would be nice to have a poudriere option to avoid rebuilds of | ports without version bumps. If something should go horribly wrong every | now and then, you can still fall back to the default rebuild behavior. | | I think it should be possibly provided that port versions are bumped | correctly. But maybe I'm wrong. Like someone else said, you can use bulk -S, but don't complain if you end up with something that's horribly broken :-) -- Mathieu Arnold ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: poudriere: reduce the number of rebuilt packages?
On 1/12/2015 11:45 AM, Kurt Jaeger wrote: Hi! The option -S (Don't recrusively rebuild packages affected by other packages requiring incremental rebuild) looked promising. But automatic packages are not always rebuilt and I've also encountered build problems. I'll try this option now and would appreciate if you could describe the problems you had with it. Details help. This option was added for an intent that never panned out. I should remove it. It's dangerous and will create a broken repository. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: Build Failure: webkit-gtk2
On Mon, 12 Jan 2015 15:20:23 +0100, Kurt Jaeger stated: Is anyone besides me having a problem building webkit-gtk2? It fails with this error message: CXXLDlibWTF.la CXXLDPrograms/LLIntOffsetsExtractor /usr/bin/ld:./.libs/libWTF.a: file format not recognized; treating as linker script /usr/bin/ld:./.libs/libWTF.a:1: syntax error The webkit-gtk2 build fails if the ports 'ar' is found before the system 'ar'. Check $PATH and put /usr/bin before /usr/local/bin. Okay, that fixed the problem. While it may not be technically a BUG, it is a serious annoyance never-the-less. -- Jerry pgp3eC0RpPNXr.pgp Description: OpenPGP digital signature
