Gentoo Bug Filed: moor-2.6.1 aborts if user is assumed to be Russian

2 weeks ago 3
Application sys-apps/moor-2.6.1 The app contains extremist content. It contains political statements. It requires the user to violate the criminal law of the Russian Federation (Article 280.1 of the Criminal Code of the Russian Federation) - Public calls for actions aimed at violating the territorial integrity of the Russian Federation. Reproducible: Always Steps to Reproduce: 1.set locale ru_RU.UTF-8 2.run application Actual Results: ERROR: russia not supported (but Russian is!) Options for using moor in Russian: * Change your language setting to ru_UA.UTF-8 * Set CRIMEA=Ukraine in your environment * russia leaves Ukraine

Comment 1 Enne Eziarc 2025-10-19 18:07:50 UTC

You're being just as much of a rabble-rousing umarell as the upstream author. Use the political freedom granted to you by the BSD-2 license to put a one-liner in /etc/portage/patches and move on with your perfectly spherical, frictionless, apolitical life. Maybe reflect on why you're so pressed to use this software in the first place - everyone else is able to quietly make do with `less`. diff --git a/cmd/moor/moor.go b/cmd/moor/moor.go index 480ab9624..d8d013bc4 100644 --- a/cmd/moor/moor.go +++ b/cmd/moor/moor.go @@ -627,7 +627,7 @@ func main() { var loglines internal.LogWriter logsRequested := false log.SetOutput(&loglines) - russiaNotSupported() + //russiaNotSupported() defer func() { err := recover()

Comment 2 Sergey 2025-10-19 18:38:26 UTC

(In reply to Enne Eziarc from comment #1) > You're being just as much of a rabble-rousing umarell as the upstream author. > > Use the political freedom granted to you by the BSD-2 license to put a > one-liner in /etc/portage/patches and move on with your perfectly spherical, > frictionless, apolitical life. Maybe reflect on why you're so pressed to use > this software in the first place - everyone else is able to quietly make do > with `less`. > > diff --git a/cmd/moor/moor.go b/cmd/moor/moor.go > index 480ab9624..d8d013bc4 100644 > --- a/cmd/moor/moor.go > +++ b/cmd/moor/moor.go > @@ -627,7 +627,7 @@ func main() { > var loglines internal.LogWriter > logsRequested := false > log.SetOutput(&loglines) > - russiaNotSupported() > + //russiaNotSupported() > > defer func() { > err := recover() So, it turns out that packages with extremist content can be pushed through Portage, and it's up to end users to figure out how to interact with such applications? I believed that a specific Linux distribution was not a platform for political statements. Today, the software owner requires me to say that Crimea is Ukraine, forcing me, as a citizen of the Russian Federation, to violate Russian law. What could happen tomorrow with this approach? Will someone have to be killed in order to use an application from Portage? Where is the line? You say that my problem is that I use moor instead of less, but where does that logic lead? You could sneak a ransomware virus into Portage and then laugh at the victims, saying, “Why did you install the virus? What were you looking at and what were you thinking?” Translated with DeepL.com (free version)

Comment 4 Sergey 2025-10-19 18:51:10 UTC

(In reply to Sam James from comment #3) > Going over the options.. > > Patching the ebuild is going to induce the ire of the upstream author, but > even if it didn't, it would be problematic if users in a Russian locale > filed a bug upstream and then had to comply with conditions they didn't like > in order to interact. > > Last-riting it over this is a bit drastic and I don't think it would violate > any rules for another developer to bring it back. > > The best option seems to be to either unconditionally warn on installation > or to "detect Russian" in the ebuild. "Detecting Russian" has the same > problems as the upstream approach (imprecise). What might work is adding a > L10N USE and warning when that is set. > > I need to think about it some more. Considered and thoughtful opinions on > options are welcome. Thanks. I agree that the author's opinion should be stated before the application is installed, not while it is running. Today, the author limited himself to requesting a change of locale, but tomorrow, what might happen if a locale is detected (or geoip, as was the case with npm)? Might he execute rm -rf /, because that corresponds to his sense of justice? Я поддерживаю мысль, что предупреждение о мнении автора должно быть до установки приложения, а не во время исполнения его. Сегодня автор ограничился требованием сменить локаль, а завтра что может произойти, при обнаружении локали (или geoip как это было в npm) он сделает rm -rf /, т.к. это соответствует его чувствам справедливости?
Read Entire Article