Hi all,

I've recently started using OpenBSD, installing it on an old Lemote
Yeeloong, largely because of uncertainty in where Debian Linux is
headded with this port.

So far so good, it's been largely smooth sailing.  I'm in the process of
installing what I'd normally use on Linux.  Prior to this I was running
Gentoo Linux with a n32 userland on the device, and some packages are
seemingly incompatible with n32 (and also have problems on x86-64's x32
userland).

I note OpenBSD/mips64 uses n64, so we'll see how that goes.  This was
something I was unable to achieve directly with Gentoo.  (And yes, I
recognise OpenBSD is not Linux, not expecting it to work like Linux either.)

I initially installed Ports from the snapshot, but then encountered some
404 errors where package sources were no longer available.  Thus, I
figured I'd grab a version off the git mirror (github).

So I have a couple of packages (maybe about a dozen) installed via the
snapshot ports and some via git ports.  This might be the root of my
problems.

I now have seen the following a couple of times:
> ===>  Building package for py-cairo-1.10.0p1
> Create /usr/local/ports/packages/mips64el/all/py-cairo-1.10.0p1.tgz
> Error: Libraries in packing-lists in the ports tree
>        and libraries from installed packages don't match
> --- /tmp/dep_cache.5mrOMvzTf/portstree-py-cairo-1.10.0p1        Wed Nov 16 
> 09:11:03 2016
> +++ /tmp/dep_cache.5mrOMvzTf/inst-py-cairo-1.10.0p1     Wed Nov 16 09:11:04 
> 2016
> @@ -13,8 +13,8 @@
>  -W expat.11.0
>  -W fontconfig.10.0
>  -W freetype.25.0
> --W glib-2.0.4200.4
> --W gobject-2.0.4200.4
> +-W glib-2.0.4200.3
> +-W gobject-2.0.4200.3
>  -W m.9.0
>  -W pcre.3.0
>  -W pixman-1.32.6
> *** Error 1 in /usr/ports/graphics/py-cairo 
> (/usr/ports/infrastructure/mk/bsd.port.mk:3157 'wantlib-args')
> *** Error 1 in /usr/ports/graphics/py-cairo 
> (/usr/ports/infrastructure/mk/bsd.port.mk:1888 
> '/usr/local/ports/packages/mips64el/all/py-cairo-1.10.0p1.tgz')

I understand this is due to a discrepancy between the versions normally
used in packages and those actually installed.  I've been able to work
around these using PKG_CREATE_NO_CHECKS=yes but I sense this is not a
good idea long-term.

What's the best way of fixing the underlying problem?  Would manually
updating (in this case) the glib and gobject ports fix it, or is there
some other fix?

Regards,
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

Reply via email to