hi
attached patch updates pgbadger,
also I'd like to take maintainership if no one
cares.
I'm unsure about the PLIST change, tough...
comments, ok?
thanks.
Index: Makefile
===
RCS file: /cvs/ports/databases/pgbadger/Makefile,v
retri
>This fixes stack smashing I've seen in Okteta.
>
>The problem is that fd_set by default uses limit (FD_SETSIZE) of 1024,
>unless FD_SETSIZE is set before including the header.
>The Qt4 source code contains some checks, but backtrace from GDB tells
>they're not enough. Instead of spending time on
I just noticed xstatbar using "quite a lot" more memory than I was
expecting. Does anyone fancy trying to track down the leak? It doesn't
look like any flags are needed to trigger the leak, but using "-s 0"
to avoid sleeping between updates makes it very easy to spot.
thanks Karel and Bryan,
I succeeded to compile JDK 1.8 with "ulimit -d 480".
(didn't check how many is minimum required,
just 480 (KB) was enough for my environment.)
% (ulimit -d 4800 ; make package ...)
time(cpu-seconds)unlimited
file(blocks) unlimited
coredump(blocks)
If we would rather restore pexpect as the default ssh backend instead of
paramiko,
this should do it.
Tim.
Index: Makefile
===
RCS file: /cvs/ports/sysutils/duplicity/Makefile,v
retrieving revision 1.35
diff -u -p -r1.35 Makefile
--
[ ... ]
>> As it was my first patch ever, I did it from scratch (the plist part
>> was my fault).
>
> Looks good!
@all thanks for help and feedback.
On Mon, February 8, 2016 7:59 am, Jérémie Courrèges-Anglas wrote:
> tro...@kagu-tsuchi.com writes:
>
>> Seems that with the change to duplicity 0.7, the default sftp backend
>> changed.
>> The manpage was being patched to say the default was pexpect over
>> paramiko.
>> This is no longer true.
Fwiw,
for those who care about exotic archs, alpha has lots of failures
because (among others) we dont build libGL/libGLU there anymore.
other failures are probably toolchain segfaults.
Landry
- Forwarded message from Landry Breuil
-
bulk build on alpha-1.ports.openbsd.org
started on
On Mon, Feb 08, 2016 at 02:53:16PM -0600, attila wrote:
>
> Landry Breuil writes:
> > Have you tried leaving the .xpi files compressed in their respective
> > dirs at runtime (eventually unzipping/patching/rezipping) as you comment
> > in Makefile.inc line 68 ? Iirc this should also work and i
attila writes:
> Landry Breuil writes:
>
>> On Mon, Nov 16, 2015 at 09:07:46AM -0600, attila wrote:
>>>
>>> attila writes:
>>>
>>> > attila writes:
>>> >
>>> >> attila writes:
>>> >>
>>> >>> attila writes:
>>> >>>
>>> attila writes:
>>>
>>> > Hi ports@,
>>> >
>>> >
Landry Breuil writes:
> On Mon, Nov 16, 2015 at 09:07:46AM -0600, attila wrote:
>>
>> attila writes:
>>
>> > attila writes:
>> >
>> >> attila writes:
>> >>
>> >>> attila writes:
>> >>>
>> attila writes:
>>
>> > Hi ports@,
>> >
>> > I have been informed that my previo
On Mon, 8 Feb 2016 18:09:06 + Stuart Henderson wrote:
> On 2016/02/08 12:44, dan mclaughlin wrote:
> > i am assuming that the distfiles on the cdrom preserve the same structure
> > as on the ftp sites and also created during builds.
>
> This won't have been noticed because there are no distfi
On 2016/02/08 12:44, dan mclaughlin wrote:
> i am assuming that the distfiles on the cdrom preserve the same structure
> as on the ftp sites and also created during builds.
This won't have been noticed because there are no distfiles on the
cdrom, PERMIT_DISTFILES_CDROM is no longer permitted in a
i am assuming that the distfiles on the cdrom preserve the same structure
as on the ftp sites and also created during builds.
to illustrate:
$ env CDROM_SITE=/home/olddistfiles DISTDIR=/home/distfiles make fetch
===> Checking files for bash-4.3.42
cp: /home/olddistfiles/bash-4.3.30.tar.gz: No su
On Mon, Feb 08, 2016 at 08:11:22AM +0100, viq wrote:
> Bump
Hrrmmm, the mail I sent about this last week never made it to the list.
I would prefer to commit this fix.
Ok?
Index: Makefile
===
RCS file: /work/cvsroot/ports/productivit
tro...@kagu-tsuchi.com writes:
> Seems that with the change to duplicity 0.7, the default sftp backend changed.
> The manpage was being patched to say the default was pexpect over paramiko.
> This is no longer true. Remove the manpage changes.
Was there a rationale for changing the default again
On 2016-02-07, Landry Breuil wrote:
> A quick look at the 'list of bugs fixed in this release' (link at the
> bottom of the page) yields to some fontconfig-related bugs like
> https://bugzilla.mozilla.org/show_bug.cgi?id=1180560
Yes, that's it.
Switching gfx.font_rendering.fontconfig.fontlist.en
On Mon, 8 Feb 2016, Christoph R. Murauer wrote:
> > You'll learn soon that sending patches as attachments is a wonderful
> > way to get people angry.
>
> Sorry, was not my intention. I saw often attachments so, I thought it
> is the prefered way. I also like inline things more.
>
> > These lines
On Sun, Feb 07, 2016 at 06:06:48PM -0500, Jiri B wrote:
> We need to explicitly disable pulling of wireshark inside libvirt port
> or if not, libvirt port should has subpackage (as Fedora[1] does) for
> wireshark dissector plugin (IMO not much used on OpenBSD).
>
> j.
Thanks, I'll handle it. The d
19 matches
Mail list logo
