Leap Micro 6.2 Adopts the Leap Release Cycle

Members of the openSUSE Release Team are excited to announce that the Leap 16 Beta is now available for testing!

Like its predecessor Leap 15.6, the Leap 16.0 version continues the tradition of a stable, classic Linux distribution; it’s built from SUSE Linux Enterprise 16 and its new base, SUSE Linux Framework One (formerly ALP).

You can download both online and offline Agama installer images from get.opensuse.org. Leap remains the project’s traditional, full-featured Linux distribution.

Meanwhile, people looking for a modern, immutable system with point releases, take a look at our Leap Micro instead; It’s designed for containerized and virtualized workloads.

Roadmap Highlights

The Leap Micro 6.2 schedule and lifecycle align with Leap 16.0’s roadmap. This makes Leap Micro effectively a specialized image of Leap 16.X going forward.

• Leap Micro 6.2 Beta release within a few days
• Both Leap 16.0 and Leap Micro 6.2 releases are planned for October 2025

What’s New in the Beta?

Leap 16.0 with its fresh fork brings a renewed foundation and cleaner system.

• Expected to be Wayland-only (some Xorg remnants remain for now)
• SysV init support has been dropped
• The new Agama installer is now the default
• The traditional YaST stack is retired in favor of:
  • Cockpit for system management
  • Myrlyn as a drop-in replacement for the YaST Software GUI (Note: YaST is still available in Tumbleweed but will no longer be developed. YaST has been removed from Leap 16 and Myrlyn takes on this role of software installation like YaST. If someone is interested in the maintanece of YaST for further development and bugfixes, the sources are available on github.)
• Leap 16.0 will no longer run on machines that do not support x86_64-v2.

Versions of Interest

• Kernel: 6.12 (from SLES 16.0)
• GNOME: 48.0 (targeting 48.1 for GA)
• KDE Plasma: 6.3.4 (aiming for 6.4.0 in the final release)
• AppArmor: 4.1
• GIMP: 3.0
• RPM: 4.20 coming soon
• Cockpit 334.1 (aiming for latest version available at time of RC)
• GNU Health 5.0 once it’s available in June

Revamped Repositories

Leap 16.0 now uses RIS-based repository management through the openSUSE-repos package and is a system already familiar to users of Leap Micro 6.0.

Leap 16.0 distribution repositories are now split per architecture, which makes metadata smaller and refreshes faster. Aside from that Leap 16.0 Beta contains experimental support for parallel package downloads in Zypper, speeding up installs and updates`. We expect the feature to become stable and therefore enabled by default before the release.

All of these changes should hopefuly result into a much better experience with software management on Leap overall.

You can find the full list of Leap 16.0 repositories here.

Migration Options

We recommend fresh installs to fully test the new Agama installer. If you would like to upgrade from Leap 15.6 manually with zypper dup, you’ll need to update distribution repositories. We are newly using split repodata per architecture and we no longer have a separate update repositories. Users are adviced to disable all 3rd party repositories, as these are usually the root cause of most upgrade issues.

More details at https://en.opensuse.org/SDB:System_upgrade

sudo zypper dup --releasever 16.0

Alternatively, test our experimental migration tool which utilizes openSUSE-repos and will do the repository change for you:

sudo zypper in opensuse-migration-tool

sudo opensuse-migration-tool

You can find it on GitHub: opensuse-migration-tool

Screenshot:

SELinux, AppArmor and Gaming

Leap 16.0 follows SUSE Linux Enterprise in using SELinux by default. Unlike SLE, openSUSE also provides AppArmor, thanks to active community contributions.

You can switch from SELinux to AppArmor if preferred. Steam users may want to follow this workaround until gaming-targeted SELinux policies land in 16.0 Beta.

New Release Notes System

Our documentation team has introduced a modular release notes system using SUSE/release-notes. This allows for better sharing of SLE changes and should lead to more complete and useful documention.

Submitting Bug Reports

Your feedback is critical at this stage. People participating in alpha and beta testing help to identify and resolve issues before the general release of distributions. Whether bugs are in software packages, printing, networking or other areas, reporting these problems now ensures a smoother experience for everyone. Please report any issues on bugzilla.opensuse.org.

Thank you for testing and being part of the openSUSE community. Let’s shape Leap 16.0 together!

The interview has been conducted by Jose Pomeyrol and published originally in Spanish on MuyLinux. Find the English version here below.

The other day I noticed something curious: after updating one of the apps I use regularly, it now shows a bold message when starting up — “Made with ❤️ Europe.” It’s similar to the tagline on the credits page of EU OS, a new Linux distribution being discussed in various tech-focused forums these last days. What do these two projects have in common? Among other things, they are both developed in Europe — or at least, their final form is.

Europe, and the European Union in particular, is preparing to face challenges unprecedented in recent history: tensions with Russia and calls for rearmament among Eurozone members; Trump’s return to the White House and a new wave of protectionist policies; and China’s technological rise, especially in AI. Europe must respond on multiple fronts — and the complexity of these issues doesn’t make things any easier.

To explore all this, we exchanged via email with Robert Riemann, master in physics and PhD in computer science, Head of Digital Transformation in the Technology and Privacy Unit of one body of the EU, and project lead of EU OS, a Linux distribution with institutional ambitions… proudly “Made with ❤️ in Brussels.”

I recently read a headline suggesting that EU OS is “the EU’s official Linux distribution” — which isn’t quite accurate. According to the project’s website, it’s a proof of concept for implementing a Linux operating system […] in a typical public sector organisation. The existence of such a project raises several questions: what motivated you to propose something like this? Has the current geopolitical situation influenced your thinking?

Indeed, some writers only see "EU OS" and believe it must be from the Commission. Let me clarify that this is currently a community project that as of now has no support from the EU institutions and is not used by them. So when I get aware of misleading articles, I write them an email and ask to be clear about this. I hope of course that EU OS will be adopted officially in the future.

In my day job, I work for the European Data Protection Supervisor and I often hear that there are no alternatives to Windows. Given the geopolitical situation, I think alternatives are very valuable. Even if you do not use them, they give you more leverage and decrease your exit costs as an organisation. I am already a Linux user for over 15 years. I think the Linux user experience improved drastically during this period. If the administrations in the EU (meaning both on member state and EU level) have not enough phantasy to imagine how using Linux would be, someone needs to build a pilot, so they can try it out themselves. I’ve been building previously pilots in my professional capacity to convince decision makers and had some success. This is how the project EU OS was born. As this project is larger and resources are scarce at work, I work on it in my free time. I think it is too important to not even try due to lack of resources. If you are a Linux admin, please subscribe to our issues tracker and join our Matrix channel. EU OS needs as much help as it can get.

Although EU OS is described not as just another distribution but rather a common base upon which tailored solutions for different countries or use cases could be built, in the end it is still a distribution. Specifically, it’s based on Fedora and KDE Plasma. Why this combination? And more importantly, why not a European-origin distribution such as Debian or SUSE?

I received this question often and answered in great detail on the project website. If organisations want to actually assume control, they need to in-source the development and maintenance of the operating system. Already today, public sector organisations struggle to recruit IT talent. So the two options to deploy Linux at scale in the public sector would be to outsource to an Enterprise Linux company or to collaborate for the development and maintenance with the community and with other public sector organisations. The latter already works quite well for Docker/Podman containers. When I learnt first about how the bootable container (bootc) technology permits to build containers with Kernels included, so that those containers are bootable on desktop machines, I thought that this matches the collaboration style of the public sector quite well: sharing Containerfiles and building customisations locally to stay in control and maintain autonomy all while reusing existing container IT infrastructure.

bootc builds on top of rpm-ostree, which is stable for some time and also used by e.g. flatpak applications. The ecosystem is quite vivid, but all its adopters belong to the fedora family: fedora, CentOS stream, universal blue, AlmaLinux and few smaller more. SUSE does not support bootc. SUSE’s Kalpa is only in alpha and their technology is less suited. I acknowledge that Debian is popular, but Fedora has apparently thanks to Redhat Linux more consistent tooling for enterprise users. This is important for enterprise users.

However, as far as I understood SUSE also offers professional services for fedora-like distributions. Their build service supports also fedora. So EU OS could still leverage some tools and know-how from SUSE. Maybe SUSE manages in the future to support bootc as well. Then it would be easy to switch to opensuse base images in EU OS.

KDE is mostly a personal choice. Schlewig-Holstein apparently also selected KDE for their desktop. This gave me some confidence. For the piloting of EU OS, the choice of the desktop environment is not so important as long as with one bootc command, one can easily switch between KDE and Gnome based images. Of course I hope, that we can agree on one desktop environment later on and do not have to support both.

Redhat Linux, RockyLinux, and AlmaLinux compete currently for similar use cases. This keeps the exist costs down from any of those and offers a competitive market. That’s important. Redhat and SUSE have both business in the US and the EU. These are global companies. Many FOSS projects rely on contributions from all over the world and I think this is international collaboration is very inspiring. It would be unfair to judge and select FOSS projects by the origin of their core team or office address only.

Looking deeper into the choice of base system, I noticed you’re not just referring to Fedora, but specifically to Fedora Kinoite, the immutable KDE edition. And when someone suggested Kalpa (openSUSE), you dismissed it citing a couple of technical reasons. Beyond the detail: wouldn’t it be reasonable for a project with EU OS’s aspirations to aim higher? I mean: if something’s missing, we make it happen — but we build it in-house.

I totally agree. Unfortunately, it is not happening already and I don’t believe I can make it happen now for two reasons:

1. EU OS does not have enough volunteers who contribute in code. With many, EU OS could be more ambitious.
2. The public sector is not convinced and resources are scarce. To justify more resources for something like EU OS, EU OS first needs to build some traction. Most public servants have never used something else than Windows. I assume it is no different for most IT decision makers.

I invite the readers to ask themselves what they have done so far: Have you talked to your local, national or EU parliamentarians? To political parties? How many have signed the recent European Parliament petition? Only 2500 people in the entire European Union. It was maybe not the best text, but nobody submitted since then a better one. It seems to me the Linux community hasn’t learnt yet how to organise campaigns. Commenting on tech blogs and Mastodon resonates in our own echo chamber, but does not reach the average politician, IT decision maker or user in the public sector.

On the project’s motivation page, you explicitly mention campaigns like Public Money? Public Code! launched years ago by the Free Software Foundation Europe. You also reference similar initiatives to EU OS. In Spain, there have been some interesting success stories. For example, in the region of Valencia, public primary school students have been using LliureX, an Ubuntu-based system adapted to their needs, for years. And there are more examples. But whenever these initiatives are discussed, the same criticisms usually arise — especially regarding supposed resource waste, arguing that existing solutions could be reused. What’s your view on this criticism? And what do you think are the real chances of implementing an operating system at a European level, even as a shared base that different institutions and public bodies could adapt to their own needs — which is exactly what EU OS aims to offer?

The added value of EU OS is not to use Linux is some public sector organisations. As you point out rightly, Linux is already used in Europe and also Spain specifically, so this has been proven to work.

However, all those projects are very much isolated from each other. EU OS offers an added value as it proposes to use bootable container technology (bootc). bootc has security advantages and eases the collaboration, so that organisations can mutualise the efforts of a migration from Windows and the operations afterwards. Given the scarcity of budget and IT experts in the public sector, this collaboration could be decisive to start a migration in the first place.

Initially, EU OS could be setup in 3 or 4 specific organisations that require (for some users) more control than Windows 11 may be able to offer.

To achieve further than more control also cost savings, scaling effects must be achieved through replacing licensed Windows computers with EU OS (or other Linux distributions) on a large scale. To pay a team of 10 IT experts (est. 160k€/a) one would need to replace Windows 11 (est. 100€/a)¹ on 16k workplaces. From the 80k people working for or in an EU administration, this would mean 20%. From the 2.9 Mio people working in the Spanish public sector,² this would mean 0.6%. Higher adoption would then lead to savings. These are of course just some basic estimates that do not factor in IT support yet.

You currently work for the EU as Head of Digital Transformation in the Technology and Privacy Unit. Can you explain what your job actually entails? And beyond that: to what extent can your position help push forward a project like EU OS within EU institutions? What would the path look like for it to be considered officially, receive funding, and ultimately grow under the EU’s wing?

Until the Commission is recruiting me to speak publicly about EU OS, I shall keep separate my work and this personal project. Only that much: Obviously, my work experience helps me to understand how I need to position EU OS to make it appealing. It doesn’t mean though I cannot be mistaken.

The path is entirely unclear. At best citizens would ask their members of the European Parliament to discuss this in the European Parliament and their governments to discuss this in the Council of the European Union. Meanwhile, I look for partners to support the piloting.

At MuyLinux we’ve followed several EU open source initiatives in recent years — from bounty programmes to evaluations of open source applications and services like Signal, or more recently, Nextcloud and Collabora Online. Since you work for the EU: how well is open source software actually adopted in EU institutions? Not just on the server side, but also for end users. What’s the overall picture? And what about your own case — or your department’s?

I can point your to a press release: https://www.edps.europa.eu/edps-inspection-software_en

For more information from public organisations, you need to ask them, not me.

I recently interviewed Gerald Pfeifer, CTO of SUSE, about the new geopolitical context and its implications for Europe. He’s confident that Open Source will be key to Europe’s digital future — and I agree. But we don’t fully see eye to eye on one issue: the balance between digital sovereignty and economic competitiveness. If the EU is known for one thing, it’s regulation — sometimes fragmented across member states, even if unification efforts are underway. The aim is to protect citizens, but it often slows innovation. What’s your take on this?

I think the Draghi report written for the European Commission offers some answers answer. I do not think this balancing act is so important for the ambitions of EU OS.

Following up on that: I can understand the benefits of having a community -on a european community sense- OS for Europe. But we’re missing big tech players: we don’t have a Google, a Microsoft, a Meta or an Amazon in Europe. How independent are we, really? Or how independent can we hope to be, when 90% of Europeans rely on Gmail and WhatsApp to communicate, use Microsoft Office for work, and shop on Amazon?

Important is that with EU OS, the EU would be more independent than before. EU OS could be considered as a building block of another, broader initiative to increase the strategic IT sovereignty in the European Union: https://euro-stack.eu is a proposal backed by some members of the European Parliament and the industry. The proposal considers the entire digital supply chain. People should translate their worries or hopes into actions. Everyone can join a political party or non-partisan initiative and promote change. People who can subscribe to the ideas of the euro stack initiative should promote it.

Beyond global tensions, various EU member states have for years tried to spy on their own citizens, or at least to push for more control over communications systems, encryption, and so on — all in the name of national security. Are we perhaps a bit too self-righteous in Europe when comparing ourselves to foreign powers? How much trust can we really place in our own governments?

EU OS focuses on corporate computers only that the government distributes to their own staff. Already today, people have a lot of choice of alternative operating systems. In this context, I like to mention the initiative https://endof10.org that promotes the migration from Windows 10 to Linux for non-corporate private computers.

Then, it is not my role to judge the trustworthiness of governments. The EU grants a lot of rights to citizens to protect their privacy from both the private and public sector – most famously the GDPR. Use these rights!

And finally, just out of curiosity: you're not just a technocrat. From your social media, it’s clear you have a genuine interest in free and open technologies. Tell us a bit more about that. On a personal level... what do you run on your PC? What free software projects are you most passionate about, and why?

I guess I use the same tools on my private computer that most physicists or scientists working with data would use on their Linux computer. The only difference is that I joint after my PhD the public service. So I have to use a Windows computer as well during week days – let’s see for how long still! ;)

Since my first semester in 2007 (maybe even a bit early), I used opensuse (back then they called it differently) on my own computer and Debian in the university. 2024, I switched to opensuse Kalpa and then to Fedora Kinoite.

I am a member of the Chaos Computer Club, of KDE, of Matrix and lend a hand to keep OpenStreetMap updated. They all help to shape the IT infrastructure for our democratic societies. However, I do not hold formal roles on these projects.

Disclaimer: The views expressed in this interview are personal and do not represent directly or indirectly the views of the European Data Protection Supervisor.

Dear Tumbleweed users and hackers,

As many know, last weekend was Easter-Weekend, which means many of us in Europe get a long weekend with extra days off. This is why I did not get around to writing last week’s Review. But with such a long weekend in between, it’s also not very surprising that things moved a bit slower. Let me catch up now and inform you about the changes of the last two weeks. We released 8 snapshots (0410, 0411, 0414, 0417, 0418, 0420, 0422, 0423).

The most relevant/interesting things that changed in the mentioned 8 snapshots were:

• Inkscape 1.4.1
• Systemd 257.5
• coreutils 9.7
• fwupd 2.0.8
• Mozilla Firefox 137.0.2
• Alsa 1.2.14
• Apparmor 4.1.0
• GNOME 48.1
• Linux kernel 6.14.2 & 6.14.3
• KDE Frameworks 6.13.0
• LibreOffice 25.2.2.2
• Perl 5.40.2
• Python setuptools 78.1.0: main breaking change: dist-info directories are now all lower-case
• Ruby 3.4.3
• KDE Gear 25.04.0
• cURL 8.13.0
• VirtualBox 7.1.8
• Mesa 25.0.4
• Grep 3.12
• pcre2 10.45; pcre (1) has been removed from the distribution
• PHP 8.4.6
• LibXML 2.13.8

Maintainers have submitted the following changes, which are currently being tested in the staging areas:

• Linux kernel 6.14.4
• util-linux 2.41
• openSSL 3.5.0
• openSSH 10.0p2
• Python 3.13.3
• GCC 15 as distro compiler, see https://build.opensuse.org/staging_workflows/openSUSE:Factory/staging_projects/openSUSE:Factory:Staging:Gcc7
• CMake 4.0 (not yet submitted, but please help fix issues, See https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/FHM4V3PGI3GX65LG6ZIAGJ6QQD5O57WN/

While no dates are set to stone yet, we expect a couple of syslog-ng releases in the near future. As version 4.8.1 is used in major Linux distributions and has a couple of known bugs, we will release 4.8.2 to address those. However, we are also working on 4.9.0, which will bring many changes.

Read more at https://www.syslog-ng.com/community/b/blog/posts/a-call-for-testing-the-upcoming-syslog-ng-releases

We are pleased to announce that the Call for Speakers for the openSUSE.Asia Summit 2025 is now open. The event will take place from August 29 to 31, 2025 in Faridabad, India. This summit is an excellent opportunity to share your expertise, ideas, and experiences with the openSUSE community.

We are looking for speakers who are passionate about openSUSE and open-source technologies. The openSUSE Asia committee encourages proposals from diverse backgrounds to present in-depth technical talks, tutorials, and case studies. We invite submissions from individuals with a wide range of expertise in open-source topics.

In 2025, we aim to include more cross-distro talks, focusing on collaboration with other distribution communities such as AlmaLinux, Debian, and Ubuntu.

Topics

We welcome talks in a wide range of categories that reflect both technical depth and community relevance. Topics may include, but are not limited to:

Technical Topics

• openSUSE in Action: Leap, Tumbleweed, MicroOS, openQA, YaST, and local deployment stories
• Building with Open Build Service (OBS): Packaging, collaboration, and automation
• Localized Desktop Environments & Tools: GNOME, KDE, XFCE with Indian language support
• FOSS for Creative & Educational Use: LibreOffice, GIMP, Inkscape in schools, colleges, and startups
• Cloud & DevOps Technologies: Kubernetes, Rancher, Docker – real-world implementations in India
• Cybersecurity & Digital Safety: Securing the open-source stack and managing vulnerabilities
• IoT & Embedded Systems in India: Applications in smart cities, agriculture, and local innovations
• openSUSE in Government & Institutions: Adoption stories and digital infrastructure

Community and Practice Topics

• FLOSS Ecosystem Overviews & Trends
• Tips, Experience Stories (Success or Failure), and Best Practices
• FOSS in Indian Education and Curriculum Integration

Types of Sessions

We are inviting proposals for the following types of sessions:

• Long Talks (30 min. + Q&A)
• Short Talks (15 min. + Q&A)

We will also have Lightning Talks (5 min.) announced later.

Schedule

• Proposal Deadline: June 20, 2025
• Notification to Speakers: June 30, 2025

How to Submit Your Proposal

• Submit your proposal at: events.opensuse.org
• If you do not have a SUSE community account, sign up from the top menu of the system before submitting your proposal.
• You must follow the openSUSE Conference Code of Conduct.
• Your proposal must be written in English, between 130 to 250 words.
• It should have a suitable title that clearly reflects the topic of your talk.
• Before submission, please check for spelling and grammar using tools such as:
  • LibreOffice
  • Google Docs
  • Grammarly
• Refer to our guide for writing a strong proposal.
• If you need help, reach out to committee members in your country or region:
  Asia Summit Committee List

The Mastodon instance eupolicy.social is geared towards people who identify themselves as part of the EU Bubble. Purposfully, there is no definition provided and indeed the instance is a bit flexible on what EU Bubble would mean.

To help the instance keep this focus (and avoid spam), the admins have opted for approval-based registration of signups. New users can during their signup process provide some text about themselves. To make this more relevant, eupolicy.social decided to customise the text that instructs the users to describe their relation with the instance.

Previously, the instance admins changed all language files in a source code copy of the locales folder. This was tidysome and can easily break with an update, especially when using a docker/podman-based setup that contains already all language files.

How to overwrite individual language/translation strings

The underlying Ruby on Rails loads all string (by alphabetic order) from yml files in a folder that is by default /config/locales. Files loaded later can overwrite strings from files loaded earlier. To overwrite a string, you have to find the identifier first, e.g. in the English language file.

# file: "/config/locales/en.yml"
en:
  […]
  auth:
    […]
    sign_in:
      preamble_html: Login with your <strong>%{domain}</strong> credentials. If your account is hosted on a different server, you will not be able to log in here.
      title: Login to %{domain}
    sign_up:
      manual_review: Sign-ups on %{domain} go through manual review by our moderators. To help us process your registration, write a bit about yourself and why you want an account on %{domain}.
    […]

To change the string auth.sign_up.manual_review in all languages, I have created a new language file called zz-custom-signup-message.yml here below. The prefix zz puts the file at the very end given the alphabetic ordering.

If Mastodon admins use a local git clone of the Mastodon source code, this file can stay in the folder and won’t cause conflicts when language files receive updates via git. If Mastodon admins use the Container image with Docker or Podman, they can mount this file into the setup with podman run -v ./zz-custom-signup-message.yml:/config/locales/zz-custom-signup-message.yml:z,ro […]. With Container compose file, this would look like:

# file: "docker-compose.yml"
services:
  web:
    container_name: "mastodon-web"
    image: ghcr.io/mastodon/mastodon:$MASTODON_VERSION
    restart: always
    […]
    volumes:
      - ./container-volumes/mastodon/public/system:/mastodon/public/system
      - ./zz-custom-signup-message.yml:/opt/mastodon/config/locales/zz-custom-signup-message.yml:z,ro
  […]

# file: "/config/locales/zz-custom-signup-message.yml"
---
en:
  auth:
    sign_up:
      manual_review: |
        Please describe how you are part of the EU policy bubble. If you are not sure what to write here, maybe another Mastodon server might suit you better.

de:
  auth:
    sign_up:
      manual_review: |
        Auf welche Weise sind Sie mit der EU-Politik-Bubble verbunden? Wenn Sie nicht sicher sind, was in dieses Feld soll, möchten Sie sich vielleicht einen anderen Mastodon-Server aussuchen.

fr:
  auth:
    sign_up:
      manual_review: |
        Comment faites-vous parti de la bulle politique européenne? Si vous n'êtes pas sûr quoi répondre, peut-être un autre serveur Mastodon sera plus approprié pour vous.

es:
  auth:
    sign_up:
      manual_review: |
        Por favor, describa cómo forma parte de la burbuja política de la UE. Si no está seguro de qué escribir aquí, quizá otro servidor de Mastodon le venga mejor.

bg:
  auth:
    sign_up:
      manual_review: |
        Моля, опишете по какъв начин сте част от политическия балон на ЕС. Ако не сте сигурни какво да напишете тук, може би друг сървър на Мастодон ще ви подхожда повече.

cz:
  auth:
    sign_up:
      manual_review: |
        Popište, jak jste součástí politické bubliny EU. Pokud si nejste jisti, co sem napsat, možná by vám lépe vyhovoval jiný server Mastodon.

dk:
  auth:
    sign_up:
      manual_review: |
        Beskriv venligst, hvordan du er en del af EU's politiske boble. Hvis du ikke er sikker på, hvad du skal skrive her, passer en anden Mastodon-server måske bedre til dig.

nl:
  auth:
    sign_up:
      manual_review: |
        Beschrijf alsjeblieft hoe je deel uitmaakt van de EU-beleidsbel. Als je niet zeker weet wat je hier moet schrijven, misschien past een andere Mastodon server beter bij je.

et:
  auth:
    sign_up:
      manual_review: |
        Palun kirjeldage, kuidas te olete osa ELi poliitikamullist. Kui te ei ole kindel, mida siia kirjutada, siis võib-olla sobib teile paremini mõni teine Mastodoni server.

fi:
  auth:
    sign_up:
      manual_review: |
        Kuvailkaa, miten olette osa EU:n poliittista kuplaa. Jos et ole varma, mitä kirjoittaa tänne, ehkä toinen Mastodon-palvelin voisi sopia sinulle paremmin.

gr:
  auth:
    sign_up:
      manual_review: |
        Περιγράψτε τον τρόπο με τον οποίο συμμετέχετε στην πολιτική φούσκα της ΕΕ. Αν δεν είστε σίγουροι για το τι να γράψετε εδώ, ίσως ένας άλλος διακομιστής Mastodon να σας ταιριάζει καλύτερα.

hu:
  auth:
    sign_up:
      manual_review: |
        Kérjük, írd le, hogy milyen szerepet töltesz be az uniós szakpolitikákban. Ha nem tudod, mit írj ide, talán egy másik Mastodon-szerver jobban megfelelne neked.

it:
  auth:
    sign_up:
      manual_review: |
        Descrivi come fai parte della bolla politica dell'UE. Se non sei sicuro di cosa scrivere qui, forse un altro server Mastodon potrebbe essere più adatto a te.

pl:
  auth:
    sign_up:
      manual_review: |
        Wyjaśnij, na czym polega twój związek ze środowiskiem politycznym Unii Europejskiej. Jeśli nie wiesz, co tu napisać, być może inna instancja Mastodona będzie dla Ciebie bardziej odpowiednia.

lv:
  auth:
    sign_up:
      manual_review: |
        Lūdzu, aprakstiet, kā jūs esat daļa no ES politikas burbuļa. Ja neesat pārliecināts, ko šeit rakstīt, varbūt cits Mastodon serveris varētu būt jums piemērotāks.

lt:
  auth:
    sign_up:
      manual_review: |
        Apibūdinkite, kaip dalyvaujate ES politikos burbule. Jei nežinote, ką čia rašyti, galbūt jums labiau tiktų kitas Mastodono serveris.

pt:
  auth:
    sign_up:
      manual_review: |
        Descreva de que forma faz parte da bolha política da UE. Se não tem a certeza do que escrever aqui, talvez outro servidor Mastodon seja mais adequado para si.

ro:
  auth:
    sign_up:
      manual_review: |
        Vă rugăm să descrieți modul în care faceți parte din comunitatea politicilor europene. Dacă nu sunteți sigur ce să scrieți aici, poate că un alt server Mastodon vi s-ar potrivi mai bine.

sk:
  auth:
    sign_up:
      manual_review: |
        Opíšte, ako ste súčasťou politickej bubliny EÚ. Ak si nie ste istí, čo sem napísať, možno by vám viac vyhovoval iný server Mastodon.

sl:
  auth:
    sign_up:
      manual_review: |
        Opišite, kako ste del političnega mehurčka EU. Če niste prepričani, kaj bi napisali tukaj, vam bo morda bolj ustrezal drug Mastodonov strežnik.

se:
  auth:
    sign_up:
      manual_review: |
        Beskriv hur du är en del av EU-bubblan. Om du inte är säker på vad du ska skriva här, kanske en annan Mastodon-server passar dig bättre.

uk:
  auth:
    sign_up:
      manual_review: |
        Будь ласка, опишіть, яким чином ви є частиною мильної бульбашки політики ЄС. Якщо ви не знаєте, що тут писати, можливо, вам більше підійде інший сервер Mastodon.

no:
  auth:
    sign_up:
      manual_review: |
        Beskriv hvordan du er en del av EUs politiske boble. Hvis du ikke er sikker på hva du skal skrive her, passer kanskje en annen Mastodon-server bedre.

References:

• internationalisation in Rails https://guides.rubyonrails.org/i18n.html
• how merging and as such overwriting works in Rails language files https://stackoverflow.com/a/1840077/1407622