* On 2026-03-25 at 16:59 GMT, Greg Troxel wrote:
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.
Newer pkgin would handle this upgrade correctly, and newer pkgin also detects when there is a newer version of pkgin available from the repo and will upgrade itself first before performing the rest of the upgrade, to ensure that such fixes are in place.
As you are going through the JPEG_DEFAULT switch which was last April, it's likely you were trying to upgrade using a pkgin version prior to these fixes unfortunately.
Up until I implemented these pkgin improvements I've always instructed my own binary package users to 'pkg_add -U pkgin' first, but I don't think the NetBSD repositories do that.
Sorry that it caused breakage, but hopefully at least from the pkgin side of things this shouldn't happen again in the future.
-- Jonathan Perkin pkgsrc.smartos.org Open Source Complete Cloud www.tritondatacenter.com