Neal Gompa (ニール・ゴンパ)

We'd probably want to rename the error if that's the actual root cause. `invalid-locale-subdir`, maybe?

It doesn't in Fedora, seems to be an openSUSE specific bug.

I think we're probably not handling `(x86-64)` properly in the dependency string. What do you think, @marxin?

@kalebskeithley The thing is, it's _wrong_ to not have the `%{?_isa}` suffix, so it's a bug on rpmlint's side.

> > @kalebskeithley The thing is, it's _wrong_ to not have the `%{?_isa}` suffix, so it's a bug on rpmlint's side. > > Do you mean the `x86-64` in `liborc1(x86-64)...

This is something I've been thinking about implementing. I recently saw that Debian's lintian has it, and I don't see a reason why rpmlint shouldn't, too.

Assuming a [transition from Zypper to DNF occurs in openSUSE](https://lists.opensuse.org/archives/list/[email protected]/thread/GAPGVVKWI5CCCKMR6JQI5RMEOZNTOMJK/), we should be able to finally move to file triggers like Fedora and Mageia did long ago...

I don't see a reason not to have the check. This definitely makes sense to me. Also, yikes, GNOME 1 in 2020!

@scarabeusiv As long as it's coming back, I'm happy to merge dropping the existing checks.

I like the idea of a unified diff-style view, as it's something people can easily comprehend on changes. Could we also do that for RPM payload information (metadata, deps, etc.)?