Re: FreeBSD 11.1-RELEASE - mail/milter-manager broken
Hi! > 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 That looks almost correct. If I had a repo for version, say 11.1 amd64, named 111, and a default ports tree, I would create a ports tree for milter to test, like this: poudriere ports -p milt -c Then I can create a 111-milt-make.conf with this: .if ${.CURDIR:M*/mail/milter-manager} DEFAULT_VERSIONS+=ruby=2.5 .endif and testbuild using: poudriere bulk -T -p milt -j 111 mail/milter-manager -- p...@opsec.eu+49 171 3101372 2 years to go ! ___ 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! > 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 ! ___ 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
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. -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ 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>>> 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! > 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. Tested it, seems to still dump core. Backtrace is at http://people.freebsd.org/~pi/logs/milter-backtrace.txt Anything I can test... ? -- p...@opsec.eu+49 171 3101372 2 years to go ! ___ 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> 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"
Re: FreeBSD 11.1-RELEASE - mail/milter-manager broken
Hello, From: Leander SchäferSubject: 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"
Re: 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. Can you provide a backtrace and submit a PR to bugs.freebsd.org ? -- p...@opsec.eu+49 171 3101372 2 years to go ! ___ 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"