- Feb 06, 2023
-
-
Jean-Pierre Giraud authored
[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>
-
Remus-Gabriel Chelu authored
Signed-off-by:
Guillem Jover <guillem@debian.org>
-
Theppitak Karoonboonyanan authored
Signed-off-by:
Guillem Jover <guillem@debian.org>
-
Nagy Elemér Károly authored
Signed-off-by:
Guillem Jover <guillem@debian.org>
-
Quentin PAGÈS authored
Signed-off-by:
Guillem Jover <guillem@debian.org>
-
Yuri Kozlov authored
[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>
-
Sangdo Jun authored
Signed-off-by:
Guillem Jover <guillem@debian.org>
-
Peter Krefting authored
Signed-off-by:
Guillem Jover <guillem@debian.org>
-
Cheng-Chia Tseng authored
Signed-off-by:
Guillem Jover <guillem@debian.org>
-
Boyuan Yang authored
Signed-off-by:
Guillem Jover <guillem@debian.org>
-
jonatan porras authored
Signed-off-by:
Guillem Jover <guillem@debian.org>
-
Miroslav Kure authored
Closes: #1029706, #1030267 Signed-off-by:
Guillem Jover <guillem@debian.org>
-
Guillem Jover authored
-
Peter Krefting authored
Signed-off-by:
Guillem Jover <guillem@debian.org>
-
Guillem Jover authored
-
Guillem Jover authored
There was a missing 1 in the version. Fixes: commit b21501dd Closes: #1030288
-
Guillem Jover authored
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.
-
- Jan 25, 2023
-
-
Guillem Jover authored
-
- Jan 24, 2023
-
-
Guillem Jover authored
-
Guillem Jover authored
-
Guillem Jover authored
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
-
Shengjing Zhu authored
[guillem@debian.org: Fix typos in comments. ] Ref: https://bugs.launchpad.net/bugs/2002582 Signed-off-by:
Guillem Jover <guillem@debian.org>
-
Guillem Jover authored
The recently added lto handling for Ubuntu, did not take into account that the DEB_BUILD_OPTIONS and DEB_BUILD_MAINT_OPTIONS environment variables are parsed and their options applied just after setting the defaults, and before applying any arch-specific mask. We add a new init_build_features() internal method, which sits between these two actions, so that the Ubuntu vendor module can modify the defaults before any user or maintainer override are applied. Fixes: commit df7627ac Fixes: https://bugs.launchpad.net/bugs/2002582
-
- Jan 16, 2023
-
-
Guillem Jover authored
The source ChangeLog.old file might have different permissions depending on the umask during the source package unpack. Copy the file without any flags, and then explicitly set known permissions on the result file. This should fix the build on reproducible variants. Fixes: commit 2c2f7066
-
Guillem Jover authored
When verifying a signature, we were using the internal dearmor() method, as that makes it possible to not have gpg around when we are using gpgv. The problem is that the internal dearmor() method does not handle concatenated ASCII Armor blocks, and might then fail to find the certificates. When using gpgv this is only a partial regression as we were previously not verifying at all on minimal systems where gpg was not available. But when it is available, now that has regressed. In the future we might require no concatenated ASCII Armor blocks, but for now let's mitigate this regression. Fixes: commit a11d7340 Reported-by: Sven Joachim <svenjoac@gmx.de> (on IRC)
-
Guillem Jover authored
The gpgv command expects a trustedkeys.gpg keyring, and if there is none it will try the trustedkeys.kbx one, but then will emit an error such as: gpgv: unknown type of key resource 'trustedkeys.kbx' gpgv: keyblock resource '<GPGHOME>/trustedkeys.kbx': General error This error will only show if the gpgv invocation failed for other reasons, but it is still an unnecessary distraction. Avoid that error, by touching the trustedkeys.gpg keyring.
-
- Jan 15, 2023
-
-
Américo Monteiro authored
Closes: #1028981 Signed-off-by:
Guillem Jover <guillem@debian.org>
-
Guillem Jover authored
The current GnuPG defaults with --openpgp cater for heavy backwards compatibility at the cost of being insecure but potentially being compatible with very old programs. We care more about secure defaults than backwards compatibility with ancient programs, so we pass our preferences to gpg when signing. This should also cover the case for users that have created old keys with insecure key preferences which might end up producing insecure signatures. Fixes: commit b83114da Closes: #1028961
-
Guillem Jover authored
-
- Jan 11, 2023
-
-
Helge Kreutzmann authored
-
- Jan 10, 2023
-
-
Sven Joachim authored
Update to 1184t.
-
Guillem Jover authored
-
Guillem Jover authored
-
Guillem Jover authored
-
Guillem Jover authored
-
Guillem Jover authored
Closes: #1008486
-
Guillem Jover authored
This adds support for .deb ZStandard compression and decompression. The main reason for this addition is due to Ubuntu having forked the .deb ecosystem when they added support for this unilaterally, so now there are many .deb in the wild using this compression format, which cannot be handled by the upstream dpkg-deb tool. Although at least now the ZStandard format is widely used on many projects, has been specified within the IETF as RFC8878, so backwards compatibility and format stability are no longer a concern, and it has good trade offs between size and speed. This has been implemented from scratch, based on the initial prototype code used during the early request evaluation. Using the new advanced API, with support for multi-threading, and using an I/O loop resembling the one used with liblzma, as the plan is to eventually switch all compressors to use a single I/O loop implementation. Closes: #892664
-
Guillem Jover authored
Use a new enum dpkg_stream_status to track the stream status, instead of using the liblzma codes directly in the I/O loop, which will make it possible in the future to generalize and use a single loop for all compressors.
-
Guillem Jover authored
Stop handling the xz/lzma actions using the liblzma specific actions, and use a generic enum, renamed from the old dpkg_stream_status, which was in fact partially handling the action. This will make it easier in the future to use the same action for all compressors.
-
Guillem Jover authored
Tracking the compression filter operation and its status merges two distinct values into the same variable making things more difficult, as we were using bits when these should really be mutually exclusive values.
-