FreeBSD 12 EoL, or something else? pkg: http://pkgmir.geo.freebsd.org/FreeBSD:12:amd64/quarterly/meta.txz: Not Found

R

rowan194

Trying to update packages on a 12.4 system, the following happens:

Code: 
# pkg update
Updating FreeBSD repository catalogue...
pkg: http://pkgmir.geo.freebsd.org/FreeBSD:12:amd64/quarterly/meta.txz: Not Found
repository FreeBSD has no meta file, using default settings
pkg: http://pkgmir.geo.freebsd.org/FreeBSD:12:amd64/quarterly/packagesite.pkg: Not Found
pkg: http://pkgmir.geo.freebsd.org/FreeBSD:12:amd64/quarterly/packagesite.txz: Not Found
Unable to update repository FreeBSD
Error updating repositories!

This happens on 2 different systems. On a third, things get a little more vague:

Code: 
# pkg update
Updating FreeBSD repository catalogue...
pkg: An error occured while fetching package
pkg: An error occured while fetching package
repository FreeBSD has no meta file, using default settings
pkg: An error occured while fetching package
pkg: An error occured while fetching package
Unable to update repository FreeBSD
Error updating repositories!

I have confirmed with a browser that the URLs are indeed 404.

I'm assuming this is an EoL thing, but I thought I'd ask. If so, is there a repository for older release packages, or has it been permanently removed?

( freebsd-update warns me about EoL, but still completes; pkg isn't playing so nice.)
 
It's been written here a lot, still another time:

EOL never comes by surprise. By the time a new major version is released, you already know it will be supported for 5 years (all you have to do is follow minor releases, which keep the ABI stable, so issues doing these upgrades should be, at least, extremely rare). There's always a table of scheduled EOL dates available on the website, plus IIRC freebsd-update warns some time before EOL of the version you're running.

With the typical schedule of a new major release being done while there are still two earlier major versions supported, you're expected to do a major upgrade around every 2 to 2.5 years .... or, if you want to skip every other major, every 4 to 5 years. This really shouldn't be an issue, but you're expected to plan ahead a bit, and choose your own "upgrade strategy" matching your needs ... and of course, upgrade before hitting EOL. Yes, package repositories are removed as soon as a version is EOL. And btw, ports won't "help" here either, as anything specific to the EOL version is removed from them as well, and sanity-checks are updated to require a supported version -- all you could do is use an earlier version of the ports tree temporarily.
 
  • Like
Reactions: mer
I have v12 on my XigmaNAS, and have no intention of upgrading it.
I see this as a sleeping dog that is currently doing everything I need, so I have no need to kick it.
 
People are frightened to upgrade to either of these due to number of reported problems. The pkg repository could have stayed a little longer. Moreover there might be another release of 12.4 series. If that happens there will be a new OS without its pkg.
 
Matlib said:
People are frightened to upgrade to either of these due to number of reported problems.
Click to expand...
Please name the problems you are talking about.

Matlib said:
The pkg repository could have stayed a little longer. Moreover there might be another release of 12.4 series. If that happens there will be a new OS without its pkg.
Click to expand...
No. And regarding this SA, you're misinterpreting it. What happened was: 12.4 had an older version of OpenSSH, so the patch needed to be backported, which proved "non-trivial". The issue was relevant enough to not wait for that to complete. Now, 12.4 is EOL, and as a consequence, this issue will never be patched. That's just the first and most obvious issue you'll have if you continue to use 12.4 ... more unpatched security holes are to come.
 
  • Like
Reactions: mer
Matlib said:
Click to expand...
So, this one is some issue you had which is unconfirmed and could be caused by whatever, while ...

Matlib said:
Click to expand...
... this isn't even a bug. Well, arguably, the error message is misleading. So, maybe a bug, but not a functional one. BSD sed does not support perl-style character classes like \s (and never has, not in 12 not in any earlier version). And no, the fact it doesn't support them isn't a bug either. They're a non-standard perl idea, and the fact that GNU decided to add support doesn't mean everyone should follow suit.

Matlib said:
to name just two that come to my mind right now.
Click to expand...
Looks like they're unfit to support your earlier claim. Do you have any other, or was ist just some expression of a "feeling"?
 
Let's focus on the main question of this thread....

I'm facing the same problem...
Is there any way to update pkg in 12.4 EOL ?

Code: 
# pkg update
Updating FreeBSD repository catalogue...
pkg: http://pkgmir.geo.freebsd.org/FreeBSD:12:amd64/quarterly/meta.txz: Not Found
repository FreeBSD has no meta file, using default settings
pkg: http://pkgmir.geo.freebsd.org/FreeBSD:12:amd64/quarterly/packagesite.pkg: Not Found
pkg: http://pkgmir.geo.freebsd.org/FreeBSD:12:amd64/quarterly/packagesite.txz: Not Found
Unable to update repository FreeBSD
Error updating repositories!
 
You must log in or register to reply here.
Back
Top