Solved pkg repos for 15.0 (basify) and latest

fjdlr

fjdlr

Hi,
I have doubts about enabling the latest repository in FreeBSD-15.0 (pkgbasify). I've encountered package conflicts and I'm looking for help with the configuration.about enabling the latest repository in FreeBSD-15.0 (pkgbasify). I've encountered package conflicts and I'm looking for help with the configuration.
/usr/local/etc/pkg/repos 12:17 #> cat FreeBSD-base.conf
FreeBSD-base: {
enabled: yes
}
Click to expand...

/usr/local/etc/pkg/repos 12:17 #> cat FreeBSD.conf
#FreeBSD: { url: "pkg+https://pkg.freebsd.org/${ABI}/latest" }
FreeBSD: {
url: "http://pkg0.sjb.freebsd.org/${ABI}/latest",
mirror_type: "NONE",
enabled: no
}
Click to expand...

freebsd-version -kru
15.0-RELEASE-p1
15.0-RELEASE-p1
15.0-RELEASE-p1
Click to expand...


Thks
 
For the conflicting repos, see my post: https://forums.freebsd.org/threads/conflict-hell-after-freebsd-update.100824/#post-733744

You have all the repos defined in /etc/pkg/FreeBSD.conf. The "ports" repos are on quarterly by default. To be on latest repos, you put a conf file in /usr/local/etc/pkg/repos/. Then, as the repos names changed for 15, you have a conflict with that. You just need to adjust your conf file as in my post.

In a pkgbasified system you need, in addition, to enable FreeBSD-base to "yes" as in your quote.

The output you give with freebsd-version -kru is in the wrong order. Be more rigorous.
 
Emrion said:
For the conflicting repos, see my post: https://forums.freebsd.org/threads/conflict-hell-after-freebsd-update.100824/#post-733744

You have all the repos defined in /etc/pkg/FreeBSD.conf. The "ports" repos are on quarterly by default. To be on latest repos, you put a conf file in /usr/local/etc/pkg/repos/. Then, as the repos names changed for 15, you have a conflict with that. You just need to adjust your conf file as in my post.

In a pkgbasified system you need, in addition, to enable FreeBSD-base to "yes" as in your quote.

The output you give with freebsd-version -kru is in the wrong order. Be more rigorous.
Click to expand...
Thks
I try
I don't understand the wrong order
%> freebsd-version -kru
15.0-RELEASE-p1
15.0-RELEASE-p1
15.0-RELEASE-p1
Click to expand...
 
fjdlr said:
OK, if I understand correctly, I change the contents of the file
Code: 
/usr/local/etc/pkg/repos/FreeBSD.conf
by this one
Code: 
FreeBSD-ports: {
url: "pkg+https://pkg.freebsd.org/${ABI}/latest"
}
FreeBSD-ports-kmods: {
url: "pkg+https://pkg.freebsd.org/${ABI}/kmods_latest_${VERSION_MINOR}"
}
Click to expand...
That is a correct setting for using latest packages from the ports tree. However, when installing a fresh FreeBSD 15.0-RELEASE with a packaged base; that is having selected the option Packages (Tech Preview) at installation time, then, for enabling the FreeBSD-base repository, the installer installs additionally,
/usr/local/etc/pkg/repos/FreeBSD.conf
Code: 
FreeBSD-base: {
    enabled: yes,
}
/usr/local/etc/pkg/repos/FreeBSD-base.conf was introduced when a packaged base was still experimental on the 14 branch. While you can have separate, multiple, .conf files as your package configuration files in /usr/local/etc/pkg/repos/, I suggest you consider keeping just one user maintained configuration file: /usr/local/etc/pkg/repos/FreeBSD.conf—unless you have a specific reason not to do so. A more elaborate explananation wrt to switching form quarterly to latest, when having quarterly packages as the default, you can find here.

fjdlr said:
I don't understand the wrong order
Code: 
%> freebsd-version -kru
15.0-RELEASE-p1
15.0-RELEASE-p1
15.0-RELEASE-p1
Click to expand...
It's the same on my packaged base 15.0-RELEASE-p1; I don't see anything wrong with it.
 
Emrion said:
You edited your post. It was p1 only on the first line.
I was referring to a non-pkgbase system. I forgot it shows p1 at all lines in this case. Anyway it's not only not rigorous but also now not honest too.
Click to expand...
Okay, I initially made a mistake with the copy-paste, which I've edited to correct. Sorry.
 
Erichans said:
That is a correct setting for using latest packages from the ports tree. However, when installing a fresh FreeBSD 15.0-RELEASE with a packaged base; that is having selected the option Packages (Tech Preview) at installation time, then, for enabling the FreeBSD-base repository, the installer installs additionally,
/usr/local/etc/pkg/repos/FreeBSD.conf
Code: 
FreeBSD-base: {
    enabled: yes,
}
/usr/local/etc/pkg/repos/FreeBSD-base.conf was introduced when a packaged base was still experimental on the 14 branch. While you can have separate, multiple, .conf files as your package configuration files in /usr/local/etc/pkg/repos/, I suggest you consider keeping just one user maintained configuration file: /usr/local/etc/pkg/repos/FreeBSD.conf—unless you have a specific reason not to do so. A more elaborate explananation wrt to switching form quarterly to latest, when having quarterly packages as the default, you can find here.


It's the same on my packaged base 15.0-RELEASE-p1; I don't see anything wrong with it.
Click to expand...
Okay, I'm starting to understand the intricacies of FreeBSD-15.0 better.
Thanks
 
Ok solved repos
pkg repos
FreeBSD-ports: {
url : "pkg+https://pkg.freebsd.org/FreeBSD:15:amd64/latest",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}
FreeBSD-ports-kmods: {
url : "pkg+https://pkg.freebsd.org/FreeBSD:15:amd64/kmods_latest_0",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}
FreeBSD-base: {
url : "pkg+https://pkg.freebsd.org/FreeBSD:15:amd64/base_release_0",
enabled : no,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkgbase-15"
}
FreeBSD-kmods: {
url : "pkg+https://pkg.freebsd.org/FreeBSD:15:amd64/kmods_latest_0",
enabled : yes,
priority : 1,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
Click to expand...
Now boot last BE
#> freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 15.0-RELEASE from update1.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 15.0-RELEASE-p1.
Click to expand...
And
#> freebsd-version -kru
15.0-RELEASE
15.0-RELEASE
15.0-RELEASE-p1
Click to expand...
Now I am left without being able to upgrade :confused:
 
You have to delete FreeBSD-kmods because it's the same as FreeBSD-ports-kmods.

Thing I don't understand: have you run or not pkgbasify.lua? Seems yes at your first post but no at your last. It's a BE you said, so maybe it's before your run it but that's not clear at all.

When you are under freebsd-update, it's normal to have an userland at p1 and nothing for the kernel.
When you are under pkgbase, you have p1 at all the three lines, but it's the same binaries.

FreeBSD isn't clear on this point, but so it is.

Your system is up-to-date.
 
I don't know if this helps. But I have a 15.0 install on laptop, started as somehthinkg much earlier a few years ago, and this time, was updated with FreeBSD update. Today, I decided it should use pkg so downloaded and ran pkgbasify. When I looked at FreeBSD-base.conf to see what pkgbasify had done it just has
FreeBSD-base: {
enabled: yes
}

Now if I run pkgbasify.lua on a 14.3 system, I get a more detailed FreeBSD-base.conf more like

url = "pkg+https://pkg.freebsd.org/${ABI}/base_release_3";
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}
 
scottro said:
I don't know if this helps. But I have a 15.0 install on laptop, started as somehthinkg much earlier a few years ago, and this time, was updated with FreeBSD update. Today, I decided it should use pgk so downloaded and ran pkgbasify. When I looked at FreeBSD-base.conf to see what pkgbasify had done it just has
FreeBSD-base: {
enabled: yes
}

Now if I run pkgbasify.lua on a 14.3 system, I get a more detailed FreeBSD-base.conf more like

url = "pkg+https://pkg.freebsd.org/${ABI}/base_release_3";
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}
Click to expand...
It's because for a 15 version, you have all the the details of FreeBSD-base in /etc/pkg/FreeBSD.conf. pkgbasify just have to set enabled: yes in /usr/local/etc/pkg/repos/.

In a 14 version, you have nothing in /etc/pkg/FreeBSD.conf concerning FreeBSD-base. So, all the details fall in /usr/local/etc/pkg/repos/.

Very simple but very confusing, especially when you upgrade to a 15 version. As I said, it may leave your recorded repos in a sad state.
 
Emrion said:
You have to delete FreeBSD-kmods because it's the same as FreeBSD-ports-kmods.

Thing I don't understand: have you run or not pkgbasify.lua? Seems yes at your first post but no at your last. It's a BE you said, so maybe it's before your run it but that's not clear at all.

When you are under freebsd-update, it's normal to have an userland at p1 and nothing for the kernel.
When you are under pkgbase, you have p1 at all the three lines, but it's the same binaries.

FreeBSD isn't clear on this point, but so it is.

Your system is up-to-date.
Click to expand...
Yes, indeed, I have tested several BEs including one with pkbasify and another "normal" one My last post is from a BE without pkgbasify Thank you very much, I'll fix the FreeBSD-ports-kmods duplicate. And start again with the modification of the system to pkgbasify BE in ZFS is really great Thank you all
 
You must log in or register to reply here.
Back
Top