Hi,
thanks, verified and seems to work fine, at least on unplug/re-plug.
I added a "logger "logger ATTACH event on $cdev;" to the action too. On
unplug-plug scenario this was logged and all worked fine [1].
On a reboot it did not log it [2], but it actually seems to have
executed, as the dialer g
On 4/10/17 12:56 am, Ian Lepore wrote:
On Wed, 2017-10-04 at 00:18 +0800, Julian Elischer wrote:
Our 10.4 system is using gcc (for now).
when we compile the devel/binutils port, we get a failure with a
bunch
of these errors:
`_ZTSN12_GLOBAL__N_110Stub_tableILi64ELb1EEE' referenced in section
On Wed, 2017-10-04 at 00:18 +0800, Julian Elischer wrote:
> Our 10.4 system is using gcc (for now).
>
> when we compile the devel/binutils port, we get a failure with a
> bunch
> of these errors:
>
>
> `_ZTSN12_GLOBAL__N_110Stub_tableILi64ELb1EEE' referenced in section
> `.rodata' of aarch64.o
On Tue, Oct 03, 2017 at 01:29:23AM +0800, Julian Elischer wrote:
> can we just find out who runs the poudriere instances and
> ask them to just append the svn revision number somewhere?
> or maybe even the poudriere commands used..
http://www.freebsd.org/portmgr/ ; port...@freebsd.org
Specifical
On 29 Sep 2017, at 15:21, Marco Beishuizen wrote:
> On Fri, 29 Sep 2017, the wise Thomas Mueller wrote:
>
>> What is the current status of portupgrade and portmaster?
>>
>> I haven't used portupgrade in some time, but what about portmaster?
>
> Using portupgrade every day and still works great. Tr
Our 10.4 system is using gcc (for now).
when we compile the devel/binutils port, we get a failure with a bunch
of these errors:
`_ZTSN12_GLOBAL__N_110Stub_tableILi64ELb1EEE' referenced in section
`.rodata' of aarch64.o: defined in discarded section
`.rodata._ZTSN12_GLOBAL__N_110Stub_tableIL
On 03/10/2017 12:08, Kurt Jaeger wrote:
> Hi!
>
>> When using "poudriere", it seems ABI is freebsd:12:x86:64.
>
> Where do you get that value from ? If I access a repo,
> I access e.g.
>
> https://repo.opsec.eu/${ABI}
>
> and ABI maps to
>
> FreeBSD:12:amd64
>
There's history here. Original
Am Tue, 3 Oct 2017 13:08:53 +0200
Kurt Jaeger schrieb:
> Hi!
>
> > When using "poudriere", it seems ABI is freebsd:12:x86:64.
As I wrote: poudriere repo.
>
> Where do you get that value from ? If I access a repo,
> I access e.g.
>
> https://repo.opsec.eu/${ABI}
>
> and ABI maps to
>
> Fr
Hi!
> When using "poudriere", it seems ABI is freebsd:12:x86:64.
Where do you get that value from ? If I access a repo,
I access e.g.
https://repo.opsec.eu/${ABI}
and ABI maps to
FreeBSD:12:amd64
--
p...@opsec.eu+49 171 3101372 3 years to go !
On Tue, 3 Oct 2017 10:51:24 +0200, "O. Hartmann" wrote:
> When using "poudriere", it seems ABI is freebsd:12:x86:64. When using FreeBSD
> base, it
> seems always to be referred to FreeBSD:12:amd64. What now? All non-BSD world
> uses x86:64,
> FreeBSD is using amd64, but why is this used incon
Kurt Jaeger writes:
> Hi!
>
>> Since a few days my 4GiB desktop is crawling due to swap usage and
>> looking at top, I see FireFox using almost 7GiB of RAM (SIZE column),
>> 2.5 of which are "RES".
>
> Firefox memory usage grows without bounds, depending on the
> websites you visit. I do not cl
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
When using "poudriere", it seems ABI is freebsd:12:x86:64. When using FreeBSD
base, it
seems always to be referred to FreeBSD:12:amd64. What now? All non-BSD world
uses x86:64,
FreeBSD is using amd64, but why is this used inconsistently all over the places?
I run into trouble setting up some pac
Hi!
> Hello Everyone, I wonder what is the procedure to find out whether anyone
> is working on getting Nextcloud 12.03 in freshports..
Look at bugs.freebsd.org and search for nextcloud.
You will find
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222738
and now we wait for maintainer appro
14 matches
Mail list logo
