Re: pkg_rolling-replace issue with non-installed package

[Riccardo Mottola <riccardo.mottola%libero.it@localhost>]

Hi,

Greg Troxel wrote:
> yes, it's ok not to have build deps installed.

In theory... what I found that sometimes they are not pulled in, 
apparently it thinks they are there, even if pkg_info doesn't show them 
nor are the file there.


> For a shell script, you can
>
> sh -x /path/to/script
>
> and it prints a trace of what it is doing.  Reading the man page, it's
> more complicated, and you might want to add "set -x" as an early extra
> line in the script.

Sorry, didn't understand that you meant that, but an argument to pkg_rr 
... my mistake.
I went over this using a "hammer".

> The problem is that pkg_rr is somehow finding meson as a dependency, btu
> not finding it installed.  That may be a pkg_rr bug and it may be a
> messed up database.  You are the first report.

For some packages I had an error in "make replace" that checksum did not 
match what it is, wonder.

> Just do 'make replace clean' in glib2, and that will likely build and
> install meson, and then you can run again.

for that and a couple of other packages I had issue it I went on 
installing the missing package, then setting it as "automatic=YES"
Some package built but failed to install/replace. But I could just 
"pkg_add" the created binary, getting some complaints.
Most other packages went on fine though. Once a couple of packages were 
replaced manually, pkg_rr started working and it is churning out updates.
If it stop, I fix/replace that package, then reissue it again.

All with the times of the old SparcStation 20, but have over 60 packages 
rebuilt now!

Riccardo