> -----Original Message-----
> From: owner-misc@openbsd.org [mailto:owner-misc@openbsd.org] On Behalf
> Of Stuart Henderson
> Sent: Saturday, November 02, 2019 4:12 AM
> To: misc@openbsd.org
> Subject: Re: Following current - pkg_add update forward depedencies
> don't match question
>
> On 2019-11-01, Theodore Wynnychenko <tmw@uchicago.edu> wrote:
> > Hello
> >
> > I just updated a system to current the other day.
> >
> > OpenBSD 6.6 GENERIC.MP#411 amd64
> >
> > The last time I updated was probably 2-3 months ago.
> >
> > Anyway, when I went to updated packages (also following
> current/snapshots),
> > I got a number of "forward dependencies - don't match" notices and
> the
> > packages don't update.
>
> What command are you running to update?
>
> The "don't match" are expected but (at least with "pkg_add -u" without
> restricting to a subset of packages) it shouldn't stop packages from
> updating anyway.
>
> Can you show the pkg_add command line you're using and complete output?
> i.e. run it under script(1) and send the typescript.
>
> This doesn't match "probably 2-3 months ago", php 5.6 and the
> associated
> pecl packages were removed before 6.5, and php-7.1.27 was from
> somewhere
> between 6.4 and 6.5. Not that this matters in itself, an update over
> that time period would still be expected to work, but if you're
> going to be updating infrequently you should definitely stick to
> releases+syspatch rather than -current.
>
Sorry, it was probably longer than "2-3 months." Life got in the way. I
should do better going forward, and I understand that going "back" to
release from current can be problematic.
In any case, I wanted to describe my "experience" with this issue. I will
try to be brief.
Yesterday afternoon, I noticed that the timestamps for packages had updated.
So, I tried again (on another system where "breaking" is less
consequential).
I decided to just try updating gettext, so (this is the full output on that
system):
# PKG_PATH=https://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/
pkg_add -u -Dsnap gettext
quirks-3.184 signed on 2019-11-01T17:28:51Z
.libs1-gettext-0.19.4p0+gettext-0.19.8.1p3->gettext-runtime-0.20.1p0 forward
dependencies:
| Dependencies of python-2.7.16 on gettext-* don't match
| Dependencies of python-3.6.8p0 on gettext-* don't match
| Dependencies of libidn-1.35 on gettext-* don't match
| Dependencies of glib2-2.58.3p8 on gettext-* don't match
| Dependencies of wget-1.20.2 on gettext-* don't match
| Dependencies of libpsl-0.20.2 on gettext-* don't match
| Dependencies of libgpg-error-1.36 on gettext-* don't match
| Dependencies of monitoring-plugins-2.2p7 on gettext-* don't match
Merging python-2.7.16->2.7.16p1 (ok)
NOT MERGING: can't find update for [python-3.6.8p0] (ok)
Merging libidn-1.35->1.35p0 (ok)
Merging glib2-2.58.3p8->2.60.7 (ok)
Merging wget-1.20.2->1.20.3p1 (ok)
Merging libpsl-0.20.2->0.20.2p0 (ok)
Merging libgpg-error-1.36->1.36p0 (ok)
Merging monitoring-plugins-2.2p7->2.2p8 (ok)
Proceed with update anyway ? [y/N/a] y
Detected loop, merging sets ok
| python-3.7.5
|
.libs1-gettext-0.19.4p0+gettext-0.19.8.1p3+glib2-2.58.3p8+libgpg-error-1.36+
libidn-1.35+libpsl-0.20.2+monitoring-plugins-2.2p7+python-2.7.16+wget-1.20.2
->gettext-runtime-0.20.1p0+glib2-2.60.7+libgpg-error-1.36p0+libidn-1.35p0+li
bpsl-0.20.2p0+monitoring-plugins-2.2p8+python-2.7.16p1+wget-1.20.3p1
[python-3.6.8p0].libs-glib2-2.56.1+.libs-libidn-1.34+.libs-libpsl-0.7.1p1+.l
ibs1-gettext-0.19.4p0+gettext-0.19.8.1p3+glib2-2.58.3p8+libgpg-error-1.36+li
bidn-1.35+libpsl-0.20.2+monitoring-plugins-2.2p7+python-2.7.16+wget-1.20.2->
gettext-runtime-0.20.1p0+glib2-2.60.7+libgpg-error-1.36p0+libidn-1.35p0+libp
sl-0.20.2p0+monitoring-plugins-2.2p8+python-2.7.16p1+python-3.7.5+wget-1.20.
3p1 forward dependencies:
| Dependencies of python-3.6.8p0 on gettext-* don't match
Proceed with update anyway ? [y/N/a] y
Can't install
[python-3.6.8p0].libs-glib2-2.56.1+.libs-libidn-1.34+.libs-libpsl-0.7.1p1+.l
ibs1-gettext-0.19.4p0+gettext-0.19.8.1p3+glib2-2.58.3p8+libgpg-error-1.36+li
bidn-1.35+libpsl-0.20.2+monitoring-plugins-2.2p7+python-2.7.16+wget-1.20.2->
gettext-runtime-0.20.1p0+glib2-2.60.7+libgpg-error-1.36p0+libidn-1.35p0+libp
sl-0.20.2p0+monitoring-plugins-2.2p8+python-2.7.16p1+python-3.7.5+wget-1.20.
3p1: can't resolve gettext-*
Couldn't find updates for .libs-glib2-2.56.1 .libs-libidn-1.34
.libs-libpsl-0.7.1p1 .libs1-gettext-0.19.4p0 gettext-0.19.8.1p3
glib2-2.58.3p8 libgpg-error-1.36 libidn-1.35 libpsl-0.20.2
monitoring-plugins-2.2p7 python-2.7.16 wget-1.20.2
Couldn't install gettext-runtime-0.20.1p0 glib2-2.60.7 libgpg-error-1.36p0
libidn-1.35p0 libpsl-0.20.2p0 monitoring-plugins-2.2p8 python-2.7.16p1
python-3.7.5 wget-1.20.3p1
----------------------------------------------
After staring at this for a while, I started to wonder (because it had been
a while since I last updated...) if the fact that "gettext" is now listed as
"getttext-runtime" (I guess this is just a "flavor," right?, but the change
was something I noticed) could be an issue.
I then looked at the pkg_info for one of the "don't match" packages on my
system, and compared them to the new/current packages.
So, for a local problem package I saw (in the depend list):
@depend devel/gettext:gettext-*:gettext-0.19.8.1p3
When I looked at the -current package I saw:
@depend devel/gettext,-runtime:gettext-runtime-*:gettext-runtime-0.20.1p0
Now, I really have little idea of what this means, or what I am doing, but I
decided I would just manually "fix" the @depend line in my local
"/var/db/pkg/[package]/+CONTENTS" to the "new" line (with
"gettext-runtime-0.20.1p0" in it).
I did that for all the "don't match" conflict packages, then re-ran "pkg_add
-vui -Dsnap" (although, I now understand the need or lack thereof for
"-Dsnap" better - thanks) and the package update completed without any real
issues. Specifically, gettext and all the "don't match" packages were
updated to the -current packages available yesterday.
As I said, I have little idea of what I am doing, but this (at least for the
last 30 hours) seems to have worked and the system appears to be "stable"
(and, once again, -current).
Thanks for the help
Ted
No comments:
Post a Comment