Can someone explain to me whats going on with pkg?

[CeXP1917]

Imagine having a /usr/local2025q1 and a /usr/local2025q2. Things would be so much more flexible and resilient.

Sounds like

# peadm create 2025Q1
# pkg upgrade
...
# peadm 2025Q1 run /usr/local/bin/someapp

 

[kpedersen]

Sounds like

# peadm create 2025Q1
# pkg upgrade
...
# peadm 2025Q1 run /usr/local/bin/someapp

Isn't something like peadm more like creating an entire chroot / jail?

We still want simplicity alongside resilience.

 

[POSIX.1]

What can i do to prevent accidentally purging important software from my system?

You may lock essential packages with pkg-lock(8) to protect things you need to survive like browser, Libreoffice or mail client etc..
And yes having backups or at least creating a zfs-snapshot before upgrading is regarded as best practice.

 

[joe81tx]

The quarterly build from Monday has finally replicated to the pkg repos, you should be able to access most things via binary packages again after a pkg update -f. It looks like the latest repo already updated on Tuesday. The only main desktop missing is the full fat version of gnome, but gnome-lite is available.

 

[astyle]

The current issue however is little more involved as it's caused by a bug in the OS itself.

What bug are you talking about?

When I looked at pkg-fallout.com, it points to build failure logs at https://pkg-status.freebsd.org, like this one for x11/plasma6-plasma... And what I'm seeing there, very early on:

!!! Jail is newer than host. (Jail: 1500031, Host: 1500028) !!!
!!! This is not supported. !!!
!!! Host kernel must be same or newer than jail. !!!
!!! Expect build failures. !!!

Well, at the end, this particular compilation failed on pam_kwallet5.so, so this points to KDE 6 packages not building right... the log is for x11/plasma6-plasma v. 6.2.5, which built just fine for me on 14.2-RELEASE, I have screenshots over in the thread about trying to make Wayland cooperate with Plasma 6... Close, but no cigar... my version was 6.2.4...

My initial impression was that this is more about how the build jails get spun up by Poudriere. Either the Poudriere automated process is doing something strange when creating a jail for the compilation, or somebody updated an existing build jail by hand (when that was probably not the best idea).

But now that I look at the logs a bit more closely, I note the versions involved in the failure, and I have less confidence in my initial impression. I just don't see the connection between a dependency resolution failure and the age difference between host and jail. I don't think that Poudriere should be scared of that.

 

[bgroper]

Set up your own repository, build once, install many. This is especially beneficial if you have to provide for a bunch of machines. Added benefit, you can set your own default versions for mysql, perl, php, python, ruby, java, etc. And you get to set/unset options for everything. Meaning you can really tailor made the packages for your environment. And, last but not least, you get to decide what to update and what not, and when this happens. With a local repository you get the best of both worlds, the flexibility of ports and the ease of management from packages.

I'm interested to learn how to do this efficiently and effectively.
Couldn't find any good notes in the handbook, but maybe I missed it.
Pleases and thankyous for any tips or clues to find good informations.

 

[facedebouc]

https://freebsdfoundation.org/our-w...om-poudriere-packages-in-your-own-repository/
https://vermaden.wordpress.com/2023/04/30/simple-freebsd-poudriere-harvester-guide/

 

[bgroper]

https://freebsdfoundation.org/our-w...om-poudriere-packages-in-your-own-repository/
https://vermaden.wordpress.com/2023/04/30/simple-freebsd-poudriere-harvester-guide/

Thanks.

 

[USerID]

It looks like the latest repo already updated on Tuesday.

Can those who have XFCE4 update?
$ sudo pkg upgrade -n

Installed packages to be REMOVED:
    webkit2-gtk3: 2.34.6_10

Number of packages to be removed: 1
Number of packages to be installed: 11
Number of packages to be upgraded: 268
Number of packages to be reinstalled: 37

 

[kota905]

xfce was missing few day ago but is available now.
Installed it this morning and it works fine.

 

[mer]

Took a little bit for the package repos to be updated from the builds, but at least items I was waiting for are now available.

 

[ejpirat]

Friends, a general question therefore. Please, do not take this as a typical ungrateful rant of another FOSS user, I understand the challenges and complexity of the project.
I went for daily driving FreeBSD on a personal PC recently and starting from 14.0, mere research interest, and it suffices well my personal computing demands. Of course, there are no problems with the base system, but I must say I found everything to be rather polish for a contemporary personal use.
Yet and as you can imagine, the last several weeks were quite bad. Since I am forcing myself to read whatever the software prompts me to do, I did not break anything. But there were moments when pkg offered me to strip everything down to barebone x11, and several pretty popular and too complex/with way too heavy dependencies to install from ports packages were not available. I am wondering, are such disruptions in a non-base environment common in the FreeBSD world?

 

[astyle]

I'm interested to learn how to do this efficiently and effectively.
Couldn't find any good notes in the handbook, but maybe I missed it.
Pleases and thankyous for any tips or clues to find good informations.

Poudriere only has very minimal notes in the Handbook about building ports, IIRC. And even that urges the readers to refer to the manpages and the Porter's Handbook.

 

[cracauer@]

I am wondering, are such disruptions in a non-base environment common in the FreeBSD world?

It's the first time it has been this bad.

 

[fernandel]

Can those who have XFCE4 update?
$ sudo pkg upgrade -n

Installed packages to be REMOVED:
    webkit2-gtk3: 2.34.6_10

Number of packages to be removed: 1
Number of packages to be installed: 11
Number of packages to be upgraded: 268
Number of packages to be reinstalled: 37

On the lates we have long time
https://www.freshports.org/www/webkit2-gtk/

 

[mer]

It's the first time it has been this bad.

Agreed and I'm going back to at least 5.x.
Honestly looking at it, "quarterly" does that mean "everything built for the first day of the new quarter"? I don't know, but it seems to have been fixed within the first month of the quarter, so "close enough for government work".

But it does point out the need for paitence and "don't jump on updates at 12:01am" The package builds take a while, pushing results to all the pkg repo servers takes some time.

 

[ShelLuser]

I'm interested to learn how to do this efficiently and effectively.
Couldn't find any good notes in the handbook, but maybe I missed it.

There are dozens of ways to set up your own repository, I even wrote a guide about doing this with Portmaster.

Most people will focus on using a port manager such as Portmaster and/or Poudriere which can then sort the whole thing out for me. But... always keep the Unix philosophy in mind which is also a big part of FreeBSD: it's not too difficult to script something of your own.

I mean... it all essentially boils down to using pkg-repo(8) to set up & maintain your repository plus pkg-create(8) to actually populate it with contents.

 

[Kaminar]

The pkg-status.freebsd.org page shows that packages for 14.2 of default branch are now being built on three servers beefy7, beefy8 and beefy22 at the same time. It looks like the first two have started building packages from scratch. Does anyone know what is happening with the builds for 14.2?

 

[mer]

The pkg-status.freebsd.org page shows that packages for 14.2 of default branch are now being built on three servers beefy7, beefy8 and beefy22 at the same time. It looks like the first two have started building packages from scratch. Does anyone know what is happening with the builds for 14.2?

I'm not sure I understand your question. "Default" branch is "package latest", typically gets rebuilt all the time because changes could be committed daily. Given that I think one should think of "packages on default branch doing continuous integration builds". It may not be strictly accurate, but reasonably close in concept.

 

[astyle]

The pkg-status.freebsd.org page shows that packages for 14.2 of default branch are now being built on three servers beefy7, beefy8 and beefy22 at the same time. It looks like the first two have started building packages from scratch. Does anyone know what is happening with the builds for 14.2?

Well, 'latest' is where you could end up in a bit of a gamble, where some packages fail to build. Add in the fact that you're at the mercy of the official repo builders who decide what Makefile flags to set...

 

[Kaminar]

I'm not sure I understand your question. "Default" branch is "package latest", typically gets rebuilt all the time because changes could be committed daily. Given that I think one should think of "packages on default branch doing continuous integration builds". It may not be strictly accurate, but reasonably close in concept.

Yes, I meant the packages latest. I was surprised that lates packages are now being built on three servers at once.

 

[POSIX.1]

I was surprised that latest packages are now being built on three servers at once.

That would take me surprise too if all 3 bulk builds go into the same repository, because the time line of committed ports and their dependencies might not be consistent. I.e. a bulk run of ~35.000 ports takes typically some days to complete, while a later bulk run with only ~10.000 ports to build would be finished earlier, but some of the ~35.000 ports might have an older version.