reebsd.org/build.html?mastername=main-amd64-default&build=p569609_s5b3b19db73
> >> (ipv6 only)
> >>
> >> NB: I'm not involved in the pkg building cluster.
> >>
> >> Regards,
> >> Ronald.
> >>
> >>
> >> Van: "
m: vrijdag, 9 april 2021 07:27
Aan: FreeBSD Ports
Onderwerp: Re: poudriere: net/openldap24-server: stage/runaway , building
forever
On Fri, 9 Apr 2021 06:17:03 +0200
"Hartmann, O." wrote:
> Recent CURRENT host (FreeBSD 14.0-CURRENT #26 main-n245806-4d221f59b85: Sat
> Apr 3 06:43:44 C
ge
> > >>
> > >> It is stuck in "stage/runaway" for 61 hours now.
> > >> http://beefy18.nyi.freebsd.org/build.html?mastername=main-amd64-default&build=p569609_s5b3b19db73
> > >> (ipv6 only)
> > >>
> > >> NB: I'm not i
Aan: FreeBSD Ports
Onderwerp: Re: poudriere: net/openldap24-server: stage/runaway , building
forever
On Fri, 9 Apr 2021 06:17:03 +0200
"Hartmann, O." wrote:
Recent CURRENT host (FreeBSD 14.0-CURRENT #26 main-n245806-4d221f59b85:
Sat Apr 3 06:43:44 CEST 2021 amd64), poudriere CUR
n "stage/runaway" for 61 hours now.
> http://beefy18.nyi.freebsd.org/build.html?mastername=main-amd64-default&build=p569609_s5b3b19db73
> (ipv6 only)
>
> NB: I'm not involved in the pkg building cluster.
>
> Regards,
> Ronald.
>
>
> Van: "O. Hartman
main-amd64-default&build=p569609_s5b3b19db73
(ipv6 only)
NB: I'm not involved in the pkg building cluster.
Regards,
Ronald.
Van: "O. Hartmann"
Datum: vrijdag, 9 april 2021 07:27
Aan: FreeBSD Ports
Onderwerp: Re: poudriere: net/openldap24-server: stage/runaway , building
fo
On Fri, 9 Apr 2021 06:17:03 +0200
"Hartmann, O." wrote:
> Recent CURRENT host (FreeBSD 14.0-CURRENT #26 main-n245806-4d221f59b85: Sat
> Apr 3 06:43:44 CEST 2021 amd64), poudriere CURRENT jail at 14.0-CURRENT
> 147 amd64 from 2021-04-08 05:25:38. It seems that the recent CURRENT does
> have a
Tatsuki Makino wrote:
> -U default value can be changed in ${LOCALBASE}/etc/poudriere.conf, cannot it?
> The default value is defined in common.sh.
>
> GIT_PORTSURL="git.FreeBSD.org/ports.git"
> And
> poudriere ports -c -m git+https -B main
>
Yes, you can put GIT_PORTSURL into poudriere.conf and
Guido Falsi via freebsd-ports wrote on 2021/04/06 06:37:
> poudriere ports -c -B main -m git -U 'https://git.FreeBSD.org/ports.git' -p
> freebsd
>
-U default value can be changed in ${LOCALBASE}/etc/poudriere.conf, cannot it?
The default value is defined in common.sh.
GIT_PORTSURL="git.FreeBSD.
On 05/04/21 23:26, Jose Quinteiro wrote:
On 4/4/21 7:35 AM, Carmel wrote:
On Sat, 3 Apr 2021 12:18:27 +, Rene Ladan stated:
...
Is or will poudriere default to using net/gitup in FreeBSD 13? Is there
a way to configure it in the "poudriere.conf" file?
There's a "git" option for the "-m me
On 4/4/21 7:35 AM, Carmel wrote:
> On Sat, 3 Apr 2021 12:18:27 +, Rene Ladan stated:
> ...
> Is or will poudriere default to using net/gitup in FreeBSD 13? Is there
> a way to configure it in the "poudriere.conf" file?
>
There's a "git" option for the "-m method" command-line switch of
poudri
On Sun, Apr 04, 2021 at 10:35:25AM -0400, Carmel wrote:
> On Sat, 3 Apr 2021 12:18:27 +, Rene Ladan stated:
> >On Sat, Apr 03, 2021 at 07:43:49AM -0400, Carmel wrote:
> >> I am using "poudriere-devel", version 3.3.99.20210303_1 on a FreeBSD
> >> 11.4-RELEASE-p8 amd64 machine. I was told that po
On Sat, 3 Apr 2021 12:18:27 +, Rene Ladan stated:
>On Sat, Apr 03, 2021 at 07:43:49AM -0400, Carmel wrote:
>> I am using "poudriere-devel", version 3.3.99.20210303_1 on a FreeBSD
>> 11.4-RELEASE-p8 amd64 machine. I was told that poudriere uses
>> 'portsnap' by default. What, do I have to do if
On Sat, Apr 03, 2021 at 07:43:49AM -0400, Carmel wrote:
> I am using "poudriere-devel", version 3.3.99.20210303_1 on a FreeBSD
> 11.4-RELEASE-p8 amd64 machine. I was told that poudriere uses
> 'portsnap' by default. What, do I have to do if I want it to defer to
> "gitup" {devel/py-git-up} instead?
gitup is not yet an option for creating the ports tree in poudriere:
$ zfs snapshot zroot/poudriere/ports/default@svn
$ zfs send zroot/poudriere/ports/default@svn | zfs recv
zroot/poudriere/ports/svn
$ poudriere ports -d
$ poudriere ports -c -U https://git.freebsd.org/ports.git -m git -B main
Th
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.
[...]
On Tue, Oct 6, 2020 at 2:30 PM Rainer Hurling wrote:
>
> On 02.10.20 11:19, Rainer Hurling wrote:
> > For some time now, I get the following error when trying to create or
> > update 11.4 or 12.2 jails in Poudriere:
> >
> >
> > #poudriere jail -c -j F114i386 -v stable/11 -a i386 -m svn+https
> >
>
On 02.10.20 11:19, Rainer Hurling wrote:
> For some time now, I get the following error when trying to create or
> update 11.4 or 12.2 jails in Poudriere:
>
>
> #poudriere jail -c -j F114i386 -v stable/11 -a i386 -m svn+https
>
> [..snip..]
> --- all_subdir_rescue ---
> --- /poudriere/jails/F114
On Tue, Oct 06, 2020 at 06:20:05PM +0900, Yasuhiro KIMURA wrote:
> This is because base system implicitly assumes PREFIX=/usr/local.
Evidently part of my issue is confused over PREFIX vs LOCALBASE. The most
detailed thing I found was here:
https://www.freebsd.org/doc/en/books/porters-handboo
On Mon, Oct 05, 2020 at 11:30:36PM -0400, Mason Loring Bliss wrote:
> Hi, all. I just spun up a Poudriere build server, building 2020Q4 for 12.1
> amd64. I set PREFIX=/opt in /usr/local/etc/poudriere.d/make.conf and a
> number of things broke, but a number didn't. When I killed the build, as
> clea
From: Mason Loring Bliss
Subject: Poudriere/PREFIX breakage?
Date: Mon, 5 Oct 2020 23:30:36 -0400
> Hi, all. I just spun up a Poudriere build server, building 2020Q4 for 12.1
> amd64. I set PREFIX=/opt in /usr/local/etc/poudriere.d/make.conf and a
> number of things broke, but a number didn't. Wh
On Sun, May 24, 2020 at 04:31:42PM +0200, Jan Beich wrote:
> ...
> According to the full log the reason is "(signal: 9, SIGKILL: kill)" and
> the signal was sent to multiple processes. The kernel usually sends
> SIGKILL on out-of-memory conditions.
Oh! OK; thank you: I had failed to see that.
I'
David Wolfskill writes:
> It appears (to my eye that is quite unfamiliar with rust) that the first
> failure in the log is:
>
> sysroot:
> "/wrkdirs/usr/ports/lang/rust/work/rustc-1.43.1-src/build/x86_64-unknown-freebsd/stage1"
> libdir:
> "/wrkdirs/usr/ports/lang/rust/work/rustc-1.43.1-src/bui
On Sat, May 23, 2020 at 03:56:09PM -0700, David Wolfskill wrote:
> ...
> load: 8.59 cmd: sh 99503 [piperd] 35609.83r 1.23u 1.88s 0% 2156k
> [12amd64-ports-home] [2020-05-23_12h08m48s] [parallel_build:] Queued: 1003
> Built: 999 Failed: 1Skipped: 2Ignored: 0Tobuild: 1 Time:
> 09:
Grzegorz Junka wrote:
On 20/05/2020 19:33, Yuri Pankov wrote:
Grzegorz Junka wrote:
When configuring ports with this option:
poudriere options -j 13 -p gui -z v8 lang/v8
for every port the configuration ends with "Segmentation fault". For
example, with that command the first port that shows
On 20/05/2020 19:33, Yuri Pankov wrote:
Grzegorz Junka wrote:
When configuring ports with this option:
poudriere options -j 13 -p gui -z v8 lang/v8
for every port the configuration ends with "Segmentation fault". For
example, with that command the first port that shows up is
"python27-2.7.
Grzegorz Junka wrote:
When configuring ports with this option:
poudriere options -j 13 -p gui -z v8 lang/v8
for every port the configuration ends with "Segmentation fault". For
example, with that command the first port that shows up is
"python27-2.7.18". After the ncurses dialog is shown I cl
On 2020-05-15 19:36, Bryan Drewery wrote:
===> Patching for python27-2.7.18
xargs: illegal option -- e
usage: xargs [-0opt] [-E eofstr] [-I replstr [-R replacements] [-S
replsize]]
[-J replstr] [-L number] [-n number [-x]] [-P maxprocs]
[-s size] [utility [argument .
On 5/15/2020 6:21 AM, Miroslav Lachman wrote:
> I am trying to use port overlays with poudriere-devel.
> I have main tree with old quaterly branch from December 2019 (default).
> The overlay contains just a bunch of ports from current tree with
> updated versions of Apache, Python etc. and Mk from
On 2020-May-11, at 11:34, Patrick M. Hausen wrote:
> I’m confused by this thread. isn’t the point of Poudriere
> bulk builds to
When I listed:
# poudriere jail -l
JAILNAME VERSION ARCH METHOD TIMESTAMP PATH
FBSDFSSDjail 13.0-CURRENT amd64 nu
Hi all,
I’m confused by this thread. isn’t the point of Poudriere
bulk builds to
- start with a clean jail
- build the first port in the list and all dependencies
- store the packages for later incorporation into the pkg repo
- clean out the jail completely
- start with the next port in the list
Leander Schaefer info at NetOcean.de wrote on
Tue May 5 20:38:49 UTC 2020 :
> I have been dealing with Poudriere for quite a while and one of the most
> issues I have is, that I have ports which won't compile along with
> another. Reason is mostly something like:
>
> pkg-static: ImageMagick7-7.
On Thu, May 07, 2020 at 08:39:41PM +0200, Leander Schaefer wrote:
> Hello Chris,
>
> Hello List,
>
> I have checked out ports-mgmt/synth unfortunately it would be a massive
> downgrade compared to poudriere. Does anyone have the right clue about how
> the FreeBSD package managment team provides a
On Thu, 7 May 2020 20:39:41 +0200 Leander Schaefer i...@netocean.de said
Hello Chris,
Hello List,
I have checked out ports-mgmt/synth unfortunately it would be a massive
downgrade compared to poudriere. Does anyone have the right clue about
how the FreeBSD package managment team provides a c
## Leander Schaefer (i...@netocean.de):
> Does anyone have the right clue about
> how the FreeBSD package managment team provides a complete repository
> without having these conflicts? There must be a way to do this with
> poudriere since I am most certainly sure they also use poudriere.
The
Hello Chris,
Hello List,
I have checked out ports-mgmt/synth unfortunately it would be a massive
downgrade compared to poudriere. Does anyone have the right clue about
how the FreeBSD package managment team provides a complete repository
without having these conflicts? There must be a way to
Hello Chris,
thanks for your reply. Thanks for the hint about ports-mgmt/synth. I am
definitly going to have a look into this! Well, my Podriere is using
Jails by default. Is there any hack you applied for this issue to avoid?
Best regards,
Leander
Am 05.05.20 um 22:46 schrieb Chris:
On
On Tue, 5 May 2020 22:38:36 +0200 Leander Schaefer i...@netocean.de said
Hello,
I have been dealing with Poudriere for quite a while and one of the most
issues I have is, that I have ports which won't compile along with
another. Reason is mostly something like:
pkg-static: ImageMagick7-7.0.
Jose Quinteiro wrote:
> It packages all its dependencies, though. This is a little
> disconcerting. It's also possible I'm doing something wrong.
>
Use `bulk -t` to test and package the port; refer to poudriere-bulk(8)
for details.
--
Charlie Li
…nope, still don't have an exit line.
(This email
Both 'testport' and 'bulk' package the port, but 'testport' discards
it and 'bulk' saves it.
In testport, the port is built with WITH_DEBUG enabled (among others).
That's not the build that should be saved.
# Adam
On Sat, Apr 18, 2020 at 1:50 PM Jose Quinteiro wrote:
>
> It packages all its de
On Fri, Apr 17, 2020 at 10:54 AM Brooks Davis wrote:
>
> On Fri, Apr 17, 2020 at 09:42:51AM -0700, Jose Quinteiro wrote:
> > Hello,
> >
> > The Handbook says:
> > "The system make.conf and this new file are combined at build time to
> > create the make.conf used by the build jail."
> > https://www
On Fri, Apr 17, 2020 at 09:42:51AM -0700, Jose Quinteiro wrote:
> Hello,
>
> The Handbook says:
> "The system make.conf and this new file are combined at build time to
> create the make.conf used by the build jail."
> https://www.freebsd.org/doc/handbook/ports-poudriere.html
>
> The poudriere man
Miroslav Lachman writes:
> [...]
> Any possibility that you have some kind of automatic snapshoting utility
> run from crontab recursively on filesystem where poudriere have builder
> jails mounted?
>
> I saw this error when I setup zfsnap in crontab with resursive snapshot
> of /vol0 (e
George Hartzell wrote on 2020/03/20 18:13:
I have a FreeBSD 12.1p3 (just updated) root-on-zfs system that's
having trouble doing Poudriere builds.
It started off life as a FreeBSD 12.1 system and has been building
it's own set of packages using Poudriere successfully since its
inception.
I few
> Am 28.02.2020 um 01:22 schrieb Tatsuki Makino :
>
> Your poudriere.conf is written as PARALLEL_JOBS=4.
> Combining this with writing MAKE_JOBS_NUMBER:=4 in
> /usr/local/etc/poudriere.d/*make.conf, load average reaches 16.
> If you are concerned about that load average reaching 16, you need to
Your poudriere.conf is written as PARALLEL_JOBS=4.
Combining this with writing MAKE_JOBS_NUMBER:=4 in
/usr/local/etc/poudriere.d/*make.conf, load average reaches 16.
If you are concerned about that load average reaching 16, you need to
adjust PARALLEL_JOBS and MAKE_JOBS_NUMBER.
If it only rise up t
> Am 27.02.2020 um 00:09 schrieb Tatsuki Makino :
>
> .MAKE.JOBS=4
This was the only way to force a
-j 4
to make.
>
> If you want to limit the number of parallel jobs to 4, write:
>
> MAKE_JOBS_NUMBER:=4
This has no effect here, if combined with
ALLOW_MAKE_JOBS=yes
in poudrier
> Am 27.02.2020 um 00:09 schrieb Tatsuki Makino :
>
>
> The cause of this trouble is the following part of make.conf.
>
> .MAKE.JOBS=4
YEP, that’s it.
Surprisingly this worked for days (weeks?) until pkg received an update. (-;
Thank you for your great work,
Axel
---
PGP-Key: CDE74120 ☀ com
I have finally made the poudriere the same as yours.
The cause of this trouble is the following part of make.conf.
.MAKE.JOBS=4
If you want to limit the number of parallel jobs to 4, write:
MAKE_JOBS_NUMBER:=4
___
freebsd-ports@freebsd.org mailing li
> Am 26.02.2020 um 00:18 schrieb Tatsuki Makino :
>
> TMPFS_LIMIT=4 -> 6
> MAX_MEMORY=2 -> 4
> MAX_FILES=1024 -> 2048
> PARALLEL_JOBS=4 -> 2
> PREPARE_PARALLEL_JOBS=5
Trying it. The result looks so:
———
root@db3:~ # poudriere testport -vv -j 120amd64 ports-mgmt/pkg
=>> Debug: Reading /usr/local
Your poudriere.conf has resource limits.
Would you try removing the resource limit and reducing the number of
parallels?
e.g.
TMPFS_LIMIT=4 -> 6
MAX_MEMORY=2 -> 4
MAX_FILES=1024 -> 2048
PARALLEL_JOBS=4 -> 2
PREPARE_PARALLEL_JOBS=5
___
freebsd-ports@free
> Am 25.02.2020 um 18:43 schrieb Axel Rau :
>
>
> I attach my poudriere.conf and portshaker.conf (which worked for years).
https://www.chaos1.de/downloads/pp.tar.gz
Axel
---
PGP-Key: CDE74120 ☀ computing @ chaos claudius
signature.asc
Description: Message signed with OpenPGP
> Am 25.02.2020 um 09:27 schrieb Axel Rau :
>
>
> Question: How do I reset the poudriere environment to let it start over and
> bootstrap a new pkg?
> Is cleaning data enough (as ports tree is maintained by portshaker here)?
I cleaned jails and ports and re-created them. (created an empty
${
> Am 25.02.2020 um 09:27 schrieb Axel Rau :
>
> Question: How do I reset the poudriere environment to let it start over and
> bootstrap a new pkg?
> Is cleaning data enough (as ports tree is maintained by portshaker here)?
Even after removing poudriere data tree and recreating poudriere jails an
> Am 24.02.2020 um 23:48 schrieb Tatsuki Makino :
>
> Is there a mistake in any of /usr/local/etc/poudriere.d/*make.conf ?
Nothing changed recently:
———
#?# WITH_SSP_PORTS (bool) If set, enables -fstack-protector for most
ports.
#
CC=clang # Highly recommended over GCC,
CXX
Is there a mistake in any of /usr/local/etc/poudriere.d/*make.conf ?
___
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"
Thanks for your answer!
> Am 24.02.2020 um 00:00 schrieb Tatsuki Makino :
>
> For example, re-extracting ports tree.
>
>> portsnap -d "`cat /usr/local/etc/poudriere.d/ports/default/mnt`/.snap"
> -p "`cat /usr/local/etc/poudriere.d/ports/default/mnt`“ extract
I’m using portshaker, so I did:
por
For example, re-extracting ports tree.
> portsnap -d "`cat /usr/local/etc/poudriere.d/ports/default/mnt`/.snap"
-p "`cat /usr/local/etc/poudriere.d/ports/default/mnt`" extract
For example, to revert ports tree.
svnlite revert -R "`cat /usr/local/etc/poudriere.d/ports/default/mnt`"
_
> Am 22.02.2020 um 10:58 schrieb Axel Rau :
>
> How to fix this situation?
After cleaning distfile cache and putting the previous version
pkg-1.13.1.txz
into
${POUDRIERE_DATA}/packages/120amd64-default/.real_1582359892/All
I’m still getting:
. . .
=>> Status ports-mgmt/pkg |
On 2019-10-25 15:32, Miroslav Lachman wrote:
>...
As I understand it should be possible to have default ports tree
synchronised by SVN or Git with official tree and the second tree with
private ports only, called for example "myports" (/usr/myports)
Then in make.conf define OVERLAYS= /usr/mypor
Andrea Venturoli wrote on 2019/10/25 11:54:
On 2019-10-25 11:35, Miroslav Lachman wrote:
I would like to try Overlay support in ports tree (announced few weeks
ago in 2019Q4 branch).
The question is will it work with Poudriere or not? We are building
all our packages with poudriere.
I tried a
On 2019-10-25 11:35, Miroslav Lachman wrote:
I would like to try Overlay support in ports tree (announced few weeks
ago in 2019Q4 branch).
The question is will it work with Poudriere or not? We are building all
our packages with poudriere.
I tried adding OVERLAYS= /vol0/poudriere/ports/myports
On 21/10/2019 14:59, John Kennedy wrote:
On Mon, Oct 21, 2019 at 01:59:17PM +0100, Matthew Seaman wrote:
On 21/10/2019 13:31, Sergei Vyshenski wrote:
Is it possible to instruct "poudriere testport" such
that it downloads depends (in a form of binary packages) from the
central repository,
and ac
On Mon, Oct 21, 2019 at 01:59:17PM +0100, Matthew Seaman wrote:
> On 21/10/2019 13:31, Sergei Vyshenski wrote:
> > Is it possible to instruct "poudriere testport" such
> > that it downloads depends (in a form of binary packages) from the
> > central repository,
> > and actually tests only the port
Sergei Vyshenski writes:
> Hi,
>
> Is it possible to instruct "poudriere testport" such
> that it downloads depends (in a form of binary packages) from the
> central repository,
> and actually tests only the port in question?
See also https://github.com/freebsd/poudriere/issues/319
_
On 21/10/2019 13:31, Sergei Vyshenski wrote:
Is it possible to instruct "poudriere testport" such
that it downloads depends (in a form of binary packages) from the
central repository,
and actually tests only the port in question?
Currently, no this is not available. Using another repo to see
On Tue, Apr 30, 2019 at 04:21:52PM +0200, Philippe Maechler wrote:
> Hello Mathieu
>
>
>
> >On Tue, Apr 30, 2019 at 02:23:31PM +0200, Mathieu Arnold wrote:
>
>
>
> >> It seems that devel/pecl-pthreads's Makefile has not been updated in the
>
> >> last 6 years to account for how packages
Hello Mathieu
>On Tue, Apr 30, 2019 at 02:23:31PM +0200, Mathieu Arnold wrote:
>> It seems that devel/pecl-pthreads's Makefile has not been updated in the
>> last 6 years to account for how packages are built. I'll try to fiddle
>> with it.
Thank you very much for your efforts!
Hi again,
On Tue, Apr 30, 2019 at 02:23:31PM +0200, Mathieu Arnold wrote:
> Hi,
>
> On Tue, Apr 30, 2019 at 10:17:07AM +0200, Philippe Maechler wrote:
> > Hello freebsd-ports, it's me again
> >
> >
> >
> > Once more I have troubles building ports on FreeBSD 11.2 and 12.0. The last
> > time I
Hi,
On Tue, Apr 30, 2019 at 10:17:07AM +0200, Philippe Maechler wrote:
> Hello freebsd-ports, it's me again
>
>
>
> Once more I have troubles building ports on FreeBSD 11.2 and 12.0. The last
> time I could build those "problemativ" ports in my poudriere installation
> and used the package fro
On 27/02/2019 12:51, Mark Martinec wrote:
> Now that poudriere has been upgraded from 3.2.8 to 3.3.0,
> when I press ^T during interactive bulk build, I see:
>
> sed: 1: "s,^\[( *[0-9]+%|[0-9]+/ ...": RE error: repetition-operator
> operand invalid
>
> with many (but not all) build jobs. For ex
Hi!
> > > I have found the real cause of most of the problems: it's ccache
> > > configuration.
> >
> > Thanks for the update. I've never used ccache, but I've changed my
> > setup to test this 8-}
>
> I've been bitten by this in the past with that exact scenario, except
> it also slowed the amd
On Tue, Jan 1, 2019 at 11:22 AM Kurt Jaeger wrote:
>
> Hi!
>
> > I have found the real cause of most of the problems: it's ccache
> > configuration.
>
> Thanks for the update. I've never used ccache, but I've changed my
> setup to test this 8-}
I've been bitten by this in the past with that exac
Hi!
> I have found the real cause of most of the problems: it's ccache
> configuration.
Thanks for the update. I've never used ccache, but I've changed my
setup to test this 8-}
--
p...@freebsd.org +49 171 3101372 One year to go !
___
> > Hi!
> >
> > > > SSD or spinning drives ?
> > > >
> > > > > I have 3.6 Gb of RAM and 2 Gb of swap.
> > > >
> > > > Run top and check the state of ARC.
> > > > I think it needs much more RAM.
> > >
> > > I don't think it is a SSD (it has cylinders, sectors etc.).
> > > If you can tell me a way to
> Hi!
>
> > > SSD or spinning drives ?
> > >
> > > > I have 3.6 Gb of RAM and 2 Gb of swap.
> > >
> > > Run top and check the state of ARC.
> > > I think it needs much more RAM.
> >
> > I don't think it is a SSD (it has cylinders, sectors etc.).
> > If you can tell me a way to check it I will be gl
Hi!
> > SSD or spinning drives ?
> >
> > > I have 3.6 Gb of RAM and 2 Gb of swap.
> >
> > Run top and check the state of ARC.
> >
> > I think it needs much more RAM.
>
> I don't think it is a SSD (it has cylinders, sectors etc.).
> If you can tell me a way to check it I will be glad to do it.
> T
> Hi!
>
> > > > Am I the only poudriere user that notices very long build times on an
> > > > amd64 machine in i386 jails? This does not happen always, but
> > > > frequently enough to be a nuisance.
> > >
> > > Can you say more about the rest of the setup ?
> > > Filesystem type ? Type of storag
Hi!
> > > Am I the only poudriere user that notices very long build times on an
> > > amd64 machine in i386 jails? This does not happen always, but frequently
> > > enough to be a nuisance.
> >
> > Can you say more about the rest of the setup ?
> >
> > Filesystem type ? Type of storage ? Memory
> On 31.12.18 21:03, Lorenzo Salvadore via freebsd-ports wrote:
>
> > > Hi!
> > >
> > > > Am I the only poudriere user that notices very long build times on an
> > > > amd64 machine in i386 jails? This does not happen always, but
> > > > frequently enough to be a nuisance.
> > > > Can you say m
On 31.12.18 21:03, Lorenzo Salvadore via freebsd-ports wrote:
Hi!
Am I the only poudriere user that notices very long build times on an amd64
machine in i386 jails? This does not happen always, but frequently enough to be
a nuisance.
Can you say more about the rest of the setup ?
Filesyst
> Hi!
>
> > Am I the only poudriere user that notices very long build times on an amd64
> > machine in i386 jails? This does not happen always, but frequently enough
> > to be a nuisance.
>
> Can you say more about the rest of the setup ?
>
> Filesystem type ? Type of storage ? Memory size ? Base
1 - 100 of 487 matches
Mail list logo
