confusing error message stops pkgin in its tracks about pkgin

[jperkin]

I think this was resolved a few years ago, but certainly 23.8.0 should avoid this, unless there are new corner cases I'm not aware of. Will close for now and if it happens again we can get a proper test case for it.

[0-wiz-0]

Just saw this again, with wip/bup this time.
Is there a workaround?

[mamash]

We've seen this too, though usually when a customer changes their pkgin configuration from one release to another and tries to upgrade in place (which we do not recommend).

Does 'bup' show up in pkgin se bup I wonder? Or is it a mismatch between PKGPATH of the installed package and the one available in pkg_summary?

[0-wiz-0]

I've since "fixed" this by "pkg_delete bup; pkg_add bup".

I think it could come from this:

My 'pkgin im' input file contains "sysutils/bup". During some 'pkgin
fug' that usually gets replaced with the version from "wip/bup" since
it has a higher number. In this bulk build, wip/bup didn't build, so
only sysutils/bup was available, which would match what you're
describing.

[mamash]

Either way it's an annoying bug that should be easy to fix. Identical PKGNAME should imply "same package" regardless of PKGPATH to pkgin.