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 +-+ devel/ucommon | 6.1.11 | 6.5.7 +-+ 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 https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS-UP] switching default Perl to 5.22
Hi, In one or two weeks, I'll be switching the default Perl version to 5.22, and from now on, the new Perl will be added at the end of May when released, and switched to at the beginning of September. -- Mathieu Arnold pgp2UIXjRh1jZ.pgp Description: PGP signature
Re: [HEADS-UP] switching default Perl to 5.22
Hi! > In one or two weeks, I'll be switching the default Perl version to 5.22, > and from now on, the new Perl will be added at the end of May when > released, and switched to at the beginning of September. mod_perl is still broken with 5.22. Which is very sad. So maybe it's premature to switch the default ? -- p...@opsec.eu+49 171 3101372 5 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: [HEADS-UP] switching default Perl to 5.22
Hi!
> |> In one or two weeks, I'll be switching the default Perl version to 5.22,
> |> and from now on, the new Perl will be added at the end of May when
> |> released, and switched to at the beginning of September.
> |
> | mod_perl is still broken with 5.22. Which is very sad. So maybe
> | it's premature to switch the default ?
>
> But, it was building when I added Perl 5.22 in May, when did it break ?
ohauer marked it broken on the 9th of June.
The www/mod_perl2 Makefile says:
.if ${PERL_VER} == 5.22
BROKEN= PERL ${PERL_VER} is not supported by upstream,\
see
http://svn.apache.org/viewvc/perl/modperl/trunk/README?view=markup
.endif
There is:
https://rt.cpan.org/Ticket/Display.html?id=101962
I tried to understand that problem, but somehow it did not click 8-(
--
p...@opsec.eu+49 171 3101372 5 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: [HEADS-UP] switching default Perl to 5.22
+--On 28 août 2015 17:06:03 +0200 Kurt Jaeger wrote: | Hi! | |> In one or two weeks, I'll be switching the default Perl version to 5.22, |> and from now on, the new Perl will be added at the end of May when |> released, and switched to at the beginning of September. | | mod_perl is still broken with 5.22. Which is very sad. So maybe | it's premature to switch the default ? But, it was building when I added Perl 5.22 in May, when did it break ? -- Mathieu Arnold pgpwJ5o9Qq4en.pgp Description: PGP signature
Re: [HEADS-UP] switching default Perl to 5.22
+--On 28 août 2015 17:13:34 +0200 Kurt Jaeger wrote: | Hi! | |> |> In one or two weeks, I'll be switching the default Perl version to |> |> 5.22, and from now on, the new Perl will be added at the end of May |> |> when released, and switched to at the beginning of September. |> | |> | mod_perl is still broken with 5.22. Which is very sad. So maybe |> | it's premature to switch the default ? |> |> But, it was building when I added Perl 5.22 in May, when did it break ? | | ohauer marked it broken on the 9th of June. Oh, maybe it did not work and I told myself "never mind, mod_perl never works anyway" -- Mathieu Arnold pgpvjgGC3xX8t.pgp Description: PGP signature
Re: [HEADS-UP] switching default Perl to 5.22
2015-08-28 17:16, Mathieu Arnold wrote: +--On 28 août 2015 17:13:34 +0200 Kurt Jaeger wrote: |> |> In one or two weeks, I'll be switching the default Perl version to |> |> 5.22, and from now on, the new Perl will be added at the end of May |> |> when released, and switched to at the beginning of September. |> | |> | mod_perl is still broken with 5.22. Which is very sad. So maybe |> | it's premature to switch the default ? |> |> But, it was building when I added Perl 5.22 in May, when did it break ? | | ohauer marked it broken on the 9th of June. Oh, maybe it did not work and I told myself "never mind, mod_perl never works anyway" The lang/perl5.20 will still be in ports, for anyone that needs it. Being heavy Perl users we have switched to 5.22 when it hit the ports, and I have no complaints about it. Mark ___ 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: [HEADS-UP] switching default Perl to 5.22
+--On 28 août 2015 17:34:49 +0200 Mark Martinec wrote: | 2015-08-28 17:16, Mathieu Arnold wrote: |> +--On 28 août 2015 17:13:34 +0200 Kurt Jaeger wrote: |> |> |> In one or two weeks, I'll be switching the default Perl version |> to |> |> |> 5.22, and from now on, the new Perl will be added at the end of |> May |> |> |> when released, and switched to at the beginning of September. |> |> | |> |> | mod_perl is still broken with 5.22. Which is very sad. So maybe |> |> | it's premature to switch the default ? |> |> |> |> But, it was building when I added Perl 5.22 in May, when did it |> break ? |> | |> | ohauer marked it broken on the 9th of June. |> |> Oh, maybe it did not work and I told myself "never mind, mod_perl never |> works anyway" | | The lang/perl5.20 will still be in ports, for anyone that needs it. | | Being heavy Perl users we have switched to 5.22 when it hit the ports, | and I have no complaints about it. Oh, yes, Perl 5.20 will still be until 2018-12-31, as will 5.18 until 2017-12-31 and 5.16 until 2016-12-31 :-) But I'm talking about switching the default, it means people using packages will not have mod_perl. (And you really can't use a non default Perl, and binary packages for the rest.) -- Mathieu Arnold pgpBo3KXiHeEc.pgp Description: PGP signature
Re: [HEADS-UP] switching default Perl to 5.22
On 08/28/15 16:34, Mark Martinec wrote: > 2015-08-28 17:16, Mathieu Arnold wrote: >> +--On 28 août 2015 17:13:34 +0200 Kurt Jaeger wrote: >> |> |> In one or two weeks, I'll be switching the default Perl version to >> |> |> 5.22, and from now on, the new Perl will be added at the end of May >> |> |> when released, and switched to at the beginning of September. >> |> | >> |> | mod_perl is still broken with 5.22. Which is very sad. So maybe >> |> | it's premature to switch the default ? >> |> >> |> But, it was building when I added Perl 5.22 in May, when did it >> break ? >> | >> | ohauer marked it broken on the 9th of June. >> >> Oh, maybe it did not work and I told myself "never mind, mod_perl never >> works anyway" > > The lang/perl5.20 will still be in ports, for anyone that needs it. > > Being heavy Perl users we have switched to 5.22 when it hit the ports, > and I have no complaints about it. How many ports are going to be hit by CGI no longer being one of the core modules? I've certainly got a couple of my own to fix. Cheers, Matthew signature.asc Description: OpenPGP digital signature
Re: [HEADS-UP] switching default Perl to 5.22
+--On 28 août 2015 17:44:55 +0200 Mathieu Arnold wrote: | +--On 28 août 2015 17:34:49 +0200 Mark Martinec | wrote: || 2015-08-28 17:16, Mathieu Arnold wrote: ||> +--On 28 août 2015 17:13:34 +0200 Kurt Jaeger wrote: ||> |> |> In one or two weeks, I'll be switching the default Perl version ||> to ||> |> |> 5.22, and from now on, the new Perl will be added at the end of ||> May ||> |> |> when released, and switched to at the beginning of September. ||> |> | ||> |> | mod_perl is still broken with 5.22. Which is very sad. So maybe ||> |> | it's premature to switch the default ? ||> |> ||> |> But, it was building when I added Perl 5.22 in May, when did it ||> break ? ||> | ||> | ohauer marked it broken on the 9th of June. ||> ||> Oh, maybe it did not work and I told myself "never mind, mod_perl never ||> works anyway" || || The lang/perl5.20 will still be in ports, for anyone that needs it. || || Being heavy Perl users we have switched to 5.22 when it hit the ports, || and I have no complaints about it. | | Oh, yes, Perl 5.20 will still be until 2018-12-31, as will 5.18 until | 2017-12-31 and 5.16 until 2016-12-31 :-) Scratch that, remove one year for all those 0:-) -- Mathieu Arnold pgp44y_2fsM3u.pgp Description: PGP signature
Re: [HEADS-UP] switching default Perl to 5.22
On 28/08/2015 16:44, Mathieu Arnold wrote: +--On 28 août 2015 17:34:49 +0200 Mark Martinec wrote: | 2015-08-28 17:16, Mathieu Arnold wrote: |> +--On 28 août 2015 17:13:34 +0200 Kurt Jaeger wrote: |> |> |> In one or two weeks, I'll be switching the default Perl version |> to |> |> |> 5.22, and from now on, the new Perl will be added at the end of |> May |> |> |> when released, and switched to at the beginning of September. |> |> | |> |> | mod_perl is still broken with 5.22. Which is very sad. So maybe |> |> | it's premature to switch the default ? |> |> |> |> But, it was building when I added Perl 5.22 in May, when did it |> break ? |> | |> | ohauer marked it broken on the 9th of June. |> |> Oh, maybe it did not work and I told myself "never mind, mod_perl never |> works anyway" | | The lang/perl5.20 will still be in ports, for anyone that needs it. | | Being heavy Perl users we have switched to 5.22 when it hit the ports, | and I have no complaints about it. Oh, yes, Perl 5.20 will still be until 2018-12-31, as will 5.18 until 2017-12-31 and 5.16 until 2016-12-31 :-) But I'm talking about switching the default, it means people using packages will not have mod_perl. (And you really can't use a non default Perl, and binary packages for the rest.) Yer that's not good :( Regards Steve ___ 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: [HEADS-UP] switching default Perl to 5.22
On Fri, Aug 28, 2015 at 05:49:30PM +0200, Mathieu Arnold wrote: > > > +--On 28 ao??t 2015 17:44:55 +0200 Mathieu Arnold wrote: > | +--On 28 ao??t 2015 17:34:49 +0200 Mark Martinec > | wrote: > || 2015-08-28 17:16, Mathieu Arnold wrote: > ||> +--On 28 ao??t 2015 17:13:34 +0200 Kurt Jaeger wrote: > ||> |> |> In one or two weeks, I'll be switching the default Perl version > ||> to > ||> |> |> 5.22, and from now on, the new Perl will be added at the end of > ||> May > ||> |> |> when released, and switched to at the beginning of September. > ||> |> | > ||> |> | mod_perl is still broken with 5.22. Which is very sad. So maybe > ||> |> | it's premature to switch the default ? > ||> |> > ||> |> But, it was building when I added Perl 5.22 in May, when did it > ||> break ? > ||> | > ||> | ohauer marked it broken on the 9th of June. > ||> > ||> Oh, maybe it did not work and I told myself "never mind, mod_perl never > ||> works anyway" > || > || The lang/perl5.20 will still be in ports, for anyone that needs it. > || > || Being heavy Perl users we have switched to 5.22 when it hit the ports, > || and I have no complaints about it. > | > | Oh, yes, Perl 5.20 will still be until 2018-12-31, as will 5.18 until > | 2017-12-31 and 5.16 until 2016-12-31 :-) > > Scratch that, remove one year for all those 0:-) There is definitely some acrimony in the 5.22 release. I only mention Canary::Stability/stableperl bitter taste. The TeXlive tlmgr tripped over the cosmetic but annoying regression in 5.22, there were no fix some time ago, despite the fact that the bug was known for porters for long time, see http://www.perlmonks.org/?node_id=1132751 (the article claims that the issue was fixed, I am not sure). Previous policy, even if informal, was to wait for 5.xx.1 before bringing the port to the tree. May be, we should wait for xx.1 before switching the default port, at least ? ___ 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: [HEADS-UP] switching default Perl to 5.22
+--On 28 août 2015 19:11:21 +0300 Konstantin Belousov wrote: | Previous policy, even if informal, was to wait for 5.xx.1 before bringing | the port to the tree. May be, we should wait for xx.1 before switching | the default port, at least ? The previous policy was "oh shit, our default version is not supported any more, let's try and see how it goes with the version that will not be supported after this year." I've been bumping default Perl versions every six months for a long time so that we could catch up. Also, if everyone waits for the .1 release before using it, there will never be a .1 release. -- Mathieu Arnold pgp_cnCmOZvgl.pgp Description: PGP signature
Re: [HEADS-UP] switching default Perl to 5.22
+--On 28 août 2015 16:47:08 +0100 Matthew Seaman wrote: | On 08/28/15 16:34, Mark Martinec wrote: |> 2015-08-28 17:16, Mathieu Arnold wrote: |>> +--On 28 août 2015 17:13:34 +0200 Kurt Jaeger wrote: |>> |> |> In one or two weeks, I'll be switching the default Perl version to |>> |> |> 5.22, and from now on, the new Perl will be added at the end of |>> |> |> May when released, and switched to at the beginning of September. |>> |> | |>> |> | mod_perl is still broken with 5.22. Which is very sad. So maybe |>> |> | it's premature to switch the default ? |>> |> |>> |> But, it was building when I added Perl 5.22 in May, when did it |>> break ? |>> | |>> | ohauer marked it broken on the 9th of June. |>> |>> Oh, maybe it did not work and I told myself "never mind, mod_perl never |>> works anyway" |> |> The lang/perl5.20 will still be in ports, for anyone that needs it. |> |> Being heavy Perl users we have switched to 5.22 when it hit the ports, |> and I have no complaints about it. | | How many ports are going to be hit by CGI no longer being one of the | core modules? I've certainly got a couple of my own to fix. This should already be fixed, since Perl 5.22 was added in May. -- Mathieu Arnold pgpVzmGcNDFiY.pgp Description: PGP signature
Re: revive wmmemload port
On Fri, 28 Aug 2015, the wise A.J. "Fonz" van Werven wrote: Hmm, It seems like uses types such as u_int and dev_t without including , which is where those types are defined. I'm not sure whether that's a bug in FreeBSD or it's supposed to be this way, but in the meantime, does it help if you add #include to mem_freebsd.c? If so, I'd suggest adding a patch to the port's files/ directory. Hi, Adding results in less, but fatal errors as well: ... ===> Building for wmmemload-0.1.8 --- all --- /usr/bin/make all-recursive --- all-recursive --- Making all in src --- main.o --- --- mem_freebsd.o --- --- dockapp.o --- --- main.o --- cc -DHAVE_CONFIG_H -I. -I.. -I/usr/local/include -I/usr/local/include -O2 -pipe -march=nocona -fstack-protector -fno-strict-aliasing -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o main.c --- mem_freebsd.o --- cc -DHAVE_CONFIG_H -I. -I.. -I/usr/local/include -I/usr/local/include -O2 -pipe -march=nocona -fstack-protector -fno-strict-aliasing -MT mem_freebsd.o -MD -MP -MF .deps/mem_freebsd.Tpo -c -o mem_freebsd.o mem_freebsd.c --- dockapp.o --- cc -DHAVE_CONFIG_H -I. -I.. -I/usr/local/include -I/usr/local/include -O2 -pipe -march=nocona -fstack-protector -fno-strict-aliasing -MT dockapp.o -MD -MP -MF .deps/dockapp.Tpo -c -o dockapp.o dockapp.c --- mem_freebsd.o --- In file included from mem_freebsd.c:18: /usr/include/vm/vm_param.h:94:2: error: unknown type name 'u_int' u_int xsw_version; ^ /usr/include/vm/vm_param.h:95:2: error: unknown type name 'dev_t'; did you mean 'div_t'? dev_t xsw_dev; ^ /usr/include/stdlib.h:62:3: note: 'div_t' declared here } div_t; ^ 2 errors generated. *** [mem_freebsd.o] Error code 1 ... Regards, Marco ___ 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: revive wmmemload port
Marco Beishuizen wrote: > Adding results in less, but fatal errors as well: [snip] > --- mem_freebsd.o --- > In file included from mem_freebsd.c:18: > /usr/include/vm/vm_param.h:94:2: error: unknown type name 'u_int' > u_int xsw_version; > ^ > /usr/include/vm/vm_param.h:95:2: error: unknown type name 'dev_t'; did you > mean 'div_t'? > dev_t xsw_dev; > ^ > /usr/include/stdlib.h:62:3: note: 'div_t' declared here > } div_t; > ^ > 2 errors generated. > *** [mem_freebsd.o] Error code 1 > ... That *looks* like files being included in an incorrect order. Can you send me a tarball of the port directory as you have it now? With any luck I might be able to track down the problem more easily then. AvW -- I'm not completely useless, I can be used as a bad example. pgpiYTKxAqu7a.pgp Description: PGP signature
Re: [HEADS-UP] switching default Perl to 5.22
> On Aug 28, 2015, at 12:11 PM, Konstantin Belousov wrote: > >> On Fri, Aug 28, 2015 at 05:49:30PM +0200, Mathieu Arnold wrote: >> >> >> +--On 28 ao??t 2015 17:44:55 +0200 Mathieu Arnold wrote: >> | +--On 28 ao??t 2015 17:34:49 +0200 Mark Martinec >> | wrote: >> || 2015-08-28 17:16, Mathieu Arnold wrote: >> ||> +--On 28 ao??t 2015 17:13:34 +0200 Kurt Jaeger wrote: >> ||> |> |> In one or two weeks, I'll be switching the default Perl version >> ||> to >> ||> |> |> 5.22, and from now on, the new Perl will be added at the end of >> ||> May >> ||> |> |> when released, and switched to at the beginning of September. >> ||> |> | >> ||> |> | mod_perl is still broken with 5.22. Which is very sad. So maybe >> ||> |> | it's premature to switch the default ? >> ||> |> >> ||> |> But, it was building when I added Perl 5.22 in May, when did it >> ||> break ? >> ||> | >> ||> | ohauer marked it broken on the 9th of June. >> ||> >> ||> Oh, maybe it did not work and I told myself "never mind, mod_perl never >> ||> works anyway" >> || >> || The lang/perl5.20 will still be in ports, for anyone that needs it. >> || >> || Being heavy Perl users we have switched to 5.22 when it hit the ports, >> || and I have no complaints about it. >> | >> | Oh, yes, Perl 5.20 will still be until 2018-12-31, as will 5.18 until >> | 2017-12-31 and 5.16 until 2016-12-31 :-) >> >> Scratch that, remove one year for all those 0:-) > > There is definitely some acrimony in the 5.22 release. I only mention > Canary::Stability/stableperl bitter taste. The TeXlive tlmgr tripped > over the cosmetic but annoying regression in 5.22, there were no fix > some time ago, despite the fact that the bug was known for porters for > long time, see http://www.perlmonks.org/?node_id=1132751 (the article > claims that the issue was fixed, I am not sure). > > Previous policy, even if informal, was to wait for 5.xx.1 before bringing > the port to the tree. May be, we should wait for xx.1 before switching > the default port, at least ? I second this. I'm using 5.22 happily, however I think bumping the default is premature. I for one appreciate the conservative nature of FreeBSD and don't think we should feel compelled to keep up with the Joneses. ___ 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: revive wmmemload port
On Fri, 28 Aug 2015, the wise A.J. "Fonz" van Werven wrote: That *looks* like files being included in an incorrect order. Can you send me a tarball of the port directory as you have it now? With any luck I might be able to track down the problem more easily then. Yes, this was it. Seems to build ok now. Thanks for the help so far! Now I'll try to make a patch. -- It pays in England to be a revolutionary and a bible-smacker most of one's life and then come round. -- Lord Alfred Douglas ___ 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"
distfiles directory in poudriere
One of my ports depends on linux-oracle-jdk8 that must be downloaded by hand and place it in the distfiles directory before re-running 'make install' (license constraints). If I'm going to test my port with poudriere, where should I place the distribution file? Thanks in advance ___ 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: distfiles directory in poudriere
+--On 28 août 2015 23:25:59 +0200 Fernando Apesteguía wrote: | One of my ports depends on linux-oracle-jdk8 that must be downloaded | by hand and place it in the distfiles directory before re-running | 'make install' (license constraints). | | If I'm going to test my port with poudriere, where should I place the | distribution file? In the directory defined by DISTFILES_CACHE. -- Mathieu Arnold pgptyuAR3bZJO.pgp Description: PGP signature
MonoDevelop port
Hello, I would like to update the ports files for the MonoDevelop IDE to the latest version. I have contacted the m...@freebsd.org mailing list about my intentions with no response. What is the next step forward to submit an update? Do I just create the shar and submit it via bugzilla? Thanks, Russell ___ 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"
