- 25 9月, 2021 1 次提交
-
-
由 Ansgar 提交于
Expliclty inheriting from `object` was needed in Python 2 for new-style classes, but is no longer needed in Python 3 where all classes implicitly inherit from `object`.
-
- 25 8月, 2021 6 次提交
- 14 8月, 2021 1 次提交
-
-
由 Ansgar 提交于
-
- 22 6月, 2021 1 次提交
-
-
由 Youngtaek Yoon 提交于
The default mode is 'rt', which leads `copyfileobj()` to failure.
-
- 04 3月, 2021 1 次提交
-
-
由 Dominic Hargreaves 提交于
-
- 25 2月, 2021 1 次提交
-
-
由 Ansgar 提交于
-
- 16 1月, 2021 3 次提交
- 31 12月, 2020 4 次提交
- 30 12月, 2020 1 次提交
-
-
由 Ansgar 提交于
-
- 19 12月, 2020 1 次提交
-
-
由 Niels Thykier 提交于
Signed-off-by: NNiels Thykier <niels@thykier.net>
-
- 16 12月, 2020 2 次提交
- 15 12月, 2020 2 次提交
-
-
由 Ansgar 提交于
This should also ensure that the warning is not reported by the test suite as we want to see it.
-
- 13 12月, 2020 1 次提交
-
-
由 Stephane Blondon 提交于
The DeprecationWarnings are 'comparison with a `str` is deprecated'. Signed-off-by: NStéphane Blondon <sblondon@debian.org>
-
- 12 12月, 2020 1 次提交
-
-
由 Niels Thykier 提交于
Due to a previous bug in dak, the pdiff history in Debian experimental is currently misaligned. Unfortunately, dak is not self-healing with this kind of history corruption (but it had been if the field order had been different). This patch will have dak detect misaligned patch histories (where e.g. `SHA1-Patches` and `SHA256-Patches` disagree on the order) and attempt to re-align them. We re-align by looking from the end of the two misaligned histories and keep all the patches they have in common. This is done on the basis that we keep adding patches at the end, so the history should be aligned there (assumping relevant bug fixes for the corruption source have implemented). Once we discover a difference, we discard that and all older patches. This is a deliberate choice as our PDiff code assumes that the history is in order without any gaps (plus it was easier that way). In the worst case, this will reset the entire history and slow rebuild from there. Note that we repair unmerged and merged histories separately. This can cause one series to have more patches than the other. This is mostly a non-issue as dak will cope with it (as long as both series are consistent internally). Signed-off-by: NNiels Thykier <niels@thykier.net>
-
- 11 12月, 2020 1 次提交
-
-
由 Stephane Blondon 提交于
-
- 10 12月, 2020 1 次提交
-
-
由 Ansgar 提交于
This was suggested by the python-apt maintainer to work around #977000.
-
- 09 12月, 2020 2 次提交
-
-
由 Niels Thykier 提交于
Signed-off-by: NNiels Thykier <niels@thykier.net>
-
由 Niels Thykier 提交于
Signed-off-by: NNiels Thykier <niels@thykier.net>
-
- 05 12月, 2020 5 次提交
-
-
由 Ansgar 提交于
With the "daklib.daksubprocess" module gone, some modules no longer saw the "daklib" modules, but tried to access other modules under it which then failed.
-
由 Ansgar 提交于
-
由 Ansgar 提交于
Since Python 3.2 the standard subprocess modules restores the signal handler to `SIG_DFL` by default.
-
由 Ansgar 提交于
-
由 Ansgar 提交于
-
- 26 11月, 2020 1 次提交
-
-
由 Ansgar 提交于
-
- 24 11月, 2020 1 次提交
-
-
由 Ansgar 提交于
-
- 08 11月, 2020 2 次提交
-
-
由 Niels Thykier 提交于
Signed-off-by: NNiels Thykier <niels@thykier.net>
-
由 Niels Thykier 提交于
Signed-off-by: NNiels Thykier <niels@thykier.net>
-
- 07 11月, 2020 1 次提交
-
-
由 Niels Thykier 提交于
Signed-off-by: NNiels Thykier <niels@thykier.net>
-