Solved pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64

[JAW]

I'm sorry to be dense, what exactly is the process for fixing this issue on the user end? Just wait? Try `pkg update -f` every day until the error no longer appears?

Latest packages 12.1-amd64
https://pkg-status.freebsd.org/builds/default:default:121amd64:527609:beefy6

It'll be finished at ~32533 packages built, as of posting it's at 27053.

 

[SaMaeL]

Hi,

After struggling a bit with the same issue I found a workaround that may help people running into this problem.

# ALTABI=FreeBSD:13.0:amd64 pkg-static update -f
# ALTABI=FreeBSD:13.0:amd64 pkg-static upgrade -f pkg

You obviously need to adapt this command to your version (12.0 ...) if not running current.

 

[acheron]

It's fixed.

 

[eternal_noob]

It's fixed.

No:

root@xxx:~ # pkg update -f
Updating FreeBSD repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01   
Fetching packagesite.txz: 100%    6 MiB   6.4MB/s    00:01   
Processing entries:  64%
pkg: wrong architecture: FreeBSD:12.0:i386 instead of FreeBSD:12:i386
pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:i386
Processing entries: 100%
Unable to update repository FreeBSD
Error updating repositories!

 

[skillcoder]

$ sudo pkg install go
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%    916 B   0.9kB/s    00:01
Fetching packagesite.txz: 100%    6 MiB 195.6kB/s    00:33
Processing entries:  63%
pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64
pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:amd64
Processing entries: 100%
Unable to update repository FreeBSD
Error updating repositories!

$ sudo pkg install go
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        go: 1.13.5,1 -> 1.13.7,1

Number of packages to be upgraded: 1

75 MiB to be downloaded.

Proceed with this action? [y/N]: y
pkg: http://pkg.FreeBSD.org/FreeBSD:12:amd64/latest/All/go-1.13.7,1.txz: Not Found

 

[Oriann]

It's fixed.

Build for latest is still at 99% stucked, we have to wait until finished because updating packages downloads list of all packages. Quarterly still rebuilding tho at 81%

 

[gnath]

Output from pkg search go is go-1.14,1. The terget URL also have same version. Somewhere it got mixed up. Delete all pkg's and then install from list fresh. There is nothing like 10.0, 11.0 & 12.0.

 

[acheron]

Yeah, sorry, it's fixed on -head.

 

[Oriann]

Yeah, sorry, it's fixed on -head.

As of 05.03.2020 05:05 PM i still got the error

root@nas:~ # pkg update
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%    916 B   0.9kB/s    00:01
Fetching packagesite.txz: 100%    6 MiB 174.4kB/s    00:37
Processing entries:  63%
pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64
pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:amd64
Processing entries: 100%
Unable to update repository FreeBSD
Error updating repositories!

 

[jimbo]

What is happening? I still can't do a pkg update -f
Any news?

 

[SirDice]

Quarterly for 12.1 AMD64 is still building: https://pkg-status.freebsd.org/builds?jailname=121amd64

Latest for 12.1 AMD64 should be finished though.

 

[jimbo]

I should be on latest but I'm still getting the error :-(

FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest"
}

What am I doing wrong?

 

[Emrion]

I should be on latest but I'm still getting the error :-(

FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest"
}

What am I doing wrong?

Nothing, it actually doesn't work on latest for the moment.

 

[rootbert]

did anyone of the responsible persons take note about this? any hints on mailing lists, or did somebody of the forums notify someone?

 

[Alexander88207]

PR 244549

 

[Emrion]

It works now on latest. It was just a matter of time.

 

[tedbell]

I am on lastest (amd64) and I cannot access pkg or freebsd-update.

 

[eternal_noob]

Latest for i386 doesn't work yet.

 

[Oriann]

Latest for amd64 doesn't work yet either...

 

[jimbo]

Latest still doesn't work for me either, on amd64 as well :-(

 

[elscripto]

It appears that an emergency fix could have been done in minutes, instead a fix for a week time has been chosen.
Disappointing attitude and questionable quality support for an OS.

 

[Emrion]

Actually, the amd64 latest is gone since yesterday. It has worked, though.

It appears that an emergency fix could have been done in minutes, instead a fix for a week time has been chosen.
Disappointing attitude and questionable quality support for an OS.

You forgot "for a free OS"... Maybe you should become commiter?

 

[Alberto B.]

Now work?
Becuase i still have the error. I only want to understand if is my problem or not.
Thanks

 

[Oriann]

Actually, the amd64 latest is gone since yesterday. It has worked, though.


You forgot "for a free OS"... Maybe you should become commiter?

Sure its free, but realize that we use pkgs for production and that is a very big challenge when you are stuck with low system and building ports takes ages to complete. Free or not this is critical issue for all.

But as far I know sometimes searching for root issue is bit more quest for an achievement

 

[SirDice]

I only want to understand if is my problem or not.

The issue is not on your end. It was caused by a bug in the packaging system and unfortunately resulted in all packages having the "bad" ABI string. The issue itself has been resolved but now we have to wait until all packages have been rebuilt.