When dealing with virtual packages (such as the ones from Provides, or
for not-installed Recommends or Suggests), there might be no version
field at all, so we cannot assume we can use these when filling in the
version information in the fallback code handling the missing Source
field.

The commit that removed the check for not-installed packages missed that
this instance had not been protected, as the code in varbufversion() is
doing the correct thing, but unfortunately we are not using that because
we need to get at the upstream part, so we need to also check explicitly
for a non-NULL upstream part. This was causing a segfault.

Fixes: commit 560574b5
Stable-Candidates: 1.20.x 1.21.x
Reported-by: John Scott <jscott@posteo.net>
(cherry picked from commit 2c4814f7)

[guillem@debian.org: Hook into build system. ]

Closes: #1032562
Signed-off-by: Guillem Jover <guillem@debian.org>
(cherry picked from commit 0e56a85c)

This reverts commit f9187c8b.

This reintroduces the loong64 CPU support that got reverted. The GNU
triplet and the multiarch tuples have gone back upstream to the previous
agreed names.

Closes: #1028654
(cherry picked from commit 4c9e67b5)

Signed-off-by: Guillem Jover <guillem@debian.org>
(cherry picked from commit f36a5944)

This caused the author checks to fail, and consequently the CI pipelines
too. Unfortunately the release script did not catch this, probably due
to not properly installing the build dependencies.

Warned-by: i18nspector
(cherry picked from commit a436a216)

Signed-off-by: Guillem Jover <guillem@debian.org>

Closes: #1030712
Signed-off-by: Guillem Jover <guillem@debian.org>

Closes: #1030710, #1030711
Signed-off-by: Guillem Jover <guillem@debian.org>

This kind of file includes translated entries, which causes spelling
check false positives, and makes the author tests and CI systems
checking those fail.

The non-breaking space before the colon seems to be confusing po4a which
ends up using it for all subsequent spaces within the I<> markup. Move
the non-breaking space outside the I<> markup to avoid the issue.

Warned-by: lintian

[guillem@debian.org:
 - Fix missing format specifier conversion characters. ]

Signed-off-by: Guillem Jover <guillem@debian.org>

[guillem@debian.org:
 - Remove trailing newline from translation.
 - Fix end-of-line withing string syntax errors.
 - Add missing closing angle for POD markup. ]

Closes: #1030618
Signed-off-by: Guillem Jover <guillem@debian.org>

Signed-off-by: Guillem Jover <guillem@debian.org>

Signed-off-by: Guillem Jover <guillem@debian.org>

Signed-off-by: Guillem Jover <guillem@debian.org>

Signed-off-by: Guillem Jover <guillem@debian.org>

[guillem@debian.org:
 - Remove trailing newline from translation.
 - Fix translations with mismatched format specifiers. ]

Closes: #1030162, #1030378
Signed-off-by: Guillem Jover <guillem@debian.org>

Signed-off-by: Guillem Jover <guillem@debian.org>

Signed-off-by: Guillem Jover <guillem@debian.org>

Signed-off-by: Guillem Jover <guillem@debian.org>

Signed-off-by: Guillem Jover <guillem@debian.org>

Signed-off-by: Guillem Jover <guillem@debian.org>

Closes: #1029706, #1030267
Signed-off-by: Guillem Jover <guillem@debian.org>

Signed-off-by: Guillem Jover <guillem@debian.org>

There was a missing 1 in the version.

Fixes: commit b21501dd
Closes: #1030288

Some of these are valid, but we'll fix them in the soon to open 1.22.x
series. This should make the CI systems based on Debian unstable
checking author mode, get back to normal.

This reverts commit 321e479b.

This arch which was supposedly already defined, with an agreed ABI,
GNU triplet and dpkg multiarch paths, seems to want to redefine all
these. There is no clear rationale for why this is happening at this
point in time, while patches for at least gcc have been submitted
with no coordination (which ended up being applied).

The handling of this is less than ideal. Until the whole situation
gets clarified, the safest way is to revert the support. It can be
reintroduced once things clear out.

Ref: #1028654