Bug#1056298: riseup-vpn dns configuration don't work with systemd-resolved
package: riseup-vpn severity: grave version: 0.21.11+ds1-5+b4 It misses a dependency on openvpn-systemd-resolved and on boomworm it was working after installing it. But on mobian trixie, which has systemd-resolved installed by default (through mobian-base), dns resolution fails when riseup vpn is connected. error log attached ;; communications error to 127.0.0.53#53: timed out ;; communications error to 127.0.0.53#53: timed out ;; no servers could be reached
Processed: retitle 1056281 to snort: CVE-2023-20246
Processing commands for cont...@bugs.debian.org: > retitle 1056281 snort: CVE-2023-20246 Bug #1056281 [src:snort] snort: CVE-2023-20246 CVE-2023-20031 Changed Bug title to 'snort: CVE-2023-20246' from 'snort: CVE-2023-20246 CVE-2023-20031'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1056183
Processing commands for cont...@bugs.debian.org: > affects 1056183 + tex-common Bug #1056183 [texlive-binaries] texlive-luatex: lualatex exits immediately due to new zlib Bug #1056186 [texlive-binaries] texlive-binaries: zlib library mismatch Bug #1056189 [texlive-binaries] luahbtex: PANIC: unprotected error in call to Lua API (zlib library version does not match - header: 1.2.13, library: 1.3) Bug #1056210 [texlive-binaries] luatex panics with zlib 1.3 Added indication that 1056183 affects tex-common Added indication that 1056186 affects tex-common Added indication that 1056189 affects tex-common Added indication that 1056210 affects tex-common > thanks Stopping processing here. Please contact me if you need assistance. -- 1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183 1056186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056186 1056189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056189 1056210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Looks like the systemctl links are gone but not the pm-utils ones
Processing control commands: > tags -1 + confirmed Bug #1056279 [molly-guard] Symlinks in /usr/lib/molly-guard/ are gone after upgrade Added tag(s) confirmed. > clone -1 -2 Bug #1056279 [molly-guard] Symlinks in /usr/lib/molly-guard/ are gone after upgrade Bug 1056279 cloned as bug 1056292 > reassign -2 systemd-sysv Bug #1056292 [molly-guard] Symlinks in /usr/lib/molly-guard/ are gone after upgrade Bug reassigned from package 'molly-guard' to 'systemd-sysv'. No longer marked as found in versions molly-guard/0.8.1. Ignoring request to alter fixed versions of bug #1056292 to the same values previously set > found -2 255-rc2-1 Bug #1056292 [systemd-sysv] Symlinks in /usr/lib/molly-guard/ are gone after upgrade There is no source info for the package 'systemd-sysv' at version '255-rc2-1' with architecture '' Unable to make a source version for version '255-rc2-1' Marked as found in versions 255-rc2-1. > retitle -2 duplicated diversions are still broken by moved files Bug #1056292 [systemd-sysv] Symlinks in /usr/lib/molly-guard/ are gone after upgrade Changed Bug title to 'duplicated diversions are still broken by moved files' from 'Symlinks in /usr/lib/molly-guard/ are gone after upgrade'. -- 1056279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056279 1056292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056279: Looks like the systemctl links are gone but not the pm-utils ones
Control: tags -1 + confirmed Control: clone -1 -2 Control: reassign -2 systemd-sysv Control: found -2 255-rc2-1 Control: retitle -2 duplicated diversions are still broken by moved files On Sun, Nov 19, 2023 at 02:08:35PM -0800, Francois Marier wrote: > I'm also a little confused by the diverts. Perhaps something changed in > systemd (which owns the ultimate underlying symlinks)? I was sure I had this properly tested and yet it doesn't work as expected. I'm sorry for having gotten this wrong. Reproducer: mmdebstrap bookworm /dev/null http://deb.debian.org/debian --include=systemd-sysv,molly-guard --customize-hook='sed -i -e s/bookworm/sid/ $1/etc/apt/sources.list' --chrooted-customize-hook='apt-get update' --chrooted-customize-hook='apt-get -y install systemd-sysv' --customize-hook='ls -l $1/lib/molly-guard/' Different reproducer: mmdebstrap trixie /dev/null http://deb.debian.org/debian --include=systemd-sysv,molly-guard --customize-hook='sed -i -e s/trixie/sid/ $1/etc/apt/sources.list' --chrooted-customize-hook='apt-get update' --customize-hook='test -e $1/lib/molly-guard/reboot' --chrooted-customize-hook='apt-get -y install systemd-sysv' --customize-hook='ls -l $1/lib/molly-guard/' Specifically, the files vanish on upgrading systemd-sysv such that /sbin/reboot moves to /usr/sbin/reboot. I should have seen this failure in earlier tests. I've dug into dpkg and usually when it moves a file from / to /usr, it'll first unpack the new file (unknowingly replacing the existing old one) and then removes the old one (via pkg_remove_old_files). During that removal, it has a check to see whether the file to be removed happens to match one of the files it just installed and skips the removal in that case. For some reason, this safety check does not work when the file is diverted. So I have a vague understanding of what is wrong here, but no solution yet. For the time being, I duplicate this into a blocker bug for systemd-sysv to prevent it from migrating to testing until we figure out a solution. Sorry for the inconvenience. Helmut
Bug#1042640: marked as done (lazr.config: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')
Your message dated Sun, 19 Nov 2023 22:48:58 + with message-id and subject line Bug#1042640: fixed in lazr.config 3.0-1 has caused the Debian Bug report #1042640, regarding lazr.config: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042640 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lazr.config Version: 2.2.3-3 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, lazr.config fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > python3 setup.py build_sphinx > /usr/lib/python3/dist-packages/setuptools/dist.py:945: > SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. > !! > > > > Please replace its usage with implicit namespaces (PEP 420). > > See > https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages > for details. > > > > !! > ep.load()(self, ep.name, value) > usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] >or: setup.py --help [cmd1 cmd2 ...] >or: setup.py --help-commands >or: setup.py cmd --help > > error: invalid command 'build_sphinx' > make[1]: *** [debian/rules:11: override_dh_installdocs] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/30/exp/lazr.config_2.2.3-3_unstable_sphinx-exp.log Please see [1] for Sphinx changelog and [2] for Docutils changelog. Also see [3] for the list of deprecated/removed APIs in Sphinx and possible alternatives to them. Some notable changes in Sphinx 6 and Sphinx 7: - Sphinx no longer includes jquery.js and underscore.js by default. Please use python3-sphinxcontrib.jquery package if you are using a custom template and it still needs jquery. - The setup.py build_sphinx command was removed. Please instead call sphinx-build or "python3 -m sphinx" directly. - For packages using the extlinks extension, the caption should contain exactly one "%s" placeholder (if caption is not None). In case you have questions, please Cc sph...@packages.debian.org on reply. [1]: https://www.sphinx-doc.org/en/master/changes.html [2]: https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt [3]: https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx7.1=python-modules-t...@lists.alioth.debian.org=1=1=1=1#results If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects --- End Message --- --- Begin Message --- Source: lazr.config Source-Version: 3.0-1 Done: Colin Watson We believe that the bug you reported is fixed in the latest version of lazr.config, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson (supplier of updated lazr.config package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 19 Nov 2023 22:26:02 + Source: lazr.config Architecture: source Version: 3.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Colin Watson Closes: 1042640 Changes: lazr.config (3.0-1) unstable; urgency=medium . * Update standards version to 4.6.2, no changes needed. * Update watch file format version to 4. * Opportunistically check upstream PGP signatures. * Use sphinx-build rather than "setup.py build_sphinx" (closes: #1042640). * New
Bug#1056288: django-assets FTBFS: TypeError: 'TextNode' object is not iterable
Source: django-assets Version: 2.0-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=django-assets=all=2.0-3=1700432008=0 ... dh_auto_test -i -O--buildsystem=pybuild I: pybuild base:310: cd /<>/.pybuild/cpython3_3.11_django-assets/build; python3.11 -m nose -v tests tests.test_django.TestConfig.test_custom_options ... ok The builtin options have different names within the Django ... ok tests.test_django.TestFilter.test_template ... ok tests.test_django.TestLoader.test ... ERROR tests.test_django.TestLoader.test_cached_loader ... ERROR Finders are used to find source files. ... ok If debug is disabled, the finders are not used. ... ok Test that the cssrewrite filter can deal with staticfiles. ... ok Globs can be used across staticdirs. ... ok Recursive globs. ... ok An error is raised if a source file is missing. ... ok The files we write to STATIC_ROOT are served in debug mode ... ok tests.test_django.TestTemplateTag.test_debug_option ... ok Ensure the tag correcly spits out the urls the bundle returns. ... ok tests.test_django.TestTemplateTag.test_reference_bundles ... ok tests.test_django.TestTemplateTag.test_reference_files ... ok tests.test_django.TestTemplateTag.test_reference_mixed ... ok Using commas is optional. ... ok tests.test_django.TestTemplateTag.test_with_vars ... ok == ERROR: tests.test_django.TestLoader.test -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/.pybuild/cpython3_3.11_django-assets/build/tests/test_django.py", line 193, in test bundles = self.loader.load_bundles() ^^ File "/<>/.pybuild/cpython3_3.11_django-assets/build/django_assets/loaders.py", line 79, in load_bundles bundles.extend(self.with_file(filename, self._parse) or []) ^ File "/usr/lib/python3/dist-packages/webassets/loaders.py", line 333, in with_file return then_run(filename, contents) File "/<>/.pybuild/cpython3_3.11_django-assets/build/django_assets/loaders.py", line 110, in _parse for node in t: # don't move into _recurse_node, ``Template`` has a .nodelist attribute File "/usr/lib/python3/dist-packages/django/template/base.py", line 158, in __iter__ yield from node TypeError: 'TextNode' object is not iterable == ERROR: tests.test_django.TestLoader.test_cached_loader -- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/<>/.pybuild/cpython3_3.11_django-assets/build/tests/test_django.py", line 203, in test_cached_loader bundles = self.loader.load_bundles() ^^ File "/<>/.pybuild/cpython3_3.11_django-assets/build/django_assets/loaders.py", line 79, in load_bundles bundles.extend(self.with_file(filename, self._parse) or []) ^ File "/usr/lib/python3/dist-packages/webassets/loaders.py", line 333, in with_file return then_run(filename, contents) File "/<>/.pybuild/cpython3_3.11_django-assets/build/django_assets/loaders.py", line 110, in _parse for node in t: # don't move into _recurse_node, ``Template`` has a .nodelist attribute File "/usr/lib/python3/dist-packages/django/template/base.py", line 158, in __iter__ yield from node TypeError: 'TextNode' object is not iterable -- Ran 19 tests in 0.113s FAILED (errors=2)
Processed: Re: xarray test failure on s390x
Processing control commands: > tags -1 patch Bug #1053700 [src:python-xarray] python-xarray: autopkgtest regression on s390x Added tag(s) patch. -- 1053700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053700: xarray test failure on s390x
Control: tags -1 patch
These all come from xarray/tests/test_coding_times.py, and are probably
fixable by replacing both instances of ("M8[ns]" if
sys.byteorder=='big' else "haven't actually tried that.
Bug#1056279: Looks like the systemctl links are gone but not the pm-utils ones
CCing Helmut who wrote the initial patch for systemd 255+ support (see Bug#1055510). I also see the same thing: $ ls -lh /usr/lib/molly-guard/ Permissions Size User Group Date Modified Name .rwxr-xr-x 3,4k root root 11 nov 14:02 molly-guard* lrwxrwxrwx31 root root 14 nov 2019 pm-hibernate -> /usr/lib/pm-utils/bin/pm-action* lrwxrwxrwx31 root root 14 nov 2019 pm-suspend -> /usr/lib/pm-utils/bin/pm-action* lrwxrwxrwx31 root root 14 nov 2019 pm-suspend-hybrid -> /usr/lib/pm-utils/bin/pm-action* $ sudo reboot --help E: not a regular file: /usr/lib/molly-guard/reboot I'm also a little confused by the diverts. Perhaps something changed in systemd (which owns the ultimate underlying symlinks)? Francois -- https://fmarier.org/
Bug#1050854: xarray test failure on amd64
This bug is now a crash (not the original error message): https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-xarray/39962554/log.gz I don't know whether the same patch still works. The Salsa repository now appears to be up to date. You probably also want to include the fixes for the other two RC bugs (see there).
Bug#1056287: adios2: binary-all FTBFS
Source: adios2 Version: 2.8.2+dfsg1-2 Severity: serious Tags: ftbfs X-Debbugs-Cc: Drew Parsons https://buildd.debian.org/status/fetch.php?pkg=adios2=all=2.8.2%2Bdfsg1-2=1700402832=0 ... debian/rules override_dh_missing make[1]: Entering directory '/<>' dh_missing --sourcedir=install-serial dh_missing: warning: usr/bin/adios2-config.serial exists in install-serial but is not installed to anywhere dh_missing: error: missing files, aborting The following debhelper tools have reported what they installed (with files per package) * dh_cmake_install: adios2-data (13), adios2-mpi-bin (7), adios2-scripts (14), adios2-serial-bin (4), libadios2-mpi-c++11-2 (4), libadios2-mpi-c++11-dev (16), libadios2-mpi-c-2 (4), libadios2-mpi-c-dev (12), libadios2-mpi-core-2 (5), libadios2-mpi-core-dev (184), libadios2-mpi-fortran-2 (4), libadios2-mpi-fortran-dev (33), libadios2-serial-c++11-2 (2), libadios2-serial-c++11-dev (15), libadios2-serial-c-2 (2), libadios2-serial-c-dev (11), libadios2-serial-core-2 (3), libadios2-serial-core-dev (183), libadios2-serial-fortran-2 (2), libadios2-serial-fortran-dev (30), python3-adios2-mpi (1), python3-adios2-serial (1) * dh_install: adios2-data (0), adios2-mpi-bin (0), adios2-scripts (0), adios2-serial-bin (0), libadios2-common-c++11-dev (0), libadios2-common-c-dev (0), libadios2-common-core-dev (0), libadios2-mpi-auxiliary-2 (10), libadios2-mpi-auxiliary-dev (6), libadios2-mpi-c++11-2 (0), libadios2-mpi-c++11-dev (0), libadios2-mpi-c-2 (0), libadios2-mpi-c-dev (0), libadios2-mpi-core-2 (0), libadios2-mpi-core-dev (0), libadios2-mpi-fortran-2 (0), libadios2-mpi-fortran-dev (0), libadios2-serial-auxiliary-2 (10), libadios2-serial-auxiliary-dev (6), libadios2-serial-c++11-2 (0), libadios2-serial-c++11-dev (0), libadios2-serial-c-2 (0), libadios2-serial-c-dev (0), libadios2-serial-core-2 (0), libadios2-serial-core-dev (0), libadios2-serial-fortran-2 (0), libadios2-serial-fortran-dev (0), python3-adios2 (1), python3-adios2-mpi (0), python3-adios2-serial (0) * dh_installdocs: adios2-data (0), adios2-mpi-bin (0), adios2-scripts (0), adios2-serial-bin (0), libadios2-common-c++11-dev (0), libadios2-common-c-dev (0), libadios2-common-core-dev (0), libadios2-mpi-auxiliary-2 (0), libadios2-mpi-auxiliary-dev (0), libadios2-mpi-c++11-2 (0), libadios2-mpi-c++11-dev (0), libadios2-mpi-c-2 (0), libadios2-mpi-c-dev (0), libadios2-mpi-core-2 (0), libadios2-mpi-core-dev (0), libadios2-mpi-fortran-2 (0), libadios2-mpi-fortran-dev (0), libadios2-serial-auxiliary-2 (0), libadios2-serial-auxiliary-dev (0), libadios2-serial-c++11-2 (0), libadios2-serial-c++11-dev (0), libadios2-serial-c-2 (0), libadios2-serial-c-dev (0), libadios2-serial-core-2 (0), libadios2-serial-core-dev (0), libadios2-serial-fortran-2 (0), libadios2-serial-fortran-dev (0), python3-adios2 (1), python3-adios2-mpi (0), python3-adios2-serial (0) If the missing files are installed by another tool, please file a bug against it. When filing the report, if the tool is not part of debhelper itself, please reference the "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.md.gz) Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built If the omission is intentional or no other helper can take care of this consider adding the paths to debian/not-installed. make[1]: *** [debian/rules:172: override_dh_missing] Error 25
Bug#1056286: node-get-stream: FTBFS in sid with internet access disabled
Package: node-get-stream
Version: 8.0.1-8
Severity: serious
Tags: patch
Hello,
looks like the package is using internet during tests, and so FTBFS without
internet access.
The log is:
✔ string › handles truncated UTF-8 sequences over maxBuffer
✔ string › get stream with invalid UTF-8 sequences
─
integration › works with fetch()
Rejected promise returned by test. Reason:
TypeError {
cause: Error {
code: 'ENOTFOUND',
errno: -3008,
hostname: 'nodejs.org',
syscall: 'getaddrinfo',
message: 'getaddrinfo ENOTFOUND nodejs.org',
},
message: 'fetch failed',
}
› async file://test/integration.js:66:18
─
1 test failed
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Can you please have a look?
thanks
G.
Processed: tagging 1056284, tagging 1056283, tagging 1056282 ...
Processing commands for cont...@bugs.debian.org: > tags 1056284 + upstream Bug #1056284 [src:nss] nss: CVE-2023-5388 Added tag(s) upstream. > tags 1056283 + upstream fixed-upstream Bug #1056283 [src:postgresql-15] postgresql-15: CVE-2023-5868 CVE-2023-5869 CVE-2023-5870 Added tag(s) upstream and fixed-upstream. > tags 1056282 + upstream Bug #1056282 [src:gpac] gpac: CVE-2023-47384 CVE-2023-48011 CVE-2023-48013 CVE-2023-48014 CVE-2023-5998 CVE-2023-46001 Added tag(s) upstream. > # remove CVE which was for grpc > retitle 1056282 gpac: CVE-2023-47384 CVE-2023-48011 CVE-2023-48013 > CVE-2023-48014 CVE-2023-5998 CVE-2023-46001 Bug #1056282 [src:gpac] gpac: CVE-2023-47384 CVE-2023-48011 CVE-2023-48013 CVE-2023-48014 CVE-2023-5998 CVE-2023-46001 Ignoring request to change the title of bug#1056282 to the same title > thanks Stopping processing here. Please contact me if you need assistance. -- 1056282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056282 1056283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056283 1056284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1056282 to gpac: CVE-2023-47384 CVE-2023-48011 CVE-2023-48013 CVE-2023-48014 CVE-2023-5998 CVE-2023-46001
Processing commands for cont...@bugs.debian.org: > retitle 1056282 gpac: CVE-2023-47384 CVE-2023-48011 CVE-2023-48013 > CVE-2023-48014 CVE-2023-5998 CVE-2023-46001 Bug #1056282 [src:gpac] gpac: CVE-2023-47384 CVE-2023-4785 CVE-2023-48011 CVE-2023-48013 CVE-2023-48014 CVE-2023-5998 CVE-2023-46001 Changed Bug title to 'gpac: CVE-2023-47384 CVE-2023-48011 CVE-2023-48013 CVE-2023-48014 CVE-2023-5998 CVE-2023-46001' from 'gpac: CVE-2023-47384 CVE-2023-4785 CVE-2023-48011 CVE-2023-48013 CVE-2023-48014 CVE-2023-5998 CVE-2023-46001'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056282: gpac: CVE-2023-47384 CVE-2023-4785 CVE-2023-48011 CVE-2023-48013 CVE-2023-48014 CVE-2023-5998 CVE-2023-46001
Source: gpac X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for gpac. CVE-2023-47384[0]: | MP4Box GPAC v2.3-DEV-rev617-g671976fcc-master was discovered to | contain a memory leak in the function gf_isom_add_chapter at | /isomedia/isom_write.c. This vulnerability allows attackers to cause | a Denial of Service (DoS) via a crafted MP4 file. https://github.com/gpac/gpac/issues/2672 CVE-2023-4785[1]: | Lack of error handling in the TCP server in Google's gRPC starting | version 1.23 on posix-compatible platforms (ex. Linux) allows an | attacker to cause a denial of service by initiating a significant | number of connections with the server. Note that gRPC C++ Python, | and Ruby are affected, but gRPC Java, and Go are NOT affected. https://github.com/grpc/grpc/pull/33656 https://github.com/grpc/grpc/pull/33667 https://github.com/grpc/grpc/pull/33669 https://github.com/grpc/grpc/pull/33670 https://github.com/grpc/grpc/pull/33672 CVE-2023-48011[2]: | GPAC v2.3-DEV-rev566-g50c2ab06f-master was discovered to contain a | heap-use-after-free via the flush_ref_samples function at | /gpac/src/isomedia/movie_fragments.c. https://github.com/gpac/gpac/issues/2611 https://github.com/gpac/gpac/commit/c70f49dda4946d6db6aa55588f6a756b76bd84ea CVE-2023-48013[3]: | GPAC v2.3-DEV-rev566-g50c2ab06f-master was discovered to contain a | double free via the gf_filterpacket_del function at | /gpac/src/filter_core/filter.c. https://github.com/gpac/gpac/issues/2612 https://github.com/gpac/gpac/commit/cd8a95c1efb8f5bfc950b86c2ef77b4c76f6b893 CVE-2023-48014[4]: | GPAC v2.3-DEV-rev566-g50c2ab06f-master was discovered to contain a | stack overflow via the hevc_parse_vps_extension function at | /media_tools/av_parsers.c. https://github.com/gpac/gpac/issues/2613 https://github.com/gpac/gpac/commit/66abf0887c89c29a484d9e65e70882794e9e3a1b CVE-2023-5998[5]: | Out-of-bounds Read in GitHub repository gpac/gpac prior to | 2.3.0-DEV. https://huntr.com/bounties/ea02a231-b688-422b-a881-ef415bcf6113 https://github.com/gpac/gpac/commit/db74835944548fc3bdf03121b0e012373bdebb3e CVE-2023-46001[6]: | Buffer Overflow vulnerability in gpac MP4Box v.2.3-DEV- | rev573-g201320819-master allows a local attacker to cause a denial | of service via the gpac/src/isomedia/isom_read.c:2807:51 function in | gf_isom_get_user_data. https://github.com/gpac/gpac/issues/2629 https://github.com/gpac/gpac/commit/e79b0cf7e72404750630bc01340e999f3940dbc4 If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-47384 https://www.cve.org/CVERecord?id=CVE-2023-47384 [1] https://security-tracker.debian.org/tracker/CVE-2023-4785 https://www.cve.org/CVERecord?id=CVE-2023-4785 [2] https://security-tracker.debian.org/tracker/CVE-2023-48011 https://www.cve.org/CVERecord?id=CVE-2023-48011 [3] https://security-tracker.debian.org/tracker/CVE-2023-48013 https://www.cve.org/CVERecord?id=CVE-2023-48013 [4] https://security-tracker.debian.org/tracker/CVE-2023-48014 https://www.cve.org/CVERecord?id=CVE-2023-48014 [5] https://security-tracker.debian.org/tracker/CVE-2023-5998 https://www.cve.org/CVERecord?id=CVE-2023-5998 [6] https://security-tracker.debian.org/tracker/CVE-2023-46001 https://www.cve.org/CVERecord?id=CVE-2023-46001 Please adjust the affected versions in the BTS as needed.
Bug#1056281: snort: CVE-2023-20246 CVE-2023-20031
Source: snort X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for snort. CVE-2023-20246[0]: | Multiple Cisco products are affected by a vulnerability in Snort | access control policies that could allow an unauthenticated, remote | attacker to bypass the configured policies on an affected system. | This vulnerability is due to a logic error that occurs when the | access control policies are being populated. An attacker could | exploit this vulnerability by establishing a connection to an | affected device. A successful exploit could allow the attacker to | bypass configured access control rules on the affected system. https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ftd-snort3acp-bypass-3bdR2BEh CVE-2023-20031[1]: | A vulnerability in the SSL/TLS certificate handling of Snort 3 | Detection Engine integration with Cisco Firepower Threat Defense | (FTD) Software could allow an unauthenticated, remote attacker to | cause the Snort 3 detection engine to restart. This vulnerability is | due to a logic error that occurs when an SSL/TLS certificate that is | under load is accessed when it is initiating an SSL connection. | Under specific, time-based constraints, an attacker could exploit | this vulnerability by sending a high rate of SSL/TLS connection | requests to be inspected by the Snort 3 detection engine on an | affected device. A successful exploit could allow the attacker to | cause the Snort 3 detection engine to reload, resulting in either a | bypass or a denial of service (DoS) condition, depending on device | configuration. The Snort detection engine will restart | automatically. No manual intervention is required. https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ftd-snort3-8U4HHxH8 If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-20246 https://www.cve.org/CVERecord?id=CVE-2023-20246 [1] https://security-tracker.debian.org/tracker/CVE-2023-20031 https://www.cve.org/CVERecord?id=CVE-2023-20031 Please adjust the affected versions in the BTS as needed.
Bug#1056279: Symlinks in /usr/lib/molly-guard/ are gone after upgrade
Christoph Biedl wrote... > after upgrading from 0.7.2 to 0.8.1, the symlinks in /usr/lib/molly-guard/ > are gone. It was suggested in IRC this might be the effect of another package's upgrade. I find that unlikely since no other package should touch /usr/lib/molly-guard/ - still, here's the upgrade list after that I found the change: 2023-11-19 18:50:51 upgrade bsdutils:ppc64 1:2.39.2-5 1:2.39.2-6 2023-11-19 18:50:53 upgrade coreutils:ppc64 9.1-1 9.4-2 2023-11-19 18:50:55 upgrade libsmartcols1:ppc64 2.39.2-5 2.39.2-6 2023-11-19 18:50:56 upgrade util-linux-extra:ppc64 2.39.2-5 2.39.2-6 2023-11-19 18:50:57 upgrade util-linux:ppc64 2.39.2-5 2.39.2-6 2023-11-19 18:51:04 upgrade mount:ppc64 2.39.2-5 2.39.2-6 2023-11-19 18:51:05 upgrade systemd-dev:all 254.5-1 255~rc2-2 2023-11-19 18:51:06 upgrade libblkid1:ppc64 2.39.2-5 2.39.2-6 2023-11-19 18:51:07 upgrade libuuid1:ppc64 2.39.2-5 2.39.2-6 2023-11-19 18:51:08 upgrade libfdisk1:ppc64 2.39.2-5 2.39.2-6 2023-11-19 18:51:09 upgrade libmount1:ppc64 2.39.2-5 2.39.2-6 2023-11-19 18:51:10 upgrade systemd:ppc64 254.5-1 255~rc2-2 2023-11-19 18:51:13 upgrade libsystemd-shared:ppc64 254.5-1 255~rc2-2 2023-11-19 18:51:14 upgrade libsystemd0:ppc64 254.5-1 255~rc2-2 2023-11-19 18:51:15 upgrade molly-guard:all 0.7.2 0.8.1 Note: The timestamp of /usr/lib/molly-guard/ fits here: drwxr-xr-x 2 root root 4096 2023-11-19 18:52:08.994207913 +0100 /usr/lib/molly-guard/ 2023-11-19 18:52:08 upgrade systemd-sysv:ppc64 254.5-1 255~rc2-2 2023-11-19 18:52:09 upgrade libdb5.3:ppc64 5.3.28+dfsg2-3 5.3.28+dfsg2-4 2023-11-19 18:52:10 upgrade zlib1g:ppc64 1:1.2.13.dfsg-3 1:1.3.dfsg-2 2023-11-19 18:52:12 upgrade libelf1:ppc64 0.189-4 0.190-1 2023-11-19 18:52:13 upgrade libtirpc-common:all 1.3.3+ds-1 1.3.4+ds-1 2023-11-19 18:52:14 upgrade libtirpc3:ppc64 1.3.3+ds-1 1.3.4+ds-1 2023-11-19 18:52:16 upgrade iproute2:ppc64 6.5.0-5 6.6.0-1 2023-11-19 18:52:19 upgrade libgpg-error0:ppc64 1.47-2 1.47-3 2023-11-19 18:52:20 upgrade udev:ppc64 254.5-1 255~rc2-2 2023-11-19 18:52:21 upgrade libudev1:ppc64 254.5-1 255~rc2-2 2023-11-19 18:52:23 upgrade mawk:ppc64 1.3.4.20230808-1 1.3.4.20231102-1 2023-11-19 18:52:23 upgrade fdisk:ppc64 2.39.2-5 2.39.2-6 2023-11-19 18:52:24 upgrade vim-nox:ppc64 2:9.0.2087-1 2:9.0.2103-1 2023-11-19 18:52:25 upgrade vim:ppc64 2:9.0.2087-1 2:9.0.2103-1 2023-11-19 18:52:26 upgrade vim-common:all 2:9.0.2087-1 2:9.0.2103-1 2023-11-19 18:52:28 upgrade vim-runtime:all 2:9.0.2087-1 2:9.0.2103-1 2023-11-19 18:52:32 upgrade autopkgtest:all 5.31 5.31.1 2023-11-19 18:52:33 upgrade bsdextrautils:ppc64 2.39.2-5 2.39.2-6 2023-11-19 18:52:35 upgrade libglib2.0-0:ppc64 2.78.1-3 2.78.1-4 2023-11-19 18:52:36 upgrade libio-socket-ssl-perl:all 2.083-1 2.084-1 2023-11-19 18:52:37 upgrade libmaxminddb0:ppc64 1.7.1-1 1.8.0-1 2023-11-19 18:52:38 upgrade libsasl2-modules-db:ppc64 2.1.28+dfsg1-3 2.1.28+dfsg1-4 2023-11-19 18:52:38 upgrade libsasl2-2:ppc64 2.1.28+dfsg1-3 2.1.28+dfsg1-4 2023-11-19 18:52:39 upgrade pci.ids:all 0.0~2023.08.10-1 0.0~2023.09.22-1 Hope this is helpful, Christoph signature.asc Description: PGP signature
Bug#1055922: rmatrix: ABI change in Matrix 1.6-2
On 19 November 2023 at 09:59, Dirk Eddelbuettel wrote: | On 19 November 2023 at 13:49, Graham Inggs wrote: | | We don't believe only touching debian/changelog, or a binNMU, is | | sufficient. We were surprised that your r-cran-lme4 upload did not at | | least include: | | Depends: r-cran-matrix (>= 1.6-2-1) | | Without that relationship, r-cran-lme4 could migrate to testing and be | | installed on users' systems without the corresponding version of | | r-cran-matrix. It is no surprise that the excuses page for lme4 [4] | | is all red, because that is exactly what is being tested. More on | | this to come in my next email. | | I can add that, and probably should have. And I agree with the sentiment in | your other mail that a transition is overkill here. Done in lme4 1.1-35.1-3. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1056279: Symlinks in /usr/lib/molly-guard/ are gone after upgrade
Package: molly-guard Version: 0.8.1 Severity: grave X-Debbugs-Cc: debian.a...@manchmal.in-ulm.de Greetings, after upgrading from 0.7.2 to 0.8.1, the symlinks in /usr/lib/molly-guard/ are gone. As this happened on a second machine today, I reckon it's not a coincidence. Current state: # ls -l /usr/lib/molly-guard/ total 8 -rwxr-xr-x 1 root root 99 5. Okt 00:17 coldreboot -rwxr-xr-x 1 root root 3365 11. Nov 23:02 molly-guard Old state: # ls -l /usr/lib/molly-guard/ total 7 -rwxr-xr-x 1 root root 99 5. Okt 00:17 coldreboot lrwxrwxrwx 1 root root 14 30. Sep 12:34 halt -> /bin/systemctl -rwxr-xr-x 1 root root 2847 9. Jul 2019 molly-guard lrwxrwxrwx 1 root root 14 30. Sep 12:34 poweroff -> /bin/systemctl lrwxrwxrwx 1 root root 14 30. Sep 12:34 reboot -> /bin/systemctl lrwxrwxrwx 1 root root 14 30. Sep 12:34 shutdown -> /bin/systemctl This is the upgrade log: Preparing to unpack .../molly-guard_0.8.1_all.deb ... No diversion 'diversion of /sbin/pm-hibernate by molly-guard', none removed. No diversion 'diversion of /sbin/pm-suspend by molly-guard', none removed. No diversion 'diversion of /sbin/pm-suspend-hybrid by molly-guard', none removed. Adding 'diversion of /usr/sbin/halt to /usr/lib/molly-guard/halt by molly-guard' Leaving 'diversion of /sbin/halt to /lib/molly-guard/halt by molly-guard' Adding 'diversion of /usr/sbin/poweroff to /usr/lib/molly-guard/poweroff by molly-guard' Leaving 'diversion of /sbin/poweroff to /lib/molly-guard/poweroff by molly-guard' Adding 'diversion of /usr/sbin/reboot to /usr/lib/molly-guard/reboot by molly-guard' Leaving 'diversion of /sbin/reboot to /lib/molly-guard/reboot by molly-guard' Adding 'diversion of /usr/sbin/shutdown to /usr/lib/molly-guard/shutdown by molly-guard' Leaving 'diversion of /sbin/shutdown to /lib/molly-guard/shutdown by molly-guard' Adding 'diversion of /usr/sbin/coldreboot to /usr/lib/molly-guard/coldreboot by molly-guard' Leaving 'diversion of /sbin/coldreboot to /lib/molly-guard/coldreboot by molly-guard' Removing 'diversion of /usr/sbin/pm-hibernate to /lib/molly-guard/pm-hibernate by molly-guard' Adding 'diversion of /usr/sbin/pm-hibernate to /usr/lib/molly-guard/pm-hibernate by molly-guard' Removing 'diversion of /usr/sbin/pm-suspend to /lib/molly-guard/pm-suspend by molly-guard' Adding 'diversion of /usr/sbin/pm-suspend to /usr/lib/molly-guard/pm-suspend by molly-guard' Removing 'diversion of /usr/sbin/pm-suspend-hybrid to /lib/molly-guard/pm-suspend-hybrid by molly-guard' Adding 'diversion of /usr/sbin/pm-suspend-hybrid to /usr/lib/molly-guard/pm-suspend-hybrid by molly-guard' Unpacking molly-guard (0.8.1) over (0.7.2) ... dpkg: warning: unable to delete old directory '/lib/molly-guard': Directory not empty Setting up molly-guard (0.8.1) ... The resultat is a major problem, hence the severity: Trying to shut down or reboot just triggers an error: # shutdown -P E: not a regular file: /usr/lib/molly-guard/shutdown (Workaround: Manually restore the links.) Looking into the maintainer scripts, I see some changes were done. Can you please re-check they to the right thing? Regards, Chri- "diversions are a nightmare" stoph signature.asc Description: PGP signature
Bug#1042693: marked as done (python-django-celery-results: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2)
Your message dated Sun, 19 Nov 2023 18:06:21 + with message-id and subject line Bug#1042693: fixed in python-django-celery-results 2.5.1-2 has caused the Debian Bug report #1042693, regarding python-django-celery-results: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-django-celery-results Version: 2.5.1-1 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, python-django-celery-results fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/views.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/utils.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/apps.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/__init__.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/urls.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/admin.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/models.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/managers.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > creating > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying > django_celery_results/migrations/0011_taskresult_periodic_task_name.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0008_chordcounter.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0006_taskresult_date_created.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/__init__.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0003_auto_20181106_1101.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0010_remove_duplicate_indices.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0007_remove_taskresult_hidden.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0001_initial.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0009_groupresult.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0002_add_task_name_args_kwargs.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0004_auto_20190516_0412.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0005_taskresult_worker.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > creating > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/backends > copying django_celery_results/backends/cache.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/backends > copying django_celery_results/backends/__init__.py -> > /<>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/backends > copying django_celery_results/backends/database.py -> >
Bug#1056240: marked as done (debputy-py.test calls py3versions -s without depending on python3-all)
Your message dated Sun, 19 Nov 2023 18:04:06 +
with message-id
and subject line Bug#1056240: fixed in debputy 0.1.8
has caused the Debian Bug report #1056240,
regarding debputy-py.test calls py3versions -s without depending on python3-all
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1056240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:debputy
Version: 0.1.7.8
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
debputy-py.test calls py3versions -s without depending on python3-all.
[...]
234s autopkgtest [18:22:37]: test debputy-py.test: [---
234s + mkdir /tmp/autopkgtest.zLpGEQ/autopkgtest_tmp/debian
234s + cp -r pyproject.toml tests/ /tmp/autopkgtest.zLpGEQ/autopkgtest_tmp
234s + cp -a debian/control /tmp/autopkgtest.zLpGEQ/autopkgtest_tmp/debian
234s + export PYTHONWARNINGS=d
234s + DEBPUTY_PYTHONPATH=/usr/share/dh-debputy
234s + PYTHOHPATH=
234s + [ ]
234s + PYTHOHPATH=/usr/share/dh-debputy
234s + cd /tmp/autopkgtest.zLpGEQ/autopkgtest_tmp/
234s + py3versions -s
234s + echo --
234s + echo Testing with python3.12
234s + echo --
234s + PYTHONPATH=/usr/share/dh-debputy LC_ALL=C python3.12 -m pytest
234s /tmp/autopkgtest.zLpGEQ/build.xFL/src/debian/tests/debputy-py.test:
23: python3.12: not found
234s --
234s Testing with python3.12
234s --
--- End Message ---
--- Begin Message ---
Source: debputy
Source-Version: 0.1.8
Done: Niels Thykier
We believe that the bug you reported is fixed in the latest version of
debputy, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Niels Thykier (supplier of updated debputy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 19 Nov 2023 19:00:00 +0100
Source: debputy
Architecture: source
Version: 0.1.8
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers
Changed-By: Niels Thykier
Closes: 1056240
Changes:
debputy (0.1.8) unstable; urgency=medium
.
* Manifest changes:
- Breaking change: Rename some manifest variables like `{{TAB}}`
`{{token:TAB}}`. This change only affects manifest variables
intended to provide textual tokens that might be hard to write
literally or to avoid triggering substitution of another manifest
variable.
- Split `arch-matches` condition into three. The `arch-matches`
is still preferred. The other two variants are for special-cases
related to cross-building. As a side-effect of this change,
`arch-matches` can now be used in source context.
- Support manifest declared variables. A new `definitions.variables`
key is defined where variables can be declared. See
MANIFEST-FORMAT.md for the details. (Closes: debputy#58)
- It is now possible to use substitution variables in package names
in the manifest. This enables the use of `libfoo{{SONAME}}` instead
of hard-coding the value.
.
* Plugin changes:
- Breaking change: Remove the previously required plugin-version
attribute.
- Streamline installation process for "simple" `debputy` plugins by
providing a debhelper tool and by having `debputy` take
responsibility for the Python byte-compilation requirement for
`debputy` plugins. Additionally, support for running plugin tests
have been added too (both as build-time and as installed tests).
- Breaking (test-only) change: The test API for loading plugins have
been renamed and should no longer be passed a JSON descriptor file.
Instead, the test framework will attempt to find the JSON descriptor
file on its own. With this method, the test does not have to
distinguish between install-time and build-time test runs.
- A metadata detector can now request the binary
Processed: found 1056238 in 13.1.0-7
Processing commands for cont...@bugs.debian.org: > # > https://buildd.debian.org/status/fetch.php?pkg=gcc-13=mips64el=13.1.0-7=1688411201=0 > found 1056238 13.1.0-7 Bug #1056238 [src:gcc-13] gcc-13: FTBFS on mips64el: E: Build killed with signal TERM after 150 minutes of inactivity Marked as found in versions gcc-13/13.1.0-7. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1042693 marked as pending in python-django-celery-results
Processing control commands: > tag -1 pending Bug #1042693 [src:python-django-celery-results] python-django-celery-results: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2 Added tag(s) pending. -- 1042693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042693: marked as pending in python-django-celery-results
Control: tag -1 pending Hello, Bug #1042693 in python-django-celery-results reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-django-celery-results/-/commit/fe83675c2c4e9ffd1e8355d93ad50145ca0c80f6 Add patch to satisfy assinine sphinx 7.x parsing logic for copyright year substitution (Closes: #1042693). (this message was generated automatically) -- Greetings https://bugs.debian.org/1042693
Bug#1037192: sd: version is lower than in squeeze
On Mon, 23 Oct 2023 17:28:50 +0200 Orión González wrote: > A contributor suggested that 1.0 release should be on hold until some new > features get stabilized > https://github.com/chmln/sd/issues/203#issuecomment-1775390770 > > This might mean that the 1.0 release might take many more months. 1.0 has been released: https://github.com/chmln/sd/releases/tag/v1.0.0 I'm now preparing the update. -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: trac: FTBFS: ValueError: ("Missing 'Version:' header and/or PKG-INFO file at path: /<>/Trac.egg-info/PKG-INFO", Trac [unknown version] (/<>))
Processing control commands:
> severity -1 normal
Bug #1054730 [src:trac] trac: FTBFS: ValueError: ("Missing 'Version:' header
and/or PKG-INFO file at path: /<>/Trac.egg-info/PKG-INFO", Trac
[unknown version] (/<>))
Severity set to 'normal' from 'serious'
> tag -1 + moreinfo
Bug #1054730 [src:trac] trac: FTBFS: ValueError: ("Missing 'Version:' header
and/or PKG-INFO file at path: /<>/Trac.egg-info/PKG-INFO", Trac
[unknown version] (/<>))
Added tag(s) moreinfo.
--
1054730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1054730: trac: FTBFS: ValueError: ("Missing 'Version:' header and/or PKG-INFO file at path: /<>/Trac.egg-info/PKG-INFO", Trac [unknown version] (/<>))
Control: severity -1 normal Control: tag -1 + moreinfo Hi, I can't reproduce this FTBFS. Could you try again, please? I'll upload a new version, but it shouldn't make a difference.
Bug#1055922: rmatrix: ABI change in Matrix 1.6-2
Hi Graham,
On 19 November 2023 at 13:49, Graham Inggs wrote:
| On Tue, 14 Nov 2023 at 12:42, Dirk Eddelbuettel wrote:
| > Doesn't 'normal' do that?
|
| No, only serious and above are considered RC [1] and also for migration.
|
| This week, Paul Gevers and I spent some time discussing ways to move
| this transition forward.
|
| Referring back to some of your previous emails below.
|
| On Tue, 14 Nov 2023 at 12:01, Dirk Eddelbuettel wrote:
| > We need to address the packages needing a rebuild. Mine (r-cran-lme4,
| > r-cran-rcppeigen). have been taken care of.
|
| We see the upload of lme4 1.1-35.1-2 on 2023-11-14 [2], and the
| changelog mentions a rebuild, but the upload of r-cran-rcppeigen
| 0.3.3.9.4-1 on 2023-11-03 [3] happened before the upload of matrix
| 1.6-2-1. Does r-cran-rcppeigen still require a rebuild?
I am upstream for RcppEigen.
And the upstream NEWS has
\item The interface to package \pkg{Matrix} has been updated and
simplified thanks to an excllent patch by Mikael Jagan.
\item The new upload is coordinated with packages \pkg{lme4} and
\pkg{OpenMx}.
So it contains a patch by Mikael which had been applied _permitting Matrix
1.6-2_ to get to CRAN. So for this particular pair it was the other way around.
And I acted accordingly as Debian maintainer for a package for which I am
upstream.
| On Mon, 13 Nov 2023 at 12:23, Dirk Eddelbuettel wrote:
| > I would appreciate it if someone could tickle rebuilds. To me a quick
| > informal touch of debian/changelog would do; if someone thinks this needs a
| > formal transition go for it.
|
| We don't believe only touching debian/changelog, or a binNMU, is
| sufficient. We were surprised that your r-cran-lme4 upload did not at
| least include:
| Depends: r-cran-matrix (>= 1.6-2-1)
| Without that relationship, r-cran-lme4 could migrate to testing and be
| installed on users' systems without the corresponding version of
| r-cran-matrix. It is no surprise that the excuses page for lme4 [4]
| is all red, because that is exactly what is being tested. More on
| this to come in my next email.
I can add that, and probably should have. And I agree with the sentiment in
your other mail that a transition is overkill here.
Matrix has 1304 reverse dependencies at CRAN [1], Mikael (in the two emails
he wrote at my urging) identified 14 packages that needed a rebuild because
they use Matrix header files (R packages can build against headers in another
package, this is more specialised use), and another 3 that had cached S4 (the
more complicated OO model in R) function signature.
So 17 out of 1304 is not exactly a general breakage. I think I found 6 out of
the 17 as being in Debian. I had dealt with three myself and then sent email to
initiate
simple rebuilds. But that went nowhere.
So I leave this in your hands. If you think that after all this needs a
transtion, I may shrug but will of course help.
And please dDon't get wrong: I am considering this to be an open problem
upstream. The R Core team, the CRAN team, and others are discussing, but the
CRAN system does not quite have our mechanisms even to push binary
rebuilds. So this is an ongoing and open issue.
Dirk
[1] See the R snippet:
> db <- tools::CRAN_package_db()
> length(tools::package_dependencies("Matrix", reverse=TRUE, db=db)$Matrix)
[1] 1304
>
so 1304 are found right now at CRAN, and 17/1304 is about 1.3%. We seem
to have 6 identified out of about 138 (per apt-cache rdepends ...)
which is a little higher at 4.3% which is normal as 'heavier' packages
are more likely to be packaged. But net-net it is still only one out
over twenty packages around Matrix.
|
| Regards
| Graham
|
|
| [1] https://www.debian.org/Bugs/Developer#severities
| [2]
https://tracker.debian.org/news/1478501/accepted-lme4-11-351-2-source-into-unstable/
| [3]
https://tracker.debian.org/news/1475888/accepted-r-cran-rcppeigen-03394-1-source-into-unstable/
| [4] https://qa.debian.org/excuses.php?package=lme4
--
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1038111: marked as done (haproxy-log-analysis: current version not usable, new upstream release available)
Your message dated Sun, 19 Nov 2023 15:19:33 +
with message-id
and subject line Bug#1038111: fixed in haproxy-log-analysis 5.1.0-1
has caused the Debian Bug report #1038111,
regarding haproxy-log-analysis: current version not usable, new upstream
release available
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1038111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: haproxy-log-analysis
Version: 2.0~b0-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
directly after installation of haproxy-log-analysis the postinst script throws
errors:
Selecting previously unselected package python3-haproxy-log-analysis.
Preparing to unpack .../python3-haproxy-log-analysis_2.0~b0-4_all.deb ...
Unpacking python3-haproxy-log-analysis (2.0~b0-4) ...
Selecting previously unselected package haproxy-log-analysis.
Preparing to unpack .../haproxy-log-analysis_2.0~b0-4_all.deb ...
Unpacking haproxy-log-analysis (2.0~b0-4) ...
Setting up python3-pkg-resources (66.1.1-1) ...
Setting up python3-haproxy-log-analysis (2.0~b0-4) ...
/usr/lib/python3/dist-packages/haproxy/filters.py:122: SyntaxWarning: "is not"
with a literal. Did you mea
n "!="?
if start_value is not '':
/usr/lib/python3/dist-packages/haproxy/filters.py:125: SyntaxWarning: "is not"
with a literal. Did you mea
n "!="?
if delta_value is not '':
/usr/lib/python3/dist-packages/haproxy/filters.py:128: SyntaxWarning: "is not"
with a literal. Did you mea
n "!="?
if start_value is not '' and delta_value is not '':
/usr/lib/python3/dist-packages/haproxy/filters.py:128: SyntaxWarning: "is not"
with a literal. Did you mea
n "!="?
if start_value is not '' and delta_value is not '':
/usr/lib/python3/dist-packages/haproxy/filters.py:132: SyntaxWarning: "is" with
a literal. Did you mean "=
="?
if start_value is '':
Setting up haproxy-log-analysis (2.0~b0-4) ...
Also executing haproxy-log-analysis throws an error which makes it basically
unusable:
Traceback (most recent call last):
File "/usr/bin/haproxy_log_analysis", line 33, in
sys.exit(load_entry_point('haproxy-log-analysis==2.0b0', 'console_scripts',
'haproxy_log_analysis')())
File "/usr/lib/python3/dist-packages/haproxy/main.py", line 289, in
console_script
main(arguments)
File "/usr/lib/python3/dist-packages/haproxy/main.py", line 274, in main
for command in args['commands']:
TypeError: 'NoneType' object is not iterable
The currently in Debian available version of haproxy-log-analysis is 7 years
old. There have been several releases by upstream since then. The latest was
version 5.1.0 released on December 3rd, 2022.
Please update haproxy-log-analysis so that we have a working version in Debian
again.
Thank you and kind regards,
Daniel
-- System Information:
Versions of packages haproxy-log-analysis depends on:
ii python3 3.9.2-3
pn python3-haproxy-log-analysis
haproxy-log-analysis recommends no packages.
--- End Message ---
--- Begin Message ---
Source: haproxy-log-analysis
Source-Version: 5.1.0-1
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
haproxy-log-analysis, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1038...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated haproxy-log-analysis
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 19 Nov 2023 17:02:20 +0200
Source: haproxy-log-analysis
Architecture: source
Version: 5.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Stefano Rivera
Closes: 825599 1038111 1040286
Changes:
haproxy-log-analysis (5.1.0-1) unstable; urgency=medium
.
* Team upload.
.
[ Dale Richards ]
* New upstream version 5.1.0 (Closes: #1038111, #1040286).
* Review and update to Debian Policy version 4.6.2.
- Increase build verbosity.
* Run tests with pytest.
.
[ Stefano Rivera ]
*
Bug#1055922: rmatrix: ABI change in Matrix 1.6-2
Hi Andreas
On Sat, 18 Nov 2023 at 19:18, Andreas Tille wrote:
> We need some means to follow ABI changes. In Debian we could use
> something like r-matrix-abi-VERSION.
Indeed, this is one solution. As you saw in [1], upstream now provide
an ABI version and a way to extract it:
> Matrix will commence ABI versioning in 1.6-2. The ABI version will be
> available
> in R as Matrix.Version()[["abi"]] and in C as R_MATRIX_ABI_VERSION (from
> header
> Matrix/Matrix.h). It is numeric_version("1") in Matrix 1.6-2 and _implicitly_
> numeric_version("0") in Matrix < 1.6-2.
However, since rmatrix has over 100 reverse-dependencies, and only a
very small number of these are broken by the ABI change, we feel this
may be overkill, but wouldn't dissuade anyone from proposing patches
to implement this.
Another option is simply to add a versioned dependency on
r-cran-matrix to the affected packages, e.g.:
Depends: r-cran-matrix (>= 1.6-2-1)
...but this requires a source change and an upload, is error-prone,
and a binNMU would not be sufficient.
We liked the change you made to r-cran-tmb [2], as this allows the
affected packages to be binNMU'd and gain a versioned dependency on
r-cran-matrix. Would you please apply this to the other affected
packages (only r-cran-irlba and r-cran-openmx, if I understand
correctly)?
Unfortunately, it seems the two-sided dependency introduced
subsequently [3], which produces:
r-cran-matrix (>= 1.6-2-1), r-cran-matrix (<= 1.6-2-199)
...is too strict, and r-cran-tmb already needs another rebuild due to
the upload of rmatrix 1.6-3-1. Would you please revert that change
and upload?
Regards
Graham
[1] https://stat.ethz.ch/pipermail/r-sig-mac/2023-October/014890.html
[2]
https://salsa.debian.org/r-pkg-team/r-cran-tmb/-/commit/92579f72c2db4d51a45cf317f580d790da158f4f
[3]
https://salsa.debian.org/r-pkg-team/r-cran-tmb/-/commit/0a4d35d10f9c875863fa0238287cee8ab25aecdd
Bug#1055922: rmatrix: ABI change in Matrix 1.6-2
Hi Dirk On Tue, 14 Nov 2023 at 12:42, Dirk Eddelbuettel wrote: > Doesn't 'normal' do that? No, only serious and above are considered RC [1] and also for migration. This week, Paul Gevers and I spent some time discussing ways to move this transition forward. Referring back to some of your previous emails below. On Tue, 14 Nov 2023 at 12:01, Dirk Eddelbuettel wrote: > We need to address the packages needing a rebuild. Mine (r-cran-lme4, > r-cran-rcppeigen). have been taken care of. We see the upload of lme4 1.1-35.1-2 on 2023-11-14 [2], and the changelog mentions a rebuild, but the upload of r-cran-rcppeigen 0.3.3.9.4-1 on 2023-11-03 [3] happened before the upload of matrix 1.6-2-1. Does r-cran-rcppeigen still require a rebuild? On Mon, 13 Nov 2023 at 12:23, Dirk Eddelbuettel wrote: > I would appreciate it if someone could tickle rebuilds. To me a quick > informal touch of debian/changelog would do; if someone thinks this needs a > formal transition go for it. We don't believe only touching debian/changelog, or a binNMU, is sufficient. We were surprised that your r-cran-lme4 upload did not at least include: Depends: r-cran-matrix (>= 1.6-2-1) Without that relationship, r-cran-lme4 could migrate to testing and be installed on users' systems without the corresponding version of r-cran-matrix. It is no surprise that the excuses page for lme4 [4] is all red, because that is exactly what is being tested. More on this to come in my next email. Regards Graham [1] https://www.debian.org/Bugs/Developer#severities [2] https://tracker.debian.org/news/1478501/accepted-lme4-11-351-2-source-into-unstable/ [3] https://tracker.debian.org/news/1475888/accepted-r-cran-rcppeigen-03394-1-source-into-unstable/ [4] https://qa.debian.org/excuses.php?package=lme4
Processed: cloning 1053674, reassign -1 to src:g3dviewer, severity of -1 is serious
Processing commands for cont...@bugs.debian.org: > clone 1053674 -1 Bug #1053674 [ftp.debian.org] RM: g3dviewer -- ROM; abandoned upstream; depends on gtk2 Bug 1053674 cloned as bug 1056272 967358 was blocked by: 1053674 967358 was blocking: 947713 967491 Added blocking bug(s) of 967358: 1056272 > reassign -1 src:g3dviewer Bug #1056272 [ftp.debian.org] RM: g3dviewer -- ROM; abandoned upstream; depends on gtk2 Bug reassigned from package 'ftp.debian.org' to 'src:g3dviewer'. Ignoring request to alter found versions of bug #1056272 to the same values previously set Ignoring request to alter fixed versions of bug #1056272 to the same values previously set > severity -1 serious Bug #1056272 [src:g3dviewer] RM: g3dviewer -- ROM; abandoned upstream; depends on gtk2 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1053674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053674 1056272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056272 967358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 1050359, cloning 1050359, reassign -1 to src:gpr, severity of -1 is serious
Processing commands for cont...@bugs.debian.org: > affects 1050359 src:gpr Bug #1050359 [ftp.debian.org] RM: gpr -- RoQA; dead upstream; depends on gtk2 Added indication that 1050359 affects src:gpr > clone 1050359 -1 Bug #1050359 [ftp.debian.org] RM: gpr -- RoQA; dead upstream; depends on gtk2 Bug 1050359 cloned as bug 1056271 1053418 was blocked by: 1050359 1053418 was not blocking any bugs. Added blocking bug(s) of 1053418: 1056271 > reassign -1 src:gpr Bug #1056271 [ftp.debian.org] RM: gpr -- RoQA; dead upstream; depends on gtk2 Bug reassigned from package 'ftp.debian.org' to 'src:gpr'. Ignoring request to alter found versions of bug #1056271 to the same values previously set Ignoring request to alter fixed versions of bug #1056271 to the same values previously set > severity -1 serious Bug #1056271 [src:gpr] RM: gpr -- RoQA; dead upstream; depends on gtk2 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1050359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050359 1053418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053418 1056271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: cloning 1051070, reassign -1 to src:gtimer, severity of -1 is serious, affects 1051070
Processing commands for cont...@bugs.debian.org: > clone 1051070 -1 Bug #1051070 [ftp.debian.org] RM: gtimer -- RoQA; low popcon; depends on gtk2 Bug 1051070 cloned as bug 1056270 > reassign -1 src:gtimer Bug #1056270 [ftp.debian.org] RM: gtimer -- RoQA; low popcon; depends on gtk2 Bug reassigned from package 'ftp.debian.org' to 'src:gtimer'. Ignoring request to alter found versions of bug #1056270 to the same values previously set Ignoring request to alter fixed versions of bug #1056270 to the same values previously set > severity -1 serious Bug #1056270 [src:gtimer] RM: gtimer -- RoQA; low popcon; depends on gtk2 Severity set to 'serious' from 'normal' > affects 1051070 src:gtimer Bug #1051070 [ftp.debian.org] RM: gtimer -- RoQA; low popcon; depends on gtk2 Added indication that 1051070 affects src:gtimer > thanks Stopping processing here. Please contact me if you need assistance. -- 1051070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051070 1056270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042646: dh-virtualenv: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx'
Hello,
to make the package build in a buildd chroot some more adaptions are
needed:
- Depend on python3-docutils (which was pulled in before by
python3-sphinx)
- Drop debian/dh-virtualenv.doc-base as the documentation is missing
now
- Don't call dh with --with sphinxdoc
The complete deb diff now is:
dpkg-source: warning: extracting unsigned source package
(/home/uwe/debsrc/dh-virtualenv_1.2.2-1.4.dsc)
diff -Nru dh-virtualenv-1.2.2/debian/changelog
dh-virtualenv-1.2.2/debian/changelog
--- dh-virtualenv-1.2.2/debian/changelog2023-02-02 20:10:21.0
+0100
+++ dh-virtualenv-1.2.2/debian/changelog2023-11-17 19:40:18.0
+0100
@@ -1,3 +1,10 @@
+dh-virtualenv (1.2.2-1.4) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop Sphinx docs (Closes: #1042646)
+
+ -- Uwe Kleine-König Fri, 17 Nov 2023 19:40:18 +0100
+
dh-virtualenv (1.2.2-1.3) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru dh-virtualenv-1.2.2/debian/control dh-virtualenv-1.2.2/debian/control
--- dh-virtualenv-1.2.2/debian/control 2022-08-25 21:00:57.0 +0200
+++ dh-virtualenv-1.2.2/debian/control 2023-11-17 19:40:18.0 +0100
@@ -2,26 +2,24 @@
Section: python
Priority: optional
Maintainer: Jyrki Pulliainen
-Build-Depends: debhelper-compat (= 12), python3,
- python3-setuptools, python3-sphinx, python3-mock, dh-exec,
- dh-python, libjs-jquery, libjs-underscore,
-# python-sphinx-rtd-theme doesn't exist in distributions
-# predating Debian Jessie and Ubuntu Xenial. On these legacy
-# systems:
-# 1. Comment the dependency below.
-# 2. pip install sphinx_rtd_theme.
-# 3. Proceed with your build process (typically dpkg-build).
-# See https://github.com/spotify/dh-virtualenv/issues/230
- python3-sphinx-rtd-theme
+Build-Depends:
+ debhelper-compat (= 12),
+ python3,
+ python3-docutils,
+ python3-setuptools,
+ python3-mock,
+ dh-exec,
+ dh-python,
+ libjs-jquery,
+ libjs-underscore,
Standards-Version: 4.5.0
Homepage: https://www.github.com/spotify/dh-virtualenv
Rules-Requires-Root: no
Package: dh-virtualenv
Architecture: all
-Depends: ${python3:Depends}, ${perl:Depends}, ${misc:Depends},
${sphinxdoc:Depends},
+Depends: ${python3:Depends}, ${perl:Depends}, ${misc:Depends},
virtualenv | python3-virtualenv (>= 1.7) | python${pyversion}-venv
-Built-Using: ${sphinxdoc:Built-Using}
Description: wrap and build Python packages using virtualenv
This package provides a dh sequencer that helps you to deploy your
virtualenv wrapped installation inside a Debian package.
diff -Nru dh-virtualenv-1.2.2/debian/dh-virtualenv.doc-base
dh-virtualenv-1.2.2/debian/dh-virtualenv.doc-base
--- dh-virtualenv-1.2.2/debian/dh-virtualenv.doc-base 2022-08-25
21:00:57.0 +0200
+++ dh-virtualenv-1.2.2/debian/dh-virtualenv.doc-base 1970-01-01
01:00:00.0 +0100
@@ -1,9 +0,0 @@
-Document: dh-virtualenv
-Title: dh-virtualenv documentation
-Author: Spotify
-Abstract: This manual describes dh-virtualenv and how to use it.
-Section: Programming
-
-Format: HTML
-Index: /usr/share/doc/dh-virtualenv/html/index.html
-Files: /usr/share/doc/dh-virtualenv/html/*.html
diff -Nru dh-virtualenv-1.2.2/debian/rules dh-virtualenv-1.2.2/debian/rules
--- dh-virtualenv-1.2.2/debian/rules2022-08-25 21:00:57.0 +0200
+++ dh-virtualenv-1.2.2/debian/rules2023-11-17 19:40:18.0 +0100
@@ -1,9 +1,6 @@
#!/usr/bin/make -f
DH_ARGS ?=
-ifeq (,$(findstring nodoc, $(DEB_BUILD_OPTIONS)))
- DH_ARGS += --with sphinxdoc
-endif
PYTHON_VERSION := $(shell python3 -c 'import sys; print("%s.%s" %
sys.version_info[:2])')
@@ -22,9 +19,3 @@
override_dh_gencontrol:
dh_gencontrol -- -Vpyversion=$(PYTHON_VERSION)
-
-ifeq (,$(findstring nodoc, $(DEB_BUILD_OPTIONS)))
-override_dh_installdocs:
- python3 setup.py build_sphinx
- dh_installdocs doc/_build/html
-endif
I'll upload that to DELAYED/7 after sending this mail.
Best regards
Uwe
signature.asc
Description: PGP signature
Bug#1056253: rust-ripasso-cursive - FTBFS with rust-ripasso 0.6.4
On 19/11/2023 12:14, Peter Michael Green wrote: Package: rust-ripasso-cursive Version: 0.6.1-1 Severity: serious Tags: trixie, sid It appears, that despite the version number indicating a compatible release, that the new version of ripasso broke the build of ripasso-cursive. https://tests.reproducible-builds.org/debian/rb-pkg/trixie/amd64/rust-ripasso-cursive.html error[E0425]: cannot find function `push` in module `pass` --> src/main.rs:941:29 | 941 | let push_result = pass::push(().unwrap().lock().unwrap()); | not found in `pass` | help: consider importing this function | 18 + use ripasso::git::push; | help: if you import `push`, refer to it directly | 941 - let push_result = pass::push(().unwrap().lock().unwrap()); 941 + let push_result = push(().unwrap().lock().unwrap()); | error[E0425]: cannot find function `pull` in module `pass` --> src/main.rs:953:19 | 953 | let _ = pass::pull(().unwrap().lock().unwrap()) | not found in `pass` | help: consider importing this function | 18 + use ripasso::git::pull; | help: if you import `pull`, refer to it directly | 953 - let _ = pass::pull(().unwrap().lock().unwrap()) 953 + let _ = pull(().unwrap().lock().unwrap()) | error[E0603]: function `init_git_repo` is private --> src/wizard.rs:32:26 | 32 | let init_res = pass::init_git_repo(::password_dir(password_store_dir, home).unwrap()); | ^ private function | note: the function `init_git_repo` is defined here --> /usr/share/cargo/registry/ripasso-0.6.4/src/pass.rs:34:60 | 34 | add_and_commit_internal, commit, find_last_commit, init_git_repo, match_with_parent, |^ I tried to update ripasso-cursive to 0.6.4 to match ripasso but I got. Applying patch unbreak-new-user-wizard.patch patching file src/main.rs Hunk #1 succeeded at with fuzz 1 (offset -58 lines). Hunk #2 FAILED at 1189. Hunk #3 succeeded at 1324 with fuzz 1 (offset 109 lines). Hunk #4 FAILED at 1773. Hunk #5 FAILED at 1789. Hunk #6 FAILED at 1798. Hunk #7 succeeded at 1849 with fuzz 2 (offset 43 lines). 4 out of 7 hunks FAILED -- rejects in file src/main.rs Patch unbreak-new-user-wizard.patch does not apply (enforce with -f) Can someone confirm whether this patch is still needed, and if-so update it for the new upstream version? For what it's worth I was able to get a succesful build by. 1. Upgrading ripasso-cursive to 0.6.3 (0.6.4 has a new dependency that is not in Debian) 2. Disabling unbreak-new-user-wizard.patch and translation-locations.patch I would still like feedback from Alexander on whether those patches are still relavent.
Processed: affects 1051243
Processing commands for cont...@bugs.debian.org: > affects 1051243 src:postgis Bug #1051243 [tex-common] tex-common: fmtutil failed on tex-common upgrade Added indication that 1051243 affects src:postgis > thanks Stopping processing here. Please contact me if you need assistance. -- 1051243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056253: rust-ripasso-cursive - FTBFS with rust-ripasso 0.6.4
Package: rust-ripasso-cursive Version: 0.6.1-1 Severity: serious Tags: trixie, sid It appears, that despite the version number indicating a compatible release, that the new version of ripasso broke the build of ripasso-cursive. https://tests.reproducible-builds.org/debian/rb-pkg/trixie/amd64/rust-ripasso-cursive.html error[E0425]: cannot find function `push` in module `pass` --> src/main.rs:941:29 | 941 | let push_result = pass::push(().unwrap().lock().unwrap()); | not found in `pass` | help: consider importing this function | 18 + use ripasso::git::push; | help: if you import `push`, refer to it directly | 941 - let push_result = pass::push(().unwrap().lock().unwrap()); 941 + let push_result = push(().unwrap().lock().unwrap()); | error[E0425]: cannot find function `pull` in module `pass` --> src/main.rs:953:19 | 953 | let _ = pass::pull(().unwrap().lock().unwrap()) | not found in `pass` | help: consider importing this function | 18 + use ripasso::git::pull; | help: if you import `pull`, refer to it directly | 953 - let _ = pass::pull(().unwrap().lock().unwrap()) 953 + let _ = pull(().unwrap().lock().unwrap()) | error[E0603]: function `init_git_repo` is private --> src/wizard.rs:32:26 | 32 | let init_res = pass::init_git_repo(::password_dir(password_store_dir, home).unwrap()); | ^ private function | note: the function `init_git_repo` is defined here --> /usr/share/cargo/registry/ripasso-0.6.4/src/pass.rs:34:60 | 34 | add_and_commit_internal, commit, find_last_commit, init_git_repo, match_with_parent, |^ I tried to update ripasso-cursive to 0.6.4 to match ripasso but I got. Applying patch unbreak-new-user-wizard.patch patching file src/main.rs Hunk #1 succeeded at with fuzz 1 (offset -58 lines). Hunk #2 FAILED at 1189. Hunk #3 succeeded at 1324 with fuzz 1 (offset 109 lines). Hunk #4 FAILED at 1773. Hunk #5 FAILED at 1789. Hunk #6 FAILED at 1798. Hunk #7 succeeded at 1849 with fuzz 2 (offset 43 lines). 4 out of 7 hunks FAILED -- rejects in file src/main.rs Patch unbreak-new-user-wizard.patch does not apply (enforce with -f) Can someone confirm whether this patch is still needed, and if-so update it for the new upstream version?
Bug#1056240: debputy-py.test calls py3versions -s without depending on python3-all
Package: src:debputy Version: 0.1.7.8 Severity: serious Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 debputy-py.test calls py3versions -s without depending on python3-all. [...] 234s autopkgtest [18:22:37]: test debputy-py.test: [--- 234s + mkdir /tmp/autopkgtest.zLpGEQ/autopkgtest_tmp/debian 234s + cp -r pyproject.toml tests/ /tmp/autopkgtest.zLpGEQ/autopkgtest_tmp 234s + cp -a debian/control /tmp/autopkgtest.zLpGEQ/autopkgtest_tmp/debian 234s + export PYTHONWARNINGS=d 234s + DEBPUTY_PYTHONPATH=/usr/share/dh-debputy 234s + PYTHOHPATH= 234s + [ ] 234s + PYTHOHPATH=/usr/share/dh-debputy 234s + cd /tmp/autopkgtest.zLpGEQ/autopkgtest_tmp/ 234s + py3versions -s 234s + echo -- 234s + echo Testing with python3.12 234s + echo -- 234s + PYTHONPATH=/usr/share/dh-debputy LC_ALL=C python3.12 -m pytest 234s /tmp/autopkgtest.zLpGEQ/build.xFL/src/debian/tests/debputy-py.test: 23: python3.12: not found 234s -- 234s Testing with python3.12 234s --
Bug#1055952: marked as done (vlc: upgrade to libva 7:6.1-2)
Your message dated Sun, 19 Nov 2023 10:19:49 + with message-id and subject line Bug#1055952: fixed in ffmpeg 7:6.1-3 has caused the Debian Bug report #1055952, regarding vlc: upgrade to libva 7:6.1-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1055952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vlc Version: 3.0.20-1+b1 Severity: normal As result vlc crashed on video play. Downgrade libva to 7:6.0-9+b1 solves this problem. Please update vlc for the new libva version. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vlc depends on: ii vlc-bin 3.0.20-1+b1 ii vlc-plugin-base 3.0.20-1+b1 ii vlc-plugin-qt3.0.20-1+b1 ii vlc-plugin-video-output 3.0.20-1+b1 Versions of packages vlc recommends: ii vlc-l10n 3.0.20-1 ii vlc-plugin-access-extra3.0.20-1+b1 ii vlc-plugin-notify 3.0.20-1+b1 ii vlc-plugin-samba 3.0.20-1+b1 ii vlc-plugin-skins2 3.0.20-1+b1 ii vlc-plugin-video-splitter 3.0.20-1+b1 ii vlc-plugin-visualization 3.0.20-1+b1 Versions of packages vlc suggests: ii vlc-plugin-fluidsynth 3.0.20-1+b1 ii vlc-plugin-jack3.0.20-1+b1 ii vlc-plugin-pipewire3-2 ii vlc-plugin-svg 3.0.20-1+b1 Versions of packages libvlc-bin depends on: ii libc62.37-12 ii libvlc5 3.0.20-1+b1 Versions of packages libvlc5 depends on: ii libc62.37-12 ii libvlccore9 3.0.20-1+b1 Versions of packages libvlc5 recommends: ii libvlc-bin 3.0.20-1+b1 Versions of packages libvlccore8 depends on: ii libc62.37-12 ii libdbus-1-3 1.14.10-3 ii libidn11 1.33-3 Versions of packages libvlccore8 recommends: ii libproxy-tools 0.4.18-1.2 Versions of packages vlc-bin depends on: ii libc6 2.37-12 ii libvlc-bin 3.0.20-1+b1 ii libvlc5 3.0.20-1+b1 Versions of packages vlc-plugin-access-extra depends on: ii libc62.37-12 ii libsrt1.5-gnutls 1.5.3-1 ii libvlccore9 [vlc-plugin-abi-3-0-0f] 3.0.20-1+b1 ii libvncclient10.9.14+dfsg-1 ii libxcb-composite01.15-1 ii libxcb-shm0 1.15-1 ii libxcb1 1.15-1 Versions of packages vlc-plugin-base depends on: ii liba52-0.7.4 0.7.4-20 ii libarchive13 3.7.2-1 ii libaribb24-0 1.0.3-2 ii libasound2 1.2.10-1 ii libass9 1:0.17.1-1 ii libavahi-client3 0.8-13 ii libavahi-common3 0.8-13 ii libavc1394-0 0.5.4-5 ii libavcodec60 7:6.0-9+b1 ii libavformat607:6.0-9+b1 ii libavutil58 7:6.0-9+b1 ii libbluray2 1:1.3.4-1 ii libc62.37-12 ii libcairo21.18.0-1 ii libcddb2 1.3.2-7 ii libchromaprint1 1.5.1-4 ii libdav1d71.3.0-2 ii libdbus-1-3 1.14.10-3 ii libdc1394-25 2.2.6-4 ii libdca0 0.0.7-2 ii libdvbpsi10 1.3.3-1 ii libdvdnav4 6.1.1-1 ii libdvdread8 6.1.3-1 ii libebml5 1.4.4-1 ii libfaad2 2.11.1-1 ii libflac121.4.3+ds-2 ii libfontconfig1 2.14.2-6 ii libfreetype6 2.13.2+dfsg-1 ii libfribidi0 1.0.13-3 ii libgcc-s113.2.0-6 ii libgcrypt20 1.10.2-3 ii libglib2.0-0 2.78.1-4 ii
Bug#1056238: gcc-13: FTBFS on mips64el: E: Build killed with signal TERM after 150 minutes of inactivity
Source: gcc-13 Version: 13.2.0-6 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=gcc-13=mips64el=13.2.0-6=1700351970=0 === libstdc++ Summary for unix === # of expected passes3886 # of expected failures 43 # of unsupported tests 139 Running target unix/-fstack-protector Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /<>/src/libstdc++-v3/testsuite/config/default.exp as tool-and-target-specific interface file. Running /<>/src/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ... Running /<>/src/libstdc++-v3/testsuite/libstdc++-prettyprinters/prettyprinters.exp ... FAIL: libstdc++-abi/abi_check Running /<>/src/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ... Running /<>/src/libstdc++-v3/testsuite/libstdc++-xmethods/xmethods.exp ... === libstdc++ Summary for unix === # of expected passes158 # of unexpected failures1 # of unresolved testcases 1 Running target unix/-fstack-protector Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /<>/src/libstdc++-v3/testsuite/config/default.exp as tool-and-target-specific interface file. Running /<>/src/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ... Running /<>/src/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ... Running /<>/src/libstdc++-v3/testsuite/libstdc++-prettyprinters/prettyprinters.exp ... Running /<>/src/libstdc++-v3/testsuite/libstdc++-xmethods/xmethods.exp ... === libstdc++ Summary for unix === # of expected passes3689 # of unexpected failures1 # of expected failures 37 # of unsupported tests 186 Running target unix/-fstack-protector Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /<>/src/libstdc++-v3/testsuite/config/default.exp as tool-and-target-specific interface file. Running /<>/src/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ... Running /<>/src/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ... testsuite still running ... E: Build killed with signal TERM after 150 minutes of inactivity Cheers -- Sebastian Ramacher
Processed: Re: midge possibly contains non-DFSG-free examples
Processing control commands: > tag -1 patch Bug #1056147 [src:midge] midge possibly contains non-DFSG-free examples Added tag(s) patch. -- 1056147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056147: midge possibly contains non-DFSG-free examples
Control: tag -1 patch I have now uploaded a possible repackaged .orig.tar.bz2: http://users.am-1.org/~ivan/src/sfn.2xNKGoveuNoRGASEQosuADUES3vYQfQmWVeMuitdtLI.tar.bz2 It was produced with the following shell command (where 39 blocks starting with 180 cover the entirety of midge-0.2.41 /examples/covers/ directory in the Tar file.) $ (zcat | (dd count=180 ; dd count=39 > /dev/null ; dd) | bzip2 -4c) \ < midge_0.2.41.orig.tar.gz > midge_0.2.41+dfsg1.orig.tar.bz2 -- FSF associate member #7257 http://am-1.org/~ivan/
Bug#1042591: marked as done (pg8000: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')
Your message dated Sun, 19 Nov 2023 09:34:07 + with message-id and subject line Bug#1042591: fixed in pg8000 1.30.3-1 has caused the Debian Bug report #1042591, regarding pg8000: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pg8000 Version: 1.10.6-3 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, pg8000 fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > python3 setup.py build_sphinx > /usr/lib/python3/dist-packages/setuptools/dist.py:745: > SetuptoolsDeprecationWarning: Invalid dash-separated options > !! > > > > Usage of dash-separated 'upload-dir' will not be supported in future > versions. Please use the underscore name 'upload_dir' instead. > > By 2023-Sep-26, you need to update your project and remove deprecated > calls > or your builds will no longer be supported. > > See > https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for > details. > > > > !! > opt = self.warn_dash_deprecation(opt, section) > usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] >or: setup.py --help [cmd1 cmd2 ...] >or: setup.py --help-commands >or: setup.py cmd --help > > error: invalid command 'build_sphinx' > make[1]: *** [debian/rules:13: override_dh_installdocs] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/30/exp/pg8000_1.10.6-3_unstable_sphinx-exp.log Please see [1] for Sphinx changelog and [2] for Docutils changelog. Also see [3] for the list of deprecated/removed APIs in Sphinx and possible alternatives to them. Some notable changes in Sphinx 6 and Sphinx 7: - Sphinx no longer includes jquery.js and underscore.js by default. Please use python3-sphinxcontrib.jquery package if you are using a custom template and it still needs jquery. - The setup.py build_sphinx command was removed. Please instead call sphinx-build or "python3 -m sphinx" directly. - For packages using the extlinks extension, the caption should contain exactly one "%s" placeholder (if caption is not None). In case you have questions, please Cc sph...@packages.debian.org on reply. [1]: https://www.sphinx-doc.org/en/master/changes.html [2]: https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt [3]: https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx7.1=python-modules-t...@lists.alioth.debian.org=1=1=1=1#results If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects --- End Message --- --- Begin Message --- Source: pg8000 Source-Version: 1.30.3-1 Done: Alexander Sulfrian We believe that the bug you reported is fixed in the latest version of pg8000, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexander Sulfrian (supplier of updated pg8000 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 19 Nov 2023 09:02:22 + Source: pg8000 Built-For-Profiles: noudeb Architecture: source Version: 1.30.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Alexander Sulfrian Closes: 858485 910580 986223 1042591 Changes: pg8000 (1.30.3-1) unstable; urgency=medium . * New
Processed (with 1 error): (No Subject)
Processing commands for cont...@bugs.debian.org: > forcemerge 1038111 1040286 Bug #1038111 [haproxy-log-analysis] haproxy-log-analysis: current version not usable, new upstream release available Unable to merge bugs because: package of #1040286 is 'python3-haproxy-log-analysis' not 'haproxy-log-analysis' Failed to forcibly merge 1038111: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1038111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038111 1040286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038111: haproxy-log-analysis: current version not usable, new upstream release available
Hi, I'm not a member of the DPT, but I've created a merge request in the package repository for updating this package to upstream 5.1.0: https://salsa.debian.org/python-team/packages/haproxy-log-analysis/-/merge_requests/2 I hope this is of some use in getting this resolved. Best regards, Dale Richards
Processed: src:deb-gview: fails to migrate to testing for too long: autopkgtest failure
Processing control commands: > close -1 0.3.5 Bug #1056218 [src:deb-gview] src:deb-gview: fails to migrate to testing for too long: autopkgtest failure Marked as fixed in versions deb-gview/0.3.5. Bug #1056218 [src:deb-gview] src:deb-gview: fails to migrate to testing for too long: autopkgtest failure Marked Bug as done -- 1056218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056218: src:deb-gview: fails to migrate to testing for too long: autopkgtest failure
Source: deb-gview Version: 0.3.3 Severity: serious Control: close -1 0.3.5 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:deb-gview has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable has a (new, thanks, that's great) autopkgtest that fails. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=deb-gview OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#1056210: luatex panics with zlib 1.3
Processing control commands: > block -1 by 1056204 Bug #1056210 [texlive-binaries] luatex panics with zlib 1.3 1056210 was not blocked by any bugs. 1056210 was not blocking any bugs. Added blocking bug(s) of 1056210: 1056204 > merge -1 1056183 Bug #1056210 [texlive-binaries] luatex panics with zlib 1.3 Bug #1056183 [texlive-binaries] texlive-luatex: lualatex exits immediately due to new zlib Bug #1056186 [texlive-binaries] texlive-binaries: zlib library mismatch Bug #1056189 [texlive-binaries] luahbtex: PANIC: unprotected error in call to Lua API (zlib library version does not match - header: 1.2.13, library: 1.3) Merged 1056183 1056186 1056189 1056210 -- 1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183 1056186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056186 1056189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056189 1056210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056210: luatex panics with zlib 1.3
Control: block -1 by 1056204 Control: merge -1 1056183 signature.asc Description: PGP signature
Bug#1056217: src:rust-async-task: fails to migrate to testing for too long: autopkgtest regression
Source: rust-async-task Version: 4.4.1-1 Severity: serious Control: close -1 4.5.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1055099 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:rust-async-task has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable fails its autopkgtest as reported in bug 1055099. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=rust-async-task OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:rust-async-task: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 4.5.0-1
Bug #1056217 [src:rust-async-task] src:rust-async-task: fails to migrate to
testing for too long: autopkgtest regression
Marked as fixed in versions rust-async-task/4.5.0-1.
Bug #1056217 [src:rust-async-task] src:rust-async-task: fails to migrate to
testing for too long: autopkgtest regression
Marked Bug as done
> block -1 by 1055099
Bug #1056217 {Done: Paul Gevers } [src:rust-async-task]
src:rust-async-task: fails to migrate to testing for too long: autopkgtest
regression
1056217 was not blocked by any bugs.
1056217 was not blocking any bugs.
Added blocking bug(s) of 1056217: 1055099
--
1056217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#1056210: luatex panics with zlib 1.3
Processing control commands: > severity -1 grave Bug #1056210 [texlive-binaries] luatex panics with zlib 1.3 Severity set to 'grave' from 'normal' > merge -1 1056183 Bug #1056210 [texlive-binaries] luatex panics with zlib 1.3 Unable to merge bugs because: blockedby of #1056183 is '1056204' not '' blockedby of #1056189 is '1056204' not '' blockedby of #1056186 is '1056204' not '' Failed to merge 1056210: Did not alter merged bugs. -- 1056183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056183 1056186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056186 1056189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056189 1056210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
