Hey,
mpdscribble is marked as unfetchable, but is available at
http://www.musicpd.org/download/ now.
-Stephen
8c8
< MASTER_SITES= SF/musicpd/${PORTNAME}/${PORTVERSION}
---
> MASTER_SITES= http://www.musicpd.org/download/${PORTNAME}/${PORTVERSION}/
__
Patrick Powell wrote:
> Please do not switch to a new version of Perl until ModPerl2 works.
> This, for me, is a show stopper, and I suspect for a lot of people.
>
> Do you have a list of the current Perl Modules or associated items
> that do not work?
I agree - though I build everything with my
Patrick Powell wrote:
> Please do not switch to a new version of Perl until ModPerl2 works.
> This, for me, is a show stopper, and I suspect for a lot of people.
>
> Do you have a list of the current Perl Modules or associated items
> that do not work?
I agree - though I build everything with my
Patrick Powell wrote:
> Ummm... Guilty as charged. The only reason I updated to 5.20 was that
> the pkg repository changed.
>
> However, I think that making 5.22 the default before fixing up (for
> me at least) some issues with
> modperl support might be a bit premature.
>
> Just for my informat
Please do not switch to a new version of Perl until ModPerl2 works.
This, for me, is a show stopper, and I suspect for a lot of people.
Do you have a list of the current Perl Modules or associated items
that do not work?
On 08/28/15 08:06, Kurt Jaeger wrote:
Hi!
In one or two weeks, I'll be
On 08/28/15 09:16, Mathieu Arnold wrote:
+--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
On 09/01/15 00:03, dutchman01 wrote:
> Hi,
>
>
>
> Can you please upgrade lighttpd-1.4.36 to ighttpd-1.4.37.
I just took the PR with the update (bug 202637), which was added little
time ago, I just need a little time still for testing. Will commit shortly.
Please note that the new version got
Hi,
Can you please upgrade lighttpd-1.4.36 to ighttpd-1.4.37.
It contains a lot of fixes for freebsd too
http://www.lighttpd.net/
Regards,
Dutchman
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/lis
Hi!
On 8/31/15, Kurt Jaeger wrote:
> Hi!
>
>> There are currently two remaining PRs with patches for mail/ifile
>> (202572) and net-p2p/namecoin (2012603), getting those committed soon
>> would avoid traumas in the ports tree once FORTIFY_SOURCE is committed.
>
> 202572: done.
Cool! Thank you!
>
Hi!
> There are currently two remaining PRs with patches for mail/ifile
> (202572) and net-p2p/namecoin (2012603), getting those committed soon
> would avoid traumas in the ports tree once FORTIFY_SOURCE is committed.
202572: done.
--
p...@opsec.eu+49 171 3101372
Dear ports developers;
This year I mentored Oliver Pinter's GSoC project [1] to port
FORTIFY_SOURCE to FreeBSD. The project was more complex than we
thought initially but it was successful.
For those of you that haven't heard of it, it's a trick supported by
libc to enable bounds-checking on co
No verbose output or any useful info in the log file. When debugging, I see
this:
Program received signal SIGSEGV, Segmentation fault.
0x000800a8fdd4 in tn5250_terminal_config () from /usr/local/lib/lib5250.so.0
In /usr/local/lib I do see these 5250 files:
lib5250.alib5250.so
I build my own customized packages using poudriere. Lately (roughy about
when go changed from 1.4 to 1.5) it cannot build the go 1.4.2 bootstrap. It
fails with a bus error. This also is roughly about the time I upgraded my
poudriere server from 10.1 to 10.2.
Is anyone observing this?
Any hints on
Hi!
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198925
>
> Could anyone please look at this bug report?
Done.
--
p...@opsec.eu+49 171 3101372 5 years to go !
___
freebsd-ports@freebsd.org mailing list
https
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
Good day!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198925
Could anyone please look at this bug report?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd
Hi,
Try to add 'no-secmem-warning' in $HOME/.gnupg/gpg.conf
Regards,
--
Carlos Jacobo Puga Medina
PGP fingerprint = C60E 9497 5302 793B CC2D BB89 A1F3 5D66 E6D0 5453
signature.asc
Description: This is a digitally signed message part
17 matches
Mail list logo
