Matthias Kilian wrote:
> On Sat, Feb 27, 2016 at 02:04:37AM -0500, Michael McConville wrote:
> > This port seems truly ancient - if I understand correctly, it's been on
> > version 1.6.1 since it was imported in 1997. The fact that it's a server
> > makes this less tolerable. I came across it while
Hi,
On Sat, Feb 27, 2016 at 02:04:37AM -0500, Michael McConville wrote:
> This port seems truly ancient - if I understand correctly, it's been on
> version 1.6.1 since it was imported in 1997. The fact that it's a server
> makes this less tolerable. I came across it while scanning distfiles for
>
This port seems truly ancient - if I understand correctly, it's been on
version 1.6.1 since it was imported in 1997. The fact that it's a server
makes this less tolerable. I came across it while scanning distfiles for
undefined behavior... And it has a patch that changes gets(3) to
fgets(3). What's
Update to the latest stable release. This fixes a crash when accessing the
preferences. Added patches are to fix a compilation issue in this release with
libnotify. The fix was made upstream [0] already so should be in the next
release.
Tim.
[0] https://github.com/lwindolf/liferea/compare/v
On Sat, 27 Feb 2016 02:12:27 +0100
Adam Wolk wrote:
> Hi ports@
>
> The update itself is fairly straightforward but the changes are not
> backwards compatible. Additionally upstream is undergoing through
> development practice changes (introducing stable branches, security
> releases) and it's s
Hi ports@
The update itself is fairly straightforward but the changes are not
backwards compatible. Additionally upstream is undergoing through
development practice changes (introducing stable branches, security
releases) and it's still not perfectly fleshed out.
PORT CHANGES:
- with -DLWS_WITHO
I've been having lots of Firefox crashes. I am running Firefox from
ports (v 39.0.3) on amd64 5.8 -stable.
I increased my limits in login.conf. I have tried a few different
combinations, but this is what I'm doing currently:
$ getcap -f /etc/login.conf staff
staff:datasize-cur=3500M:datasize-ma
On Fri, Feb 26, 2016 at 11:11:01AM -0500, Michael McConville wrote:
> Seems like the Python module's not working in some context, unless I'm
> doing something wrong. I suspect that rm'ing your /usr/local/bin/python
> symlink (if you have one) will expose this.
This port uses ${WRKDIR}/bin/python w
On Thu, Feb 25, 2016 at 09:21:54AM -0700, Ken wrote:
> So reading the documentation on porting , I wanted to communicate my intent
> and verify this is not already a port being worked on. So is anyone already
> working on a z3 port?
FWIW, there's no port of z3 in openbsd-wip:
https://github.com/ja
