Can someone explain to me whats going on with pkg?

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.
 
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.
 
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.
 
It looks like the latest repo already updated on Tuesday.
Can those who have XFCE4 update?
$ sudo pkg upgrade -n
Code:
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
 
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?
 
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.
 
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.
 
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.
 
Back
Top