Greetings,
this patch had a few errors that are fixed with this patch, checking for
NOT_MOVED and dont produce an error if its not there and also dont
delete packages that are in NOT_MOVED to build them again.
This Patch targets poudriere-devel 3.3.99.20200326_2
--- common.sh.1st 2021-
Tatsuki Makino wrote on 2021/01/29 08:28:
> If I were to use OVERLAYS, where should I place the ovarlay tree?
>
> When poudriere starts a jail, it will cpio all its files.
> Ports tree will be mounted readonly by nullfs.
> In order to access the overlay tree from the poudriere jails, it seems that
Greetings,
i created a simple patch for this, this may not be the best solution but
my tests seems to be successful to get the desired result:
Without NOT_MOVED:
=>> Debug: Reading /usr/local/etc/poudriere.conf
[00:00:00] Creating the reference jail... done
[00:00:02] Mounting system devices
If I were to use OVERLAYS, where should I place the ovarlay tree?
When poudriere starts a jail, it will cpio all its files.
Ports tree will be mounted readonly by nullfs.
In order to access the overlay tree from the poudriere jails, it seems that we
need to put files under them.
Am 28.01.21 um 21:14 schrieb Miroslav Lachman:
On 28/01/2021 17:47, Henrik Rosenke wrote:
I tried this with a patched MOVED file, copied from the master
portstree, deleted the entry and tried to build but this File seems
to be ignored. I dont really understand where the MOVED file is
handled
On 28/01/2021 17:47, Henrik Rosenke wrote:
I tried this with a patched MOVED file, copied from the master
portstree, deleted the entry and tried to build but this File seems to
be ignored. I dont really understand where the MOVED file is handled, it
seems to be bsd.port.subdir.mk but i am not s
I tried this with a patched MOVED file, copied from the master
portstree, deleted the entry and tried to build but this File seems to
be ignored. I dont really understand where the MOVED file is handled, it
seems to be bsd.port.subdir.mk but i am not sure. I think the best way
to handle this wo
On 28/01/2021 10:55, Henrik Rosenke wrote:
Greetings,
UIDs and GIDs are also not resprected, i could solve this via this patch:
I didn't tried it but what if you have patched Mk/bsd.port.mk and MOVED
in overlay tree? Does it work or not?
Miroslav Lachman
Greetings,
UIDs and GIDs are also not resprected, i could solve this via this patch:
Index: Mk/bsd.port.mk
===
--- Mk/bsd.port.mk (Revision 563120)
+++ Mk/bsd.port.mk (Arbeitskopie)
@@ -1274,8 +1274,17 @@
# where 'make co
Greetings,
i just added the overlay to my portstree, works good and great addition.
I wonder how you handle moved ports with this? As example we are using a
adapted Version of sysutils/sge62 with own patches but i need to remove
this Line in MOVED on the Original portstree to allow building it
Hello.
I am also using poudriere to debug a port that is maintained by me.
At that time, there is a file that I want to output to the port tree and
collect.
In doing so, cover the other directories as follows. They were brought from my
~/.history :)
(src-svn is poudriere's option -j src -p svn)
On Mon, Jan 25, 2021 at 04:25:09PM +0100, Miroslav Lachman wrote:
> On 25/01/2021 15:10, Baptiste Daroussin wrote:
> > On Sun, Jan 24, 2021 at 10:23:45PM +0100, Guido Falsi via freebsd-ports
> > wrote:
> > > On 24/01/21 20:35, Russell L. Carter wrote:
> > > > Greetings,
> > > > I am completely ign
On 25/01/2021 15:10, Baptiste Daroussin wrote:
On Sun, Jan 24, 2021 at 10:23:45PM +0100, Guido Falsi via freebsd-ports wrote:
On 24/01/21 20:35, Russell L. Carter wrote:
Greetings,
I am completely ignorant here and am looking for up to
date advice on how to get poudriere to build and make
avail
On Sun, Jan 24, 2021 at 10:23:45PM +0100, Guido Falsi via freebsd-ports wrote:
> On 24/01/21 20:35, Russell L. Carter wrote:
> > Greetings,
> > I am completely ignorant here and am looking for up to
> > date advice on how to get poudriere to build and make
> > available package sets from multiple p
On 1/25/21 12:19 AM, Guido Falsi wrote:
On 25/01/21 00:24, Russell L. Carter wrote:
On 1/24/21 2:23 PM, Guido Falsi wrote:
On 24/01/21 20:35, Russell L. Carter wrote:
Greetings, I am completely ignorant here and am looking for up to
date advice on how to get poudriere to build and make availab
Am 25.01.2021 um 08:19 schrieb Guido Falsi via freebsd-ports:
There already is a git mirror of the ports tree, so you could also
start doing this now. Only problem is, when the tree is converted you
would probably have a messy time migrating to the new tree, which, I
guess, will have new commit
On 25/01/21 00:24, Russell L. Carter wrote:
On 1/24/21 2:23 PM, Guido Falsi wrote:
On 24/01/21 20:35, Russell L. Carter wrote:
Greetings, I am completely ignorant here and am looking for up to
date advice on how to get poudriere to build and make available
package sets from multiple ports tree
On 1/24/21 2:23 PM, Guido Falsi wrote:
On 24/01/21 20:35, Russell L. Carter wrote:
Greetings, I am completely ignorant here and am looking for up to
date advice on how to get poudriere to build and make available
package sets from multiple ports trees. I see there is a port
"portshaker" that s
On 24/01/21 20:35, Russell L. Carter wrote:
Greetings,
I am completely ignorant here and am looking for up to
date advice on how to get poudriere to build and make
available package sets from multiple ports trees. I
see there is a port "portshaker" that seems to do much
of what I want.
I can th
On 24/01/2021 20:35, Russell L. Carter wrote:
Greetings,
I am completely ignorant here and am looking for up to
date advice on how to get poudriere to build and make
available package sets from multiple ports trees. I
see there is a port "portshaker" that seems to do much
of what I want.
[...]
Greetings,
I am completely ignorant here and am looking for up to
date advice on how to get poudriere to build and make
available package sets from multiple ports trees. I
see there is a port "portshaker" that seems to do much
of what I want.
I can think of possible alternatives:
I can reasonab
21 matches
Mail list logo
