Re: pkgin carnage possible culprit

[Greg Troxel <gdt%lexort.com@localhost>]

steve%prd.co.uk@localhost (Steve Blinkhorn) writes:

> There are a few hundred lines in  the error log such as these:
>
> pkg_add: Package `libjpeg-turbo-3.1.3' conflicts with `jpeg-[0-9]*',
> and `jpeg-9f' is installed.
> pkg_add: Installed package `jpeg-9f' conflicts with
> `libjpeg-turbo-[0-9]*' when trying to install `libjpeg-turbo-3.1.3'.

pkgin has baked in an assumption that when you use a binary package
repo, then every package you have will be from that repo.  Yes, you can
rebuild things locally from compatible sources, and do other things if
you know what you're doing, but you're off the rails.

pkgsrc changed the default from jpeg to jpeg-turbo.  That's the root
cause of the above error message.

My advice is

  save the log someplace safe so you know what was tried to be installed
  and failed

  "pkg_delete jpeg" which will likely fail, and save the output to know
  which packages depend on it

  "pkg_delete -f jpeg" to remove it anyway

  "pkgin fug" to make more progress

  "pkgin in foo" for foo that you want that was failed in the logs.


My other advice is:

  NetBSD 9 is old, and 9.2 is an old version of 9.  Consider upgrading
  to NetBSD 10.  Many packages are having trouble building on 9, or if
  they do require a newer compiler leading to possible ABI issues with
  libstc++.

Basically I see NetBSD 9 as fuctionally EOL for doing anything
desktop-ish, even though it's not yet technically EOL.  But, any day
there's probably going to be an announcement, and I'm giving it even
odds that it's "11 has been released" vs "please test 11.0 RC3".  (I
don't know anything that hasn't been on the lists.)