Mastodawn

FreeBSD people: anyone monitoring poudriere output checking for failed/ignored/skipped packages in an automated way somehow? Answering questions like "how many ports were skipped? Was www/nginx built successfully?" #FreeBSD #poudriere

Pete Orrall 6d ago

Great #video by @garyhtech on why #BSD will never own the cloud.

#Linux owns the #cloud and frankly I'm fine with that. #FreeBSD doesn't need to compete with Linux in this area. It may not have the massive ecosystem, but given its strengths, it functions just fine for back end #infrastructure, in general and niche use cases.

People frequently tout FreeBSD for #ZFS and #Jails but honestly I think #Ports and #Poudriere are huge selling points

https://www.youtube.com/watch?v=XWf1z1ifjOc

Why Linux Owns the Cloud (And BSD Probably Never Will)

YouTube

Show thread

Graham Perrin Mar 3

@dvl I always chose the pkgbase method when using poudriere to create a jail.

Historically (before FreeBSD 16.0-CURRENT):

poudriere jail -c -v 15 -j main -m pkgbase=base_latest -U https://pkg.freebsd.org/

– from <https://www.reddit.com/r/freebsd/comments/1cmffhu/poudriere_jail_method_pkgbase/l3atzzs/> (you were in a different thread under the same post).

poudriere-jail(8) and pkgbase: FreeBSD-base package cache accumulation: <https://github.com/freebsd/poudriere/discussions/1276>

#FreeBSD #poudriere #pkgbase

pkg.FreeBSD.org

Show thread

/dev/aubergine0 Feb 12

Well wouldja lookit that. It actually did need that much memory, and with a bit more configuration I got it to build the package that I wanted. 😲

A little more mucking about with setting up a bare-bones local package repository and it's done. It works, as far as I can tell.

Of course after building over 350 packages, when I went to install it, it only needed 4 packages to satisfy everything.

Will I get significant mileage out of the new application? Hard to tell. But at least I'm in a place where I can perform decent builds to plug the odd gap in the quarterly package repository.

Thank you #FreeBSD and #poudriere.

/dev/aubergine0 Feb 9

I had been thinking of what to do with the 2012 #MacPro that I crammed full of 64 GB of memory.

I found something in #FreeBSD #ports that I wanted to build, and my newer machines with 32 GB of memory each couldn't handle it. Somewhere within the giant dependency graph of over 350 ports, there are two versions of LLVM as well as all of Node and Rust. A #slow process would be one way to describe it, but that might be underselling it a bit.

I guess I'm #reducing #waste a little bit, maybe? I don't know. I don't know if what I'm building will even work or be useful. But hey, at least I get a little experience with #poudriere so I guess it can't be all bad?

Dan Langille Feb 7

Today I removed devel/freebsd-git-devtools from a buildlist I have in #poudriere - it has been renamed.

I removed it because it wasn't installed on any of my hosts.

I conclude that by this query:

samdrucker=# select host from hostswithpackageshowversion('freebsd-git-devtools');
host
------
(0 rows)

Then I got to thinking: where was it installed and when?

The comment in the buildlist said:

-# for working on FreeBSD
-
-devel/freebsd-git-devtools

I went back to the SamDrucker database and struggled parsing the JSON for a while. Eventually I came up with this inefficient but effective query:

samdrucker=# select date_added, client_ip from incoming_packages where data::text like '%freebsd-git-devtools%' order by date_added desc;
date_added | client_ip
----------------------------+---------------
2024-01-17 03:05:26.208061 | 10.55.0.29/32
2024-01-16 03:24:16.145212 | 10.55.0.29/32
2024-01-15 03:39:19.388747 | 10.55.0.29/32
2024-01-14 03:58:35.967538 | 10.55.0.29/32
...
2023-04-01 03:35:54.836752 | 10.55.0.29/32
2023-03-31 03:59:51.397951 | 10.55.0.29/32
2023-03-30 03:52:11.768713 | 10.55.0.29/32

That tells me it was installed on one host for about 10 months. That host is pkg01, my package build server.

This type of search was one of the orignal goals for SamDrucker, but having historical data has helped me here.

SamDrucker was written for FreeBSD, but it wouldn't take much to port. Both client and server are lightweight and easily understood.

The PostgreSQL function might take a bit of work if you want to migrate away from that choice. The reset is all shell/lua.

https://github.com/dlangille/SamDrucker

GitHub - dlangille/SamDrucker: Stores lists of packages installed on hosts

Stores lists of packages installed on hosts. Contribute to dlangille/SamDrucker development by creating an account on GitHub.

GitHub

KaiXin Jan 9

I am running #FreeBSD RELEASE 15.0 with #pkg for package management, no #ports at all. It appeared to me that the Joe's Window Manager port, x11-wm/jwm, was built without #SVG image support by default. However svg files are actually widely used by multiple icon themes, meaning that many of them will not work under #JWM . Should I simply compile it manually out of ports tree? I mean getting the ports tree is not difficult but setting up #poudriere and all just for one package seems tedious. Are there any other simpler waysnto achieve this?

#AskFedi #BSD #RunBSD #unix #WM