> On 10 Sep 2024, at 5:37 pm, Stuart Henderson <stu@spacehopper.org> wrote:
> 
> On 2024/09/10 17:25, Ian McWilliam wrote:
>> 
>> 
>>> On 10 Sep 2024, at 4:35 pm, Stuart Henderson <stu@spacehopper.org> wrote:
>>> 
>>> On 2024/09/10 11:52, Ian McWilliam wrote:
>>>> Hi,
>>>> 
>>>> 
>>>> After testing an update from 7.5-stable to a current snapshot I see that 
>>>> 
>>>> net/rsnapshot                  # @rsync-3.2.7p1 -> @rsync-3.3.0p2
>>>> 
>>>> doesn’t update without manual intervention.
>>>> 
>>>> Any chance of a pkg version bump so that it updates correctly?
>>> 
>>> What is there to update? rsnapshot hasn't changed since 2022 and there's
>>> no detection of rsync version in the autoconf script so should be no
>>> change in the package.
>>> 
>> 
>> Obviously nothing except the listed run deps gets out of sync, doesn’t stop it from working. I can live with manually updating it each release.
> 
> You're reading more into the @depend line than is actually there -
> looking at a fresh pkg_add:
> 
> @depend net/rsync:rsync-*:rsync-3.3.0p2
> 
> The run dep is on any rsync-* package. The version number just shows
> which version was installed when the package was built.
> 
> If your aim is to replace all packages with fresh ones whether they
> need it or not, you can use -D installed, but it's more helpful not to
> do that (except in an emergency) as using that means you won't find
> out about any real missed bumps (i.e. where a depended-on package
> changed in an incompatible way that is picked up by autoconf etc
> to trigger changes in the build).


My main reason for checking to make sure packages with libs were updated correctly not leaving any old packages with old libc, etc installed. This just happened to show up. Thanks for the explanation.

Ian McWilliam