bulk build on arm64.ports.openbsd.org
started on Wed Apr 3 12:55:07 MDT 2019
finished at Sat Apr 6 00:51:52 MDT 2019
lasted 03D04h56m
done with kern.version=OpenBSD 6.5 (GENERIC.MP) #67: Tue Apr 2 23:04:51 MDT
2019
built packages:8466
Apr 3:3086
Apr 4:1319
Apr 5:2932
Apr 6:1128
critical path
On Fri, 5 Apr 2019 15:55:03 +0200
Charlene Wendling wrote:
> Here is a diff that fixes it on amd64, i can't test on macppc
> at the moment as it's building x11/qt4.
sthen@ committed the diff as supertux-0.6.0p1. I built it on amd64.
I believe that it fixes the PREFIX error but not the /usr/obj
On 2019-03-30 20:04, Stuart Henderson wrote:
Ah I didn't check the file contents ... OK - we don't really have a
"how it should be done" as it's not a great fit for the Python setup in
ports. The two options that come to mind:
- just pick one version (preferably py3) and forget about the other
On Thu, Apr 04, 2019 at 02:40:19PM +0200, Raphael Graf wrote:
> The attached diff adds input support to portmidi.
> For each open input device, a thread is started, waiting for input using
> poll(2).
>
> The following program can be used for testing input and ouput:
> /usr/ports/pobj/portmidi-217/
Hi all,
On Thu, 4 Apr 2019 21:40:47 -0400
George Koehler wrote:
> To OpenBSD ports list,
>
> I can't start OpenBSD's amd64 snapshot package of supertux-0.6.0p0.
> Are other people getting the same error? I get
>
> opa$ supertux2
> [FATAL]
> /usr/obj/ports/supertux-0.6.0/SuperTux-v0.6.0-Sourc
On 4/5/19 7:44 AM, Edward Lopez-Acosta wrote:
Is this due to an inefficient process, technical limitation, or other
reason (lack of manpower doesn't qualify as that seems self inflicted
by the project)?
This wording is one of several things that led to accusations of
disrespect. If I said "Ar
On 2019/04/05 06:44, Edward Lopez-Acosta wrote:
> Could you please explain the logic behind this as I am confused. Is this due
> to an inefficient process, technical limitation, or other reason (lack of
> manpower doesn't qualify as that seems self inflicted by the project)?
You seem to disagree a
On Fri, Apr 05, 2019 at 06:44:36AM -0500, Edward Lopez-Acosta wrote:
> Could you please explain the logic behind this as I am confused. Is this due
> to an inefficient process, technical limitation, or other reason (lack of
> manpower doesn't qualify as that seems self inflicted by the project)? Ar
Apr 05, 2019 at 07:20:49AM -0500, Edward Lopez-Acosta wrote:
> Do you have documentation on this process? I would be happy to read it and
> ask questions you feel may be better. As an open source project I am
> surprised about the lack of transparency for various things.
You will find several link
On Fri, Apr 05, 2019 at 06:44:36AM -0500, Edward Lopez-Acosta wrote:
> Could you please explain the logic behind this as I am confused. Is this due
> to an inefficient process, technical limitation, or other reason (lack of
> manpower doesn't qualify as that seems self inflicted by the project)? Ar
>Do you have documentation on this process? I would be happy to read it
>and ask questions you feel may be better. As an open source project I am
>surprised about the lack of transparency for various things.
Such strong words!
>I have opinions yes, but I also try to understand those of others w
Do you have documentation on this process? I would be happy to read it
and ask questions you feel may be better. As an open source project I am
surprised about the lack of transparency for various things.
I have opinions yes, but I also try to understand those of others which
is what prompted
>You are correct its not my process, but I am still curious as to the
>rationale which is just a question that was not answered. Nowhere did I
>suggest, or imply, that it should be changed.
>
>And how do you define crappier releases? If something is stable enough
>that the development team decid
You are correct its not my process, but I am still curious as to the
rationale which is just a question that was not answered. Nowhere did I
suggest, or imply, that it should be changed.
And how do you define crappier releases? If something is stable enough
that the development team decide to
>Could you please explain the logic behind this as I am confused. Is this
>due to an inefficient process, technical limitation, or other reason
>(lack of manpower doesn't qualify as that seems self inflicted by the
>project)? Are you somehow tracking submissions to take care of when this
>unloc
Could you please explain the logic behind this as I am confused. Is this
due to an inefficient process, technical limitation, or other reason
(lack of manpower doesn't qualify as that seems self inflicted by the
project)? Are you somehow tracking submissions to take care of when this
unlocked s
16 matches
Mail list logo
