Bug#1043103: Package data not updated since August 4th
The package data on available via NFS on ullmann.d.o hasn't been updated since August 4th as reported in #1043103: " sebastic@ullmann:~$ ls -l /auto.dsa/debian/ls-lR.gz -rw-r--r-- 1 1176 1176 14092271 Aug 4 20:16 /auto.dsa/debian/ls-lR.gz deb.debian.org has 2023-08-06 02:57 for ls-lR.gz. " We see the same on coccia: sebastic@coccia:~$ ls -l /srv/ftp-master.debian.org/mirror/ls-lR.gz -rw-r--r-- 1 1176 1176 14092271 Aug 4 20:16 /srv/ftp-master.debian.org/mirror/ls-lR.gz Can you have a look why these archive copies aren't updated? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1043103: qa.debian.org: DDPO does not update package information
On 8/6/23 07:15, Bas Couwenberg wrote: DDPO does not update the package information for unstable at least. Neither does DMD, this suggests an issue with UDD. spatialite (5.1.0-1) & spatialite-tools (5.1.0-1) are in unstable but still shows spatialite (5.0.1-3) & spatialite-tools (5.0.1-2) in stable, testing, unstable. ullmann.debian.org:/auto.dsa/debian/dists/sid/main/binary-amd64/Packages.gz does not have these yet, but the mirrors do. It seems like the package data hasn't been updated since August 4th: sebastic@ullmann:~$ ls -l /auto.dsa/debian/ls-lR.gz -rw-r--r-- 1 1176 1176 14092271 Aug 4 20:16 /auto.dsa/debian/ls-lR.gz deb.debian.org has 2023-08-06 02:57 for ls-lR.gz. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1043045: transition: spatialite
On 8/5/23 15:50, Sebastian Ramacher wrote: Please go ahead. Thanks. spatialite (5.1.0-1) has been uploaded to unstable and is built & installed on all release architectures. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1041457: python-escript: FTBFS on i386
Control: severity -1 important python-escript was removed from i386 (#1042939). Reducing the severity accordingly. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1042725: qgis-providers: upgrade of qgis will create /.cache/crssync at the root of system
Control: tags -1 pending On 7/31/23 09:35, Alexandre Detiste wrote: Sometimes, the upgrade of the QGIS toolkit through unattended-upgrades will create some garbage empty dirs a the root of the filesystem. This was fixed for .config some time ago: https://github.com/qgis/QGIS/issues/44793 Sadly I cannot reproduce this. Neither can I. Can you please: - try to mitigate this problem by setting $HOME to /tmp before calling crssync That we can do. - clean-up existing systems. "find /.cache -type -d -empty -delete" should be harmless. That we won't. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1037925: [Pkg-nagios-devel] Bug#1037925: not resolved
On 7/30/23 18:12, Folkert van Heusden wrote: * clean debian bookworm install * install icingaweb2 and the other icinga packages * trying to configure mysql via the web-interface * get tons of deprecation warnings that make the web-interface unusable: https://vanheusden.com/permshare/debian-icinga2.png Try configuring the .ini files manually: https://icinga.com/docs/icinga-web/latest/doc/03-Configuration/#configuration-general Or patch the file in question to fix the dynamic property. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1042494: otb still uses ITK 4
On 7/29/23 11:03, Adrian Bunk wrote: Forwarded: https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/1917 The MR linked from that issue got closed without being merged, there is another one which is still marked as WIP: https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/merge_requests/528 OTB 9.0 was supposed to get ITK5 support but this was postponed to OTB 10.0: https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2248 It's unclear when we can expect ITK5 support in OTB, so I think we should remove OTB from Debian to unblock the insighttoolkit4 removal. I don't use the package, and popcon shows only a handful of votes too. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1042428: qa.debian.org: Missing description for lintian warning tags (https://udd.debian.org/lintian/?packages=)
On 7/28/23 09:09, Christian Buhtz wrote: To less experienced users it is not clear what this tags do mean. The explanation should be linked somehow. You can get the tag description from lintian-explain-tags: $ lintian-explain-tags -t groff-message N: W: groff-message N: N: A manual page provoked warnings or errors from the man program. Here are some common ones: N: N: "cannot adjust" or "can't break" are issues with paragraph filling. They are usually related to long lines. Justifying text on the left hand side can help with adjustments. Hyphenation can help with breaks. N: N: For more information, please see "Manipulating Filling and Adjusting" and "Manipulating Hyphenation" in the Groff manual (see info groff). N: N: "can't find numbered character" usually means that the input was in a national legacy encoding. The warning means that some characters were dropped. Please use escapes such as \[:a] as described on the groff_char manual page. N: N: Other common warnings are formatting typos. String arguments to .IP require quotes. Usually, some text is lost or mangled. See the groff_man (or groff_mdoc if using mdoc) manual page for details on macros. N: N: The check for manual pages uses the --warnings option to man to catch common problems, like a . or a ' at the beginning of a line as literal text. They are interpreted as Groff commands. Just reformat the paragraph so the N: characters are not at the beginning of a line. You can also add a zero-width space (\&) in front of them. N: N: Aside from overrides, warnings can be disabled with the .warn directive. Please see "Debugging" in the Groff manual. N: N: You can see the warnings yourself by running the command used by Lintian: N: N: LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 \ N: man --warnings -E UTF-8 -l -Tutf8 -Z >/dev/null N: N: Please refer to the groff_man(7) manual page and the groff_mdoc(7) manual page for details. N: N: Visibility: warning N: Show-Always: no N: Check: documentation/manual N: Renamed from: manpage-has-errors-from-man N: Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1041906: RM: freecad [mipsel] -- RoQA; Blocks removal of qtwebengine-opensource-src
On 7/27/23 08:28, Petter Reinholdtsen wrote: [Bas Couwenberg] Please remove the package from mipsel to unblock the qtwebengine-opensource-src removal. I do not believe this removal is needed any more, as someone managed to get qtwebengine-opensource-src building on mipsel. The question whether or not to keep these RM bugreports open is outstanding, see: https://lists.debian.org/debian-release/2023/07/msg01025.html If I were the qtwebengine-opensource-src maintainer, I would upload a new revision without mipsel in its list of architectures now that it as migrated to testing to not have this issue repeat. But since mipsel is going away as a release architecture it won't affect testing migrations once its gone, that might still be quite some time away though. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1041948: RM: algobox [mipsel] -- RoQA; Blocks removal of qtwebengine-opensource-src
On 7/25/23 13:02, Petter Reinholdtsen wrote: [Bas Couwenberg] Please remove the package from mipsel to unblock the qtwebengine-opensource-src removal. I suspect freecad also will block this, as it has earlier been built with qtwebengine-opensource-src on mipsel, see https://tracker.debian.org/pkg/freecad >. Is there a BTS report about the mipsel build problem for qtwebengine-opensource-src? Yes: #1041250 qtwebengine-opensource-src: FTBFS on mipsel Related RM bugreports: #1041268 RM: qtwebengine-opensource-src [mipsel] -- RoQA; FTBFS on mipsel #1041906 RM: freecad [mipsel] -- RoQA; Blocks removal of qtwebengine-opensource-src Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1041633: cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH
Control: tags -1 pending On 7/23/23 15:26, Timo Röhling wrote: It is the package maintainer's responsibility to set DEB_PYTHON_INSTALL_LAYOUT=deb in d/rules, either implicitly through the use of pybuild, or explicitly with "export DEB_PYTHON_INSTALL_LAYOUT", as you already did in Salsa. The advise for packages should be DEB_PYTHON_INSTALL_LAYOUT=deb_system based on the python3 changelog as that's intended for package builds. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1041760: src:python-geopandas: unsatisfied build dependency in testing: python3-pyepsg
On 7/23/23 09:07, Paul Gevers wrote: Can you please investigate the situation and figure out how to resolve it? python-pyepsg is affected by an RC issue [2] and has been removed from testing, you could help its maintainers to solve the issue. python-geopandas was marked for autoremoval from testing due to the RC bug affecting python-pyepsg but then wasn't. That suggests an issue in britney. pyepsg doesn't appear to be used anymore although it's still referenced in documentation. I'll drop the build dependency to resolve this issue. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1041633: cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH
Changes between bookworm and sid:
cmake 3.25.1:
``Python_SITELIB``
Third-party platform independent installation directory.
Information returned by
``distutils.sysconfig.get_python_lib(plat_specific=False,standard_lib=False)``
or else ``sysconfig.get_path('purelib')``.
``Python_SITEARCH``
Third-party platform dependent installation directory.
Information returned by
``distutils.sysconfig.get_python_lib(plat_specific=True,standard_lib=False)``
or else ``sysconfig.get_path('platlib')``.
cmake 3.27.0:
``Python_SITELIB``
Third-party platform independent installation directory.
Information returned by ``sysconfig.get_path('purelib')``.
``Python_SITEARCH``
Third-party platform dependent installation directory.
Information returned by ``sysconfig.get_path('platlib')``.
On bookworm distutils is still used which returns:
>>> distutils.sysconfig.get_python_lib(
plat_specific=False,
standard_lib=False,
)
'/usr/lib/python3/dist-packages'
On sid sysconfig is used which results:
>>> sysconfig.get_path('platlib')
'/usr/local/lib/python3.11/dist-packages'
To get the right path for the Debian python3 interpreter,
you need to add 'deb_system':
>>> sysconfig.get_path('platlib', 'deb_system')
'/usr/lib/python3/dist-packages'
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1040780: [Pkg-nagios-devel] Bug#1040780: icingaweb2 incompatible with php8.2
forcemerge 1040780 1037925 thanks On 7/10/23 15:36, David Kunz wrote: It would be nice if you could update this package for using with php8.2. It has been: https://salsa.debian.org/nagios-team/icingaweb2/-/blob/master/debian/patches/php8.2.patch This issue is a duplicate of #1037925. The deprecation notices should not prevent icingaweb2 from working. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1040634: pycoast autopkg tests fail with pillow 10.0.0
On 7/8/23 09:31, Matthias Klose wrote:
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pycoast/35498778/log.gz
[...]
101s self =
101s draw =
101s position = (8.56126709559166, 4), txt = '50W'
101s font = , align
= 'CT'
101s kwargs = {'fill': 'white', 'lat_placement': 'lr', 'lon_placement':
'tb', 'minor_is_tick': True, ...}
101s
101s def _draw_text(self, draw, position, txt, font, align="cc",
**kwargs):
101s """Draw text with agg module."""
101s > txt_width, txt_height = draw.textsize(txt, font)
101s E AttributeError: 'ImageDraw' object has no attribute 'textsize'
101s
101s ../build.wr6/src/pycoast/cw_base.py:170: AttributeError
From the upstream changelog:
Removed
ImageDraw.textsize() and
ImageDraw.multiline_textsize()
Use instead
ImageDraw.textbbox(),
ImageDraw.textlength() and
ImageDraw.multiline_textbbox()
https://pillow.readthedocs.io/en/stable/releasenotes/10.0.0.html#font-size-and-offset-methods
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1040554: grass-dev-doc: missing Depends: libjs-jquery
Control: tags -1 pending On 7/7/23 17:42, Andreas Beckmann wrote: Is grass-dev-doc missing a dependency on libjs-jquery ? Yes, fixed in git. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1039664: closed by Andreas Tille (Re: Bug#1039664: r-cran-tikzdevice: autopkgtest failure with r-base (4.3.1-1))
Andreas Tille wrote: Done in 0.12.4-3 This does not mark the bug as fixed in that version. Use a version header at the top of your email: Version: 0.12.4-3 Or use the control commands: https://www.debian.org/Bugs/server-control#fixed Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1040361: python3-fiona: do not ship /usr/lib/python3/dist-packages/docs/conf.py
Control: tags -1 upstream pending Control: forwarded -1 https://github.com/Toblerity/Fiona/pull/1272 Control: block -1 by 1040316 On 7/5/23 05:38, Sebastiaan Couwenberg wrote: On 7/4/23 22:27, Helmut Grohne wrote: python3-fiona contains /usr/lib/python3/dist-packages/docs/conf.py. It's not just that: /usr/lib/python3/dist-packages/docs/ /usr/lib/python3/dist-packages/docs/conf.py /usr/lib/python3/dist-packages/examples/ /usr/lib/python3/dist-packages/examples/open.py /usr/lib/python3/dist-packages/examples/orient-ccw.py /usr/lib/python3/dist-packages/examples/with-descartes-functional.py /usr/lib/python3/dist-packages/examples/with-descartes.py /usr/lib/python3/dist-packages/examples/with-pyproj.py /usr/lib/python3/dist-packages/examples/with-shapely.py /usr/lib/python3/dist-packages/scripts/ /usr/lib/python3/dist-packages/scripts/check_deprecated.py /usr/lib/python3/dist-packages/scripts/check_urls.py We should have a lintian check that complains about files outside of /usr/lib/python*/dist-packages/, this won't be last time this happens. I've patched pyproject.toml to not include the .py files outside the fiona toplevel directory, but when I forwarded it upstream I found that they already fixed it. The fix will be uploaded once python3-defaults is fixed in unstable, 3.11.4-4 has not reached the mirrors yet. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1040361: python3-fiona: do not ship /usr/lib/python3/dist-packages/docs/conf.py
On 7/4/23 22:27, Helmut Grohne wrote: python3-fiona contains /usr/lib/python3/dist-packages/docs/conf.py. It's not just that: /usr/lib/python3/dist-packages/docs/ /usr/lib/python3/dist-packages/docs/conf.py /usr/lib/python3/dist-packages/examples/ /usr/lib/python3/dist-packages/examples/open.py /usr/lib/python3/dist-packages/examples/orient-ccw.py /usr/lib/python3/dist-packages/examples/with-descartes-functional.py /usr/lib/python3/dist-packages/examples/with-descartes.py /usr/lib/python3/dist-packages/examples/with-pyproj.py /usr/lib/python3/dist-packages/examples/with-shapely.py /usr/lib/python3/dist-packages/scripts/ /usr/lib/python3/dist-packages/scripts/check_deprecated.py /usr/lib/python3/dist-packages/scripts/check_urls.py We should have a lintian check that complains about files outside of /usr/lib/python*/dist-packages/, this won't be last time this happens. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1039871: python-xarray: FTBFS (PermissionError: [Errno 13] Permission denied: '/sbuild-nonexistent')
Control: tags -1 patch The attached patch resolves the FTBFS by nbsphinx_allow_errors = False from doc/conf.py Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1diff -Nru python-xarray-2023.06.0/debian/changelog python-xarray-2023.06.0/debian/changelog --- python-xarray-2023.06.0/debian/changelog2023-06-27 15:47:04.0 +0200 +++ python-xarray-2023.06.0/debian/changelog2023-06-29 06:58:55.0 +0200 @@ -1,3 +1,11 @@ +python-xarray (2023.06.0-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Add patch to fix FTBFS. +(closes: #1039871) + + -- Bas Couwenberg Thu, 29 Jun 2023 06:58:55 +0200 + python-xarray (2023.06.0-1) unstable; urgency=medium * New upstream release diff -Nru python-xarray-2023.06.0/debian/patches/series python-xarray-2023.06.0/debian/patches/series --- python-xarray-2023.06.0/debian/patches/series 2023-06-27 15:47:04.0 +0200 +++ python-xarray-2023.06.0/debian/patches/series 2023-06-29 06:55:24.0 +0200 @@ -12,3 +12,4 @@ xfail-pad-constant.patch no-sphinx-design.patch xfail-on-random-patch +xarray_tutorial_data.patch diff -Nru python-xarray-2023.06.0/debian/patches/xarray_tutorial_data.patch python-xarray-2023.06.0/debian/patches/xarray_tutorial_data.patch --- python-xarray-2023.06.0/debian/patches/xarray_tutorial_data.patch 1970-01-01 01:00:00.0 +0100 +++ python-xarray-2023.06.0/debian/patches/xarray_tutorial_data.patch 2023-06-29 06:58:55.0 +0200 @@ -0,0 +1,16 @@ +Description: Fix FBTBFS, docs write to $HOME. +Author: Bas Couwenberg +Bug-Debian: https://bugs.debian.org/1039871 +Forwarded: not-needed + +--- a/doc/conf.py b/doc/conf.py +@@ -63,8 +63,6 @@ except ImportError: + ] + ) + +-nbsphinx_allow_errors = False +- + # -- General configuration + + # If your documentation needs a minimal Sphinx version, state it here.
Bug#1038115: transition: gdal
On 6/23/23 10:45, Sebastiaan Couwenberg wrote: On 6/21/23 12:31, Sebastiaan Couwenberg wrote: On 6/20/23 23:49, Sebastian Ramacher wrote: On 2023-06-15 17:15:27 +0200, Bas Couwenberg wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: g...@packages.debian.org Control: affects -1 + src:gdal Control: forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html Control: block -1 by 1030129 998833 1037920 984398 1037976 For the Debian GIS team I'd like to transition to GDAL 3.7.0. Please go ahead. gdal (3.7.0+dfsg-1) has been uploaded to unstable and is now built & installed on all release architectures. Please also binNMU mysql-workbench which builds successfully now that the ca-certificates-java workaround is in unstable. mysql-workbench still needs to be rebuilt in unstable. r-base is blocking testing migration of r-cran-rgdal/r-cran-sf/r-cran-terra which in turn prevents the removal of libgdal32 from testing. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1038733: r-cran-rgeos: autopkgtest failure with GEOS 3.12
severity 1038733 serious thanks GEOS 3.12.0 is now in unstable, raising the severity accordingly. Testing migration of r-cran-rgeos (0.6-3-1) is blocked by r-base which in turn is blocked by autopkgtest failures of quite a few rdeps. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1039446: python3-qgis: please remove obsolete dependency on python3-six
Control: tags -1 pending The dependency is dropped in git. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1039095: owslib: Homepage: is outdated
Control: tags -1 pending This is fixed in git. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1038115: transition: gdal
On 6/21/23 12:31, Sebastiaan Couwenberg wrote: On 6/20/23 23:49, Sebastian Ramacher wrote: On 2023-06-15 17:15:27 +0200, Bas Couwenberg wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: g...@packages.debian.org Control: affects -1 + src:gdal Control: forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html Control: block -1 by 1030129 998833 1037920 984398 1037976 For the Debian GIS team I'd like to transition to GDAL 3.7.0. Please go ahead. gdal (3.7.0+dfsg-1) has been uploaded to unstable and is now built & installed on all release architectures. Please also binNMU mysql-workbench which builds successfully now that the ca-certificates-java workaround is in unstable. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1038115: transition: gdal
On 6/21/23 12:31, Sebastiaan Couwenberg wrote: On 6/20/23 23:49, Sebastian Ramacher wrote: On 2023-06-15 17:15:27 +0200, Bas Couwenberg wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: g...@packages.debian.org Control: affects -1 + src:gdal Control: forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html Control: block -1 by 1030129 998833 1037920 984398 1037976 For the Debian GIS team I'd like to transition to GDAL 3.7.0. Please go ahead. gdal (3.7.0+dfsg-1) has been uploaded to unstable and is now built & installed on all release architectures. To make the libgdal-grass autopkgtest pass it needs both gdal and libgdal-grass from unstable. I've scheduled jobs for this, but it seems britney ignores tests it hasn't scheduled itself. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1038115: transition: gdal
On 6/20/23 23:49, Sebastian Ramacher wrote: On 2023-06-15 17:15:27 +0200, Bas Couwenberg wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: g...@packages.debian.org Control: affects -1 + src:gdal Control: forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html Control: block -1 by 1030129 998833 1037920 984398 1037976 For the Debian GIS team I'd like to transition to GDAL 3.7.0. Please go ahead. gdal (3.7.0+dfsg-1) has been uploaded to unstable and is now built & installed on all release architectures. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1038735: python3-mapscript: python hook /usr/share/doc content (Policy 12.3): /usr/share/doc/python3-mapscript/examples/__init__.py
Control: tags -1 pending On 6/20/23 19:05, Andreas Beckmann wrote: This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. From the attached log (scroll to the bottom...): Setting up python3 (3.11.2-1+b1) ... [Errno 2] No such file or directory: '/usr/share/doc/python3-mapscript/examples/__init__.py'error running python rtupdate hook python3-mapscript dpkg: error processing package python3 (--configure): installed python3 package post-installation script subprocess returned error exit status 4 Setting up libgdal32 (3.6.4+dfsg-1) ... dpkg: dependency problems prevent configuration of python3-mapscript: python3-mapscript depends on python3 (<< 3.12); however: Package python3 is not configured yet. In this case it's probably sufficient to exclude the examples from the hook. This is done by dh_python3: # Automatically added by dh_python3 if command -v py3compile >/dev/null 2>&1; then py3compile -p python3-mapscript:amd64 /usr/share/doc/python3-mapscript/examples fi if command -v pypy3compile >/dev/null 2>&1; then pypy3compile -p python3-mapscript:amd64 /usr/share/doc/python3-mapscript/examples || true fi dh_python3 is used to rewrite the shebang, we'll just ignore the example-unusual-interpreter lintian issue then. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1038650: closed by Sebastiaan Couwenberg (Re: Bug#1038650: libnetcdf19: build support for parallel io)
On 6/19/23 20:02, Drew Parsons wrote: On 2023-06-19 19:51, Sebastiaan Couwenberg : No, see prior discussion on the debian-gis list: https://lists.debian.org/debian-gis/2018/04/msg00020.html Ok, thanks for the reference. If you need MPI netcdf, use netcdf-parallel: https://tracker.debian.org/pkg/netcdf-parallel That makes sense. What I'm really looking for is the parallel support in the python module, python3-netcdf4, so I filed this bug against the wrong package. Multiple builds of the python package might be a bit trickier to manage. It was done for h5py, with some effort. Like netcdf, I'm not willing to maintain MPI support in netcdf4-python. Ideally netcdf upstream support building both serial and parallel variants of the library, and having both installed. Library users can then choose which is best for their use case. This is something upstream needs to support. As long as we need to choose one or the other for the package in Debian, we will choose the serial variant as the lowest common denominator. This also has the bonus of not having to bother choosing an MPI implementation. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1038624: netcdf-cxx-legacy: Should not be included in trixie
Patches have been submitted for the netcdf-cxx-legacy rdeps. The netcdf-cxx-legacy-rm usertag tracks these bugreports: https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-...@lists.debian.org&tag=netcdf-cxx-legacy-rm
Bug#1013153: camitk: vtk[6,7] removal
On Fri, 10 Feb 2023 20:53:17 +0100 Pierre Gruet wrote: Sorry I was not able to look at it before. Anyway, I pushed changed to the Salsa repo, we have 22 tests failing now (hey, that's better). Among them: 18 segfaults and 4 failures (3 of them being differences between an output file and a reference one). Would you consider doing a nocheck upload to unstable to unblock the vtk7 removal? The FTBFS on the buildds and autopkgtest failures would keep blocking testing migration until the vtk9 support is fully fixed. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1038614: vtk9: Stop using netcdf-cxx-legacy
Control: tags -1 pending This is fixed in the experimental branch: https://salsa.debian.org/science-team/vtk9/-/commit/b4d5c6bf1de79c3ef0e75cd94d176f0c2fbc99f4 Anton, please pull the changes to ensure they're included when you move the package from experimental to unstable. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#996976: vtk6: Remove vtk6 from the Debian 12
itksnap is the only remain rdep of vtk6: sebastic@coccia:~$ dak rm -Rn vtk6 Will remove the following packages from unstable: libvtk6-dev | 6.3.0+dfsg2-8.1+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x libvtk6-qt-dev | 6.3.0+dfsg2-8.1+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x libvtk6.3 | 6.3.0+dfsg2-8.1+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x libvtk6.3-qt | 6.3.0+dfsg2-8.1+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x vtk6 | 6.3.0+dfsg2-8.1 | source Maintainer: Debian Science Team --- Reason --- -- Checking reverse dependencies... # Broken Depends: itksnap: itksnap [amd64 i386] # Broken Build-Depends: itksnap: libvtk6-dev Dependency problem found. The maintainer has not responded to the RC bugs affecting itksnap (#1013152 & #1010549). itksnap should be removed from Debian along with vtk6, or itksnap should be update to 4.0 which claims to support VTK 9: " * Updated library references to ITK 5, VTK 9, and Qt 6 " https://github.com/pyushkevich/itksnap/blob/v4.0.0/ReleaseNotes.md#version-400 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1037925: [Pkg-nagios-devel] Bug#1037925: I also get this on Arm64/aarch64
On 6/16/23 17:40, Ralph Aichinger wrote: I would love to do the Removing the .ini files I ran the wizard again. workaround, but I don't understand which .ini files I should remove, and if I should do something else in addition (downgrade PHP?). The icingaweb2 setup generates the ini files under: /etc/icingaweb2/ Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1037925: [Pkg-nagios-devel] Bug#1037925: icingacli: Icinga is not compatible with php8.2
On 6/15/23 15:46, Gabriel Rolland wrote: But it keeps giving me error of deprecated functions. It should not be an error. E_DEPRECATED is excluded from error reporting in the default php.ini configuration: error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT Deprecated: Creation of dynamic property Zend_Validate_NotEmpty::$zfBreakChainOnFailure is deprecated in /usr/share/icingaweb2/library/vendor/Zend/Form/Element.php on line 2176 Where do you get this message? Which page in icingaweb2 needs to be visited? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1037925: [Pkg-nagios-devel] Bug#1037925: icingaweb2: Same problem here
On 6/14/23 15:39, Gabriel Rolland wrote: - Deprecated: Creation of dynamic property Zend_Validate_NotEmpty::$zfBreakChainOnFailure is deprecated in /usr/share/icingaweb2/library/vendor/Zend/Form/Element.php on line 2176 [proxy_fcgi:error] [pid 349605] [client 192.168.111.3:59922] AH01071: Got error 'PHP message: PHP Deprecated: Creation of dynamic property Zend_Validate_NotEmpty::$zfBreakChainOnFailure is deprecated in /usr/share/icingaweb2/libra ry/vendor/Zend/Form/Element.php on line 2176 Cannot reproduce this either, how do you get this? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1037925: [Pkg-nagios-devel] Bug#1037925: icingacli: Icinga is not compatible with php8.2
Control: severity -1 important On 6/14/23 14:19, Frederic Danel wrote: Icingacli module enable --> crash with deprecated print. Making impossible to use module if you start from scratch, or if you'r comming from bullseye and want to enable a new custom module. I cannot reproduce the crash. icingacli just shows a bunch of deprecation warning that were not caught while testing the php8.2 compatibility. Also icingaweb2 print a lot of deprecated print on the website. I also cannot reproduce this. Only the downtime form shows deprecation warnings which were likewise missed while testing the php8.2 compatibility. Also Bullseye --> Bookworm migration shutdown mariadb before migrating sql. The package upgrade doesn't touch the database, you need to apply the schema changes yourself. https://icinga.com/docs/icinga-2/latest/doc/16-upgrading-icinga-2/ https://icinga.com/docs/icinga-web/latest/doc/80-Upgrading/ Probably other issues, solution for now is to use php8.1 package from sury repo. You need check your environment for third party packages or icingaweb2-module packages maintained outside the Nagios team, I have only patched the packages maintained in the team fix the php8.2 deprecations encountered while testing. issue for php8.2 : https://github.com/Icinga/icingaweb2/issues/4918 I forwarded all the changes for php8.2 applied to the packages in Debian to that issue. If they didn't have a CLA they could be forwarded as PRs. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1037336: fixed in devscripts 2.23.5
On Mon, 12 Jun 2023 17:37:12 + Debian FTP Masters wrote: * debchange: Update to current Debian distributions (Add bookworm and trixie and drop stretch, jessie, and wheezy) (Closes: #1037336) This change is also needed in bookworm where `dch --bpo` still uses bullseye-backports instead of bookworm-backports. Will you provide the bookworm-pu? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1036428: libapache2-mod-apreq2: the package is missing from testing release and from i386 architecture
On Sat, 20 May 2023 19:25:41 +0200 Rafal Pietrak wrote: I've experieced problem after upgrading old (i386) machine to Debian-12 I've upgraded it from Debian-10, through Debian-11 (without testing this The package got removed from bookworm due to #1027355. libapreq2 (2.17-3) should migrate to testing in a few days. Once it's back in testing, it will be rebuilt for bookworm-backports. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#850955: libapache2-request-perl: description should include the names of the libraries
Control: tags -1 pending This is fixed in git: https://salsa.debian.org/debian/libapreq2/-/commit/b450debda66bcf40de4c1053da642a8bd972a973 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1030129: ca-certificates-java - Fails to install with OpenJDK 21: Error loading java.security file
On 6/13/23 05:22, tony mancill wrote: I am not able to reproduce the failure in a clean unstable schroot with either openjdk-17 or openjdk-21 yet - for example: I also had trouble reproducing the issue in a sid cowbuilder chroot. This worked for me: apt install ca-certificates-java default-jdk openjdk-21-jdk Just building osmpbf also triggered the issue yesterday, but now apt build-dep osmpbf succeeds like it does for other Java packages. This suggests a race condition or apt package ordering issue. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1030129: ca-certificates-java - Fails to install with OpenJDK 21: Error loading java.security file
On Tue, 31 Jan 2023 13:56:42 +0100 Bastian Blank wrote: | dpkg: error processing package openjdk-21-jdk:arm64 (--configure): | dependency problems - leaving unconfigured It also fails to install with openjdk-17: Setting up ca-certificates-java (20230103) ... Exception in thread "main" java.lang.InternalError: Error loading java.security file at java.base/java.security.Security.initialize(Security.java:106) at java.base/java.security.Security$1.run(Security.java:84) at java.base/java.security.Security$1.run(Security.java:82) at java.base/java.security.AccessController.doPrivileged(AccessController.java:318) at java.base/java.security.Security.(Security.java:82) at java.base/sun.security.jca.ProviderList.(ProviderList.java:178) at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:96) at java.base/sun.security.jca.ProviderList$2.run(ProviderList.java:94) at java.base/java.security.AccessController.doPrivileged(AccessController.java:318) at java.base/sun.security.jca.ProviderList.fromSecurityProperties(ProviderList.java:93) at java.base/sun.security.jca.Providers.(Providers.java:55) at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:156) at java.base/java.security.cert.CertificateFactory.getInstance(CertificateFactory.java:193) at org.debian.security.KeyStoreHandler.(KeyStoreHandler.java:50) at org.debian.security.UpdateCertificates.(UpdateCertificates.java:65) at org.debian.security.UpdateCertificates.main(UpdateCertificates.java:51) dpkg: error processing package ca-certificates-java (--configure): installed ca-certificates-java package post-installation script subprocess returned error exit status 1 Setting up liblwp-protocol-https-perl (6.10-1) ... Setting up default-jre-headless (2:1.17-74) ... Setting up libwww-perl (6.70-1) ... Setting up ant (1.10.13-1) ... dpkg: dependency problems prevent configuration of openjdk-17-jre-headless:amd64: openjdk-17-jre-headless:amd64 depends on ca-certificates-java (>= 20190405~); however: Package ca-certificates-java is not configured yet. dpkg: error processing package openjdk-17-jre-headless:amd64 (--configure): dependency problems - leaving unconfigured Setting up libxml-parser-perl (2.46-4) ... dpkg: dependency problems prevent configuration of openjdk-17-jre:amd64: openjdk-17-jre:amd64 depends on openjdk-17-jre-headless (= 17.0.7+7-1); however: Package openjdk-17-jre-headless:amd64 is not configured yet. dpkg: error processing package openjdk-17-jre:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of default-jre: default-jre depends on openjdk-17-jre; however: Package openjdk-17-jre:amd64 is not configured yet. dpkg: error processing package default-jre (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of openjdk-17-jdk:amd64: openjdk-17-jdk:amd64 depends on openjdk-17-jre (= 17.0.7+7-1); however: Package openjdk-17-jre:amd64 is not configured yet. dpkg: error processing package openjdk-17-jdk:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of openjdk-17-jdk-headless:amd64: openjdk-17-jdk-headless:amd64 depends on openjdk-17-jre-headless (= 17.0.7+7-1); however: Package openjdk-17-jre-headless:amd64 is not configured yet. dpkg: error processing package openjdk-17-jdk-headless:amd64 (--configure): dependency problems - leaving unconfigured Setting up libxml-sax-expat-perl (0.51-2) ... update-perl-sax-parsers: Registering Perl SAX parser XML::SAX::Expat with priority 50... update-perl-sax-parsers: Updating overall Perl SAX parser modules info file... Replacing config file /etc/perl/XML/SAX/ParserDetails.ini with new version dpkg: dependency problems prevent configuration of default-jdk: default-jdk depends on default-jre (= 2:1.17-74); however: Package default-jre is not configured yet. default-jdk depends on openjdk-17-jdk; however: Package openjdk-17-jdk:amd64 is not configured yet. dpkg: error processing package default-jdk (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of default-jdk-headless: default-jdk-headless depends on openjdk-17-jdk-headless; however: Package openjdk-17-jdk-headless:amd64 is not configured yet. dpkg: error processing package default-jdk-headless (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.36-9) ... Processing triggers for sgml-base (1.31) ... Setting up docbook-xsl (1.79.2+dfsg-2) ... Setting up sgml-data (2.0.11+nmu1) ... Setting up docbook2x (0.8.8-17+b1) ... Processing triggers for sgml-base (1.31) ... Setting up docbook-xml (4.5-12) ... Processing triggers for ca-certificates (20230311) ... Updating certificates in
Bug#1034993: software-properties-qt: missing Breaks+Replaces for software-properties-kde when upgrading from bullseye
On Thu, 27 Apr 2023 14:58:57 +0200 Helmut Grohne wrote: Attempting to unpack software-properties-qt/0.99.30-4 from Debian bookworm on a minimal Debian bullseye with software-properties-kde/0.96.20.2-2.1 installed, causes an unpack error from dpkg due to /usr/share/software-properties/designer/dialog_add.ui being contained in both packages. | Selecting previously unselected package software-properties-qt. | (Reading database ... 11560 files and directories currently installed.) | Preparing to unpack .../software-properties-qt_0.99.30-4_all.deb ... | Unpacking software-properties-qt (0.99.30-4) ... | dpkg: error processing archive ./software-properties-qt_0.99.30-4_all.deb (--unpack): | trying to overwrite '/usr/share/software-properties/designer/dialog_add.ui', which is also in package software-properties-kde 0.96.20.2-2.1 | Errors were encountered while processing: | ./software-properties-qt_0.99.30-4_all.deb Workaround for the failure during the upgrade from bullseye to bookworm: apt upgrade --without-new-pkgs apt purge software-properties-kde software-properties-qt+ apt full-upgrade Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1034993: software-properties-qt: missing Breaks+Replaces for software-properties-kde when upgrading from bullseye
On 6/8/23 22:39, Julian Andres Klode wrote: FWIW, the premise of the bug is wrong, there is no software-properties-kde package anymore and the -qt one replaces it, so we must use unversioned Conflicts and Breaks as per policy requirements. When are your going to upload that change? Your preferred solution has not been committed to the git repo yet. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1034993: software-properties-qt: missing Breaks+Replaces for software-properties-kde when upgrading from bullseye
Control: tags -1 patch
The attached patch resolves the issue.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1diff -Nru software-properties-0.99.30/debian/changelog
software-properties-0.99.30/debian/changelog
--- software-properties-0.99.30/debian/changelog2023-01-20
22:52:46.0 +0100
+++ software-properties-0.99.30/debian/changelog2023-06-08
22:13:55.0 +0200
@@ -1,3 +1,11 @@
+software-properties (0.99.30-4.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add Breaks/Replaces on software-properties-kde to fix upgrade failure.
+(closes: #1034993)
+
+ -- Bas Couwenberg Thu, 08 Jun 2023 22:13:55 +0200
+
software-properties (0.99.30-4) unstable; urgency=medium
* py3-software-properties: Depend on lazr.restfulclient (Closes: #1029047)
diff -Nru software-properties-0.99.30/debian/control
software-properties-0.99.30/debian/control
--- software-properties-0.99.30/debian/control 2023-01-20 22:52:46.0
+0100
+++ software-properties-0.99.30/debian/control 2023-06-08 22:13:54.0
+0200
@@ -109,6 +109,8 @@
${misc:Depends},
${python3:Depends}
Suggests: plasma-discover
+Breaks: software-properties-kde (<< 0.99.30)
+Replaces: software-properties-kde (<< 0.99.30)
Description: manage the repositories that you install software from (Qt)
This software provides an abstraction of the used apt repositories.
It allows you to easily manage your distribution and independent software
Bug#1036963: Bug#1034065: sasl-xoauth2: FTBFS: ModuleNotFoundError: No module named 'distutils.core'
Control: reassign -1 src:argparse-manpage
Control: found -1 argparse-manpage/1.2.2-1
Control: tags -1 patch sid bookworm
Control: severity -1 important
Control: affects -1 src:sasl-xoauth2 src:osm2pgsql
On Tue, 30 May 2023 18:34:24 -0400 Daniel Kahn Gillmor wrote:
On Fri 2023-04-07 22:14:44 +0200, Andreas Beckmann wrote:
> sasl-xoauth2/experimental FTBFS on all architectures:
> https://buildd.debian.org/status/package.php?p=sasl-xoauth2&suite=experimental
>
> ...
>debian/rules execute_after_dh_auto_build
> make[1]: Entering directory '/<>'
> mkdir -p completions manpages
> register-python-argcomplete --shell bash sasl-xoauth2-tool >
completions/sasl-xoauth2-tool
> argparse-manpage --pyfile obj-x86_64-linux-gnu/scripts/sasl-xoauth2-tool
--object parser \
>--author 'Tarick Bedeir' --author-email 'tar...@bedeir.com' --project-name
sasl-xoauth2 \
>--url https://github.com/tarickb/sasl-xoauth2 --output
manpages/sasl-xoauth2-tool.1
> Traceback (most recent call last):
> File "/usr/bin/argparse-manpage", line 5, in
> from build_manpages.cli import main
> File "/usr/lib/python3/dist-packages/build_manpages/cli/__init__.py", line 5, in
> from build_manpages.build_manpage import ManPageWriter, get_parser
> File "/usr/lib/python3/dist-packages/build_manpages/build_manpage.py", line 10,
in
> from distutils.core import Command
> ModuleNotFoundError: No module named 'distutils.core'
> make[1]: *** [debian/rules:11: execute_after_dh_auto_build] Error 1
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:6: binary-arch] Error 2
> ...
I think this represents a missing dependency in
python3-argparse-manpage, which makes packages that build-depend on
python3-argparse-manpage to generate their manpages FTBFS.
distutils was removed from setuptools 60:
https://setuptools.pypa.io/en/latest/deprecated/distutils-legacy.html#prefer-setuptools
Upstream dealt with this in v4:
https://github.com/praiskup/argparse-manpage/commit/3e10dac5702915b9b92fdc686bad690c1b15bf61
The package is still at 1.2.2, quite a way behind to simply cherry-pick
those changes.
I'm lowering the severity, because the package is not entirely unusable,
the osm2psql package uses it during the build to generate a manpage for
osm2pgsql-replication which still works because it uses selective imports:
from build_manpages.manpage import Manpage
from build_manpages.build_manpage import get_parser_from_file
Only the the build_manpage class is broken because it subclasses
distutils.Command and raises DistutilsOptionError.
The attached patch replaces the distutils imports with those for
setuptools, except the DistutilsOptionError exception which is replaced
with plain Exception.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1diff -Nru argparse-manpage-1.2.2/debian/changelog
argparse-manpage-1.2.2/debian/changelog
--- argparse-manpage-1.2.2/debian/changelog 2019-09-12 08:33:21.0
+0200
+++ argparse-manpage-1.2.2/debian/changelog 2023-05-31 05:53:15.0
+0200
@@ -1,3 +1,11 @@
+argparse-manpage (1.2.2-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch to not use deprecated distutils module, removed in setuptools 60.
+(closes: #1034065)
+
+ -- Bas Couwenberg Wed, 31 May 2023 05:53:15 +0200
+
argparse-manpage (1.2.2-1) unstable; urgency=medium
* New upstream release.
diff -Nru argparse-manpage-1.2.2/debian/control
argparse-manpage-1.2.2/debian/control
--- argparse-manpage-1.2.2/debian/control 2019-09-12 08:24:48.0
+0200
+++ argparse-manpage-1.2.2/debian/control 2023-05-31 05:51:44.0
+0200
@@ -16,7 +16,7 @@
Package: python3-argparse-manpage
Architecture: all
-Depends: ${misc:Depends}, ${python3:Depends},
+Depends: ${misc:Depends}, ${python3:Depends}, python3-setuptools
Description: Automatically build a manpage from argparse
Generate a manual page in an automatic way from an ArgumentParser object,
so that the manpage matches to the automatically generated --help output.
diff -Nru argparse-manpage-1.2.2/debian/patches/no-distutils.patch
argparse-manpage-1.2.2/debian/patches/no-distutils.patch
--- argparse-manpage-1.2.2/debian/patches/no-distutils.patch1970-01-01
01:00:00.0 +0100
+++ argparse-manpage-1.2.2/debian/patches/no-distutils.patch2023-05-31
05:53:11.0 +0200
@@ -0,0 +1,74 @@
+Description: Don't use deprecated distutils module, removed in setuptools 60.
+Author: Bas Couwenberg
+Bug-Debian: https://bugs.debian.org/1036963
+
+--- a/build_manpages/build_manpage.py
b/build_manpages/build_manpage.py
+@@ -7,8 +7,7 @@ import datetime
+ import optparse
+ import argparse
+
+-from distutils.core import Command
+-from distutils.errors import DistutilsOptionError
++from setuptools import Command
+
+ from .manpage import Manpage
+
+@@ -216,9 +215,9 @@ class build_manpage(Command):
+
+ def finali
Bug#1036939: proj: reproducible-builds: build paths trigger differences
Control: tags -1 pending On 5/30/23 02:57, Vagrant Cascadian wrote: The RPATH contains the build path resulting in different buildid and various other differences: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/proj.html The attached patch modifies debian/rules to pass -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON to dh_auto_configure. Also applied in git. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1035704: proj: reproducible-builds: timezone-dependent timestamps in .gsb/.gtx files
Control: tags -1 - moreinfo + pending On 5/30/23 00:35, Vagrant Cascadian wrote: On 2023-05-29, Sebastiaan Couwenberg wrote: On 5/29/23 06:13, Vagrant Cascadian wrote: On 2023-05-29, Sebastiaan Couwenberg wrote: Does TZ=UTC also work when set in the environment? If so, that could be passed to the unshar commands in d/rules. I would expect that to work as well, which I though of shortly after sending the updated patch... though did not yet test it! Can you test that? Tested! Works! Patch attached! Thanks for confirming the theory. Applied in git. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1035704: proj: reproducible-builds: timezone-dependent timestamps in .gsb/.gtx files
On 5/29/23 06:13, Vagrant Cascadian wrote:
On 2023-05-29, Sebastiaan Couwenberg wrote:
On 5/28/23 23:38, Vagrant Cascadian wrote:
That said, I think it really is the touch commands in debian/datumgrids*
as touch's timestamp modification is timezone dependent in many cases...
The attached patch fixes this by setting the TZ=UTC as an environment
variable in the debian/datumgrids*.shar files.
I also had success with a patch where the touch calls are done with
--date=${SOURCE_DATE_EPOCH} which also worked for me (as touch assumes
to be TZ=UTC in this case)... if that would be preferable, I can also
provide a patch for that.
Patching the shar files is not ideal, when their content is modified
these changes will be lost.
shar/unshar should be more likely be patched.
Does TZ=UTC also work when set in the environment? If so, that could be
passed to the unshar commands in d/rules.
I would expect that to work as well, which I though of shortly after
sending the updated patch... though did not yet test it!
Can you test that? Otherwise we'll have to upload to experimental.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1035704: proj: reproducible-builds: timezone-dependent timestamps in .gsb/.gtx files
On 5/28/23 23:38, Vagrant Cascadian wrote:
On 2023-05-08, Vagrant Cascadian wrote:
On 2023-05-09, Sebastiaan Couwenberg wrote:
On 5/9/23 05:47, Sebastiaan Couwenberg wrote:
On 5/8/23 22:43, Vagrant Cascadian wrote:
On 2023-05-08, Sebastiaan Couwenberg wrote:
On 5/8/23 02:07, Vagrant Cascadian wrote:
The attached patch fixes this by not touching these files during the
build process.
From shar(1):
"
-m, --no-timestamp
do not restore modification times.
...
That should be used when generating the archives instead of your patch
to not have the mtimes touched when unpacking the archives.
...
But the diffoscope-results only show a few of the files from the shar
archives with different mtimes, and all of them get touched when
unpacking the archive just before the configure target is executed.
Well, I too was perplexed why other files were not affected, but it is
consistently those .gsb and .gtx files, and the submitted patch allows
to consistently build reproducibly in the dozens of times I've build
it...
shar actually makes the timestamps reproducible by always using the
mtime recorded in the archive instead of the time the files were
unpacked.
Something else is likely changing the mtime after the files are
unpacked. Some of these grids are used by the testsuite for example.
I will try to look into it further, but without really being familiar
with the proj codebase (or even what proj itself does)... any additional
very specific suggestions where to look next would definitely be
appreciated! :)
CMake's configure_file() is used to copy the .gsb & .gtx files from
CMAKE_CURRENT_SOURCE_DIR to CMAKE_CURRENT_BINARY_DIR, that might be
touching the mtimes too. See: data/CMakeLists.txt
Thanks, that is definitely worth taking a look at...
...
Will try to poke at it more tomorrow...
I had no luck with poking at that approach... though did not have great
ideas what to even try there.
That said, I think it really is the touch commands in debian/datumgrids*
as touch's timestamp modification is timezone dependent in many cases...
The attached patch fixes this by setting the TZ=UTC as an environment
variable in the debian/datumgrids*.shar files.
I also had success with a patch where the touch calls are done with
--date=${SOURCE_DATE_EPOCH} which also worked for me (as touch assumes
to be TZ=UTC in this case)... if that would be preferable, I can also
provide a patch for that.
Patching the shar files is not ideal, when their content is modified
these changes will be lost.
shar/unshar should be more likely be patched.
Does TZ=UTC also work when set in the environment? If so, that could be
passed to the unshar commands in d/rules.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1036597: python3-cartopy: broken symlink: /usr/share/doc/python3-cartopy/examples -> ../../../lib/python3/dist-packages/cartopy/examples
Control: tags -1 pending Thanks for reporting this issue, it's fixed in git by dropping the symlink. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1036573: grass-core: broken symlink: /usr/share/man/man1/x-grass.1.gz -> grass.1.gz
Control: tags -1 pending On 5/23/23 01:13, Andreas Beckmann wrote: during a test with piuparts I noticed your package ships (or creates) a broken symlink: 0m55.9s ERROR: FAIL: Broken symlinks: /usr/share/man/man1/x-grass.1.gz -> grass.1.gz (grass-core) The manpages seem to have moved to grass-doc, so the symlink should follow. Also the target does no longer exist, but has likely been renamed to grass.1grass.gz, so the symlink should probably follow. Thanks for reporting this issue, it is fixed in git by symlinking to grass.1grass.gz. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1036067: [Pkg-nagios-devel] Bug#1036067: nagvis: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
Control: tags -1 pending Thanks for the updated translation, it's committed in git. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1035921: postgresql-13-postgis-3: Inverted x-y-coordinates for EPSG:31466 when transforming coordinates since 3.1.1+dfsg-1+deb11u1
On 5/11/23 10:52, Sebastiaan Couwenberg wrote: The next bullseye point release should include this fix, in the mean your can downgrade to 3.1.1+dfsg-1. The bullseye-pu bugreport: #1035924 The changes are available in git: https://salsa.debian.org/debian-gis-team/postgis/-/commits/bullseye Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1035921: postgresql-13-postgis-3: Inverted x-y-coordinates for EPSG:31466 when transforming coordinates since 3.1.1+dfsg-1+deb11u1
Hi Stephan, Your bugreport came in just as I submitted #1035922 on your behalf. The two bugreports have been merged. As noted in #1035922, two more upstream commits are required to resolve the regression, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035922#5 The next bullseye point release should include this fix, in the mean your can downgrade to 3.1.1+dfsg-1. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1031410: Closing p-u requests for fixes included in 11.7
> Should I file another bug report for this?
Yes.
On unstable:
gis=# SELECT
ST_AsGeoJSON(ST_Transform(ST_SetSRID('010120110F04F0844A1349264120ED527FE9DD5841'::geometry,
3857), 31466));
st_asgeojson
---
{"type":"Point","crs":{"type":"name","properties":{"name":"EPSG:31466"}},"coordinates":[2539841.861857439,5586869.519378289]}
(1 row)
On bullseye:
bagv2=# SELECT
ST_AsGeoJSON(ST_Transform(ST_SetSRID('010120110F04F0844A1349264120ED527FE9DD5841'::geometry,
3857), 31466));
st_asgeojson
---
{"type":"Point","crs":{"type":"name","properties":{"name":"EPSG:31466"}},"coordinates":[5586869.519378289,2539841.861857439]}
(1 row)
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1035704: proj: reproducible-builds: timezone-dependent timestamps in .gsb/.gtx files
On 5/9/23 05:47, Sebastiaan Couwenberg wrote: On 5/8/23 22:43, Vagrant Cascadian wrote: On 2023-05-08, Sebastiaan Couwenberg wrote: On 5/8/23 02:07, Vagrant Cascadian wrote: The attached patch fixes this by not touching these files during the build process. From shar(1): " -m, --no-timestamp do not restore modification times. Avoid generating 'touch' commands to restore the file modification dates when unpacking files from the archive. When file modification times are not preserved, project build programs like "make" will see built files older than the files they get built from. This is why, when this option is not used, a special effort is made to restore timestamps. " That should be used when generating the archives instead of your patch to not have the mtimes touched when unpacking the archives. Is it actually a problem to allow dpkg to normalize the timestamps on these files rather than forcefully setting them to ... a value from a shar archive? It is perhaps a naive question; I really do not know. Where does dpkg normalize the timestamps? shar sets the timestamps when the archive is unpacked before the package built starts. Some of the files in the diffoscope-results are only installed in proj-data and not used otherwise during the build. * BETA2007.gsb is used in test/gie/DHDN_ETRS89.gie * CHENYX06.gsb/CHENYX06_etrs.gsb/CHENYX06a.gsb are only installed * egm96_15.gtx is used in test/gie/deformation.gie, test/gie/more_builtins.gie, test/gie/4D-API_cs2cs-style.gie, and test/cli/testdatumfile * ntf_r93.gsb is used in test/gie/more_builtins.gie, test/gie/4D-API_cs2cs-style.gie, and test/cli/testdatumfile * nzgd2kgrid0005.gsb is used in unit tests But the diffoscope-results only show a few of the files from the shar archives with different mtimes, and all of them get touched when unpacking the archive just before the configure target is executed. Well, I too was perplexed why other files were not affected, but it is consistently those .gsb and .gtx files, and the submitted patch allows to consistently build reproducibly in the dozens of times I've build it... shar actually makes the timestamps reproducible by always using the mtime recorded in the archive instead of the time the files were unpacked. Something else is likely changing the mtime after the files are unpacked. Some of these grids are used by the testsuite for example. I will try to look into it further, but without really being familiar with the proj codebase (or even what proj itself does)... any additional very specific suggestions where to look next would definitely be appreciated! :) CMake's configure_file() is used to copy the .gsb & .gtx files from CMAKE_CURRENT_SOURCE_DIR to CMAKE_CURRENT_BINARY_DIR, that might be touching the mtimes too. See: data/CMakeLists.txt Seeing how the mtimes are off by two hours, this could be the difference between UTC and CEST. The latter was in effect when the archives were created: $ grep "Made on" debian/datumgrids*.shar debian/datumgrids-ch.shar:# Made on 2018-02-26 22:27 CET by . debian/datumgrids.shar:# Made on 2018-09-15 20:13 CEST by . But why does it only affect the binary GSB & GTX files, and not also the binary ntv1_can.dat file or text files like README.DATUMGRID and the init files (the ones without extensions)? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1035704: proj: reproducible-builds: timezone-dependent timestamps in .gsb/.gtx files
On 5/8/23 22:43, Vagrant Cascadian wrote: On 2023-05-08, Sebastiaan Couwenberg wrote: On 5/8/23 02:07, Vagrant Cascadian wrote: The attached patch fixes this by not touching these files during the build process. From shar(1): " -m, --no-timestamp do not restore modification times. Avoid generating 'touch' commands to restore the file modification dates when unpacking files from the archive. When file modification times are not preserved, project build programs like "make" will see built files older than the files they get built from. This is why, when this option is not used, a special effort is made to restore timestamps. " That should be used when generating the archives instead of your patch to not have the mtimes touched when unpacking the archives. Is it actually a problem to allow dpkg to normalize the timestamps on these files rather than forcefully setting them to ... a value from a shar archive? It is perhaps a naive question; I really do not know. Where does dpkg normalize the timestamps? shar sets the timestamps when the archive is unpacked before the package built starts. Some of the files in the diffoscope-results are only installed in proj-data and not used otherwise during the build. * BETA2007.gsb is used in test/gie/DHDN_ETRS89.gie * CHENYX06.gsb/CHENYX06_etrs.gsb/CHENYX06a.gsb are only installed * egm96_15.gtx is used in test/gie/deformation.gie, test/gie/more_builtins.gie, test/gie/4D-API_cs2cs-style.gie, and test/cli/testdatumfile * ntf_r93.gsb is used in test/gie/more_builtins.gie, test/gie/4D-API_cs2cs-style.gie, and test/cli/testdatumfile * nzgd2kgrid0005.gsb is used in unit tests But the diffoscope-results only show a few of the files from the shar archives with different mtimes, and all of them get touched when unpacking the archive just before the configure target is executed. Well, I too was perplexed why other files were not affected, but it is consistently those .gsb and .gtx files, and the submitted patch allows to consistently build reproducibly in the dozens of times I've build it... shar actually makes the timestamps reproducible by always using the mtime recorded in the archive instead of the time the files were unpacked. Something else is likely changing the mtime after the files are unpacked. Some of these grids are used by the testsuite for example. I will try to look into it further, but without really being familiar with the proj codebase (or even what proj itself does)... any additional very specific suggestions where to look next would definitely be appreciated! :) CMake's configure_file() is used to copy the .gsb & .gtx files from CMAKE_CURRENT_SOURCE_DIR to CMAKE_CURRENT_BINARY_DIR, that might be touching the mtimes too. See: data/CMakeLists.txt Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1035704: proj: reproducible-builds: timezone-dependent timestamps in .gsb/.gtx files
Control: tags -1 moreinfo On 5/8/23 02:07, Vagrant Cascadian wrote: The attached patch fixes this by not touching these files during the build process. From shar(1): " -m, --no-timestamp do not restore modification times. Avoid generating 'touch' commands to restore the file modification dates when unpacking files from the archive. When file modification times are not preserved, project build programs like "make" will see built files older than the files they get built from. This is why, when this option is not used, a special effort is made to restore timestamps. " That should be used when generating the archives instead of your patch to not have the mtimes touched when unpacking the archives. But the diffoscope-results only show a few of the files from the shar archives with different mtimes, and all of them get touched when unpacking the archive just before the configure target is executed. shar actually makes the timestamps reproducible by always using the mtime recorded in the archive instead of the time the files were unpacked. Something else is likely changing the mtime after the files are unpacked. Some of these grids are used by the testsuite for example. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1035017: unblock: pdl/1:2.081-2
Control: tags -1 - moreinfo On 4/29/23 10:51, Sebastian Ramacher wrote: On 2023-04-27 16:52:36 +0200, Bas Couwenberg wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: p...@packages.debian.org Control: affects -1 + src:pdl Please unblock package pdl [ Reason ] It fixed the upgrade failure from bullseye reported in #1034942. [ Impact ] Upgrade from bullseye to bookworm fails. [ Tests ] autopkgtest, Salsa CI, and upstream test suite. I've manually verified the fix for #1034942 by upgrading a bullseye chroot to bookworm using the fixed pdl from my local repo. [ Risks ] Low, the other changes that were pending in git since 1:2.081-1 don't risk breakage. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] The package has been uploaded to unstable. unblock pdl/1:2.081-2 diff -Nru pdl-2.081/debian/changelog pdl-2.081/debian/changelog --- pdl-2.081/debian/changelog 2022-10-27 18:57:46.0 +0200 +++ pdl-2.081/debian/changelog 2023-04-27 15:54:44.0 +0200 @@ -1,3 +1,22 @@ +pdl (1:2.081-2) unstable; urgency=medium + + * Team upload. + + [ Bas Couwenberg ] + * Add Rules-Requires-Root to control file. + * Add a debhelper sequence to run dh_pdl. Would you mind re-uploading without that change? It doesn't seem to provide a targetted fix for a bug report. I'd rather not. While not a targeted fix, it also doesn't risk introducing regressions. + * Bump Standards-Version to 4.6.2, no changes. + * Add Breaks/Replaces on libpdl-stats-perl to fix upgrade. +(closes: #1034942) + + [ Debian Janitor ] + * Update lintian override info to new format: ++ debian/source/lintian-overrides: line 2 ++ debian/pdl.lintian-overrides: line 6, 10, 22, 28 + * Use secure URI in Homepage field. + + -- Bas Couwenberg Thu, 27 Apr 2023 15:54:44 +0200 + pdl (1:2.081-1) unstable; urgency=medium * Team upload. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1034942: pdl: missing Breaks+Replaces for libpdl-stats-perl when upgrading from bullseye
Control: tags -1 pending On 4/27/23 14:58, Helmut Grohne wrote: Attempting to unpack pdl/1:2.081-1+b1 from Debian bookworm on a minimal Debian bullseye with libpdl-stats-perl/0.76-1 installed, causes an unpack error from dpkg due to /usr/share/man/man3/PDL::GSL::CDF.3pm.gz being contained in both packages. libpdl-stats-perl (0.82-3) in bookworm no longer includes the PDL::GSL::CDF files, but that can only be installed after the pdl (1:2.081-1). The CDF files are no longer included since libpdl-stats-perl (0.77-1~exp1). The issue is fixed in git and a new upload to unstable will follow shortly. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1034206: unblock: owslib/0.27.2-3
On 4/11/23 06:48, Bas Couwenberg wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: ows...@packages.debian.org Control: affects -1 + src:owslib Please unblock package owslib It is affected by CVE-2023-27476 reported in #1034182. [ Reason ] Fixes security issue and missing recommended dependencies. [ Impact ] Unfixed security issue. [ Tests ] Upstream test suite. [ Risks ] Low, the changes are pretty straight forward. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] Testing autoremoval of rdeps would remove qgis which is one of, if not the, most important GIS packages for users. The package has not been unloaded to unstable yet. unblock owslib/0.27.2-3 Since there was no objection to the pending changes from git that were included in tirex (#1034242), owslib (0.27.2-3) has been uploaded to unstable. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1034242: unblock: tirex/0.7.0-3
Control: tags -1 - moreinfo On 4/15/23 18:03, Sebastian Ramacher wrote: Please remove the moreinfo tag once the package is available in unstable. tirex (0.7.0-3) is built & installed on all release architectures. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1031410: bullseye-pu: package postgis/3.1.1+dfsg-1+deb11u1
On 4/1/23 21:23, Adam D. Barratt wrote: On Thu, 2023-02-16 at 19:38 +0100, Bas Couwenberg wrote: As reported in #1031392, postgis 3.1.1 has an important issue with polar stereographic projections which was resolved in 3.1.2. [ Impact ] Unusable coordinates from transformations. Please go ahead. Thanks, postgis (3.1.1+dfsg-1+deb11u1) has been upload. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1033666: [Pkg-nagios-devel] Bug#1033666: icinga2-common: wrong executable in /usr/share/icinga2/include/plugins-contrib.d/systemd.conf
Control: tags -1 pending On 3/29/23 20:07, Andreas B. Mundt wrote: the configuration in '/usr/share/icinga2/include/plugins-contrib.d/systemd.conf' contains a wrong executable in line 4: command = [ PluginContribDir + "/check_systemd.py" ] The plugin's path is '/usr/lib/nagios/plugins/check_systemd' (no .py) [1]. That's a divergence from upstream in the Debian package: https://salsa.debian.org/python-team/packages/monitoring-plugins-systemd/-/blob/debian/master/debian/monitoring-plugins-systemd.install We'll have to patch the CheckCommand like check_postgres: https://salsa.debian.org/nagios-team/icinga2/-/blob/master/debian/patches/postgres-checkcommand.patch Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1025745: libhdf4: add support for loongarch64
On 12/8/22 14:34, zhangdandan wrote: I have added support for loongarch64 in libhdf4 source package. The results of test-units(make check) all passed. Please consider applying the attached patch. HDF4 4.2.16 no longer has the architecture conditionals, this made your loongarch.patch and similar architecture patches obsolete. From the upstream ticket: " We released 4.2.16 recently. Would you please try and let us know if that version works for your platform? " https://jira.hdfgroup.org/servicedesk/customer/portal/2/SUPPORT-1876 Is there a porterbox to test whether libhdf4 (4.2.16-1~exp2) from experimental builds successfully on loongarch46? Or can you verify whether libhdf4 still works without your patch? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1033085: [DKIM] [Pkg-nagios-devel] Bug#1033085: [INTL:ro] Romanian debconf templates translation of nsca
Control: tags -1 pending Thanks for the translation, it's added in git. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1031410: bullseye-pu: package postgis/3.1.1+dfsg-1+deb11u1
Can we get this into the upcoming 11.7 point release? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#961221: broken lintian report link on packages overview
On Fri, 24 Jul 2020 12:22:38 +0200 Samuel Thibault wrote: Similarly, links for packages are broken: on https://qa.debian.org/developer.php?email=sthibault%40debian.org the link for accerciser brings to https://lintian.debian.org/reports/accerciser.html (404) while it should be https://lintian.debian.org/sources/accerciser.html The package links have already been switched to udd.d.o. https://qa.debian.org/developer.php?email=sthibault%40debian.org#accerciser links to: https://udd.debian.org/lintian?packages=accerciser Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#961221: broken lintian report link on packages overview
Control: tags -1 patch
Control: retitle -1 DDPO: Use udd.d.o for Lintian report link
On Thu, 21 May 2020 11:05:28 -0400 Ryan Kavanagh wrote:
Package: qa.debian.org
Severity: normal
The "Lintian" reports link on packages overview pages are broken. For
example, clicking on "Lintian" on my packages overview page [0] brings
you to the following non-existing page [1]. It looks like the page may
have moved to [2].
[0] https://qa.debian.org/developer.php?login=rak&comaint=yes
[1] https://lintian.debian.org/reports/maintainer/rak%40debian.org.html
[2]
https://lintian.debian.org/maintainer/ryan%20kavanagh%20%3c...@debian.org%3E.html
The attached patch resolves the issue by using udd.d.or instead of
lintian.d.o.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1From 1cc78ae1e0d9b8382ce1b28446c9cdbdeb12e9d0 Mon Sep 17 00:00:00 2001
From: Bas Couwenberg
Date: Fri, 24 Feb 2023 14:38:25 +0100
Subject: Replace lintian.d.o with udd.d.o in Reports link.
---
wml/developer.wml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/wml/developer.wml b/wml/developer.wml
index c26ee4e1..9cba994a 100644
--- a/wml/developer.wml
+++ b/wml/developer.wml
@@ -210,7 +210,7 @@ function print_header_entries_body($login, $name)
$maintainer_data .= "Reports: " .
html_a("Dashboard", "https://udd.debian.org/dmd.cgi?email1=$ulogin";) . " - " .
html_a("Buildd", "https://buildd.debian.org/status/package.php?p=$ulogin&comaint="; . isdisplayed('comaint')) . " - " .
-html_a("Lintian", "https://lintian.debian.org/reports/maintainer/$ulogin.html";) . " - " .
+html_a("Lintian", "https://udd.debian.org/lintian/?email1=$ulogin#all";) . " - " .
html_a("Debtags", "https://debtags.debian.org/reports/maint/$login";) . " - " . // enrico says no encoding is ok
html_a("Piuparts", "https://piuparts.debian.org/sid/maintainer/$initial/$ulogin.html";) . " - " .
html_a("Janitor", "https://janitor.debian.net/m/$login";) . " - " .
--
2.30.2
Bug#1031825: [Pkg-nagios-devel] Bug#1031825: icinga-php-library: Creation of dynamic property is deprecated in PHP 8.2
Hi Frederik, Resending with correct Reply-To header. On 2/23/23 17:55, Frederik Himpe wrote: Sebastiaan Couwenberg schreef op 2023-02-23 17:45: On 2/23/23 17:05, Frederik wrote: I'm using Debian Bookworm with icinga-php-library 0.10.1-1 and PHP 8.2. When I log in in icingaweb2, I see three times this message in the left sidebar between the search bar in the menu: Deprecated: Creation of dynamic property ipl\Sql\Config::$skip_validation is deprecated in /usr/share/icinga-php/ipl/vendor/ipl/sql/src/Config.php on line 32 Are you using icinga2-ido-mysql by chance? I cannot reproduce the issue with icinga2-ido-pgsql No, I'm not using any of the icinga2-ido-* packages, I am using icingadb with icingadb-web instead. What about my other question? " skip_validation is not a documented resource option: https://icinga.com/docs/icinga-web/latest/doc/04-Resources/#configuration You likely have this in /etc/icingaweb2/resources.ini though, can you confirm that? Please remove or comment out the setting if you do. " Please check /etc/icingaweb2/resources.ini. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1031825: [Pkg-nagios-devel] Bug#1031825: icinga-php-library: Creation of dynamic property is deprecated in PHP 8.2
Control: tags -1 moreinfo Hi Frederik, On 2/23/23 17:05, Frederik wrote: I'm using Debian Bookworm with icinga-php-library 0.10.1-1 and PHP 8.2. When I log in in icingaweb2, I see three times this message in the left sidebar between the search bar in the menu: Deprecated: Creation of dynamic property ipl\Sql\Config::$skip_validation is deprecated in /usr/share/icinga-php/ipl/vendor/ipl/sql/src/Config.php on line 32 Are you using icinga2-ido-mysql by chance? I cannot reproduce the issue with icinga2-ido-pgsql, that setup was used to develop the PHP 8.2 changes are discussed in the upstream issue: https://github.com/Icinga/icingaweb2/issues/4918 skip_validation is not a documented resource option: https://icinga.com/docs/icinga-web/latest/doc/04-Resources/#configuration You likely have this in /etc/icingaweb2/resources.ini though, can you confirm that? Please remove or comment out the setting if you do. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1031596: London-Tokyo vs. Tokyo-London distance much different!!
tags 1031596 upstream severity 1031596 important forwarded 1031596 https://rt.cpan.org/Public/Bug/Display.html?id=146578 thanks On 2/19/23 03:08, Dan Jacobson wrote: Regarding Geo::Calc version 0.12, there is something very wrong. The distance from London to Tokyo, 11314595.851556 is different that from Tokyo to London, 8256133.168096 !! See https://rt.cpan.org/Public/Bug/Display.html?id=146578 . There is no activity on the many years of reports there. That's not usual for RT tickets. Are you sure this package should be in Debian? As noted in the ITP (#1021476) it was required for Geo::GPX 1.00, but was dropped in 1.08. If software is dead upstream and doesn't work for you, stop using it. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1031392: postgis: Polar stereographic axis order wrong when transforming coordinates
On 2/16/23 15:05, Paul Cochrane wrote: On Thu, Feb 16, 2023 at 02:44:36PM +0100, Sebastiaan Couwenberg wrote: I'm not sure if it's worth the effort to fix this issue in bullseye with a stable update. Since you've already done the work to patch package in bullseye, can you prepare the stable update in a bullseye branch [0] and submit it as an MR in Salsa [1]? [0] https://debian-gis-team.pages.debian.net/policy/packaging.html#git-package-branches [1] https://salsa.debian.org/debian-gis-team/postgis/ I can give it a go :-) Nevermind, the pu is ready: https://salsa.debian.org/debian-gis-team/postgis/-/commits/bullseye https://bugs.debian.org/1031410 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1030921: satpy/spyder-kernels: unsatisfied build dependency in testing: python3-distributed
On 2/9/23 09:11, Paul Gevers wrote: Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. dask.distributed was removed from testing because of bug 1030096. dask.distributed is fixed in unstable and should migrate in a few days: https://qa.debian.org/excuses.php?package=dask.distributed With the soft freeze in two days it will likely need help from the release managers to migrate. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#774565: closing 774565
Control: submitter -1 Thorsten Glaser On 2/7/23 19:53, Thorsten Glaser wrote: Why did you close the bug with no explanation? Because I filed it, and no longer care for OpenLayers 3 and the shit that is the Node.js ecosystem. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1016598: closed by Debian FTP Masters (reply to Picca Frédéric-Emmanuel ) (Bug#1016598: fixed in binoculars 0.0.11-2)
Control: tags -1 patch On Sat, 4 Feb 2023 13:04:04 +0200 Adrian Bunk wrote: On Sun, Oct 16, 2022 at 09:51:03AM +, Debian Bug Tracking System wrote: >... > binoculars (0.0.11-2) unstable; urgency=medium >... >* Switch from vtk7 to vtk9 (Closes: #1016598) >... This fixed the build dependency, but the runtime dependency is still on python3-vtk7. A fix has been committed: https://salsa.debian.org/science-team/binoculars/-/commit/ce5f826f95e0df48f79aea7f9bac9af150c70e28 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1029798: [Pkg-nagios-devel] Bug#1029798: icingaweb2-common fails to install
Control: tags -1 pending Thanks for reporting this issue, the fixed package will be uploaded shortly. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028994: [Pkg-mailman-hackers] Bug#1028994: mailman3: (autopkgtest) needs update for Python 3.11
On Tue, 17 Jan 2023 15:32:53 +0100 Pierre-Elliott Bécue wrote: I intend to do a full sweep on mailman suite in the next week, so don't worry too much! :) How is that going? mailman3 is the last major blocker for testing migration of python3-defaults. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1029422: [Pkg-nagios-devel] Bug#1029422: icinga2: FTBFS in bookworm (undeclared build-dependency on tzdata)
Control: severity -1 important You should not do these kind of rebuilds so shortly before the freeze. The severity should be important, because tzdata is installed in the usual build environments. Instead of creating RC bugs in specially crafted build environments, our time is better spent fixing issues before the bookworm freeze. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1029249: scikit-learn: FTBFS: build-dependency not installable: python-numpy-doc
Control: tags -1 patch A fix has been committed in git: https://salsa.debian.org/science-team/scikit-learn/-/commit/2f2538d7538f693f3600713fc816c07f8a0990da Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1029109: cimg: build dependency gone after tiff transition
Control: tags -1 patch A patch has been committed in git: https://salsa.debian.org/science-team/cimg/-/commit/1dc81d57ed0d293cf2b7c208da25ece765f64004 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028513: dovecot: autopkgtest failure with python3.11
Control: tags -1 pending On 1/12/23 08:10, Bas Couwenberg wrote: The attached patch resolves the issue by using python3-passlib which has a pure Python implementation to fall back on when the crypt module is not available. I've uploaded a 0-day NMU with the patch from this issue. The changes are attached and pushed to the repo on Salsa: https://salsa.debian.org/debian/dovecot/-/commits/debian/1%252.3.19.1+dfsg1-2.1 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 diff --git a/debian/changelog b/debian/changelog index 14c1e62e2..22c9a9ce8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +dovecot (1:2.3.19.1+dfsg1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * [b02ebc9] Don't use deprecated crypt module. +(closes: #1028513) + + -- Bas Couwenberg Fri, 20 Jan 2023 07:01:26 +0100 + dovecot (1:2.3.19.1+dfsg1-2) unstable; urgency=medium [ Christian Göttsche ] diff --git a/debian/tests/control b/debian/tests/control index 106e5d04a..496cfcc0b 100644 --- a/debian/tests/control +++ b/debian/tests/control @@ -11,4 +11,4 @@ Restrictions: needs-root, breaks-testbed, allow-stderr Tests: testmails Restrictions: needs-root, breaks-testbed -Depends: dovecot-imapd, dovecot-pop3d, lsb-release, python3 +Depends: dovecot-imapd, dovecot-pop3d, lsb-release, python3, python3-passlib diff --git a/debian/tests/testmails b/debian/tests/testmails index 71ae3caab..3329809b5 100755 --- a/debian/tests/testmails +++ b/debian/tests/testmails @@ -1,6 +1,5 @@ #!/usr/bin/python3 -import crypt import grp import imaplib import os @@ -13,6 +12,8 @@ import subprocess import sys import unittest +from passlib.hash import des_crypt + def random_string(length): '''Return a random string, consisting of ASCII letters, with given @@ -57,7 +58,7 @@ class TestUser: self.salt = random_string(2) self.password = random_string(8) -self.crypted = crypt.crypt(self.password, self.salt) +self.crypted = des_crypt.using(salt=self.salt).hash(self.password) subprocess.check_call(['useradd', '-p', self.crypted, '-m', login])
Bug#1028148: celery FTBFS with Python 3.11 as default version
Control: tags -1 patch A patch has been committed in git: https://salsa.debian.org/python-team/packages/celery/-/commit/c94d7c031d3686596305d435898199e3d452e87c Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028671: python-django-tagging: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.11" --system=custom "--test-args=PYTHONPATH=. DJANGO_SETTINGS_MODULE=tagging.tests.settings
Control: tags -1 patch A patch has been committed in git: https://salsa.debian.org/python-team/packages/python-django-tagging/-/commit/580dfcf54791ea0613c0edc622867b44e5738fb5 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028687: termbox: FTBFS: ValueError: invalid mode: 'rUb'
Control: tags -1 patch A patch has been committed in git: https://salsa.debian.org/debian/termbox/-/commit/814a247912b907d66adb8b761c616e1f1a5f471f Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028695: python-hdf5storage: FTBFS: build-dependency not installable: python-numpy-doc
Control: tags -1 pending A fix has been committed in git: https://salsa.debian.org/science-team/python-hdf5storage/-/commit/78d2bc277af59a8d2881b2290d175822b39ca65b Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028673: pydl: FTBFS: ImportError: cannot import name 'float' from 'numpy' (/usr/lib/python3/dist-packages/numpy/__init__.py)
Control: tags -1 patch A patch has been committed in git: https://salsa.debian.org/debian-astro-team/pydl/-/commit/3cd70897436e4166f495aee204bcf0c7b026a5bc Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028825: python-igor: FTBFS: AttributeError: module 'numpy' has no attribute 'complex'
Control: affects -1 src:arpys Control: tags -1 patch A patch has been committed in git: https://salsa.debian.org/science-team/igor/-/commit/4f292cca1d326fea9162c4d857ad76b9328b23ab Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028731: python-crank: FTBFS: ImportError: cannot import name 'getargspec' from 'inspect' (/usr/lib/python3.11/inspect.py)
Control: tags -1 patch The attached patch resolves the issue. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1diff -Nru python-crank-0.7.2/debian/changelog python-crank-0.7.2/debian/changelog --- python-crank-0.7.2/debian/changelog 2019-10-06 12:11:53.0 +0200 +++ python-crank-0.7.2/debian/changelog 2023-01-19 14:29:02.0 +0100 @@ -1,3 +1,11 @@ +python-crank (0.7.2-5.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Add patch to fix FTBFS with python3.11. +(closes: #1028731) + + -- Bas Couwenberg Thu, 19 Jan 2023 14:29:02 +0100 + python-crank (0.7.2-5) unstable; urgency=medium [ Ondřej Nový ] diff -Nru python-crank-0.7.2/debian/patches/python3.11.patch python-crank-0.7.2/debian/patches/python3.11.patch --- python-crank-0.7.2/debian/patches/python3.11.patch 1970-01-01 01:00:00.0 +0100 +++ python-crank-0.7.2/debian/patches/python3.11.patch 2023-01-19 14:29:01.0 +0100 @@ -0,0 +1,25 @@ +Description: Don't used getargspec, removed in python3.11. +Author: Bas Couwenberg +Forwarded: not-needed +Bug-Debian: https://bugs.debian.org/1028731 + +--- a/crank/util.py b/crank/util.py +@@ -6,7 +6,7 @@ MIT License + """ + + import collections, sys, string +-from inspect import getargspec ++from inspect import getfullargspec + + __all__ = [ + 'get_argspec', 'get_params_with_argspec', 'remove_argspec_params_from_params', +@@ -31,7 +31,7 @@ def get_argspec(func): + try: + argspec = _cached_argspecs[im_func] + except KeyError: +-spec = getargspec(im_func) ++spec = getfullargspec(im_func) + argvals = spec[3] + + # this is a work around for a crappy api choice in getargspec diff -Nru python-crank-0.7.2/debian/patches/series python-crank-0.7.2/debian/patches/series --- python-crank-0.7.2/debian/patches/series2019-10-06 12:11:53.0 +0200 +++ python-crank-0.7.2/debian/patches/series2023-01-19 14:26:26.0 +0100 @@ -1 +1,2 @@ remove-broken-test.patch +python3.11.patch
Bug#1028775: python-ironic-lib: FTBFS: ModuleNotFoundError: No module named 'async_timeout'
On Sat, 14 Jan 2023 13:43:55 +0100 Lucas Nussbaum wrote: = Failures during discovery = --- import errors --- Failed to import test module: ironic_lib.tests.test_mdns Traceback (most recent call last): File "/usr/lib/python3.10/unittest/loader.py", line 436, in _find_test_path module = self._get_module_from_name(name) File "/usr/lib/python3.10/unittest/loader.py", line 377, in _get_module_from_name __import__(name) File "/<>/ironic_lib/tests/test_mdns.py", line 17, in import zeroconf File "/usr/lib/python3/dist-packages/zeroconf/__init__.py", line 26, in from ._core import Zeroconf File "/usr/lib/python3/dist-packages/zeroconf/_core.py", line 36, in from ._handlers import ( File "/usr/lib/python3/dist-packages/zeroconf/_handlers.py", line 45, in from ._services.info import ServiceInfo File "/usr/lib/python3/dist-packages/zeroconf/_services/info.py", line 40, in from .._utils.asyncio import get_running_loop, run_coro_with_timeout File "/usr/lib/python3/dist-packages/zeroconf/_utils/asyncio.py", line 30, in from async_timeout import timeout as asyncio_timeout ModuleNotFoundError: No module named 'async_timeout' python3-zeroconf has this dependency: python3-async-timeout (>= 4.0.1) | python3 (>> 3.11) Because python3.11 is now default python3-async-timeout doesn't get installed even though it's still required for python3.10. python3-async-timeout should probably be an hard dependency of python3-zeroconf until python3.10 is removed. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028793: pymodbus: FTBFS: TypeError: BaseEventLoop.create_datagram_endpoint() got an unexpected keyword argument 'reuse_address'
Control: tags -1 patch A patch has been committed in git: https://salsa.debian.org/python-team/packages/pymodbus/-/commit/d1b4d6d58ed69174a27486cb94dad504d7f8bf9c Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028794: oregano: FTBFS: ValueError: invalid mode: 'rUb'
Control: tags -1 patch
The attached patch resolves the issue.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1diff -Nru oregano-0.84.41+dfsg.1/debian/changelog
oregano-0.84.41+dfsg.1/debian/changelog
--- oregano-0.84.41+dfsg.1/debian/changelog 2019-01-29 16:36:16.0
+0100
+++ oregano-0.84.41+dfsg.1/debian/changelog 2023-01-19 12:41:16.0
+0100
@@ -1,3 +1,11 @@
+oregano (0.84.41+dfsg.1-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch to fix FTBFS with python3.11.
+(closes: #1028794)
+
+ -- Bas Couwenberg Thu, 19 Jan 2023 12:41:16 +0100
+
oregano (0.84.41+dfsg.1-1) unstable; urgency=medium
* New upstream release
diff -Nru oregano-0.84.41+dfsg.1/debian/patches/python3.11.patch
oregano-0.84.41+dfsg.1/debian/patches/python3.11.patch
--- oregano-0.84.41+dfsg.1/debian/patches/python3.11.patch 1970-01-01
01:00:00.0 +0100
+++ oregano-0.84.41+dfsg.1/debian/patches/python3.11.patch 2023-01-19
12:41:10.0 +0100
@@ -0,0 +1,35 @@
+Description: Don't use U mode, removed in python3.11.
+Author: Bas Couwenberg
+Bug-Debian: https://bugs.debian.org/1028794
+
+--- a/waflib/ConfigSet.py
b/waflib/ConfigSet.py
+@@ -146,7 +146,7 @@ class ConfigSet(object):
+ Utils.writef(filename,''.join(buf))
+ def load(self,filename):
+ tbl=self.table
+- code=Utils.readf(filename,m='rU')
++ code=Utils.readf(filename,m='r')
+ for m in re_imp.finditer(code):
+ g=m.group
+ tbl[g(2)]=eval(g(3))
+--- a/waflib/Context.py
b/waflib/Context.py
+@@ -106,7 +106,7 @@ class Context(ctx):
+ cache[node]=True
+ self.pre_recurse(node)
+ try:
+- function_code=node.read('rU',encoding)
++ function_code=node.read('r',encoding)
+
exec(compile(function_code,node.abspath(),'exec'),self.exec_dict)
+ finally:
+ self.post_recurse(node)
+@@ -346,7 +346,7 @@ def load_module(path,encoding=None):
+ pass
+ module=imp.new_module(WSCRIPT_FILE)
+ try:
+- code=Utils.readf(path,m='rU',encoding=encoding)
++ code=Utils.readf(path,m='r',encoding=encoding)
+ except EnvironmentError:
+ raise Errors.WafError('Could not read the file %r'%path)
+ module_dir=os.path.dirname(path)
diff -Nru oregano-0.84.41+dfsg.1/debian/patches/series
oregano-0.84.41+dfsg.1/debian/patches/series
--- oregano-0.84.41+dfsg.1/debian/patches/series2019-01-29
16:36:16.0 +0100
+++ oregano-0.84.41+dfsg.1/debian/patches/series2023-01-19
12:38:32.0 +0100
@@ -2,3 +2,4 @@
0007-Update-russian-translation.patch
0003-Remove-Encoding-field-in-desktop-file.patch
0004-Spelling-fixes.patch
+python3.11.patch
Bug#1028840: weather-util: FTBFS: ValueError: invalid mode: 'rUb'
Control: tags -1 patch
The attached patch resolves the issue.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1diff -Nru weather-util-2.4.1/debian/changelog
weather-util-2.4.1/debian/changelog
--- weather-util-2.4.1/debian/changelog 2020-08-30 22:03:08.0 +0200
+++ weather-util-2.4.1/debian/changelog 2023-01-19 12:19:41.0 +0100
@@ -1,3 +1,11 @@
+weather-util (2.4.1-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch to fix FTBFS with python3.11.
+(closes: #1028840)
+
+ -- Bas Couwenberg Thu, 19 Jan 2023 12:19:41 +0100
+
weather-util (2.4.1-1) unstable; urgency=low
* New upstream release (closes: #964721)
diff -Nru weather-util-2.4.1/debian/patches/python3.11.patch
weather-util-2.4.1/debian/patches/python3.11.patch
--- weather-util-2.4.1/debian/patches/python3.11.patch 1970-01-01
01:00:00.0 +0100
+++ weather-util-2.4.1/debian/patches/python3.11.patch 2023-01-19
12:19:39.0 +0100
@@ -0,0 +1,51 @@
+Description: Don't use U mode, removed in python3.11.
+Author: Bas Couwenberg
+Bug-Debian: https://bugs.debian.org/1028840
+
+--- a/weather.py
b/weather.py
+@@ -1386,7 +1386,7 @@ def correlate():
+ sys.stdout.write(message)
+ sys.stdout.flush()
+ count = 0
+-slist = codecs.open(slist_fn, "rU", "utf-8")
++slist = codecs.open(slist_fn, "r", "utf-8")
+ for line in slist:
+ icao = line.split("#")[0].strip()
+ if icao:
+@@ -1401,7 +1401,7 @@ def correlate():
+ sys.stdout.write(message)
+ sys.stdout.flush()
+ count = 0
+-nsd = codecs.open(nsd_fn, "rU", "utf-8")
++nsd = codecs.open(nsd_fn, "r", "utf-8")
+ for line in nsd:
+ line = str(line)
+ fields = line.split(";")
+@@ -1430,7 +1430,7 @@ def correlate():
+ sys.stdout.write(message)
+ sys.stdout.flush()
+ count = 0
+-ourairports = open(ourairports_fn, "rU")
++ourairports = open(ourairports_fn, "r")
+ for row in csv.reader(ourairports):
+ icao = row[12].lower()
+ if icao in stations:
+@@ -1468,7 +1468,7 @@ def correlate():
+ sys.stdout.write(message)
+ sys.stdout.flush()
+ count = 0
+-zlist = codecs.open(zlist_fn, "rU", "utf-8")
++zlist = codecs.open(zlist_fn, "r", "utf-8")
+ for line in zlist:
+ line = line.split("#")[0].strip()
+ if line:
+@@ -1481,7 +1481,7 @@ def correlate():
+ sys.stdout.flush()
+ count = 0
+ cpfz = {}
+-cpfzcf = codecs.open(cpfzcf_fn, "rU", "utf-8")
++cpfzcf = codecs.open(cpfzcf_fn, "r", "utf-8")
+ for line in cpfzcf:
+ fields = line.strip().split("|")
+ if len(fields) == 11 \
diff -Nru weather-util-2.4.1/debian/patches/series
weather-util-2.4.1/debian/patches/series
--- weather-util-2.4.1/debian/patches/series2017-01-19 20:56:41.0
+0100
+++ weather-util-2.4.1/debian/patches/series2023-01-19 12:17:27.0
+0100
@@ -1,2 +1,3 @@
fhs.patch
pypath.patch
+python3.11.patch
Bug#1028848: python-miio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
On Sat, 14 Jan 2023 14:02:05 +0100 Lucas Nussbaum wrote:> > ERRORS > _ ERROR collecting .pybuild/cpython3_3.10/build/miio/tests/test_airconditioningcompanion.py _ > ImportError while importing test module '/<>/.pybuild/cpython3_3.10/build/miio/tests/test_airconditioningcompanion.py'. > Hint: make sure your test modules/packages have valid Python names. > Traceback: > /usr/lib/python3.10/importlib/__init__.py:126: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > miio/__init__.py:49: in > from miio.discovery import Discovery > miio/discovery.py:8: in > import zeroconf > /usr/lib/python3/dist-packages/zeroconf/__init__.py:26: in > from ._core import Zeroconf > /usr/lib/python3/dist-packages/zeroconf/_core.py:36: in > from ._handlers import ( > /usr/lib/python3/dist-packages/zeroconf/_handlers.py:45: in > from ._services.info import ServiceInfo > /usr/lib/python3/dist-packages/zeroconf/_services/info.py:40: in > from .._utils.asyncio import get_running_loop, run_coro_with_timeout > /usr/lib/python3/dist-packages/zeroconf/_utils/asyncio.py:30: in > from async_timeout import timeout as asyncio_timeout > E ModuleNotFoundError: No module named 'async_timeout' python3-zeroconf has this dependency: python3-async-timeout (>= 4.0.1) | python3 (>> 3.11) Because python3.11 is now default python3-async-timeout doesn't get installed even though it's still required for python3.10. python3-async-timeout should probably be an hard dependency of python3-zeroconf until python3.10 is removed. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028762: pylint-plugin-utils: FTBFS: ModuleNotFoundError: No module named 'tomli'
On Sat, 14 Jan 2023 13:42:27 +0100 Lucas Nussbaum wrote: > == > ERROR: pylint_plugin_utils (unittest.loader._FailedTest) > -- > ImportError: Failed to import test module: pylint_plugin_utils > Traceback (most recent call last): > File "/usr/lib/python3.10/unittest/loader.py", line 470, in _find_test_path > package = self._get_module_from_name(name) > File "/usr/lib/python3.10/unittest/loader.py", line 377, in _get_module_from_name > __import__(name) > File "/<>/.pybuild/cpython3_3.10_pylint-plugin-utils/build/pylint_plugin_utils/__init__.py", line 4, in > from pylint.lint import PyLinter > File "/usr/lib/python3/dist-packages/pylint/lint/__init__.py", line 19, in > from pylint.config.exceptions import ArgumentPreprocessingError > File "/usr/lib/python3/dist-packages/pylint/config/__init__.py", line 25, in > from pylint.config.arguments_provider import UnsupportedAction > File "/usr/lib/python3/dist-packages/pylint/config/arguments_provider.py", line 15, in > from pylint.config.arguments_manager import _ArgumentsManager > File "/usr/lib/python3/dist-packages/pylint/config/arguments_manager.py", line 50, in > import tomli as tomllib > ModuleNotFoundError: No module named 'tomli' pylint has this dependency: python3-tomli | python3 (>> 3.11) Because python3.11 is now default python3-tomli doesn't get installed even though it's still required for python3.10. python3-tomli should probably be an hard dependency of pylint until python3.10 is removed. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028753: salt-pylint: FTBFS: ModuleNotFoundError: No module named 'tomli'
On Sat, 14 Jan 2023 13:44:49 +0100 Lucas Nussbaum wrote: == ERROR: saltpylint.py3modernize (unittest.loader._FailedTest) -- ImportError: Failed to import test module: saltpylint.py3modernize Traceback (most recent call last): File "/usr/lib/python3.10/unittest/loader.py", line 470, in _find_test_path package = self._get_module_from_name(name) File "/usr/lib/python3.10/unittest/loader.py", line 377, in _get_module_from_name __import__(name) File "/<>/.pybuild/cpython3_3.10/build/saltpylint/py3modernize/__init__.py", line 24, in from saltpylint.checkers import BaseChecker File "/<>/.pybuild/cpython3_3.10/build/saltpylint/checkers.py", line 13, in from pylint.checkers import BaseChecker as _BaseChecker File "/usr/lib/python3/dist-packages/pylint/checkers/__init__.py", line 48, in from pylint.checkers.base_checker import ( File "/usr/lib/python3/dist-packages/pylint/checkers/base_checker.py", line 17, in from pylint.config.arguments_provider import _ArgumentsProvider File "/usr/lib/python3/dist-packages/pylint/config/__init__.py", line 25, in from pylint.config.arguments_provider import UnsupportedAction File "/usr/lib/python3/dist-packages/pylint/config/arguments_provider.py", line 15, in from pylint.config.arguments_manager import _ArgumentsManager File "/usr/lib/python3/dist-packages/pylint/config/arguments_manager.py", line 50, in import tomli as tomllib ModuleNotFoundError: No module named 'tomli' pylint has this dependency: python3-tomli | python3 (>> 3.11) Because python3.11 is now default python3-tomli doesn't get installed even though it's still required for python3.10. python3-tomli should probably be an hard dependency of pylint until python3.10 is removed. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028853: python-pyvmomi: FTBFS: dh_auto_test: error: pybuild --test --test-tox -i python{version} -p "3.10 3.11" returned exit code 13
Control: tags -1 patch A fix has been committed in git: https://salsa.debian.org/python-team/packages/python-pyvmomi/-/commit/ee94929f94ddfaf0616e93b4bf2d8746db1cb5da Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028884: scanmem: FTBFS: make: *** [debian/rules:6: binary] Error 25
Control: tags -1 patch A fix has been committed in git: https://salsa.debian.org/debian/scanmem/-/commit/193063f600db49c003aed53de0d2fec8a375ca15 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028452: unblock: golang-1.19/1.19.5-1
On 1/19/23 10:26, Shengjing Zhu wrote: On Thu, Jan 19, 2023 at 4:55 PM Paul Gevers wrote: The history record for golang point release doesn't show regressions. That's good, are you talking about point release in general, or releases to stable? Missed this one. I'm talking about the upstream point release. We haven't met regression so far when we update golang-1.x packages in unstable. I remember 1.18.4 introducing a regression that broke icingadb: https://bugs.debian.org/1015088 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
