Processed: severity of 1071977 is normal
Processing commands for cont...@bugs.debian.org: > severity 1071977 normal Bug #1071977 [tmux] tmux: /lib/x86_64-linux-gnu/libtinfo.so.6: version `NCURSES6_TINFO_6.4.current' 404 Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1071977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1071977: tmux: /lib/x86_64-linux-gnu/libtinfo.so.6: version `NCURSES6_TINFO_6.4.current' 404
Downgrading this bug while we wait for more information for the submitter. -- Romain Francoise https://people.debian.org/~rfrancoise/
Bug#1072555: elpa-rust-mode: This is an obsolete snapshot of the packaging
Package: elpa-rust-mode Version: 1.0.5+git20240301.6d86af4-1 Severity: serious Dear Maintainer, This is a placeholder bug for the current version in unstable, which is now being obsoleted by a newer snapshot prepared on mentors[1]. [1] https://mentors.debian.net/package/elpa-rust-mode/ -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-21-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 elpa-rust-mode depends on: ii dh-elpa-helper 2.1.2~bpo12+0manphiz1 ii emacsen-common 3.0.5 Versions of packages elpa-rust-mode recommends: ii emacs 1:29.3+1-3~bpo12+1 ii emacs-gtk [emacs] 1:29.3+1-3~bpo12+1 elpa-rust-mode suggests no packages. -- no debconf information
Bug#1072549: gl4es: Broken autopkgtest: unconditionally depends on gcc-multilib
Hi, Thanks for reporting it. On Tue, Jun 4, 2024 at 9:48 AM Boyuan Yang wrote: > > Source: gl4es > Version: 1.1.6+ds-1 > Severity: grave > X-Debbugs-CC: tsu.y...@gmail.com ship...@gmail.com > > Dear Debian gl4es package maintainers, > > As currently shown on the package tracker > https://tracker.debian.org/pkg/gl4es , > package gl4es is experiencing autopkgtest failures on some architectures. > Looking > deeper, it seems that gl4es unconditionally depends on binary package > gcc-multilib, > which is not available on certain architectures. > > I am not sure why we need gcc-multilib in autopkgtest tests. Please adjust the > source code accordingly, possibly following one of the following options: > > * Limit autopkgtest architectures and only run it where gcc-multilib is > available. > * Rework on autopkgtest script so that gcc-multilib is not needed, and only > depends on > the native gcc tools. > * If gl4es only supports a limited set of architectures, please consider > limiting the > supported hardware architecture in debian/control file. Personally I would like to improve it based on option 2 andI will fix it in the next days. Thanks again for your reminder.:) BR, Bo > > I have zero knowledge on how gl4es works, so I cannot recommend a best option > for you. > Please take a look and solve this issue properly. > > Thanks, > Boyuan Yang
Bug#1072549: gl4es: Broken autopkgtest: unconditionally depends on gcc-multilib
Source: gl4es Version: 1.1.6+ds-1 Severity: grave X-Debbugs-CC: tsu.y...@gmail.com ship...@gmail.com Dear Debian gl4es package maintainers, As currently shown on the package tracker https://tracker.debian.org/pkg/gl4es , package gl4es is experiencing autopkgtest failures on some architectures. Looking deeper, it seems that gl4es unconditionally depends on binary package gcc-multilib, which is not available on certain architectures. I am not sure why we need gcc-multilib in autopkgtest tests. Please adjust the source code accordingly, possibly following one of the following options: * Limit autopkgtest architectures and only run it where gcc-multilib is available. * Rework on autopkgtest script so that gcc-multilib is not needed, and only depends on the native gcc tools. * If gl4es only supports a limited set of architectures, please consider limiting the supported hardware architecture in debian/control file. I have zero knowledge on how gl4es works, so I cannot recommend a best option for you. Please take a look and solve this issue properly. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Processed: tagging 1063735
Processing commands for cont...@bugs.debian.org: > tags 1063735 + ftbfs Bug #1063735 [python-maturin] python-maturin - upcoming rust-indexmap update. Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1063735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000118: marked as done (generator-scripting-language: depends on obsolete pcre3 library)
Your message dated Mon, 03 Jun 2024 22:20:18 + with message-id and subject line Bug#1000118: fixed in generator-scripting-language 4.1.5-4 has caused the Debian Bug report #1000118, regarding generator-scripting-language: depends on obsolete pcre3 library 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.) -- 1000118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: generator-scripting-language Severity: important User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian --- End Message --- --- Begin Message --- Source: generator-scripting-language Source-Version: 4.1.5-4 Done: Luca Boccassi We believe that the bug you reported is fixed in the latest version of generator-scripting-language, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Boccassi (supplier of updated generator-scripting-language 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: Mon, 03 Jun 2024 22:53:57 +0100 Source: generator-scripting-language Architecture: source Version: 4.1.5-4 Distribution: unstable Urgency: medium Maintainer: Luca Boccassi Changed-By: Luca Boccassi Closes: 1000118 1051448 Changes: generator-scripting-language (4.1.5-4) unstable; urgency=medium . * Merge pull request #1 from debian-janitor/lintian-fixes * Backport patch to fix Loongarch64 build (Closes: #1051448) * Set Rules-Requires-Root: no * Bump debhelper-compat to 13 * Bump Standards-version to 4.7.0 * Vendor pcre3 * debian/pcre3: remove unneeded files * Build using the vendored static libpcre.a (Closes: #1000118) Checksums-Sha1: 204c48a97d96a1ccc93ff09e053783027a1f96aa 2120 generator-scripting-language_4.1.5-4.dsc cdcd4f928e28ed3538bb639f71010c26a54bab9c 255380 generator-scripting-language_4.1.5-4.debian.tar.xz 1076cf4604c169ac276fcbaa315b93b390950d05 7373 generator-scripting-language_4.1.5-4_source.buildinfo Checksums-Sha256: 8f7d6f52274d033be3e0808a0f85d813a2b1ce38620fce53199a0a957b0e8445 2120 generator-scripting-language_4.1.5-4.dsc efa812a138c9e883bc16c1a5c0704b20af7cbcd23ec40d457e0865e07fe22919 255380 generator-scripting-language_4.1.5-4.debian.tar.xz 68d329652b84c0329a4115fee53b77f4db3803a45269ba0ae59d80e7c5c1eaa5 7373 generator-scripting-language_4.1.5-4_source.buildinfo Files: 82dbb1d8ab4697aee1d409bc7b1af59f 2120 devel optional generator-scripting-language_4.1.5-4.dsc faf85546b3d9b2263e29b92e10ab451e 255380 devel optional generator-scripting-language_4.1.5-4.debian.tar.xz 53a27ed979ee914c69a73554af8ec9ef 7373 devel optional generator-scripting-language_4.1.5-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmZePKURHGJsdWNhQGRl Ymlhbi5vcmcACgkQKGv37813JB4LEg//QQ2FkjSnoup3W8TikVAYL1kHs0jTAPFh q0a2oMU/0bFcz2cAgy1/SsH2FEuDLLMWS3tzpSdvpcvH2mA+2AOmw2I3EP3BJhid XRQvmLsxZSKhIRudizvEj+yHWKIUi3wkXPWb+E37tNTuD6SmDV0YloZndPUPeYAU dlJlhGrwMV5YXS4bo2bVi7KNmAU43kBZwkvMjghtorgSGRoFNaVMirbtAt06caiy yhtSEWbGJto+Dvbs4MHhUmdZxtg9Wo43p1KxR2nbMyxZclufqLnSYs61lkQZEsB+
Processed: python-cooler: FTBFS due to TypeError in dask.dataframe import
Processing control commands: > tags -1 + confirmed Bug #1069359 [src:python-cooler] python-cooler: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpi8kk3ih0/tmp_sf3nv42.multi.cool' Added tag(s) confirmed. > block -1 by 1068422 Bug #1069359 [src:python-cooler] python-cooler: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpi8kk3ih0/tmp_sf3nv42.multi.cool' 1069359 was not blocked by any bugs. 1069359 was not blocking any bugs. Added blocking bug(s) of 1069359: 1068422 > retitle -1 python-cooler: FTBFS due to TypeError in dask.dataframe import Bug #1069359 [src:python-cooler] python-cooler: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpi8kk3ih0/tmp_sf3nv42.multi.cool' Changed Bug title to 'python-cooler: FTBFS due to TypeError in dask.dataframe import' from 'python-cooler: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpi8kk3ih0/tmp_sf3nv42.multi.cool''. -- 1069359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069359: python-cooler: FTBFS due to TypeError in dask.dataframe import
Control: tags -1 + confirmed Control: block -1 by 1068422 Control: retitle -1 python-cooler: FTBFS due to TypeError in dask.dataframe import Hi, After some investigations, it seems that #1069359 affecting python-cooler is actually a manifestation of #1068422 affecting dask, more precisely all attempts to load dataframe. I adjust the bug metadata to reflect that. The relevant call trace looks like: tests/test_create.py:24: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib/python3/dist-packages/dask/dataframe/__init__.py:98: in from dask.dataframe import backends, dispatch, rolling /usr/lib/python3/dist-packages/dask/dataframe/backends.py:15: in from dask.dataframe.core import DataFrame, Index, Scalar, Series, _Frame /usr/lib/python3/dist-packages/dask/dataframe/core.py:36: in from dask.dataframe import methods /usr/lib/python3/dist-packages/dask/dataframe/methods.py:34: in from dask.dataframe.utils import is_dataframe_like, is_index_like, is_series_like /usr/lib/python3/dist-packages/dask/dataframe/utils.py:20: in from dask.dataframe import ( # noqa: F401 register pandas extension types /usr/lib/python3/dist-packages/dask/dataframe/_dtypes.py:9: in from dask.dataframe.extensions import make_array_nonempty, make_scalar /usr/lib/python3/dist-packages/dask/dataframe/extensions.py:8: in from dask.dataframe.accessor import ( /usr/lib/python3/dist-packages/dask/dataframe/accessor.py:126: in class DatetimeAccessor(Accessor): /usr/lib/python3/dist-packages/dask/dataframe/accessor.py:81: in __init_subclass__ _bind_property(cls, pd_cls, attr, min_version) /usr/lib/python3/dist-packages/dask/dataframe/accessor.py:35: in _bind_property setattr(cls, attr, property(derived_from(pd_cls, version=min_version)(func))) /usr/lib/python3/dist-packages/dask/utils.py:983: in wrapper method.__doc__ = _derived_from( /usr/lib/python3/dist-packages/dask/utils.py:936: in _derived_from method_args = get_named_args(method) /usr/lib/python3/dist-packages/dask/utils.py:697: in get_named_args s = inspect.signature(func) /usr/lib/python3.12/inspect.py:3310: in signature return Signature.from_callable(obj, follow_wrapped=follow_wrapped, /usr/lib/python3.12/inspect.py:3054: in from_callable return _signature_from_callable(obj, sigcls=cls, /usr/lib/python3.12/inspect.py:2642: in _signature_from_callable call = _descriptor_get(call, obj) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ descriptor = obj = def _descriptor_get(descriptor, obj): if isclass(descriptor): return descriptor get = getattr(type(descriptor), '__get__', _sentinel) if get is _sentinel: return descriptor > return get(descriptor, obj, type(obj)) E TypeError: descriptor '__call__' for 'type' objects doesn't apply to a 'property' object Looking through cooler code, it seems dask.dataframe is an optional component, and it may be possible to resolve the present issue without waiting for resolution of the problem in dask. It would however require active reintroduction of dask in the build dependencies, once the root cause is fixed, to get the original test coverage on tracks. On the other hand, skipping tests involving unconditional loading of dask.dataframe would probably permit reintroduction of python-cooler in testing, even without dask. I'm not implementing such skip right now: lookup of the dask bug upstream[1] suggests there may be options to get the issue sorted at the source. [1]: https://github.com/dask/dask/pull/11035 In hope this helps, -- .''`. Étienne Mollier : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/4, please excuse my verbosity `-on air: Moon Safari - Bluebells signature.asc Description: PGP signature
Bug#1000015: marked as done (mp4h: depends on obsolete pcre3 library)
Your message dated Mon, 03 Jun 2024 20:36:42 + with message-id and subject line Bug#115: fixed in mp4h 1.3.1-17.1 has caused the Debian Bug report #115, regarding mp4h: depends on obsolete pcre3 library 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.) -- 115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mp4h Severity: important User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian --- End Message --- --- Begin Message --- Source: mp4h Source-Version: 1.3.1-17.1 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of mp4h, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated mp4h 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: Mon, 03 Jun 2024 21:06:36 +0200 Source: mp4h Architecture: source Version: 1.3.1-17.1 Distribution: unstable Urgency: medium Maintainer: Axel Beckert Changed-By: Chris Hofstaedtler Closes: 115 Changes: mp4h (1.3.1-17.1) unstable; urgency=medium . * Non-maintainer upload. . [ Yavor Doganov ] * debian/patches/pcre2.patch: New; port to PCRE2 (Closes: #115). * debian/control (Build-Depends): Replace libpcre3-dev with libpcre2-dev. Checksums-Sha1: 9eb968d152a21b342914ad985cd56815cc7de674 1948 mp4h_1.3.1-17.1.dsc 7d7d95a22733dbfe07d8dc39782b2e4294cffb31 19368 mp4h_1.3.1-17.1.debian.tar.xz 0c27b382b88103c3ab9a96daf2ed1590dc33dc91 6128 mp4h_1.3.1-17.1_arm64.buildinfo Checksums-Sha256: 4f94c878ff01a5ebbf8472a89c4e25ac38a84be160c92d61839ad8574712490a 1948 mp4h_1.3.1-17.1.dsc 7a05b953806f017f2a19a36112fc2788408a7db9dbb47b8b33fe70495a02f042 19368 mp4h_1.3.1-17.1.debian.tar.xz 0728017cdb0f6093aee106d2e39da06fd021c8cec71c039ffb18e55dad3e6c82 6128 mp4h_1.3.1-17.1_arm64.buildinfo Files: 3e4539c22f7f6916386e45a54109565d 1948 web optional mp4h_1.3.1-17.1.dsc f2eae2127dcf834e6244dcba6b163e44 19368 web optional mp4h_1.3.1-17.1.debian.tar.xz 6ee77b8fe65431599681857ac6286f2a 6128 web optional mp4h_1.3.1-17.1_arm64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmZeFRYACgkQXBPW25MF LgNgXw//ZP6mAyiJvplv7gh72HEk5Wzxu5H1nR2+eYtRX9Q96RcCJ/kgyZoj0OFO tEwLGOzI0XtU8ViueEwGIFfW47eb0oIqlD4GvbdxgKvDhFvJ+Q7znjB2TJ/Xnoq3 de9X6spsHKRAeopO11yqrWJPTRM5m7Tv/vrNobL5QCLQrrg2JG/MitGjFyOdk8kV ph5SfYpKf6ZYgB+ynS9uiTucX1nLSoF0DZp6mn4mQIfNI2f4Tti1oIHdHrF8do64 /Luh/KIZ2ONFoARxGlxQrfcrl9e+ialTpjwLBFQ/C55sDGtpsFYQTJ1UaZp+qFnB l0u90nKcZ+8YyK4C/R6W6m1eRsFOQhJgIkvhiyWzIU6Vy0EEN3ttxfmwuUN5h9Za Y+88T4gFzY6ufVf5MR9sElUwsJ8V0LPOMv81ztOAxO4Y5tx6rcTxbUaxx9rqVOdZ 9vICsd9CrZY6v0pAVErehnUxf7ttz/RNcL6hWHJ+4kgFO90aggj3yg20S4sbbOfI mzx9Ksxa9sUWlrSLZab28qvUKi/4VrYJwfrTcGkgrR0SpLdYpSS8nEgkm5BbxO2T JogzGc3m3q82WlzfL21wxxVDL+OI9zfeyGSpOeVmS2WSP2CWQ7Et5VKuRwu2GdTW GG5sWwySyALSgjAkA8tvNLSU/QtnpZmtNdJndKH1Qcw94yG0ySE= =2fzu -END PGP SIGNATURE- pgpy12yAKK9xX.pgp Description: PGP signature --- End Message ---
Bug#1072535: puma: flaky autopkgtest
Source: puma Version: 6.4.2-4 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package because it showed up as regression for glibc. I noticed that it regularly fails. This particularly on happens on amd64, where our host is used to run many tests in parallel, so this may be a race condition under load. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul https://ci.debian.net/packages/p/puma/testing/amd64/47272763/ 189s 1) Error: 189s TestPluginSystemd#test_systemd_notify_usr2_hot_restart_cluster: 189s Errno::EPIPE: Broken pipe 189s /tmp/autopkgtest-lxc.7lvlk_yq/downtmp/build.uxb/src/test/test_plugin_systemd.rb:90:in `write' 189s /tmp/autopkgtest-lxc.7lvlk_yq/downtmp/build.uxb/src/test/test_plugin_systemd.rb:90:in `assert_restarts_with_systemd' 189s /tmp/autopkgtest-lxc.7lvlk_yq/downtmp/build.uxb/src/test/test_plugin_systemd.rb:42:in `test_systemd_notify_usr2_hot_restart_cluster' 189s /tmp/autopkgtest-lxc.7lvlk_yq/downtmp/build.uxb/src/test/helper.rb:90:in `block (4 levels) in run' 189s /usr/lib/ruby/3.1.0/timeout.rb:107:in `block in timeout' 189s /usr/lib/ruby/3.1.0/timeout.rb:117:in `timeout' 189s /tmp/autopkgtest-lxc.7lvlk_yq/downtmp/build.uxb/src/test/helper.rb:88:in `block (3 levels) in run' OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072533: procps: flaky autopkgtest:
Source: procps Version: 2:4.0.4-4 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package, because it showed up in the glibc regressions. I noticed that it regularly fails on amd64, ppc64el and s390x. For your info, as it seems to correlate, those are the architectures where multiple tests run in parallel, each in their own lxc container. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul E.g. https://ci.debian.net/packages/p/procps/testing/amd64/47064938/ 52s autopkgtest [06:08:26]: test vmstat: [--- 53s test_no_arguments 53s [1;31mASSERT:[0mvalue line 53s [1;31mshunit2:ERROR[0m test_no_arguments() returned non-zero return code. 53s test_forks 53s test_disk 53s 53s Ran [1;36m3[0m tests. 53s 53s [1;31mFAILED[0m ([1;31mfailures=2[0m) 53s autopkgtest [06:08:27]: test vmstat: ---] OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: pcre3 removal
Processing commands for cont...@bugs.debian.org: > severity 1000118 serious Bug #1000118 [src:generator-scripting-language] generator-scripting-language: depends on obsolete pcre3 library Severity set to 'serious' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1072532: dh-sequence-phpcomposer: stop creating libpcre3 dependencies
Processing control commands: > affects 1072532 src:php-ml-iri Bug #1072532 [pkg-php-tools] dh-sequence-phpcomposer: stop creating libpcre3 dependencies Added indication that 1072532 affects src:php-ml-iri > affects 1072532 src:php-mockery Bug #1072532 [pkg-php-tools] dh-sequence-phpcomposer: stop creating libpcre3 dependencies Added indication that 1072532 affects src:php-mockery -- 1072532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072532: dh-sequence-phpcomposer: stop creating libpcre3 dependencies
Control: affects 1072532 src:php-ml-iri Control: affects 1072532 src:php-mockery On Thu, May 23, 2024 at 08:18:45PM +0200, Bastian Germann wrote: > The dependency generation in share/php/pkgtools/base/dependency.php for > "lib-" prefixed composer dependencies needs fixing. I caught it by it using > libpcre3, which should be libpcre2-8-0 now. But some other generated names > are also outdated and should be brought in sync with the current php > interpreter version. I've cloned #1071684 as #1072532 and set it to serious, as libpcre3 dependencies really must go away now. Given the interpreter already uses libpcre2*, they are wrong and probably useless. Please stop generating them ASAP, so pcre3 can be removed from testing. Chris
Processed: clone #1071684 for libpcre3
Processing commands for cont...@bugs.debian.org: > clone 1071684 -1 Bug #1071684 [pkg-php-tools] pkg-php-tools: composer library dependency generation Bug 1071684 cloned as bug 1072532 > retitle -1 dh-sequence-phpcomposer: stop creating libpcre3 dependencies Bug #1072532 [pkg-php-tools] pkg-php-tools: composer library dependency generation Changed Bug title to 'dh-sequence-phpcomposer: stop creating libpcre3 dependencies' from 'pkg-php-tools: composer library dependency generation'. > severity -1 serious Bug #1072532 [pkg-php-tools] dh-sequence-phpcomposer: stop creating libpcre3 dependencies Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1071684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071684 1072532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000015: mp4h: diff for NMU version 1.3.1-17.1
Dear maintainer,
I've prepared an NMU for mp4h (versioned as 1.3.1-17.1). The diff
is attached to this message.
Regards.
diff -Nru mp4h-1.3.1/debian/changelog mp4h-1.3.1/debian/changelog
--- mp4h-1.3.1/debian/changelog 2018-06-27 02:04:54.0 +0200
+++ mp4h-1.3.1/debian/changelog 2024-06-03 21:06:36.0 +0200
@@ -1,3 +1,13 @@
+mp4h (1.3.1-17.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Yavor Doganov ]
+ * debian/patches/pcre2.patch: New; port to PCRE2 (Closes: #115).
+ * debian/control (Build-Depends): Replace libpcre3-dev with libpcre2-dev.
+
+ -- Chris Hofstaedtler Mon, 03 Jun 2024 21:06:36 +0200
+
mp4h (1.3.1-17) unstable; urgency=medium
[ Axel Beckert ]
diff -Nru mp4h-1.3.1/debian/control mp4h-1.3.1/debian/control
--- mp4h-1.3.1/debian/control 2018-06-27 01:46:42.0 +0200
+++ mp4h-1.3.1/debian/control 2024-06-03 21:06:14.0 +0200
@@ -9,7 +9,7 @@
fakeroot,
gettext,
libltdl-dev,
- libpcre3-dev,
+ libpcre2-dev,
libtool,
tidy
Build-Conflicts: autoconf2.13,
diff -Nru mp4h-1.3.1/debian/patches/pcre2.patch mp4h-1.3.1/debian/patches/pcre2.patch
--- mp4h-1.3.1/debian/patches/pcre2.patch 1970-01-01 01:00:00.0 +0100
+++ mp4h-1.3.1/debian/patches/pcre2.patch 2024-06-03 21:06:14.0 +0200
@@ -0,0 +1,449 @@
+Description: Port to PCRE2.
+Bug-Debian: https://bugs.debian.org/115
+Author: Yavor Doganov
+Forwarded: no
+Last-Update: 2023-12-10
+---
+
+--- mp4h.orig/src/Makefile.am
mp4h/src/Makefile.am
+@@ -17,7 +17,7 @@
+ if LOADABLE_MODULES
+ mp4h_LDFLAGS = -export-dynamic
+ endif
+-mp4h_LDADD = -lm $(top_builddir)/lib/libmp4h.a -lpcre @LIBINTL@ $(MODULE_LDADD)
++mp4h_LDADD = -lm $(top_builddir)/lib/libmp4h.a -lpcre2-8 @LIBINTL@ $(MODULE_LDADD)
+
+ include_HEADERS = mp4h.h
+ noinst_HEADERS = builtin.h
+--- mp4h.orig/src/builtin.c
mp4h/src/builtin.c
+@@ -373,7 +373,7 @@
+ static char * utf8char_skip __P ((char *, int));
+ static int utf8char_strlen __P ((char *));
+ static int encoding_strlen __P ((char *));
+-static void substitute __P ((struct obstack *, const char *, const char *, int *));
++static void substitute __P ((struct obstack *, const char *, const char *, size_t *));
+ static void string_regexp __P ((struct obstack *, int, token_data **, int, const char *));
+ static void subst_in_string __P ((struct obstack *, int, token_data **, int));
+ static void generic_variable_lookup __P ((MP4H_BUILTIN_PROTO, boolean));
+@@ -382,6 +382,8 @@
+ static int array_member __P ((const char *, symbol *, boolean));
+ static int sort_function __P ((const void *, const void *));
+ static void logical_to_physical_paths __P ((char **));
++static void * pcre_malloc (size_t, void *);
++static void pcre_free (void *, void *);
+
+ /* This symbol controls breakings of flow statements. */
+ static symbol varbreak;
+@@ -398,7 +400,12 @@
+ struct lconv *my_locale;
+
+ /* Table of characters used by PCRE with non-C locales */
+-static const unsigned char *re_tableptr = NULL;
++static const uint8_t *re_tableptr = NULL;
++
++/* PCRE contexts needed for custom memory management and adding
++non-builtin character tables. */
++static pcre2_general_context *gen_ctxt;
++static pcre2_compile_context *comp_ctxt;
+
+ /* Timer */
+ static struct tms elapsed_time;
+@@ -662,12 +669,22 @@
+ | Initialise all builtin and predefined macros. |
+ `---*/
+
++static void *
++pcre_malloc (size_t size, void *ptr)
++{
++ return xmalloc (size);
++}
++
++static void
++pcre_free (void *ptr, void *tag)
++{
++ xfree (ptr);
++}
++
+ void
+ builtin_init (void)
+ {
+ install_builtin_table (builtin_tab);
+- pcre_malloc = xmalloc;
+- pcre_free = xfree;
+ }
+
+ /*---.
+@@ -688,18 +705,22 @@
+ varstack_check ();
+ }
+
+-static pcre *
++static pcre2_code *
+ xre_compile (const char *pattern, int cflags)
+ {
+- pcre *patcomp;
+- const char *errbuf;
+- int erroffset;
++ pcre2_code *patcomp;
++ PCRE2_UCHAR errbuf[120];
++ int errcode;
++ size_t erroffset;
+
+ if (document_encoding == ENCODING_UTF8)
+- cflags |= PCRE_UTF8;
+- patcomp = pcre_compile (pattern, cflags, , , re_tableptr);
++ cflags |= PCRE2_UTF;
++ pcre2_set_character_tables (comp_ctxt, re_tableptr);
++ patcomp = pcre2_compile ((PCRE2_SPTR) pattern, PCRE2_ZERO_TERMINATED,
++ cflags, , , comp_ctxt);
+ if (patcomp == 0)
+ {
++ pcre2_get_error_message (errcode, errbuf, sizeof (errbuf));
+ MP4HERROR ((warning_status, 0,
+ _("Warning:%s:%d: Bad regular expression `%s' at position %d: %s"),
+ CURRENT_FILE_LINE, pattern, erroffset, errbuf));
+@@ -822,11 +843,10 @@
+ register char *cp;
+ char *name;
+ int i, j, special_chars;
+- pcre *re;
+- pcre_extra *re_extra = NULL;
+- const char *errptr = NULL;
++
Processed: tagging 1072531, tagging 1072530, tagging 1072529
Processing commands for cont...@bugs.debian.org: > tags 1072531 + upstream Bug #1072531 [src:389-ds-base] 389-ds-base: CVE-2024-2199 Added tag(s) upstream. > tags 1072530 + upstream Bug #1072530 [src:smarty3] smarty3: CVE-2024-35226 Added tag(s) upstream. > tags 1072529 + upstream Bug #1072529 [src:smarty4] smarty4: CVE-2024-35226 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1072529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072529 1072530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072530 1072531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072530: smarty3: CVE-2024-35226
Source: smarty3 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for smarty3. CVE-2024-35226[0]: | Smarty is a template engine for PHP, facilitating the separation of | presentation (HTML/CSS) from application logic. In affected versions | template authors could inject php code by choosing a malicious file | name for an extends-tag. Sites that cannot fully trust template | authors should update asap. All users are advised to update. There | is no patch for users on the v3 branch. There are no known | workarounds for this vulnerability. https://github.com/smarty-php/smarty/security/advisories/GHSA-4rmg-292m-wg3w https://github.com/smarty-php/smarty/commit/76881c8d33d80648f70c9b0339f770f5f69a87a2 (support/4) https://github.com/smarty-php/smarty/commit/0be92bc8a6fb83e6e0d883946f7e7c09ba4e857a (v5.2.0) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-35226 https://www.cve.org/CVERecord?id=CVE-2024-35226 Please adjust the affected versions in the BTS as needed.
Bug#1072529: smarty4: CVE-2024-35226
Source: smarty4 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for smarty4. CVE-2024-35226[0]: | Smarty is a template engine for PHP, facilitating the separation of | presentation (HTML/CSS) from application logic. In affected versions | template authors could inject php code by choosing a malicious file | name for an extends-tag. Sites that cannot fully trust template | authors should update asap. All users are advised to update. There | is no patch for users on the v3 branch. There are no known | workarounds for this vulnerability. https://github.com/smarty-php/smarty/security/advisories/GHSA-4rmg-292m-wg3w https://github.com/smarty-php/smarty/commit/76881c8d33d80648f70c9b0339f770f5f69a87a2 (support/4) https://github.com/smarty-php/smarty/commit/0be92bc8a6fb83e6e0d883946f7e7c09ba4e857a (v5.2.0) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-35226 https://www.cve.org/CVERecord?id=CVE-2024-35226 Please adjust the affected versions in the BTS as needed.
Bug#1010445: mono-complete: Mono package in Debian is very outdated (6.8 but should be 6.12)
On Mon, Jun 03, 2024 at 06:49:13PM +0200, Antoine Le Gonidec wrote: > Please consider lowering this bug report severity. > > While it would indeed be really nice to get a more recent build of Mono > in Debian repositories (I am sure the Debian Mono Group would be happy > to get help with this) (assuming it still exists) > keeping the current outdated build is much more useful than not having > access to Mono at all from Debian repositories. Considering the amount of packages depending on mono, removing it from testing is probably out of question anyway, but that's up tio the Release and Security teams. Also, "keeping the outdated unmaintained package is better than not keeping it" is overturned by one of those teams quite often. > More generally requests for the packaging of new upstream releases > tend to use a "wishlist" severity level, not "important" and even less > "serious". Indeed, the completely correct state would be a wishlist bug "the version is too old" and a serious bug "the package is unmaintained", with the exactly same result but more paperwork, but it's a common practice to not make a separate bug report of the second type and just bump the severity of a related one. -- WBR, wRAR signature.asc Description: PGP signature
Processed: block 1033828 with 1010445
Processing commands for cont...@bugs.debian.org: > block 1033828 with 1010445 Bug #1033828 [mono-xbuild] mono-xbuild: Mono packages should provide msbuild instead of xbuild 1033828 was not blocked by any bugs. 1033828 was not blocking any bugs. Added blocking bug(s) of 1033828: 1010445 > thanks Stopping processing here. Please contact me if you need assistance. -- 1033828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: patch
Processing commands for cont...@bugs.debian.org: > tags 1072522 patch Bug #1072522 [cozy] cozy: File conflict with blackbox-terminal/0.14.0-3: /usr/share/icons/hicolor/scalable/actions/settings-symbolic.svg Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 1072522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010445: mono-complete: Mono package in Debian is very outdated (6.8 but should be 6.12)
Please consider lowering this bug report severity. While it would indeed be really nice to get a more recent build of Mono in Debian repositories (I am sure the Debian Mono Group would be happy to get help with this), keeping the current outdated build is much more useful than not having access to Mono at all from Debian repositories. Here we rely extensively on the Debian-provided 6.8 build to run non-free games built on top of the XNA/FNA engine through ./play.it (https://wiki.debian.org/Games/PlayIt). Losing these packages would make us rely on the binaries and libraries shipped by the game developers instead, that are usually older than the current Debian build. More generally requests for the packaging of new upstream releases tend to use a "wishlist" severity level, not "important" and even less "serious". pgpfcH3lp5N84.pgp Description: Signature digitale OpenPGP
Bug#1070692: marked as done (libdata-messagepack-stream-perl: FTBFS with msgpack-c 6.x)
Your message dated Mon, 03 Jun 2024 16:49:14 + with message-id and subject line Bug#1070692: fixed in libdata-messagepack-stream-perl 1.05+ds-2 has caused the Debian Bug report #1070692, regarding libdata-messagepack-stream-perl: FTBFS with msgpack-c 6.x 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.) -- 1070692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdata-messagepack-stream-perl Version: 1.05+ds-1 Severity: important Control: block 1070689 by -1 libdata-messagepack-stream-perl FTBFS with the 6.x version of the msgpack C library. Upstream renamed the library from libmsgpackc to libmsgpack-c and the pkg-config file from msgpack.pc to msgpack-c.pc, so any checks for the presence of the library at build time should handle both names. The new msgpack-c packages are available in experimental, so you can test any changes against those. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB --- End Message --- --- Begin Message --- Source: libdata-messagepack-stream-perl Source-Version: 1.05+ds-2 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libdata-messagepack-stream-perl, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libdata-messagepack-stream-perl 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: Mon, 03 Jun 2024 18:30:50 +0200 Source: libdata-messagepack-stream-perl Architecture: source Version: 1.05+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 1070692 Changes: libdata-messagepack-stream-perl (1.05+ds-2) unstable; urgency=medium . * Team upload. * Update use-packaged-msgpack.patch: Link against msgpack-c instead of msgpackc. Thanks to James McCoy for the bug report. (Closes: #1070692) * Update build dependencies: libmsgpack-dev → libmsgpack-c-dev. Cf. #1070692 * Declare compliance with Debian Policy 4.7.0. Checksums-Sha1: d4976b53f93f10993abbc76fe7575ed03c6935a5 2668 libdata-messagepack-stream-perl_1.05+ds-2.dsc 6900a455d8ea85aa8e1f3141113e27a1d32b4a7c 3476 libdata-messagepack-stream-perl_1.05+ds-2.debian.tar.xz Checksums-Sha256: 7b14f46a6a761c9a4d2a34e8d3c447c9292cd515b9f90a501a32b40ea958038a 2668 libdata-messagepack-stream-perl_1.05+ds-2.dsc 9f73183fcf529c22a57a395642dfdec9b501324226016ae4a693f66990d37143 3476 libdata-messagepack-stream-perl_1.05+ds-2.debian.tar.xz Files: 53c5bae08bbf23cc3aa6ad926a71979e 2668 perl optional libdata-messagepack-stream-perl_1.05+ds-2.dsc 582e681c3c5a4f60f3e0d08719c237a8 3476 perl optional libdata-messagepack-stream-perl_1.05+ds-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmZd8GFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbC2w/9H640z5853d6A4fsaK108uEibcxxrxEdxsE0yeCmFbGwyjaDjtMyGM6kK Ue6++t4+Pl40zx7wppT+xT/nRPHQr3ig+dqCqgNfnQi8ZElTyGLqDeuoeqlflBap SMWM5ccSN/f0QBbSEghHpAiBRerryjYhci/xX4jYdlCNw7DZ2Z0SaWT4dm0vH+Ff swrbAzmknIeVH0E+OLj9mQmvE7LFcqVNQU+6wuatqlNjIUqbT78kPwjYGCevpw6d PqxGGEI8K7Yf2VpnwF/+9jOb1EZ/E5C8laHqLO4SX9pXpXahpoeh6QdOTGVmjbsC eEykmpHhl8bdUc0xr2RFhuCO6BFnjVaTYwLs/NhWvFteS2LX7CRXj6mMsZpO/fIf /K/ikZ8XP4XqvksdqMxoXvOIyjxPg3KsAkRMXwmTUi0OOHdh5mIVe/6byZe+h8KR 1pv5xsD1Q0iDM9NBUvisYQR9+pUnrFf83rX+tENJ6db06V67uJuKIBMMhybavYn9 9Wpge5pUljo/bryK+YJGO8NyL7XEeD7mqmcnYQjCJF3xOVDG5HTVFYugA6NkofQp Y2f00hyxBW7r9m2PhlPqbehNoU3TehB2Zap8SJnhDXGkKesLTv1OM4Su9uP3JnuQ MZ7HVPC4aCUWsBW0xqlVfn8mdlNcXtkig2t7N3NpSmhW0DT5f4g= =/006 -END PGP SIGNATURE- pgpPWxOir35BK.pgp Description: PGP signature --- End Message ---
Bug#1072522: cozy: File conflict with blackbox-terminal/0.14.0-3: /usr/share/icons/hicolor/scalable/actions/settings-symbolic.svg
Hi Axel, thanks for reporting. On Mon, Jun 03, 2024 at 05:08:41PM +0200, Axel Beckert wrote: > Package: cozy > Severity: serious > Version: 1.3.0-2 > Control: affects -1 blackbox-terminal > > Hi Manuel, > > installing cozy fails if blackbox-terminal (at least at version > 0.14.0-3) is also installed due to a file conflict at > /usr/share/icons/hicolor/scalable/actions/settings-symbolic.svg (and > potentially further files as dpkg always only reports the first > occurrence): > > Preparing to unpack .../11-cozy_1.3.0-2_all.deb ... > Unpacking cozy (1.3.0-2) ... > dpkg: error processing archive > /tmp/apt-dpkg-install-RrJabH/11-cozy_1.3.0-2_all.deb (--unpack): > trying to overwrite > '/usr/share/icons/hicolor/scalable/actions/settings-symbolic.svg', which is > also in package blackbox-terminal 0.14.0-3 > > The probably easiest and cleanest way to fix this is to rename the > file. Best way would be if neither package would use such a generic file > name. (X-Debbugs-Cc'ed the blackbox-terminal maintainers.) > > -- System Information: > Debian Release: trixie/sid > APT prefers unstable > APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), > (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), > (1, 'buildd-experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) > Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set > Shell: /bin/sh linked to /usr/bin/dash > Init: sysvinit (via /sbin/init) > LSM: AppArmor: enabled I pushed a version that shall fix this bug to salsa. Can you please have a quick look and if it is OK for you, it would be nice if you could upload the package. Thanks Manuel
Bug#1072107: marked as done (libarchive: CVE-2024-26256)
Your message dated Mon, 03 Jun 2024 15:34:13 + with message-id and subject line Bug#1072107: fixed in libarchive 3.7.2-2.1 has caused the Debian Bug report #1072107, regarding libarchive: CVE-2024-26256 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.) -- 1072107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libarchive Version: 3.7.2-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 3.6.2-1 Hi, The following vulnerability was published for libarchive. CVE-2024-26256[0]: | libarchive Remote Code Execution Vulnerability If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-26256 https://www.cve.org/CVERecord?id=CVE-2024-26256 [1] https://github.com/advisories/GHSA-2jc9-36w4-pmqw [2] https://github.com/libarchive/libarchive/commit/eb7939b24a681a04648a59cdebd386b1e9dc9237 Regards, Salvatore --- End Message --- --- Begin Message --- Source: libarchive Source-Version: 3.7.2-2.1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of libarchive, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated libarchive 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: Sat, 01 Jun 2024 15:50:51 +0200 Source: libarchive Architecture: source Version: 3.7.2-2.1 Distribution: unstable Urgency: medium Maintainer: Peter Pentchev Changed-By: Salvatore Bonaccorso Closes: 1072107 Changes: libarchive (3.7.2-2.1) unstable; urgency=medium . * Non-maintainer upload. * fix: OOB in rar e8 filter (CVE-2024-26256) (Closes: #1072107) * fix: OOB in rar delta filter * fix: OOB in rar audio filter Checksums-Sha1: d41ac6ed23dddb4a02f1cd642d10884d73d53aaa 2736 libarchive_3.7.2-2.1.dsc 3b18f2d47a498499f74e6de2f47a5e1e243c4558 28476 libarchive_3.7.2-2.1.debian.tar.xz 4742c7e8c1a44609402fe387ea7d2e2176cdda77 7148 libarchive_3.7.2-2.1_source.buildinfo Checksums-Sha256: a551872217995576b0cb2a9839a57897b943f889b3e5eb9df54ae94d448c4e2f 2736 libarchive_3.7.2-2.1.dsc 90b8ee2253cd04c4c9c9626bcd5ec6d94c88a38dd12fc94617a3b1e774ef2647 28476 libarchive_3.7.2-2.1.debian.tar.xz 02c5af5697cd40eae624921558141bd4578449f25d52ffde302afd24a08cf29d 7148 libarchive_3.7.2-2.1_source.buildinfo Files: c1492dba14abe06c1e3dd07896b840e9 2736 libs optional libarchive_3.7.2-2.1.dsc 5b82aaa9067dd24301604fc6c1b9d2ed 28476 libs optional libarchive_3.7.2-2.1.debian.tar.xz ff6e5308ef77a1841db4f7d22e80fefc 7148 libs optional libarchive_3.7.2-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmZbJ4NfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EwksP/0G0MJAHES2+a7K72RHvpqcG5HifvU+G hXbQwPUsBP06HX6WCCX26bK+Txf9Q3fCxC0otpGCPuEqoWFcbp+9I7LIfoA8Mbkp HzLEdXtjwguAwOevLiTxFEvskiHCw9YM1kQKfsGiiM2HuGG0SWktgt4PyZ60Ah5J hMfxmrqLkhJE2xNtJmvUiU8m8VePcssj0ukJaE7wcWGdaf0/PxFJ4J6feSLbkwjp N+Bnu4um83uMqxS95Zu/a8XskImOe6K+VWF/2bHeZgRCPmZKu9pGtwOmlnAITG+R 3REXtw7s5pthdBkrMvzWq5PdOEqBAVaDw1rpzcahBSzRks9Lx6C1IVwJc9JEDCFm 2WYbV0ktHz9BlnYG9KWX9bqa2ubTllKd8rGKF/v3uwvGBf0zaM8b+ITVq0an9qDd oRJRSOjbw0yYSgOeLBJIAAwDaVKelP9kNhIi/dbwsgZFEKK86GYB2l3dwI90WteM DuNec4z+G7MI3p9xZ8H8RwKZ/sNc2pb/P8rYJ5DSgLBmfqJXs4fw8PVzix1+rjGk /8bqwTrYsJ8nFQlSyX8yINq6EuwTHZC9jSqKIDM8CGodOdBJH3wDHrVq2G3QzKBZ 5TDFUPllKVnX8e8nblkgIo+RqVxdldHXS9ejhKzLG79SiRM3ZCK/PIrJUtvh3DB/ Cs6lTjrtHLh7 =fG8V -END PGP SIGNATURE- pgpKTo6Xs8CRN.pgp Description: PGP signature --- End Message ---
Processed: cozy: File conflict with blackbox-terminal/0.14.0-3: /usr/share/icons/hicolor/scalable/actions/settings-symbolic.svg
Processing control commands: > affects -1 blackbox-terminal Bug #1072522 [cozy] cozy: File conflict with blackbox-terminal/0.14.0-3: /usr/share/icons/hicolor/scalable/actions/settings-symbolic.svg Added indication that 1072522 affects blackbox-terminal -- 1072522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072522: cozy: File conflict with blackbox-terminal/0.14.0-3: /usr/share/icons/hicolor/scalable/actions/settings-symbolic.svg
Package: cozy Severity: serious Version: 1.3.0-2 Control: affects -1 blackbox-terminal Hi Manuel, installing cozy fails if blackbox-terminal (at least at version 0.14.0-3) is also installed due to a file conflict at /usr/share/icons/hicolor/scalable/actions/settings-symbolic.svg (and potentially further files as dpkg always only reports the first occurrence): Preparing to unpack .../11-cozy_1.3.0-2_all.deb ... Unpacking cozy (1.3.0-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-RrJabH/11-cozy_1.3.0-2_all.deb (--unpack): trying to overwrite '/usr/share/icons/hicolor/scalable/actions/settings-symbolic.svg', which is also in package blackbox-terminal 0.14.0-3 The probably easiest and cleanest way to fix this is to rename the file. Best way would be if neither package would use such a generic file name. (X-Debbugs-Cc'ed the blackbox-terminal maintainers.) -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled
Bug#1072521: fakeroot hangs on some commands with faked-sysv using 100% CPU
Package: fakeroot
Version: 1.34-1
Severity: critical
Hello,
Assigning to fakeroot for now, but not sure it's not something for ftp.d.o (a
binNMU) or libc6.
Today, after an upgrade, I am not able to build packages with sbuild as
it hanks with this process tree:
(TZ is CEST)
peb 8859 0.1 0.0 24048 17644 pts/4Ss 14:15 0:09 | \_ zsh
peb 224642 3.2 0.1 37664 32640 pts/4S+ 16:24 0:00 | | \_
/usr/bin/perl /usr/bin/sbuild -As --source-only-changes
peb 224665 0.0 0.0 2596 1536 pts/4S+ 16:24 0:00 | |
\_ /bin/sh /usr/bin/fakeroot debian/rules clean
peb 224680 0.0 0.0 6196 2304 pts/4S+ 16:24 0:00 | |
\_ /usr/bin/make -f debian/rules clean
In parallel, one can find a faked-sysv process eating all a CPU resources.
peb 225847 100 0.0 2440 648 pts/4R+ 16:25 0:02 \_
/usr/bin/faked-sysv
When running make -f debian/rules clean directly, everything works well.
Running it through fakeroot with strace gives:
❯ LC_ALL=C strace /bin/sh /usr/bin/fakeroot
~/git/cgg/projects/OaaSiS/packaging/libbnxtre/libbnxtre/debian/rules clean
execve("/bin/sh", ["/bin/sh", "/usr/bin/fakeroot",
"/home/peb/git/cgg/projects/OaaSi"..., "clean"], 0x7ffd1e5d6348 /* 66 vars */)
= 0
brk(NULL) = 0x55d974431000
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f07e4275000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=103847, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 103847, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f07e425b000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P~\2\0\0\0\0\0"..., 832)
= 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
newfstatat(3, "", {st_mode=S_IFREG|0755, st_size=1933688, ...}, AT_EMPTY_PATH)
= 0
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
mmap(NULL, 1985936, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f07e4076000
mmap(0x7f07e409c000, 1404928, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x26000) = 0x7f07e409c000
mmap(0x7f07e41f3000, 348160, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x17d000) = 0x7f07e41f3000
mmap(0x7f07e4248000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1d1000) = 0x7f07e4248000
mmap(0x7f07e424e000, 52624, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f07e424e000
close(3)= 0
mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f07e4073000
arch_prctl(ARCH_SET_FS, 0x7f07e4073740) = 0
set_tid_address(0x7f07e4073a10) = 233801
set_robust_list(0x7f07e4073a20, 24) = 0
rseq(0x7f07e4074060, 0x20, 0, 0x53053053) = 0
mprotect(0x7f07e4248000, 16384, PROT_READ) = 0
mprotect(0x55d9731b3000, 8192, PROT_READ) = 0
mprotect(0x7f07e42a7000, 8192, PROT_READ) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024,
rlim_max=RLIM64_INFINITY}) = 0
munmap(0x7f07e425b000, 103847) = 0
getuid()= 1000
getgid()= 1000
getpid()= 233801
rt_sigaction(SIGCHLD, {sa_handler=0x55d9731a8550, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7f07e40b3580}, NULL, 8) = 0
geteuid() = 1000
getrandom("\x87\x75\x90\x03\xa9\x28\xe2\x59", 8, GRND_NONBLOCK) = 8
brk(NULL) = 0x55d974431000
brk(0x55d974452000) = 0x55d974452000
getppid() = 233798
newfstatat(AT_FDCWD,
"/home/peb/git/cgg/projects/OaaSiS/packaging/libbnxtre/libbnxtre",
{st_mode=S_IFDIR|0755, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, ".", {st_mode=S_IFDIR|0755, st_size=4096, ...}, 0) = 0
openat(AT_FDCWD, "/usr/bin/fakeroot", O_RDONLY) = 3
fcntl(3, F_DUPFD, 10) = 10
close(3)= 0
fcntl(10, F_SETFD, FD_CLOEXEC) = 0
geteuid() = 1000
getegid() = 1000
rt_sigaction(SIGINT, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGINT, {sa_handler=0x55d9731a8550, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7f07e40b3580}, NULL, 8) = 0
rt_sigaction(SIGQUIT, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGQUIT, {sa_handler=SIG_DFL, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER, sa_restorer=0x7f07e40b3580}, NULL, 8) = 0
rt_sigaction(SIGTERM, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGTERM, {sa_handler=SIG_DFL, sa_mask=~[RTMIN RT_1],
sa_flags=SA_RESTORER,
Processed: Re: Bug#1072512: debci: mutter fails tests
Processing control commands: > severity -1 important Bug #1072512 [src:mutter] debci: mutter fails tests Severity set to 'important' from 'serious' > tags -1 upstream Bug #1072512 [src:mutter] debci: mutter fails tests Added tag(s) upstream. -- 1072512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072512: debci: mutter fails tests
Control: severity -1 important Control: tags -1 upstream On Mon, Jun 3, 2024 at 4:16 AM Drew Parsons wrote: > Source: mutter > Version: 44.8-3.1 > Severity: serious > Justification: debci > Control: affects -1 libxcursor-dev > > mutter is failing tests in debci. > This is blocking migration of libxcursor to testing. The tests passed on retry and libxcursor is no longer blocked from migrating. Sorry that the autopkgtests are flaky. :( Thank you, Jeremy Bícha
Bug#1072517: /etc/apparmor.d/cockpit-desktop in Zeile 1: Could not open 'abi/4.0'
Package: cockpit-ws Version: 317-1 Severity: serious File: /etc/apparmor.d/cockpit-desktop During todays boot I encountered the following failure: × apparmor.service - Load AppArmor profiles Loaded: loaded (/usr/lib/systemd/system/apparmor.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Mon 2024-06-03 14:35:42 CEST; 1min 55s ago Invocation: 05781cbd4c8c4e7e96203d87010c5716 Docs: man:apparmor(7) https://gitlab.com/apparmor/apparmor/wikis/home/ Process: 1014 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, status=1/FAILURE) Main PID: 1014 (code=exited, status=1/FAILURE) Jun 03 14:35:42 mars apparmor.systemd[1014]: Restarting AppArmor Jun 03 14:35:42 mars apparmor.systemd[1014]: Reloading AppArmor profiles Jun 03 14:35:42 mars apparmor.systemd[1026]: AppArmor-Analysefehler f?r /etc/apparmor.d in profile /etc/apparmor.d/cockpit-desktop in Zeile 1: Could not open 'abi/4.0': Datei oder Verzeichnis nicht gefunden Jun 03 14:35:42 mars apparmor.systemd[1040]: Skipping profile in /etc/apparmor.d/disable: usr.bin.thunderbird Jun 03 14:35:42 mars apparmor.systemd[1065]: AppArmor-Analysefehler f?r /etc/apparmor.d/cockpit-desktop in profile /etc/apparmor.d/cockpit-desktop in Zeile 1: Could not open 'abi/4.0': Datei oder Verzeichnis nicht gefunden Jun 03 14:35:42 mars apparmor.systemd[1134]: Skipping profile in /etc/apparmor.d/disable: usr.bin.thunderbird Jun 03 14:35:42 mars apparmor.systemd[1014]: Error: At least one profile failed to load Jun 03 14:35:42 mars systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE Jun 03 14:35:42 mars systemd[1]: apparmor.service: Failed with result 'exit-code'. Jun 03 14:35:42 mars systemd[1]: Failed to start apparmor.service - Load AppArmor profiles. I suppose, the cockpit-desktop AA profile uses features that are not available on Debian: # apt-cache policy apparmor apparmor: Installed: 3.0.13-2 Candidate: 3.0.13-2 Version table: *** 3.0.13-2 500 500 http://deb.debian.org/debian sid/main amd64 Packages 100 /var/lib/dpkg/status -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.8.12-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 cockpit-ws depends on: ii adduser 3.137 ii glib-networking 2.80.0-1 ii libc6 2.38-12 ii libcrypt1 1:4.4.36-4 ii libglib2.0-0t64 2.80.2-2 ii libgnutls30t64 3.8.5-4 ii libgssapi-krb5-21.20.1-6+b1 ii libjson-glib-1.0-0 1.8.0-2+b1 ii libpam0g1.5.3-7 ii libsystemd0 256~rc3-7 ii openssl 3.2.1-3 ii systemd 256~rc3-7 cockpit-ws recommends no packages. Versions of packages cockpit-ws suggests: ii python33.11.8-1 pn sssd-dbus -- no debconf information
Bug#1071182: marked as done (dracut: requires changes for systemd 256; boot fails otherwise)
Your message dated Mon, 03 Jun 2024 12:34:09 + with message-id and subject line Bug#1071182: fixed in dracut 102-1 has caused the Debian Bug report #1071182, regarding dracut: requires changes for systemd 256; boot fails otherwise 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.) -- 1071182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dracut Version: 060+5-1 Severity: serious Tags: upstream X-Debbugs-Cc: Debian systemd Maintainers Hi, dracut requires two changes for systemd 256: 1. systemd 256 makes /usr read-only in initrd: - https://github.com/systemd/systemd/issues/32511 - https://github.com/dracut-ng/dracut-ng/issues/253 2. libkmod.so.2 might need to be installed manually: - https://github.com/systemd/systemd/issues/32508#issuecomment-2080063182 systemd should get a `Breaks: dracut (<< fixed-version-goes-here)` once a fixed version is uploaded. Ansgar -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'stable'), (300, 'buildd-unstable'), (300, 'unstable'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.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 -- no debconf information --- End Message --- --- Begin Message --- Source: dracut Source-Version: 102-1 Done: Thomas Lange We believe that the bug you reported is fixed in the latest version of dracut, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Lange (supplier of updated dracut 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: Mon, 03 Jun 2024 14:14:11 +0200 Source: dracut Architecture: source Version: 102-1 Distribution: unstable Urgency: low Maintainer: Thomas Lange Changed-By: Thomas Lange Closes: 753752 1022129 1029324 1033158 1041614 1059501 1068250 1071182 1071592 1072174 Changes: dracut (102-1) unstable; urgency=low . * new upstream: Closes: 1029324, 1041614, 1022129, 1071592, 1072174, 1068250 Closes: 1071182, 1059501 * change to new dracut-ng upstream repository, the package name remains unchanged * apply salsa MR #11, Closes: 753752 * move kpartx from depends to recommends, Closes: 1033158 Checksums-Sha1: 243e80c680cd0aa32ab388aed698535d0561b874 2675 dracut_102-1.dsc 8dd0a35897b9ccc409bc87d03f23962b397722b0 404872 dracut_102.orig.tar.xz 6dc7d7a7ee6de1ec53eddf027d75dee08764889a 16560 dracut_102-1.debian.tar.xz e0829285e0b086e9867ee76f0f239f1951af9152 9784 dracut_102-1_amd64.buildinfo Checksums-Sha256: 2e1f23e97c233cbd7748b5ac2bf675064b46d8529dcd38f0298c3598910b7e5d 2675 dracut_102-1.dsc ee392497f92452a4141d23e5fa23d2594ea63c4126a4b57cc78b5a297a1ba7c9 404872 dracut_102.orig.tar.xz 3f1a6aa8b4b26361d31b857c1ce6aef9b1153291a149218aeb9183761cee9b64 16560 dracut_102-1.debian.tar.xz bc0a191b5722bf23599447ff69a354e19f4045ca3ac24a69634592ea15fb595c 9784 dracut_102-1_amd64.buildinfo Files: d4381750201c692cba6d28f3d405e3b9 2675 utils optional dracut_102-1.dsc ea0b3b3cda1f12410f0ac4de0c39e38b 404872 utils optional dracut_102.orig.tar.xz 6c56e5295e59486e5cf9fea837334614 16560 utils optional dracut_102-1.debian.tar.xz 3c6272c7a7a94dac2074d1fc6dc65590 9784 utils optional dracut_102-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEsR7jJz9rLetSjJPaK/jZ/gdLzeQFAmZdtBwRHGxhbmdlQGRl Ymlhbi5vcmcACgkQK/jZ/gdLzeQAtQ//ZbwAgHrc0BMHId63qA6PB6zXm7pezs8e Z3CIfZJGsi0uSp5ABjjnCb+2rX/FAIjFcO7f23QE03rIwwpVihm3EKGVeGCh7eEV 9O2wO4RD7Ccd/NFXWVm/TThtAUtYAeeiJKCKBwPATj/ybadnzJbQF74w/wY/D4wp fayx0vW2Yw/+Rb+d1ypnRN9EmZDlhnfsRIPNMzNHJ7PUuVa9ozSxEEraqhgwyfQL o4+SJtur5rKYOkef8eEF7uBaZjCenRlBzeDW1DvlnF24H+ADcUENNU1Pp89CixKT JG2kipq1of8ERqVA+96DyG2bkt2PqPOHnD9TBEy9BFff00g91B5RkX0tOpG14g0P
Bug#1070693: marked as done (tmate: FTBFS with msgpack-c 6.x)
Your message dated Mon, 03 Jun 2024 12:05:24 + with message-id and subject line Bug#1070693: fixed in tmate 2.4.0-3 has caused the Debian Bug report #1070693, regarding tmate: FTBFS with msgpack-c 6.x 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.) -- 1070693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tmate Version: 2.4.0-2 Severity: important Control: block 1070689 by -1 tmate FTBFS with the 6.x version of the msgpack C library. Upstream renamed the library from libmsgpackc to libmsgpack-c and the pkg-config file from msgpack.pc to msgpack-c.pc, so any checks for the presence of the library at build time should handle both names. The new msgpack-c packages are available in experimental, so you can test any changes against those. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB --- End Message --- --- Begin Message --- Source: tmate Source-Version: 2.4.0-3 Done: Sergio de Almeida Cipriano Junior We believe that the bug you reported is fixed in the latest version of tmate, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sergio de Almeida Cipriano Junior (supplier of updated tmate 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: Mon, 03 Jun 2024 08:28:26 -0300 Source: tmate Architecture: source Version: 2.4.0-3 Distribution: unstable Urgency: medium Maintainer: Lucas Kanashiro Changed-By: Sergio de Almeida Cipriano Junior Closes: 1070693 Changes: tmate (2.4.0-3) unstable; urgency=medium . [ francisco1code ] * Change Forwarded to Applied-Upstream: - d/p/04-fix-spelling-error-in-binary.patch. - d/p/03-manpage.patch. * d/watch: Change upstream tarball path. . [ Sergio de Almeida Cipriano Junior ] * d/rules: Simplify target by using execute_before_* from dh 13. * d/p/0004-Fix-finding-msgpack-6.patch: Backport fix for msgpack 6+ Thanks to James McCoy for the bug report (Closes: #1070693). * d/patches: Rename and refresh patches with gbp. * Update build dependency: libmsgpack-dev -> libmsgpack-c-dev. * d/rules: export DEB_BUILD_MAINT_OPTIONS before the include. * d/control: - Build depend on pkgconf instead of pkg-config. - Bump Standards-Version from 4.5.0 to 4.7.0, no changes needed. - Change my email in the Uploaders field. * Add myself in the debian section of d/copyright. Checksums-Sha1: 0f7e679069fb359eb735da3f3314485830759c6c 2010 tmate_2.4.0-3.dsc 722ac9a3ba42540b5267456e15f1ef995dd9de0d 7164 tmate_2.4.0-3.debian.tar.xz 201f448f225509a9a5f62ca88b8320c18110de28 6536 tmate_2.4.0-3_amd64.buildinfo Checksums-Sha256: 0c911b5c65690cec6796d796295c312a00b799bc3781fe9a5f3af15177e16230 2010 tmate_2.4.0-3.dsc d72d96b5b94a091460d083b7a107bfbd7fa73781d0e44a974566e1028fc6e631 7164 tmate_2.4.0-3.debian.tar.xz 23af5bdec359da293840942ad56c96e0868b55006692e66d5d2d92c46037a1d2 6536 tmate_2.4.0-3_amd64.buildinfo Files: ddd918473b9e80ab0510eede7d318efc 2010 devel optional tmate_2.4.0-3.dsc c9b2ec9a530172e3eeabb7a5d8036bc7 7164 devel optional tmate_2.4.0-3.debian.tar.xz 616862ad5d405839b2a54fb05963567b 6536 devel optional tmate_2.4.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEERXPp0q0n24lrvy+e8V3OUxYFHycFAmZdq4sACgkQ8V3OUxYF HycBGQ//TwnwMU7H8dw7LnrXdHMTomvHR4VrdgV5ARAmQNSKvwEg19CfwqAwUD6e wzDKcnKJBjX7uU1wydw0ogiXbxFBshOu5mVivnGQQEk2vCKrZ4cO7TkfyjAsy/8Y /rACZbqspsgUtYqt2Gf+UTbF3sSUV+9DVigJpbO1chv03MWChIGKOY4y9dD/IotR WFqcH6fasnfn2huj7H0ER7vdbtHRJcnk59BlgE6BX0712HrcMxEpvshiPijF5k0t aHqF215BQFhYfVv0tgnjN8HtX99SPtqfJ1yVP9sG8S4jSnl1RQivi9kFjIizH3eD D1Dw4X5c0qeDuTRZAyfi9CuT5pvn2InS7T3wq0spJmpEVorjt9Gswv+8iat6Q/Ce g/yGu1iQYVj7N9Uq8sNfqPh8rHsJcRMEiSOuUQOC1Vp4NrHWLfXxCa/dwt32fTy+ zISPcsiyh30ObzvHQ7j2PQNwdXB8sbaGW2erAyIrAGQKykL/rktzBRRjid7dpiC5 ndcyACk3cu306PGJ54/E0X8hifQO3sikSHtIw5jTUwlaSwKWmRuvcIaszEeyivpr 9dOC1I/CXYhSLqmM19HT2PKOyWxM89RWg7eOZ2O7zGFm3U/Ipi1/2p6JkwN7P0hH QFFk4pZGoRoyMOJ52KNrhvjFQbhXf3Z7ukhSG3jHzWhzon/i1ac= =Ew6U -END PGP
Bug#1071769: marked as done (golang-github-google-cel-go: FTBFS: panic: interface conversion: ref.Val is *types.Err, not types.Bool)
Your message dated Mon, 03 Jun 2024 11:19:10 +
with message-id
and subject line Bug#1071769: fixed in golang-github-google-cel-go 0.18.2+ds-1
has caused the Debian Bug report #1071769,
regarding golang-github-google-cel-go: FTBFS: panic: interface conversion:
ref.Val is *types.Err, not types.Bool
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.)
--
1071769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-github-google-cel-go
Version: 0.12.5+ds-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --builddirectory=build --buildsystem=golang --with=golang
dh_update_autotools_config -O--builddirectory=build -O--buildsystem=golang
dh_autoreconf -O--builddirectory=build -O--buildsystem=golang
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
mkdir -p -v build/src/github.com/google/cel-go/vendor
mkdir: created directory 'build'
mkdir: created directory 'build/src'
mkdir: created directory 'build/src/github.com'
mkdir: created directory 'build/src/github.com/google'
mkdir: created directory 'build/src/github.com/google/cel-go'
mkdir: created directory 'build/src/github.com/google/cel-go/vendor'
cp -v -a debian/missing-sources/* build/src/github.com/google/cel-go/vendor
[... snipped ...]
--- PASS: TestParse/135_? (0.00s)
--- PASS: TestParse/134_-- (0.00s)
--- PASS: TestParse/133_ind[a{b}] (0.00s)
--- PASS: TestParse/132_{:a} (0.00s)
--- PASS: TestParse/131_{a} (0.00s)
--- PASS: TestParse/130_msg{:a} (0.00s)
--- PASS: TestParse/129_func{{a}} (0.00s)
--- PASS: TestParse/128_[1,_2,_3].map(var,_var_*_var) (0.00s)
--- PASS: TestParse/127_while (0.00s)
--- PASS: TestParse/126_void (0.00s)
--- PASS: TestParse/125_var (0.00s)
--- PASS: TestParse/124_return (0.00s)
--- PASS: TestParse/123_namespace (0.00s)
--- PASS: TestParse/122_package (0.00s)
--- PASS: TestParse/121_loop (0.00s)
--- PASS: TestParse/120_let (0.00s)
--- PASS: TestParse/119_in (0.00s)
--- PASS: TestParse/118_import (0.00s)
--- PASS: TestParse/117_if (0.00s)
--- PASS: TestParse/116_function (0.00s)
--- PASS: TestParse/115_for (0.00s)
--- PASS: TestParse/114_else (0.00s)
--- PASS: TestParse/113_continue (0.00s)
--- PASS: TestParse/112_const (0.00s)
--- PASS: TestParse/93_x["a"].single_int32_==_23 (0.00s)
--- PASS: TestParse/110_as (0.00s)
--- PASS: TestParse/109___''_in_['',_'',_'']&&_in. (0.00s)
--- PASS: TestParse/108_""_in_["",_"",_""] (0.00s)
--- PASS: TestParse/107_"\a\b\f\n\r\t\v\'\"\\\?_Illegal_escape_\>" (0.00s)
--- PASS: TestParse/106_"\xFh" (0.00s)
--- PASS: TestParse/105_"\a\b\f\n\r\t\v'\"\\\?_Legal_escapes" (0.00s)
--- PASS: TestParse/104_"\U03A8\?" (0.00s)
--- PASS: TestParse/103_"hi\u263A_\u263Athere" (0.00s)
--- PASS: TestParse/102_"\303\277" (0.00s)
--- PASS: TestParse/101_"\xC3\XBF" (0.00s)
--- PASS: TestParse/100_{"a":_1}."a" (0.00s)
--- PASS: TestParse/99_"abc"_+_"def" (0.00s)
--- PASS: TestParse/98_1_+_+ (0.00s)
--- PASS: TestParse/97_1_+_2_*_3_-_1_/_2_==_6_%_1 (0.00s)
--- PASS: TestParse/96_b"abc"_+_B"def" (0.00s)
--- PASS: TestParse/95_false_&&_!true_||_false_?_2_:_3 (0.00s)
--- PASS: TestParse/94_x.single_nested_message_!=_null (0.00s)
--- PASS: TestParse/84_{1:2u,_2:3u} (0.00s)
--- PASS: TestParse/92_1.all(2,_3) (0.00s)
--- PASS: TestParse/91_[1,3,4][0] (0.00s)
--- PASS: TestParse/90_"\"" (0.00s)
--- PASS: TestParse/89_1_+_2_3_+ (0.00s)
--- PASS: TestParse/88_1_+_$ (0.00s)
--- PASS: TestParse/87_size(x)_==_x.size() (0.00s)
--- PASS: TestParse/86_TestAllTypes(){single_int32:_1,_single_int64:_2}
(0.00s)
--- PASS: TestParse/85_TestAllTypes{single_int32:_1,_single_int64:_2}
(0.00s)
--- PASS: TestParse/79_{foo:_5,_bar:_"xyz",_} (0.00s)
--- PASS: TestParse/83_[]_+_[1,2,3,]_+_[4] (0.00s)
--- PASS: TestParse/82_{ (0.00s)
--- PASS: TestParse/81_a_<_5_||_a_>_10 (0.00s)
--- PASS: TestParse/80_a_>_5_&&_a_<_10 (0.00s)
--- PASS: TestParse/77_[3,_4,_5,] (0.01s)
--- PASS: TestParse/78_{foo:_5,_bar:_"xyz"} (0.00s)
--- PASS: TestParse/76_[3,_4,_5] (0.00s)
--- PASS: TestParse/75_SomeMessage{foo:_5,_bar:_"xyz"} (0.00s)
--- PASS:
Bug#1072012: libxml-libxml-perl: new upstream release 2.0210, addressing test failures with libxml2 >= 2.11
Hi, On Sat, Jun 1, 2024 at 2:26 AM gregor herrmann wrote: > > On Wed, 29 May 2024 23:15:10 +0300, Niko Tyni wrote: > > > But I think we should add dependency metadata so that the release team, > > britney, debci etc. can see the need for a rebuild when we have a > > "broken" combination, and then hint the "correct" versions for testing > > migration together. Updating libxml2 "middle version" would then mean > > a mini-transition. > > Ack. > > > At the moment that would mean having libxml-libxml-perl > > Depends: libxml2 (>> 2.12), libxml2 (<< 2.13~) > > or something like that, with the numbers automatically generated during > > the build of course. > > Implemented in 2.0207+dfsg+really+2.0134-3: > > Depends: perl (>= 5.38.2-5), perlapi-5.38.2, libc6 (>= 2.14), libxml2 (>= > 2.12), libxml2 (<< 2.13~), libxml-namespacesupport-perl, libxml-sax-perl > > > > On Fri, 31 May 2024 15:12:03 +0800, Aron Xu wrote: > > > I'm fine with the resolution and I have committed a similar thing to > > libxml2 following gregoa's advice: > > https://salsa.debian.org/xml-sgml-team/libxml2/-/commit/f0f2fc3a207aed66e651b0d75ecea2d9b2028c8c > > Thanks, please adjust the Breaks to > > Breaks: > libxml-libxml-perl (<< 2.0207+dfsg+really+2.0134-3~), > Done. > > Also, please don't close _this_ bug in the upload; getting the > dependency meta-information in order should fix the autopkgtest > failures, but the core problem most probably will persist: The test > failures on several architectures which makes the package FTBFS: > https://buildd.debian.org/status/package.php?p=libxml-libxml-perl > I have removed the Closes from changelog and uploaded libxml2 to unstable. Let's see how it goes. Thanks, Aron
Bug#1071856: src:alttab: fails to migrate to testing for too long: autopkgtest regression
This patch should fix the issue: https://salsa.debian.org/debian/alttab/-/merge_requests/1
Processed: debci: mutter fails tests
Processing control commands: > affects -1 libxcursor-dev Bug #1072512 [src:mutter] debci: mutter fails tests Added indication that 1072512 affects libxcursor-dev -- 1072512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072512: debci: mutter fails tests
Source: mutter Version: 44.8-3.1 Severity: serious Justification: debci Control: affects -1 libxcursor-dev mutter is failing tests in debci. This is blocking migration of libxcursor to testing. The failing tests in the last amd64 unstable run are 125s # Running test: mutter-12/set-override-redirect-parent.test 126s # Executing: mutter-12/set-override-redirect-parent.test 128s # FAIL: mutter-12/set-override-redirect-parent.test (Child process exited with code 133) 128s not ok - mutter-12/set-override-redirect-parent.test 139s # Running test: mutter-12/closed-transient-no-input-parent-delayed-focus-default-cancelled.test 141s # Executing: mutter-12/closed-transient-no-input-parent-delayed-focus-default-cancelled.test 142s # FAIL: mutter-12/closed-transient-no-input-parent-delayed-focus-default-cancelled.test (Child process exited with code 133) 142s not ok - mutter-12/closed-transient-no-input-parent-delayed-focus-default-cancelled.test 162s # SUMMARY: total=30; passed=28; skipped=0; failed=2; user=18.9s; system=9.3s; maxrss=173092 162s # FAIL: mutter-12/set-override-redirect-parent.test (Child process exited with code 133) 162s # FAIL: mutter-12/closed-transient-no-input-parent-delayed-focus-default-cancelled.test (Child process exited with code 133)
Processed: retitle 1072391 to python3-specreduce: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py and /usr/lib/python3/dist-packages/docs/conf.py ...
Processing commands for cont...@bugs.debian.org: > retitle 1072391 python3-specreduce: ships > /usr/lib/python3/dist-packages/build/lib/docs/conf.py and > /usr/lib/python3/dist-packages/docs/conf.py Bug #1072391 [python3-specreduce] python3-specreduce: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py Changed Bug title to 'python3-specreduce: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py and /usr/lib/python3/dist-packages/docs/conf.py' from 'python3-specreduce: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py'. > retitle 1072507 python3-google-auth-oauthlib: ships > /usr/lib/python3/dist-packages/docs/conf.py Bug #1072507 [python3-google-auth-oauthlib] python3-google-auth-oauthlib: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py Changed Bug title to 'python3-google-auth-oauthlib: ships /usr/lib/python3/dist-packages/docs/conf.py' from 'python3-google-auth-oauthlib: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1072391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072391 1072507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: python3-specreduce has an undeclared file conflict
Processing control commands: > retitle -1 python3-specreduce: ships > /usr/lib/python3/dist-packages/build/lib/docs/conf.py Bug #1072391 [python3-specreduce] python3-specreduce has an undeclared file conflict Changed Bug title to 'python3-specreduce: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py' from 'python3-specreduce has an undeclared file conflict'. -- 1072391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072391: python3-specreduce has an undeclared file conflict
Followup-For: Bug #1072391 Control: retitle -1 python3-specreduce: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py /usr/lib/python3/dist-packages/build/lib/docs/conf.py is an overly generic name (and outside the package's namespace) that shouldn't be shipped in any package. Andreas
Bug#1072507: python3-google-auth-oauthlib: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py
Package: python3-google-auth-oauthlib Version: 1.2.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. Preparing to unpack .../python3-google-auth-oauthlib_1.2.0-1_all.deb ... Unpacking python3-google-auth-oauthlib (1.2.0-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-google-auth-oauthlib_1.2.0-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/docs/conf.py', which is also in package python3-specreduce 1.4.0-1 Errors were encountered while processing: /var/cache/apt/archives/python3-google-auth-oauthlib_1.2.0-1_all.deb /usr/lib/python3/dist-packages/build/lib/docs/conf.py is an overly generic name (and outside the package's namespace) that shouldn't be shipped in any package. There could be even more conflicting files. cheers, Andreas
