Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Mar 2023 06:13:39 +0100
From:      void <void@f-m.fm>
To:        freebsd-hackers@freebsd.org
Subject:   Re: poudriere ports -u (was: what's the Correct git update method keeping local changes)
Message-ID:  <ZCUag4mz4PGLjpEn@int21h>
In-Reply-To: <5ee400db-bd3c-ee67-643f-d5f24b187834@gmail.com>
References:  <ZCJct8nsBSABpKOL@int21h> <708822f5-2a2f-35f7-8f79-bf48ff644a22@FreeBSD.org> <ZCL44wGy3j3O3oYS@int21h> <5ee400db-bd3c-ee67-643f-d5f24b187834@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On Wed, Mar 29, 2023 at 11:47:24PM +0100, Graham Perrin wrote:
>On 28/03/2023 15:25, void wrote:
>
>> … I've not looked/found what git subcommand 'poudriere ports -u' maps
>> to, yet. …
>
><https://github.com/freebsd/poudriere/blob/cc14f49acd7852c468bc07ea618cfcac602fedcd/src/share/poudriere/ports.sh#L382-L388>;
>
>So, for example:
>
>/usr/local/bin/git -C /usr/local/poudriere/ports/default pull --rebase -q

Thanks. I'm updating the ports tree with git now then null mounting it 
as it avoids the issues I was having.

Do you know what poudriere is doing when it's at the "inspecting ports 
for changes" phase? It's at that stage where the delay is the longest; most 
recently taking over 10 minutes.
-- 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZCUag4mz4PGLjpEn>