Source strings

61 Strings 100%
Browse Translate
1,618 Words 100%
11,473 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
61 1,618 11,473
All strings Browse Translate Zen
61 1,618 11,473
Read-only strings Browse Translate Zen

Overview

Project website pagure.io/fedora-docs-l10n/modularity
Instructions for translators

Mailing list for translators: <trans@lists.fedoraproject.org
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository ssh://pagure.io/fedora-docs-l10n/modularity.git
Repository branch master
Last remote commit automatic update of pot/po files d453d4ba
♪ I'm a bot, bot, bot ♪ authored 11 months ago
Last commit in Weblate Translated using Weblate (Spanish) 5f2e1899
User avatar vareli authored yesterday
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-modularity/nav/
File mask po/*/master/pages/core-concepts/upgrade-paths.po
Translation file Download pot/master/pages/core-concepts/upgrade-paths.pot
Last change Aug. 11, 2023, 10:02 p.m.
Last author None
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 61 1,618 11,473
Translated 100% 61 100% 1,618 100% 11,473
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 61 100% 1,618 100% 11,473
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 2 changes 0 changes 0 changes 0 changes
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

Quick numbers

1,618
Hosted words
61
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

Resource updated
The “pot/master/pages/core-concepts/upgrade-paths.pot” file was changed. a year ago
User avatar None

String updated in the repository
Add all nonmodular packages whose name is not on the list and which do not provide a name from the list to the pile of available packages. This step ensures that modular packages always have a higher priority than nonmodular ones. In other words, nonmodular packages can never upgrade modular packages unless explicitly unlisted by the stream.
Add all nonmodular packages whose name is not on the list and which do not provide a name from the list to the pile of available packages. This step ensures that modular packages always have a higher priority than nonmodular ones. In other words, nonmodular packages can never upgrade modular packages unless explicitly unlisted by the stream.
a year ago
User avatar None

Resource updated
The “pot/master/pages/core-concepts/upgrade-paths.pot” file was changed. 2 years ago
User avatar None

String updated in the repository
With a static context it's possible to use a xref:building-modules/fedora/module-obsoletes.adoc[`modulemd-obsoletes` document] to switch to a completely different stream. This is useful when you want to stop supporting an existing stream, or a context, and you provide a replacement. When user has installed an obsolete stream, or a context, DNF will offer switching to the replacement.
With a static context it's possible to use a xref:building-modules/fedora/module-obsoletes.adoc[`modulemd-obsoletes` document] to switch to a completely different stream. This is useful when you want to stop supporting an existing stream, or a context, and you provide a replacement. When user has installed an obsolete stream, or a context, DNF will offer switching to the replacement.
2 years ago
User avatar None

String updated in the repository
The same constrains of dynamic context and a strong recommendation for static context apply here. With static context you can stop building modules for that context whenever you want. With dynamic context you cannot and need to maintain the full matrix forever.
The same constrains of dynamic context and a strong recommendation for static context apply here. With static context you can stop building modules for that context whenever you want. With dynamic context you cannot and need to maintain the full matrix forever.
2 years ago
User avatar None

String updated in the repository
Removing a context
Removing a context
2 years ago
User avatar None

String updated in the repository
On the other hand, with a static context DNF will understand that modules from context `B` should not mix with module from a context `A`. When installing `perl-DBI:stream` for the first time, DNF will pick the right context based on an already installed `perl` stream. When upgrading `perl-DBI:stream`, DNF will preserve the context based on an already installed `perl-DBI:stream` context. Thus using static-context modules is recommended.
On the other hand, with a static context DNF will understand that modules from context `B` should not mix with module from a context `A`. When installing `perl-DBI:stream` for the first time, DNF will pick the right context based on an already installed `perl` stream. When upgrading `perl-DBI:stream`, DNF will preserve the context based on an already installed `perl-DBI:stream` context. Thus using static-context modules is recommended.
2 years ago
User avatar None

String updated in the repository
Upgrade path 1 Upgrade path 2
──────────────────── ────────────────────
perl-DBI:stream:2:A ↑ perl-DBI:stream:2:B ↑
requires perl:5.30 ↑ requires perl:5.32 ↑
↑ ┌────────────────────┐
perl-DBI:stream:1:A ↑ │perl-DBI:stream:1:B │ An artificial module build
requires perl:5.30 ↑ │ requires perl:5.32│ filling a gap in this matrix
└────────────────────┘
Upgrade path 1 Upgrade path 2
──────────────────── ────────────────────
perl-DBI:stream:2:A ↑ perl-DBI:stream:2:B ↑
requires perl:5.30 ↑ requires perl:5.32 ↑
↑ ┌────────────────────┐
perl-DBI:stream:1:A ↑ │perl-DBI:stream:1:B │ An artificial module build
requires perl:5.30 ↑ │ requires perl:5.32│ filling a gap in this matrix
└────────────────────┘
2 years ago
User avatar None

String updated in the repository
It's not possible to achieve this by standard means with a dynamic context. DNF would report https://bugzilla.redhat.com/show_bug.cgi?id=1708589[a warning] or https://bugzilla.redhat.com/show_bug.cgi?id=1757460[an error]. If you ever needed to achieve this with nonstatic contexts, the key point how to indulge DNF is fill a matrix of contexts and versions with artificial modules which have never been built (i.e. manually writing the modulemd documents):
It's not possible to achieve this by standard means with a dynamic context. DNF would report https://bugzilla.redhat.com/show_bug.cgi?id=1708589[a warning] or https://bugzilla.redhat.com/show_bug.cgi?id=1757460[an error]. If you ever needed to achieve this with nonstatic contexts, the key point how to indulge DNF is fill a matrix of contexts and versions with artificial modules which have never been built (i.e. manually writing the modulemd documents):
2 years ago
User avatar None

String updated in the repository
Upgrade path A Upgrade path B
──────────────────── ────────────────────
perl-DBI:stream:2:A ↑ perl-DBI:stream:2:B ↑
requires perl:5.30 ↑ requires perl:5.32 ↑
perl-DBI:stream:1:A ↑
requires perl:5.30 ↑
╰──────────────────╯ ╰──────────────────╯
Old context New context
Upgrade path A Upgrade path B
──────────────────── ────────────────────
perl-DBI:stream:2:A ↑ perl-DBI:stream:2:B ↑
requires perl:5.30 ↑ requires perl:5.32 ↑
perl-DBI:stream:1:A ↑
requires perl:5.30 ↑
╰──────────────────╯ ╰──────────────────╯
Old context New context
2 years ago
Browse all translation changes