Friday, November 01, 2019

Re: Following current - pkg_add update forward depedencies don't match question

On Thu, Oct 31, 2019 at 07:09:49PM -0500, Theodore Wynnychenko wrote:
> Hello
>
> I just updated a system to current the other day.
>
> OpenBSD 6.6 GENERIC.MP#411 amd64
> When I check:
> # pkg_info | grep gettext
> gettext-0.19.8.1p3 GNU gettext runtime libraries and programs
>
> And the mirror shows:
> gettext-runtime-0.20.1p0.tgz
>
> Or (another example), with similar notices about forward dependencies not
> matching:
> # pkg_info | grep php-7
> php-7.1.27 server-side HTML-embedded scripting language
>
> And the mirror shows:
> php-7.1.32.tgz
>
> I see that I can "force" the update with "pkg_add -u -D updatedepends".
>

NO. You need to use pkg_add -u -Dsnap.
Or, the packages really don't match yet. Then wait a little. -Dsnap is a
must. Some snapshots are also "defective" as in trying some new stuff
that will get changed more later. Upgrade again.

Occasionally you might need to use sysupgrade -s. That happened to me
from one -current to another.

If you genuinely need stability, then run -stable.

-current makes changes to the C libraries and headers and then
recompiles the packages. The packages are the same but C, etc. has
changed. Thus the packages have changed on that level. Thus they keep
the same Makefiles, but the resulting package binaries are different.

Chris Bennett


> It seems like this should be safe to do, but it's not something I have done
> before.
>
> While my system isn't "production" for a large multi-national, I do use it
> as a file server and stuff, and it is working right now, and I don't want to
> make it not work.
>
> So, before I did this, I was wondering if there was anything I should
> consider/do to address this issue, other than just "forcing" the update?
>
> I guess, when at its core, I don't really completely understand what the
> notice means, and how and why it happened.
>
> Thanks
> Ted
>
>
>

No comments:

Post a Comment