Re: Looking for testers for curl - PR 283266

On Fri, 20 Dec 2024 02:35:01 +0100 Daniel Engberg wrote: > On 2024-12-20T02:06:46.000+01:00, Michael Gmelin > wrote: > > >>  On 20. Dec 2024, at 00:18, Daniel Engberg > >>   wrote: > >  > >>   > >>   > >>  O

Re: Looking for testers for curl - PR 283266

On 20. Dec 2024, at 00:18, Daniel Engberg wrote: > >  > On 2024-12-19T23:30:41.000+01:00, Michael Gmelin > wrote: > >> >> >> On 19. Dec 2024, at 22:26, Daniel Engberg >> wrote: >>>  >>> On 2024-12-19T21:33:14.000+01:00, Mich

Re: Looking for testers for curl - PR 283266

On 20. Dec 2024, at 00:18, Daniel Engberg wrote:On 2024-12-19T23:30:41.000+01:00, Michael Gmelin <gre...@freebsd.org> wrote:On 19. Dec 2024, at 22:26, Daniel Engberg <daniel.engberg.li...@pyret.net> wrote:On 2024-12-19T21:33:14.000+01:00, Michael Gmelin <gre...@freebsd.org> wr

Re: Looking for testers for curl - PR 283266

On 19. Dec 2024, at 22:26, Daniel Engberg wrote:On 2024-12-19T21:33:14.000+01:00, Michael Gmelin <gre...@freebsd.org> wrote:On Thu, 19 Dec 2024 20:39:54 +0100Daniel Engberg <daniel.engberg.li...@pyret.net> wrote: Hi, While this should be uneventful if possible please try PR 28326

Re: Looking for testers for curl - PR 283266

i?id=283266 > > Best regards, > > Daniel (diizzy@) > Prior to testing, one question: The bug indicates that the port maintainer was not involved in these changes - is this true and has it been resolved in the meantime? Best Michael -- Michael Gmelin

Re: Help please. USB HID problem (was Re: Nut can't open Mini-Box OPEN-UPS2)

eebsd.org/threads/nut-2-8-0-generic-ups-blazer_usb-cant-claim-usb-device.90744/ Best Michael -- Michael Gmelin

Re: Poudriere 3.4.1 regression: can't run in a jail

> On 27. Apr 2024, at 08:56, Andrea Venturoli wrote: > > Hello. > > First of all, thanks for your work. > > I've got a 14.0/amd64 system where I run Poudriere in a jail, but if I > upgrade it from 3.4.0 to 3.4.1_1 it stops working. > E.g. > >> # poudriere bulk -f /root/133amd64.lst -v -j 1

Re: poudriere(8) short circuits my ability to build packages

> On 4. Apr 2024, at 09:31, Chris wrote: > > I do all of my development in jails. As such I have no use for poudriere(8). > But an attempt to build editors/vscode threw the following: > > The limit imposed by poudriere(8) for the maximum number of files allowed to > be > opened by a jail (de

Re: Proposed ports deprecation and removal policy

> On 16. Mar 2024, at 10:45, void wrote: > > On Sat, 16 Mar 2024, at 08:28, Miroslav Lachman wrote: > >> For vulnerabilities, there is VuXML and pkg audit, not removing >> vulnerable port from the tree. > > I'm talking about *moving* them to a *different* tree, with different > priorities

Re: Proposed ports deprecation and removal policy

> On 14. Mar 2024, at 23:59, Daniel Engberg > wrote: > On 2024-03-14T23:27:53.000+01:00, Tomoaki AOKI > wrote: >> On Thu, 14 Mar 2024 22:17:39 +0100 >> Daniel Engberg wrote: >> >> >>> On 2024-03-14T21:49:46.000+01:00, Michael Gmelin >

Re: Proposed ports deprecation and removal policy

> On 14. Mar 2024, at 21:38, Daniel Engberg > wrote: > > On 2024-03-12T15:15:49.000+01:00, Eugene Grosbein wrote: >> 12.03.2024 3:24, Daniel Engberg пишет: >> >> [skip] >> >> >>> Another possible option would be to add something to the port's matedata >>> that makes pkg aware and easy

Re: Proposed ports deprecation and removal policy

> On 28. Feb 2024, at 20:22, Florian Smeets wrote: > > Dear ports community, > > as the removal of ports is a recurring source of friction and dispute we > would like to add a ports removal and deprecation policy to the porters > handbook. > > We tried to find a sensible middle ground bet

Re: Is the ZPOOL option broken in poudriere?

> On 29. Dec 2023, at 07:24, Yuri wrote: > >  > Hi, > > > > > > I have a valid ZFS pool assigned to the ZPOOL variable. > > poudriere creates these directories in this pool: > > poudriere/ > > poudriere/jails > > > > These directories remain empty. > > > > poudriere works fine, b

Re: Portscout is stuck

> On 17. Jun 2023, at 02:27, Danilo G. Baio wrote: > >  > >> On Fri, Jun 16, 2023, at 17:55, Yuri wrote: >> It looks like portscout is stuck again. >> >> The numbers changed once 27+ hours ago, and didn't change again. >> >> Normally portscount updates numbers at least several times a day.

Re: Unmaintained FreeBSD ports which are out of date

> On 6. Mar 2023, at 21:29, Dave Horsfall wrote: > > On Mon, 6 Mar 2023, portsc...@freebsd.org wrote: > > [...] > >> +-+ >> cad/ifcopenshell| 0.6.0 | >> blenderbim-230306 >

Re: Can security/ca_root_nss be retired?

On Fri, 20 Jan 2023 17:54:15 +0100 (CET) free...@oldach.net (Helge Oldach) wrote: > Michael Gmelin wrote on Fri, 20 Jan 2023 17:31:43 +0100 (CET): > > The CA_BUNDLE knob was enabled on ftp/curl by default for many years > > and was just recently disabled (in c63a8f65af, j

Re: Can security/ca_root_nss be retired?

On Fri, 20 Jan 2023 17:15:07 +0100 (CET) free...@oldach.net (Helge Oldach) wrote: > Michael Gmelin wrote on Fri, 20 Jan 2023 17:07:41 +0100 (CET): > > Well, whatever is done, such a change needs to be managed properly, > > which includes adding an entry to UPDATING in p

Re: Can security/ca_root_nss be retired?

On Fri, 20 Jan 2023 09:15:32 +0100 (CET) free...@oldach.net (Helge Oldach) wrote: > Michael Gmelin wrote on Fri, 20 Jan 2023 08:51:31 +0100 (CET): > > > On 20. Jan 2023, at 07:45, free...@oldach.net wrote: > > > Definitely however ca_root_nss should go away in favor of th

Re: Can security/ca_root_nss be retired?

> On 20. Jan 2023, at 09:15, free...@oldach.net wrote: > > Michael Gmelin wrote on Fri, 20 Jan 2023 08:51:31 +0100 (CET): >>>> On 20. Jan 2023, at 07:45, free...@oldach.net wrote: >>> Definitely however ca_root_nss should go away in favor of the built-in >>

Re: Can security/ca_root_nss be retired?

> On 20. Jan 2023, at 07:45, free...@oldach.net wrote: > > Mel Pilgrim wrote on Thu, 19 Jan 2023 14:58:12 +0100 (CET): >>> On 2023-01-19 4:08, Tomoaki AOKI wrote: >>> On Thu, 19 Jan 2023 03:13:48 -0800 >>> Mel Pilgrim wrote: >>> Given /usr/share/certs exists for all supported releases,

Re: Can security/ca_root_nss be retired?

> On 19. Jan 2023, at 23:09, Tomoaki AOKI wrote: > > On Thu, 19 Jan 2023 05:58:12 -0800 > Mel Pilgrim wrote: > >>> On 2023-01-19 4:08, Tomoaki AOKI wrote: >>> On Thu, 19 Jan 2023 03:13:48 -0800 >>> Mel Pilgrim wrote: >>> Given /usr/share/certs exists for all supported releases, is th

Re: New port: security/local-php-security-checker

On 8. Dec 2022, at 08:24, Kevin Oberman wrote:On Wed, Dec 7, 2022 at 7:33 AM Martin Neubauer wrote:On Wed, 7 Dec 2022, Einar Bjarni Halldórsson wrote: > Hi, > > I created a PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261148 > which I've been updating when new ve

Re: Git malfunctions on the ports tree

> On 7. Nov 2022, at 19:58, Yuri wrote: > > This happened several times to me. I had to revert commits. Now this > happened again. > > > When several ports have changes in the tree and one of the ports is committed > with 'cd / && git commit .' - other ports sometimes also get > into the

Re: aarch64 ports build on amd64

> On 11. Oct 2022, at 13:22, Nuno Teixeira wrote: > >  > Hello, > > I don't yet have arm64 hardware to test ports so I will rely on emulation for > tests. > > poudriere+qemu don't let me build rust, python, etc. > > Is there other way to emulate arm64? > I documented the procedure I used

Re: ERROR: Ports Collection support for your FreeBSD version has ended o_O

> On 8. Sep 2022, at 05:03, Tomek CEDRO wrote: > > On Mon, Sep 5, 2022 at 11:52 PM Michael Gmelin wrote: >> On 5. Sep 2022, at 22:45, Tomek CEDRO wrote: >> Hello world :-) >> After `git pull` I get this warning now on each port build: >> /!\ ERROR: /!\ >

Re: ERROR: Ports Collection support for your FreeBSD version has ended o_O

> On 5. Sep 2022, at 22:45, Tomek CEDRO wrote: > > Hello world :-) > > After `git pull` I get this warning now on each port build: > > /!\ ERROR: /!\ > Ports Collection support for your FreeBSD version has ended, and no > ports are guaranteed to build on this system. Please upgrade to a > su

Re: nginx-full version numbering question

> On 29. Aug 2022, at 00:33, Pete Wright wrote: > > On Sun, Aug 28, 2022 at 11:05:24PM +0200, Michael Gmelin wrote: >> >> >>>> On 28. Aug 2022, at 19:23, Pete Wright wrote: >>> >>>  hey there - i had a question about an apparent ve

Re: nginx-full version numbering question

> On 28. Aug 2022, at 23:05, Michael Gmelin wrote: > >  > > >>> On 28. Aug 2022, at 19:23, Pete Wright wrote: >>> >>  hey there - i had a question about an apparent version numbering issue >> with the nginx-full port: >> https://www.

Re: nginx-full version numbering question

> On 28. Aug 2022, at 19:23, Pete Wright wrote: > >  hey there - i had a question about an apparent version numbering issue with > the nginx-full port: > https://www.freshports.org/www/nginx-full/ > > on April 10th the version number is: 1.20.2_9,2 > then on the next update (may 31) the vers

Re: security/clamav: /ar/run on TMPFS renders the port broken by design

On Sun, 28 Aug 2022 03:21:24 -0700 Cy Schubert wrote: > In message <16b4-76a1-4e46-b7c3-60492d379...@freebsd.org>, > Michael Gmelin w > rites: > > > > > > > > > On 28. Aug 2022, at 10:42, free...@oldach.net wrote: > > >=20 > >

Re: security/clamav: /ar/run on TMPFS renders the port broken by design

> On 28. Aug 2022, at 10:42, free...@oldach.net wrote: > > Cy Schubert wrote on Sat, 27 Aug 2022 17:26:38 +0200 (CEST): >> As stated before in this thread, replacing /var/run with tmpfs is not a >> supported configuration. > > Not supported? What is the purpose of /etc/rc.d/var then? That cre

Re: security/clamav: /ar/run on TMPFS renders the port broken by design

> On 27. Aug 2022, at 15:18, free...@oldach.net wrote: > > Michael Gmelin wrote on Sat, 27 Aug 2022 15:02:04 +0200 (CEST): >> (you're removing /var/run, which shouldn't be removed > > Not quite. It's actually not uncommon to boot with an empty /var. Ple

Re: security/clamav: /ar/run on TMPFS renders the port broken by design

> On 27. Aug 2022, at 12:54, FreeBSD User wrote: > > Am Sat, 27 Aug 2022 11:21:40 +0200 > Michael Gmelin schrieb: > >>>> On 27. Aug 2022, at 08:31, FreeBSD User wrote: >>> >>> Hello, >>> >>> I'm referencing to Bug 259

Re: security/clamav: /ar/run on TMPFS renders the port broken by design

> On 27. Aug 2022, at 08:31, FreeBSD User wrote: > > Hello, > > I'm referencing to Bug 259699 [2] and Bug 259585 [1]. > > Port security/clamav is without doubt for many of FreeBSD users an important > piece of security > software so I assume a widespread usage. > > It is also a not uncomm

Re: poudriere overlay: passing down git ENV variables (problem: self signed certificates)

ert can be more secure if you pin it, but since their approach was ignoring cert verification completely, this level of security probably isn’t what they were going for. Cheers Michael > . > > Michael Gmelin wrote on 2022/08/04 07:58: >>> Thanks, I simply copy and pasted

Re: poudriere overlay: passing down git ENV variables (problem: self signed certificates)

> On 4. Aug 2022, at 00:55, Michael Gmelin wrote: > >  > >> On 4. Aug 2022, at 00:38, Tatsuki Makino wrote: >> Hello. >> >> In git-2.37.1/http.c... >> >> 　　　︙ >> if (!curl_ssl_verify) { >>

Re: poudriere overlay: passing down git ENV variables (problem: self signed certificates)

> On 4. Aug 2022, at 00:38, Tatsuki Makino wrote: > Hello. > > In git-2.37.1/http.c... > > 　　　︙ >if (!curl_ssl_verify) { >curl_easy_setopt(result, CURLOPT_SSL_VERIFYPEER, 0); >curl_easy_setopt(result, CURLOPT_SSL_VERIFYHOST, 0); >} else { >

Re: poudriere overlay: passing down git ENV variables (problem: self signed certificates)

er way to achive that > task? > If you read /usr/local/bin/poudriere you see that it filters the environment. So neither GIT_NO_SSL_VERIFY will come through, nor HOME (which also means that git can't read $HOME/.gitconfig). The pragmatic solution would be to create a git wrapper script and tell poudriere to use it: cat >/tmp/git_wrap <>/usr/local/etc/poudriere.conf Cheers Michael -- Michael Gmelin

Re: MegaCLI port is ports-only -- how would you deploy it?

> On 3. Aug 2022, at 01:07, Dan Mahoney wrote: > > Hey there all, > > At the dayjob we have a fleet of Dell Poweredge servers that can use either > mptsas or mrsas -- if you use mptsas, you use mptutil (in base) to check the > state of the card. > > If you use mrsas, you need megacli, whi

Re: Handling conflicts and cherry-pick to 2022Q3 issue

Look at what you’re trying to commit and check if there are any conflict marker (>>>, <>, =). > On 28. Jul 2022, at 23:44, Nuno Teixeira wrote: > >  > Hello, > > I'm trying to commit to 2022Q3 PR 265530 and after solving Makefile conflicts > (PORTREVISIONs), git push

Re: Heads-up: Pending removal of 'Created by' from the ports tree

> On 5. Jul 2022, at 15:17, Tobias C. Berner wrote: > > Moin moin > > portmgr is intending to remove all occurrences of 'Created by' from the tree > by the end of this quarter [1]. > > This is done to honor those that are actively maintaining the ports tree and > not those that were there b

Re: git pull not replicating?

> On 18. Jun 2022, at 22:25, Andy Farkas wrote: > >  > Thank you Michael and Mark, you have increased my understanding of git > such that it now makes a bit more sense of what is going on. The many > many git manpages I find hard to comprehend. (what does > supposed to mean?) See top answer

Re: Issue with install prefix

> On 18. Jun 2022, at 17:20, jbo@insane.engineer wrote: > >  > Hello guys, > > Please excuse the non-telling subject of this e-mail. I am a bit lost here > and don't exactly understand where the problem I'm about to outline > originates form. > > A few weeks ago, I created a port of a C++17

Re: git pull not replicating?

> On 18. Jun 2022, at 15:58, Andy Farkas wrote: > >  > If I do a 'git pull' in /usr/ports usually it updates a few files > and I think 'good, my ports tree is in sync with upstream'. And if > I do it again shortly afterwards, I get: > > root:/usr/ports # git pull > Already up to date. > root:

Re: Differences between ports build and poudriere

> On 15. Jun 2022, at 23:11, Tatsuki Makino wrote: > > I write optimistically in reference to the ports I maintain, but it seems > very difficult to port a build by Bazel. > Only port of games/anki exist that are built by Bazel, but there are a lot of > patches. > > It looks like it would

Re: Help needed with USE_GITHUB

The key is correcting the typo in PORTNAME: gingko => ginkgo Cheers Michael > On 12. Jun 2022, at 01:23, Philipp Ost wrote: > > Hi everyone, > > I'm working on a port for the Gingko library > (https://github.com/ginkgo-project/ginkgo). Since the project is hosted on > GitHub, I'd like to m

Re: make index fail

> On 9. Jun 2022, at 11:59, Andy Farkas wrote: > >  > Whenever I update my ports tree (git pull) I then do a make index. What is the output of “git status”? -m > Over the last week or so it has been failing like this: > > %%% > root@mater:/usr/ports # make index > Generating INDEX-13 -

Re: Bugzilla preview does not work

> On 16. Apr 2022, at 17:05, Marcel Bischoff wrote: > > Hi all, > > I just wanted to submit a bug ticket for a port and found that the Bugzilla > preview window does not work at all — its output is just blank. I've tested > this in Safari and Firefox with all ad blockers off. There's no err

Re: [FreeBSD-Ports-Announce] New 2022Q1 branch

> On 3. Jan 2022, at 01:00, George Mitchell wrote: > > On 1/1/22 15:05, Jan Beich wrote: >> Rene Ladan writes: >> [...] >> Also: >> - New Python version: 3.11 >> [...] > > Given that https://docs.python.org/3/ describes Python 3.11 as "(in > development)", is this possibly a little prematur

Re: Cannnot fetch net-im/scli

ersioneer/python-versioneer/issues/217 I opened a task to discuss the issue with the author and tagged 0mp in it: https://github.com/isamert/scli/issues/151 I also pushed a corrected distinfo: https://cgit.freebsd.org/ports/commit/?id=a22bf332 Best Michael -- Michael Gmelin

Re: Outdated ports

> On 1. Jan 2022, at 16:00, Michael Fiano wrote: > > Forgive me if this is not the correct forum. I've only been using FreeBSD > for a a couple months after a couple decades of Linux, and I noticed some > popular projects have ports that are severely out-dated: > > sysutils/dunst is behind

Re: Regarding port(s) you maintain in FreeBSD ports collection

> On 8. Nov 2021, at 00:46, Daniel Engberg wrote: > > Hi, > > I apologize for the confusion, I tried to catch "everyone" and I've (b)cc > all maintainers that do no have a Phabricator account but since a lot of > ports are old and unassigned to I figured that I should also notify > ports@ too

Re: Regarding port(s) you maintain in FreeBSD ports collection

> On 7. Nov 2021, at 23:40, Greg 'groggy' Lehey wrote: > > On Sunday, 7 November 2021 at 20:27:01 +0100, Michael Gmelin wrote: >>> On 7. Nov 2021, at 20:06, Dan Mahoney (Ports) wrote: >>>>> On Nov 7, 2021, at 7:04 AM, Daniel Engberg wrote: >&g

Re: Regarding port(s) you maintain in FreeBSD ports collection

> On 7. Nov 2021, at 20:06, Dan Mahoney (Ports) wrote: > > Hi, > > This caused me some headscratching (wait, is my port here but not in the > list? Am I mailed because a port here is a dependency of my port?) > > I’ve concluded that instead I’m receiving this mail because you sent it to

Re: deskutils/nextcloudclient Cannot connect securely to

> On 29. Oct 2021, at 14:12, Per olof Ljungmark wrote: > > On 10/25/21 16:22, Per olof Ljungmark wrote: >>> On 10/25/21 09:51, Guido Falsi wrote: >>> On 25/10/21 08:14, Per olof Ljungmark wrote: FreeBSD 12-STABLE from Oct 15 nextcloudclient 3.3.5 I get popup messages from

Re: Portscout and gitlab

On Sat, 16 Oct 2021 20:35:09 +0200 Michael Gmelin wrote: > Hi, > > It seems like portscout didn‘t pick up the new version of > net-im/signald, is there anything I as a maintainer can do, or would > this need to be added as a feature to portscout itself? > > Thanks >

Portscout and gitlab

Hi, It seems like portscout didn‘t pick up the new version of net-im/signald, is there anything I as a maintainer can do, or would this need to be added as a feature to portscout itself? Thanks Michael

Re: State of LibreSSL in FreeBSD ports

> On 4. Oct 2021, at 20:21, Mathieu Arnold wrote: > > On Sun, Oct 03, 2021 at 04:16:54PM +0200, Felix Palmen wrote: >> Is LibreSSL in FreeBSD ports >> >> * supported, so ports should build with it if at all possible? >> * supported on a "best effort" base, so setting a port BROKEN is >> acc

Re: Issues with security/step-cli

On Tue, 3 Aug 2021 14:53:07 +0200 Markus Wipp wrote: > > On 3. Aug 2021, at 14:34, Michael Gmelin wrote: > > > > > > > > On Tue, 3 Aug 2021 13:41:42 +0200 > > Markus Wipp wrote: > > > >> Sure. I attached you the diff. > >> &

Re: Issues with security/step-cli

On Tue, 3 Aug 2021 13:41:42 +0200 Markus Wipp wrote: > Sure. I attached you the diff. > > > > On 3. Aug 2021, at 13:35, Michael Gmelin wrote: > > > > > > > >> On 3. Aug 2021, at 13:29, Markus Wipp wrote: > >> > >> Hi all,

Re: Issues with security/step-cli

> On 3. Aug 2021, at 13:29, Markus Wipp wrote: > > Hi all, > > I’m the maintainer of the security/step-cli port and I’m currently facing > some issues, I seem to be unable to fix. > > I currently try to create the patch for the latest version 0.16.1 > > I did the following: > > 1) I rem

Re: problem building gstreamer1

> On 13. Jul 2021, at 19:04, Robert Huff wrote: > >  >[ sent this to maintainer Saturday; got no reply; trying here ] > > > Hello: >For several weeks, attempts to build gstreamer1 have produced the > appended and a hung-but-killable process. >This is way above my pay grade. >

Re: git command to run .hooks/prepare-commit-msg

> On 3. Jul 2021, at 18:58, Nuno Teixeira wrote: > > Hello, > > I can't find git command so I can run .hooks/prepare-commit-msg when I > commit. The hook itself contains instructions how to install it. -m > > Thanks > Nuno

Re: Bind 9.16.17 update built for packages?

> On 21. Jun 2021, at 13:26, Stefan Esser wrote: > > Am 21.06.21 um 09:49 schrieb Simon Wright: >> Indeed "these things they do 'appen!" :) Is it possible/worth adding a >> note to UPDATING to not upgrade to 9.16.17? >> >> Something like this: >> >> >> 20210621: >> AFFECTS: use

Re: Restarting poudriere

On Tue, 15 Jun 2021 01:31:32 -0700 Mark Millard wrote: > Michael Gmelin wrote on > Date: Tue, 15 Jun 2021 09:31:26 +0200 : > > On Mon, 14 Jun 2021 18:02:33 -0700 > bob prohaska wrote: > > > > > On Mon, Jun 14, 2021 at 09:52:22

Re: Restarting poudriere

On Mon, 14 Jun 2021 18:02:33 -0700 bob prohaska wrote: > On Mon, Jun 14, 2021 at 09:52:22PM +0200, Michael Gmelin wrote: > > > > > > > On 14. Jun 2021, at 20:30, bob prohaska > > > wrote: > > > > > > ???On Mon, Jun 14, 2021 at 06:46:

Re: Restarting poudriere

> On 14. Jun 2021, at 20:30, bob prohaska wrote: > > On Mon, Jun 14, 2021 at 06:46:52PM +0200, Michael Gmelin wrote: >> On Mon, 14 Jun 2021 09:28:39 -0700 >> What do you mean by "restarting"? >> How do you invoke poudriere exactly? > As root, >

Re: Restarting poudriere

Perhaps building the offending packages individually, or in separate > jails? I've been using the same jail for all attempts so far. > > Thanks for reading, and everyone's help! > > bob prohaska -- Michael Gmelin

Re: Restraining poudriere

> On 12. Jun 2021, at 20:08, bob prohaska wrote: > > On Sat, Jun 12, 2021 at 10:45:13AM -0700, Jose Quinteiro wrote: >>> On 6/12/21 10:29 AM, bob prohaska wrote: >>> In playing with poudriere on raspberry pi 3 and 4 it seems to >>> work well on the 8 GB Pi4 but is over-optimistic on the 1 GB P

Re: Restraining poudriere

> On 12. Jun 2021, at 19:31, bob prohaska wrote: > > In playing with poudriere on raspberry pi 3 and 4 it seems to > work well on the 8 GB Pi4 but is over-optimistic on the 1 GB Pi3. > > Can poudriere be configured to tackle packages one at a time? Yes, see poudriere.conf: # parallel build