Re: Fwd: Re: php and pkgin

[Fekete Zoltán <fekete.zoltan%minux.hu@localhost>]

Ekkor: 2025. április 9. 14:23:05 CEST, "Fekete Zoltán" <fekete.zoltan%minux.hu@localhost> írta:
>2025-04-09 14:03 időpontban Jonathan Perkin ezt írta:
>> * On 2025-04-09 at 12:55 BST, Fekete Zoltán wrote:
>> 
>>> pkgin list however, did:
>>> bash-5.2# pkgin list | grep php
>>> php-8.1.31           PHP Hypertext Preprocessor version 8.1
>>> bash-5.2# pkg_delete php
>>> pkg_delete: No matching package for basename `php' of `php'
>>> bash-5.2# pkg_delete php-8.1.31
>>> pkg_delete: No matching package for basename `php-8.1.31' of `php-8.1.31'
>>> bash-5.2#
>> 
>> It's unclear how you can get into this state.  One of the first things that pkgin does on every invocation is check that its database is in sync with the pkgdb, and if the mtime of the pkgdb has changed then it will force a refresh.  Clearly here they are not in sync.
>> 
>> I'm certainly very interested in any test cases that can reproduce this.
>
>My usual workflow is just running pkgin up && pkgin ug && pkgin fug
>
>However at this time I had a problem with my bulkbuild process which I used to run on another build machine.
>I have pulled pkgsrc-2025Q1 from the pkgsrc git repo, then started the bulkbuild in the sandbox environment as usually.
>When the process has finished, I ran the commands above. Then experienced some weirdness in the output, not remember what exactly.
>I figured out, that bulkbuild had problem. I fixed that, and ran these commands again. And here we are.
>I assume bulkbuild has updated the packages_list also in the first run, where php might have been missing. Then, in the 2nd run it updated again, now it contained the corresponding, already newer php packages. Somewhere after the first run, when I synced with the packages_list without php, the old php version information has lost.
>At least this is my rough imagination what could happen.
>
>FeZ

So, does anybody have an idea how to proceed from here?

FeZ