Re: Maia Mailgaurd
Hello Janky Jay! -Original Message- Sent: Monday, December 3, 2018 4:17 PM Subject: Re: Maia Mailgaurd Okay. No sweat. I'll work on getting a port patch going as that seems it would be the easiest way to push this out. I'll provide a download as soon as I have something available for testing. Sounds good, thank you for your work on ports! -Reko ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Maia Mailgaurd
Hello Janky Jay! --Original Message-- Monday, November 26, 2018 10:11 PM Subject: Re: Maia Mailgaurd That being said, with just a few minor changes, I have been able to get Maia to work with PHP 7.2 without any issues (that I've seen, anyway). If you're interested in that, I can provide those changes/patches if you'd like to upgrade to PHP7 before the upstream code is ready. I would also love the preliminary patches for getting Maia to work on PHP7+ Thank you in advance, Reko ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade of security/openssl111 fails to install
Longer explanation: DISTVERSION=1.1.1a names the port/package 1.1.1.a which pkg/ports installer understands being older than 1.1.1_2 PORTVERSION=1.1.1a does naming correctly to 1.1.1a which is uderstood as more recent than 1.1.1_2.[1] This is what I did based on reading port naming from porters handbook and changing DIST to PORT. -Reko [1] https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-naming.html -Original Message- From: Reko Turja via freebsd-ports Sent: Wednesday, November 21, 2018 9:17 PM To: po...@freebsd.org Subject: Re: Upgrade of security/openssl111 fails to install Editing the makefile and removing DISTVERSION line and replacing it with: PORTVERSION=1.1.1a fixed the issue for me. -Reko -Original Message- From: j...@mailman-hosting.com Sent: Wednesday, November 21, 2018 5:53 PM To: po...@freebsd.org Subject: Upgrade of security/openssl111 fails to install Hello, After upgrading my packages with poudriere, the updated version (1.1.1.a) is not installed by pkg(8). Apparently, because of the versioning, it's seen as a downgrade: root@teresa:~ # pkg upgrade Updating poudriere-php56-openssl111 repository catalogue... poudriere-php56-openssl111 repository is up to date. All repositories are up to date. Checking for upgrades (1 candidates): 100% Processing candidates (1 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. root@teresa:~ # pkg upgrade -f openssl111 Updating poudriere-php56-openssl111 repository catalogue... poudriere-php56-openssl111 repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): Installed packages to be DOWNGRADED: openssl111: 1.1.1_2 -> 1.1.1.a [poudriere-php56-openssl111] Number of packages to be downgraded: 1 Proceed with this action? [Y/n]: ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrade of security/openssl111 fails to install
Editing the makefile and removing DISTVERSION line and replacing it with: PORTVERSION=1.1.1a fixed the issue for me. -Reko -Original Message- From: j...@mailman-hosting.com Sent: Wednesday, November 21, 2018 5:53 PM To: po...@freebsd.org Subject: Upgrade of security/openssl111 fails to install Hello, After upgrading my packages with poudriere, the updated version (1.1.1.a) is not installed by pkg(8). Apparently, because of the versioning, it's seen as a downgrade: root@teresa:~ # pkg upgrade Updating poudriere-php56-openssl111 repository catalogue... poudriere-php56-openssl111 repository is up to date. All repositories are up to date. Checking for upgrades (1 candidates): 100% Processing candidates (1 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. root@teresa:~ # pkg upgrade -f openssl111 Updating poudriere-php56-openssl111 repository catalogue... poudriere-php56-openssl111 repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): Installed packages to be DOWNGRADED: openssl111: 1.1.1_2 -> 1.1.1.a [poudriere-php56-openssl111] Number of packages to be downgraded: 1 Proceed with this action? [Y/n]: ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Poudriere building far more ports than it should
First of all, big thanks to everyone who tried to help! Mostly asking to make sure if this is something to be expected, glitch in some ports or possibly a bug. I think Poudriere pulls in all the possible dependencies, just in case and compiles them as well, just in case. Now I've done some installs etc, I'm just going to blacklist the unnecessary ports which aren't used or linked, in order to make the Poudriere build process meaner and leaner. -Reko ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Poudriere building far more ports than it should
-Original Message- From: AlexandreC. Guimarães Sent: Wednesday, November 14, 2018 9:26 PM Do you mean the OPTIONS you previously set were not honoured by poudriere? Just in case, poudriere does not `read` OPTIONS and/or other things like make.conf from the default location but from /usr/local/etc/poudriere.d/* Yes, I copied over my make.conf, my src.conf and then /var/db/ports/ to options. And as I said in previous then douplechecked with "poudriere options -c..." What I can understand is that poudriere brought for example every single Imagick dependency, even if I just use a selected few. Of course if everything is as intended and the packages install without any extra dependencies I don't need, I'm happy. Just haven't got time yet to check if the packages I've built "behave", been too busy rebuilding my home firewall/gateway to incorporate the delivery of the packages to intended targets :) Mostly asking to make sure if this is something to be expected, glitch in some ports or possibly a bug. -Reko ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Poudriere building far more ports than it should
-Original Message- From: Matthias Fechner Sent: Wednesday, November 14, 2018 9:10 PM Am 14.11.2018 um 19:57 schrieb Reko Turja via freebsd-ports: I guess one option would be blacklisting in poudriere those unneeded dependencies which shouldn't be linked with my packages, if my options are honoured by poudriere. have you made your options (maybe they are located on /var/db/ports) available to poudriere? < (normally poudriere searches them in /usr/local/etc/poudriere.d/options) Yes I have andd after noticing the huge increase in ports to be build, doublechecked that my options had really transferred over using poudriere options -c -j -f instead of -C... -Reko ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Poudriere building far more ports than it should
Hello! -Original Message- From: Dmytro Bilokha On Wed, Nov 14, 2018 at 03:33:38AM +0200, reko.turja--- via freebsd-ports wrote: I finally took the hurdle and made a poudriere VM for building my ports instead of building them on target system. At first I did however build every single port I will need on the VM resulting on 240 or so ports. Then I copied over my options, and the list of installed ports etc. and started the build. For some reason poudriere wants to build a ton of extra baggage (360+ ports instead of 240.) Hello, Reko! Poudriere builds different kinds of ports: 1. Ports from your list. 2. Run-time dependencies of ports from your list. 3. Build-time dependecies of ports from your list. < 4. Run-time and build-time dependencies of your ports dependencies, as well That all I know - Ive been using ports and only ports since early 2000's. So the problem is that I made a dry run from ports, linking only to stuff that I wanted on the final package receiver. Then I copied the list of ports over to poudriere using portversion -oQ. When I started the run, there was suddenly every single dependency I previously dropped brought in. (I know about automake, autoconf and similar build dependencies.) I guess one option would be blacklisting in poudriere those unneeded dependencies which shouldn't be linked with my packages, if my options are honoured by poudriere. -Reko ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Is there a way to automatically edit port Makefile and plist after updates
-Original Message-
From: Walter Schwarzenfeld
once more for clear, there are some typos
you can for example put in the makefile
.if ${.CURDIR:M*/ports/lang/php56}
CONFIGURE_ARGS+=--disable-mysqlnd
.endif
Thanks a lot Walter!
This does indeed do the trick for my needs - I did a full build test
and reinstall and it worked as it should.
-Reko
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Is there a way to automatically edit port Makefile and plist after updates
-Original Message- From: Chris H There is one port that has completely unneeded things in both Makefile and plist. Is there a way to Automatically change those afterwards - I guess usual method of patching isn't applicable? Of course doing a portsnap fetch update and sedding the unneeded stuff out from a shellscript each night instead of just portsnap is always an option if there's nothing more refined available. If I'm following you correctly; Wouldn't just filing a pr(1) (https://bugs.freebsd.org/bugzilla/) against the port, with your proposed patch, do it? i don't think that even a patch would help at all, as the maintainer closed a PR already with "working as intended" reply. Just can't understand how having runtime module compiled and loaded for toy... - sorry - mysql is "as intended" for us running something else as the favoured datastore. -Reko ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Is there a way to automatically edit port Makefile and plist after updates
There is one port that has completely unneeded things in both Makefile and plist. Is there a way to Automatically change those afterwards - I guess usual method of patching isn't applicable? Of course doing a portsnap fetch update and sedding the unneeded stuff out from a shellscript each night instead of just portsnap is always an option if there's nothing more refined available. -Reko ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Updating php
Thanks for the info. Can you tell me where I can find some documentation on how to set up "php-fpm" on a FreeBSD-10.2 system running "apache24"? As MAtthew said, this removes lots of hassle (and actually allows running of threaded Apache and php on top of each other without all kinds of interesting side effects) This is how I've done it based on sources from internet and then adjusting the sources into practise - tbh the amount of good how-to's on the subject is pretty minimal: First you need to load mod fcgi (and of course compile/install binary too) in httpd.conf like this (just add on the bottom of other LoadModules if not already there: LoadModule fcgid_module libexec/apache24/mod_fcgid.so For my applications I've had to set some other variables, the following is snippet of my httpd conf just after the LoadModules: FcgidFixPathinfo 1 FcgidMaxRequestLen 13107200 FcgidMaxProcessesPerClass 50 FcgidMaxRequestInMem 131072 FcgidIOTimeout 90 AddHandler fcgid-script .php Options +ExecCGI FcgidWrapper /usr/local/bin/php-wrapper .php As you see, we need a wrapper script in whatever directory we want, for sake of consistency I use /usr/local/bin. For my needs the contents of the wrapper shell script are very simply: #!/bin/sh # Set desired PHP_FCGI_* environment variables. # Example: # PHP FastCGI processes exit after 500 requests by default. PHP_FCGI_MAX_REQUESTS=1000 export PHP_FCGI_MAX_REQUESTS As we are running cgi from "page directories" we need to tell Apache that running CGI is "okay" (as there's always a risk involved, this you need to think yourself) from these, so: ... Options ExecCGI ... ... That's basically how to set the thing up and running. -Reko " ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkgng abilities (was: pkgng vs. portupgrade reporting ports outdated)
-Original Message- From: Robert Huff OK, Obi-wan - what's the replacement for: a) portsclean with the C, D (single and double), and L options? (Use no more than two commands.) b) pkg_sort ? With these, I will cheerfully delete portupgrade. portupgrade != pkg_old Actually, for me portupgrade with pkgng is getting close the ideal solution, made yesterday the portsnap fetch upgrade portversion -v | grep -v '=' portupgrade -rf php5 dance and got the whole php rebuild from source with one minor hitch. Due the way extensions.ini is rebuilt every php installation I got wrong module order and couple of modules got signal 11's when trying to rebuild. After manually correcting extensions.ini order I just portupgrade -f'd the 2 failed packages in dependency order, this time without any problems. pkgng pretty nicely built just the stuff that needed rebuild, not half the installed ports. I'm already running php in cgi mode, so no mod for apache was needed (and due the recent improvement, the said mod was not autoinstalled to my httpd.conf either). -Reko ___ 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
How to build PHP 5.4 without mysqlnd?
Greetings! Compiling mysqlnd into PHP is excess baggage for us not using MySQL in any shape or form. Yet it seems that there is no way for disabling in in the php5 building process. Setting WITHOUT_MYSQL=yes in make.conf does not do anything, removing --enable_mysqlnd in Makefile results in staging errors etc. So, any pointers how to make the build complete without mysqlnd, preferably so that I didn't need to manually fix the port files after every update? -Reko ___ 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: Wordpress PostGreSql plugin
-Original Message- From: Paul Pathiakis Hi, Could someone upgrade the wordpress port to have PostGreSQL interface option? wordpress.org/extend/plugins/postgresql-for-wordpress/ Seconded. There are some plugins that do not play along nicely with postgres, but in general the plugin has been working stable with the sites I've been running it on. Of course, one can always disable the MySQL dependency from the port makefile and put the pgsql plugin into place later, but it would be easier if the db backend could be selected from the port. CC sent to WP maintainer. -Reko ___ 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: lang/php53 dumps core
From: Volodymyr Kostyrko On some of my servers php keeps dumping core on some requests. There are days that it dumps core almost continuously. However there are days it works smoothly. What other data I should collect to file a PR? Or is this just a memory problem? Most probably it's php extension loading order, which is really bit of hit and miss to debug. Fooling around with /usr/local/php/extension.ini loading order might help once you find the culprit. Been thinking about one possible solution to this problem as everytime php is rebuilt, extension order changes, unless old and working extension ini is stored somewhere. What I've had in mind is having php itself install the extension file in known working load order with extensions commented out and then every extension port removing comment at installtime and putting comment back at deinstall. -Reko ___ 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: lang/php53 dumps core
-Original Message- From: Volodymyr Kostyrko php keeps dumping core on some requests. There are days that it dumps core almost continuously. However there are days it works smoothly. Do you use e-accelerator? No. Here is full extension list: Hmmm... you might try moving memcache.so to the top of the list. -Reko ___ 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: lang/php53 dumps core
From: Volodymyr Kostyrko
Rebuilding whole PHP without clang/gcc4.6 (my local settings) dumps core
with this backtrace:
...
Maybe something like this in /etc/make.conf
.if ${.CURDIR:M*php53*}
WITH_DEBUG=YES
.endif
.if ${.CURDIR:M*php5-redis*}
WITH_DEBUG=YES
.endif
And rebuild php+extensions.
then load the corefile to gdb.
-Reko
___
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
How to remove erroneous deps from pkgng
I'm testing out the pkgng system and somehow a port managed to pull devel/pkg-config into one low level port polluting whole db. pkg check just wants to install the annoying thing. Is there any way to get rid of that erroneous dependency? In production system, these kind of errors should be somehow correctable, especially if pkgng is to be used with ports as well. -Reko ___ 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: How to remove erroneous deps from pkgng
-Original Message- From: Bryan Drewery On 7/20/2012 11:57 AM, Reko Turja wrote: I'm testing out the pkgng system and somehow a port managed to pull devel/pkg-config into one low level port polluting whole db. pkg check just wants to install the annoying thing. Is there any way to get rid of that erroneous dependency? Which port is pulling it in? sqlite3 In production system, these kind of errors should be somehow correctable, especially if pkgng is to be used with ports as well. If the port defines invalid dependencies, it's not pkgng's problem, it's the port. True that, but there should be way of pruning cruft from the pkg tree anyway. Even if the system is going more and more to linux way for majority of users (one package fits all) there should be some kind of allowance for those who want to build their own ports, but do not have access to major build clusters ;) Ability to build and customise ports has been major reason for using freebsd for me. If you get force-fed all the dependencies the port does not really need something like portupgrade -a will become major PITA. Kimmo Paasiala wrote: The port devel/pkg-config is used in many ports, there's no harm in installing it. I'm not running Gnome nor any gnome stuff except glib2. pkg-config might be used somewhere, but it's completely unneeded in my systems and just extra baggage for building and tracking dependencies. -Reko ___ 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: How to remove erroneous deps from pkgng
Its use is not limited to Gnome, as you can see it's used in the build process of databases/sqlite3 and there are many other ports that have nothing to do with Gnome that use it the same way. The only thing that is wrong with it is that ends up being a run time dependency of sqlite3 instead of being only a build time dependency. Maybe this could be changed, anyone know if it's possible? Actually, sqlite3 builds and works quite fine with pkg-config dependency removed from makefile. So it's kinda silly to pull it in by force - of course it's not pkgng problem, but a problem in the port itself. Just hoping that in pkgng there would be some Yes I might shoot myself in foot, but sod it -options. On the other hand, based on experience with 2 boxes running pkgng+portupgrade experimentally for some days pkgng looks like pretty good backend. Just still with some minor nits. -Reko ___ 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: How to remove erroneous deps from pkgng
-Original Message- From: Kimmo Paasiala I'm wondering if the dependency is removed then will all ports that link to sqlite3 pull in pkg-config if it's not installed? After cleaning downstream ports and using portupgrade -f -O removes the dependency from that port, downstream is still affected though, so full downstream rebuild is needed in order to completely remove the dependency. And I'm not a dev, so having a utility that is only needed in certain linking scenarios isn't that useful for me as a dependency. -Reko ___ 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: How to remove erroneous deps from pkgng
-Original Message- From: Kimmo Paasiala Sqlite3 isn't the only one with a bogus dependency to pkg-config, for example audio/libsndfile does the same by using USE_GNOME=gnomehack Libxml2 is another, maybe grepping ports tree against pkg-config might be a start. -Reko ___ 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
