Re: pkg-2.4.1 broken?

On 11/4/25 3:23 PM, Baptiste Daroussin wrote:
> On Tue 04 Nov 15:18, Jan Henrik Sylvester wrote:
>> # pkg delete -f pkg
>> ...
>> # ../pkg-static add pkg-2.4.1.pkg
>> pkg-static: pkg-2.4.1.pkg is not a valid package: no manifest found
>>
>> This is on 14.3-RELEASE/amd64. pkg-2.4.1.pkg was created on a different
>> machine using 'pkg create pkg-2.4.1' after upgrading pkg from 2.3.1_1 to
>> 2.4.1 using portmaster. pkg-static is also copied from that machine.
>>
>> I can still install pkg-2.3.1_1.pkg with the same pkg-static. I only get:
>>
>> pkg: warning: database version 37 is newer than libpkg(3) version 36, but
>> still compatible
>>
>> Besides that warning, everything seems to work with pkg-2.3.1_1.
>>
>> I know that portmaster is not really recommended anymore and using
>> pkg-static to install pkg is probably not the best way, either. Anyhow, it
>> used to work and it should work from my understanding.
>>
>> Best,
>> Jan Henrik
>>
> 
> I would need more output that what you show.
> 
> How was your pkg-2.4.1.pkg created? can you host it somewhere to I can analyse.

Thanks for your quick reply.

As I said, it was created on another machine using 'pkg create 
pkg-2.4.1', but you made me recheck the log. Previously, I failed to 
spot the following. Sorry.

pkg: dir '/usr/local/lib/compat/pkg' is missing
pkg: package creation failed

Hence, I could have known that the package is broken before I copied it 
to another machine.

I think it is simply an empty tar archive: https://janh.de/tmp/pkg-2.4.1.pkg

After creating /usr/local/lib/compat/pkg manually, I was able to 
recreate a working package.

That /usr/local/lib/compat/pkg was missing seems to be a bug in 
portmaster, which was used to upgrade pkg-2.3.1_1 to pkg-2.4.1, because 
when I do 'pkg delete -f pkg' and 'make -C /usr/ports/ports-mgmt/pkg 
install clean' the directory is created correctly. I guess I should 
learn that portmaster really is an outdated method to upgrade.

Best,
Jan Henrik