Date: Thu, 05 Mar 2020 09:51:50 +0100 From: Evilham <contact@evilham.com> To: freebsd-questions@freebsd.org Subject: Re: pkg error Message-ID: <d8d0c041-39de-4313-9aab-2a4af837f56d@yggdrasil.evilham.com> In-Reply-To: <af826591-5957-4efa-8572-1c1f0bdd3e83@fastmail.com> References: <20200305065608.GB6019@foucry.net> <af826591-5957-4efa-8572-1c1f0bdd3e83@fastmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On dj., mar=C3=A7 05 2020, Yuri Pankov wrote:
> On 05.03.2020 09:56, Jacques Foucry wrote:
>> Hello folks,
>>
>> I recently upgrade my laptop from 12.1-RELEASE-p1 to=20
>> 12.1-RELEASE-p2 add it
>> seems something went wrong. When I try to install a new pkg I=20
>> got an error:
>>
>> [1/3] Fetching enigma-1.21.txz: 100% 52 MiB 621.8kB/s=20
>> 01:27
>> pkg: cached package enigma-1.21: size mismatch, fetching from=20
>> remote
>> [2/3] Fetching enigma-1.21.txz: 100% 52 MiB 693.5kB/s=20
>> 01:18
>> pkg: cached package enigma-1.21: size mismatch, cannot continue
>> Consider running 'pkg update -f'
>>
>> pkg update -f run an error too:
OTOH this hint to run 'pkg update -f' is pretty awesome :-D.
That's a whole class of questions that will never happen again \o/=20
("what does size mismatch, cannot continue mean?").
>>
>> Updating FreeBSD repository catalogue...
>> Fetching meta.conf: 100% 163 B 0.2kB/s 00:01
>> Fetching packagesite.txz: 100% 6 MiB 806.6kB/s 00:08
>> Processing entries: 63%
>> pkg: wrong architecture: FreeBSD:12.0:amd64 instead of=20
>> FreeBSD:12:amd64
>> pkg: repository FreeBSD contains packages with wrong ABI:=20
>> FreeBSD:12.0:amd64
>> Processing entries: 100%
>> Unable to update repository FreeBSD
>> Error updating repositories!
>>
>> Seems there is still olds references of package from 12.0
>>
>> I tried pkg check, pkg cache, etc but the error is still there.
>>
>> Any advice are welcome.
>>
>> Thanks in advance,
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244549
>
> TL;DR: it's being worked on and new builds are already in=20
> progress (AFAIK).
This was already solved for 13-current yesterday IIRC and indeed=20
it looks like it's working fine on 12.1-release for me now.
--
Evilham
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d8d0c041-39de-4313-9aab-2a4af837f56d>