On 2019-May-24, at 11:25, Mark Linimon wrote:
> On Thu, May 23, 2019 at 10:33:35PM -0700, Mark Millard via freebsd-toolchain
> wrote:
>> That is no matter what the system compiler is for powerpc64.
>>
>> This lead to the below mixing of libstdc++.so.6 and libc++/libcxxrt . . .
>
> Yeah. This
On 2019-05-23, at 12:31 -0700, Mark Millard wrote:
> On 2019-May-23, at 11:47, Jan Beich wrote:
>
> > Mark Millard writes:
> >
> >> Unfortunately poudiere bulk tar archives of failures do not
> >> catch the /tmp/* material from:
> >>
> >> cc: error: unable to execute command: Abort trap (core
On 2019-May-24, at 00:10, Ralf Wenk wrote:
> On 2019-05-23, at 12:31 -0700, Mark Millard wrote:
>> On 2019-May-23, at 11:47, Jan Beich wrote:
>>
>>> Mark Millard writes:
>>>
Unfortunately poudiere bulk tar archives of failures do not
catch the /tmp/* material from:
___
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"
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,
Ralf Wenk writes:
> On 2019-05-23, at 12:31 -0700, Mark Millard wrote:
>
>> On 2019-May-23, at 11:47, Jan Beich wrote:
>>
>> > Mark Millard writes:
>> >
>> >> Unfortunately poudiere bulk tar archives of failures do not
>> >> catch the /tmp/* material from:
>> >>
>> >> cc: error: unable to
Hey,
Is there any policy/document when a bug can be closed? For example, is
it OK to close a bug that is fixed upstream but not yet in ports?
Thanks
GrzegorzJ
___
freebsd-ports@freebsd.org mailing list
On 24.05.19 12:07, Grzegorz Junka wrote:
Hey,
Is there any policy/document when a bug can be closed? For example, is
it OK to close a bug that is fixed upstream but not yet in ports?
Thanks
GrzegorzJ
I don't know of any official policy, but as a user (and port maintainer)
I would prefer an
On 24/05/2019 11:30, Grzegorz Junka wrote:
On 24/05/2019 11:12, Kubilay Kocak wrote:
On 24/05/2019 8:07 pm, Grzegorz Junka wrote:
Hey,
Is there any policy/document when a bug can be closed? For example,
is it OK to close a bug that is fixed upstream but not yet in ports?
Thanks
On 24/05/2019 12:34, Kubilay Kocak wrote:
On 24/05/2019 9:52 pm, Grzegorz Junka wrote:
On 24/05/2019 11:30, Grzegorz Junka wrote:
On 24/05/2019 11:12, Kubilay Kocak wrote:
On 24/05/2019 8:07 pm, Grzegorz Junka wrote:
Hey,
Is there any policy/document when a bug can be closed? For
On 24/05/2019 10:53, Jan Bramkamp wrote:
On 24.05.19 12:07, Grzegorz Junka wrote:
Hey,
Is there any policy/document when a bug can be closed? For example,
is it OK to close a bug that is fixed upstream but not yet in ports?
Thanks
GrzegorzJ
I don't know of any official policy, but as a
On 24/05/2019 10:45 pm, Grzegorz Junka wrote:
On 24/05/2019 12:34, Kubilay Kocak wrote:
On 24/05/2019 9:52 pm, Grzegorz Junka wrote:
On 24/05/2019 11:30, Grzegorz Junka wrote:
On 24/05/2019 11:12, Kubilay Kocak wrote:
On 24/05/2019 8:07 pm, Grzegorz Junka wrote:
Hey,
Is there any
On 24/05/2019 11:12, Kubilay Kocak wrote:
On 24/05/2019 8:07 pm, Grzegorz Junka wrote:
Hey,
Is there any policy/document when a bug can be closed? For example,
is it OK to close a bug that is fixed upstream but not yet in ports?
Thanks
GrzegorzJ
Hi Grzegorz,
Bugs are closed after they
On 24/05/2019 9:30 pm, Grzegorz Junka wrote:
On 24/05/2019 11:12, Kubilay Kocak wrote:
On 24/05/2019 8:07 pm, Grzegorz Junka wrote:
Hey,
Is there any policy/document when a bug can be closed? For example,
is it OK to close a bug that is fixed upstream but not yet in ports?
Thanks
On 24/05/2019 9:52 pm, Grzegorz Junka wrote:
On 24/05/2019 11:30, Grzegorz Junka wrote:
On 24/05/2019 11:12, Kubilay Kocak wrote:
On 24/05/2019 8:07 pm, Grzegorz Junka wrote:
Hey,
Is there any policy/document when a bug can be closed? For example,
is it OK to close a bug that is fixed
On 24/05/2019 8:07 pm, Grzegorz Junka wrote:
Hey,
Is there any policy/document when a bug can be closed? For example, is
it OK to close a bug that is fixed upstream but not yet in ports?
Thanks
GrzegorzJ
Hi Grzegorz,
Bugs are closed after they are "resolved". Resolved means a resolution
On 24/05/2019 12:48, Kubilay Kocak wrote:
On 24/05/2019 10:45 pm, Grzegorz Junka wrote:
On 24/05/2019 12:34, Kubilay Kocak wrote:
On 24/05/2019 9:52 pm, Grzegorz Junka wrote:
On 24/05/2019 11:30, Grzegorz Junka wrote:
On 24/05/2019 11:12, Kubilay Kocak wrote:
On 24/05/2019 8:07 pm,
On 24/05/2019 12:26, Kubilay Kocak wrote:
On 24/05/2019 9:30 pm, Grzegorz Junka wrote:
On 24/05/2019 11:12, Kubilay Kocak wrote:
On 24/05/2019 8:07 pm, Grzegorz Junka wrote:
Hey,
Is there any policy/document when a bug can be closed? For example,
is it OK to close a bug that is fixed
Hi,
net/rtg no longer runs on modern perl. The maintainer made a patch
almost a year ago, but it's been stalled on some flavour stuff.
I've modified the patch to remove the offending flavour bits, but
haven't heard back from the maintainer in almost a month, even tried
poking him out of
19 matches
Mail list logo