On 8/07/2020 4:52 pm, Dave Horsfall wrote:
> On Wed, 8 Jul 2020, Dewayne Geraghty wrote:
>
>> # cat +MANIFEST | jq -rM '.scripts'
>
> Sorry, but this always pushes one of my buttons. When using "cat file |
> proc"
> what's wrong with "proc < file"?
>
> -- Dave
Almost answered the question. :)
On Wed, Jul 08, 2020 at 04:32:34PM +1000, Dewayne Geraghty wrote:
> Is there a more convenient method to examine a package's scripts than
> unpacking the manifest file and
> # cat +MANIFEST | jq -rM '.scripts'
> ? As I'd like to know what changes will, or have been applied.
pkg info --raw-format
Van: bob prohaska
Datum: woensdag, 8 juli 2020 05:47
Aan: freebsd-ports@freebsd.org
Onderwerp: Gracefully killing and restarting a port build
While compiling www/chromium on a Pi3B it has become clear that the
default -j4 isn't going to work (yes, I know, ya told me).
On the plus side, it
On 8/07/2020 5:23 pm, Baptiste Daroussin wrote:
> On Wed, Jul 08, 2020 at 04:32:34PM +1000, Dewayne Geraghty wrote:
>> Is there a more convenient method to examine a package's scripts than
>> unpacking the manifest file and
>> # cat +MANIFEST | jq -rM '.scripts'
>> ? As I'd like to know what chang
FreeBSD 11.4-RELEASE
With a freshly updated ports tree, when I attempt to run poudriere to
update the installed ports, I am greeted with this warning:
[00:00:21] Ignoring net/qt5-network | qt5-network-5.15.0: is marked as broken:
Qt5 requires Openssl 1.1.1, upgrade to FreeBSD 12.x/13.x or add
D
Moin moin
As you see the Ignore-message, I would say that your make.conf is not
used by poudriere.
mfg Tobias
On Wed, 8 Jul 2020 at 13:10, Carmel NY wrote:
>
> FreeBSD 11.4-RELEASE
>
> With a freshly updated ports tree, when I attempt to run poudriere to
> update the installed ports, I am gree
>On Wed, 8 Jul 2020 at 13:10, Carmel NY wrote:
>>
>> FreeBSD 11.4-RELEASE
>>
>> With a freshly updated ports tree, when I attempt to run poudriere to
>> update the installed ports, I am greeted with this warning:
>>
>> [00:00:21] Ignoring net/qt5-network | qt5-network-5.15.0: is marked
>> as broke
On Wed, Jul 8, 2020 at 4:28 PM Carmel NY wrote:
> >On Wed, 8 Jul 2020 at 13:10, Carmel NY wrote:
> >>
> >> FreeBSD 11.4-RELEASE
> >>
> >> With a freshly updated ports tree, when I attempt to run poudriere to
> >> update the installed ports, I am greeted with this warning:
> >>
> >> [00:00:21] Ig
On Wed, 8 Jul 2020 16:30:52 +0400, Gleb Popov stated:
>On Wed, Jul 8, 2020 at 4:28 PM Carmel NY wrote:
>
>> >On Wed, 8 Jul 2020 at 13:10, Carmel NY
>> >wrote:
>> >>
>> >> FreeBSD 11.4-RELEASE
>> >>
>> >> With a freshly updated ports tree, when I attempt to run
>> >> poudriere to update the inst
## Carmel NY (carmel...@outlook.com):
> The entire build log, what there is of it, is available here:
> https://seibercom.net/logs/qt5-network_build.log
And there's your problem:
: /usr/local/etc/poudriere.d/make.conf
:
: LICENSES_ACCEPTED+= PDFlib
: DEFAULT_VERSIONS=samba=4.11
: DEFAU
On Wed, 8 Jul 2020 15:44:21 +0200, Christoph Moench-Tegeder stated:
>## Carmel NY (carmel...@outlook.com):
>
>> The entire build log, what there is of it, is available here:
>> https://seibercom.net/logs/qt5-network_build.log
>
>And there's your problem:
>: /usr/local/etc/poudriere.d/make.co
On Wed, Jul 08, 2020 at 10:44:03AM +0200, Ronald Klop wrote:
>
>
> Kill the leaf nodes of the process tree. So kill the c++ processes. Or type
> ctrl-c if you have control of the terminal.
In this case I'd lost control of the controlling terminal and didn't
know how to recover it. After kill
In the future, if you can, try using "screen" or "tmux" to run these
large builds in so you don't take the risk of losing the
terminal/console. Or, maybe I'm completely off-base as to how it was
lost to begin with.
On 7/8/20 9:30 AM, bob prohaska wrote:
> On Wed, Jul 08, 2020 at 10:44:03AM +0200,
On Tue, 7 Jul 2020 20:47:03 -0700 bob prohaska f...@www.zefox.net said
While compiling www/chromium on a Pi3B it has become clear that the
default -j4 isn't going to work (yes, I know, ya told me).
On the plus side, it hasn't crashed, despite several days of
continuous swapping with 1-2GB of
On Wed, 8 Jul 2020 08:30:13 -0700 bob prohaska f...@www.zefox.net said
On Wed, Jul 08, 2020 at 10:44:03AM +0200, Ronald Klop wrote:
>
>
> Kill the leaf nodes of the process tree. So kill the c++ processes. Or type
> ctrl-c if you have control of the terminal.
In this case I'd lost control of
On Wed, Jul 08, 2020 at 09:34:53AM -0600, Janky Jay, III wrote:
> In the future, if you can, try using "screen" or "tmux" to run these
> large builds in so you don't take the risk of losing the
> terminal/console. Or, maybe I'm completely off-base as to how it was
> lost to begin with.
>
AIUI, sc
On Wed., Jul. 8, 2020, 2:53 p.m. bob prohaska, wrote:
> On Wed, Jul 08, 2020 at 09:34:53AM -0600, Janky Jay, III wrote:
> > In the future, if you can, try using "screen" or "tmux" to run these
> > large builds in so you don't take the risk of losing the
> > terminal/console. Or, maybe I'm complet
On 2020-07-08 14:53, bob prohaska wrote:
>
> AIUI, screen runs until the session terminates and then stops...
I'm a tmux user now, but I never experienced this behavior when I used
screen. Screen was my go-to workaround for a flaky Internet connection
to the host I was trying to manage. Tmux cert
18 matches
Mail list logo
