Pkg static repository freebsd load error meta cannot be loaded no error 0

After updating an old machine to 12, I get this error:

pkg-static reports the same error when running the suggested command. Manually downloading the latest pkg-.txz package then let me to pkg add -f ./pkg*.txz , but that’s not something that’s obvious to users (and, without the meta info in the repo, it’s not very secure because there’s no hash provided for the package). pkg can always upgrade itself, but it appears that it can’t always find the package that it needs to be able to upgrade itself.

The text was updated successfully, but these errors were encountered:

This is expected an there is not much we can do. The correct solution is running ‘pkg bootstrap -f’
pkg 1.11 only know about meta version 1.
pkg 1.12 added support for meta version 2.
pkg 1.13 switch meta to version 2.
pkg 1.12 is still the version in quarterly, this issue is only a problem if you’re using latest and do not upgrade often.

There are several things that we could do about this:

1. Have pkg tell you to run pkg bootstrap -f instead of telling you to run pkg-static install -f pkg .
2. Have pkg automatically run that if the check failed.
3. Provide a version 1 meta file that just contains the pkg tool (though this would require the version 2 file having a different name).

Currently, the user experience is very bad if you have a machine that has not been updated for a while. Any version of pkg installed prior to September of last year is currently broken when using the ‘latest’ repo (which, given the lack of real QA or any guarantees of security back-ports to the Quarterly branch, I’d still recommend everyone does).

Источник

pkg update error

I’m getting the following error on my FreeBSD 12.1-RELEASE-p2:

This is my pkg config:

Any thoughts on what might cause the issue?

Lamia

This is my /usr/local/etc/pkg/repos/FreeBSD.conf:

I would add that I’ve had the same setup for quite some time and it only recently broke.

Removing the pkg+http scheme results in a deprecation warning.

Even a bare-minimum .conf like so:

At any rate, I don’t think the problem is with the mirror or the connection, but rather with my local database.

SirDice

Administrator

Reactions: Sevendogsbsd

SirDice

Administrator

I don’t think your local registration database is at fault, it only complains about the meta data and SQL from the locally cached remote repositories. Try removing /var/db/pkg/FreeBSD.meta, /var/db/pkg/FreeBSD_latest.meta, /var/db/pkg/repo-FreeBSD.sqlite and /var/db/pkg/repo-FreeBSD_latest.sqlite. Then running pkg update again.

Do NOT remove /var/db/pkg/local.sqlite (it contains the registrations for your currently installed packages). In case you still want to checkout the backups, they’re in /var/backups/.

Reactions: Brian Cunnie and mfaridi

Thanks for your suggestions.

Unfortunately it sill gives the same «wrong version 2» error as before:

tsarya

Try updating ports-mgmt/pkg from the ports tree using ports-mgmt/portmaster.
If you haven’t fetched the ports tree yet, just do the following:

At the end, you should see pkg version 1.13.2 installed (at the time of writing this post)

Источник

PKG Problem, Can’t Install or Update Packages in 11.2-U7

amp88

Explorer

Hi all. Another strange problem. I just did this procedure a couple of days ago and it worked fine, but now on a clean install of FreeNAS 11.2-U7 it’s failing and I don’t know why. I’m running FreeNAS virtualised in XCP-ng 8.0 and trying to install the xe-guest-utilities package, but it’s failing.

I’m following this procedure (which has worked in a couple of other 11.2-U7 installations I’ve run in the last week or so). Toggle ‘enabled’ in /usr/local/etc/pkg/repos/FreeBSD.conf from ‘no’ to ‘yes’, toggle ‘enabled’ in /usr/local/etc/pkg/repos/local.conf from ‘yes’ to ‘no’, then run ‘pkg install xe-guest-utilities’. However, when I do this I get the following error (with the debug flag enabled to get more verbose output):

amp88

Explorer

In case it’s useful to anyone in figuring this out, here’s the output from running ‘pkg -vv’:

Jailer

Not strong, but bad

amp88

Explorer

Patrick M. Hausen

Hall of Famer

amp88

Explorer

Patrick M. Hausen

Hall of Famer

Unsupported FreeBSD Releases

amp88

Explorer

Unsupported FreeBSD Releases

Patrick M. Hausen

Hall of Famer

FlyingPersian

Patron

I have the same issue in my iocage jails, which are on 11.3.

Here is what happens when I try to update pkg:

And here when I do pkg -d update:

And here when I do pkg -vv:

FlyingPersian, I was making a joke. Survivor is a reality show where people are on an island. I was implying that Lost was also a reality show (which it’s not)
sorry didn#t get that haha
Are you german ?
yes I am
how did you figureß 😀
marbus never gets jokes either
he’s a robot
bite my shiny metal ass.

FlyingPersian: you can use iocage on the cli
that will fetch any jail version you want
oh lord help us.
You may attempt to do this as SweetAndLow says, sir,
but I’ve known you for years,
and I am quite sure it won’t end well.
FlyingPersian> 😀

Patrick M. Hausen

Hall of Famer

FlyingPersian

Patron

Weirdly enough, it works in my other jails, all 11.3

FlyingPersian, I was making a joke. Survivor is a reality show where people are on an island. I was implying that Lost was also a reality show (which it’s not)
sorry didn#t get that haha
Are you german ?
yes I am
how did you figureß 😀
marbus never gets jokes either
he’s a robot
bite my shiny metal ass.

FlyingPersian: you can use iocage on the cli
that will fetch any jail version you want
oh lord help us.
You may attempt to do this as SweetAndLow says, sir,
but I’ve known you for years,
and I am quite sure it won’t end well.
FlyingPersian> 😀

SeaFox

Explorer

Can anyone offer any further advice on this?
It seems I’m having this same issue on multiple 11.3 jails.

damjan

Dabbler

I had the same problem on the upgraded jails. The problem on my system was caused by the outdated repo file in the local directory pointing to FreeBSD 10 repo:
/usr/local/etc/pkg/repos/FreeBSD.conf

I removed the outdated repo config file and pkg update completed successfully; so did the pkg upgrade .

On one of the upgraded zones, pkg did not work because of outdated dependencies. I used pkg-static to upgrade pkg to the latest version followed by the pkg upgrade . Since then I do not have any issues.

So check if you have any /usr/local/etc/pkg/repos/FreeBSD.conf file pointing to the old FreeBSD repo.

SeaFox

Explorer

Nah, that file does not exist by default in the jails. They seem to be configured elsewhere to use the quarterly update manifest and not the latest. But you did give me an idea. I know I can create that file and point it to the Latest packages for FreeBSD, so I tried that, and it also did not work. I was still getting the same error as FlyingPersian.

But I think I just found the solution: pkg bootstrap -f

I seem to be able to update packages normally now. I’m going to roll back this jail and try again one more time to make sure the change in respository is not playing a role, too.

When this first started happening it was a weeks ago, and I thought I was being effected by this bug. But it got resolved and I was still having the issue, even earlier today when I upgraded an old jail.

Edit: Yes — this works, without changing the repository.

No error about repositories. Nothing to update at this point since I’m back to the normal quarterly repo, but I think we’ll be fine.
Thanks for helping me look at this further. I was afraid I would have to remake every jail I have (which I’ve already done with my Plex jail now).

Источник

PKG ERROR

coutter

When trying to run
pkg update && pkg upgrade -y
I get this error:
I tried several methods to solve this and none of them worked out. I’m kinda lost here.

SirDice

Administrator

The entire 10 branch is end-of-life and not supported any more.

Unsupported FreeBSD Releases

jimeha

Deleted member 66267

Guest

I don’t know if anything like that exists. The only thing that works is pkgsrc, which is designed just for this: continue the life of legacy systems!

pkgsrc

jimeha

Apologies for the delayed reply, life in the way. So for much older versions we still have ftp-archive.freebsd.org for versions 1.x through 9.x (on i386) and 5.x ot 9.x (on amd64). But on pkg.freebsd.org, 10.x has been wiped, so now we have a gap then 11+? I would’ve hoped FreeBSD would keep this available on some archive server, just like the older versions. That’s very unfortunate.

I glanced at pkgsrc, but that does seem to involve having to build all of ports at least once, or a portion of it if we want to be able to do final updates to our BSD 10.x systems, before they eventually migrate to 12.x or newer. Is there really no pkg archive of 10.x? Will 1.x through 9.x eventually disappear too then if the move is to only ‘new’ supported stuff to be available from pkg?

zirias@

Cause EOL always hits you like lightning in a clear sky, right?

Operating EOL systems is dangerous, you should never do it, so there’s no point in providing any support for shooting your foot. You can always fetch ports trees from ages ago and build yourself what you need if you insist, but the only sane way is: upgrade.

Reactions: Deleted member 30996

SirDice

Administrator

Those never existed.

There are archives of the releases. Some of those included packages. But they are packages that were built at the time of the release (you could find those included on the CD/DVD images). They are not the ‘last’ builds of that release.

T-Daemon

SirDice

Administrator

zirias@

T-Daemon

jimeha

Those never existed.

There are archives of the releases. Some of those included packages. But they are packages that were built at the time of the release (you could find those included on the CD/DVD images). They are not the ‘last’ builds of that release.

My fault that one; bad comparison then. I suppose a portion of my argument is also for consistency. One could, in theory (not recommended, yes, I know), install an older FreeBSD version right now and set PACKAGESITE to ftp-archive.freebsd.org so pkg_add et al work. Currently, I see no way to do that with, for example, FreeBSD 10.x and pkg without building ports and pointing pkg at that after setting up a frontend to my internal builds that were built and packaged nicely. The pkg.freebsd.org system just doesn’t have FreeBSD:10:amd64 (released or latest) and others anymore, only supported 12.x, etc, releases. This seems like a miss in consistency vs older FreeBSD versions unless this new practice for maintaining pkg.freebsd.org is posted somewhere I haven’t found yet which is entirely possible.

Zirias absolutely agree with your overall premise: 100% use new *supported* releases when possible. Badger those who ‘need’ the old systems to upgrade. However, I’m sure I’m not the only one trying to maintain an old server though for «reasons» by attempting to patch in the very last released builds of a package(s) as an attempt to update it ‘a little bit’ before that OS upgrade oppotunity comes. I had managed to upgrade several before FreeBSD:10:amd64 disappeared, was going to do more of them, but can’t.

Источник

How To Upgrade To FreeBSD 13 From FreeBSD 12

A Step By Step Guide To Upgrade FreeBSD 12.x To FreeBSD 13.1

FreeBSD 13.1 stable version is officially released. This tutorial walks you through the steps to upgrade to FreeBSD 13.1 from FreeBSD 12.3 and older versions.

Introduction

The FreeBSD Release Engineering Team is recently announced the availability of FreeBSD 13.1-RELEASE. This is the second release of the stable/13 branch.

FreeBSD 13.1 is shipped with many updated set of features. It supports several architectures including amd64, i386, powerpc, powerpc64, powerpc64le, powerpcspe, armv6, armv7, aarch64, and riscv64.

If you prefer a fresh installation, head over to the FreeBSD 13.1 download page and get a suitable version for your architecture. And then refer to the following guide to know how to install FreeBSD.

If you’re already running older versions (E.g. FreeBSD 12.x), you can directly upgrade FreeBSD 12.x to FreeBSD 13.1. In this step by step guide, let us see how to upgrade to FreeBSD 13.1 from FreeBSD 12.3 version.

Update FreeBSD 12

First things first. Take a backup of everything that you can’t afford losing. FreeBSD upgrade process worked just fine in my case. However, I strongly recommend you to backup your data.

Let us now go ahead and update the current FreeBSD version.

Check FreeBSD OS version and kernel version using commands:

Sample output:

Sample output:

As you see above, the installed version is FreeBSD 12.3-RELEASE.

Before upgrading to next available major version, we must update our current FreeBSD 12.x version.

To download and install the FreeBSD security patches, run the following commands as root user:

Once the packages are upgraded, reboot your system:

It is time to upgrade FreeBSD 12 to FreeBSD 13.

Upgrade To FreeBSD 13 From FreeBSD 12

As of writing this guide, the latest stable FreeBSD version 13.1.

Run the following command to upgrade to FreeBSD 13.1-RELEASE from FreeBSD 12.x version:

Once you run this command, the freebsd-update command will evaluate the configuration file and current system in an attempt to gather the information necessary to perform the upgrade.

During the upgrade, you will be asked what to install, what to remove or how to proceed. You may need to type y and hit ENTER a few times to continue.

Sample output:

The above command will start to download all packages. Sit back and relax. It will take several minutes depending upon the Internet speed and the number of installed packages on your FreeBSD system.

During the upgrade task, Configuration files will then be merged. The results of every successful merge will be shown to the user as the process continues.

Please note that the current system is not being altered yet, because all merging and patching is happening in another directory.

Once all patches have been applied successfully, all configuration files have been merged, run the following command to commit all changes to the disk:

Sample output:

All Kernel updates have been installed in your FreeBSD, reboot your system to apply the patches.

After logging into the system, run the following command again to finish installing updates:

After all updates are installed, you will see the following output:

Once again the run the same command to remove old shared libraries and complete FreeBSD 13.1 upgrade task.

Finally, reboot your system to complete the upgrade task.

Verify if FreeBSD 13.1 is upgraded successfully by checking the OS version.

And check the FreeBSD Kernel version:

Congratulations! We just upgraded to FreeBSD 13.1.

We need to do one more thing as well. After a major version upgrade, all installed packages and ports should be upgraded.

Update all installed packages and ports collections using the following commands:

That’s it. Reboot once again and start using FreeBSD version.

Troubleshooting Pkg Update Error In FreeBSD

After upgrading to FreeBSD 13, I got the following error when I try to update the ports collections:

This usually happens when we upgrade 12.0 to 12.1 or 2.

To fix this issue, update ports-mgmt/pkg from the ports tree using ports-mgmt/portmaster .

Fetch the ports tree using commands if you haven’t done it already:

Sample output:

Next run the following command to download and extract the entire ports tree to the /usr/ports directory.

This usually happens when we do minor upgrade i.e. 12.0 to 12. After running pkg bootstrap -f everything worked as expected.

Change Hostname (Optional)

I used to set the hostname to any Linux or Unix systems with the operating system’s version. For instance, I will usually set name as «freebsd12» for FreeBSD 12 systems. If you’re anything like me, you should update your hostname to reflect the current version.

As root user, type «hostname «, and the hostname will be changed immediately.

Replace «freebsd13.ostechnix.lan» with your own hostname.

To make this change permanent across reboots, edit the file » /etc/rc.conf » using a text editor:

Add/modify the following line:

Reboot your system to take effect the changes.

Check if the hostname is changed with command:

Perfect! Start using your FreeBSD 13.1 system!!

Источник

FreeBSD 13.1 stable version is officially released. This tutorial walks you through the steps to upgrade to FreeBSD 13.1 from FreeBSD 12.3 and older versions.

Introduction

The FreeBSD Release Engineering Team is recently announced the availability of FreeBSD 13.1-RELEASE. This is the second release of the stable/13 branch.

FreeBSD 13.1 is shipped with many updated set of features. It supports several architectures including amd64, i386, powerpc, powerpc64, powerpc64le, powerpcspe, armv6, armv7, aarch64, and riscv64.

If you prefer a fresh installation, head over to the FreeBSD 13.1 download page and get a suitable version for your architecture. And then refer to the following guide to know how to install FreeBSD.

Install FreeBSD — Step By Step Guide

If you’re already running older versions (E.g. FreeBSD 12.x), you can directly upgrade FreeBSD 12.x to FreeBSD 13.1. In this step by step guide, let us see how to upgrade to FreeBSD 13.1 from FreeBSD 12.3 version.

Update FreeBSD 12

First things first. Take a backup of everything that you can’t afford losing. FreeBSD upgrade process worked just fine in my case. However, I strongly recommend you to backup your data.

Let us now go ahead and update the current FreeBSD version.

Check FreeBSD OS version and kernel version using commands:

# freebsd-version -k

Sample output:

12.3-RELEASE

$ uname -mrs

Sample output:

FreeBSD 12.3-RELEASE amd64

As you see above, the installed version is FreeBSD 12.3-RELEASE.

Before upgrading to next available major version, we must update our current FreeBSD 12.x version.

To download and install the FreeBSD security patches, run the following commands as root user:

# freebsd-update fetch

# freebsd-update install

# pkg upgrade

Once the packages are upgraded, reboot your system:

# shutdown -r now

Or,

# reboot

It is time to upgrade FreeBSD 12 to FreeBSD 13.

Upgrade To FreeBSD 13 From FreeBSD 12

As of writing this guide, the latest stable FreeBSD version 13.1.

Run the following command to upgrade to FreeBSD 13.1-RELEASE from FreeBSD 12.x version:

# freebsd-update -r 13.1-RELEASE upgrade

Once you run this command, the freebsd-update command will evaluate the configuration file and current system in an attempt to gather the information necessary to perform the upgrade.

During the upgrade, you will be asked what to install, what to remove or how to proceed. You may need to type y and hit ENTER a few times to continue.

Sample output:

 src component not installed, skipped
 Looking up update.FreeBSD.org mirrors… 2 mirrors found.
 Fetching metadata signature for 12.3-RELEASE from update1.freebsd.org… done.
 Fetching metadata index… done.
 Fetching 1 metadata files… done.
 Inspecting system… done.
 The following components of FreeBSD seem to be installed:
 kernel/generic kernel/generic-dbg src/src world/base world/base-dbg world/doc
 world/lib32 world/lib32-dbg
 The following components of FreeBSD do not seem to be installed:
 Does this look reasonable (y/n)? y
 Fetching metadata signature for 13.1-RELEASE from update2.freebsd.org… done.
 Fetching metadata index… done.
 Fetching 1 metadata patches. done.
 Applying metadata patches… done.
 Fetching 1 metadata files… 
[...]

The above command will start to download all packages. Sit back and relax. It will take several minutes depending upon the Internet speed and the number of installed packages on your FreeBSD system.

During the upgrade task, Configuration files will then be merged. The results of every successful merge will be shown to the user as the process continues.

Please note that the current system is not being altered yet, because all merging and patching is happening in another directory.

Once all patches have been applied successfully, all configuration files have been merged, run the following command to commit all changes to the disk:

# freebsd-update install

Sample output:

ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Installing updates…
Kernel updates have been installed.  Please reboot and run
"/usr/sbin/freebsd-update install" again to finish installing updates.

All Kernel updates have been installed in your FreeBSD, reboot your system to apply the patches.

After logging into the system, run the following command again to finish installing updates:

# freebsd-update install

After all updates are installed, you will see the following output:

[...]
Completing this upgrade requires removing old shared object files.
Please rebuild all installed 3rd party software (e.g., programs
installed from the ports tree) and then run "/usr/sbin/freebsd-update install"
again to finish installing updates.

Once again the run the same command to remove old shared libraries and complete FreeBSD 13.1 upgrade task.

# freebsd-update install

Finally, reboot your system to complete the upgrade task.

Verify if FreeBSD 13.1 is upgraded successfully by checking the OS version.

# freebsd-version -k
13.1-RELEASE

And check the FreeBSD Kernel version:

# uname -mrs
FreeBSD 13.1-RELEASE amd64

Congratulations! We just upgraded to FreeBSD 13.1.

We need to do one more thing as well. After a major version upgrade, all installed packages and ports should be upgraded.

Update all installed packages and ports collections using the following commands:

# pkg-static install -f pkg

# pkg bootstrap -f

# pkg update

# pkg upgrade -y

That’s it. Reboot once again and start using FreeBSD version.

Troubleshooting Pkg Update Error In FreeBSD

After upgrading to FreeBSD 13, I got the following error when I try to update the ports collections:

 pkg-static: Warning: Major OS version upgrade detected.  Running "pkg-static install -f pkg" recommended
 Updating FreeBSD repository catalogue…
 pkg-static: repository meta has wrong version 2
 pkg-static: Repository FreeBSD load error: meta cannot be loaded No error: 0
 Fetching meta.txz: 100%    916 B   0.9kB/s    00:01    
 pkg-static: repository meta has wrong version 2
 repository FreeBSD has no meta file, using default settings
 Fetching packagesite.txz: 100%    6 MiB   1.6MB/s    00:04    
 pkg-static: repository meta has wrong version 2
 pkg-static: Repository FreeBSD load error: meta cannot be loaded No error: 0
 Unable to open created repository FreeBSD
 Unable to update repository FreeBSD
 Error updating repositories!

This usually happens when we upgrade 12.0 to 12.1 or 2.

To fix this issue, update ports-mgmt/pkg from the ports tree using ports-mgmt/portmaster.

Fetch the ports tree using commands if you haven’t done it already:

# portsnap fetch

Sample output:

 Looking up portsnap.FreeBSD.org mirrors… 4 mirrors found.
 Fetching public key from ipv4.aws.portsnap.freebsd.org… done.
 Fetching snapshot tag from ipv4.aws.portsnap.freebsd.org… done.
 Fetching snapshot metadata… done.
 Fetching snapshot generated at Sat May 28 05:59:31 IST 2022:
 552628c35b88d79f5a54b7774ddca0463fde713e43f367          88 MB 3233 kBps    28s
 Extracting snapshot… done.
 Verifying snapshot integrity… done.
 Fetching snapshot tag from ipv4.aws.portsnap.freebsd.org… done.
 Fetching snapshot metadata… done.
 Updating from Sat May 28 05:59:31 IST 2022 to Sat May 28 17:23:31 IST 2022.
 Fetching 5 metadata patches… done.
 Applying metadata patches… done.
 Fetching 0 metadata files… done.
 Fetching 18 patches. 
 (18/18) 100.00%  done.                             
 done.
 Applying patches… 
 done.
 Fetching 0 new ports or files… done.

Next run the following command to download and extract the entire ports tree to the /usr/ports directory.

# portsnap extract

And then run:

# pkg bootstrap -f

# pkg update -f

# pkg upgrade -f

This usually happens when we do minor upgrade i.e. 12.0 to 12. After running pkg bootstrap -f everything worked as expected.

Change Hostname (Optional)

I used to set the hostname to any Linux or Unix systems with the operating system’s version. For instance, I will usually set name as «freebsd12» for FreeBSD 12 systems. If you’re anything like me, you should update your hostname to reflect the current version.

As root user, type «hostname <new hostname>», and the hostname will be changed immediately.

# hostname freebsd13.ostechnix.lan

Replace «freebsd13.ostechnix.lan» with your own hostname.

To make this change permanent across reboots, edit the file «/etc/rc.conf» using a text editor:

# vi /etc/rc.conf

Add/modify the following line:

hostname="freebsd13.ostechnix.lan"

Reboot your system to take effect the changes.

Check if the hostname is changed with command:

# hostname
freebsd13.ostechnix.lan

Perfect! Start using your FreeBSD 13.1 system!!

Related read:

• How To Enable SSH On FreeBSD

If its minor upgrade it will just install upgrades and most like you would not need to rebuild packages. In case you get below msg follow next steps just like a major upgrade.

For major upgrade you will need to rebuild packages and follow next steps:

Installing updates...
Completing this upgrade requires removing old shared object files.
Please rebuild all installed 3rd party software (e.g., programs
installed from the ports tree) and then run "/usr/sbin/freebsd-update install"
again to finish installing updates.

# pkg-static install -f pkg

Possible problem:

pkg: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2
pkg: Repository FreeBSD load error: meta cannot be loaded No error: 0

Solution would be deleting the pkg and reinstalling:
# pkg delete -f pkg
# pkg update -f pkg

or

# pkg-static install -f pkg

This will re install pkg then

# pkg update
# pkg upgrade
# freebsd-update install

In case you run out of space during these upgrades (if you are doing couple of minor upgrades one by one) you can remove downloaded packages located under:

/var/db/freebsd-update/files/

if you are deleting with rm command

# rm -f *.gz

you can get below error

# /bin/rm: Argument list too long

to see max arg conf in your system you can run # getconf ARG_MAX

You can use below command to overcome this problem, just dont forget you need to be in /var/db/freebsd-update/files/ directory

# find . -type f -exec rm -v {} ;

if you want to delete specific extension

# find . -maxdepth 1 -name "*.gz" -print0 | xargs -0 rm

Also if your default shell is anything other then sh another possible problem you would face would be broken shell. You would get a error something like:

Shared object "libdl.so.1" not found, required by "bash"

And your connection will clode or you wont be able to login system. In this case you need to boot to single usermode (click ‘s’ on boot) and change your default shell:

If you’re using UFS:

# mount -uw /

On ZFS you’d use:

# zfs set readonly=off zroot/DEFAULT/root

Then fix your shell:

# pw usermod root -s /bin/csh
or
# pw usermod root -s /bin/sh

Or use:
# chsh
and edit your profile file and fix the shell entry