Re: FreeBSD 11.2-RELEASE (64bit) databases/mariadb103-server
Hi, Looks fine now. Thanks for your quick response. Best regards, Leander Am 12.11.18 um 19:26 schrieb Walter Schwarzenfeld: > I am not clear if it is the same error as in > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233135 > > If it is, it is fixed few moments ago with > > https://svnweb.freebsd.org/ports?view=revision=484810 > > ___ > 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: FreeBSD 11.2-RELEASE (64bit) databases/mariadb103-server
Hi, Looksfine now. Thanks for your quick response Best regards, Leander Am 12.11.18 um 21:29 schrieb Bernard Spil: > On 2018-11-12 19:13, Leander Schäfer wrote: >> Hello, >> >> databases/mariadb103-server doesn't want to build any more. I use >> poudriere to build own local package repositories. It seems like one of >> the two last updates broke databases/mariadb103-server port for me: >> - 12 Nov 2018 16:58:52 or >> - 10 Nov 2018 14:11:46 >> >> https://www.freshports.org/databases/mariadb103-server/ >> >> My make.conf looks like this: >> >> DEFAULT_VERSIONS+=php=71 >> DEFAULT_VERSIONS+=pgsql=9.6 >> DEFAULT_VERSIONS+=mysql=8.0 >> DEFAULT_VERSIONS+=samba=4.8 >> DEFAULT_VERSIONS+=python=2.7 python2=2.7 python3=3.6 >> DEFAULT_VERSIONS+=ssl=openssl >> >> The options of databases/mariadb103-server are left default except >> GSSAPI_NONE. >> >> OPTIONS_FILE_SET+=CONNECT_EXTRA >> OPTIONS_FILE_SET+=DOCS >> OPTIONS_FILE_SET+=WSREP >> OPTIONS_FILE_UNSET+=LZ4 >> OPTIONS_FILE_UNSET+=LZO >> OPTIONS_FILE_UNSET+=SNAPPY >> OPTIONS_FILE_UNSET+=ZSTD >> OPTIONS_FILE_SET+=INNOBASE >> OPTIONS_FILE_UNSET+=MROONGA >> OPTIONS_FILE_UNSET+=OQGRAPH >> OPTIONS_FILE_UNSET+=ROCKSDB >> OPTIONS_FILE_SET+=SPHINX >> OPTIONS_FILE_SET+=SPIDER >> OPTIONS_FILE_UNSET+=TOKUDB >> OPTIONS_FILE_UNSET+=ZMQ >> OPTIONS_FILE_UNSET+=MSGPACK >> OPTIONS_FILE_UNSET+=GSSAPI_BASE >> OPTIONS_FILE_UNSET+=GSSAPI_HEIMDAL >> OPTIONS_FILE_UNSET+=GSSAPI_MIT >> OPTIONS_FILE_SET+=GSSAPI_NONE >> >> >> [...] >> >> --- storage/connect/CMakeFiles/connect.dir/all --- >> [ 87%] Building CXX object >> storage/connect/CMakeFiles/connect.dir/ha_connect.cc.o >> cd >> /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10/storage/connect >> >> && /usr/local/libexec/ccache/c++ -DFORCE_INIT_OF_VARS -DGZ_SUPPORT >> -DHAVE_CONFIG_H -DHUGE_SUPPORT -DLIBXML2_SUPPORT -DLINUX -DMARIADB >> -DMYSQL_DYNAMIC_PLUGIN -DNOCRYPT -DODBC_SUPPORT -DUBUNTU -DUNIX >> -DVCT_SUPPORT -DXMAP -DZIP_SUPPORT -Dconnect_EXPORTS >> -I/wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10/include >> >> -I/wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10/sql >> >> -I/wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10/pcre >> >> -I/usr/local/include -I/usr/local/include/libxml2 -O2 -pipe >> -fstack-protector -isystem /usr/local/include -fno-strict-aliasing >> -isystem /usr/local/include -Wl,-z,relro,-z,now -fstack-protector >> --param=ssp-buffer-size=4 -fno-rtti -Wall -Wmissing-declarations >> -Wno-unused-function -Wno-unused-variable -Wno-unused-value >> -Wno-parentheses -Wno-strict-aliasing -Wno-implicit-fallthrough >> -fpermissive -fexceptions -fPIC -O2 -pipe -fstack-protector -isystem >> /usr/local/include -fno-strict-aliasing -isystem /usr/local/include >> -D_FORTIFY_SOURCE=2 -DDBUG_OFF -fPIC -o >> CMakeFiles/connect.dir/ha_connect.cc.o -c >> /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10/storage/connect/ha_connect.cc >> >> --- extra/mariabackup/CMakeFiles/mariabackup.dir/all --- >> /usr/bin/ld: mariabackup: hidden symbol >> `_Z31fil_space_verify_crypt_checksumPhRK11page_size_tmm' isn't defined >> /usr/bin/ld: final link failed: Nonrepresentable section on output >> c++: error: linker command failed with exit code 1 (use -v to see >> invocation) >> *** [extra/mariabackup/mariabackup] Error code 1 >> >> make[3]: stopped in >> /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10 >> 1 error >> >> make[3]: stopped in >> /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10 >> *** [extra/mariabackup/CMakeFiles/mariabackup.dir/all] Error code 2 >> >> make[2]: stopped in >> /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10 >> --- storage/innobase/CMakeFiles/innobase.dir/all --- >> Scanning dependencies of target innobase >> A failure has been detected in another branch of the parallel make >> >> make[3]: stopped in >> /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10 >> *** [storage/innobase/CMakeFiles/innobase.dir/all] Error code 2 >> >> make[2]: stopped in >> /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10 >> --- plugin/metadata_lock_info/CMakeFiles/metadata_lock_info.dir/all --- >> c++: warning: -Wl,-z,relro,-z,now: 'linker' input unused >> [-Wunused-command-line-argument] >> --- storage/bla
FreeBSD 11.2-RELEASE (64bit) databases/mariadb103-server
Hello, databases/mariadb103-server doesn't want to build any more. I use poudriere to build own local package repositories. It seems like one of the two last updates broke databases/mariadb103-server port for me: - 12 Nov 2018 16:58:52 or - 10 Nov 2018 14:11:46 https://www.freshports.org/databases/mariadb103-server/ My make.conf looks like this: DEFAULT_VERSIONS+=php=71 DEFAULT_VERSIONS+=pgsql=9.6 DEFAULT_VERSIONS+=mysql=8.0 DEFAULT_VERSIONS+=samba=4.8 DEFAULT_VERSIONS+=python=2.7 python2=2.7 python3=3.6 DEFAULT_VERSIONS+=ssl=openssl The options of databases/mariadb103-server are left default except GSSAPI_NONE. OPTIONS_FILE_SET+=CONNECT_EXTRA OPTIONS_FILE_SET+=DOCS OPTIONS_FILE_SET+=WSREP OPTIONS_FILE_UNSET+=LZ4 OPTIONS_FILE_UNSET+=LZO OPTIONS_FILE_UNSET+=SNAPPY OPTIONS_FILE_UNSET+=ZSTD OPTIONS_FILE_SET+=INNOBASE OPTIONS_FILE_UNSET+=MROONGA OPTIONS_FILE_UNSET+=OQGRAPH OPTIONS_FILE_UNSET+=ROCKSDB OPTIONS_FILE_SET+=SPHINX OPTIONS_FILE_SET+=SPIDER OPTIONS_FILE_UNSET+=TOKUDB OPTIONS_FILE_UNSET+=ZMQ OPTIONS_FILE_UNSET+=MSGPACK OPTIONS_FILE_UNSET+=GSSAPI_BASE OPTIONS_FILE_UNSET+=GSSAPI_HEIMDAL OPTIONS_FILE_UNSET+=GSSAPI_MIT OPTIONS_FILE_SET+=GSSAPI_NONE [...] --- storage/connect/CMakeFiles/connect.dir/all --- [ 87%] Building CXX object storage/connect/CMakeFiles/connect.dir/ha_connect.cc.o cd /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10/storage/connect && /usr/local/libexec/ccache/c++ -DFORCE_INIT_OF_VARS -DGZ_SUPPORT -DHAVE_CONFIG_H -DHUGE_SUPPORT -DLIBXML2_SUPPORT -DLINUX -DMARIADB -DMYSQL_DYNAMIC_PLUGIN -DNOCRYPT -DODBC_SUPPORT -DUBUNTU -DUNIX -DVCT_SUPPORT -DXMAP -DZIP_SUPPORT -Dconnect_EXPORTS -I/wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10/include -I/wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10/sql -I/wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10/pcre -I/usr/local/include -I/usr/local/include/libxml2 -O2 -pipe -fstack-protector -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include -Wl,-z,relro,-z,now -fstack-protector --param=ssp-buffer-size=4 -fno-rtti -Wall -Wmissing-declarations -Wno-unused-function -Wno-unused-variable -Wno-unused-value -Wno-parentheses -Wno-strict-aliasing -Wno-implicit-fallthrough -fpermissive -fexceptions -fPIC -O2 -pipe -fstack-protector -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include -D_FORTIFY_SOURCE=2 -DDBUG_OFF -fPIC -o CMakeFiles/connect.dir/ha_connect.cc.o -c /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10/storage/connect/ha_connect.cc --- extra/mariabackup/CMakeFiles/mariabackup.dir/all --- /usr/bin/ld: mariabackup: hidden symbol `_Z31fil_space_verify_crypt_checksumPhRK11page_size_tmm' isn't defined /usr/bin/ld: final link failed: Nonrepresentable section on output c++: error: linker command failed with exit code 1 (use -v to see invocation) *** [extra/mariabackup/mariabackup] Error code 1 make[3]: stopped in /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10 1 error make[3]: stopped in /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10 *** [extra/mariabackup/CMakeFiles/mariabackup.dir/all] Error code 2 make[2]: stopped in /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10 --- storage/innobase/CMakeFiles/innobase.dir/all --- Scanning dependencies of target innobase A failure has been detected in another branch of the parallel make make[3]: stopped in /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10 *** [storage/innobase/CMakeFiles/innobase.dir/all] Error code 2 make[2]: stopped in /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10 --- plugin/metadata_lock_info/CMakeFiles/metadata_lock_info.dir/all --- c++: warning: -Wl,-z,relro,-z,now: 'linker' input unused [-Wunused-command-line-argument] --- storage/blackhole/CMakeFiles/blackhole.dir/all --- c++: warning: -Wl,-z,relro,-z,now: 'linker' input unused [-Wunused-command-line-argument] --- storage/federatedx/CMakeFiles/federatedx.dir/all --- c++: warning: -Wl,-z,relro,-z,now: 'linker' input unused [-Wunused-command-line-argument] --- storage/test_sql_discovery/CMakeFiles/test_sql_discovery.dir/all --- A failure has been detected in another branch of the parallel make make[3]: stopped in /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10 *** [storage/test_sql_discovery/CMakeFiles/test_sql_discovery.dir/all] Error code 2 make[2]: stopped in /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10 --- plugin/qc_info/CMakeFiles/query_cache_info.dir/all --- A failure has been detected in another branch of the parallel make make[3]: stopped in /wrkdirs/usr/ports/databases/mariadb103-server/work/mariadb-10.3.10 --- storage/spider/CMakeFiles/spider.dir/all --- c++: warning: -Wl,-z,relro,-z,now: 'linker' input unused [-Wunused-command-line-argument] --- plugin/qc_info/CMakeFiles/query_cache_info.dir/all --- ***
Re: FreeBSD textproc/elasticsearch6 does not honour /etc/profile
Hello Mark, Thanks for your reply. I didn't know about the elasticsearch_env="" - so thanksfor that. So my follow-up questions are: * How would I have to set up elasticsearch_env="", cause according to the man of env elasticsearch_env="-S -P /usr/local/bin:/usr/local/sbin" wouldn't do the job. * What needs to be changed, so elasticsearch's auto detect script would work with regular values of PATH? Cause currently the default PATH is like: PATH=/sbin:/bin:/usr/sbin:/usr/bin and this won't work with an openjdk compiled from ports. Cause this would be my prefered way. Can I post your replies in the FreeBSD forum? Might be useful for others as well ;) Thanks a lot Best regards, Leander Am 30.03.18 um 21:34 schrieb Mark Felder: > > On Thu, Mar 29, 2018, at 05:43, Leander Schäfer wrote: >> Hello, >> >> it looks like textproc/elasticsearch6 does not honour /etc/profile? >> Please have a look for detailed description and reproduction of the >> issue: >> https://forums.freebsd.org/threads/textproc-elasticsearch6-does-not-honour-etc-profile.65338/ >> >> Best regards, >> >> Leander S. > I'm pretty sure this is not supposed to work. /etc/profile is used by sh(1) > and would only be read during a login shell. The FreeBSD rc subsystem uses > "su -m" when running processes as a specific user, not "su -l". The "su -l" > would fail because ElasticSearch's user has a default shell of /sbin/nologin. > As far as I can tell this is normal behavior. > > If you need to change env for Elastic you can use the elasticsearch_env="" in > /etc/rc.conf. Any further questions about overcoming issues in your > environment are welcome. We also have a list for elastic now called > "freebsd-elas...@freebsd.org". > > > Hope that helps, > > ___ 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 textproc/elasticsearch6 does not honour /etc/profile
Hello, it looks like textproc/elasticsearch6 does not honour /etc/profile? Please have a look for detailed description and reproduction of the issue: https://forums.freebsd.org/threads/textproc-elasticsearch6-does-not-honour-etc-profile.65338/ Best regards, Leander S. ___ 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: FreeBSD 11.1-RELEASE - mail/milter-manager broken
Alright, but how am I going to tell my poudriere to build this specific port
‘mail/milter-manager‘ with the specific ‘lang/ruby25‘ without forcing all the
other ports to be built with ‘lang/ruby25‘. This far I‘m only aware of using
DEFAULT_VERSIONS+=ruby=2.5
in the /usr/local/etc/poudriere.d/repo-make.conf
unfortunately enforcing it this the global way, ruby 2.5 will break other ports
being built in this repo and not harmonize as desired. I was hoping for
something oldschool like in poudrier's
/usr/local/etc/poudriere.d/repo-make.conf:
.if ${CURDIR:M*/ports/mail/milter-manager}
DEFAULT_VERSIONS+=ruby=2.5
.endif
Any clue how this is done with poudriere?
Best regards,
Leander
Am 19.03.18 um 02:07 schrieb Kenji Okimoto:
> You cannot use milter-manager with Ruby 2.4.3.
> It's known issue. It has been fixed in Ruby 2.5.0 and
> https://github.com/ruby/ruby/tree/ruby_2_4
> If you want to cherry-pick the patch see
> https://github.com/ruby/ruby/commit/3d4a397354fd8d27c5eb91ca5c3bd7afe9b11af0#diff-7875e170ada1a2b62a8c8798729afa11
>
>
> ---
>
> ** [bugs:#7] Segmentation fault (core dumped)**
>
> **Status:** open
> **Group:** v1.0_(example)
> **Created:** Sun Mar 18, 2018 10:30 AM UTC by Leander Schäfer
> **Last Updated:** Sun Mar 18, 2018 11:21 AM UTC
> **Owner:** nobody
>
>
> Execution of milter-manager binary results in a Segmentation fault (core
> dumped).
> OS: FreeBSD 11.1-RELEASE
>
> pkg info milter-manager
> milter-manager-2.0.7_1
> Name : milter-manager
> Version: 2.0.7_1
> Installed on : Sun Mar 18 11:12:56 2018 CET
> Origin : mail/milter-manager
> Architecture : FreeBSD:11:amd64
> Prefix : /usr/local
> Categories : ruby mail
> Licenses : GPLv3, LGPL3, GFDL, AGPLv3
> Maintainer : po...@freebsd.org
> WWW: http://milter-manager.sourceforge.net/
> Comment: Super milter that can invoke several milters selectively
> Options:
> DOCS : on
> EXAMPLES : on
> Shared Libs required:
> libintl.so.8
> libglib-2.0.so.0
> libgobject-2.0.so.0
> libgmodule-2.0.so.0
> libruby24.so.24
> libgthread-2.0.so.0
> libev.so.4
> libunwind.so.8
> Shared Libs provided:
> libmilter-core.so.0
> libmilter-server.so.0
> libmilter-client.so.0
> libmilter-manager.so.0
> libmilter.so.1
> Annotations:
> repo_type : binary
> repository : FreeBSD
> Flat size : 4.66MiB
> Description:
> milter manager protects you from spam mails and virus mails effectively
> with milter. milter manager has embedded Ruby interpreter to control
> milters flexibly.
>
> WWW: http://milter-manager.sourceforge.net/
>
>
>
> ---
>
> Sent from sourceforge.net because you indicated interest in
> <https://sourceforge.net/p/milter-manager/bugs/7/>
>
>
>
> To unsubscribe from further messages, please visit
> <https://sourceforge.net/auth/subscriptions/>
Am 19.03.18 um 08:35 schrieb Kurt Jaeger:
Hi!
> I'm most certain you did, but just to be safe: are you sure you used the
> updated version 2.1.1 / patch from Yasuhiro? Cause the changes of
> Yasuhiro did not reflect for my poudriere when it pulled the latest
> ports tree. If you applied the changes manually to your poudriere, how
> did you do this?
I have a svn checkout of the ports, updated that version, then
copied the milter files to the poudriere ports tree I use
to do testbuilds.
The build version was used to upgrade a testbox:
pkg info | grep milter
milter-manager-2.1.1 Super milter that can invoke several milters selectively
-- p...@opsec.eu +49 171 3101372 2 years to go !
Am 19.03.18 um 00:07 schrieb Yasuhiro KIMURA:
From: Leander Schäfer <i...@netocean.de>
Subject: Re: FreeBSD 11.1-RELEASE - mail/milter-manager broken
Date: Sun, 18 Mar 2018 17:41:06 +0200
> I was trying to re-build my poudriere package server. Unfortunately it
> did not reflect your changes after I updated the ports. Instead the
> current ports tree still holds milter-manager version 2.0.7. Is it
> commited yet?
No, It is not committed yet. So if you try tha patch you need to
manually download and apply it to your ports tree.
Best Regards.
---
Yasuhiro KIMURA
Am 19.03.18 um 00:03 schrieb Matthew D. Fuller:
> On Sun, Mar 18, 2018 at 08:10:14PM +0100 I heard the voice of
> Kurt Jaeger, and lo! it spake thus:
>> Tested it, seems to still dump core.
>>
>> Backtrace is at
>>
>> http://people.freebsd.org/~pi/logs/milter-backtrace.txt
> I recall trying to build it on ruby 2.4 on a server some time back
> (early last year? It's been a while...) and it failed to even start
> up. Went back to 2.3 and it's been solid since. So I'd guess it's
> ruby version dependent.
>
>
___
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: FreeBSD 11.1-RELEASE - mail/milter-manager broken
Hi Kurt, I'm most certain you did, but just to be safe: are you sure you used the updated version 2.1.1 / patch from Yasuhiro? Cause the changes of Yasuhiro did not reflect for my poudriere when it pulled the latest ports tree. If you applied the changes manually to your poudriere, how did you do this? Best regards, Leander Am 18.03.18 um 21:10 schrieb Kurt Jaeger: > Hi! > > Tested it, seems to still dump core. > > Backtrace is at > > http://people.freebsd.org/~pi/logs/milter-backtrace.txt > > Anything I can test... ? > Am 18.03.18 um 17:41 schrieb Leander Schäfer: > Hi Yasuhiro, > > I was trying to re-build my poudriere package server. Unfortunately it > did not reflect your changes after I updated the ports. Instead the > current ports tree still holds milter-manager version 2.0.7. Is it > commited yet? > > Best regards, > Leander > > > Am 18.03.18 um 15:07 schrieb Leander Schäfer: >> Hi Yasuhiro, >> >> Thank you for your feedback. I was about to file my bug report to >> https://bugs.freebsd.org when I found your update. The Segmentation >> fault (core dumped) appears already when you execute "milter-manager" >> binary without any further options/flags or configuration file. I'm also >> using poudriere and 11.1-RELEASE amd64 - so lets see if it works now. >> >> Best regards, >> Leander >> >> Am 18.03.18 um 14:48 schrieb Yasuhiro KIMURA: >>> Hello, >>> >>> From: Leander Schäfer <i...@netocean.de> >>> Subject: FreeBSD 11.1-RELEASE - mail/milter-manager broken >>> Date: Sun, 18 Mar 2018 12:18:24 +0200 >>> >>>> It seems like the package and the port mail/milter-manager are broken >>>> and it has no maintainer. To be more specific, I keep on getting a >>>> "Segmentation fault (core dumped)" when executing the binary. I assume >>>> it is being compiled against something which milter-manager is not >>>> compatible yet, cause both, pkg and port, used to work round about a >>>> half a year ago. >>> I found newer version 2.1.1 is released. So I updated the port and >>> submitted patch as following bug report. >>> >>> Bug 226692 - mail/milter-manager: update to 2.1.1 and etc. >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226692 >>> >>> I confirmed build succeeds with poudriere and 11.1-RELEASE amd64 >>> jail. But I didn't check if segmentation fault happens because I don't >>> know how to use it. So please test it if possible. >>> >>> Best Regards. >>> >>> --- >>> Yasuhiro KIMURA >>> ___ >>> 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: FreeBSD 11.1-RELEASE - mail/milter-manager broken
Hi Yasuhiro, Thank you for your feedback. I was about to file my bug report to https://bugs.freebsd.org when I found your update. The Segmentation fault (core dumped) appears already when you execute "milter-manager" binary without any further options/flags or configuration file. I'm also using poudriere and 11.1-RELEASE amd64 - so lets see if it works now. Best regards, Leander Am 18.03.18 um 14:48 schrieb Yasuhiro KIMURA: > Hello, > > From: Leander Schäfer <i...@netocean.de> > Subject: FreeBSD 11.1-RELEASE - mail/milter-manager broken > Date: Sun, 18 Mar 2018 12:18:24 +0200 > >> It seems like the package and the port mail/milter-manager are broken >> and it has no maintainer. To be more specific, I keep on getting a >> "Segmentation fault (core dumped)" when executing the binary. I assume >> it is being compiled against something which milter-manager is not >> compatible yet, cause both, pkg and port, used to work round about a >> half a year ago. > I found newer version 2.1.1 is released. So I updated the port and > submitted patch as following bug report. > > Bug 226692 - mail/milter-manager: update to 2.1.1 and etc. > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226692 > > I confirmed build succeeds with poudriere and 11.1-RELEASE amd64 > jail. But I didn't check if segmentation fault happens because I don't > know how to use it. So please test it if possible. > > Best Regards. > > --- > Yasuhiro KIMURA > ___ > 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 11.1-RELEASE - mail/milter-manager broken
Hi, It seems like the package and the port mail/milter-manager are broken and it has no maintainer. To be more specific, I keep on getting a "Segmentation fault (core dumped)" when executing the binary. I assume it is being compiled against something which milter-manager is not compatible yet, cause both, pkg and port, used to work round about a half a year ago. Best regards, Leander ___ 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"
devel/gitolite on FreeBSD 10.3-RELEASE (amd64)
Hi Ports it seems like devel/gitolite is broken. It doesn't run without changing the source code. It seems like PATH is not handed over as expected. Please have a look at the discussion we've had about this: https://forums.freebsd.org/threads/57463/#post-327723 Best regards Leander ___ 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 Lua Port seems broken
Hi Please have a look at the broken lua port. Thank you very much root@FreeBSD [/usr/ports/editors/vim]$ make install clean ===> Found saved configuration for vim-7.4.873 ===> vim-7.4.873 depends on file: /usr/local/sbin/pkg - found => vim-vim-v7.4.873_GH0.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch https://codeload.github.com/vim/vim/tar.gz/v7.4.873?dummy=/vim-vim-v7.4.873_GH0.tar.bz2 vim-vim-v7.4.873_GH0.tar.bz2 100% of 11 MB 518 kBps 00m23s ===> Fetching all distfiles required by vim-7.4.873 for building ===> Extracting for vim-7.4.873 => SHA256 Checksum OK for vim-vim-v7.4.873_GH0.tar.bz2. ===> vim-7.4.873 depends on file: /usr/local/bin/ruby21 - found ===> Patching for vim-7.4.873 ===> vim-7.4.873 depends on file: /usr/local/bin/ruby21 - found ===> Applying FreeBSD patches for vim-7.4.873 ===> vim-7.4.873 depends on file: /usr/local/bin/ruby21 - found ===> vim-7.4.873 depends on package: libiconv>=1.14_8 - found ===> vim-7.4.873 depends on executable: pkgconf - found ===> vim-7.4.873 depends on executable: msgfmt - found ===> vim-7.4.873 depends on file: /usr/local/bin/python2.7 - found ===> vim-7.4.873 depends on package: perl5>=5.20<5.21 - found ===> vim-7.4.873 depends on shared library: liblua-5.2.so - not found ===> lua52-5.2.4 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by lua52-5.2.4 for building ===> Extracting for lua52-5.2.4 => SHA256 Checksum OK for lua-5.2.4.tar.gz. ===> Patching for lua52-5.2.4 ===> Applying FreeBSD patches for lua52-5.2.4 ===> lua52-5.2.4 depends on shared library: libedit.so.0 - found (/usr/local/lib/libedit.so.0) ===> Configuring for lua52-5.2.4 ===> Building for lua52-5.2.4 make[3]: "/nonexistent" line 1: Need an operator make[3]: Fatal errors encountered -- cannot continue make[3]: stopped in /usr/ports/lang/lua52/work/lua-5.2.4/src ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[2]: stopped in /usr/ports/lang/lua52 *** Error code 1 Stop. make[1]: stopped in /usr/ports/editors/vim *** Error code 1 Stop. make: stopped in /usr/ports/editors/vim ___ 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: FreeBSD Lua Port seems broken
make is run as root. Pkg also fails. All other ports can be installed just fine. root@FreeBSD [~]$ pkg install vim Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Updating database digests format: 100% Checking integrity... done (1 conflicting) pkg: Cannot solve problem using SAT solver: cannot install package vim, remove it from request? [Y/n]: pkg: cannot find vim in the request pkg: cannot solve job using SAT solver Checking integrity... done (0 conflicting) The most recent version of packages are already installed Am 23.09.15 um 19:34 schrieb Lowell Gilbert: Leander Schäfer <leander.schae...@netocean.de> writes: Please have a look at the broken lua port. Thank you very much It builds fine for everyone else. ===> Building for lua52-5.2.4 make[3]: "/nonexistent" line 1: Need an operator make[3]: Fatal errors encountered -- cannot continue make[3]: stopped in /usr/ports/lang/lua52/work/lua-5.2.4/src ===> Compilation failed unexpectedly. /nonexistent is the "home" directory for system accounts that don't actually need a home directory at all. Maybe you're running make as a bogus user? ___ 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"
lang/lua52 on FreeBSD 10.1-RELEASE (amd64)
Hi lang/lua52 seems to have trouble and eventually fails. I thought I would let you know, so you have a chance to fix it when you have a chance. Thanks best regards Leander Installing patch-2.7.5... === Returning to build of vim-7.4.691 === vim-7.4.691 depends on file: /usr/local/bin/ruby21 - found === Applying distribution patches for vim-7.4.691 === Applying FreeBSD patches for vim-7.4.691 === vim-7.4.691 depends on file: /usr/local/bin/ruby21 - found === vim-7.4.691 depends on package: libiconv=1.14_8 - found === vim-7.4.691 depends on executable: pkgconf - found === vim-7.4.691 depends on executable: msgfmt - found === vim-7.4.691 depends on file: /usr/local/bin/python2.7 - found === vim-7.4.691 depends on file: /usr/local/bin/perl5.18.4 - found === vim-7.4.691 depends on shared library: liblua-5.2.so - not found ===Verifying for liblua-5.2.so in /usr/ports/lang/lua52 === lua52-5.2.4 depends on file: /usr/local/sbin/pkg - found = lua-5.2.4.tar.gz doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch http://www.lua.org/ftp/lua-5.2.4.tar.gz lua-5.2.4.tar.gz 0 B0 Bps === Fetching all distfiles required by lua52-5.2.4 for building === Extracting for lua52-5.2.4 = SHA256 Checksum OK for lua-5.2.4.tar.gz. === Patching for lua52-5.2.4 === Applying FreeBSD patches for lua52-5.2.4 === lua52-5.2.4 depends on shared library: libedit.so.0 - found (/usr/local/lib/libedit.so.0) === Configuring for lua52-5.2.4 === Building for lua52-5.2.4 make[2]: /nonexistent line 1: Need an operator make[2]: Fatal errors encountered -- cannot continue make[2]: stopped in /usr/ports/lang/lua52/work/lua-5.2.4/src === Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[1]: stopped in /usr/ports/lang/lua52 *** Error code 1 Stop. make: stopped in /usr/ports/editors/vim ___ 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
lang/lua52 on FreeBSD 10.1-RELEASE (amd64)
Hi
lang/lua52 seems to have trouble and eventually fails. I thought I would
let you know, so you have a chance to fix it when you have a chance.
Thanks best regards
Leander
Installing patch-2.7.5...
=== Returning to build of vim-7.4.691
=== vim-7.4.691 depends on file: /usr/local/bin/ruby21 - found
=== Applying distribution patches for vim-7.4.691
=== Applying FreeBSD patches for vim-7.4.691
=== vim-7.4.691 depends on file: /usr/local/bin/ruby21 - found
=== vim-7.4.691 depends on package: libiconv=1.14_8 - found
=== vim-7.4.691 depends on executable: pkgconf - found
=== vim-7.4.691 depends on executable: msgfmt - found
=== vim-7.4.691 depends on file: /usr/local/bin/python2.7 - found
=== vim-7.4.691 depends on file: /usr/local/bin/perl5.18.4 - found
=== vim-7.4.691 depends on shared library: liblua-5.2.so - not found
===Verifying for liblua-5.2.so in /usr/ports/lang/lua52
=== lua52-5.2.4 depends on file: /usr/local/sbin/pkg - found
= lua-5.2.4.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
= Attempting to fetch http://www.lua.org/ftp/lua-5.2.4.tar.gz
lua-5.2.4.tar.gz 0 B0 Bps
=== Fetching all distfiles required by lua52-5.2.4 for building
=== Extracting for lua52-5.2.4
= SHA256 Checksum OK for lua-5.2.4.tar.gz.
=== Patching for lua52-5.2.4
=== Applying FreeBSD patches for lua52-5.2.4
=== lua52-5.2.4 depends on shared library: libedit.so.0 - found
(/usr/local/lib/libedit.so.0)
=== Configuring for lua52-5.2.4
=== Building for lua52-5.2.4
make[2]: /nonexistent line 1: Need an operator
make[2]: Fatal errors encountered -- cannot continue
make[2]: stopped in /usr/ports/lang/lua52/work/lua-5.2.4/src
=== Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1
Stop.
make[1]: stopped in /usr/ports/lang/lua52
*** Error code 1
Stop.
make: stopped in /usr/ports/editors/vim
#
# And here the chekup on the single port itself #
#
root@FreeBSD [/usr/ports/lang/lua52]$ env BATCH=YES make install clean
=== lua52-5.2.4 depends on file: /usr/local/sbin/pkg - found
=== Fetching all distfiles required by lua52-5.2.4 for building
=== Extracting for lua52-5.2.4
= SHA256 Checksum OK for lua-5.2.4.tar.gz.
=== Patching for lua52-5.2.4
=== Applying FreeBSD patches for lua52-5.2.4
=== lua52-5.2.4 depends on shared library: libedit.so.0 - found
(/usr/local/lib/libedit.so.0)
=== Configuring for lua52-5.2.4
=== Building for lua52-5.2.4
make[1]: /nonexistent line 1: Need an operator
make[1]: Fatal errors encountered -- cannot continue
make[1]: stopped in /usr/ports/lang/lua52/work/lua-5.2.4/src
=== Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1
Stop.
make: stopped in /usr/ports/lang/lua52
root@FreeBSD [/usr/ports/lang/lua52]$ FILE=/etc/make.conf
root@FreeBSD [/usr/ports/lang/lua52]$ RESULT=$( cat ${FILE} | sed -E
'/MAKE_JOBS_UNSAFE=.*/d' )
root@FreeBSD [/usr/ports/lang/lua52]$ [[ ! -z ${RESULT} ]] echo
${RESULT} ${FILE}
root@FreeBSD [/usr/ports/lang/lua52]$ echo 'MAKE_JOBS_UNSAFE=yes' ${FILE}
root@FreeBSD [/usr/ports/lang/lua52]$ env BATCH=YES make install clean
=== Building for lua52-5.2.4
make[1]: /nonexistent line 1: Need an operator
make[1]: Fatal errors encountered -- cannot continue
make[1]: stopped in /usr/ports/lang/lua52/work/lua-5.2.4/src
*** Error code 1
Stop.
make: stopped in /usr/ports/lang/lua52
___
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
Port upgrade issue
Hi,
I have optimized the current rsyncd rc script some time ago. Added
features are e.g.:
* run multiple instances - as known eg. by OpenVPN rc-script
* pid lock files cleaned up nicely under
/var/run/rsync/{instance}.{pid,lock}
* added rc.conf variables for better control
o NAME_pidfile=/var/run/rsync/NAME.pid # Where to write process id
o NAME_lockfile=/var/run/rsync/NAME.lock # Support for the lqmax
connectionsrq parameter
This way the FreeBSD user can change pid and lock file without screwing
up rc-script expectations.
The port maintainer offered to apply the changes if I would provide them
to him as diff patch.
Emanuel Haupt said:
[...] You're the first one to ask for such a feature ever since I
maintain this port. But tell you what, If you can fabricate a clean,
well tested (poudriere logs) patch I will commit it. [...]
Well I did so (a couple of times) via email but unfortunately he never
replied or made any other move. Eventually I decided to open up a commit
request as described in the
Handbook_https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195232_
Unfortunately nothing has changed since ever then. I don't know if
something happened to the port maintainer or if he simply doesn't have
internet access anymore?! Now my question is what can I do / Who can I
ask to apply this patch?
Thank you
--- ./rsyncd-current2015-01-19 14:04:33.0 +0100
+++ /usr/local/etc/rc.d/rsyncd 2014-10-30 13:44:51.0 +0100
@@ -8,39 +8,83 @@
# BEFORE: securelevel
# KEYWORD: shutdown
-# Add the following lines to /etc/rc.conf to enable `rsyncd':
+# -
#
-# rsyncd_enable=YES
-# rsyncd_flags=set as needed
+# This script supports running multiple instances of rsyncd.
+# To run additional instances link this script to something like
+# % ln -s rsyncd rsyncd_foo
+# and define additional rsyncd_foo_* variables in one of
+# /etc/rc.conf, /etc/rc.conf.local or /etc/rc.conf.d/openvpn_foo
#
-# See rsync(1) for rsyncd_flags
+# Below NAME should be substituted with the name of this script. By default
+# it is rsyncd, so read as rsyncd_enable. If you linked the script to
+# rsyncd_foo, then read as rsyncd_foo_enable etc.
#
+# The following variables are supported (defaults are shown).
+# You can place them in any of
+# /etc/rc.conf, /etc/rc.conf.local or /etc/rc.conf.d/NAME
+#
+# NAME_enable=NO # set to YES to enable rsyncd
+#
+# # optional:
+# NAME_configfile=/usr/local/etc/rsync/NAME.conf # Where to look for config
file
+# NAME_pidfile=/var/run/rsync/NAME.pid# Where to write process id
+# NAME_lockfile=/var/run/rsync/NAME.lock # Support for the lqmax
connectionsrq parameter
+# NAME_flags=set as needed # See rsync(1) for
NAME_flags
+#
+# -
. /etc/rc.subr
-name=rsyncd
-rcvar=rsyncd_enable
+case ${0} in
+/etc/rc*)
+# during boot (shutdown) ${0} is /etc/rc (/etc/rc.shutdown),
+# so get the name of the script from $_file
+name=${_file}
+;;
+*)
+name=${0}
+;;
+esac
+
+name=${name##*/}
+rcvar=${name}_enable
+
command=/usr/local/bin/rsync
start_precmd=rsyncd_precmd
-pidfile=/var/run/$name.pid
+stop_postcmd=rsyncd_postcmd
# read configuration and set defaults
-load_rc_config $name
-: ${rsyncd_enable=NO}
-: ${rsyncd_configfile:=/usr/local/etc/rsync/$name.conf}
-
-required_files=${rsyncd_configfile}
-
-command_args=--daemon --config ${rsyncd_configfile}
-
-rsyncd_precmd()
-{
- if [ -f /usr/local/etc/$name.conf ] [ ! -L
/usr/local/etc/$name.conf ]; then
- echo Found /usr/local/etc/$name.conf in old location.
Migrating to /usr/local/etc/rsync/$name.conf.
- mv /usr/local/etc/$name.conf /usr/local/etc/rsync/$name.conf
- ln -s /usr/local/etc/rsync/$name.conf /usr/local/etc/$name.conf
- fi
+load_rc_config ${name}
+eval : \${${name}_enable:=\NO\}
+eval : \${${name}_configfile:=\/usr/local/etc/rsync/${name}.conf\}
+eval : \${${name}_pidfile:=\/var/run/rsync/${name}.pid\}
+eval : \${${name}_lockfile:=\/var/run/rsync/${name}.lock\}
+
+configfile=$(eval echo \${${name}_configfile} )
+pidfile=$(eval echo \${${name}_pidfile})
+lockfile=$(eval echo \${${name}_lockfile})
+
+required_files=${configfile}
+
+command_args=--daemon --config ${configfile} --dparam=pidfile=${pidfile}
--dparam=lockfile=${lockfile}
+
+rsyncd_precmd () {
+mkdir -p -m 0755 $(dirname ${pidfile})
+mkdir -p -m 0755 $(dirname ${lockfile})
+if [ -f /usr/local/etc/${name}.conf ] [ ! -L
/usr/local/etc/${name}.conf ]; then
+echo Found /usr/local/etc/${name}.conf in old location. Migrating to
${configfile}.
+mv /usr/local/etc/${name}.conf ${configfile}
+ln -s ${configfile} /usr/local/etc/${name}.conf
+fi
}
-run_rc_command $1
+rsyncd_postcmd() {
+rmdir $(dirname
