Re: pkgsrc name collisions

["David H. Gutteridge" <david%gutteridge.ca@localhost>]

On Mon, 2023-01-30 at 23:13 -0500, David H. Gutteridge wrote:
> On Mon, 30 Jan 2023 at 22:52:24 +0000, Taylor R Campbell wrote:
> > The following packages have colliding names in different categories:
> > 
> > {fonts,sysutils}/gnome-font-viewer
> 
> [...]
> 
> > gnome-font-viewer and mdp are PKGBASE collisions.  The two
> > gnome-font-viewers appear to be the same software (imported and then
> > updated at different times), but in the case of mdp, this means
> > pkg_add or pkgin will try to install the wrong package for `mdp' if
> > you want misc/mdp because mbone/mdp has a higher version number.
> 
> The gnome-font-viewer one I flagged back a couple of years ago[1]. No
> one ever responded, so I guess we could take that as no objection to
> removing one of them. (I'd forgotten about this topic.)
> 
> IIRC, I did find that the newer of the two under sysutils built for
> me,
> but then crashed on startup. I haven't tried it recently.
> 
> 1. http://mail-index.netbsd.org/pkgsrc-users/2021/08/18/msg034254.html

The crash is reproducible for me, it occurs when the session is using a
locale that gnome-font-viewer (or somewhere in GTK) can't handle, e.g.,
if LC_ALL is unset (which can happen in some DEs). It then tries to fall
back to the "C" locale, but this still causes a crash.

(gnome-font-viewer:818): Gtk-WARNING **: 21:27:14.920: Locale not
supported by C library.
        Using the fallback 'C' locale.

(gnome-font-viewer:818): Gdk-WARNING **: 21:27:20.681: The program
'gnome-font-viewer' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this
connection)'.
  (Details: serial 945 error_code 14 request_code 130 (MIT-SHM)
minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error()
function.)

I did try that advice, but found that caused another issue that obscured
getting any useful details. Since the "workaround" seems clear, I don't
see it as an impediment to removing the older version of the package.

Regards,

Dave